Hi @sscotti , In the initial spike that we did for getting the ability to view DICOM images in Bahmni Product we have tried Orthanc as well. When we tested Orthanc integration with one of our clients 3rd party software i.e ImageSuite, the X-Rays were synched to Orthanc server but they were not rendered properly. Thats when we stopped spiking around Orthanc and looked for other OpenSource DICOM web Viewers like Oviyam2. When Oviyam2 wasn’t able to retrieve X-Rays then we had to introduce DMC4CHEE as both are very well compatible(Both from same Organization).
All this is one phase when we worked with client with a Full fledged Sofrtware(Modality, PACS, WorkList server). The workflow looked as below.
- Order Xray - > Creates HL7 Order Message with order number as accession number (pacs-integration module of Bhamni) and sends it to ImageSuite(Which has worklist server)
- DCM4CHEE is configured at Imagesuite to get X-Rays automatically.
- View images using Oviyam2 (DICOM view URL made of Order Number) which in turn talks to DCM4CHEE.
The next phase is when we to integrate our Bahmni Product with a Vendor software without WorkList server at JSS. Then we started using the DCM4CHEE Worklist feature as well. The workflow now looked like
- Order Xray - > Creates HL7 Order Message with order number as accession number (pacs-integration module of Bhamni) and sends it to DCM4CHEE Worklist server
- The vendor software pulls the worklist from DCM4CHEE
- DCM4CHEE is configured at Vedor Software to get X-Rays automatically.
- View images using Oviyam2 (DICOM view URL made of Order Number) which in turn talks to DCM4CHEE.
We can separate Oviyam2 from DCM4CHEE but this option right now is not available in Bahmni installation package. We can manually do it.