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 (Header)

Page standards status: Informative
Statement N:

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

Criteria N:
APU.3#77 SHALL

User has authenticated identity to an app and has an active session before pairing an external device to an app account.

APU.3#78 SHALL

Before a device is paired with an app to collect information about a specific individual, the app displays a screen which asks the user to confirm that the device will collect information about a specific, named person. The person may be the account holder or a proxy subject of the account holder.

APU.3#79 SHALL

The person who pairs a device with an individual in context of use of a specific app can un-pair the device and individual through an app utility function.

APU.3#80 SHALL

Before a device is paired with an app to collect information about a specific individual, the app states what data will be collected by the device and how the device data is used. This statement may include a link to an informational page which provides details about data collection and use.

APU.3#81 SHALL

[Data for more than one person can be collected by the app/device pair] The app asks the account holder to confirm the person for whom data will be collected by the device before data is collected and transmitted.

APU.3#82 SHALL

[Developer includes a syncing option within APP (e.g., same app data synchronized across smartphone and tablet devices)] User is provided with option to consent with syncing process.[1]