DICOM PS3.2 2024b - Conformance

N.5.2.7 Query/Retrieve Service Class

[The sections below define some of the most used Query Retrieve SOP Classes as examples, however, there are many more Query/Retrieve SOP Classes defined in DICOM PS 3.4. If your product supports any of these additional SOP Classes, add additional Sections for these SOP Classes for SCU and SCP using the structure as indicated for any of the SOP Classes below.]

N.5.2.7.1 SCU of the Study Root Q/R Information Model - FIND SOP Class

As a Service Class User of the Study Root Q/R - Information Model - FIND SOP Class, the <Product> uses the C-FIND-RQ message and supports the Query Keys listed in Table N.5-17 for hierarchical queries.

In the "Matching Type" column the following Values can be used:

  • SINGLE_VALUE: SCU can request Single Value matching on this Attribute.

  • UID: SCU can request List of UID matching on this Attribute.

  • WILDCARD: SCU can request Wildcard matching on this Attribute.

  • RANGE: SCU can request Range matching on this Attribute.

  • SEQUENCE: SCU can request Sequence matching on this Attribute.

  • UNIVERSAL: SCU can request that the Attribute be a return Value (universal matching).

In the "Query Value Source" column the following Values can be used:

  • FIXED: The query Value cannot be modified by the user or by configuration.

  • GENERATED: The query Value is generated by the system (e.g., current date as the study date).

  • CONFIGURATION: The query Value is dependent on system configuration.

  • USER: The query Value is entered by the user.

  • SCANNED: The query Value is read from a barcode scanner or similar device.

  • EMPTY: The query Value is sent with a zero-length value to indicate it is a return key only.

In the "Display on UI" column the following Values can be used:

  • D: the return Value is displayed on the main UI by default.

  • C: the return Value is displayed on the main UI if configured.

  • N: the return Value is never displayed.

[Modify Table N.5-17 to include all Attributes supported by your system (standard Attributes as well as private Attributes) and use the terms defined for matching type, query Value source and Display on UI above. If multiple codes are supported, list all of them.]

Table N.5-17. Supported C-FIND Attribute Matching for Study Root Q/R Model -SCU

Attribute Name

Tag

Matching Type

Query Value Source

Value

Display on UI

Comments

Study Level

Study Date

(0008,0020)

RANGE

USER

D

Study Time

(0008,0030)

RANGE

USER

D

Accession Number

(0008,0050)

SINGLE_VALUE

USER

D

Patient's Name

(0010,0010)

WILDCARD

USER

D

Patient ID

(0010,0020)

SINGLE_VALUE

USER, GENERATED

D

Study Instance UID

(0020,000D)

UNIVERSAL

EMPTY

N

Modalities in Study

(0008,0061)

SINGLE_VALUE

USER

D

Study Description

(0008,1030)

WILDCARD

USER

D

Series Level

Modality

(0008,0060)

SINGLE_VALUE

USER

D

Body Part Examined

(0018,0015)

SINGLE_VALUE

USER

C

Instance Level

Private Attributes

Private Creator

(0009,0010)

SINGLE_VALUE

FIXED

N

Private Value1

(0009,1001)

UNIVERSAL

EMPTY

C


[If <product> supports Extended Negotiation for Relational Queries, describe supported matching Attributes.]

[Describe scenarios in which the SCU can issue C-FIND-CANCEL requests, e.g.

The product issues C-FIND CANCEL requests in the following scenarios:* Configurable maximum of matches detected* Initiated by user]

[Also describe the behavior if the SCP ignores the cancellation request and continues sending responses.]

[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:

When configured for Japanese character set support, Person Name query attributes may contain ideographic (kanji) and/or phonetic (hiragana and katakana) and/or Romanized (romaji) representations.

When configured for Chinese character set support, Person Name query attributes may contain ideographic (hanzi) and/or phonetic (pinyin) representations are supported. For Patient’s Name (0010,0010), the representation which is displayed by default in the worklist is configurable.

When configured for Korean character set support, Person Name query attributes may contain ideographic (hanja) and/or phonetic (hangul) and/or Romanized representations.

If the product receives from the SCP a C-FIND response containing unsupported values in Specific Character Set (0008,0005), characters in that character set will be treated as unknown characters as described in Section 6.1.2.3 in PS3.5 .

If a Person Name attribute contains multiple representations, the GUI will display one representation based on a configurable order of preference.]

DICOM PS3.2 2024b - Conformance