Материал: part03

IODs specify additional constraints on Relationships (including lists of​

Enumerated Values).​

Enumerated Values:​

CONTAINS​

HAS OBS CONTEXT​

HAS ACQ CONTEXT​

HAS CONCEPT MOD​

See Section C.17.3.2.4 for further explanation.​

>Include Table C.17-6 “Document Relationship Macro​

Attributes”​

>Include Table C.17-5 “Document Content Macro Attributes”​

- Standard -​

Note​

1.​One could distinguish four stages in the creation of the Encapsulated Document Object, identified by the following At-​ tributes:​

1.​Measurementand/ordatacollection,identifiedbyAcquisitionDateTime(0008,002A)intheEncapsulatedDocument​ Module.​

2.​Creation of the original documentation of the data collection, identified by Content Date (0008,0023) and Content​ Time (0008,0033).​

3.​Rendering of the original documentation into the format that will be encapsulated, e.g., a PDF document. The ren-​ dering time is not captured by any DICOM Attribute, but may be encoded in the rendering.​

4.​EncapsulationoftherenderingintoaDICOMObject,identifiedbyInstanceCreationDate(0008,0012)andInstance​ Creation Time (0008,0013) in the SOP Common Module.​

2.​DICOM does not specify requirements for consistency between DICOM Attribute values and data in the encapsulated​ document.Itisexpectedthatapplicationswillensureconsistencyinamannerappropriatetotheapplication.Forexample,​ the Patient ID in an encapsulated CDA document may be that of a different institution, which originated the document,​ and it may be appropriate for the DICOM Attribute value to be different.​

- Standard -​

C.24.2.1 Attribute Requirements for Encapsulated CDA Document​

For an Encapsulated CDA Document, Document Title (0042,0010) shall have the value of the CDA Document Title, if one is present​ in the encapsulated document.​

Concept Name Code Sequence (0040,A043) shall have the value of the CDA Document Type Code, with transcoding as necessary​ for converting the HL7 CE Data Type to the DICOM Code Sequence Item.​

Enumerated Values for MIME Type of Encapsulated Document (0042,0012):​

text/XML​

C.24.2.2 Content Sequence​

ContentSequence(0040,A730)encodesstructuredcontentrelevanttotheEncapsulatedDocument(0042,0011).Thisallowsstructured​ data in DICOM encoded form to accompany or describe some or all of the contents of the otherwise opaque encapsulated document,​ and enables receiving implementations to extract that data, e.g., to tabulate numeric measurements, provide them as merge fields​ for dictation, or store them in a database.​

Note​

Some encapsulated document formats may themselves have some structured content, e.g., the non-narrative part of an​ HL7 CDA object, or the XMP metadata of a PDF object. This mechanism allows a DICOM-aware system to extract data​ without needing to parse or understand what is encapsulated.​

Thereisnoexpectationthatallofthenarrativeorvisuallyrenderedcontentintheencapsulateddocumentbereplicatedinastructured​ form in the Content Sequence (0040,A730), nor is it expected that all of the information in the Content Sequence (0040,A730) be​ present in the encapsulated document. E.g., the structured content might contain codes describing the encapsulated document, or​ the encapsulated document may contain observations that are not replicated in the structured content.​

The use of the Content Sequence (0040,A730) follows the pattern established for Structured Reports, and each Item of the Sequence​ in the top level Data Set is a Content Item (see Section C.17.3.2 “Content Item Attributes”).​

Each Item of the Sequence in the top level Data Set may, for instance, be a numeric measurement content item (see Section C.18.1​ “Numeric Measurement Macro”). E.g.:​

•​NUM (8821-1, LN, "Left Ventricular ED Volume") = 98 (mm3, UCUM, "mm3")​

•​NUM (8808-8, LN, "Left Ventricular Ejection Fraction by Angiography") = 65 (%, UCUM, "Percent")​

Alternatively, nested content items may be used in the manner of a typical Structured Report, and an appropriate template from​ PS3.16 invoked (e.g., the TID 1500 Measurement Report template), in which case the Concept Name Code Sequence (0040,A043)​ serves as Document Title and the name of the top level CONTAINER content item of the Structured Report, and such Content Items​ as measurements are nested within containers, may be related to regions of interest, given tracking identifiers, etc.​

C.24.2.3 Security Considerations for Encapsulated Documents (Informative)​

The encapsulated documents may conform to another standard, e.g., PDF, or may be in a proprietary format. Many of these formats​ have had their own security issues, both with the format itself and with common implementations for processing the format.​

Implementations that support encapsulated documents may need to:​

•​Perform input validation and sanitation to detect and perhaps remove invalid or malicious content.​

•​Perform output validation to ensure safe compliance with format specification.​

•​Monitor library implementations for vulnerability reports, updates, and have a process for managing these updates.​

Tracking, notification, and remediation of these security problems will normally be in the context of the encapsulated format and not​ in the context of DICOM. This means those implementing and deploying the encapsulated format must consider security issues from​ those other contexts.​

- Standard -​

C.24.2.4 Relative URI Reference Within Encapsulated Document​

The relative URI reference within encapsulated document value shall be encoded as a relative URI reference [RFC3986], with the​ following restrictions:​

•​The base path (URI) to which the reference is relative is the location where the referencing file would hypothetically be written,​ were it to be unencapsulated and written to a file, such that the set of related encapsulated documents share the same base path.​

•​The path shall not begin with a slash or two slashes.​

•​The path shall not refer to a higher level in the file system hierarchy (i.e., use of ".." is not permitted).​

•​File name extensions corresponding to executable file types (exe, dll, etc.) are not permitted.​

•​Embedded white space is not permitted.​

The following are examples of valid relative URI references:​

•​"matlist.mtl"​

•​"materials/matlist.mtl"​

•​"./materials/matlist.mtl"​

•​"file:///matlist.mtl" (not a relative reference)​

•​"/matlist.mtl" (initial slash not permitted)​

•​"//matlist.mtl" (initial slashes not permitted)​

•​"c:/matlist.mtl" (not a relative reference)​

•​"../matlist.mtl" (".." not permitted)​

•​"mat list.mtl" (embedded spaces not permitted)​

•​"materials\matlist.mtl" (backslash not permitted)​

C.25 Real World Value Mapping Modules​

C.25.1 Real World Value Mapping Series Module​

Table C.25.1-1 defines the general Attributes of the Real World Value Mapping Series Module.​

Table C.25.1-1. Real World Value Mapping Series Module Attributes​

C.25.2 Real World Value Mapping Module​

Table C.25.2-1 defines the general Attributes of the Real World Value Mapping Module.​

Table C.25.2-1. Real World Value Mapping Module Attributes​

- Standard -​

One or more Items shall be included in this​ Sequence.​

>>Include Table 10-3 “Image SOP Instance Reference Macro Attributes”​

C.26 Substance Administration Modules​

C.26.1 Product Characteristics Module​

Table C.26-1 specifies the Attributes used to convey the characteristics or parameters of a contrast agent, drug, or device.​

Table C.26-1. Product Characteristics Module Attributes​

This Attribute is limited by the LT Value Representation to 10240​ characters. Larger text descriptions, or graphical descriptions,​ may be referenced in the Pertinent Documents Sequence​ (0038,0100).​

- Standard -​