DICOM PS3.16 2024e - Content Mapping Resource

TID 5223 Pediatric, Fetal and Congenital Cardiac Ultrasound Measurement

This Template provides for the post-coordination of a measurement with a variety of concept modifiers and acquisition context observations. When invoked from TID 5222 “Pediatric, Fetal and Congenital Cardiac Ultrasound Section”, the measurement concept is implicitly post-coordinated with the concept modifiers of the Measurement Group (TID 5222 “Pediatric, Fetal and Congenital Cardiac Ultrasound Section” Rows 5 and 6), and with the Finding Site of the report section (TID 5222 “Pediatric, Fetal and Congenital Cardiac Ultrasound Section” Row 2). The finding site may be further specified within this Template by the Target Site and Target Site Modifiers (CID 12280 “Cardiac Ultrasound Target Site” and CID 12281 “Cardiac Ultrasound Target Site Modifier”).

The implicit finding site inherited from TID 5222 “Pediatric, Fetal and Congenital Cardiac Ultrasound Section” can be made explicit by using the same finding site concept in the Target Site (the measurement concept modifier), rather than a term from CID 12280 “Cardiac Ultrasound Target Site”. This explicit post-coordination allows the use of one of the modifiers of CID 12281 “Cardiac Ultrasound Target Site Modifier” to that finding site, as the Target Site Modifier requires an explicit Target Site in the measurement structure (TID 300 “Measurement” 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., D4-31220 "Atrial Septal Defect", or M-36700 "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."

Note

Thus when TID 5221 “Cardiac Ultrasound Pediatric Echo Measurement Section” Row 14 invokes TID 5222 “Pediatric, Fetal and Congenital Cardiac Ultrasound Section” with the section finding site concept (76848001, SCT, "Pericardium"), and TID 5223 “Pediatric, Fetal and Congenital Cardiac Ultrasound Measurement” Row 1 applies the target site (41699000, SCT, "Effusion"), the effective finding site is "pericardial effusion".

Table TID 5223. Parameters

Parameter Name

Parameter Usage

$Measurement

Coded term or Context Group for Concept Name of measurement

$Method

Value for Measurement Method


Type:

Extensible

Order:

Significant

Root:

No

Table TID 5223. Pediatric, Fetal and Congenital Cardiac Ultrasound Measurement

NL

Rel with Parent

VT

Concept Name

VM

Req Type

Condition

Value Set Constraint

1

INCLUDE

DTID 300 “Measurement”

1

M

$Measurement = $Measurement

$Method = $Method

$TargetSite = BCID 12280 “Cardiac Ultrasound Target Site”

$TargetSiteMod = BCID 12281 “Cardiac Ultrasound Target Site Modifier”

$Derivation = DCID 3838 “Diameter Derivation”

2

>

HAS CONCEPT MOD

CODE

EV (121425, DCM, "Index")

1

U

DCID 3455 “Index Method”

3

>

HAS CONCEPT MOD

CODE

EV (260674002, SCT, "Flow Direction")

1

U

BCID 12221 “Flow Direction”

4

>

HAS CONCEPT MOD

CODE

EV (272517003, SCT, "Respiratory Cycle Point")

1

U

DCID 12234 “Respiration State”

5

>

HAS CONCEPT MOD

CODE

EV (272518008, SCT, "Cardiac Cycle Point")

1

U

DCID 12233 “Cardiac Phase”

6

>

HAS ACQ CONTEXT

CODE

EV (399264008, SCT, "Image Mode")

1

U

DCID 12224 “Ultrasound Image Mode”

7

>

HAS ACQ CONTEXT

CODE

EV (111031, DCM, "Image View")

1

U

BCID 12226 “Echocardiography Image View”


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.

DICOM PS3.16 2024e - Content Mapping Resource