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

: AST.1 App and Data Removal (Function)

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-AST.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:
• European Union Privacy Code of Conduct on Mobile Health apps
https://ec.europa.eu/digital-single-market/en/privacy-code-conduct-mobile-health-apps
Example:
Data download should be in a standard or at least nonproprietary format (e.g., CSV, XML, JSON) that
can be manipulated by off-the-shelf tooling. The format should be selected appropriate to the data being
downloaded.</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;">
            AST.1#01
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL provide the account holder with the ability to remove the system from a mobile device at any time.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#02
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL inform the account holder of the consequences of removing it from a smartphone, such as loss of locally stored data, and SHALL give the account holder an opportunity to confirm the removal before it occurs.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#03
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL provide the account holder with the ability to close an associated account or data store.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#04
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL inform the account holder of the consequences of deleting the account and SHALL give an opportunity to confirm closing the account before it is closed.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#05
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL inform the account holder that data that was part of the account may have been transmitted to other systems outside the account itself and may persist. For example, where the user collects device data in the system and transmits that data to an EHR which stores it as patient-generated health data, the user is informed that deleting the account may not delete the data now held in the EHR.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.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 the system uses consumer data in AI processing THEN the system SHALL stop future AI processing and future model-improvement use of that account's data when the account is closed, unless another documented legal basis applies, and SHALL describe any retained data required for legal, safety, or security reasons.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#07
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHOULD provide the account holder with the ability to download data generated by the account holder, or by a proxy subject of the account holder, to a data set under the full control of the account holder (data portability), before an account is closed.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#08
            </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 provides consumer data portability THEN the system SHOULD include AI-generated or AI-derived data in the export and preserve available provenance, source-data references, model version, and human-review status.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.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 the device on which the system is installed permits remote or external access to device data THEN the system SHALL provide the ability for any PHI or PII stored on the device to be wiped remotely by the account holder, without deleting the account related to the wiped data.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#10
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHOULD set and communicate to the user clear criteria regarding the deletion of data, including automatic deletion if the user has not used the system for a specified period.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AST.1#11
            </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 stores prompts, retrieval caches, embeddings, AI outputs, or AI audit data linked to an account THEN the system SHALL delete, de-identify, or otherwise render unusable the prompts, retrieval caches, embeddings, AI outputs, and AI audit data linked to the account, or SHALL state which categories are retained, for what purpose, and for how long, when an account is closed.</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-AST.1"/>
  <version value="2.0.1"/>
  <name value="AST_1_App_and_Data_Removal"/>
  <title value="AST.1 App and Data Removal (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>
  <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:
• European Union Privacy Code of Conduct on Mobile Health apps
https://ec.europa.eu/digital-single-market/en/privacy-code-conduct-mobile-health-apps
Example:
Data download should be in a standard or at least nonproprietary format (e.g., CSV, XML, JSON) that
can be manipulated by off-the-shelf tooling. The format should be selected appropriate to the data being
downloaded."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-01"/>
    <label value="AST.1#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the account holder with the ability to remove the system from a mobile device at any time."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-02"/>
    <label value="AST.1#02"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL inform the account holder of the consequences of removing it from a smartphone, such as loss of locally stored data, and SHALL give the account holder an opportunity to confirm the removal before it occurs."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-03"/>
    <label value="AST.1#03"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the account holder with the ability to close an associated account or data store."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-04"/>
    <label value="AST.1#04"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL inform the account holder of the consequences of deleting the account and SHALL give an opportunity to confirm closing the account before it is closed."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-05"/>
    <label value="AST.1#05"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL inform the account holder that data that was part of the account may have been transmitted to other systems outside the account itself and may persist. For example, where the user collects device data in the system and transmits that data to an EHR which stores it as patient-generated health data, the user is informed that deleting the account may not delete the data now held in the EHR."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-06"/>
    <label value="AST.1#06"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the system uses consumer data in AI processing THEN the system SHALL stop future AI processing and future model-improvement use of that account's data when the account is closed, unless another documented legal basis applies, and SHALL describe any retained data required for legal, safety, or security reasons."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-07"/>
    <label value="AST.1#07"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the account holder with the ability to download data generated by the account holder, or by a proxy subject of the account holder, to a data set under the full control of the account holder (data portability), before an account is closed."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-08"/>
    <label value="AST.1#08"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the system provides consumer data portability THEN the system SHOULD include AI-generated or AI-derived data in the export and preserve available provenance, source-data references, model version, and human-review status."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-09"/>
    <label value="AST.1#09"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the device on which the system is installed permits remote or external access to device data THEN the system SHALL provide the ability for any PHI or PII stored on the device to be wiped remotely by the account holder, without deleting the account related to the wiped data."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-10"/>
    <label value="AST.1#10"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD set and communicate to the user clear criteria regarding the deletion of data, including automatic deletion if the user has not used the system for a specified period."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-AST.1-11"/>
    <label value="AST.1#11"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the system stores prompts, retrieval caches, embeddings, AI outputs, or AI audit data linked to an account THEN the system SHALL delete, de-identify, or otherwise render unusable the prompts, retrieval caches, embeddings, AI outputs, and AI audit data linked to the account, or SHALL state which categories are retained, for what purpose, and for how long, when an account is closed."/>
  </statement>
</Requirements>