PR for default config:

Test scenarios on http://product-qa04.mybahmni.org

Setup

1. Follow WIKI doc and setup Modality and Order type in “bahmni_pacs” database

2. Mapped procedure codes following WIKI - mapped for - Chest PA, Chest AP, and Neck Soft tissue XRays

3. Set up DCM4CHEE modality worklist by updating HL7Service ORM through JMX-Console, following WIKI

Steps

1. Create a patient “Suzie Q” and order the 3 radilogy tests above

2. Check in DCM4CHEEE modality worklist and verified 3 accessions created

3. Upload image

   1. Followed WIKI to download DCM4CHEE binaries (mainly to get DCMSND command)

   2. Downloaded “pacssimulator-1.0.0-jar-with-dependencies.jar” from source mentioned in WIKI

   3. Followed instructions of “upload dicom file directly to DCM4CHEE” and generated 2 dicom files for ORD-308 and ORD-310 (Chest PA & Soft tissue neck).

   4. Followed instructions in the WIKI above and used DCMSND command to upload 2 dicom files generated in the above process for accessions for Chest PA and Soft Tissue neck. No dicom uploaded for “Chest AP”

4. Verified images from oviyam viewer directly - https://product-qa04.mybahmni.org/oviyam2/

   1. Oviyam renders the 2 studies and images correctly. Clicking on the image opens up detailed view of the studies.

   2. Verified on DCM4CHEE “Folder” tab to list the 2 studies

5. Verified Oviyam upgraded to 2.8.1 (Earlier 2.1.x)

6. Verified integration from patient dashboard

   1. Clicking on a specific order on PACS display control - still shows up an incorrect image

      1. opens up URL - /oviyam2/viewer.html?patientID=GAN203006&accessionNumber=ORD-308

      2. The above is a bug thats fixed in the upcoming OVIYAM 2.8.2+

         1. check https://groups.google.com/g/dcm4che/c/4shTD-WzdEo

   2. Modify app config

      1. edited /var/www/bahmni_config/openmrs/apps/clinical/dashboard.json and edited control “pacs” and changed config param “pacsImageUrl” to "/oviyam2/oviyam?patientID={{patientID}}&accessionNumber={{orderNumber}}". Note this is the new URL thats supported in the upcoming fix and also in Oviyam2.8.x

   3. Clicked on the the order that has no study - it correctly opened up the URL https://product-qa04.mybahmni.org/oviyam2/oviyam?patientID=GAN203006&accessionNumber=ORD-309 .. matching the configuration set above. No image is displayed - correct behavior as image was uploaded. Note, in case a study was found with the above URL and parameters, new oviyam (upcoming version with the OV-241 fix) will redirect to URL with studyUID, otherwise it will show a blank screen.

      1. the above no-study order, shows a message on screen “Unable to identify study for the order..”

7. Test with new configuration on OMRS to use pacsquery module:

   1. In OMRS Settings, update Pasquery.”Pacs Config” to DCM4CHEE@localhost:11112

   2. Reload the patient dashboad, clicking on ORD-308 (Chest PA) and ORD-310 (Neck Soft tissue) shows the right images. Verified the studyUID matching with the link opened up directly from oviyam viewer.

   3. Clicking the ORD-309 (Chest AP) for non-existent study showed a blank page (courtesy changed “pacsImageUrl” config in app config)

Conclusion:

1. Worked as expected with the “PacsQuery.Pacs Config” settings, barring the non-existent study case.

Expectations:

1. The default “pacsImageUrl” in app config should reflect the new URL pattern. A blank screen is better than invalid study being shown.

PR:

The above PR is for the case when oviyam sends a redirect URL (in case of searching by accessionNumber) and because oviyam sees the connection coming as over http (apache acting as reverse proxy). This results in browser throwing up error because of same origin policy for ajax request

Bahmni Package PR:

openmrs-distro dependency PR:

(should be cherry-picked onto master). - DONE.