This page is part of the HL7 Electronic Health Record System Functional Model, Release 2.1.1 (v2.1.1-ballot: Normative 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
: TI.5.3 Standards-Based Application Integration (Function) - TTL Representation
Raw ttl | Download
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
a fhir:Requirements ;
fhir:nodeRole fhir:treeRoot ;
fhir:id [ fhir:v "EHRSFMR2-TI.5.3"] ; #
fhir:meta [
( fhir:profile [
fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction> ] )
] ; #
fhir:text [
fhir:status [ fhir:v "extensions" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <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>Integrate applications in a standards-based manner.</p>\n</div></span>\n\n \n <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>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>\n<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.\nExample:\nExamples of standards-based application integration approaches include:</p>\n<ul>\n<li>Desktop visual integration via HL7 Clinical Context Object Workgroup (CCOW) standards.</li>\n<li>Workflow function integration via the Workflow Management Coalition (WfMC) standards.</li>\n<li>Enterprise Information System Architecture integration of EHR systems via Service Oriented Architecture (SOA) standards.</li>\n</ul>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <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>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.5.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.5.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"^^rdf:XMLLiteral
] ; #
fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ] ;
fhir:value [
a fhir:code ;
fhir:v "ehr" ]
] ) ; #
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.5.3"^^xsd:anyURI] ; #
fhir:version [ fhir:v "2.1.1-ballot"] ; #
fhir:name [ fhir:v "TI_5_3_Standards_Based_Application_Integration"] ; #
fhir:title [ fhir:v "TI.5.3 Standards-Based Application Integration (Function)"] ; #
fhir:status [ fhir:v "active"] ; #
fhir:date [ fhir:v "2025-04-04T11:04:36+11:00"^^xsd:dateTime] ; #
fhir:publisher [ fhir:v "HL7 International / Electronic Health Records"] ; #
fhir:contact ( [
( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://www.hl7.org/Special/committees/ehr" ] ] )
] ) ; #
fhir:description [ fhir:v "Integrate applications in a standards-based manner."] ; #
fhir:jurisdiction ( [
( fhir:coding [
fhir:system [ fhir:v "http://unstats.un.org/unsd/methods/m49/m49.htm"^^xsd:anyURI ] ;
fhir:code [ fhir:v "001" ] ;
fhir:display [ fhir:v "World" ] ] )
] ) ; #
fhir:purpose [ fhir:v "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.\n\nThe 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.\nExample:\nExamples of standards-based application integration approaches include:\n- Desktop visual integration via HL7 Clinical Context Object Workgroup (CCOW) standards.\n- Workflow function integration via the Workflow Management Coalition (WfMC) standards.\n- Enterprise Information System Architecture integration of EHR systems via Service Oriented Architecture (SOA) standards."] ; #
fhir:statement ( [
( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false ] ] ) ;
fhir:key [ fhir:v "EHRSFMR2-TI.5.3-01" ] ;
fhir:label [ fhir:v "TI.5.3#01" ] ;
( fhir:conformance [ fhir:v "SHALL" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "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." ] ;
fhir:derivedFrom [ fhir:v "EHR-S_FM_R1.1 IN.5.3#1" ]
] [
( fhir:extension [
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ] ;
fhir:value [
a fhir:boolean ;
fhir:v false ] ] ) ;
fhir:key [ fhir:v "EHRSFMR2-TI.5.3-02" ] ;
fhir:label [ fhir:v "TI.5.3#02" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v false ] ;
fhir:requirement [ fhir:v "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))." ]
] ) . #
|
Propose a change