EHRS-FM IG

ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build

Publish Box goes here

: CPS.8.6 Communication with Personal Health Record Systems (Function) - XML Representation

Active as of 2024-08-12

Raw xml | Download



<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-CPS.8.6"/>
  <meta>
    <profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
  </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>Statement: Enable and manage communication between EHR Systems and PHR Systems.</p>
</div></span>

    
    <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>With the increasing use of Personal Health Record systems, it is necessary for the EHR-S to appropriately communicate with the PHR to both capture patient information from the PHR and transmit relevant portions of the EHR patient record to the PHR to support patient self care.</p>
</div></span>
    

    

    
    <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>
    
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#01</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                
                <span>SHALL</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHALL provide the ability to capture and maintain documentation of communications between providers/providers EHR-S and the PHR-S.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#02</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability to capture communication originating from the PHR-S (e.g., date, person identification and details of communication).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#03</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                
                <span>SHALL</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHALL provide the ability to capture 3rd party (e.g., family member, authorized representative) authorization documentation for the receipt of health information from the PHR-S.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#04</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability to exchange communications between providers and PHR-S using a secure internet connection.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#05</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY provide the ability to receive clinical and administrative data (e.g., insurance information) as part of the referral process from a PHR-S.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>CPS.8.6#06</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability to transmit clinical, administrative data, test results and procedure results to a PHR-S based on authorization documentation and according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
                
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.8.6"/>
  <version value="0.16.0"/>
  <name value="CPS_8_6_Communication_with_Personal_Health_Record_Systems"/>
  <title
         value="CPS.8.6 Communication with Personal Health Record Systems (Function)"/>
  <status value="active"/>
  <date value="2024-08-12T10:56:01+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Statement: Enable and manage communication between EHR Systems and PHR Systems."/>
  <purpose
           value="With the increasing use of Personal Health Record systems, it is necessary for the EHR-S to appropriately communicate with the PHR to both capture patient information from the PHR and transmit relevant portions of the EHR patient record to the PHR to support patient self care."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-01"/>
    <label value="CPS.8.6#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to capture and maintain documentation of communications between providers/providers EHR-S and the PHR-S."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-02"/>
    <label value="CPS.8.6#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture communication originating from the PHR-S (e.g., date, person identification and details of communication)."/>
    <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#3"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-03"/>
    <label value="CPS.8.6#03"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to capture 3rd party (e.g., family member, authorized representative) authorization documentation for the receipt of health information from the PHR-S."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-04"/>
    <label value="CPS.8.6#04"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to exchange communications between providers and PHR-S using a secure internet connection."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-05"/>
    <label value="CPS.8.6#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to receive clinical and administrative data (e.g., insurance information) as part of the referral process from a PHR-S."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="EHRSFMR2.1-CPS.8.6-06"/>
    <label value="CPS.8.6#06"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to transmit clinical, administrative data, test results and procedure results to a PHR-S based on authorization documentation and according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
</Requirements>