HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

## : CPS.8.6 Communication with Personal Health Record Systems (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.8.6"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <language value="en"/>
      <text>
        <status value="extensions"/>
        <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">

        <div id="description"><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></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;">
                CPS.8.6#01
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <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>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.6#02
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <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>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.6#03
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <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>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.6#04
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to exchange communications between providers and PHR-S using a secure internet connection.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.6#05
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <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>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.6#06
                </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: #e5f5e5;color: #388e3c;border: 1px solid #a2d1a2;">dependent</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <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>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
        <valueCode value="normative"/>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CPS.8.6"/>
      <version value="2.1.1"/>
      <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="2025-12-13T09:06:06+00:00"/>
      <publisher value="HL7 International / Electronic Health Records"/>
      <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."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-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/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-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>