Материал: part20
DICOM PS3.20 2020a - Imaging Reports using HL7 Clinical Document Architecture |
Page 21 |
3 Definitions
For the purposes of this Standard the following definitions apply.
3.1 Codes and Controlled Terminology Definitions:
The following definitions are commonly used in this Part of the DICOM Standard:
Context Group |
A set of coded concepts defined by a Mapping Resource forming a set appropriate to use in a |
|
particular context. |
Context ID (CID) |
Identifier of a Context Group. |
Template |
A pattern that describes the Content Items, Value Types, Relationship Types and Value Sets |
|
that may be used in part of a Structured Report content tree, or in other Content Item constructs, |
|
suchasAcquisitionContextorProtocolContext.AnalogoustoaModuleofanInformationObject |
|
Definition. |
Template ID (TID) |
Identifier of a Template. |
Coding Schemes |
Dictionaries (lexicons) of concepts (terms) with assigned codes and well defined meanings. |
3.2 Vocabulary Model Definitions:
The following terms used in this Part of the DICOM Standard are defined in HL7 Core Principles and Properties of Version 3 Models:
Concept Domain |
Anamedcategoryoflikeconcepts(asemantictype)thatisspecifiedinthevocabularydeclaration |
|
ofanattributeinaninformationmodel.Itconstrainstheintentofthecodedelementwhiledeferring |
|
the binding of the element to a specific set of codes until later in the specification process. |
Value Set |
Auniquelyidentifiablesetofvalidconceptidentifiers.Valuesetsconstrainthepermissiblecontent |
|
for a coded element in an information model or data type specification. |
Vocabulary Binding |
Themechanismofidentifyingspecificcodestobeusedtoexpressthesemanticsofcodedmodel |
|
elements in information models or coded data type properties. Vocabulary Binding may bind the |
|
coded element or data type property to a single fixed value code, or may bind it to a Value Set |
|
Assertion. |
3.3 Template Definitions
The following term used in this Part of the DICOM Standard is defined in the HL7 Templates Standard, and applies to CDA template specifications:
Template A set of conformance statements which further constrain an existing information model.
3.4 Imaging Report Definitions
The following definitions apply to terms used in this Part of the Standard:
Business Name |
Identifier for a CDA Data Element, Attribute, or structure of Data Elements that corresponds to |
|
a business requirement for information exchange. |
- Standard -
Page 22 |
DICOM PS3.20 2020a - Imaging Reports using HL7 Clinical Document Architecture |
- Standard -
DICOM PS3.20 2020a - Imaging Reports using HL7 Clinical Document Architecture |
Page 23 |
4 Symbols and Abbreviations
The following symbols and abbreviations are used in this Part of the Standard.
ANSI American National Standards Institute
CDA Clinical Document Architecture (HL7)
DICOM Digital Imaging and Communications in Medicine
HL7 Health Level 7
HMD Hierarchical Message Description (HL7)
IE Information Entity
IHE Integrating the Healthcare Enterprise
IOD Information Object Definition
ISO International Standards Organization
LOINC Logical Observation Identifiers Names and Codes
MRRT IHE Management of Radiology Report Templates Profile
NEMA National Electrical Manufacturers Association
OID Object Identifier (ISO 8824)
RSNA Radiological Society of North America
SNOMEDSystematized Nomenclature of Medicine
SR Structured Reporting
UCUM Unified Code for Units of Measure
UID Unique Identifier
XML Extensible Markup Language
The following symbols and abbreviations for HL7 v3 Data Types are used in this Part of the Standard.
AD Postal Address
CE Coded With Equivalents
CD Concept Descriptor
CS Coded Simple Value
ED Encapsulated Data
EN Entity Name
II Instance Identifier
INT Integer Number
IVL<> Interval
LIST<> List
- Standard -
Page 24 |
DICOM PS3.20 2020a - Imaging Reports using HL7 Clinical Document Architecture |
OID ISO Object Identifier
ON Organization Name
PN Person Name
PQ Physical Quantity
REAL Real Number
ST Character String
TEL Telecommunication Address
TS Point in Time
UID Unique Identifier String
URL Universal Resource Identifier
- Standard -
DICOM PS3.20 2020a - Imaging Reports using HL7 Clinical Document Architecture |
Page 25 |
5 Conventions
5.1 Template Metadata
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 |
Template ID |
OID (see Section 5.1.1) |
Name |
|
Effective Date |
|
Version Label |
(see Section 5.1.1) |
Status |
"draft", "active", "review" or "retired" |
Description |
|
Classification |
type of the template, e.g., CDA Section Level |
Relationships |
relationships to other templates or model artifacts |
Context |
"parent node", "sibling node" (see Section 5.1.2) |
Open/Closed |
"open", "closed"(see Section 5.1.3) |
Revision History |
|
5.1.1 Template IDs and Version
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).
5.1.2 Context
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 templateswithasingleparentelementwithchildelementstructure,andtotemplateswithflatlistofsiblingelements(seeSection5.2.8).
5.1.3 Open and Closed Templates
Eachtemplateisdefinedasbeingeither"open"or"closed".In"open"templates,allofthefeaturesoftheCDASpecificationareallowed except as constrained by the templates. By contrast, a "closed" template specifies everything that is allowed and nothing further may be included.
5.2 Template Table Structure
Each template is specified in tabular form, as shown in Table 5.2-1.
- Standard -