<?xml version="1.0" encoding="UTF-8"?>

<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-PDS"/>
  <meta>
    <profile value="http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMSection"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/><div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
    
    
    
    
    <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="2026-03-20T11:58:09+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.&#xA;Although cMHAFF does not have guidelines for all aspects of the software product life cycle, cMHAFF still recommends&#xA;that the product development life cycle, for new apps and for upgrades to apps, ensure that requirements for functionality,&#xA;reliability, performance, scalability, safety, compatibility, portability, and maintainability have been addressed, as well as any&#xA;requirements that relate to aspects that include these items previously described above:&#xA;* Product Information for consumers (e.g., App Store descriptions, product disclosures)&#xA;* Security&#xA;* Privacy&#xA;* Permission to use device features&#xA;* Data Access&#xA;* Data Sharing&#xA;* Terms of Use, Conditions&#xA;* Product Development, including risk management, user-centered design, compliance with applicable regulations,&#xA;functions (product description), reliability, performance, scalability, safety, compatibility, and portability.&#xA;The security and privacy of information used by the app needs to be considered throughout the development&#xA;phases of the app. Functionality must support the intended use of the app for the target users and stakeholders.&#xA;Thorough and iterative risk assessment and requirement analysis, testing, evidence collection, documentation, and&#xA;configuration management ensures quality to satisfy the needs of the application’s various stakeholders 8 .&#xA;Assessing the usability of the app helps ensure the app’s viability and adoption; testing must be population-&#xA;relevant and demonstrate reasonable product usability (accessibility) by people with visual, auditory and motor&#xA;disabilities within the intended target audience. Establishing a system of customer support enables product&#xA;defects and usability issues to be surfaced in a systematic way and helps problems related to use of the app to be&#xA;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>