Description I:

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.
Criteria N:
TI.5.3#01 SHALL

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.
TI.5.3#02 SHOULD

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)).
<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>