Материал: part03

1.​Inthecaseofascannedpatientlabel,thismaybethesame​ as Patient ID (0010,0020), but it is included in an Instance​ level Module rather than a Patient level Module since​ barcodes may also be used to identify lower level entities.​ Thismightbeobtainedbyscanningthepatient'swristband,​ requestform,orextractingaburned-inlabelfromtheimage​ pixel data, for example.​

2.​In the case of a scanned slide label, this may be the same​ asContainerIdentifier(0040,0512)intheSpecimenModule.​

Note​

IfIssuerofPatientID(0010,0021)isincludedintheModifiedAttributeSequence,thecontextofthepriorPatientID(0010,0020)​ can be more precisely identified.​

C.12.1.1 SOP Common Attribute Descriptions​

C.12.1.1.1 SOP Class UID, SOP Instance UID​

The SOP Class UID and SOP Instance UID Attributes are defined for all DICOM IODs. However, they are only encoded in Composite​ IODs with the Type equal to 1. See Section C.1.2.3. When encoded they shall be equal to their respective Attributes in the DIMSE​ Services and the File Meta Information header (see PS3.10 Media Storage).​

C.12.1.1.2 Specific Character Set​

Specific Character Set (0008,0005) identifies the Character Set that expands or replaces the Basic Graphic Set (ISO 646) for values​ of Data Elements that have Value Representation of SH, LO, ST, PN, LT, UC or UT. See PS3.5.​

If the Attribute Specific Character Set (0008,0005) is not present or has only a single value, Code Extension techniques are not used.​ DefinedTermsfortheAttributeSpecificCharacterSet(0008,0005),whensinglevalued,arederivedfromtheInternationalRegistration​ Number as per ISO 2375 (e.g., ISO_IR 100 for Latin alphabet No. 1). See Table C.12-2.​

Table C.12-2. Defined Terms for Single-Byte Character Sets Without Code Extensions​

- Standard -​

Note​

To use the single-byte code table of JIS X0201, the value of Attribute Specific Character Set (0008,0005), value 1 should​ be ISO_IR 13. This means that ISO-IR 13 is designated as the G1 code element, which is invoked in the GR area. It should​ be understood that, in addition, ISO-IR 14 is designated as the G0 code element and this is invoked in the GL area.​

If the Attribute Specific Character Set (0008,0005) has more than one value, Code Extension techniques are used and Escape Se-​ quences may be encountered in all character sets. Requirements for the use of Code Extension techniques are specified in PS3.5.​ In order to indicate the presence of Code Extension, the Defined Terms for the repertoires have the prefix "ISO 2022", e.g., ISO 2022​ IR 100 for the Latin Alphabet No. 1. See Table C.12-3 and Table C.12-4. Table C.12-3 describes single-byte character sets for value​ 1 to value n of the Attribute Specific Character Set (0008,0005), and Table C.12-4 describes multi-byte character sets for value 2 to​ value n of the Attribute Specific Character Set (0008,0005).​

Note​

A prefix other than "ISO 2022" may be needed in the future if other Code Extension techniques are adopted.​

The same character set shall not be used more than once in Specific Character Set (0008,0005).​

Note​

For example, the values "ISO 2022 IR 100\ISO 2022 IR 100" or "ISO_IR 100\ISO 2022 IR 100" are redundant and not per-​ mitted.​

Table C.12-3. Defined Terms for Single-Byte Character Sets with Code Extensions​

- Standard -​

Note​

If the Attribute Specific Character Set (0008,0005) has more than one value and value 1 is empty, it is assumed that value​ 1 is ISO 2022 IR 6.​

Table C.12-4. Defined Terms for Multi-Byte Character Sets with Code Extensions​

- Standard -​

There are multi-byte character sets that prohibit the use of Code Extension Techniques. The following multi-byte character sets pro-​ hibit the use of Code Extension Techniques:​

•​The Unicode character set used in [ISO/IEC 10646], when encoded in UTF​

•​The [GB 18030] character set, when encoded per the rules of [GB 18030]​

•​The [GBK] character set encoded per the rules of [GBK]​

These character sets may only be specified as value 1 in the Specific Character Set (0008,0005) Attribute and there shall only be​ one value. The minimal length UTF-8 encoding shall always be used for [ISO/IEC 10646].​

Note​

1.​[ISO/IEC 10646] now prohibits the use of anything but the minimum length encoding for UTF-8. UTF-8 permits multiple​ different encodings, but when used to encode Unicode characters in accordance with ISO 10646-1 and 10646-2 (with​ extensions) only the minimal encodings are legal.​

2.​The representation for the characters in the DICOM Default Character Repertoire is the same single byte value for the​ Default Character Repertoire, [ISO/IEC 10646] in UTF-8, [GB 18030] and [GBK]. It is also the 7-bit US-ASCII encoding.​

3.​The [GBK] character set is a subset of the [GB 18030] character set, which is restricted in its oneand two-byte code​ points. In this subset, the [GBK] character set follows the exactly same encoding rules of [GB 18030].​

Table C.12-5. Defined Terms for Multi-Byte Character Sets Without Code Extensions​

C.12.1.1.3 Digital Signatures Macro​

This Macro allows Digital Signatures to be included in a DICOM Data Set for the purpose of insuring the integrity of the Data Set, and​ to authenticate the sources of the Data Set. Table C.12-6 defines the Attributes needed to embed a Digital Signature in a Data Set.​ This Macro may appear in individual Sequence Items as well as in the top level Data Set of the SOP Instance.​

Note​

1.​Each Item of a Sequence of Items is a Data Set. Thus, individual Sequence Items may incorporate their own Digital​ Signatures in addition to any Digital Signatures added to the Data Set in which the Sequence appears.​

2.​The inclusion of this Macro in Sequence Items, other than as specified in this Part of the Standard, may be specified in​ an application-defined Standard Extended SOP Class or Private SOP Class (see PS3.2).​

- Standard -​

Page 1380​ DICOM PS3.3 2020a - Information Object Definitions​

Table C.12-6. Digital Signatures Macro Attributes​

Note​

This is not a certified timestamp, and hence is not completely​ verifiable.Anapplicationcancomparethisdateandtimewiththose​ of other signatures and the validity date of the certificate to gain​ confidence in the veracity of this date and time.​

- Standard -​