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-CP.3.4"/>
<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 templates and forms for clinicians to use for care plans, guidelines and protocols during provision of care and care planning.</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>During the provision of care, the clinician reviews and uses templates and forms to ensure consistent quality patient care. Care plans, guidelines or protocols may contain goals or targets for the patient, specific guidance to the providers, suggested orders, and nursing interventions, among other items, including alerts. Information such as Order sets for care plans may arrive from an external institution and need to be approved locally before being inserted into the care plan. Tracking of implementation or approval dates, modifications and relevancy to specific domains or context is provided. Transfer of treatment and care plans may be implemented electronically using, for example, templates, or by printing plans to paper.</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>CP.3.4#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 manage patient-specific plans of care and treatment.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 conform to function [[CP.7.1]] (Present Guidelines and Protocols for Planning Care) and provide the ability to render locally or non-locally developed templates, guidelines, and protocols for the creation of patient-specific plans of care and treatment.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#03</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 metadata regarding a patient's plan of care or treatment (e.g., authors, creation date, version history, references, local sources and non-local sources) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 link order sets with care plans.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 link the care plan with condition(s) in problem lists.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 determine and render order sets from care plans.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 determine and render care plans from order sets.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 care plans and treatment plans to other care providers.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 conform to function [[AS.5.1]] (Clinical Task Creation, Assignment and Routing) to link care plan items into the tasks assigned and routed.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#10</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD conform to function [[AS.5.3]] (Clinical Task Linking) to link care plan items and tasks.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#11</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD conform to function [[AS.5.4]] (Clinical Task Status Tracking) to link care plan items with tasks tracked.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#12</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD conform to function [[CPS.4.2.2]] (Support for Patient-Specific Dosing and Warnings) to determine and render related warnings on drug dosing and interactions.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#13</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 [[CPS.1.7.1]] (Support for Patient and Family Preferences) to improve the effectiveness of care and treatment plans.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#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 provide the ability to determine and render a care plan review schedule or conference schedule.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#15</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, maintain and render, as discrete data, the reason for variation from rule-based clinical messages (e.g., alerts and reminders).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#16</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 that a patient should not be on a generally recommended care plan and the reason why.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#17</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 care processes across the continuum of care.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#18</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 render care processes from across the continuum of care.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#19</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 render internal care plans, guidelines, and protocols according to scope of practice.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.4#20</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 render external care plans, guidelines, and protocols according to scope of practice, and/or organizational policy.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.3.4"/>
<version value="0.16.0"/>
<name value="CP_3_4_Manage_Patient_Specific_Care_and_Treatment_Plans"/>
<title
value="CP.3.4 Manage Patient-Specific Care and Treatment Plans (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 templates and forms for clinicians to use for care plans, guidelines and protocols during provision of care and care planning."/>
<purpose
value="During the provision of care, the clinician reviews and uses templates and forms to ensure consistent quality patient care. Care plans, guidelines or protocols may contain goals or targets for the patient, specific guidance to the providers, suggested orders, and nursing interventions, among other items, including alerts. Information such as Order sets for care plans may arrive from an external institution and need to be approved locally before being inserted into the care plan. Tracking of implementation or approval dates, modifications and relevancy to specific domains or context is provided. Transfer of treatment and care plans may be implemented electronically using, for example, templates, or by printing plans to paper."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-01"/>
<label value="CP.3.4#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage patient-specific plans of care and treatment."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-02"/>
<label value="CP.3.4#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CP.7.1]] (Present Guidelines and Protocols for Planning Care) and provide the ability to render locally or non-locally developed templates, guidelines, and protocols for the creation of patient-specific plans of care and treatment."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-03"/>
<label value="CP.3.4#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture metadata regarding a patient's plan of care or treatment (e.g., authors, creation date, version history, references, local sources and non-local sources) according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-04"/>
<label value="CP.3.4#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link order sets with care plans."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-05"/>
<label value="CP.3.4#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link the care plan with condition(s) in problem lists."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-06"/>
<label value="CP.3.4#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to determine and render order sets from care plans."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-07"/>
<label value="CP.3.4#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to determine and render care plans from order sets."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-08"/>
<label value="CP.3.4#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to transmit care plans and treatment plans to other care providers."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#8"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-09"/>
<label value="CP.3.4#09"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[AS.5.1]] (Clinical Task Creation, Assignment and Routing) to link care plan items into the tasks assigned and routed."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#9"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-10"/>
<label value="CP.3.4#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[AS.5.3]] (Clinical Task Linking) to link care plan items and tasks."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#10"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-11"/>
<label value="CP.3.4#11"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[AS.5.4]] (Clinical Task Status Tracking) to link care plan items with tasks tracked."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#11"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-12"/>
<label value="CP.3.4#12"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[CPS.4.2.2]] (Support for Patient-Specific Dosing and Warnings) to determine and render related warnings on drug dosing and interactions."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#13"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-13"/>
<label value="CP.3.4#13"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY conform to function [[CPS.1.7.1]] (Support for Patient and Family Preferences) to improve the effectiveness of care and treatment plans."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#14"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-14"/>
<label value="CP.3.4#14"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to determine and render a care plan review schedule or conference schedule."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-15"/>
<label value="CP.3.4#15"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain and render, as discrete data, the reason for variation from rule-based clinical messages (e.g., alerts and reminders)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-16"/>
<label value="CP.3.4#16"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture that a patient should not be on a generally recommended care plan and the reason why."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-17"/>
<label value="CP.3.4#17"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture care processes across the continuum of care."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-18"/>
<label value="CP.3.4#18"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render care processes from across the continuum of care."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-19"/>
<label value="CP.3.4#19"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render internal care plans, guidelines, and protocols according to scope of practice."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.3.4-20"/>
<label value="CP.3.4#20"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render external care plans, guidelines, and protocols according to scope of practice, and/or organizational policy."/>
</statement>
</Requirements>