ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
Publish Box goes here
| Active as of 2024-11-26 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CP.7.2"/>
<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>Document and support the management of the disposition process for a patient by managing recommendations for future care.</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>Patient encounters or treatments can end in many different states and support for these requires that the EHR support the ability to capture and maintain recommendations for the further future care of the patient. The EHR should accommodate, at a minimum, the following possible recommendations for future care (or dispositions) along with other supporting information for the recommendations:</p>
<ul>
<li>discharge,</li>
<li>admission,</li>
<li>transfer,</li>
<li>death,</li>
<li>left without being seen (LWBS),</li>
<li>left without treatment (LWOT),</li>
<li>elopements (i.e. leaving without notifying the facility or wandering),</li>
<li>left against medical advice (AMA),</li>
<li>patients triaged to other clinics, and</li>
<li>administrative errors.</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>CP.7.2#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 recommendations for future care as discrete data elements including the recommending provider and an alert date for the recommendation to take effect.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#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 to maintain recommendations and associated recommendation meta-data (e.g., date of alert).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#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 render an alert of the recommendation based on the date associated with the recommendation (e.g., if recommendation is to "book appointment for physical therapy in 2 weeks" - alert will be triggered in 1.5 weeks for follow-up).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#04</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 recommendations for future care or post-encounter disposition from encounter and diagnostic studies imported in structured documents.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#05</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 recommended actions for future care along with the recommending provider, the date recommended and the date suggested to carry out the recommendation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#06</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 link the recommendation for future care with the original documentation of that recommendation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.7.2#07</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 link the recommendation with condition(s) on the Problem List.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.7.2"/>
<version value="2.1.0"/>
<name value="CP_7_2_Manage_Recommendations_for_Future_Care"/>
<title value="CP.7.2 Manage Recommendations for Future Care (Function)"/>
<status value="active"/>
<date value="2024-11-26T16:30:50+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Document and support the management of the disposition process for a patient by managing recommendations for future care."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="Patient encounters or treatments can end in many different states and support for these requires that the EHR support the ability to capture and maintain recommendations for the further future care of the patient. The EHR should accommodate, at a minimum, the following possible recommendations for future care (or dispositions) along with other supporting information for the recommendations:
- discharge,
- admission,
- transfer,
- death,
- left without being seen (LWBS),
- left without treatment (LWOT),
- elopements (i.e. leaving without notifying the facility or wandering),
- left against medical advice (AMA),
- patients triaged to other clinics, and
- administrative errors."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-01"/>
<label value="CP.7.2#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture recommendations for future care as discrete data elements including the recommending provider and an alert date for the recommendation to take effect."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-02"/>
<label value="CP.7.2#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to maintain recommendations and associated recommendation meta-data (e.g., date of alert)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-03"/>
<label value="CP.7.2#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render an alert of the recommendation based on the date associated with the recommendation (e.g., if recommendation is to "book appointment for physical therapy in 2 weeks" - alert will be triggered in 1.5 weeks for follow-up)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-04"/>
<label value="CP.7.2#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture recommendations for future care or post-encounter disposition from encounter and diagnostic studies imported in structured documents."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-05"/>
<label value="CP.7.2#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture recommended actions for future care along with the recommending provider, the date recommended and the date suggested to carry out the recommendation."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-06"/>
<label value="CP.7.2#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link the recommendation for future care with the original documentation of that recommendation."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.7.2-07"/>
<label value="CP.7.2#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link the recommendation with condition(s) on the Problem List."/>
</statement>
</Requirements>