Developing healthcare integration solutions by using the patterns supplied in IBM Integration Bus Healthcare Pack
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 IBM® Integration Bus and IBM Integration Bus connectivity packs.
The built-in patterns that are supplied in IBM Integration Bus Healthcare Pack are shown in the following table.
You can view patterns in the documentation by using the links only when you use the documentation that is integrated with the IBM Integration Toolkit, or when you use the online documentation in the IBM Knowledge Center.
Clinical patterns
| Pattern name | Description |
|---|---|
| Healthcare: HL7 Transformation | The Healthcare: HL7 Transformation pattern generates
graphical data maps that you can use to assemble HL7
messages. Note: This pattern uses the DFDL message model.
|
| Healthcare: HL7 to HL7 DFDL | The Healthcare: HL7 to HL7 DFDL 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 Healthcare: HL7 to HL7 DFDL pattern by using web-based monitoring. See Web-based monitoring. 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.0 and
is still available and supported in this version of IBM Integration Bus Healthcare
Pack. 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 Healthcare: HL7 to HL7 pattern by using web-based monitoring. See Web-based monitoring. 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 Healthcare: Medical Devices to EMR pattern by using web-based monitoring. See Web-based monitoring. 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 IBM Integration Bus. You can monitor the Healthcare: Web service to DICOM pattern by using web-based monitoring. See Web-based monitoring. |
| Healthcare: Home Health | The Healthcare: Home Health pattern enables your
health systems to accept web service requests from HL7 v2.6 compliant devices. This allows data that
Home Health devices collect and send to the Application Hosting Device (AHD) to then be sent to the
requesting clinical application. This pattern uses the DFDL message model. You can monitor the Healthcare: Home Health pattern by using web-based monitoring. See Web-based monitoring. Note: This pattern uses the DFDL message model.
|
| Healthcare: HIPAA to XML | The Healthcare: HIPAA to XML pattern creates a
messages flow that you can use to convert HIPAA files to XML files. You can monitor the Healthcare: HIPAA to XML pattern by using web-based monitoring. See Web-based monitoring. Note: This pattern uses
the DFDL message model.
|
| Healthcare: Patient Identifier Cross-reference Manager | The Healthcare: Patient Identifier Cross-reference Manager pattern enables
you to create a Patient Identifier Cross-reference Manager that you
can use as part of the IHE PIX profile. You can monitor the Healthcare: Patient Identifier Cross-reference Manager pattern by using web-based monitoring. See Web-based monitoring. Note: This pattern uses the DFDL message model.
|
| Healthcare: Patient Demographics Query Supplier | The Healthcare: Patient Demographics Query Supplier pattern enables you to
create a Patient Demographics Supplier that you can use as part of the IHE PDQ profile. You can monitor the Healthcare: Patient Demographics Query Supplier pattern by using web-based monitoring. See Web-based monitoring. Note: This pattern uses
the DFDL message model.
|
| Healthcare: Cross-Enterprise Document Sharing Consumer | Use the Healthcare: Cross-Enterprise Document Sharing Consumer pattern to find document Unique Universal Identifiers
(UUIDs) stored in an XDS registry and then use the UUID to retrieve those documents from the XDS
repository. You can monitor the Healthcare: Cross-Enterprise Document Sharing Consumer pattern by using web-based monitoring. See Web-based monitoring. |
| Healthcare: FHIR Transformation | Use the Healthcare: FHIR Transformation pattern to transform
HL7 FHIR resources between XML and JSON formats. The HL7 FHIR standard is a Draft Standard for Trial
Use (DSTU), rather than a full normative specification. You can monitor the Healthcare: FHIR Transformation pattern by using web-based monitoring. See Web-based monitoring. |
For more information about using patterns, see Developing integration solutions by using patterns in the IBM Integration Bus product documentation.