CP-2482Correct inclusion of TID 300 with additional rows
Status
Assigned
Date of Last Update
2025/01/21
Person Assigned
David Clunie
Submitter Name
David Clunie
Submission Date
2024/11/28
Correction Number CP-2482
Log Summary: Correct inclusion of TID 300 with additional rows
Name of StandardPS3.16
Rationale for Correction:Some templates include TID 300 (which consists of a container with sub-ordinate content items),
followed by nested content item rows, implaying that those rows are additional children of the
included container.This is not a valid pattern for template inclusion, and is confusing to automated template table
processors.Correct this by factoring out the TID 300 container content, and replacing the offending invocations with the direct use of the container content item and the inclusion of the new container content template.
Correction Wording:
Amend DICOM PS3.16 as follows (changes to existing text are bold and underlined for additions and struckthrough for removals):
MeasurementThis Template provides a general structure for a numeric measurement, together with evaluations of its normality and/or significance, and the inference source(s) for its value. This structure is instantiated by inclusion of this Template with specific contextual parameters from a parent Template.
Parameters
Parameter Name
Parameter Usage
$Measurement
Coded term or Context Group for Concept Name of measurement
$Units
Measurement Unit
$ModType
Modifier Name for Concept Name of measurement
$ModValue
Modifier Value for Concept Name of measurement
$Method
Value for Measurement Method
$Derivation
Value for Measurement Derivation
$TargetSite
Value(s) for Anatomic Location of measurement
$TargetSiteLaterality
Laterality Value for Anatomic Location of measurement
$TargetSiteMod
Modifier Value for Anatomic Location of measurement
$Equation
Coded term or Context Group for the equation or table from which the measurement was derived or computed
$ImagePurpose
Purpose of Reference for an image used as a source of the measurement
$WavePurpose
Purpose of Reference for a waveform used as a source of the measurement
$RefAuthority
Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority
Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter
Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits
Units of derivation parameter
$PrecoordinatedMeasurementMeaning
Coded value for the precoordinated concept name of measurement
EV (121050, DCM, "Equivalent Meaning of Concept Name")
1
U
16b
>
HAS CONCEPT MOD
CODE
EV (121050, DCM, "Equivalent Meaning of Concept Name")
1
U
$PrecoordinatedMeasurementMeaning
17
>
HAS OBS CONTEXT
INCLUDE
D
1
U
18
>
INFERRED FROM
COMPOSITE
EV (126100, DCM, "Real World Value Map used for measurement")
1
U
SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
19
>
HAS CONCEPT MOD
INCLUDE
D
1
U
Content Item Descriptions
Rows 2, 3, 4, 5
The HAS CONCEPT MOD items allow the explicit definition of terms for post-coordination of the measurement concept name. Additional post-coordinated modifier terms may be included in a SOP Instance based on this Template, in accordance with section 6.2.4, or as defined by Templates that invoke this Template and explicitly define additional post-coordinated modifiers (e.g., TID 5203).
Row 5
Finding site may be multiple when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. E.g., when a maligant, inflammatory or traumatic process spans actual or defined anatomical boundaries. There is no requirement that the multiple locations be contiguous.
Rows 9, 10
The INFERRED FROM items allow the specification (by-value or by-reference) of numeric values that were used in the derivation of the numeric measurement of Row 1. The nature of the inference is not explicitly conveyed; it may be implicit in the Concept Names of the measurements. Inference by-reference is valid only in SOP Classes that permit the INFERRED FROM relationship by-reference.
Row 13
Multiple SCOORD Content Items may be necessary to describe the source of the measurement. E.g., the measurement of an angle between two non-intersecting line segments requires two separate POLYLINE SCOORD Content Items with the concept name of (121223, DCM, "Arm of angle") conveyed in $Purpose.
Rows 13, 14
(260753009, SCT, "Source") may be specified for $ImagePurpose or $WavePurpose as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Rows 16, 16b
Equivalent Meaning of Concept Name allows the creating application to specify the preferred composed concept name representing the measurement and the associated post-coordinated concept modifiers. The concept modifiers may include those specified in this Template, in a Template that invokes this Template, or at the option of the creating application in accordance with . This composed concept name may be rendered by a display application. It may be supplied as text or coded concept or both.
Row 18
Row 18 is a reference to an RWV that describes how measurements were made in units that differ from the stored pixel values in the images referenced in Row 13. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference overrides any reference in an including Template (such as for a Measurement Group).
Add new template to DICOM PS3.16 as follows (no changes to what was extracted from TID 300):
Measurement ContentThis Template provides a general structure for the content of a numeric measurement, together with evaluations of its normality and/or significance, and the inference source(s) for its value.
Parameters
Parameter Name
Parameter Usage
$ModType
Modifier Name for Concept Name of measurement
$ModValue
Modifier Value for Concept Name of measurement
$Method
Value for Measurement Method
$Derivation
Value for Measurement Derivation
$TargetSite
Value(s) for Anatomic Location of measurement
$TargetSiteLaterality
Laterality Value for Anatomic Location of measurement
$TargetSiteMod
Modifier Value for Anatomic Location of measurement
$Equation
Coded term or Context Group for the equation or table from which the measurement was derived or computed
$ImagePurpose
Purpose of Reference for an image used as a source of the measurement
$WavePurpose
Purpose of Reference for a waveform used as a source of the measurement
$RefAuthority
Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority
Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter
Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits
Units of derivation parameter
$PrecoordinatedMeasurementMeaning
Coded value for the precoordinated concept name of measurement
EV (121050, DCM, "Equivalent Meaning of Concept Name")
1
U
16b
HAS CONCEPT MOD
CODE
EV (121050, DCM, "Equivalent Meaning of Concept Name")
1
U
$PrecoordinatedMeasurementMeaning
17
HAS OBS CONTEXT
INCLUDE
D
1
U
18
INFERRED FROM
COMPOSITE
EV (126100, DCM, "Real World Value Map used for measurement")
1
U
SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
19
HAS CONCEPT MOD
INCLUDE
D
1
U
Content Item Descriptions
Rows 2, 3, 4, 5
The HAS CONCEPT MOD items allow the explicit definition of terms for post-coordination of the measurement concept name. Additional post-coordinated modifier terms may be included in a SOP Instance based on this Template, in accordance with section 6.2.4, or as defined by Templates that invoke this Template and explicitly define additional post-coordinated modifiers (e.g., TID 5203).
Row 5
Finding site may be multiple when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. E.g., when a maligant, inflammatory or traumatic process spans actual or defined anatomical boundaries. There is no requirement that the multiple locations be contiguous.
Rows 9, 10
The INFERRED FROM items allow the specification (by-value or by-reference) of numeric values that were used in the derivation of the numeric measurement of Row 1. The nature of the inference is not explicitly conveyed; it may be implicit in the Concept Names of the measurements. Inference by-reference is valid only in SOP Classes that permit the INFERRED FROM relationship by-reference.
Row 13
Multiple SCOORD Content Items may be necessary to describe the source of the measurement. E.g., the measurement of an angle between two non-intersecting line segments requires two separate POLYLINE SCOORD Content Items with the concept name of (121223, DCM, "Arm of angle") conveyed in $Purpose.
Rows 13, 14
(260753009, SCT, "Source") may be specified for $ImagePurpose or $WavePurpose as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Rows 16, 16b
Equivalent Meaning of Concept Name allows the creating application to specify the preferred composed concept name representing the measurement and the associated post-coordinated concept modifiers. The concept modifiers may include those specified in this Template, in a Template that invokes this Template, or at the option of the creating application in accordance with . This composed concept name may be rendered by a display application. It may be supplied as text or coded concept or both.
Row 18
Row 18 is a reference to an RWV that describes how measurements were made in units that differ from the stored pixel values in the images referenced in Row 13. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference overrides any reference in an including Template (such as for a Measurement Group).
Amend DICOM PS3.16 as follows (changes to existing text are bold and underlined for additions and struckthrough for removals):
Echo Measurement
Parameters
Parameter Name
Parameter Usage
$Measurement
Coded term or Context Group for Concept Name of measurement
$Method
Value for Measurement Method
Type:ExtensibleOrder:SignificantRoot:No
Echo Measurement
NL
Rel with Parent
VT
Concept Name
VM
Req Type
Condition
Value Set Constraint
1
INCLUDENUM
D$Measurement
1
M
$Measurement = $Measurement$Method = $Method$TargetSite = B$TargetSiteMod = B
1b
>
INCLUDE
D
1
M
$Method = $Method$TargetSite = B$TargetSiteMod = B
2
>
HAS CONCEPT MOD
CODE
EV (260674002, SCT, "Flow Direction")
1
U
B
3
>
HAS CONCEPT MOD
CODE
EV (272517003, SCT, "Respiratory Cycle Point")
1
U
D
4
>
HAS CONCEPT MOD
CODE
EV (272518008, SCT, "Cardiac Cycle Point")
1
U
D
5
>
HAS ACQ CONTEXT
CODE
EV (399264008, SCT, "Image Mode")
1
U
D
6
>
HAS ACQ CONTEXT
CODE
EV (111031, DCM, "Image View")
1
U
B
7
>
HAS ACQ CONTEXT
CODE
EV (18139-6, LN, "Stage")
1
U
B
Content Item Descriptions
Row 1
TID 300 specifies an "Equivalent Meaning of Concept Name" that allows the creating application to specify the preferred composed concept name representing the measurement and the associated post-coordination Concept Modifiers (e.g., the ASE terminology described in ).
Pediatric, Fetal and Congenital Cardiac Ultrasound MeasurementThis Template provides for the post-coordination of a measurement with a variety of concept modifiers and acquisition context observations. When invoked from , the measurement concept is implicitly post-coordinated with the concept modifiers of the Measurement Group ( Rows 5 and 6), and with the Finding Site of the report section ( Row 2). The finding site may be further specified within this Template by the Target Site and Target Site Modifiers ( and ).The implicit finding site inherited from can be made explicit by using the same finding site concept in the Target Site (the measurement concept modifier), rather than a term from . This explicit post-coordination allows the use of one of the modifiers of to that finding site, as the Target Site Modifier requires an explicit Target Site in the measurement structure ( Rows 5 and 7). In fact, any child concept of the finding site in the SNOMED hierarchy may be used as the measurement Target Site.The finding or target site may be identified by a concept from the SNOMED "clinical finding" or "morphological anomaly" hierarchies (e.g.,
(70142008, SCT, "Atrial Septal defect"), or
(41699000, SCT, "Effusion"),
rather than the "anatomical structure" hierarchy. In this case, the meaning is inferred as "the anatomic location of the clinical finding or morphological anomaly, within the constraints of other implicit or explicit post-coordinated finding site concepts."Thus when Row 14 invokes with the section finding site concept (76848001, SCT, "Pericardium"), and Row 1 applies the target site (41699000, SCT, "Effusion"), the effective finding site is "pericardial effusion".
Parameters
Parameter Name
Parameter Usage
$Measurement
Coded term or Context Group for Concept Name of measurement
$Method
Value for Measurement Method
Type:ExtensibleOrder:SignificantRoot:No
Pediatric, Fetal and Congenital Cardiac Ultrasound Measurement
$Method = $Method$TargetSite = B$TargetSiteMod = B$Derivation = D
2
>
HAS CONCEPT MOD
CODE
EV (121425, DCM, "Index")
1
U
D
3
>
HAS CONCEPT MOD
CODE
EV (260674002, SCT, "Flow Direction")
1
U
B
4
>
HAS CONCEPT MOD
CODE
EV (272517003, SCT, "Respiratory Cycle Point")
1
U
D
5
>
HAS CONCEPT MOD
CODE
EV (272518008, SCT, "Cardiac Cycle Point")
1
U
D
6
>
HAS ACQ CONTEXT
CODE
EV (399264008, SCT, "Image Mode")
1
U
D
7
>
HAS ACQ CONTEXT
CODE
EV (111031, DCM, "Image View")
1
U
B
Content Item Descriptions
Row 1
For an index type of measurement, the concept name of this Row 1 will still be the original measurement concept name; it is Row 2 that gives the indication that Row 1 is actually an index type of measurement. When this happens, the measurement value of Row 1 should be a value after being indexed and the measurement unit of Row 1 should be an index type of unit.For example, to insert a "Stroke Volume Index" measurement to this SR object, the concept name of Row 1 will be "Stroke Volume", its numerical value will be the calculation result of "Stroke Volume /BSA" and its units are "ml/cm2".
Row 2
When this row is available, the Row 1 is an index calculation of the object.
For reference unchanged, an example of a correct invocation of TID 300 that is not followed by implicit inclusion of child rows of the invoked template container: