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

: AI Functionality and Governance

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-AIG"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/FMSection"/>
  </meta>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
    
    
    
    
    <i>Sections and Headers have no criteria.</i>
    
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="mobile"/>
  </extension>
  <url value="http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-AIG"/>
  <version value="2.0.1"/>
  <name value="AI_Functionality_and_Governance"/>
  <title value="AI Functionality and Governance"/>
  <status value="active"/>
  <date value="2026-11-18T11:24:54+00:00"/>
  <publisher value="HL7 International / Mobile Health"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/mobile"/>
    </telecom>
  </contact>
  <description
               value="This section addresses artificial intelligence functionality in consumer mobile health applications: governance, transparency, privacy, security, data provenance, user control, safety, monitoring, and accountability.

Consistent with cMHAFF's design as a horizontal, realm-agnostic framework, this section specifies cross-cutting consumer safeguards that apply wherever AI functionality is present. Disease-specific clinical validity, diagnosis and treatment claims, performance targets, threshold logic, and realm-specific regulatory obligations remain the province of implementation guides and realm or domain profiles.

Every criterion in this section is conditional on the presence of AI functionality. An application that uses no AI functionality has no obligations under this section. AIG.1 establishes that applicability determination and is the entry point for the rest.Applicability is determined by the AI questions proposed for the cMHAFF decision table: whether the app uses AI to predict, classify, recommend, rank, summarize, generate content, or act on a consumer's behalf; whether AI output can influence a health, safety, access, or financial decision; whether generative AI, retrieval-augmented generation, or an AI agent is used; whether PII, PHI, device data, or user content is sent to a third-party AI service; whether the AI function can change after deployment; and whether AI-derived data is exchanged with an EHR, PHR, device, payer, or other system.

Design inputs: NIST AI Risk Management Framework (AI RMF 1.0); NIST AI 600-1 Generative AI Profile; FDA Good Machine Learning Practice Guiding Principles; FDA Transparency for Machine Learning-Enabled Medical Devices; FDA AI-Enabled Device Software Functions lifecycle guidance; FDA Predetermined Change Control Plan guidance; FDA Digital Health and AI Glossary. These are design inputs, not asserted legal requirements; realm-specific law and regulation take precedence."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
</Requirements>