Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: TI.5.1.3 Structured-Message Interchange Standards (Function) - XML Representation

Active as of 2024-11-26

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-TI.5.1.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>Support the management of structured messages.</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>Structured messages are an important method of facilitating the exchange of information to support care. Messages are often considered to be more transitory in nature; documents are often considered to be more permanent in nature.
Example:
Examples of structured messages include notifications of a patient's arrival or discharge events.</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>TI.5.1.3#01</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>SHALL</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHALL provide the ability to manage structured messages 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-TI.5.1.3"/>
  <version value="2.1.0"/>
  <name value="TI_5_1_3_Structured_Message_Interchange_Standards"/>
  <title
         value="TI.5.1.3 Structured-Message Interchange Standards (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 management of structured messages."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <purpose
           value="Structured messages are an important method of facilitating the exchange of information to support care. Messages are often considered to be more transitory in nature; documents are often considered to be more permanent in nature.
Example:
Examples of structured messages include notifications of a patient's arrival or discharge events."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="EHRSFMR2.1-TI.5.1.3-01"/>
    <label value="TI.5.1.3#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to manage structured messages according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
</Requirements>