DICOM PS3.2 2024e - Conformance |
---|
[Note that the Annexes defined in the following subsections are a mandatory part of the DICOM Conformance Statement and must be filled for any product that creates DICOM objects.]
[For all SOP Instances of supported Storage SOP Classes (including Real-Time Video objects) that can be created by the system (see Overview Section N.1.1) provide an Annex A.x.]
[Throughout all the tables in this Annex, the Tag order is as it appears in the DICOM Standard to ease comparison and validation. It is recommended that products do the same in their Conformance Statements.]
This section describes all the SOP Instances natively created by <Product>, e.g., images created by an acquisition modality or evidence documents created on a review workstation (i.e., all SOP Classes that are marked in the "Created" column in Table N.1-1). Details on Attribute coercion are defined in Section N.5.2.5.2.
In the "Source" column, the following Values can be used:
CONFIGURATION: The Value is copied from the system configuration.
QUERY: The Value is determined by performing a query of any of the supported Query/Retrieve Services.
SCANNED: The Value is read from a barcode scanner or similar device.
SRC_INSTANCE: The Value is copied from previously created/received SOP Instances.
The "Presence" columns reflect the usage of the Module, Functional Group Macro, Attributes, or Value in the <product>Implementation and is not necessarily the same as defined in the DICOM Standard. For the "Presence" column the following Values can be used:
ALWAYS: the module, functional group macro, Attributes or Value is always present.
CONDITIONAL: the presence of the module, functional group macro, Attributes or Value is dependent on a condition. The condition must be listed in the "Conditions" column.
SRC_COPY: The presence of the Attributes and Values depends on the availability of these in the source instances, which are used for copying this information.
EMPTY: The Attribute is present but without a Value (zero length).
All SOP Instances generated by the system use the common modules listed in Table N.9-1 to Table N.9-12 or a subset of them, as defined in the IOD specific subsections below.
[The tables list the most common Modules; tables for additional Modules can be appended at the end. It is up to the editor of the DICOM Conformance Statement to move some of the tables to the IOD specific sections, if the information differs between the documented IODs.]
[Complete the following tables and provide information on all Attributes that are populated in your IOD, add additional Attributes, remove Attributes not used and provide a description how the Attributes are populated.]
[For the "Source" column use one of the pre-defined terms above, also note that multiple Values are allowed, however an explanation of the conditions under which one or the other Value is used, must be provided.]
[If in the "Value" column different Values are supported, they can be defined in the Shared Values and Code Set subsection and a reference to the respective table can be entered in the "Value" column. Furthermore, for Coded Terms it is possible to provide a reference to a CID defined in PS3.16.]
[For the "Presence" columns the Values defined above can be used. Also note that multiple Values are allowed, however an explanation of the conditions under which one or the other Value is used, must be provided.]
[If the modules use Attributes that can support different Value Types (See PS3.15), add the Value Type supported in the "Comments" column.]
Table N.9-9. Multi-Frame Functional Groups Module
[If your product uses other Modules that are shared between multiple IODs created on your product, list them in tables following the structure of the above ones.]
The tables below list the Common Functional Group Macros that can either be used as part of the Shared Functional Groups Sequence (5200,9229) or as part of the Per-frame Functional Groups Sequence (5200,9230) of enhanced image IODs.
[Modify/add/delete tables below to match your product implementation. For content of the columns, see the instructions in A.1.1 Common Modules:
If you do not create any enhanced IODs mark this section as N/A, append "-N/A" to the Section Title and remove the tables below.]
The tables below list private Attributes that are used in multiple IODs generated by the system. For documentation convenience and readability, they are organized in modules, although the concept of modules does not exist in the standard for private Attributes.
[For each Common Private Module create a table following the structure listed below and populate it with all private Attributes which are shared between different IODs. For each Attribute list name, Tag, Value Representation, Value Multiplicity, whether the Value contains Identifiable Information). In the "Identifiable Information" column the following Values can be used: SAFE, UNSAFE, MIXED. For details see the Private Data Element Characteristics Sequence (0008,0300) as defined in DICOM PS3.3.
For the other columns see the instructions above. It is highly recommended to populate the Private Data Element Characteristics Sequence (0008,0300) if Private Attributes are being used.]
[For a description of the purpose of the Private Attribute either use the "Comments" column or add a note below the table.]
Table N.9-22 lists Coded Values referenced from the "Value" column of the tables above.
[Document Coded Terms and Code String values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]
DICOM PS3.2 2024e - Conformance |
---|