<?xml version="1.0" encoding="UTF-8"?>

<Requirements xmlns="http://hl7.org/fhir">
  <id value="DHFPR2-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>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 &quot;Weights and Vitals&quot; 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 &quot;Dr. Jones must review Mr. Smith's blood work results.&quot; 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;">
            AS.5.3#01
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <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>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AS.5.3#02
            </td>
            <td style="padding-left: 4px;">
            MAY
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <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>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AS.5.3#03
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to link a non-clinical task to a clinical task.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            AS.5.3#04
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL provide the ability to link a clinical task to a patient.</p>
</div>
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="informative"/>
  </extension>
  <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
    <valueCode value="NC"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical value="http://hl7.org/ehrs/us/dhfpr2/ImplementationGuide/hl7.ehrs.us.dhfpr2"/>
      </extension>
    </valueInteger>
  </extension>
  <url value="http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-AS.5.3"/>
  <version value="2.0.0-ballot"/>
  <name value="AS_5_3_Clinical_Task_Linking"/>
  <title value="AS.5.3 Clinical Task Linking (Function)"/>
  <status value="active"/>
  <date value="2025-12-19T08:44:27+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="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </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 &quot;Weights and Vitals&quot; 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 &quot;Dr. Jones must review Mr. Smith's blood work results.&quot; 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."/>
  <derivedFrom value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.5.3"/>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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="AS.5.3#1"/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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)."/>
    <derivedFrom value="AS.5.3#2"/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="AS.5.3#3"/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="AS.5.3#4"/>
  </statement>
</Requirements>