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.5"/>
<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 following are examples of standards for data provenance. Even though they are specific to the FHIR and CDA standards respectively, the principles
and data elements -- for recording entities and processes involved in producing or delivering a resource (data) – may be applicable.
• FHIR Provenance Resource http://www.hl7.org/FHIR/provenance.html
• HL7 CDA® R2 Implementation Guide: Data Provenance, Release 1 - US Realm
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=420
• ISO 21089 Health Informatics – Trusted End-to-End Information Flows. https://www.iso.org/standard/35645.html Offers a guide to trusted
end-to-end information flow for health(care) records and to the key trace points and audit events in the electronic entity/act record lifecycle
(from point of record origination to each ultimate point of record access/use).</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.5#01
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<p>The system SHALL conform to best practices for data authenticity, provenance, and associated metadata.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#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 the system creates an AI-derived output that is stored, displayed, exported, or exchanged THEN the system SHALL label the output as AI-derived and retain provenance sufficient to identify the source data references, model or service identifier and version, time of generation, and whether a human reviewed or modified the output.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#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 itself originates data, as defined in ISO 21089, THEN the system SHALL provide the customer with the option to review, irreversibly destroy, reject, or discard that data.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#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 only receives data as a pass-through and cannot store data THEN the system SHALL provide the customer with a review option that displays the data prior to executing the pass-through, including the option to irreversibly stop and block the pass-through.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#05
</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 receives data and stores it THEN the system SHOULD provide the customer with a review option that permits only appending data or free-text comments to the received data as author, while preserving the original received data intact with its original provenance. The user may comment that data are erroneous but does not have the option to delete the original data.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#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 the system displays AI output derived from consumer or device data THEN the system SHALL preserve or reference the original source data without overwriting it and SHALL distinguish AI interpretation, summarization, prediction, or generated content from the original data.</p>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
APU.5#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 the AI function produces a meaningful confidence, uncertainty, or quality signal THEN the system SHOULD preserve and present the signal in a manner appropriate to the intended user and SHALL NOT present a confidence value as a guarantee of correctness.</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.5"/>
<version value="2.0.1"/>
<name value="APU_5_Data_Authenticity__Provenance__and_Associated_Metadata"/>
<title
value="APU.5 Data Authenticity, Provenance, and Associated Metadata (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 providing assurance that consumer data is secure when it is moved between the consumer’s device(s) and other
locations. This category is about the attribution of sources of data (provenance) and assurance of data authenticity."/>
<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 following are examples of standards for data provenance. Even though they are specific to the FHIR and CDA standards respectively, the principles
and data elements -- for recording entities and processes involved in producing or delivering a resource (data) – may be applicable.
• FHIR Provenance Resource http://www.hl7.org/FHIR/provenance.html
• HL7 CDA® R2 Implementation Guide: Data Provenance, Release 1 - US Realm
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=420
• ISO 21089 Health Informatics – Trusted End-to-End Information Flows. https://www.iso.org/standard/35645.html Offers a guide to trusted
end-to-end information flow for health(care) records and to the key trace points and audit events in the electronic entity/act record lifecycle
(from point of record origination to each ultimate point of record access/use)."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-01"/>
<label value="APU.5#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to best practices for data authenticity, provenance, and associated metadata."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-02"/>
<label value="APU.5#02"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system creates an AI-derived output that is stored, displayed, exported, or exchanged THEN the system SHALL label the output as AI-derived and retain provenance sufficient to identify the source data references, model or service identifier and version, time of generation, and whether a human reviewed or modified the output."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-03"/>
<label value="APU.5#03"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system itself originates data, as defined in ISO 21089, THEN the system SHALL provide the customer with the option to review, irreversibly destroy, reject, or discard that data."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-04"/>
<label value="APU.5#04"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system only receives data as a pass-through and cannot store data THEN the system SHALL provide the customer with a review option that displays the data prior to executing the pass-through, including the option to irreversibly stop and block the pass-through."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-05"/>
<label value="APU.5#05"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF the system receives data and stores it THEN the system SHOULD provide the customer with a review option that permits only appending data or free-text comments to the received data as author, while preserving the original received data intact with its original provenance. The user may comment that data are erroneous but does not have the option to delete the original data."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-06"/>
<label value="APU.5#06"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system displays AI output derived from consumer or device data THEN the system SHALL preserve or reference the original source data without overwriting it and SHALL distinguish AI interpretation, summarization, prediction, or generated content from the original data."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="CMHAFFR2-APU.5-07"/>
<label value="APU.5#07"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the AI function produces a meaningful confidence, uncertainty, or quality signal THEN the system SHOULD preserve and present the signal in a manner appropriate to the intended user and SHALL NOT present a confidence value as a guarantee of correctness."/>
</statement>
</Requirements>