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-PDS.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>Related Regulations and Standards:
The documents listed below are overviews of the regulatory landscape, rather than specific regulations governing mobile health apps. Specific
references are listed either following the conformance tables, or in the Appendix.
• USA Federal Trade Commission Mobile Health Apps Interactive Tool for guidance as to which federal laws apply. ( https://www.ftc.gov/tips-
advice/business-center/guidance/mobile-health- apps-interactive-tool ) All USA mobile app developers should consult this tool, which includes
determining if the app is a regulated “medical device” according to the U.S. Food and Drug Administration (FDA), and if so, obtaining necessary
pre-market approval.
Commission Staff Working Document on the existing EU legal framework applicable to lifestyle and wellbeing apps. ( https://ec.europa.eu/digital-single-
market/en/news/commission-staff-working-document- existing-eu-legal-framework-applicable-lifestyle-and )This broad guidance for the European Union,
analogous to the USA FTC document. It is complemented by country-specific guidelines. In the EU, some mHealth apps may fall under the definition of a
medical device and therefore may have to comply with the safety and performance requirements of Council Directive 93/42/EEC concerning medical
devices ( https://ec.europa.eu/growth/single-market/european- standards/harmonised-standards/medical-devices_en ).
Example:
Implementation
Guidance
Implementation Guidance:
• Use Case A: In the US Realm, a walking app which encourages general wellness is not considered a mobile medical app by the FDA. As such the
FDA does not intend to regulate this type of app.
• Use Case B: In the US Realm, a weight management app is not considered a mobile medical application by the FDA as long as it makes no claims
to improve/cure a disease. How the app is described is important, and FDA guidance defining wellness vs. apps which aim to improve specific
disease conditions should be referenced and reviewed before making a definitive decision as to its FDA classification.
• Use Case C: There are two distinctions regarding compliance issues for this app. For the data collection devices in this use case, a glucometer
would be FDA regulated, while a general activity monitor, would not. Apps which collect and display disease information would not typically be
regulated until the information is compiled or transformed and clinical decisions are made on the data. In this case, the app is capable of receiving
alerts, but the logic behind the alerts are based on individualized settings through a rules engine which is integrated into an EHR. In this case, the
locus of regulation is not clear, and as such counsel should be engaged in forming a definitive case as to what regulatory approvals might be
needed.
For the European Union, the figure below summarizes relevant guidance and regulations for Mobile Health. There are three principal EU
regulatory areas impacting mHealth apps:
• Medical devices, applying to higher medical risk apps only, including Regulation (EU) 2017/745 for medical devices in general and
Regulation (EU) 2017/746 for in vitro diagnostic devices.
• Information protection, applying to all apps that store or transmit personal data – currently a group of three directives, that will largely be
replaced by the General Data Protection Regulation on 25th May 2018, together with an expected mHealth-specific voluntary code.
•Consumer protection, including the right to fair treatment, products which meet acceptable standards, and right of redress if something goes
wrong.
Shades of blue indicate directives and regulations. Red indicates voluntary codes/guidelines. Yellow indicates possible other actions with uncertain timing.
Sectio Header/Function Name Reference Chg Ind Row#
n/Id#: Conformance Criteria</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;">
PDS.1#01
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL be analyzed to determine whether regulatory approval, following realm-specific regulatory rules, is required before the system is made available for general public use.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PDS.1#02
</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 realm-specific regulatory approval is determined to be required THEN the system SHALL NOT be presented for general public use until that approval is obtained.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PDS.1#03
</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 the system uses AI functionality that predicts, recommends, ranks, classifies, generates content, or initiates actions related to health or wellbeing THEN the system SHALL document the AI functionality's intended purpose, target users, context of use, level of autonomy, and whether the output can influence a health, wellbeing, financial, access, or safety decision; the system SHALL determine whether applicable realm-specific regulatory, privacy, consumer-protection, and medical-device requirements apply.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PDS.1#04
</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 the system uses AI functionality THEN the system SHALL maintain an inventory of each AI component, including the component owner, supplier, model or service name, version, intended purpose, deployment location, data categories processed, and whether the component is capable of learning or changing after deployment.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PDS.1#05
</td>
<td style="padding-left: 4px;">
SHOULD
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHOULD provide measures to safeguard minors in accordance with applicable regulations.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PDS.1#06
</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 the system uses AI functionality with a potentially high-impact health or safety use THEN the system SHOULD obtain review by appropriately qualified clinical, safety, privacy, and regulatory personnel before initial deployment and before a material change in intended use.</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-PDS.1"/>
<version value="2.0.1"/>
<name value="PDS_1_Regulatory_Considerations"/>
<title value="PDS.1 Regulatory Considerations (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 section is about the compliance of apps to applicable regulations for the domains (realms, locales, NC
environments) in which they are intended to be used. CMHAFF is designed as a framework that can be
further constrained (profiled) for these domains and does not require conformance to any specific locale’s
regulations."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="Related Regulations and Standards:
The documents listed below are overviews of the regulatory landscape, rather than specific regulations governing mobile health apps. Specific
references are listed either following the conformance tables, or in the Appendix.
• USA Federal Trade Commission Mobile Health Apps Interactive Tool for guidance as to which federal laws apply. ( https://www.ftc.gov/tips-
advice/business-center/guidance/mobile-health- apps-interactive-tool ) All USA mobile app developers should consult this tool, which includes
determining if the app is a regulated “medical device” according to the U.S. Food and Drug Administration (FDA), and if so, obtaining necessary
pre-market approval.
Commission Staff Working Document on the existing EU legal framework applicable to lifestyle and wellbeing apps. ( https://ec.europa.eu/digital-single-
market/en/news/commission-staff-working-document- existing-eu-legal-framework-applicable-lifestyle-and )This broad guidance for the European Union,
analogous to the USA FTC document. It is complemented by country-specific guidelines. In the EU, some mHealth apps may fall under the definition of a
medical device and therefore may have to comply with the safety and performance requirements of Council Directive 93/42/EEC concerning medical
devices ( https://ec.europa.eu/growth/single-market/european- standards/harmonised-standards/medical-devices_en ).
Example:
Implementation
Guidance
Implementation Guidance:
• Use Case A: In the US Realm, a walking app which encourages general wellness is not considered a mobile medical app by the FDA. As such the
FDA does not intend to regulate this type of app.
• Use Case B: In the US Realm, a weight management app is not considered a mobile medical application by the FDA as long as it makes no claims
to improve/cure a disease. How the app is described is important, and FDA guidance defining wellness vs. apps which aim to improve specific
disease conditions should be referenced and reviewed before making a definitive decision as to its FDA classification.
• Use Case C: There are two distinctions regarding compliance issues for this app. For the data collection devices in this use case, a glucometer
would be FDA regulated, while a general activity monitor, would not. Apps which collect and display disease information would not typically be
regulated until the information is compiled or transformed and clinical decisions are made on the data. In this case, the app is capable of receiving
alerts, but the logic behind the alerts are based on individualized settings through a rules engine which is integrated into an EHR. In this case, the
locus of regulation is not clear, and as such counsel should be engaged in forming a definitive case as to what regulatory approvals might be
needed.
For the European Union, the figure below summarizes relevant guidance and regulations for Mobile Health. There are three principal EU
regulatory areas impacting mHealth apps:
• Medical devices, applying to higher medical risk apps only, including Regulation (EU) 2017/745 for medical devices in general and
Regulation (EU) 2017/746 for in vitro diagnostic devices.
• Information protection, applying to all apps that store or transmit personal data – currently a group of three directives, that will largely be
replaced by the General Data Protection Regulation on 25th May 2018, together with an expected mHealth-specific voluntary code.
•Consumer protection, including the right to fair treatment, products which meet acceptable standards, and right of redress if something goes
wrong.
Shades of blue indicate directives and regulations. Red indicates voluntary codes/guidelines. Yellow indicates possible other actions with uncertain timing.
Sectio Header/Function Name Reference Chg Ind Row#
n/Id#: Conformance Criteria"/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-01"/>
<label value="PDS.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL be analyzed to determine whether regulatory approval, following realm-specific regulatory rules, is required before the system is made available for general public use."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-02"/>
<label value="PDS.1#02"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF realm-specific regulatory approval is determined to be required THEN the system SHALL NOT be presented for general public use until that approval is obtained."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-03"/>
<label value="PDS.1#03"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system uses AI functionality that predicts, recommends, ranks, classifies, generates content, or initiates actions related to health or wellbeing THEN the system SHALL document the AI functionality's intended purpose, target users, context of use, level of autonomy, and whether the output can influence a health, wellbeing, financial, access, or safety decision; the system SHALL determine whether applicable realm-specific regulatory, privacy, consumer-protection, and medical-device requirements apply."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-04"/>
<label value="PDS.1#04"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system uses AI functionality THEN the system SHALL maintain an inventory of each AI component, including the component owner, supplier, model or service name, version, intended purpose, deployment location, data categories processed, and whether the component is capable of learning or changing after deployment."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-05"/>
<label value="PDS.1#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide measures to safeguard minors in accordance with applicable regulations."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-PDS.1-06"/>
<label value="PDS.1#06"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF the system uses AI functionality with a potentially high-impact health or safety use THEN the system SHOULD obtain review by appropriately qualified clinical, safety, privacy, and regulatory personnel before initial deployment and before a material change in intended use."/>
</statement>
</Requirements>