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

: PIM.2 Launch App and Establish User Account (Function)

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-PIM.2"/>
  <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>
Example:
• Use Case A: Knowing who the user is, in an absolute sense, is not needed as data is not being sent to any external data set. Primarily, account
 controls are in place to ensure the same person is using the app each time. For this walking app, possession of a smartphone may be sufficient to
 allow someone to use it without any additional need for authentication or need to set up a unique user ID and password to access the app.
 • Use Case B: Knowing the user’s absolute identity is not needed but minimal account controls (e.g., user ID and password) should be established
 as the app will allow information to be sent to an existing data set, and these data sets will need some ability to be linked, in part showing evidence
 an individual has control over both the app data and a right to access the existing data set.
 • Use Case C: requires more rigorous identity proofing as data will be both sent to an EHR and interactions initiated by a physician result in information
 being pushed to the app. Identity proofing can occur within the app itself, or in the use of pre-existing identity credentials (e.g., patient portal
 credentials for the entity controlling the EHR) to establish identity.

 3. App Use
 Statement Overview: This section addresses functionalities and considerations to be addressed while the user is operating
 the app.</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;">
            PIM.2#01
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHALL permit a user to review its Terms of Use before personal data about the user is collected and used.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#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 account data, content, or device data will be transmitted to an AI component THEN the system SHALL inform the user, before the first such transmission, what categories of data will be processed by the AI component, whether a third party receives the data, and the purposes, retention, and applicable data-use choices.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#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 creates user accounts THEN the system SHALL log the user's acceptance of its Terms of Use before a user account is authorized. See APU.9 for audit log record creation.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#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 user is allowed to use pre-existing account credentials from an Identity Provider (IdP) to access the system THEN the system SHALL inform the user, before the user chooses to use those credentials, (a) what attribute information associated with the pre-existing credentials will be used by the system, and (b) what data is communicated back to the IdP at the time of account creation and at each subsequent user authentication.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#05
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <p>The system SHOULD collect no more than the minimum necessary amount of a user's personally identifiable information (PII) for the purpose of establishing an account, that is, information necessary to authenticate the user, provide customer support, or affect the system's logic.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#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 user data will be used to train, fine-tune, evaluate, or otherwise improve an AI model THEN the system SHALL obtain the user's permission before the first transmission of account data, user content, or device data to an AI component, and SHALL identify the recipient, the purpose, and whether the data may be retained.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            PIM.2#07
            </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 offers optional AI features THEN the system SHOULD allow a user to enable or disable optional AI features separately from unrelated App functions when technically feasible and consistent with the 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-PIM.2"/>
  <version value="2.0.1"/>
  <name value="PIM_2_Launch_App_and_Establish_User_Account"/>
  <title value="PIM.2 Launch App and Establish User Account (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="1. A user SHALL be able to review the app's Terms of Use before personal data about the user PIM.2 NC
 is collected and used."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <purpose
           value="
Example:
• Use Case A: Knowing who the user is, in an absolute sense, is not needed as data is not being sent to any external data set. Primarily, account
 controls are in place to ensure the same person is using the app each time. For this walking app, possession of a smartphone may be sufficient to
 allow someone to use it without any additional need for authentication or need to set up a unique user ID and password to access the app.
 • Use Case B: Knowing the user’s absolute identity is not needed but minimal account controls (e.g., user ID and password) should be established
 as the app will allow information to be sent to an existing data set, and these data sets will need some ability to be linked, in part showing evidence
 an individual has control over both the app data and a right to access the existing data set.
 • Use Case C: requires more rigorous identity proofing as data will be both sent to an EHR and interactions initiated by a physician result in information
 being pushed to the app. Identity proofing can occur within the app itself, or in the use of pre-existing identity credentials (e.g., patient portal
 credentials for the entity controlling the EHR) to establish identity.

 3. App Use
 Statement Overview: This section addresses functionalities and considerations to be addressed while the user is operating
 the app."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-01"/>
    <label value="PIM.2#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL permit a user to review its Terms of Use before personal data about the user is collected and used."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-02"/>
    <label value="PIM.2#02"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF account data, content, or device data will be transmitted to an AI component THEN the system SHALL inform the user, before the first such transmission, what categories of data will be processed by the AI component, whether a third party receives the data, and the purposes, retention, and applicable data-use choices."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-03"/>
    <label value="PIM.2#03"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the system creates user accounts THEN the system SHALL log the user's acceptance of its Terms of Use before a user account is authorized. See APU.9 for audit log record creation."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-04"/>
    <label value="PIM.2#04"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the user is allowed to use pre-existing account credentials from an Identity Provider (IdP) to access the system THEN the system SHALL inform the user, before the user chooses to use those credentials, (a) what attribute information associated with the pre-existing credentials will be used by the system, and (b) what data is communicated back to the IdP at the time of account creation and at each subsequent user authentication."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-05"/>
    <label value="PIM.2#05"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD collect no more than the minimum necessary amount of a user's personally identifiable information (PII) for the purpose of establishing an account, that is, information necessary to authenticate the user, provide customer support, or affect the system's logic."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-06"/>
    <label value="PIM.2#06"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement
                 value="IF user data will be used to train, fine-tune, evaluate, or otherwise improve an AI model THEN the system SHALL obtain the user's permission before the first transmission of account data, user content, or device data to an AI component, and SHALL identify the recipient, the purpose, and whether the data may be retained."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-PIM.2-07"/>
    <label value="PIM.2#07"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="IF the system offers optional AI features THEN the system SHOULD allow a user to enable or disable optional AI features separately from unrelated App functions when technically feasible and consistent with the intended use."/>
  </statement>
</Requirements>