| DICOM PS3.2 2025a - Conformance |
|---|
[The following sections define the details of the supported DIMSE Services in more details. Fill in the information for all services supported by the system. Tables are given as examples and should be modified to meet the functionality of the system.]
As a Service Class User of the Modality Worklist Information Model - FIND SOP Class, the <Product> uses the C-FIND-RQ message to query the SCP. It supports the Query Keys listed in Table N.5-2.
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.
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.
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:
[Modify the Table N.5-2 to include all Attributes supported by your system and use the terms defined for Matching Type, Query Value Source and Display on UI above. If Display on UI Values are modified from the ones received, indicate in a footnote. If multiple Values are supported for the Query Value Source, list all of them.]
[Describe scenarios in which the product 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 SCU behavior if the cancellation request is ignored by the SCP and the SCP 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.]
As a Service Class Provider of the Modality Worklist Information Model - FIND SOP Class, the <Product> uses the C-FIND-RSP to communicate matches back to the SCU. It supports the Matching Keys listed in Table N.5-3.
In the "Matching Type" column, the following Values can be used:
SINGLE_VALUE: SCP can perform single Value matching on this Attribute.
UID: SCP can perform List of UID matching on this Attribute.
WILDCARD: SCP can perform Wildcard matching on this Attribute.
SEQUENCE: SCP can perform sequence matching on this Attribute.
UNIVERSAL: SCP can provide the Attribute in the C-FIND response (i.e., universal matching).
[Table N.5-3 contains a set of Attributes that could be supported by a product. Add and remove Attributes in order to match your product implementation using the matching type as defined above. If multiple codes are supported, list all of them. Use the "Comments" column if clarification is needed.]
[Describe the behavior of the product when it receives a C-FIND-CANCEL Request.]
[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:
If the product receives from the SCU a Request Identifier containing unsupported values in the Specific Character Set (0008,0005), then no matching is performed and an error will be returned indicating the SCP is unable to process the request.]
[Document your product's query capabilities and behavior for handling implementation-dependent matching of VRs, such as for DA, DT, TM, IS and DS.]
| DICOM PS3.2 2025a - Conformance |
|---|