· Mar 11, 2020

Working DICOM Worklist Production


We are trying to use Ensemble as a Router for DICOM Worklist. So when a DICOM Client sends a request (ECHO Or C-FIND), We want Ensemble to carry such request to Epic EMR. When Epic EMR responds with a Response, We need to be able to forward that response back to DICOM Client. I wanted to see If anyone has a working example of this scenario. 

Examples we have in DEMO namespace are not entirely falling into this scenario.

Discussion (2)1
Log in or sign up to continue

I have implemented a dicom worklist service with integration to our RIS system.

I would advice you against a 1:1 messaging back to Epic though. Here is why:

- many Modalities request worklists very frequently, so the workload or latency to Epic side might become a limiting factor
- modalities share several study rooms/resources and that modality/resource mapping might not be available in Epic (I could be wrong here)

In stead, how I did it was to attach the dicom service to our RIS’s event handler mechanism which would send a Soap call upon any changes of a study status and describing details of the study to the dicom service. The dicom service would then store/update the relevant details of the study internally, so when the modality requests a worklist, the service already has all the data and does not have to request it from somewhere else. The dicom service also holds mapping between resources, modality AET’s and provides an UI to maintain that.