Use the built-in patterns to integrate applications that use HL7 v2 messages.
A built-in pattern is a pattern that covers a set of commonly encountered message flow scenarios and that is packaged and released with WebSphere® Message Broker and WebSphere Message Broker connectivity packs.
The built-in patterns that are supplied in IBM® WebSphere Message Broker Connectivity Pack for Healthcare are shown in the following table.
You can view patterns in the information center by using the links only when you use the information center that is integrated with the IBM WebSphere Message Broker Toolkit, or when you use the online information center.
Pattern name | Description |
---|---|
Healthcare: HL7 to HL7 DFDL | The Healthcare: HL7 to HL7 pattern
integrates an application that can send HL7 (version 2.7, 2.6, 2.5.1
or earlier) messages to one or more applications that can receive HL7 messages. The applications
must be able to send and receive the messages by using MLLP over TCP/IP. You can monitor the pattern by using operational monitoring, see Monitoring clinical applications. Note: This pattern uses the DFDL message model
|
Healthcare: HL7 to HL7
Note: This pattern was made available in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7 and is still available
and supported in IBM WebSphere Message Broker Connectivity Pack for Healthcare version
8. However, it is recommended that you use the Healthcare:
HL7 to HL7 DFDL pattern instead
if possible. The Healthcare:
HL7 to HL7 DFDL pattern
uses the DFDL message model instead
of MRM and the HL7v25P
message set. The DFDL message model has the following
benefits.
|
The Healthcare: HL7 to HL7 pattern
integrates an application that can send HL7 (version 2.5.1 or earlier)
messages to one or more applications that can receive HL7 messages. The applications
must be able to send and receive the messages by using MLLP over TCP/IP. You can monitor the pattern by using operational monitoring, see Monitoring clinical applications. Note: This pattern
uses MRM and the HL7v25P
message set
|
Healthcare: Medical Devices to EMR | The Healthcare: Medical Devices to EMR pattern integrates
medical devices with an Electronic Medical Record (EMR) application
that can receive HL7
(version 2.5.1 or earlier) observation result messages (ORU R01).
The application must be able to receive HL7 ORU R01 messages by using
MLLP over TCP/IP. You can monitor the pattern by using operational monitoring, see Monitoring clinical applications. Note: This pattern uses MRM and the HL7v25P
message set
|
Healthcare: HL7 to Reports | The Healthcare: HL7 to Reports pattern integrates
an application that can send HL7
(version 2.5.1 or earlier) messages with report generation. The source
application must be able to send and receive HL7 messages by using MLLP
over TCP/IP. You can monitor the pattern by using operational monitoring, see Monitoring clinical applications. Note: This pattern uses MRM and the HL7v25P
message set
|
Healthcare: Web Service to DICOM | The Healthcare: Web service to DICOM pattern integrates
an application that is written using web services with DICOM applications that support
C-FIND and C-MOVE operations. You can use the pattern to query patients,
studies, series, and images from a DICOM PACS using a web service
that is implemented by WebSphere Message Broker You can monitor the pattern by using operational monitoring, see Monitoring clinical applications. |
For more information about using patterns, see Developing message flow applications by using patterns in the WebSphere Message Broker documentation.