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-APU.1"/>
<meta>
<profile
value="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/FMFunction"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <p>The functionality of an app, its sponsorship, and linkages to external data sources all affect the security, privacy and data controls which are
established to ensure safe and effective use. In this section, conformance criteria point to issues which can be addressed through a range of options, and
as such implementers should consider not only the conformance criteria but the discussion regarding applicability to the exemplary use cases.</p></div>
<div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
APU.1#01
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL authenticate the identity of a user prior to any access to PHI or PII.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#02
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL communicate the method of authentication to the user when an account is established.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#03
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL authorize the user to access a feature before that feature or any associated PHI or PII is displayed. Authorization may be internal to the system or derived from an external source.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#04
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL terminate, at the request of a user, such that subsequent access to PHI or PII requires a new, successful authentication attempt.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#05
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF another external health IT system, such as an EHR, is a system actor THEN the system SHALL verify a subject's association with their real-world identity, establishing that the subject is who they claim to be (identity proofing).</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#06
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF an EHR is a system actor THEN the system SHALL ensure that the EHR authorizes the user's access to those system features that are supported by data provided by, or written to, the EHR.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#07
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF PII or PHI are displayed THEN the system SHALL terminate, or make PHI and PII invisible, after a period of user inactivity as described in its Terms of Use. This feature is sometimes called inactivity timeout, session timeout, or automatic logoff. The decision to include this feature is made as part of the overall risk analysis regarding the sensitivity of the data provided by or through the system.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#08
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF passwords are stored on the device THEN the system SHALL encrypt those passwords and SHALL NOT display them as plaintext.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#09
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF access to an account exposes Protected Health Information (PHI) or PII THEN the system SHALL give the user the option to use strong authentication methods, such as multi-factor authentication or biometrics, in addition to passwords. Before the user selects this option, the system clearly describes or demonstrates the authentication mechanism. This capability may apply to the system itself and to the pairing of the system with a device.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#10
</td>
<td style="padding-left: 4px;">
SHALL
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF an AI component can access PHI, PII, credentials, or an external system on behalf of a user THEN the system SHALL ensure that the AI component receives only the least-privileged, time-limited access necessary for the authorized task and SHALL prevent the AI component from exposing authentication secrets, tokens, or credentials in consumer-visible output or logs.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.1#11
</td>
<td style="padding-left: 4px;">
SHOULD
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<p>IF an AI-enabled function can execute an external action or disclose new data THEN the system SHOULD require re-authentication or another strong confirmation before the action is completed when the risk assessment identifies a meaningful risk of harm, disclosure, or irreversible change.</p>
</td>
</tr>
</table>
</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-APU.1"/>
<version value="2.0.1"/>
<name value="APU_1_Authentication"/>
<title value="APU.1 Authentication (Function)"/>
<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 category is about the system protecting against unauthorized access (e.g., by persons other than the consumer)."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="The functionality of an app, its sponsorship, and linkages to external data sources all affect the security, privacy and data controls which are
established to ensure safe and effective use. In this section, conformance criteria point to issues which can be addressed through a range of options, and
as such implementers should consider not only the conformance criteria but the discussion regarding applicability to the exemplary use cases."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-01"/>
<label value="APU.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL authenticate the identity of a user prior to any access to PHI or PII."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-02"/>
<label value="APU.1#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL communicate the method of authentication to the user when an account is established."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-03"/>
<label value="APU.1#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL authorize the user to access a feature before that feature or any associated PHI or PII is displayed. Authorization may be internal to the system or derived from an external source."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-04"/>
<label value="APU.1#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL terminate, at the request of a user, such that subsequent access to PHI or PII requires a new, successful authentication attempt."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-05"/>
<label value="APU.1#05"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF another external health IT system, such as an EHR, is a system actor THEN the system SHALL verify a subject's association with their real-world identity, establishing that the subject is who they claim to be (identity proofing)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-06"/>
<label value="APU.1#06"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF an EHR is a system actor THEN the system SHALL ensure that the EHR authorizes the user's access to those system features that are supported by data provided by, or written to, the EHR."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-07"/>
<label value="APU.1#07"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF PII or PHI are displayed THEN the system SHALL terminate, or make PHI and PII invisible, after a period of user inactivity as described in its Terms of Use. This feature is sometimes called inactivity timeout, session timeout, or automatic logoff. The decision to include this feature is made as part of the overall risk analysis regarding the sensitivity of the data provided by or through the system."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-08"/>
<label value="APU.1#08"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF passwords are stored on the device THEN the system SHALL encrypt those passwords and SHALL NOT display them as plaintext."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-09"/>
<label value="APU.1#09"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF access to an account exposes Protected Health Information (PHI) or PII THEN the system SHALL give the user the option to use strong authentication methods, such as multi-factor authentication or biometrics, in addition to passwords. Before the user selects this option, the system clearly describes or demonstrates the authentication mechanism. This capability may apply to the system itself and to the pairing of the system with a device."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-10"/>
<label value="APU.1#10"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF an AI component can access PHI, PII, credentials, or an external system on behalf of a user THEN the system SHALL ensure that the AI component receives only the least-privileged, time-limited access necessary for the authorized task and SHALL prevent the AI component from exposing authentication secrets, tokens, or credentials in consumer-visible output or logs."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.1-11"/>
<label value="APU.1#11"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF an AI-enabled function can execute an external action or disclose new data THEN the system SHOULD require re-authentication or another strong confirmation before the action is completed when the risk assessment identifies a meaningful risk of harm, disclosure, or irreversible change."/>
</statement>
</Requirements>