This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "HL7 Application"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
[[Image:Ats_architecture.gif|275px|right|thumb|Application Architecture]]
+
[[Image:Reference Messaging Architecture.jpg|275px|right|thumb|Application Architecture]]
An '''HL7 Application''' is an implementation of a set of one to many HL7 application roles and their respective responsibilities as defined by the HL7v3 standard. HL7 Application is the single entity in the [[Application Architecture]] that deals with the domain specific HL7 composite messages generation and management.
+
An '''HL7 Application''' is an implementation of a set of one to many HL7 application roles and their respective responsibilities as defined by the HL7v3 standard. HL7 Application is the single entity in the [[Application Architecture]] residing in the application layer, that deals with the domain specific HL7 composite messages generation and management.
 +
Note that there might be other business entities that reside in the application layer (e.g. data mining and warehousing applications, ERP systems, etc), which perfom various business fucntionalities in the healthcare settings. They are not represented on the [[Application Architecture]] map since they clearly fall out of the scope of HL7 messaging artifacts and standardization efforts.  
  
 
----
 
----

Revision as of 08:43, 29 April 2007

Application Architecture

An HL7 Application is an implementation of a set of one to many HL7 application roles and their respective responsibilities as defined by the HL7v3 standard. HL7 Application is the single entity in the Application Architecture residing in the application layer, that deals with the domain specific HL7 composite messages generation and management. Note that there might be other business entities that reside in the application layer (e.g. data mining and warehousing applications, ERP systems, etc), which perfom various business fucntionalities in the healthcare settings. They are not represented on the Application Architecture map since they clearly fall out of the scope of HL7 messaging artifacts and standardization efforts.


Back to Open ATS Issues