Ensemble DICOM Development Guide
Sample DICOM Routing to Storage Production
namespace contains a production named Demo.DICOM.Production.Storage
. This production demonstrates a basic DICOM function, sending an image from a modality to a RIS or PACS system for storage.
The scenario for this production is a DICOM modality sending a request message to send a document to a storage system. The production does the following:
The DICOM modality establishes an association with Ensemble and sends a C-STORE request message to the production through the duplex business service.
The Ensemble business process checks the connection to the output storage system and establishes the association if needed.
Ensemble recognizes the request, stores the originating message ID, and forwards the DICOM document message to the storage system through the duplex business operation.
The business operation returns the C-STORE response message from the storage system to the business process.
Ensemble sends the response message back to the modality with the originating message ID.
The following steps outline the procedure to add this type of interface to a production:
Create a business process class
that routes the incoming DICOM document to a storage system from the incoming C-STORE-RQ message and passes the returned C-STORE-RSP message back to the originating system.
Test the production
to verify that it receives a request message for a worklist and sends the appropriate response message documents back.
Duplex Target Config Names
Specify the configuration item within the production to which the business service should send any DICOM documents that it receives.
The called Application Entity Title (AET) that the remote DICOM peer uses to communicate with Ensemble. This corresponds to the Called AET
you use when defining an association in an Ensemble namespace.
When you run the Demo.DICOM.Production.Storage
production for the first time, it creates the DICOM association necessary for Ensemble to connect to a test DICOM application for this demonstration production. You can view this association in the ENSDEMO
namespace from the DICOM Settings
The calling Application Entity Title(s) of a remote DICOM peer.
When the adapter is in the role of Service Class Provider (SCP, server) it contains a comma-delimited list of names of the DICOM peers which are allowed to connect. A name can either be a literal string or a pattern/substitution.
Because of the duplex nature of DICOM communication, the business process must keep track of what is happening outside of the process. You can accomplish this using a context variable for the state
of the process. The demonstration business process creates a CurrentState
property for this purpose.
Once you have working associations and created a production, you can attempt to process valid DICOM message documents through the production. The demonstration production included with Ensemble was developed using third-party software specifically developed for testing DICOM processing. You can use any of the many available software products, or test with your actual DICOM modality data.
© 1997-2019 InterSystems Corporation, Cambridge, MA