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

<Requirements xmlns="http://hl7.org/fhir">
  <id value="CMHAFFR2-APU.6"/>
  <meta>
    <profile value="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/FMFunction"/>
  </meta>
  <language value="en"/>
  <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:
• Direct Project Applicability Statement for Secure Health Transport
 https://www.healthit.gov/policy-researchers-implementers/direct-project
 • HL7 Consolidated CDA
 • HL7 FHIR STU. http://www.hl7.org/FHIR/index.html
 • SMART ON FHIR. https://smarthealthit.org/
 • http://www.hl7.org/implement/standards/product_brief.cfm?product_id=379
 • IEEE 10073 Personal Health Data Standards https://standards.ieee.org/develop/wg/PHD.html
 • “MedMij” information Exchange standards for Personal Health Environment https://www.medmij.nl (Netherlands) Includes HL7 Health
 Clinical Information models (HCIM), which provide context for discrete clinical data (e.g., systolic blood pressure); the standard is being used
 in the Netherlands.</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.6#01
            </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 exchanges discrete clinical data THEN the system SHALL use standard terminologies, such as SNOMED CT or LOINC.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 exchanges discrete clinical data THEN the system SHALL use standard format and content, such as HL7 FHIR, SMART on FHIR, HL7 Consolidated CDA, or Detailed Clinical Models (HL7 CIMI).</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 exchanges AI-derived data with another device, app, repository, or HIT system THEN the system SHALL identify AI-derived information as such in the exchanged content and SHALL include available provenance, source-data, model-version, and human-review metadata so recipients can distinguish it from verified clinical observations.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#04
            </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 exchanges discrete clinical data with devices THEN the system SHOULD use standard format and content, such as IEEE 11073.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 exchanges unstructured data THEN the system SHOULD use standard or commonly accepted formats, such as HL7 CDA or PDF.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 exchanges AI-generated narrative or summary content THEN the system SHALL distinguish AI-generated narrative from source records and SHALL avoid transmitting the narrative as a verified clinical fact unless it has been reviewed and authenticated according to the receiving system's policy.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 collects personal health information THEN the system SHOULD allow that data to be imported into or exported from the system.</p>

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            APU.6#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 exchanges AI-derived data THEN the system SHOULD use applicable interoperable provenance and annotation mechanisms, such as HL7 FHIR Provenance or a realm-appropriate equivalent, when those mechanisms are available to the receiving system.</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.6"/>
  <version value="2.0.1"/>
  <name value="APU_6_Data_Exchange_and_Interoperability"/>
  <title value="APU.6 Data Exchange and Interoperability (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 applies only if an app exchanges data with other devices, health apps, and/or HIT systems. If so, there are applicable&#xA; standards for data format, vocabulary, and transport, to increase interoperability and ease of connection."/>
  <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:&#xA;• Direct Project Applicability Statement for Secure Health Transport&#xA; https://www.healthit.gov/policy-researchers-implementers/direct-project&#xA; • HL7 Consolidated CDA&#xA; • HL7 FHIR STU. http://www.hl7.org/FHIR/index.html&#xA; • SMART ON FHIR. https://smarthealthit.org/&#xA; • http://www.hl7.org/implement/standards/product_brief.cfm?product_id=379&#xA; • IEEE 10073 Personal Health Data Standards https://standards.ieee.org/develop/wg/PHD.html&#xA; • “MedMij” information Exchange standards for Personal Health Environment https://www.medmij.nl (Netherlands) Includes HL7 Health&#xA; Clinical Information models (HCIM), which provide context for discrete clinical data (e.g., systolic blood pressure); the standard is being used&#xA; in the Netherlands."/>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-01"/>
    <label value="APU.6#01"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges discrete clinical data THEN the system SHALL use standard terminologies, such as SNOMED CT or LOINC."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-02"/>
    <label value="APU.6#02"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges discrete clinical data THEN the system SHALL use standard format and content, such as HL7 FHIR, SMART on FHIR, HL7 Consolidated CDA, or Detailed Clinical Models (HL7 CIMI)."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-03"/>
    <label value="APU.6#03"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges AI-derived data with another device, app, repository, or HIT system THEN the system SHALL identify AI-derived information as such in the exchanged content and SHALL include available provenance, source-data, model-version, and human-review metadata so recipients can distinguish it from verified clinical observations."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-04"/>
    <label value="APU.6#04"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges discrete clinical data with devices THEN the system SHOULD use standard format and content, such as IEEE 11073."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-05"/>
    <label value="APU.6#05"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges unstructured data THEN the system SHOULD use standard or commonly accepted formats, such as HL7 CDA or PDF."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-06"/>
    <label value="APU.6#06"/>
    <conformance value="SHALL"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges AI-generated narrative or summary content THEN the system SHALL distinguish AI-generated narrative from source records and SHALL avoid transmitting the narrative as a verified clinical fact unless it has been reviewed and authenticated according to the receiving system's policy."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-07"/>
    <label value="APU.6#07"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement value="IF the system collects personal health information THEN the system SHOULD allow that data to be imported into or exported from the system."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/cmhaffr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="CMHAFFR2-APU.6-08"/>
    <label value="APU.6#08"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement value="IF the system exchanges AI-derived data THEN the system SHOULD use applicable interoperable provenance and annotation mechanisms, such as HL7 FHIR Provenance or a realm-appropriate equivalent, when those mechanisms are available to the receiving system."/>
  </statement>
</Requirements>