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: AIG.7 Monitoring, Change Control, and Incident Management (Function)

Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-AIG.7 Version: 2.0.1
Standards status: Informative Computable Name: AIG_7_Monitoring__Change_Control__and_Incident_Management

This category is about what happens after deployment: monitoring for performance degradation, drift and misuse; pre-defined thresholds and decision authorities for responding; and handling incidents that affect consumer safety, privacy, or performance. AI behavior can change without a conventional application release.

Criteria N:
AIG.7#01 SHALL conditional

IF the system uses AI functionality THEN the system SHALL monitor the AI function after deployment for material performance degradation, data drift, misuse, unexpected outputs, safety events, privacy events, and differences from the validated intended use.

AIG.7#02 SHALL conditional

IF the system uses AI functionality THEN the system SHALL define and document thresholds and decision authorities for investigation, consumer communication, limitation, suspension, rollback, corrective action, and retirement of an AI function.

AIG.7#03 SHALL conditional

IF a material AI incident affects consumer safety, privacy, or performance THEN the system SHALL investigate the incident, preserve evidence, assess affected consumers and data, implement corrective action, and make notifications required by applicable laws, contracts, or safety protocols.

AIG.7#04 SHOULD conditional

IF the system uses AI functionality THEN the system SHOULD periodically review real-world performance across relevant populations and use cases to identify emerging performance or equity concerns.

AIG.7#05 MAY conditional

IF the system uses AI functionality THEN the system MAY publish de-identified, aggregate post-deployment monitoring summaries when doing so does not create security, privacy, or proprietary risk.