ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.13.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.13.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.13.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-04-13 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CPS.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>Identify and present the appropriate care plans, guidelines, protocols, and/or clinical pathways for the management of patient-specific conditions that are identified in a patient clinical encounter.</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>At the time of the clinical encounter (problem identification), recommendations for tests, treatments, medications, immunizations, referrals and evaluations are presented based on evaluation of patient-specific data such as age, gender, developmental stage, their health profile, and any site-specific considerations. These may be modified on the basis of new clinical data at subsequent encounters.</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.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 render care and treatment plans that are sensitive to the context of patient data and assessments.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#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 the choice of action in response to care plan suggestions.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#03</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD determine and render alerts, notifications, and reports about variances from standard care plans, guidelines, protocols, and clinical pathways.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#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 conform to function [[CPS.3.1]] (Support for Standard Assessments).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#05</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 [[CPS.3.2]] (Support for Patient Context-Driven Assessments).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#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 conform to function [[CPS.3.3]] (Support for Standard Care Plans, Guidelines, Protocols).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#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 capture, maintain, and render specialized medical treatment guidelines and protocols for unique physical, chemical, biological, and radiologic exposures.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.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 manage biometric data, such as age-specific, weight-specific or height-specific normative data, to identify, track and provide alerts, notifications and reports about variances, care plans, guidelines and protocols.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.4#09</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 care plan templates to be used as a basis for the creation of new plans of care and treatment.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.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 provide the ability to capture care plan templates from previously developed care plans.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.3.4"/>
<version value="0.13.0"/>
<name
value="CPS_3_4_Support_for_Context_Sensitive_Care_Plans__Guidelines__Protocols"/>
<title
value="CPS.3.4 Support for Context-Sensitive Care Plans, Guidelines, Protocols (Function)"/>
<status value="active"/>
<date value="2024-04-13T09:09:23+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Identify and present the appropriate care plans, guidelines, protocols, and/or clinical pathways for the management of patient-specific conditions that are identified in a patient clinical encounter."/>
<purpose
value="At the time of the clinical encounter (problem identification), recommendations for tests, treatments, medications, immunizations, referrals and evaluations are presented based on evaluation of patient-specific data such as age, gender, developmental stage, their health profile, and any site-specific considerations. These may be modified on the basis of new clinical data at subsequent encounters."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-01"/>
<label value="CPS.3.4#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render care and treatment plans that are sensitive to the context of patient data and assessments."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-02"/>
<label value="CPS.3.4#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture and maintain the choice of action in response to care plan suggestions."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-03"/>
<label value="CPS.3.4#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD determine and render alerts, notifications, and reports about variances from standard care plans, guidelines, protocols, and clinical pathways."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-04"/>
<label value="CPS.3.4#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CPS.3.1]] (Support for Standard Assessments)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-05"/>
<label value="CPS.3.4#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CPS.3.2]] (Support for Patient Context-Driven Assessments)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#8"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-06"/>
<label value="CPS.3.4#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CPS.3.3]] (Support for Standard Care Plans, Guidelines, Protocols)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-07"/>
<label value="CPS.3.4#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain, and render specialized medical treatment guidelines and protocols for unique physical, chemical, biological, and radiologic exposures."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-08"/>
<label value="CPS.3.4#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage biometric data, such as age-specific, weight-specific or height-specific normative data, to identify, track and provide alerts, notifications and reports about variances, care plans, guidelines and protocols."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.2.1.2#9"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-09"/>
<label value="CPS.3.4#09"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain and render care plan templates to be used as a basis for the creation of new plans of care and treatment."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.6.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.4-10"/>
<label value="CPS.3.4#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture care plan templates from previously developed care plans."/>
</statement>
</Requirements>