This page is part of the Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

User Attributes

User attributes provides additional information about the user of a device. This information may be used to augment the measurement capabilities of the device. Information such as user height and weight might need to be provided to allow an app or device to compute from the number of steps taken as measured by an accelerometer, into an estimate of distance traveled (computed as a function of user height) or calories burned (computed as a function of user weight).

Attribute values about the user may be dynamically configured, or even determined by the device (e.g., current user state, such as sedentary, active, sleeping) which might enable an application to compute other functions. This data may be user entered, or determined through other means.

Some configuration data may also come from User Demographics such as age and gender. Note though, care must be taken to avoid confusing physical attributes (such as birth sex) which may be necessary to properly configure a device and gender identity, which should be a user preference.

Feature: User Height

If User Height is essential to compute an observation the app/infra **SHALL** be able to capture/report the user's height as an attribute of the user .

NOTE: Information is considered to be essential to compute an observation when the value of that observation would change if the information changes. Examples for height include distance traveld or calories used during an activity (e.g., steps or stairs climbed)

Scenario: Height is Available

NOTE 1: Additional steps may be necessary to access the Height given that the User is known. This may include retrieving the height in some way as an attribute of the user

NOTE 2: If the height is not essential for measurement, (i.e., the precondition is not met) then this test is not applicable and not reported during the assessment.

GIVEN

a <User> with <Height>

AND

an <App>

AND

<Height> is essential for the operation of <App>

AND

a <UserRecord> for <User>

WHEN

the <UserRecord> is retrieved

THEN

the <Height> can be determined from the <UserRecord>

Feature: User Weight

If the User's weight is essential to compute an observation the app/infra **SHALL**
be able to capture/report the user's weight as an attribute of the user .

NOTE: Information is considered to be essential to compute an observation when the value of that observation would change if the information changes. Examples for weight include calories used during an activity (e.g., steps or stairs climbed)

Scenario: Weight is Available

NOTE 1: Additional steps may be necessary to access the Weight given that the User is known. This may include retrieving the height in some way as an attribute of the user

NOTE 2: If the weight is not essential for measurement, (i.e., the precondition is not met) then this test is not applicable and not reported during the assessment.

GIVEN

a <User> with <Weight>

AND

an <App>

AND

<Height> is essential for the operation of <App>

AND

a <UserRecord> for <User>

WHEN

the <UserRecord> is retrieved

THEN

the <Weight> can be determined from the <UserRecord>

Feature: Birth Sex

If the user's birth sex is essential to compute a measurement, the App/Infrastructure
**SHALL** be able to associate/report the birth sex of the user.

Scenario: Birth Sex Exists

GIVEN

Birth Sex is essential to device configuration

AND

a <User> Record

AND

a <Birth Sex>

WHEN

<User> is retrieved

THEN

<User> contains <Sex>