I have a modified version of some of the Osimis images up and running and establishing connectivity with an MRI scanner was pretty simple. Now, interested in getting the MWL queries from the scanner to the Orthanc server working.
In orthanc.json:
“ESAOTE” : { // long version
“AET” : “ScannerAET”,
“Port” : 104,
“Host” : “xxx.xxx.xxx.xxx”, // LAN IP
“Manufacturer” : “Generic”,
“AllowEcho” : true,
“AllowFind” : true,
“AllowMove” : true,
“AllowStore” : true
},
“FINDSCU” : { // long version ???
“AET” : “FINDSCU”,
“Port” : 1234,
“Host” : “127.0.0.1”,
“Manufacturer” : “Generic”,
“AllowEcho” : true,
“AllowFind” : true,
“AllowMove” : true,
“AllowStore” : true
}
and in Docker, Orthanc DICOM is listening on the host 4444, docker 4242. The scanner is able to send test studies to Orthanc without a problem, and the connectivity check on Orthanc is also fine in regards to the scanner.
From the CLI on the Host machine, which has dcmtk installed I can execute:
findscu -W 192.168.10.52 4444 -k AccessionNumber . . . . -k “ScheduledProcedureStepSequence[0].ScheduledProcedureStepID” -v -d
and get a valid response.
D: Response Identifiers:
D:
D: # Dicom-Data-Set
D: # Used TransferSyntax: Little Endian Explicit
D: (0008,0005) CS [ISO_IR 192] # 10, 1 SpecificCharacterSet
D: (0008,0050) SH [DEVACC00000001] # 14, 1 AccessionNumber
D: (0008,0060) CS [MR] # 2, 1 Modality
. . . . .
etc.
and
. . . .
D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type : C-FIND RSP
D: Message ID Being Responded To : 1
D: Affected SOP Class UID : FINDModalityWorklistInformationModel
D: Data Set : none
D: DIMSE Status : 0x0000: Success
D: ======================= END DIMSE MESSAGE =======================
I have the MWL plug-in installed, configured and enabled, with a sample MWL in the worklists folder.
Just wondering how to seup the FINDSCU and how the scanner should be setup to query the MWL ? Does it just issue a C-FIND using the AET and PORT configured in the .yaml for Othanc and the same as it uses to send studies to Orthanc, i.e. 4444, the LAN IP and an AET, or does it have to use a different AET and Port for that ? Have not had a chance to try it yet, but would like to be able to use that with the scanner. Not really sure how to configure the FINDSCU in orthanc.json or if that is necessary, and if so, what the IP there should be since it is running in a Docker Container.
Thanks.