What's new in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8?

Learn about the new capabilities and enhancements in IBM® WebSphere® Message Broker Connectivity Pack for Healthcare version 8.

IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 provides the following new capabilities and enhancements:

DICOM image integration

DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting medical image information. The information can include DICOM images and DICOM Structured Reports (SR).

You can use IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8.0 to connect DICOM PACS (Picture Archiving Communication Systems) and other DICOM modalities to message flows so that you can locate, process, and route DICOM images across a healthcare system.

Use cases
The DICOM capability that is provided by IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 supports a number of key scenarios.
  • Collect studies for patient admission: When a patient is admitted to hospital, you can query DICOM PACS that are in one or more locations to find and retrieve any studies (sets of DICOM images) for the patient. The relevant medical images are then immediately available to the clinical staff who are treating the patient. For more information about this scenario, see Collect studies for patient admission.
  • Second opinion or expert referral: In locations where radiology skills are limited, you can route DICOM images (for diagnosis or research purposes) to specialists in other hospitals in a healthcare system. For more information about this scenario, see Second opinion or expert referral.
  • Clinical portal: You can use a web application to display details of a patient's DICOM studies. In this scenario, only the attributes of the study (not the image data) are presented, for example, the modality and the date and time of the study. For more information about this scenario, see Clinical portal. This scenario is also implemented in the Healthcare: Web service to DICOM pattern.
New nodes: DICOMInput, DICOMOutput, and DICOMFindMove
IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 includes three new nodes.
  • The DICOMInput node, which you can use to receive DICOM images from a DICOM SCU (Service Class User) node, for example a DICOM modality. By using this node, you can extract data from a DICOM image for use in a message flow. This node supports DICOM C-STORE requests. For more information about this node, see DICOMInput node.
  • The DICOMOutput node, which you can use to send DICOM images to a DICOM SCP (Service Class Provider) node, for example a DICOM PACS. By using this node, you can combine metadata from a message flow with a DICOM image and send the result to an external destination. This node supports DICOM C-STORE requests. For more information about this node, see DICOMOutput node.
  • The DICOMFindMove node, which you can use to query an external source for DICOM images that match given criteria and optionally move the DICOM images to another location. This node supports DICOM C-FIND and C-MOVE requests. For more information about this node, see DICOMFindMove node.
Note: The DICOM capability that is provided by the IBM WebSphere Message Broker Connectivity Pack for Healthcare does not support DICOM C-GET requests.
For more information about using DICOM nodes in message flows, see Using data from DICOM images in message flows.
New pattern: Healthcare: Web service to DICOM pattern

IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 includes a new pattern that you can use to integrate an application that is written by 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 by using a web service that is implemented by WebSphere Message Broker.

DFDL message model

DFDL (Data Format Definition Language) is a universal, shareable, non-prescriptive description for general text and binary formats, which is used in WebSphere Message Broker (version 8 and later) to define message models. For more information about the use of DFDL in message models, see Message models in the WebSphere Message Broker documentation.

DFDL message model
IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 includes a new message model that is based on DFDL. The DFDL message model has a number of advantages over MRM and the HL7v25P message set, which are used in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7.0.
  • DFDL is an open-standard format whereas MRM and the HL7v25P message set are proprietary to WebSphere Message Broker.
  • The DFDL editor provides simpler tools for developing and testing extensions to the HL7 schema compared to MRM and the HL7v25P message set.
  • The DFDL message model supports HL7 versions 2.7, 2.6, 2.5.1 and earlier whereas MRM and the HL7v25P message set only support HL7 version 2.5.1 and earlier.
Note: MRM and the HL7v25P message set that are available in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7.0 are still supported and available for applications that were developed in earlier releases of IBM WebSphere Message Broker Connectivity Pack for Healthcare. Because of the benefits of the DFDL message model, it is recommended that the DFDL message model is used for new and updated applications if possible. However, there are situations when you might still want to use the HL7v25P message set. For example, if you convert data from the HL7v2 non-XML standard to an XML representation by using the HL7v25P message set, you do not have to rename the elements of the message tree.

New nodes: HL7DFDLInput and HL7DFDLOutput
Two new HL7 nodes, which use the DFDL message model, are provided for you to use in your message flows to send and receive HL7 messages.
  • HL7DFDLInput (an updated version of GenericHL7Input), which you can use in a message flow to receive HL7 messages. For more information about this node, see HL7DFDLInput node.
  • HL7DFDLOutput (an updated version of GenericHL7Output), which you can use to pass messages to a destination over MLLP and to check that a valid acknowledgment is received. For more information about this node, see HL7DFDLOutput node.
Note: The GenericHL7Input and GenericHL7Output nodes, which are available in IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7.0, are still available in version 8. However, because of the benefits of the DFDL message model, it is recommended that the HL7DFDLInput and HL7DFDLOutput nodes are used in new and updated applications if possible.

New pattern: Healthcare: HL7 to HL7 DFDL pattern

IBM WebSphere Message Broker Connectivity Pack for Healthcare includes an updated version of the Healthcare: HL7 to HL7 pattern that is available with IBM WebSphere Message Broker Connectivity Pack for Healthcare version 7. The new pattern performs the same functions as the original pattern but the Healthcare: HL7 to HL7 DFDL pattern uses the DFDL message model and the HL7DFDLInput and HL7DFDLOutput nodes instead of MRM, the HL7v25P message set, and the GenericHL7Input and GenericHL7Output nodes.

ATNA audit repository integration

The ATNA (Audit Trail and Node Authentication) Integration Profile is defined by IHE (Integrating the Healthcare Enterprise). The ATNA Integration Profile defines the standards and processes for securely routing and storing audit event messages in a repository. IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 provides the capability to generate relevant ATNA audit event messages from the healthcare data that is routed through message flows, and to send these messages to a specified ATNA audit repository. For more information, see Auditing data from message flows.

New node: ATNAAudit node
A new node, ATNAAudit is provided, which you can add to your message flows to generate ATNA audit event messages and route them to an ATNA audit repository. For more information about the ATNAAudit node, see ATNAAudit node.

Healthcare data analysis

You can use the WebSphere Message Broker Data Analysis perspective with a Data Analysis profile provided by IBM WebSphere Message Broker Connectivity Pack for Healthcare version 8 to analyze and filter healthcare data in your message flows. Healthcare data is often carried in complex documents and messages that are not easily processed by downstream applications. Using a Data Analysis project, you can analyze healthcare data, extract key elements, and create a simplified message structure that can be mapped directly into the database tables that are used by business intelligence tools.
Four Data Analysis profiles:
IBM WebSphere Message Broker Connectivity Pack for Healthcare provides four Data Analysis profiles. Each profile is used for a specific type of healthcare data.
  • The HL7 v2 (ORU) profile is used for analyzing ORU (Observation Result) message data
  • The HL7 CDA profile is used for analyzing CDA (Clinical Document Architecture) documents
  • The HL7 v2 profile is used for analyzing otherHL7 data
  • The DICOM profile is used for analyzing DICOM data

For more information about analyzing healthcare data, see Analyzing healthcare data in message flows.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 2011, 2013Copyright IBM Corporation 2011, 2013.

        
        Last updated
        
        Last updated : 2013-03-18 14:26:52


Concept topicConcept topic | Version 8.0.0.0 | ha00005