HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 -
HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 -
HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/mvdzel/ehrsfm-fhir-r5/ and changes regularly. See the Directory of published versions
| Page standards status: Normative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2-AS.5.3"/>
<meta>
<profile
value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
</meta>
<language value="en"/>
<text>
<status value="extensions"/>
<div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
<div 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>Linkage of tasks to EHR components, patients, and/or a relevant part of the electronic health record.</p>
</div></div>
<div 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>Clinical tasks must include information or provide an electronic link to information that is required to complete the task. There is a need to create the appropriate links and, then, to have the system automatically present the information that was linked. For example, this may include a patient location in a facility, a patient's, and/or family's contact information, or a link to new laboratory results in the patient's EHR. Other example: the linkage of prescription task to the appropriate patient care plan to facilitate follow-up actions; a task to take weights links to the "Weights and Vitals" screen to record the result; a task to complete a fall assessment links to the fall assessment form to be completed. An example of a well-defined task is "Dr. Jones must review Mr. Smith's blood work results." Efficient workflow is facilitated by navigating to the appropriate area of the record to ensure that the appropriate test result for the correct patient is reviewed.</p>
</div></div>
<div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
<div>AS.5.3#01</div>
</td>
<td style="padding-left: 4px;">
<div>SHALL</div>
</td>
<td style="padding-left: 4px;" class="requirement">
<div><div><p>The system SHALL provide the ability to link a clinical task to the component of the EHR system required to complete the task (e.g., link a clinical task regarding a surgical procedure to an assessment template that will help the provider to collect laceration information regarding a patient's stab wound).</p>
</div></div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<div>AS.5.3#02</div>
</td>
<td style="padding-left: 4px;">
<div>MAY</div>
</td>
<td style="padding-left: 4px;" class="requirement">
<div><div><p>The system MAY present automatically the component of the system required to complete a clinical task (e.g., offering a provider with an assessment template that will help collect laceration information regarding a patient's stab wound).</p>
</div></div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<div>AS.5.3#03</div>
</td>
<td style="padding-left: 4px;">
<div>SHOULD</div>
</td>
<td style="padding-left: 4px;" class="requirement">
<div><div><p>The system SHOULD provide the ability to link a non-clinical task to a clinical task.</p>
</div></div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<div>AS.5.3#04</div>
</td>
<td style="padding-left: 4px;">
<div>SHALL</div>
</td>
<td style="padding-left: 4px;" class="requirement">
<div><div><p>The system SHALL provide the ability to link a clinical task to a patient.</p>
</div></div>
</td>
</tr>
</table>
</div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="normative"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="ehr"/>
</extension>
<url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.5.3"/>
<version value="2.1.1"/>
<name value="AS_5_3_Clinical_Task_Linking"/>
<title value="AS.5.3 Clinical Task Linking (Function)"/>
<status value="active"/>
<date value="2025-10-31T19:25:08+00:00"/>
<publisher value="HL7 International / Electronic Health Records"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Linkage of tasks to EHR components, patients, and/or a relevant part of the electronic health record."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="Clinical tasks must include information or provide an electronic link to information that is required to complete the task. There is a need to create the appropriate links and, then, to have the system automatically present the information that was linked. For example, this may include a patient location in a facility, a patient's, and/or family's contact information, or a link to new laboratory results in the patient's EHR. Other example: the linkage of prescription task to the appropriate patient care plan to facilitate follow-up actions; a task to take weights links to the "Weights and Vitals" screen to record the result; a task to complete a fall assessment links to the fall assessment form to be completed. An example of a well-defined task is "Dr. Jones must review Mr. Smith's blood work results." Efficient workflow is facilitated by navigating to the appropriate area of the record to ensure that the appropriate test result for the correct patient is reviewed."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2-AS.5.3-01"/>
<label value="AS.5.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to link a clinical task to the component of the EHR system required to complete the task (e.g., link a clinical task regarding a surgical procedure to an assessment template that will help the provider to collect laceration information regarding a patient's stab wound)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.3.1.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2-AS.5.3-02"/>
<label value="AS.5.3#02"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY present automatically the component of the system required to complete a clinical task (e.g., offering a provider with an assessment template that will help collect laceration information regarding a patient's stab wound)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2-AS.5.3-03"/>
<label value="AS.5.3#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link a non-clinical task to a clinical task."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2-AS.5.3-04"/>
<label value="AS.5.3#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to link a clinical task to a patient."/>
</statement>
</Requirements>
IG © 2025 HL7 International / Electronic Health Records.
Package hl7.ehrs.uv.ehrsfmr2#2.1.1 based on FHIR 5.0.0.
Generated 2025-10-31
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change