This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 Application"
Jump to navigation
Jump to search
(→Notes) |
|||
| Line 1: | Line 1: | ||
[[Image:Reference Messaging Architecture.jpg|275px|right|thumb|Application Architecture]] | [[Image:Reference Messaging Architecture.jpg|275px|right|thumb|Application Architecture]] | ||
| − | An '''HL7 Application''' is an application level entity that posses knowledge and capability to produce and consume HL7 messages. HL7 | + | An '''HL7 Application''' is an application level entity that posses knowledge and capability to produce and consume HL7 messages. HL7 Application encompasses the scope of the HL7 standardization efforts - i.e. it embeds the knowledge about processing HL7 information models (DMIMs, RMIMs, related semantics, and respective receiver responsibilities), and is responsibel for serializing the message using one of the HL7 ITS specifications available. |
== Notes == | == Notes == | ||
*HL7 applications that have produced and consumed the HL7 message within an interaction are identified in the Device.id attribute in within the Transmission Wrapper. | *HL7 applications that have produced and consumed the HL7 message within an interaction are identified in the Device.id attribute in within the Transmission Wrapper. | ||
| + | *HL7 application encompases the implementation of a set of one to many HL7 application roles and their respective responsibilities as defined by the HL7v3 standard. However, since the concept of the application role is not a normative one, we cannot reference the term in our defintion | ||
*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. | *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. | ||
| + | Last change: --[[User:Miroslav|Miroslav Koncar]] 06:30, 2 May 2007 (CDT) | ||
---- | ---- | ||
| − | |||
[[Category:ATS Glossary]] | [[Category:ATS Glossary]] | ||
Revision as of 11:30, 2 May 2007
An HL7 Application is an application level entity that posses knowledge and capability to produce and consume HL7 messages. HL7 Application encompasses the scope of the HL7 standardization efforts - i.e. it embeds the knowledge about processing HL7 information models (DMIMs, RMIMs, related semantics, and respective receiver responsibilities), and is responsibel for serializing the message using one of the HL7 ITS specifications available.
Notes
- HL7 applications that have produced and consumed the HL7 message within an interaction are identified in the Device.id attribute in within the Transmission Wrapper.
- HL7 application encompases the implementation of a set of one to many HL7 application roles and their respective responsibilities as defined by the HL7v3 standard. However, since the concept of the application role is not a normative one, we cannot reference the term in our defintion
- 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.
Last change: --Miroslav Koncar 06:30, 2 May 2007 (CDT)
