![]() |
HDR Version 7 HL7 Version 3 Messaging Conformance Specification |
Contents Previous Next Conformance Examples |
This section contains the following topics:
3.1.1 Introduction 3.1.2 RMIM 3.1.3 Referenced CMETs 3.1.4 Links to Artifacts
The Message Wrapper is the communication or transport wrapper, which contains message header information including the sending and receiving applications and organizations. It also contains the date and time that the message was sent on and the specific Interaction ID that can be used to determine the message type, trigger event and the sending and receiving application roles.
HDR Version 7 Message Wrapper is fully conformant to HL7 Message Wrapper. Attachment class is supported by Messaging Services in version 7.
Attachment Class:
Following are the classes and their attributes which have notes specific to HDR Implementation.
Table 3.1.1-1 Message Wrapper: Attributes with HDR Implementation Specific CommentsSI. No | Class Name | Attribute | Implementation Specific Comments |
1 | Message | versionCode | For HDR conformance, this field must be set to V3PR1 as no other versions are supported. OMP hardcodes this value in the generated message. |
2 | Message | interactionId | A mandatory instance identifier specifying the unique information interchange derived from the trigger event, domain message type and sending and receiving application roles. In the case of inbound messages, this value is determined by the sending system. There is no inbound processing in HDR contingent upon this value. In the case of outbound messaging, this value must be configured at implementation time for each combination of trigger event and receiver. |
3 | Message | profileId | An optional set of instance identifiers that allows a given implementation to explicitly state how it varies from the standard message definition. Since Oracle is an early adopter of V3 messages, there are 2 supported extensions for this identifier. They are 2.01.4 and 2.14.1.01. The 2.01.4 value is for messages developed under the HTB version 5 release. The 2.14.1.01 value is for messages developed under HDR Version 7. |
4 | CommunicationFunctionRCV | telecom | This attribute is not required for messages being sent to HDR. |
5 | Entity: DeviceRSP | id | A mandatory instance identifier that uniquely identifies the RespondTo Application. This identifier will be used by HDR to generate the receiver of the acknowledgment message. |
6 | CommunicationFunctionSND | The sending communication function is the place holder for the sending application and its associated Organization. The sender is mandatory in any message and is associated with the trigger event in the HDR configuration. |
The following figure diagrams the Message Wrapper RMIM:
Figure: 3.1.2-1 Message Wrapper RMIM
Artifacts | Link |
Visio File | mcci_rm000100ht04.vsd |
Visio XML File | mcci_rm000100ht04.xml |
Hierarchical Message Description (HMD) | |
Schema | mcci_mt000100ht04.xsd |
Model Interchange Files (MIF) | mcci_mt000100ht04.mif |
Contents Previous Next Conformance Examples |
Copyright © 2018, Oracle. All rights reserved. |
About Oracle Contact Us Legal Notices and Terms for Use Privacy Statement |