Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build International flag

Consumer Mobile Health Application Functional Framework, Release 2, published by HL7 International / Mobile Health. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cmhaff-ig/ and changes regularly. See the Directory of published versions

Requirements: APU.3 Pairing or Syncing User Accounts with Devices and Data Repositories (Function)

Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-APU.3 Version: 2.0.1
Standards status: Informative Computable Name: APU_3_Pairing_or_Syncing_User_Accounts_with_Devices_and_Data_Repositories

This category is about consumer verification of all devices to which they wish to pair or sync data.

Criteria N:
APU.3#01 SHALL

The system SHALL ensure that the user has successfully authenticated and has an active session before an external device is paired to an account.

APU.3#02 SHALL

The system SHALL display a screen that asks the user to confirm that the device will collect information about a specific, named person, before a device is paired with the system to collect information about that individual. The person may be the account holder or a proxy subject of the account holder.

APU.3#03 SHALL

The system SHALL provide a utility function that permits the person who paired a device with an individual to un-pair the device and the individual.

APU.3#04 SHALL

The system SHALL state what data will be collected by the device and how that data is used, before a device is paired with the system to collect information about a specific individual. This statement may include a link to an informational page giving details about data collection and use.

APU.3#05 SHALL conditional

IF the system uses device or repository data as input to AI functionality THEN the system SHALL state, before a device or repository is paired or synced, whether data from that device or repository will be used as input to AI functionality and for what purpose.

APU.3#06 SHALL conditional

IF data for more than one person can be collected by the system and device pair THEN the system SHALL ask the account holder to confirm the person for whom the device will collect data, before data is collected and transmitted.

APU.3#07 SHALL conditional

IF the system includes a syncing option, such as the same data synchronized across smartphone and tablet devices, THEN the system SHALL provide the user with the option to consent to the syncing process.

APU.3#08 SHOULD conditional

IF AI output depends on data from a paired device or repository THEN the system SHOULD detect or flag material missing, stale, implausible, or mis-associated inputs before presenting an AI output that relies on those inputs.