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.4 Support for Communications Between Provider and Patient, and/or the Patient Representative (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.8.4"/>
      <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>Providers are able to communicate with patients and others, capturing as specified by the business rules the nature and content of electronic communication, or the time and details of other communication.</p>
    <p>Examples:</p>
    <ul>
    <li>When test results arrive, the clinician may wish to email the patient that test result was normal (details of this communication are captured).</li>
    <li>A patient may wish to request a refill of medication by emailing the physician.</li>
    <li>Patients with asthma may wish to communicate their peak flow logs/diaries to their provider.</li>
    <li>Hospital may wish to communicate with selected patients about a new smoking cessation program.</li>
    <li>Automated notification regarding annual flu shots.</li>
    </ul>
    </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.4#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 store documentation of communications between providers and patients and/ or the patient representatives.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.4#02
                </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 scanned documents.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to receive and transmit information between providers and patients or their representative using a secure internet connection.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to manage authorizations documentation for family member or patient representative to receive patient related health information.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD render an alert to providers regarding the presence of communications that originated from the patient or patient representative.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD transmit a notification regarding the provider's unavailability (e.g., vacations) when the provider receives information or requests electronically based on user-defined configuration (e.g., email out-of-office notification).</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY determine alternate routing of information or requests received when the provider is unavailable based on user-defined configuration and transmit a notification of the routing (e.g., alternate provider covering for vacation).</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to render a notification of events and new treatment options to providers.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to transmit to the patient or patient representative reminders of events related to their care (e.g., upcoming appointments) as agreed upon by the patient, and/or the patient representative.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to capture and transmit information between providers and patient groups.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to render notifications, manually, and/or automatically, to patients for conditions and results that require follow-up, according to scope of practice, organizational policy, and/or jurisdictional law, and to update the patient record with the fact that this was done.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to render information (e.g., electronic, paper, CD-ROM) to patients and to update the patient record with the fact that this was done.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to render a notification to the patient when specific medication doses are due, and/or when diagnostic/screening tests are due.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.8.4#14
                </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 for the provider to capture an authorization for the transmittal of medication renewal data to an external system and transmittal of a notice to patient via preconfigured notification channel, one of which may be a Consumer Health Solution or a Personal Health Record, 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.4"/>
      <version value="2.1.1"/>
      <name
            value="CPS_8_4_Support_for_Communications_Between_Provider_and_Patient__and_or_the_Patient_Representative"/>
      <title
             value="CPS.8.4 Support for Communications Between Provider and Patient, and/or the Patient Representative (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="Facilitate communications between providers and patients, and/or the patient representatives."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Providers are able to communicate with patients and others, capturing as specified by the business rules the nature and content of electronic communication, or the time and details of other communication.

    Examples:
    - When test results arrive, the clinician may wish to email the patient that test result was normal (details of this communication are captured).
    - A patient may wish to request a refill of medication by emailing the physician.
    - Patients with asthma may wish to communicate their peak flow logs/diaries to their provider.
    - Hospital may wish to communicate with selected patients about a new smoking cessation program.
    - Automated notification regarding annual flu shots."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-01"/>
        <label value="CPS.8.4#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and store documentation of communications between providers and patients and/ or the patient representatives."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-02"/>
        <label value="CPS.8.4#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture scanned documents."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-03"/>
        <label value="CPS.8.4#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to receive and transmit information between providers and patients or their representative using a secure internet connection."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-04"/>
        <label value="CPS.8.4#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage authorizations documentation for family member or patient representative to receive patient related health information."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-05"/>
        <label value="CPS.8.4#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD render an alert to providers regarding the presence of communications that originated from the patient or patient representative."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#6"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-06"/>
        <label value="CPS.8.4#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD transmit a notification regarding the provider's unavailability (e.g., vacations) when the provider receives information or requests electronically based on user-defined configuration (e.g., email out-of-office notification)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-07"/>
        <label value="CPS.8.4#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY determine alternate routing of information or requests received when the provider is unavailable based on user-defined configuration and transmit a notification of the routing (e.g., alternate provider covering for vacation)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-08"/>
        <label value="CPS.8.4#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render a notification of events and new treatment options to providers."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#8"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-09"/>
        <label value="CPS.8.4#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to transmit to the patient or patient representative reminders of events related to their care (e.g., upcoming appointments) as agreed upon by the patient, and/or the patient representative."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#9"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-10"/>
        <label value="CPS.8.4#10"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture and transmit information between providers and patient groups."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.3.2.3#12"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-11"/>
        <label value="CPS.8.4#11"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render notifications, manually, and/or automatically, to patients for conditions and results that require follow-up, according to scope of practice, organizational policy, and/or jurisdictional law, and to update the patient record with the fact that this was done."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-12"/>
        <label value="CPS.8.4#12"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render information (e.g., electronic, paper, CD-ROM) to patients and to update the patient record with the fact that this was done."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-13"/>
        <label value="CPS.8.4#13"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render a notification to the patient when specific medication doses are due, and/or when diagnostic/screening tests are due."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CPS.8.4-14"/>
        <label value="CPS.8.4#14"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability for the provider to capture an authorization for the transmittal of medication renewal data to an external system and transmittal of a notice to patient via preconfigured notification channel, one of which may be a Consumer Health Solution or a Personal Health Record, according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
    </Requirements>