Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build
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
| Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-APU.4 | Version: 2.0.1 | ||||
| Standards status: Informative | Computable Name: APU_4_Security_for_Data_at_Rest_and_in_Transport | ||||
This category is about providing assurance that the consumer’s stored data is secure, regardless of whether it is stored on the consumer’s devices or elsewhere (e.g., in cloud-based servers for an app). It also provides assurance that consumer data is secure when it is moved between the consumer’s device(s) and other locations.
| APU.4#01 | SHALL |
The system SHALL store PHI and PII held on a smartphone as encrypted values. |
| APU.4#02 | SHALL |
The system SHALL store PHI and PII held on any external server as encrypted values. |
| APU.4#03 | SHALL |
The system SHALL permit the account holder to delete information collected through the system, including data generated by an associated device, unless that PHI or PII has been transmitted to a data set maintained by a health plan or health provider. |
| APU.4#04 | SHALL |
The system SHALL improve or upgrade its encryption ciphers and suites to match evolving best practices while it is actively being developed and maintained, that is, while it is not being sunset. |
| APU.4#05 | SHALL conditional |
IF the system contains PHI or PII THEN the system SHALL transmit PHI and PII between itself and an external data source, including data generated through an associated device, as encrypted values. |
| APU.4#06 | SHALL conditional |
IF the system uses an AI component THEN the system SHALL protect consumer data, prompts, retrieved content, model inputs, model outputs, API keys, and access tokens used by the AI component using security controls proportionate to the data sensitivity and deployment architecture. |
| APU.4#07 | SHALL conditional |
IF the system uses a third-party AI service THEN the system SHALL assess and document the security and privacy controls of the third-party AI service, including data isolation, retention, access controls, incident notification, and the provider's use of consumer data. |
| APU.4#08 | SHOULD conditional |
IF the system includes generative AI or retrieval-augmented generation THEN the system SHOULD implement technical controls to reduce prompt injection, unauthorized retrieval, data exfiltration, and cross-user data exposure. |