The integration looks good! Here are my answer to your questions:
No problem
Not much, sorry… The ‘state.json’ file is a quick way to save presentation and roi data. DICOM provides ways of storing this kind of data too which would be more standard but I did not have time to look into it.
dwv uses the i18next library, it is initialised in the applauncher with ‘dwv.i18nInitialise()’ (dwv/i18n.js at master · ivmartel/dwv · GitHub) which detects the browser language and uses HTTP requests to fetch the appropriate translation files in the locales folder.
I see you use the ‘static’ viewer, just in case, you saw there were others in the viewers folder? Is it the one you plan to use? It is the first one I did, quite similar to desktop viewers so ok with a large screen to fit the boxes. For smaller screen I would advise to use the ‘mobile’ one.
@jodogne, you are rigth, Orthanc can use PostgreSQL, it’s opensource and have a very nice REST API. I was talking about personal reasons time ago to choose DCM4CHEE. Both are goods solutions and have my admiration. I´ll be happy with any desition, more if we count with skilled people like you in this integration.
Hi @MatthewVita - thanks for the working on the press release. I just saw this post and will try to get back to you as soon as possible with an action shot.
Quick note.
With the newly released 5.0.1, a Dicom file extension is no longer required to import images in Documents. Import will now read the image header to determine mime and add a required extension to complete upload if necessary. You are still required to zip views individual images for scrolling in viewer however, there is not a requirement for file extensions inside zip as upload will review and validate all images in archive.
I’ve tested as many as 85 views on all flavors of environments OpenEMR currently runs under with success.
Good viewing!
New user here, just poking around OpenEMR 5.0.1 features to see what can be done before diving into a migration out of practice fusion. We use Conquest as our pacs server. It is fed by an ancient Konica-Minolta CS-2 xray workstation. I tried to upload a DCM image from there, but got this: “Error: Unsupoorted DICOM transfer syntax: ‘1.2.840.10008.1.2.4.80’ (JPEG-LS).” Is this because my pacs is incompatible, or do I need to do something else in OpenEMR to make it work?
When I zip the .DCM file then upload it, the viewer just says 'Still Loading…" forever.
Our viewer appears to not support 1.2.4.80 (found the error exception in code for this xfer type). Also a quote I found on web says: “Despite being included in the DICOM standard for over a decade, its actual real world use is almost non-existent in PACS”. @MatthewVita or @kofiav may have further insight.
Ha! It’s probably non-existent because of its decrepitude. In another imaging forum, whenever I post a question about that CS-2 software the only answers I ever get are like, “You need to update that old software”
Getting off topic here, but maybe the right people are seeing these questions I have:
What’s better, CS-7 or ImagePilot? Our techs are not experts.
Does anyone know at what point the image format changes to Dicom? Is it on the Xray workstation or in the PACS? When I look on the workstation, I can only find what looks like raw images (*.IMG), but I can’t find any program that can deal with them. Sometimes CS-2 ‘loses’ studies. When it does, I need to use the built-in japanese utility program, “Mainte.exe” which only runs on Windows XP, to recover the images. Nothing else in the world I can find can read them.
We have two commercial pacs in my office and i have seen many other commercial pacs, only orthanc has this simple handful feature for phycisians.
With a simple html script in my webpage i have a box where put the patient id and then goes to all patient studies
I believe that adding a feature like this in openemr will very useful
I have no knowledge of programming and just reading the orthanc book i was able in 10 minutes to setup orthanc server in docker and following the instructions and examples in orthanc book to write the script in my webpage.
Connecting a patient in openemr with orthanc stone viewer with a simple button
in my opinon will give a fuctionality that no other system has, without any inputs from enduser.
