Modality Worklist - What items are returned for a C-FIND sequence request?

My question is really the main question. Try requesting a modality worklist to get some work items as requested by C-FIND. Consider using the sequence ( SQ

) as the Return Key attribute for a query C-FIND

, for example: [0040,0100] (planned procedure step) and generic match.

What should I expect in SCP's response C-FIND

? Or, rather, what should I expect in relation to the planned procedure step for a particular work item? Any required elements that the Modality Worklist Information Model declares encapsulated in sequence? Do I have to explicitly issue a request C-FIND

for these keys, do I want SCP to return in response?

For example: if I want SCP to return the step-by-step start of the step step and the Start date of the scheduled procedure, do I need to send a specific request C-FIND

with these keys or request for the scheduled procedure Is the step key sufficient to force SCP to send all items related to the step of the planning step itself?

+3


source to share


2 answers


Yes, in the sequence 0040,0100 you must include the Start / Time Tag step tags on a schedule.

See also Technical data for class of service (K6.1.2.2)



This does not guarantee that you will receive this information, because it depends on the provider of the Modality worklist what information will be returned. You can also query the Dicom match expression from the modality provider to find out the required tags to request / receive.

+3


source


Regarding Table K.6-1, you can think of it as showing only the requirement of the SCP side, or that the SCP needs to be used to match a key (e.g. a query filter) and additional required attribute values ​​to return (i.e. a Return Key) with a successful match. Implementing SCP to maintain matching with the required key, but you can always expect SCP to use the values ​​in the appropriate key to filter requests.



Also note that SCP is only required to return the attribute values ​​present in the C-FIND request. One exception is sequence matching, and there you have a generic similar mechanism where you can pass a zero length ITEM to retrieve the entire sequence. So, as stated in PS 3.4.2.2.6, you can simply include an empty ITEM element (FFFE, E000) with VR SQ in the reference procedure steps (0040, 0100) for universal matching.

+1


source







All Articles