I am sort of a hobbyist and developer, now somewhat interested in Orthanc.
Just wondering how the MWL feature, https://book.orthanc-server.com/plugins/worklists-plugin.html
Documented for Orthanc would work with an MRI scanner. I have Horos and Osirix, so I guess I could test with that, but I would want to use it with a DICOM acquisition device if that is how it is suppose to work. I already have HOROS set up on a dev server to work with AMBRAHEALTH through their gateway and I can query retrieve exams, so it should be similar with Orthanc.
Can a scanner/device be added just by adding another entry, like “mri_main” : [ “MRI_MAIN”, “192.168.0.2”, 104 ] ?
to:
"DicomModalities" : {
"horos" : [ "HOROS", "192.168.0.8", 11112 ],
"findscu" : [ "FINDSCU", "127.0.0.1", 1234 ]
},
And then can I just dynamically generate worklist files and update them for Orthanc to use ? If so, which entries are dynamic ? Is the Meta Information always the same ?
It looks like the Data-Set is all dynamic except for maybe the CharacterSet. How is a StudyInstanceUID generated ?
# Dicom-File-Format
# Dicom-Meta-Information-Header
# Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 202 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI [1.2.276.0.7230010.3.1.0.1] # 26, 1 MediaStorageSOPClassUID
(0002,0003) UI [1.2.276.0.7230010.3.1.4.2831176407.11154.1448031138.805061] # 58, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =LittleEndianExplicit # 20, 1 TransferSyntaxUID
(0002,0012) UI [1.2.276.0.7230010.3.0.3.6.0] # 28, 1 ImplementationClassUID
(0002,0013) SH [OFFIS_DCMTK_360] # 16, 1 ImplementationVersionName
# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0050) SH [00000] # 6, 1 AccessionNumber
(0010,0010) PN [VIVALDI^ANTONIO] # 16, 1 PatientName
(0010,0020) LO [AV35674] # 8, 1 PatientID
(0010,0030) DA [16780304] # 8, 1 PatientBirthDate
(0010,0040) CS [M] # 2, 1 PatientSex
(0010,2000) LO [METASTASIS] # 10, 1 MedicalAlerts
(0010,2110) LO [TANTAL] # 6, 1 Allergies
(0020,000d) UI [1.2.276.0.7230010.3.2.101] # 26, 1 StudyInstanceUID
(0032,1032) PN [SMITH] # 6, 1 RequestingPhysician
(0032,1060) LO [EXAM6] # 6, 1 RequestedProcedureDescription
(0040,1001) SH [RP454G234] # 10, 1 RequestedProcedureID
(0040,1003) SH [LOW] # 4, 1 RequestedProcedurePriority
If that is capable of receiving queries from an MRI and responding with the worklist that would be awesome.
Are there hooks from a PHP web App to some of Orthanc commands such that worklists could be created via the PHP web app.
i.e. The web app maintains the database of orders and patients, so I could pretty easily create text files that have most of the information above. Not sure about how to generate a StudyInstanceUID, but here must be some standard and simple way to do that.
My understanding is that acquisition devices can query the DICOM server and basically get a "pick list" for scheduled exams such that no or minimal entry of data is required.
AMBRA'S orders with an MWL entry have something like this. I presume that that is similar to what is shown above, except there is no date in the example above ? The StudyInstanceUID looks kind of like their study_uid.