DICOM PS3.2 2023a - Conformance

N.12 A.D Mapping of Attributes

[Describe the Mapping of Attributes in this Annex, create a subsection for each mapping. Examples for such mappings are:

[The following subsection shows an example for the Mapping between Modality Worklist Instances and MPPS.]

N.12.1 A.D.1 Mapping Between Modality Worklist Instances and MPPS

Table N.12-1 describes the mapping of Attributes between Modality Worklist Instances and MPPS messages.

In the "Scenario" column the following Values are used:

[List the different scenarios which your product supports for mapping Attributes and use those Values in the table below in the "Scenario" column. The list below represents an example that is derived from the IHE Radiology Technical Framework - Vol. 2; however, you can define your own scenarios or modify the list below. All entries in the list need to occur as permanent text in your DICOM Conformance Statement.

  • SCHEDULED: The image acquisition was scheduled at the RIS and procedure details have been communicated in the MWL query)

  • UNSCHEDULED: The image acquisition was performed without Modality Worklist information

  • APPEND: Instances acquired are added to an existing study after the initial procedure was finalized

  • GROUP: Multiple requested procedures are grouped into one study.]

In the "Value Source" columns, the following Values are used. The column cell may additionally contain an Attribute Tag if the value is copied from a different Attribute.

  • GENERATED: The Value is generated by the system.

  • SRC_INSTANCE: The Value is copied from previously created instances.

  • MWL: The Value is copied from a Modality Worklist entry.

  • USER: The Value is entered by the user.

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

  • EMPTY: The Attribute is sent with a zero-length Value.

The "Destination" columns either contain TOP, if the Attribute is added to the top level Data Set of the Instance, or contain the Attribute Tag of the Sequence the Attribute will be added to. The "Comments" column can be used to provide additional information regarding the Values added to the Instance or MPPS.

[Update the Table to match your product implementation. The entries below are meant as an example.]

Table N.12-1. Mapping of Attributes from Modality Worklist to Instance and MPPS

Attribute Name in Image/MPPS

Tag

Scenario

Image

MPPS

Comments

Value Source

Destination

Value Source

Destination

Study Instance UID

(0020,000D)

SCHEDULED

MWL

TOP

SRC_INSTANCE

(0040,0270)

UNSCHEDULED

GENERATED

TOP

EMPTY

(0040,0270)

APPEND

SRC_INSTANCE

TOP

SRC_INSTANCE

(0040,0270)

GROUP

SYSTEM

TOP

SRC_INSTANCE

(0040,0270) (a)

(a) One item per SPS in (0040, 0270)

Accession Number

(0008,0050)

SCHEDULED

MWL

TOP

SRC_INSTANCE

(0040,0270)

UNSCHEDULED

EMPTY

TOP

EMPTY

(0040,0270)

APPEND

SRC_INSTANCE

TOP

SRC_INSTANCE

(0040,0270)

GROUP

MWL;EMPTY (a)

TOP

MWL (b)

(0040,0270)

(a) If the Accession Number for all Requested Procedures is the same, use that in the Accession Number of the Instances. If different keep empty.

(b) Copy Accession Number for each Requested Procedure into the item of the appropriate SPS

Requested Procedure ID

(0040,1001)

SCHEDULED

MWL

(0040,0275) (a)

(0040,A370) (b)

SRC_INSTANCE

(0040,0270)

(a) for use in Image IODs)

(b) for use in Evidence Documents

UNSCHEDULED

N/A

N/A

EMPTY

(0040,0270)

APPEND

SRC_INSTANCE

(0040,0275) (a)

(0040,A370) (b)

SRC_INSTANCE

(0040,0270)

(a) for use in Image IODs)

(b) for use in Evidence Documents

GROUP

Study ID

(0020,0010)

SCHEDULED

MWL (0040,1001)

TOP

SRC_INSTANCE

TOP

(0040,1001) is Requested Procedure ID

UNSCHEDULED

GENERATED

TOP

SRC_INSTANCE

TOP

APPEND

SRC_INSTANCE (0040,1001)

TOP

SRC_INSTANCE

TOP

(0040,1001) is Requested Procedure ID


DICOM PS3.2 2023a - Conformance