[Provide a short description of the product's DICOM functionality.]
[Edit the following illustration, depicting DICOM Services implemented in your product and the interactions with remote systems connected to product. Replace <Product> with your product name and <Remote Systems x> with a system category such as modality, PACS, RIS, or <DICOM Service> by the applicable service such as storage, query/ retrieve, query modality worklist, ….]
Table N.1-1 lists all Storage SOP Classes and the supported transfer mechanisms as well as the usage scenarios for those instances.
The "Transfer Syntax Set" column lists the sets of Transfer Syntaxes defined in Table N.1-2 that are applicable to each SOP Class. The "DIMSE", "DICOM Web" and "Media Services" columns indicate the roles supported for each SOP Class.
The "Function" columns indicate how the instances are used by the system:
-
Create: The system creates instances of the SOP Class. The type of the created SOP Class is indicated by one of the following abbreviations:
-
Display: The system displays the instances of the SOP Class to the user, either by displaying the SOP Instances natively or by applying instances of another suitable SOP Class to the image instances (e.g., a Presentation State or CAD SR).
-
Process: The system processes the instances of the SOP Class to derive some further information that is made available to the user (e.g., a CAD processing algorithm, or a 3D Rendering).
-
Archive: The system stores the instances of the SOP Class and makes them available again.
[List all Storage SOP Classes supported by the system in numerical order of the SOP Class UID. Indicate in the "Transfer Syntax Set" column which of the Transfer Syntax Sets defined in Table N.1-2 are supported. Note that for each SOP Class, multiple Transfer Syntax Sets can be supported.]
[For the "Create Function" columns, use Values as defined above. For all other supported role/"Function" columns, list "Y" for yes and "N" for no.]
[Table N.1-2 defines some example Transfer Syntax Sets that are referenced by their abbreviation in Table N.1-1 above. You can modify the Transfer Syntax Sets to match your product implementation and extend the Table with additional Transfer Syntax Sets as needed. For additional Transfer Syntax Sets, create additional rows and assign abbreviations in "() " that can be referenced in the Table above.]
Table N.1-2. Supported Transfer Syntaxes
Table N.1-3 lists all Template IDs (TID) of Root Templates that are supported by the system. The "Function" column indicates how the system uses the content of the DICOM SR:
-
CREATE: The system creates instances using the specified TID.
-
RENDER: The system displays the content of the SR, without using the data for any processing.
-
EXTRACT_DATA: The system can extract structured data from the content and use the data for subsequent processing (e.g., reporting).
-
OVERLAY: The system uses the information in the SR to display information directly on the images (e.g., Mammography CAD markers).
The "SOP Class UID" column indicates which of the SR Storage SOP Classes are used to encode the information or to store it. If multiple SOP Classes are supported the "Condition" column describes the conditions for using the different SOP Classes.
[Table N.1-3 provides some examples, add/remove TIDs to match your product implementation. Add Root TIDs in ascending numerical order.
For guidance on the meaning of the columns see description above. Note that in the "Function" column multiple Values can be listed.
It is recommended to add a link to the "Root Template ID" column to the relevant subsection of Section N.10.]