HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2
2.0.0-ballot - Informative United States of America flag

HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/dhfp-ig/ and changes regularly. See the Directory of published versions

: TI.5.3 Standards-Based Application Integration (Function)

Page standards status: Informative Maturity Level: 1

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="DHFPR2-TI.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>An EHR-S often consists of multiple applications. Some of those applications may be within the EHR-S; others may be external to the EHR-S. The user of the EHR-S often benefits when those applications are integrated. Application integration can be accomplished in an ad-hoc fashion or in a standards-based fashion.</p>
<p>The method(s) by which applications may be integrated within an organization depends on that organization's approach to application integration. A given organization could conceivably employ multiple application integration approaches to meet various application integration requirements.</p>
<p>Example(s):
Examples of standards-based application integration approaches include:</p>
<ul>
<li>Desktop visual integration via HL7 Clinical Context Object Workgroup (CCOW) standards.</li>
<li>Workflow function integration via the Workflow Management Coalition (WfMC) standards.</li>
<li>Enterprise Information System Architecture integration of EHR systems via Service Oriented Architecture (SOA) standards.</li>
</ul>
</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;">
            TI.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 integrate applications in a standards-based fashion when the system is composed of, and/or is extended by disparate applications.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.5.3#02
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to integrate user (or system) authentication for the purposes application context management (e.g., Graphical User Interface application integration via HL7's Context Management Standard from the Clinical Context Object Work Group (CCOW)).</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-TI.5.3"/>
  <version value="2.0.0-ballot"/>
  <name value="TI_5_3_Standards_Based_Application_Integration"/>
  <title value="TI.5.3 Standards-Based Application Integration (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="Integrate applications in a standards-based manner."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </coding>
  </jurisdiction>
  <purpose
           value="An EHR-S often consists of multiple applications. Some of those applications may be within the EHR-S; others may be external to the EHR-S. The user of the EHR-S often benefits when those applications are integrated. Application integration can be accomplished in an ad-hoc fashion or in a standards-based fashion.

The method(s) by which applications may be integrated within an organization depends on that organization's approach to application integration. A given organization could conceivably employ multiple application integration approaches to meet various application integration requirements.

Example(s):
Examples of standards-based application integration approaches include:
- Desktop visual integration via HL7 Clinical Context Object Workgroup (CCOW) standards.
- Workflow function integration via the Workflow Management Coalition (WfMC) standards.
- Enterprise Information System Architecture integration of EHR systems via Service Oriented Architecture (SOA) standards."/>
  <derivedFrom
               value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.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-TI.5.3-01"/>
    <label value="TI.5.3#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to integrate applications in a standards-based fashion when the system is composed of, and/or is extended by disparate applications."/>
    <derivedFrom value="TI.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-TI.5.3-02"/>
    <label value="TI.5.3#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to integrate user (or system) authentication for the purposes application context management (e.g., Graphical User Interface application integration via HL7's Context Management Standard from the Clinical Context Object Work Group (CCOW))."/>
    <derivedFrom value="TI.5.3#2"/>
  </statement>
</Requirements>