Failure to retrieve Modality and ScheduledProcedure from dicomserver.co.uk worklist

[Toeger]

I'm running the following command with the given result:

Code: Select all

$ ./findscu.exe www.dicomserver.co.uk 104 -k 0010,0010=Bowen^William -k 0010,0040 -k 0008,0060 -k 0040,4005
I: ---------------------------
I: Find Response: 1 (Pending)
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0010,0010) PN [Bowen^William^^Dr ]                     #  18, 1 PatientName
I: (0010,0040) CS [M ]                                     #   2, 1 PatientSex
I:
I: ---------------------------
I: Find Response: 2 (Pending)
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0010,0010) PN [Bowen^William^^Dr ]                     #  18, 1 PatientName
I: (0010,0040) CS [M ]                                     #   2, 1 PatientSex
I:
I: ---------------------------
I: Find Response: 3 (Pending)
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0010,0010) PN [Bowen^William^^Dr ]                     #  18, 1 PatientName
I: (0010,0040) CS [M ]                                     #   2, 1 PatientSex
I:

I queried the keys patient name (0010,0010), patient sex (0010,0040), modality (0008,0060) and scheduled procedure step start date time (0040,4005). I successfully retrieved the patient name and patient sex, but failed to retrieve the modality and scheduled procedure time. The worklist's web interface shows the modality and scheduled procedure data I'm trying to obtain: https://www.dicomserver.co.uk/Home/MWLTestData

Is this a defect in the worklist server or findscu?
Is there a workaround?
Can someone with access to a different worklist server confirm that findscu prints the modality and scheduled procedure data if the worklist server provides it?

Thanks.

[Michael Onken]

Hi,

That's a classic Some attributes are within the Scheduled Procedure Step Sequence (0040,1000), and your request must reflect that.

Try:

Code: Select all

./findscu.exe www.dicomserver.co.uk 104 -k 0010,0010=Bowen^William -k 0010,0040 -k 0040,0100[0].0008,0060 -k 0040,0100[0].0040,4005

Besides that, you probably want to query Scheduled Procedure Step Start Date and Scheduled Procedure Step Start Time explicitly Instead of the DateTime attribute):

Code: Select all

./findscu.exe www.dicomserver.co.uk 104 -k 0010,0010=Bowen^William -k 0010,0040 -k 0040,0100[0].0008,0060 -k 0040,0100[0].0040,0002 -k 0040,0100[0].0040,0003

See dcmodify help page for how this "path syntax" for the sequences works, if you are curious.

BR,
Michael

[Toeger]

Thanks, I can now get the data successfully.
Is there a trick to know what is in what? Ideally something that given any DcmTagKey will tell what group it is in, if any.
I looked at DcmTagKey::getBaseTag, DcmTagKey::hasValidGroup and DcmTagKey::getGroup, but those are not enough to distinguish them:
DCM_AccessionNumber (not part of DCM_ScheduledProcedureStepSequence): (0008,0050), true, 8
DCM_Modality (part of DCM_ScheduledProcedureStepSequence): (0008,0060), true, 8

[J. Riesmeier]

What about reading the relevant parts of the DICOM standard? For example, Table K.6-1 in Part 4: https://dicom.nema.org/medical/dicom/cu ... able_K.6-1

findscu is a low-level tool that allows you to specify both valid and invalid queries (for the respective Information Model).