The Healthcare: Medical devices to EMR pattern integrates medical devices with an Electronic Medical Record (EMR) application that can receive Health Level Seven International (HL7) v2 observation result messages (ORU R01). The application must be capable of receiving HL7 ORU R01 messages by using Minimal Lower Layer Protocol (MLLP) over TCP/IP.
Note: This pattern was made available in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7 and is still available and supported in version 8. However, this pattern still uses MRM and the HL7v25P message set instead of the DFDL message model that is introduced with IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8. The DFDL message model is recommended for new and updated applications because it has the following benefits:
You must deploy the HL7 message set to your integration node before deploying a pattern instance. The message set is used to parse HL7 messages as they are processed by the message flows. Message flows generated by the pattern cannot be deployed to your integration node until the message set has been deployed.
You can import the HL7 message set into your workspace from the Resources for the pattern page.
The HL7 message set takes a long time to build and can significantly slow down your workspace - you are therefore recommended to do the following:
If you want to use the Graphical Mapper for message transformations, you will need to leave the HL7 message set in your workspace. You can reduce the time it takes to build the message set by deleting the HL7 chapters from the message set. Leave the segments.mxsd , fields.mxsd and datatypes.mxsd message definition files in the message set as they are required by the pattern.
If you are using database lookups for patient identification and configure the pattern instance to create a web service, then you must import and deploy the PatientIdentifiersService message set. The SOAP nodes in the web service flow require this message set as it contains the WSDL file. This message set and also a message set which models the measurements from the MedicalDeviceInput node are available from the Resources for the pattern page.
The MedicalDeviceInput node message set can be used with the Graphical Mapper for message transformations of device messages. Make sure you set the target parser to be DataObject for the output message in the Graphical Mapper because it defaults to XMLNSC. This pattern expects all device messages to be in the DataObject domain and will not work correctly if you use XMLNSC.
The Medical Devices flow in this pattern supports the following options:
The Transform and Route flow in this pattern supports the following options:
The Sender flow in this pattern supports the following options:
This pattern can optionally generate a web service to manage the patient identifiers database:
All the message flows generated by this pattern handle exceptions by using queues to store the error information.