EHRS-FM IG

ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build

ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

: AS.7.5 Manage Transitions of Care and Discharged Patients (Function) - XML Representation

Active as of 2024-06-01

Raw xml | Download



<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-AS.7.5"/>
  <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 a means to manage outstanding patient issues after the encounter, for transits of care and discharge.</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>After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter.</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>AS.7.5#01</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 post-encounter tasks (e.g., discharge planning, patient instructions, transfer activities).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.7.5#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 tag the patient as a transfer patient (e.g., hospital-to-hospital, birthing facility, and long-term-care-facility to hospital).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.7.5#03</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 transfer facility demographic information to the transfer patient.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.7.5#04</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 the transfer mode of transportation (e.g., ambulance, airplane).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.7.5#05</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 transportation provider demographics.</p>
</div></span>
                
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7.5"/>
  <version value="0.14.0"/>
  <name value="AS_7_5_Manage_Transitions_of_Care_and_Discharged_Patients"/>
  <title
         value="AS.7.5 Manage Transitions of Care and Discharged Patients (Function)"/>
  <status value="active"/>
  <date value="2024-06-01T08:34:10+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 a means to manage outstanding patient issues after the encounter, for transits of care and discharge."/>
  <purpose
           value="After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-AS.7.5-01"/>
    <label value="AS.7.5#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to manage post-encounter tasks (e.g., discharge planning, patient instructions, transfer activities)."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-AS.7.5-02"/>
    <label value="AS.7.5#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to tag the patient as a transfer patient (e.g., hospital-to-hospital, birthing facility, and long-term-care-facility to hospital)."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-AS.7.5-03"/>
    <label value="AS.7.5#03"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to link transfer facility demographic information to the transfer patient."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-AS.7.5-04"/>
    <label value="AS.7.5#04"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to capture the transfer mode of transportation (e.g., ambulance, airplane)."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2.1-AS.7.5-05"/>
    <label value="AS.7.5#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to capture transportation provider demographics."/>
  </statement>
</Requirements>