Using data from DICOM images in message flows

Use DICOM nodes in a message flow to locate, process, and transfer DICOM images.

Before you start:

You can process and manage Digital Imaging Communications in Medicine (DICOM) images in a message flow by using a combination of one or more DICOMInput, DICOMOutput and DICOMFindMove nodes, which are included in IBM® WebSphere Message Broker Connectivity Pack for Healthcare. Use these nodes with the built-in nodes provided in WebSphere Message Broker to develop message flow applications that meet your requirements.

To use the data from DICOM images in message flows, complete the following steps:

  1. Collect connection information about any DICOM Service Class User (SCU) nodes that will access your message flow, and any DICOM Picture Archiving Communications Systems (PACS), or other DICOM Service Class Provider (SCP) nodes, that will be accessed by your message flow. This connection information includes the host name, port number, and Application Entity Title (AET).
  2. Create a message flow and add the appropriate DICOM nodes. For information about the DICOM nodes and their purposes, see DICOM nodes in message flows.
  3. Optional: If you are using a DICOMInput node in your message flow, create a configurable service to define the acceptable presentation contexts and transfer syntax groups that can be used to receive images from SCU nodes. See Configuring the presentation contexts accepted by a DICOMInput node.
  4. Complete your message flow. For more information about developing message flow applications, see Developing message flow applications in the WebSphere Message Broker documentation.

Next:

Test and debug your message flow application to verify that it functions correctly. See Testing and debugging message flow applications in the WebSphere Message Broker documentation.

Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated
        
        Last updated : 2013-03-18 14:27:05


Task topicTask topic | Version 8.0.0.0 | ha05050