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-CPS.3.1"/>
<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>Support the establishment, updates and use of assessment forms that will assist in the development of and adherence to care plans, guidelines, and protocols at the point of information capture.</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>As part of managing assessment definitions, the system will support the ability to create a set of assessment forms and, optionally, associated logic (e.g., workflow, business and clinical rules). This assessment definition process may include the ability to define, revise and manage the tools, files and processing for the conduct of a patient assessment. Furthermore, the assessment definition may also include template development, prompts for additional information, related notification alerts and workflow processes. When a clinician fills out an assessment, data entered triggers the system to prompt the assessor to consider issues that would help assure a complete/accurate assessment. A simple demographic value or presenting problem (or combination) could provide a template for data gathering that represents best practice in this situation, e.g., Type 2 (Adult Onset) Diabetes diabetic review, fall and 70+, and rectal bleeding. Support for standard assessment may include the ability to record and store the value for the answers to specific questions in standardized assessment tools or questionnaires. When a specific recognized-standard assessment does not exist, the system will support the creation of unique new, locally-defined assessment. The system may enable, and/or encourage the use of the format and data elements of similar assessments in the systems whenever possible. NOTE: A new assessment may not necessarily be unique, since a facility may copy an assessment from another facility.</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.1#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, maintain, and render recognized-standard assessment information in the patient record.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#02</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 supplemental assessment data from evidence-based standard assessments, practice standards, or other generally accepted, verifiable, and regularly updated standard clinical sources.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 render prompts based on practice standards to recommend additional assessment functions.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 capture the configuration of prompts based on practice standards to recommend additional assessment functions (e.g., by defining the text of each prompt).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 conform to function [[CP.1.4]] (Manage Problem List) and provide the ability to maintain the problem list by activating new problems and deactivating old problems as identified when captured using recognized-standard, and/or locally-defined assessments.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 maintain recognized-standard, and/or locally-defined assessment information for problems identified on the patient's problem list.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 audit modifications to the title, version, and data field labels (i.e., questions) of the recognized-standard, and/or locally-defined assessment used in a patient encounter.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 link the value of the assessment responses to the related data field label (i.e., link the answer to the exact wording of the question).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#09</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 manage assessment templates for provider use in assessing patient condition according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.3.1#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 manage recognized-standard, and/or locally-defined assessment templates 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.3.1"/>
<version value="2.1.0"/>
<name value="CPS_3_1_Support_for_Standard_Assessments"/>
<title value="CPS.3.1 Support for Standard Assessments (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="Support the establishment, updates and use of assessment forms that will assist in the development of and adherence to care plans, guidelines, and protocols at the point of information capture."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="As part of managing assessment definitions, the system will support the ability to create a set of assessment forms and, optionally, associated logic (e.g., workflow, business and clinical rules). This assessment definition process may include the ability to define, revise and manage the tools, files and processing for the conduct of a patient assessment. Furthermore, the assessment definition may also include template development, prompts for additional information, related notification alerts and workflow processes. When a clinician fills out an assessment, data entered triggers the system to prompt the assessor to consider issues that would help assure a complete/accurate assessment. A simple demographic value or presenting problem (or combination) could provide a template for data gathering that represents best practice in this situation, e.g., Type 2 (Adult Onset) Diabetes diabetic review, fall and 70+, and rectal bleeding. Support for standard assessment may include the ability to record and store the value for the answers to specific questions in standardized assessment tools or questionnaires. When a specific recognized-standard assessment does not exist, the system will support the creation of unique new, locally-defined assessment. The system may enable, and/or encourage the use of the format and data elements of similar assessments in the systems whenever possible. NOTE: A new assessment may not necessarily be unique, since a facility may copy an assessment from another facility."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-01"/>
<label value="CPS.3.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain, and render recognized-standard assessment information in the patient record."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-02"/>
<label value="CPS.3.1#02"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture supplemental assessment data from evidence-based standard assessments, practice standards, or other generally accepted, verifiable, and regularly updated standard clinical sources."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-03"/>
<label value="CPS.3.1#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD render prompts based on practice standards to recommend additional assessment functions."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-04"/>
<label value="CPS.3.1#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture the configuration of prompts based on practice standards to recommend additional assessment functions (e.g., by defining the text of each prompt)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-05"/>
<label value="CPS.3.1#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[CP.1.4]] (Manage Problem List) and provide the ability to maintain the problem list by activating new problems and deactivating old problems as identified when captured using recognized-standard, and/or locally-defined assessments."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-06"/>
<label value="CPS.3.1#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain recognized-standard, and/or locally-defined assessment information for problems identified on the patient's problem list."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-07"/>
<label value="CPS.3.1#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY audit modifications to the title, version, and data field labels (i.e., questions) of the recognized-standard, and/or locally-defined assessment used in a patient encounter."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#9"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-08"/>
<label value="CPS.3.1#08"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to link the value of the assessment responses to the related data field label (i.e., link the answer to the exact wording of the question)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.1.1#10"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-09"/>
<label value="CPS.3.1#09"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage assessment templates for provider use in assessing patient condition according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.5#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CPS.3.1-10"/>
<label value="CPS.3.1#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage recognized-standard, and/or locally-defined assessment templates according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
</Requirements>