HL7 Classes
For reference, this page lists the classes that InterSystems provides to enable you to work with HL7 Version 2 documents.
Each of these HL7 business service classes uses a different adapter, as indicated by the class name. The HL7 HTTP service can either use the CSP port or a special port.
EnsLib.HL7.MsgRouter.RoutingEngineOpens in a new tab
This class is a specialized version of the standard virtual document routing process.
Each of these HL7 business operation classes uses a different adapter, as indicated by the class name.
EnsLib.HL7.MessageOpens in a new tab
This is a specialized message class to carry HL7 documents as virtual documents.
EnsLib.HL7.SearchTableOpens in a new tab
This is a specialized search table class for HL7 documents.
You can also create and use subclasses of these classes.
The business host classes include configurable targets. The following diagram shows some of them:
For information on other configurable targets, see Reference.
Details on the HL7 Message Class
InterSystems products provide a built-in class for HL7 Version 2 virtual documents. The class is EnsLib.HL7.MessageOpens in a new tab. For basic information on virtual document message classes, see Virtual Document Classes. In addition to the basic properties and methods, EnsLib.HL7.MessageOpens in a new tab provides the following properties:
The TypeCategory property contains an HL7 category name. Typically, the HL7 business service that receives HL7 data instantiates an HL7 message and assigns a TypeCategory value to it. The production combines this TypeCategory with the message type declared in the MSH segment of the incoming message data; this combination identifies a <MessageType> within the HL7 schema definition. This <MessageType> has an associated <MessageStructure> that InterSystems uses as the DocType for the HL7 message, if no other DocType is assigned.
The Name property is a read-only string that contains the HL7 message structure name (such as ADT_A08 or ORM_O01) that the external data source has provided in the MSH segment. The Name can be useful in determining the HL7 message structure that the clinical application thinks that it is sending, although this can differ from the actual message contents.
