HDR Version 7 HL7 Version 3 Messaging Conformance Specification

Appendix A: HDR Messaging Schemas

HDR Version 7 release includes messaging schemas for all Oracle published Message Types. Messaging schema includes the following for each Message Type:

XML Schema Definition (XSDs)
Model Interchange Format files ( MIF files)
Composite Message Schema (CMS) for Each Supported/Published Interaction ID

In addition, a messaging schema contains a common Vocabulary Schema and datatypes Schema for all Message Types.

XML Schema Definition

This definition is a set of rules to which an XML document must conform in order to be considered valid according to that schema. The XSDs released in HDR Version 7 corresponds to the Oracle published artifacts as listed in Section 3, 4 and 5. For each artifact—CMET, Message Payload, Wrappers, there is a corresponding XSD that defines the structure and fixed/default content of a conformant XML instance.

Model Interchange Format Files

This model defines a series of schemas for XML files that will hold the content of HL7 V3 specifications. For each XSD released in HDR Version 7, there is a corresponding MIF file that has the HL7 V3 specifications.

Composite Message Schema for Each Supported/Published Interaction ID

This schema has 3 parts: Message Wrapper, ControlAct Wrapper and Message Payload. The number of CMS supported per Message Type depends on the number of Interaction ID supported for that Message Type.

Naming Convention

For a specific message type, the corresponding XSD file is named by simply appending a .xsd extension to the Message Type name. MIF file names are generated in a similar fashion with a .mif extension added to the Message Type name.

To locate the Messaging schemas required to generate a message, do the following.

For example Interactions supported for Result Event

1. Review Section 4 to open Result Event Message Type page.
2. Refer to Section 4.24.4 to determine the list of supported Interactions
3. Pick an interaction. For example, POLB_IN004102– Activate Result Event

Locate the messaging schemas that correspond to the above Message Type. This is done by prefixing the location path and appending .xsd to the Message Type names and the InteractionID names

For POLB_IN004102, these are:

• $JAVA_TOP/oracle/apps/ctb/message/defs/rim214101/schemas/polb_mt004000ht01.xsd
• $JAVA_TOP/oracle/apps/ctb/message/defs/rim214101/schemas/ POLB_IN004102 .xsd

For detailed information on Oracle supported Message Types, refer to Message Domains.

Note that the following attributes in the messaging schemas are never generated by OMP services. They are not supported by RIM Services.

• nullFlavor
• realmCode
• templateId
• typeId

Tools

The Implementation Technology Specification (ITS) tooling files, that are used by Oracle to generate schema (XSD) and MIF files for the message types and CMETs, are following:

datatypes.xsd
datatypes-base.xsd
voc.xsd

Top