Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: AS.4.3 Support for Communications Between Organizations (Function) - XML Representation

Active as of 2024-08-12

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-AS.4.3"/>
  <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>Facilitate communications regarding patient orders, data and status between organizations.</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>There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers.</p>
<p>This information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers).</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.4.3#01</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 render patient transfer information to other health care organizations (e.g., hospitals, clinics, specialists, nursing homes) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.4.3#02</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY provide the ability to render selected patient transfer information to non-health care organizations (e.g., funeral home) 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-AS.4.3"/>
  <version value="0.16.0"/>
  <name value="AS_4_3_Support_for_Communications_Between_Organizations"/>
  <title
         value="AS.4.3 Support for Communications Between Organizations (Function)"/>
  <status value="active"/>
  <date value="2024-08-12T10:56:01+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Facilitate communications regarding patient orders, data and status between organizations."/>
  <purpose
           value="There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers.

This information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers)."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="EHRSFMR2.1-AS.4.3-01"/>
    <label value="AS.4.3#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to render patient transfer information to other health care organizations (e.g., hospitals, clinics, specialists, nursing homes) according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="EHRSFMR2.1-AS.4.3-02"/>
    <label value="AS.4.3#02"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to render selected patient transfer information to non-health care organizations (e.g., funeral home) according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
</Requirements>