This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 Application"
Jump to navigation
Jump to search
(→Notes) |
|||
| Line 4: | Line 4: | ||
== Notes == | == Notes == | ||
| − | *HL7 applications that have produced and consumed the HL7 message within an interaction are | + | *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. |
*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. | ||
Revision as of 06:40, 2 May 2007
An HL7 Application is an application level entity that posses knowledge and capability to produce and consume HL7 messages. 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.
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.
- 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
