ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CPS.4.6.3"/>
<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>Enable the transmission of electronic referral orders from the EHR-S.</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>When a referral order is created in the system, the system should have the ability to compose the referral package, including any supporting clinical and administrative information, and transmit the referral order to the referred-to provider electronically.</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.4.6.3#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 export or transmit electronic referral(s) (e-referral), including all supporting clinical and administrative information to other care provider(s), whether internal or external to the organization.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#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 and maintain a minimum set of required information that must be included in an e-referral to be transmitted.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#03</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to capture a minimum set of required information that must be included in an e-referral to be transmitted, THEN the system SHALL determine if the minimum set of information is satisfied prior to transmitting an e-referral.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#04</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to capture a minimum set of required information that must be included in an e-referral to be transmitted and determines that the minimum set is not satisfied, THEN the system SHALL render prompts to capture missing information prior to transmitting an e-referral.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#05</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture administrative information (e.g., insurance information, consents and authorizations for disclosure) for inclusion in an e-referral according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#06</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 clinical information (e.g., medications, diagnostic results) for inclusion in an e-referral.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#07</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 present e-referrals, including all attached information, and capture an e-signature prior to transmission.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#08</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 capture diagnosis-based requirements for sending an e-referral based on the referred-to provider's requirements (e.g., a breast cancer specialist would not want to receive a colon cancer patient referral).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#09</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to capture diagnosis-based requirements for sending an e-referral based on the referred-to provider's requirements, THEN the system SHALL provide the ability to present those requirements at the time of referral order entry.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#10</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 capture a set of clinical requirements (e.g., history, physical examination, laboratory or Radiology results) for sending an e-referral based on the referred-to provider's requirements (e.g., a breast cancer specialist may require a positive mammogram before accepting the referral).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#11</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to capture clinical requirements for sending an e-referral based on the referred-to provider's requirements, THEN the system SHALL provide the ability to present those requirements at the time of referral order entry.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#12</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL capture and render a electronic acceptance or rejection of an e-referral request.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#13</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL capture and render the reason for an e-referral acceptance or rejection.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#14</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY capture a standards-based coded reason (e.g., SNOMED) for an e-referral acceptance or rejection.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#15</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD capture and render an electronic request for additional information from the referred-to provider.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#16</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 annotate an e-referral order with additional information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#17</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 export or transmit a copy of an e-referral, including all supporting clinical and administrative information, to another care provider (s), whether internal or external to the organization (e.g., in case the other provider failed to receive or inadvertently deleted the e-referral).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.6.3#18</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY conform to function [[AS.9.2]] (Support Financial Eligibility Verification) and display the results of e-referral eligibility and health plan/payer checking prior to approval of an referral order.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.4.6.3"/>
<version value="0.14.0"/>
<name value="CPS_4_6_3_Support_for_Electronic_Referral_Ordering"/>
<title
value="CPS.4.6.3 Support for Electronic Referral Ordering (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Enable the transmission of electronic referral orders from the EHR-S."/>
<purpose
value="When a referral order is created in the system, the system should have the ability to compose the referral package, including any supporting clinical and administrative information, and transmit the referral order to the referred-to provider electronically."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-01"/>
<label value="CPS.4.6.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to export or transmit electronic referral(s) (e-referral), including all supporting clinical and administrative information to other care provider(s), whether internal or external to the organization."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-02"/>
<label value="CPS.4.6.3#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture and maintain a minimum set of required information that must be included in an e-referral to be transmitted."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-03"/>
<label value="CPS.4.6.3#03"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to capture a minimum set of required information that must be included in an e-referral to be transmitted, THEN the system SHALL determine if the minimum set of information is satisfied prior to transmitting an e-referral."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-04"/>
<label value="CPS.4.6.3#04"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to capture a minimum set of required information that must be included in an e-referral to be transmitted and determines that the minimum set is not satisfied, THEN the system SHALL render prompts to capture missing information prior to transmitting an e-referral."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-05"/>
<label value="CPS.4.6.3#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture administrative information (e.g., insurance information, consents and authorizations for disclosure) for inclusion in an e-referral according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-06"/>
<label value="CPS.4.6.3#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture clinical information (e.g., medications, diagnostic results) for inclusion in an e-referral."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-07"/>
<label value="CPS.4.6.3#07"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to present e-referrals, including all attached information, and capture an e-signature prior to transmission."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-08"/>
<label value="CPS.4.6.3#08"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture diagnosis-based requirements for sending an e-referral based on the referred-to provider's requirements (e.g., a breast cancer specialist would not want to receive a colon cancer patient referral)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-09"/>
<label value="CPS.4.6.3#09"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to capture diagnosis-based requirements for sending an e-referral based on the referred-to provider's requirements, THEN the system SHALL provide the ability to present those requirements at the time of referral order entry."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-10"/>
<label value="CPS.4.6.3#10"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture a set of clinical requirements (e.g., history, physical examination, laboratory or Radiology results) for sending an e-referral based on the referred-to provider's requirements (e.g., a breast cancer specialist may require a positive mammogram before accepting the referral)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-11"/>
<label value="CPS.4.6.3#11"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to capture clinical requirements for sending an e-referral based on the referred-to provider's requirements, THEN the system SHALL provide the ability to present those requirements at the time of referral order entry."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-12"/>
<label value="CPS.4.6.3#12"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL capture and render a electronic acceptance or rejection of an e-referral request."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-13"/>
<label value="CPS.4.6.3#13"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL capture and render the reason for an e-referral acceptance or rejection."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-14"/>
<label value="CPS.4.6.3#14"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY capture a standards-based coded reason (e.g., SNOMED) for an e-referral acceptance or rejection."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-15"/>
<label value="CPS.4.6.3#15"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture and render an electronic request for additional information from the referred-to provider."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-16"/>
<label value="CPS.4.6.3#16"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to annotate an e-referral order with additional information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-17"/>
<label value="CPS.4.6.3#17"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to export or transmit a copy of an e-referral, including all supporting clinical and administrative information, to another care provider (s), whether internal or external to the organization (e.g., in case the other provider failed to receive or inadvertently deleted the e-referral)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.6.3-18"/>
<label value="CPS.4.6.3#18"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY conform to function [[AS.9.2]] (Support Financial Eligibility Verification) and display the results of e-referral eligibility and health plan/payer checking prior to approval of an referral order."/>
</statement>
</Requirements>