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 Demographics

User demographics identifies the user of a device. It includes critical information that can be used for matching a device user to patient records in an EHR, such as name, address, birthdate, user identifiers, and user contact information (which can also be used to improve user matching to patient records. This is generally considered to be static data associated with user identity, rather than other clinical or administrative information associated with the user. That information would appear in User Attributes.

Feature: User Unique Identity

An app/infrastructure **SHALL** be able to generate/report the unique identifer for a given user association with a measurement.

This scenario demonstrates the ability of an App to associate a user with an identifier, and in the process of storing the measurement has associated the measurement with the user’s identity.

NOTE: Different kinds of Unique identifiers may be used

Scenario: Identifier Exists

GIVEN

a <User> Record

AND

an <Identifier>

WHEN

<User> is retrieved

THEN

<User> contains <Identifier>

AND

<Identifier> is one of the following:

• <Identifier> is the user’s e-mail address or

• <Identifier> is the user’s login identifier for another system (e.g., Google, Facebook, Twitter, et cetera) or

• <Identifier> is the user’s selected login name for <App> or

• <Identifier> is a unique string (e.g., UUID or string) assigned by <App>

BUT

<Identifier> is not something else

Feature: User Name

The App or Infrastructure **SHALL** be able to associate the user's name with the user.

Scenario: Name Exists

GIVEN

a <User> Record

AND

a user <Name>

WHEN

<User> is retrieved

THEN

<User> contains <Name>

Feature: User Contact Information

The App or Infrastructure **SHALL** be able to associate the user's contact information (e.g., e-mail address, phone number) with the user.

Scenario: Contact Information Exists

GIVEN

a <User>Record

AND

a <Contact> information item

WHEN

<User> is retrieved

THEN

<User> contains <Contact>

AND

<Contact> is one of the following:

• <Contact> is the user’s postal address, or

• <Contact> is the user’s e-mail address, or

• <Contact> is the user’s telephone number, or

BUT

<Contact> is not something else

Feature: Date of Birth

The App and Infrastructure **SHALL** be able to associate a birth date with the patient.

Scenario: Birth Date Exists

GIVEN

a <User> Record

AND

a <Birthdate>

WHEN

<User> is retrieved

THEN

<User> contains <Birthdate>

Feature: Gender Identity

The App and Infrastructure **SHOULD** be able to associate a gender identity with the patient.

Scenario: Gender Identity Exists

GIVEN

a <User> Record

AND

a <Gender Identity>

WHEN

<User> is retrieved

THEN

<User> contains <Gender Identity>