ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
Publish Box goes here
| Active as of 2024-08-12 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CPS.9.2.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>Provide features to enable secure bi-directional communication of information electronically between practitioners and pharmacies or between practitioner and intended recipient of pharmacy orders.</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 medication is prescribed, the order is routed to the pharmacy or other intended recipient of pharmacy orders. This information is used to avoid transcription errors and facilitate detection of potential adverse reactions. If there is a question from the pharmacy, that communication can be presented to the provider with their other tasks. In certain environments, medication order creation is a collaborative process involving the prescriber and facility staff. Accordingly, this function applies to communication process between the prescriber, facility and the pharmacy or other intended recipient of pharmacy orders. The transmission of prescription data between systems should conform to realm acceptable messaging standards. Informative examples:</p>
<ul>
<li>HL7 Clinical Document Architecture Release 2</li>
<li>ISO/EN 13606 Electronic Health Record Communication</li>
<li>CEN ENV 13607:2000. Health informatics. Messages for the exchange of information on medicine prescriptions</li>
<li>X12N healthcare transactions</li>
<li>US realm: National Council for Prescription Drug Programs (NCPDP)</li>
<li>Canadian realm: National Electronic Claims Standard (NeCST)
Example:</li>
<li>HL7 Clinical Document Architecture Release 2</li>
<li>ISO/EN 13606 Electronic Health Record Communication</li>
<li>CEN ENV 13607:2000. Health informatics. Messages for the exchange of information on medicine prescriptions</li>
<li>X12N healthcare transactions</li>
<li>US realm: National Council for Prescription Drug Programs (NCPDP)</li>
<li>Canadian realm: National Electronic Claims Standard (NeCST)</li>
</ul>
</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.9.2.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 conform to function [[CP.4.2]] (Manage Medication Orders) and provide the ability to transmit medication orders.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#02</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 for a prescriber/provider to transmit orders, prescriptions, eligibility inquiries, acknowledgements and renewal responses electronically to a pharmacy to initiate, change, cancel, or renew a medication order.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#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 receive any acknowledgements, prior authorizations, renewals, inquiries and fill notifications provided by the pharmacy or other participants in the electronic prescription process.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#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 clinical information with pharmacies using current realm-specific messaging or services standards.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#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 for providers and pharmacies to receive and transmit clinical information via secure e-mail or other electronic means, on both general and specific orders.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.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 receive and transmit secure real-time messages or services.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#07</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 transmit information on workflow tasks as part of communication to the provider.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#08</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 transmit a request to the pharmacy (based on an existing order) that additional medication be delivered (i.e. re-supply request).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#09</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 receive and transmit drug utilization review (DUR) findings and formulary & benefits (F&B) data with the pharmacy using standards-based messaging.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.9.2.3#10</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 capture authorization for transmittal of medication renewal data to an external system and transmittal of a notice to patient via preconfigured notification channel (e.g., Consumer Health Solution or Personal Health Record), 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.9.2.3"/>
<version value="0.16.0"/>
<name value="CPS_9_2_3_Support_for_Provider__Pharmacy_Communication"/>
<title
value="CPS.9.2.3 Support for Provider -Pharmacy Communication (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="Provide features to enable secure bi-directional communication of information electronically between practitioners and pharmacies or between practitioner and intended recipient of pharmacy orders."/>
<purpose
value="When a medication is prescribed, the order is routed to the pharmacy or other intended recipient of pharmacy orders. This information is used to avoid transcription errors and facilitate detection of potential adverse reactions. If there is a question from the pharmacy, that communication can be presented to the provider with their other tasks. In certain environments, medication order creation is a collaborative process involving the prescriber and facility staff. Accordingly, this function applies to communication process between the prescriber, facility and the pharmacy or other intended recipient of pharmacy orders. The transmission of prescription data between systems should conform to realm acceptable messaging standards. Informative examples:
- HL7 Clinical Document Architecture Release 2
- ISO/EN 13606 Electronic Health Record Communication
- CEN ENV 13607:2000. Health informatics. Messages for the exchange of information on medicine prescriptions
- X12N healthcare transactions
- US realm: National Council for Prescription Drug Programs (NCPDP)
- Canadian realm: National Electronic Claims Standard (NeCST)
Example:
- HL7 Clinical Document Architecture Release 2
- ISO/EN 13606 Electronic Health Record Communication
- CEN ENV 13607:2000. Health informatics. Messages for the exchange of information on medicine prescriptions
- X12N healthcare transactions
- US realm: National Council for Prescription Drug Programs (NCPDP)
- Canadian realm: National Electronic Claims Standard (NeCST)"/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-01"/>
<label value="CPS.9.2.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CP.4.2]] (Manage Medication Orders) and provide the ability to transmit medication orders."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-02"/>
<label value="CPS.9.2.3#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability for a prescriber/provider to transmit orders, prescriptions, eligibility inquiries, acknowledgements and renewal responses electronically to a pharmacy to initiate, change, cancel, or renew a medication order."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-03"/>
<label value="CPS.9.2.3#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to receive any acknowledgements, prior authorizations, renewals, inquiries and fill notifications provided by the pharmacy or other participants in the electronic prescription process."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-04"/>
<label value="CPS.9.2.3#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to exchange clinical information with pharmacies using current realm-specific messaging or services standards."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-05"/>
<label value="CPS.9.2.3#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability for providers and pharmacies to receive and transmit clinical information via secure e-mail or other electronic means, on both general and specific orders."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-06"/>
<label value="CPS.9.2.3#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to receive and transmit secure real-time messages or services."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-07"/>
<label value="CPS.9.2.3#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to transmit information on workflow tasks as part of communication to the provider."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.2.2#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-08"/>
<label value="CPS.9.2.3#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to transmit a request to the pharmacy (based on an existing order) that additional medication be delivered (i.e. re-supply request)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-09"/>
<label value="CPS.9.2.3#09"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to receive and transmit drug utilization review (DUR) findings and formulary &amp; benefits (F&amp;B) data with the pharmacy using standards-based messaging."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CPS.9.2.3-10"/>
<label value="CPS.9.2.3#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture authorization for transmittal of medication renewal data to an external system and transmittal of a notice to patient via preconfigured notification channel (e.g., Consumer Health Solution or Personal Health Record), according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
</Requirements>