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
| Page standards status: Informative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="CMHAFFR2-CNA"/>
<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-CNA"/>
<version value="2.0.1"/>
<name value="Conditions_and_Agreements"/>
<title value="Conditions and Agreements"/>
<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 of cMHAFF deals with nonfunctional, and usually nontechnical, aspects of mobile health apps. While not traditionally in scope for
HIT standards oriented at large or small enterprise organizations, it is a very important and distinctive characteristic of apps targeted at consumers.Since one goal of cMHAFF is consumer protection, including their privacy and security, guidance in the area of “Conditions and Agreements”
(CnA) is offered. CnA is not a formal or legal term, but an umbrella under which can be grouped various expressions of conditions that consumers to which
are asked to agree
before they start using a mobile health app. These may be called “Terms and Conditions,” “Terms of
Use,” “Terms of Service,” “End User License Agreement (EULA),” and similar concepts. Typically, CnA are displayed and consumers are asked to click
buttons to agree to terms, when they interact with “App Stores” (a generic term including wherever a consumer downloads a mobile health app). In addition
to what the consumer agrees to, CnA may also commit the app supplier to certain behaviors or restrictions. While cMHAFF does not prescribe what these
CnA must include, it provides guidance as to items that are important to disclose. In that respect, there is some precedent in the ONC 2015 Edition
Certification, which contains disclosure and transparency requirements for EHR developers, e.g., about pricing and services that are not included in the
base software."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
</Requirements>