DICOM PS3.20 2024d - Imaging Reports using HL7 Clinical Document Architecture |
---|
Each template has a set of metadata, as specified in the HL7 Templates Specification. The metadata is presented as a table, as shown in Table 5.1-1.
Table 5.1-1. Template metadata table format
OID (see Section 5.1.1) |
|
(see Section 5.1.1) |
|
"parent node", "sibling node" (see Section 5.1.2) |
|
"open", "closed"(see Section 5.1.3) |
|
Template identifiers (templateId) are assigned for each document, section, and entry level template. When valued in an instance, the template identifier signals the imposition of a set of template-defined constraints. The value of this attribute (e.g., @root="2.16.840.1.113883.10.20.22.4.8") provides a unique identifier for the template in question.
A template may be further qualified by a version label. This label may be used as the extension attribute of the templateID (e.g., @extension="20150309"). All versions of a template, regardless of the version label, must be compatible; i.e., they may vary only by optional content conformance requirements. Thus the version label is typically not used as a conformance constraint.
Within this Standard, template versions are identified by the string "DICOM" and the date of adoption (represented as YYYYMMDD), separated by a hyphen (e.g., DICOM-20150523).
As described in the HL7 Template specification section 2.9.9.4, the context identifies whether the template applies to the parent node in which the templateID is an element, or applies to its sibling nodes in the template table. These typically are applied respectively to templates with a single parent element with child element structure, and to templates with flat list of sibling elements (see Section 5.2.8).
DICOM PS3.20 2024d - Imaging Reports using HL7 Clinical Document Architecture |
---|