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.8 Notifications and Alerts (Header)

Page standards status: Informative
Statement N:

This category applies only if an app exchanges data with other devices, health apps, and/or HIT systems. If so, there are applicable standards for data format, vocabulary, and transport, to increase interoperability and ease of connection.

 Criteria N:
APU.8#98 SHALL

Opt-in consent is required by the account holder before receiving notifications and alerts from an app.
APU.8#99 SHALL

To consent to receiving a notification or alert from an app, the account holder is informed of both the content and channel (SMS, push notification, email, etc.) of the notification or alert.
APU.8#100 SHALL

An account holder can change consent decisions about notifications and alerts through settings available on the device on which the app was downloaded.
APU.8#101 SHALL

Notifications and alerts contain the least amount of information necessary for the recipient of the alert to take a focused action.
APU.8#102 SHALL

[App alerts notify user of conditions such as “abnormal” or “exceptional” or “out of range”] Document or reference the sources (evidence base) of the formulas/algorithms upon which such alerts and notifications are based.
APU.8#103 SHOULD

[Permitted by the account holder and agreed to by recipients] notifications and alerts may be sent to the account holder and/or to another person or entity.
APU.8#104 SHOULD

Provide alerts to notify the user of potential faults that could cause inconvenience or harm to the user, e.g., low battery alerts.
APU.8#105 SHOULD

Notify the user in case of external interruptions or delays (e.g., loss of network connection, database problem, lengthy operation).
APU.8#135 SHALL

Notifications and alerts contain the least amount of information necessary for the recipient of the alert to take a focused action.