Sample DICOM File Storage Production
The sample production named Demo.DICOM.Production.StorageFile demonstrates a basic DICOM function, sending DICOM documents from a file to a DICOM compatible storage system.
In this scenario, the production receives a file containing DICOM-formatted messages and sends those messages to a storage system. The production does the following:
An business service receives a file with the .dcm extension as input and sends the messages to the DICOM business process. The DICOM message documents contain C-STORE requests.
The business process checks the connection to the output storage system and establishes the association to the storage system if needed.
The production 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.
The following steps outline the procedure to add this type of interface to a production:
Create a generic production by clicking Create New Production on the Production Configuration page. See Creating and Configuring a Production in Configuring Productions.
In Studio, modify the production definition to add the StorageLocation property and compile the production. See Configuring a DICOM Production to Control the Storage Location for details.
Add a DICOM file business service to the production using the EnsLib.DICOM.Service.FileOpens in a new tab class.
Configure the DICOM business service settings specifically for a file storage production.
Create a business process class that routes the incoming DICOM document to a storage system from the incoming C-STORE-RQ message and returns the C-STORE-RSP message.
Add a DICOM business process using the custom class from the previous step.
Add a DICOM business operation to the production using the EnsLib.DICOM.Operation.TCPOpens in a new tab class.
Test the production to verify that it receives a storage request message for a DICOM document and sends the document to the storage system.
You can view the class code of Demo.DICOM.Production.StorageFile.cls using Studio to see the production details.
Configuring the DICOM Routing to Storage Business Service
You can configure a DICOM business service by clicking it in the diagram on the Production Configuration page. Configuring a DICOM Duplex Business Host describes the details. This section describes the settings specific to the business service in the demonstration storage production.
Specify the configuration item within the production to which the business service should send any DICOM documents that it receives.
The Demo.DICOM.Production.StorageFile production uses the business process based on the class, Demo.DICOM.Process.StorageFile. This is a custom process that contains the logic for processing DICOM messages from the input file and routing them to a storage system.
Full pathname of the directory in which to look for files. This directory must exist, and it must be accessible through the file system on the local system.
Filename or wildcard file specification for file(s) to retrieve. For the wildcard specification, use the convention that is appropriate for the operating system on the local system.
The Demo.DICOM.Production.StorageFile production uses *.dcm file extension.
Testing the DICOM File Storage Production
Once you have working associations and created a production, you can attempt to process valid DICOM message documents through the production. The sample DICOM demonstration production 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.
This section shows portions of the Event Log, Message Browser, Message Details, and Message Contents pages in the Management Portal of the Demo.DICOM.Production.StorageFile production running and accepting DICOM messages from a file and passing them to a storage system that supports store requests.