Product MT
Contents
- 1 Product Brief - HL7 V3: Shared Messages
- 1.1 Product Name
- 1.2 Topics
- 1.3 Standard Category
- 1.4 Integration Paradigm
- 1.5 Type
- 1.6 Releases
- 1.7 Summary
- 1.8 Description
- 1.9 Business Case (Intended Use, Customers)
- 1.10 Benefits
- 1.11 Implementations/ Case Studies (Actual Users)
- 1.12 Resources
- 1.13 Relationship to/ Dependencies on, other standards
- 1.14 Links to current projects in development
back to Main_Page
back to Product_List
Product Name
HL7 V3: Shared Messages
Topics
Standard Category
- Health Information Exchange Standards
Integration Paradigm
- Messaging
Type
Normative, ANSI Standard
Releases
ANSI/HL7 V3 COMT: R1-2004, R2-2005, R3-2010
Summary
Shared Messages are a work product produced for expressing common, useful and reusable message types. A Shared Message can be envisioned as a message type that is reusable in interactions in any of the domains within the HL7 standard. This document provides data on common messages such acknowledgements shared across multiple domains.
Description
The scope of the Shared Messages Domain includes message types shared by all the clinical domains. The domain model consists of a minimalistic Act payload used to convey generic information related to an Act and its associated classes. Although CMET terminology does not apply to Message Types, the Common Messages domain model can be thought of as an Act CMET [minimal].
The Act in the Shared Message DMIM can be thought of as a reference to, or as a summary version of, an act. This includes use-cases such as the notification of a status change of an act, the sending of application level accept/reject messages, the registration of acts in repositories, and responding to Act-related queries.
Note: The Shared Messages domain will include storyboards, application roles, trigger events, interactions, and message types shared by any of the healthcare domains. Some of these will be for example purposes only. The examples will not be used in their own right but as a reusable payload in various domains. When used in this fashion, the message is transmitted as a result of a domain interaction and between two domain application roles. Artifacts will be documented as to whether they are examples or can be used in their own right.
Business Case (Intended Use, Customers)
This collection of artifacts is used by all of the domains for acknowledgements, etc.
Benefits
This provides a consistent set of reference artifacts, and reference models. This provides common content is a common library.
Implementations/ Case Studies (Actual Users)
The majority of the messaging standards use the shared messages. Includes any of the IHE PDQ V3 profiles.
Resources
Work Groups
Education
- See more at http://www.hl7.org/implement/training.cfm
Certification Available
- none
Presentations
Relationship to/ Dependencies on, other standards
- Incorporates elements of the RIM
- Instantiates the 'blue' classes from the RIM.
Links to current projects in development
- Project Insight ID # 277, Shared Messages Domain (COMT), Release 3
