C-Find-RQ identifier? - DICOM

This is a discussion on C-Find-RQ identifier? - DICOM ; Hi, I am looking for information on C-find-RQ's identifer. What all does this include? From P.S.3.4 of the standard i came to know that the identifer includes key attribute values, query retrieve level, and conditional attributes. Can i have an ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: C-Find-RQ identifier?

  1. C-Find-RQ identifier?

    Hi,

    I am looking for information on C-find-RQ's identifer. What all does
    this include? From P.S.3.4 of the standard i came to know that the
    identifer includes key attribute values, query retrieve level, and
    conditional attributes.

    Can i have an example of this?

    is there any end tag for this identifier?

    Thank you for your time in advance.

    regards,
    Rajesh Rapaka.


  2. Re: C-Find-RQ identifier?

    Hi Rajesh,
    In order to understand the dataset of C-Find Query, you could use
    jDicom tools. It gives you a very simple interface for customizing your
    query.

    In a C-Find request you request for certain data. The tags that you
    send in the query are the once returned. Amongst these tags, once
    baring values are take as search parameters and the result so obtained
    are sent back.

    --yogi


  3. Re: C-Find-RQ identifier?

    Rajesh,
    C-FIND-RQ DIMSE is used for more than one SOP class: Query Services and
    Modality Worklist SOP. I guess you refer to Query here.
    PS 3.4 shows you the specific usage of C-FIND (Chapter C-2 is about the
    key attributes, query model...) and the specific status error codes.
    The identifier is just a list of attributes you want to match or you
    want to get filled by the SCP, this list is ruled by PS 3.4 and
    depends on the query model. There is no "end tag". Important things
    here are:
    - only add tags allowed at the query level (PATIENT, STUDY, SERIES)
    - you must walk down the hierarchy levels (there is a relational query
    but not widely supported)
    - when you go down to the next level (e.g. Patient->Study) keep the
    unique identifiers (here Pat ID) from the levels above in the Request
    - add all tags with content you want to match (keep in mind some might
    be supported optionally by the SCP)
    - add all tags with empty value you want to query for (also some are
    supported optionally)

    To find out more about the C-FIND DIMSE in general you should go to PS
    3.7 DIMSE-C Services. It gives you a detailed description about Tag
    Numbers, Value Representation and optionallity in the Command Set part
    of the message.

    And as yogi says use JDicom to play around and have a close look at the
    messages.

    Thomas


+ Reply to Thread