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

• Narrative Content
• XML
• JSON
• TTL

: Product Development & Support - XML Representation

Page standards status: Informative

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-PDS"/>
  <meta>
    <profile
             value="http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMSection"/>
  </meta>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
    <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Prior to marketing a mobile app, the developer has a responsibility to ensure it meets Realm-specific rules and regulations.
Although cMHAFF does not have guidelines for all aspects of the software product life cycle, cMHAFF still recommends
that the product development life cycle, for new apps and for upgrades to apps, ensure that requirements for functionality,
reliability, performance, scalability, safety, compatibility, portability, and maintainability have been addressed, as well as any
requirements that relate to aspects that include these items previously described above:</p>
<ul>
<li>Product Information for consumers (e.g., App Store descriptions, product disclosures)</li>
<li>Security</li>
<li>Privacy</li>
<li>Permission to use device features</li>
<li>Data Access</li>
<li>Data Sharing</li>
<li>Terms of Use, Conditions</li>
<li>Product Development, including risk management, user-centered design, compliance with applicable regulations,
functions (product description), reliability, performance, scalability, safety, compatibility, and portability.
The security and privacy of information used by the app needs to be considered throughout the development
phases of the app. Functionality must support the intended use of the app for the target users and stakeholders.
Thorough and iterative risk assessment and requirement analysis, testing, evidence collection, documentation, and
configuration management ensures quality to satisfy the needs of the application’s various stakeholders 8 .
Assessing the usability of the app helps ensure the app’s viability and adoption; testing must be population-
relevant and demonstrate reasonable product usability (accessibility) by people with visual, auditory and motor
disabilities within the intended target audience. Establishing a system of customer support enables product
defects and usability issues to be surfaced in a systematic way and helps problems related to use of the app to be
effectively resolved and the developer to continually deliver the intended use of the app.</li>
</ul>
</div></span>

    

    
    
    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="mobile"/>
  </extension>
  <url value="http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-PDS"/>
  <version value="2.0.1"/>
  <name value="Product_Development___Support"/>
  <title value="Product Development &amp; Support"/>
  <status value="active"/>
  <date value="2025-05-28T08:01:49+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="Prior to marketing a mobile app, the developer has a responsibility to ensure it meets Realm-specific rules and regulations.
Although cMHAFF does not have guidelines for all aspects of the software product life cycle, cMHAFF still recommends
that the product development life cycle, for new apps and for upgrades to apps, ensure that requirements for functionality,
reliability, performance, scalability, safety, compatibility, portability, and maintainability have been addressed, as well as any
requirements that relate to aspects that include these items previously described above:
* Product Information for consumers (e.g., App Store descriptions, product disclosures)
* Security
* Privacy
* Permission to use device features
* Data Access
* Data Sharing
* Terms of Use, Conditions
* Product Development, including risk management, user-centered design, compliance with applicable regulations,
functions (product description), reliability, performance, scalability, safety, compatibility, and portability.
The security and privacy of information used by the app needs to be considered throughout the development
phases of the app. Functionality must support the intended use of the app for the target users and stakeholders.
Thorough and iterative risk assessment and requirement analysis, testing, evidence collection, documentation, and
configuration management ensures quality to satisfy the needs of the application’s various stakeholders 8 .
Assessing the usability of the app helps ensure the app’s viability and adoption; testing must be population-
relevant and demonstrate reasonable product usability (accessibility) by people with visual, auditory and motor
disabilities within the intended target audience. Establishing a system of customer support enables product
defects and usability issues to be surfaced in a systematic way and helps problems related to use of the app to be
effectively resolved and the developer to continually deliver the intended use of the app."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
</Requirements>