Hi,
I’m having a bit of a time trying to get the Orthanc OHIF plugin to be case insensitive for patient name filtering in the studies list.
For testing purposes, I have a test study with a patient name “Test, Tester” uploaded w/ S3 storage backing this.
My orthanc.json config has “Dicomweb”: { “QidoCaseSensitive”: false } set and also “OHIF” : { “DataSource” : “dicom-web” } set (which is default?)
I’ve primarily been testing with jodogne/orthanc-plugins:1.12.8, but also today with 1.12.9
When searching/filtering on “test” in the OHIF Study List, it yields no results, but “Test” will display the entry.
Looking a bit more at the traffic, when searching/filtering for Patient Name “test” from OHIF, the Orthanc “/dicom-web/studies?PatientName=test…” endpoint is indeed returning the JSON with the result correctly (“Test Tester”) to OHIF, but OHIF is not showing it in the study list UI.
I came across this thread:
If I do a browser override of app-config.js (this is the only way I could figure out how to influence the variable) and set staticWado: false -then- OHIF displays the result that was returned from Orthanc when filtering on patient name “test” or “Test”/etc which is what I want. It now seems case-insensitive.
Since orthanc-ohif: f185306d615f Sources/app-config-system.js is appended at the end of app-config.js with staticWado: true hardcoded, I don’t know how to get this to work as the value cannot be set in the file “OHIF” { “UserConfiguration”: “ohif.js” } because the plugin’s hardcoded config is appended after the contents of ohif.js to generate the app-confg.js response.
If staticWado: true is indeed required, are there other settings I’m missing to get this to work as expected? I tried setting supportsFuzzyMatching : true, which is hardcoded as well, but that seemed cause even less functional filtering.
Thanks!