CP-2176 Add Category of Finding to TID 1500 Status Assigned Date of Last Update 2021/11/14 Person Assigned David Clunie Submitter Name Markus Daniel Herrmann IDC Submission Date 2021/09/05 Correction Number CP-2176 Log Summary: Add Category of Finding to TID 1500 Name of Standard PS3.16 Rationale for Correction: There is an inconsistency between SR (TID 1410, 1411, and 1501) and segmentations (SEG) and annotations (ANN). For SEG/ANN, one is required to specify the property category and type, while in SR one can only specify (121071, DCM, "Finding"), which corresponds to the property type ("finding type") (added in CP 1465). There is no template row to specify the finding category. This is problematic for at least two reasons: It complicates interpretation, compared to what is possible with the SEG. E.g., is the category of a finding a normal anatomic structure or a morphologic abnormality? When providing additional ROI measurements of referenced segments, information about the category (from the SEG) is not communicated. [Ed.Note: The existing SCT code 276214006 (with the FSN "Findings category type (qualifier value)"), with the DICOM synonym "Finding category", is used rather than creating a new DCM-specific code. CRS Request ID# 764392.] [Ed.Note: TID 1501 uses TID 300, so does not reference segmentations, hence the absence of the comment cross-referencing segmentation-specific attributes; the category concept is still useful and appropriate, however.] [Ed.Note; Should we add default context groups for findingcategories and findings, to match those reference in the PS3.3 uses of Segmented Property Category Code Sequence (0062,0003) and Segmented Property Type Code Sequence (0062,000F), specifically CID 7150 and CID 7151 respectively? Certainly the categories are a short list that are reusable beyond the segmentation role; the segmentation type concepts may be too specific and not sufficient for generic TID 1500 use cases; the categories are tied to specific invocations of segmentation type context groups, however.] [Ed.Note: Is it not high time we replaced (121071, DCM, "Finding") with a concept from a more generic source that is included in UMLS, e.g., (LA9042-8, LN, "Finding") == (C61036, NCIt, "[Investigation ]Finding") == (C0243095, UMLS, "Finding")? If so, this should be done as a separate CP and generally applied, since it affects many more templates than these.] Correction Wording:
Amend DICOM PS3.16 as follows:
Planar ROI Measurements and Qualitative Evaluations ...
Parameters
...
$FindingCategory Category of the finding
$FindingType Type of the finding
...
Planar ROI Measurements and Qualitative Evaluations
NL Rel with Parent VT Concept Name VM Req Type Condition Value Set Constraint
1 CONTAINER EV (125007, DCM, "Measurement Group") 1 M
...
3 > HAS OBS CONTEXT UIDREF EV (112040, DCM, "Tracking Unique Identifier") 1 U $TrackingUID
3a > CONTAINS CODE EV (276214006, SCT, "Finding category") 1 U $FindingCategory
3b > CONTAINS CODE EV (121071, DCM, "Finding") 1 U $FindingType
...
Content Item Descriptions ... Rows 2, 3 The Tracking Identifier and Tracking Unique Identifier are defined as a text label or unique identifier (respectively) used for tracking a finding or feature, potentially across multiple reporting objects, over time. As such, they are distinct from the Observation UID (0040,A171), which is unique identifier of the specific Content Item and its subsidiary Content Items that constitute an individual observation, and would be different for different observations on different occasions of the same finding or feature. The values of these content items shall match the corresponding values of Tracking ID (0062,0020) and Tracking UID (0062,0021), if present, in the corresponding Segment of any Segmentation instance referenced in Row 7. Rows 3a, 3b The category and type of the finding describes whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different content item (Finding Site). When spatial localization is by reference to a Segmentation, the category and type may correspond to the values of Segmented Property Category Code Sequence (0062,0003) and Segmented Property Type Code Sequence (0062,000F), respectively. ...
Volumetric ROI Measurements and Qualitative Evaluations ....
Parameters
...
$FindingCategory Category of the finding
$FindingType Type of the finding
Volumetric ROI Measurements and Qualitative Evaluations
NL Rel with Parent VT Concept Name VM Req Type Condition Value Set Constraint
1 CONTAINER EV (125007, DCM, "Measurement Group") 1 M
...
3 > HAS OBS CONTEXT UIDREF EV (112040, DCM, "Tracking Unique Identifier") 1 U $TrackingUID
3a > CONTAINS CODE EV (276214006, SCT, "Finding category") 1 U $FindingCategory
3b > CONTAINS CODE EV (121071, DCM, "Finding") 1 U $FindingType
... > CONTAINS CODE EV (130400, DCM, "Geometric purpose of region") 1 U B
Content Item Descriptions ... Rows 2, 3 The Tracking Identifier and Tracking Unique Identifier are defined as a text label or unique identifier (respectively) used for tracking a finding or feature, potentially across multiple reporting objects, over time. As such, they are distinct from the Observation UID (0040,A171), which is unique identifier of the specific Content Item and its subsidiary Content Items that constitute an individual observation, and would be different for different observations on different occasions of the same finding or feature. The values of these content items shall match the corresponding values of Tracking ID (0062,0020) and Tracking UID (0062,0021), if present, in the corresponding Segment of any Segmentation instance referenced in Row 7. Rows 3a, 3b The category and type of the finding describes whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different content item (Finding Site). When spatial localization is by reference to a Segmentation, the category and type may correspond to the values of Segmented Property Category Code Sequence (0062,0003) and Segmented Property Type Code Sequence (0062,000F), respectively. ...
Measurement and Qualitative Evaluation Group ...
Parameters
Parameter Name Parameter Usage
...
$FindingCategory Category of the finding
$FindingType Type of the finding
...
Measurement and Qualitative Evaluation Group
NL Rel with Parent VT Concept Name VM Req Type Condition Value Set Constraint
1 CONTAINS CONTAINER EV (125007, DCM, "Measurement Group") 1 M
...
3 > HAS OBS CONTEXT UIDREF EV (112040, DCM, "Tracking Unique Identifier") 1 U $TrackingUID
3a > CONTAINS CODE EV (276214006, SCT, "Finding category") 1 U $FindingCategory
3b > CONTAINS CODE EV (121071, DCM, "Finding") 1 U $FindingType
...
Content Item Descriptions ... Rows 2, 3, 10 The included TID 300 contains an optional inclusion of TID 1408 Tracking Identifier as a child of the NUM measurement, which in turns allows for either or both Tracking Identifier and Tracking Unique Identifier Content Items; the intent of Rows 2 and 3 is not to send these Content Items twice, but rather to factor them out into a common location for multiple measurements, and to be consistent with TID 1410 and TID 1411. Rows 3a, 3b The category and type of the finding describes whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different content item (Finding Site). ...
English Code Meanings of Selected Codes (Normative)
English Code Meanings of Selected Codes
Coding Scheme Designator Code Value Code Meaning
SCT 276214006 Finding category
Findings category type