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.9 | Version: 2.0.1 | ||||
| Standards status: Informative | Computable Name: APU_9_Audit | ||||
This category is about auditing, which is a mechanism for user and system accountability. Important events, such as logins and access to particular functions and data, are recorded and can be used to detect instances of non-compliant behavior and to facilitate detection of improper creation, access, modification, and deletion of personal health information. Any information technology including consumer health apps should follow best practices in managing an audit trail. The audit trail should maintain a record of users who have accessed what data, from where, and when. Audit logs should also record any attempts to access the system from an unauthorized terminal; expired usernames or passwords that try to access the system, unusual numbers of authentication attempts, and violations of an organizations security policy.
Related Regulations and Standards: • Integrating the Healthcare Enterprise (IHE) Audit Trail and Node Authentication (ATNA) Integration Profile. https://www.ihe.net/Technical_Frameworks/#IT This IHE profile references the Internet Engineering Task Force (IETF) RFC 3881 Audit Record standard https://datatracker.ietf.org/doc/rfc3881/ • HL7 EHR Records Management and Evidentiary Support Functional Profile, Release 1 (RMES) ( http://www.hl7.org/implement/standards/product_brief.cfm?product_id=86 ) Provides functions in an EHR system that can help an organization maintain a legal record for business and disclosure purposes. Example: Every consumer mobile health app needs an audit strategy, which includes what data will be generated for audit, who will be able to access audit records, the location where audit data is stored, the length of time audit information will be stored, and any ability to delete audit data. Audit for security events is highly dependent on the nature of the app itself; audit requirements will differ significantly based on app sponsorship (e.g., sponsor is a HIPAA entity or a commercial non-covered entity), the need for user authentication, and if data generated through an app is accessible by consumers, clinicians, or both.
| APU.9#01 | SHALL conditional |
IF user authentication is required to access the system THEN the system SHALL generate an audit record of authentication attempts, both successful and unsuccessful. |
| APU.9#02 | SHALL |
The system SHALL generate an audit record of user permissions to access, or the revocation of access to, smartphone or tablet device capabilities used by the system, such as camera or location services. |
| APU.9#03 | SHALL conditional |
IF the system uses external devices or data sources for data collection THEN the system SHALL generate an audit record of the pairing of a device or data repository external to the system that supplies data used by the system. |
| APU.9#04 | SHALL conditional |
IF the system allows the export of data to a data repository external to the system THEN the system SHALL generate an audit record of any export of data. |
| APU.9#05 | SHALL conditional |
IF the system uses AI functionality THEN the system SHALL generate an audit record for AI processing events that is sufficient to reconstruct the event without unnecessarily retaining sensitive prompt content, including the user or system actor, AI component and version, time, authorization context, input source references, output disposition, and any resulting action. |
| APU.9#06 | SHALL conditional |
IF an AI output is overridden, corrected, reported as unsafe, or leads to a safety incident THEN the system SHALL record the event, the applicable model version, the type of issue, investigation outcome, and corrective action, subject to applicable privacy and retention requirements. |
| APU.9#07 | SHOULD conditional |
IF the system uses AI functionality THEN the system SHOULD provide an authorized consumer or evaluator with a comprehensible history of the AI outputs and material actions associated with that consumer when doing so is safe and technically feasible. |
Every consumer mobile health app needs an audit strategy, which includes what data will be generated for audit, who will be able to access audit records, the location where audit data is stored, the length of time audit information will be stored, and any ability to delete audit data. Audit for security events is highly dependent on the nature of the app itself; audit requirements will differ significantly based on app sponsorship (e.g., sponsor is a HIPAA entity or a commercial non-covered entity), the need for user authentication, and if data generated through an app is accessible by consumers, clinicians, or both.