Digital Imaging and Communications in Medicine (DICOM) Supplement 9 Multi-byte Character Set Support

JIRA ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) Supplement Multi-byte Character Set Support PART Addenda PART Addenda PART Addenda PART Addenda PART Addenda STATUS: Final Text - November, This is a draft document - do not circulate, or quote except with the approval of NEMA. Final Text - //

Scope and Field of Application This Supplement to the DICOM standard specifies a method to handle multi-byte character sets, such as Japanese character sets. This Supplement includes a number of Addenda to existing Parts of DICOM.. PART Addenda. PART Addenda. PART Addenda. PART Addenda. PART Addenda 0 Final Text - //

PART Addenda Digital Imaging and Communications in Medicine (DICOM) PART Addenda: Multi-byte Character Set Support Items to be added or changed in PS.: Data Structures and Encoding Item # Add the following to Section Normative references: 0 ISO/IEC 0: Information technology - Character code structure and extension techniques JIS X 00- Code for Information Interchange JIS X 00-0 Code for the Japanese Graphic Character set for information interchange JIS X 0-0 Code of the supplementary Japanese Graphic Character set for information interchange Item # Add Section. to Section Definitions, and remove sections.0. CODED CHARACTER SET and.0. CONTROL CHARACTER. 0. Character handling definitions This part of the standard makes use of the following terms defined in ISO/IEC 0:l: a) Coded character set; code b) Code extension c) Control character d) To designate e) Escape sequence f) Graphic character g) To invoke Final Text - //

PART Addenda Item # Make the following correction to Section Symbols and abbreviations: JIRA JIRA Item # Japanese Industry Radiology Apparatus should read Japan Industries Association of Radiation Apparatus Make the following changes to Section Value encoding: 0 Value encoding A Data Set is constructed by encoding the values of Attributes specified in the Information Object Definition (IOD) of a Real-World Object. The specific content and semantics of these Attributes are specified in Information Object Definitions (see PS.). The range of possible data types of these values and their encoding are specified in this section. The structure of a Data Set, which is composed of Data Elements containing these values, is specified in Section. Throughout this part, as well as other parts of the DICOM Standard, Tags are used to identify both specific Attributes and their corresponding Data Elements.. Support of character repertoires Values that are text or character strings can be composed of Graphic and Control Characters. The Graphic Character set, independent of its encoding, is referred to as a Character Repertoire. Depending on the native language context in which Application Entities wish to exchange data using the DICOM Standard, different Character Repertoires will be used. The Character Repertoires supported by DICOM are defined in ISO. Item #- Add the following paragraph: 0 In addition, DICOM supports the following Character Repertoires for the Japanese language: JIS X 00- Code for Information Interchange JIS X 00-0 Code for the Japanese Graphic Character set for information interchange JIS X 0-0 Code of the supplementary Japanese Graphic Character set for information interchange.. REPRESENTATION OF ENCODED CHARACTER VALUES Final Text - //

PART Addenda As defined in the ISO Standards referenced in this section, byte values used for encoded representations of characters are represented in this section as two decimal numbers in the form column/row. This means that the value can be calculated as (column * ) + row, e.g., 0/ corresponds to the value (BH). NOTE Item #- Two digit hex notation will be used throughout the remainder of this standard to represent character encoding. The column/row notation is used only within Section. to simplify any cross referencing with applicable ISO standards. Modify the following table and add a note:. 0 The byte encoding space is divided into four ranges of values: CL bytes from 00/00 to 0/ GL bytes from 0/00 to 0/ CR bytes from 0/00 to 0/ GR bytes from 0/00 to / NOTE ISO does not differentiate between a code element, e.g. G0, and the area in the code table, e.g. GL, where it is invoked. The term G0 specifies the code element as well as the area in the code table. In ISO/IEC 0 there is a clear distinction between the code elements (G0, G, G, and G) and the areas in which the code elements are invoked (GL or GR). In this Standard the nomenclature of ISO/IEC 0 is used. Item #- Modify the first sentence of the following paragraph: 0 The Control Character set C0 shall be invoked in CL and the Graphic Character sets G0 and G in GL and GR respectively. Only some Control Characters from the C0 set are used in DICOM (see Section..), and characters from the C set shall not be used... GRAPHIC CHARACTERS A Character Repertoire, or character set, is a collection of Graphic Characters specified independently of their encoding. In DICOM all references to Character Repertoires are made via the ISO registration number specified in ISO and are of the form ISO-IR xxx. Final Text - //

PART Addenda Many standards, including ISO, specify Coded Character Sets. Coded Character Sets are Graphic Character sets along with the one to one relationship between each character of the set and its coded representation.... Default character repertoire The default repertoire for character strings in DICOM shall be the Basic G0 Set of the International Reference Version of ISO :0 (ISO-IR ). See Annex E for a table of the DICOM default repertoire and its encoding. NOTE This Basic G0 Set is identical with the common character set of ISO.... Extension or replacement of the default character repertoire Item #- Replace the first paragraph: 0 0 DICOM Application Entities (AEs) that extend or replace the default repertoire convey this information in the Specific Character Set (000,000) Attribute. NOTE The Attribute Specific Character Set (000,000) is encoded using a subset of characters from ISO-IR. See the definition for the Value Representation (VR) of Code String (CS) in Table... For Data Elements with Value Representations of SH (Short String), LO (Long String), ST (Short Text), LT (Long Text), or PN (Person Name) the default character repertoire may be extended or replaced (these Value Representations are described in more detail in Section.). If such an extension or replacement is used, the replacement or extension shall be identified in the Attribute Specific Character Set of the SOP Common Module (000,000) (see PS.), and the fact shall be stated in the Conformance Statement. PS. gives conformance guidelines. Item #- Remove note and renumber : NOTES. Preferred repertoires as defined in ENV 0 and ENV 0 for use in Western and Eastern Europe, respectively, are: ISO-IR 00, ISO-IR 0, ISO- IR, ISO-IR. See Section.... Information Object Definitions using different character sets cannot rely per se on lexical ordering or string comparison of data elements represented as character strings. These operations can only be carried out within a given character repertoire and not across repertoire boundaries. Final Text - //

PART Addenda... Encoding of character repertoires Item #- Modify Section... as follows:: The -bit default character repertoire can be replaced for use in Value Representations SH, LO, ST, LT, and PN with one of the single-byte codes defined in PS.. NOTE This replacement character repertoire does not apply to other textual Value Representations (AE and CS). 0 0 The replacement character repertoire shall be specified in value of the Attribute Specific Character Set (000,000). Defined Terms for the Attribute Specific Character Set are specified in PS.. NOTES. The code table is split into the GL area which supports a character set only (bit combinations 0/0 to 0/) plus SPACE in 0/00 and the GR area which supports either a or character set (bit combinations 0/0 to / or 0/00 to /). The default character set (ISO-IR ) is always invoked in the GL area.. All character sets specified in ISO include ISO-IR. This set will always be invoked in the GL area of the code table and is the equivalent of ASCII (ANSI X.:), whereas the various extension repertoires are mapped onto the GR area of the code table.. The -bit code table of JIS X 00 includes ISO-IR (romaji alphanumeric characters) as the G0 code element and ISO-IR (katakana phonetic characters) as the G code element. ISO-IR is identical to ISO-IR, except that bit combination 0/ represents a (YEN SIGN) and bit combination 0/ represents an over-line. Item #- Modify the first sentence of the following paragraph. Two character codes of the single-byte character sets invoked in the GL area of the code table, 0/00 and 0/, have special significance in the DICOM Standard. The character SPACE, represented by bit combination 0/00, shall be used for the padding of Data Element Values that are character strings. The Graphic Character represented by the bit combination 0/, \ (BACKSLASH) in the repertoire ISO-IR, shall only be used in character strings with Final Text - //

PART Addenda Value Representations of ST and LT (see Section.). Otherwise, the character code 0/ is used as a separator for multiple valued Data Elements (see Section.) NOTE When the value of the Attribute Specific Character Set (000,000) is either IR or ISO 0 IR, the graphic character represented by the bit combination 0/ is a (YEN SIGN) in the character set of ISO-IR. The character DELETE (bit combination 0/) shall not be used in DICOM character strings. Item #-0 Replace following paragraph. 0 0 The replacement Character Repertoire specified in value of the Attribute Specific Character Set (000,000) (or the default Character Repertoire if value is empty) may be further extended with additional Coded Character Sets, if needed. The additional Coded Character Sets and extension mechanism shall be specified in additional values of the Attribute Specific Character Set. If Attribute Specific Character Set (000,000) has a single value, the DICOM SOP Instance supports only one single-byte code table and no Code Extension techniques. If Attribute Specific Character Set (000,000) has multiple values, the DICOM SOP Instance supports Code Extension techniques as described in ISO/IEC 0:. NOTE Considerations on the Handling of Unsupported Character Sets: In DICOM, character sets are not negotiated between Application Entities but are indicated by a conditional Attribute of the SOP Common Module. Therefore, implementations may be confronted with character sets that are unknown to them. The machine should print or display such characters by replacing all unknown characters with the four characters \nnn, where nnn is the three digit octal representation of each byte. An example of this for an ASCII based machine would be as follows: Character String: Günther Encoded representation: 0/0 / 0/ 0/0 0/0 0/0 0/0 ASCII based machine: G\nther Implementations may also encounter Control Characters which are unknown. The implementations should also replace each Control Character with the four characters \nnn, where nnn is the three digit octal representation of each byte. Final Text - //

PART Addenda Item #- Add Section...: 0... Code Extension Techniques For Data Elements with Value Representations of SH (Short String), LO (Long String), ST (Short Text), LT (Long Text), or PN (Person Name), the default character repertoire or the character repertoire specified by Attribute Specific Character Set (000,000), value, may be extended using the Code Extension techniques specified by ISO/IEC 0:. If such Code Extension techniques are used, the related Specific Character Set or Sets shall be specified by value to value n of the Attribute Specific Character Set (000,000) of the SOP Common Module (see PS. Addenda), and shall be stated in the Conformance Statement. NOTES. Defined Terms for Specific Character Set (000,000) are defined in PS... Support for Japanese kanji (ideographic), hiragana (phonetic), and katakana (phonetic) characters is defined in PS.. Definition of Chinese, Korean, and other multi-byte character sets awaits consideration by the appropriate standards organizations. Item #- Add Section...: 0... Usage of Code Extension DICOM supports Code Extension techniques if the Attribute Specific Character Set (000,000) is multi-valued. The method employed for Code Extension in DICOM is as described in ISO/IEC 0:. The following assumptions shall be made and the following restrictions shall apply:... Assumed Initial States - Code element G0 and code element G (in -bit mode only) are always invoked in the GL and GR areas of the code table respectively. Designated character sets for these code elements are immediately in use. Code elements G and G are not used. - The primary set of Control Characters shall always be designated as the C0 code element and this shall be invoked in the CL area of the code table. The C code element shall not be used.... Restrictions for Code Extension Final Text - //

PART Addenda 0 0 0 - As code elements G0 and G always have shift status, Locking Shifts (SI, SO) are not required and shall not be used. - As code elements G and G are not used, Single Shifts (SS and SS) cannot be used.... Requirements - The character set specified by value of the Attribute Specific Character Set (000,000), or the default character repertoire if value is missing, shall be active at the beginning of each textual Data Element value, and at the beginning of each line (i.e., after a CR and/or LF) or page (i.e., after an FF). - If within a textual value a character set other than the one specified in value of the Attribute Specific Character Set (000,000), or the default character repertoire if value is missing, has been invoked, there shall be a switch to the character set specified in the value, or the default character repertoire if value is missing, in the following instances: before the end of line (i.e., before the CR and/or LF) before the end of a page (i.e. before the FF) before the end of a Data Element value (e.g. before the 0/ character code which seperates multiple textual Data Element Values 0/ correponds to \ (BACKSLASH) in the case of default repertoire IR- or (YEN SIGN) in the case of IR- ). before the ^ and = delimiters separating name components and name component groups in Data Elements with a VR of PN. NOTE These two requirements allow an application to skip lines, values, or components in a textual data element and start the new line with a defined character set without the need to track the character set changes in the text skipped. A similar restriction appears in the RFCs describing the use of multibyte character sets over the Internet. An Escape Sequence switching to the value or default Specific Character Set is not needed within a line, value, or component if no Code Extensions are present.... Levels of Implementation and Initial Designation a) Attribute Specific Character Set (000,000) not present: -bit code Final Text - //

PART Addenda Implementation level: ISO 0 Level - Elementary -bit code (code-level identifier ) Initial designation: ISO-IR (ASCII) as G0. Code Extension shall not be used. b) Attribute Specific Character Set (000,000) single value: -bit code Implementation level: ISO 0 Level - Elementary -bit code (code-level identifier ) 0 Initial designation: One of the ISO -defined character sets, or the -bit code table of JIS X 00 specified by value of the Attribute Specific Character Set (000,000), as G0 and G. Code Extension shall not be used. c) Attribute Specific Character Set (000,000) multi-valued: -bit code Implementation level: ISO 0 Level - Redesignation of Graphic Character Sets within a Code (code-level identifier ) 0 Initial designation: One of the ISO -defined character sets, or the -bit code table of JIS X 00 specified by value of the Attribute Specific Character Set (000,000), as G0 and G. If value of the Attribute Specific Character Set (000,000) is empty, ISO-IR (ASCII) is assumed. All character sets specified in the various values of Attribute Specific Character Set (000,000), including value, may participate in Code Extension... Control Characters Item #- Add the Control Character, ESC as follows: Textual data that is interchanged may require some formatting information. Control Characters are used to indicate formatting, but their use in DICOM is kept to a minimum since some machines may handle them inappropriately. ISO :0 and ISO :0 define Final Text - //

PART Addenda Control Characters. As shown in Table..- below, only a subset of four Control Characters from the C0 set shall be used in DICOM for the encoding of Control Characters in text strings. Table.- DICOM Control Characters and their encoding Acronym Name Coded Value LF Line Feed 00/0 FF Form Feed 00/ CR Carriage Return 00/ ESC Escape 0/ 0 0 In text strings a new line shall be represented as CR LF. NOTE Some machines (such as UNIX based machines) may interpret LF (00/0) as a new line. In such cases, it is expected that the DICOM format is converted to the correct internal representation for that machine.. Value representation (VR) The Value Representation of a Data Element describes the data type and format of that Data Element's Value(s). PS. lists the VR of each Data Element by Data Element Tag. Values with VRs constructed of character strings, except in the case of the VR UI, shall be padded with SPACE characters (0H, in the Default Character Repertoire) when necessary to achieve even length. Values with a VR of UI shall be padded with a single trailing NULL (00H) character when necessary to achieve even length. Values with a VR of OB shall be padded with a single trailing NULL byte value (00H) when necessary to achieve even length. An individual Value, including padding, shall not exceed the Length of Value. For multivalued fields see Section.. NOTE The length of Value Representations for which the Character Repertoire can be extended or replaced are expressly specified in characters rather than bytes in Table.-. This is because the mapping from a character to the number of bytes used for that character s encoding may be dependent on the character set used. Escape Sequences used for Code Extension shall not be included in the count of characters. Table.- DICOM value representations Final Text - // 0

PART Addenda Item #- Some changes have been made in Table.-: DICOM value representations, to the Definition, Character Repertoire and Length of Value columns of rows with VR Name equal to SH, LO, ST, LT, PN. Only changes to Table.- are specified below. See PS.. See Editor s note/instructions within the table. VR Definition Character Length of Name Repertoire Value LO A character string that may be padded with Default Character chars Long leading and/or trailing spaces. The character Repertoire and/or maximum String code CH (the BACKSLASH \ in ISO-IR as defined by (see NOTE ) shall not be present, as it is used as the (000,000). in.) delimiter between values in multiple valued data elements. The string shall not have Control Characters except for ESC. LT A character string that may contain one or Default Character 00 chars Long more paragraphs. It may contain the Graphic Repertoire and/or maximum Text Character set and the Control Characters, CR, as defined by (see NOTE LF, FF, and ESC. It may be padded with (000,000). in.) trailing spaces, which may be ignored, but leading spaces are considered to be significant. Data Elements with this VR shall not be multi-valued and therefore character code CH (the BACKSLASH \ in ISO-IR ) may be used. PN A character string encoded using a Default Character chars Person component convention. The string may be Repertoire and/or maximum Name padded with trailing spaces. The five as defined by per components in their order of occurrence are: (000,000) component family name complex, given name complex, excluding group middle name, name prefix, name suffix. Any Control (see NOTE of the five components may be an empty Characters LF, in.) string. The component delimiter shall be the FF, and CR but caret ^ character (EH). Delimiters are allowing Control required for interior null components. Character ESC. Final Text - //

PART Addenda Trailing null components and their delimiters may be omitted. Multiple entries are permitted in each component and are encoded as natural text strings, in the format preferred by the named person. This conforms to the ANSI HISPP MSDS Person Name common data type. This group of five components is referred to as a Person Name component group. For the purpose of writing names in ideographic characters and in phonetic characters, up to groups of components (see Annex I examples and ) may be used. The delimiter for component groups shall be the equals character = (DH). The three component groups of components in their order of occurrence are: a single-byte character representation, an ideographic representation, and a phonetic representation. Any component group may be absent, including the first component group. In this case, the person name may start with one or more = delimiters. Delimiters are required for interior null component groups. Trailing null component groups and their delimiters may be omitted. Precise semantics are defined for each component group. See section... Examples: Rev. John Robert Quincy Adams, B.A. M.Div. Final Text - //

PART Addenda Adams^John Robert Quincy^^Rev.^B.A. M.Div. [One family name; three given names; no middle name; one prefix; two suffixes.] Susan Morrison-Jones, Ph.D., Chief Executive Officer Morrison-Jones^Susan^^^Ph.D., Chief Executive Officer [Two family names; one given name; no middle name; no prefix; two suffixes.] John Doe Doe^John [One family name; one given name; no middle name, prefix, or suffix. Delimiters have been omitted for the three trailing null components.] (for examples of the encoding of Person Names using multi-byte character sets see Annex I) NOTES:. This five component convention is also used by HL as defined in ASTM E-- and further specialized by the ANSI MSDS.. In typical American and European usage the first occurrence of given name would represent the first name. The second and subsequent occurrences of the given name would typically be treated as a middle name(s). The middle name component is retained for the purpose of backward compatibility with existing standards.. The Degree component present in ASTM E-- is absorbed into the Final Text - //

PART Addenda Suffix component.. The implementor should remain mindful of earlier usage forms which represented given names as first and middle and that translations to and from this previous typical usage may be required.. For reasons of backward compatibility with versions of this standard prior to V.0, person names might be considered a single family name complex (single component without "^" delimiters). SH A character string that may be padded with Default Character chars Short leading and/or trailing spaces. The character Repertoire and/or maximum String code 0CH (the BACKSLASH \ in ISO-IR as defined by (see NOTE ) shall not be present, as it is used as the (000,000). in.) delimiter between values for multiple data elements. The string shall not have Control Characters except ESC. ST A character string that may contain one or Default Character 0 chars Short more paragraphs. It may contain the Graphic Repertoire and/or maximum Text Character set and the Control Characters, CR, as defined by (see NOTE LF, FF, and ESC. It may be padded with (000,000). in.) trailing spaces, which may be ignored, but leading spaces are considered to be significant. Data Elements with this VR shall not be multi-valued and therefore character code CH (the BACKSLASH \ in ISO-IR ) may be used. Final Text - //

PART Addenda Item #- Add Section..: 0 0.. Ideograph and phonetic characters in Data Elements with VR of PN Character strings representing person names are encoded using a convention for PN value representations based on component groups with components. For the purpose of writing names in ideographic characters and in phonetic characters, up to component groups may be used. The delimiter of the component group shall be the equals character = (DH). The three component groups in their order of occurrence are: a singlebyte representation, an ideographic representation, and a phonetic representation. Any component group may be absent, including the first component group. In this case, the person name may start with one or more = delimiters. Delimiters are also required for interior null component groups. Trailing null component groups and their delimiters may be omitted. The first component group shall be encoded using a single-byte character set with no Code Extensions. The character set shall be the one specified by the Attribute Specific Character Set (000,000), value. If Attribute Specific Character Set (000,000) is not present, the default Character Repertoire ISO-IR shall be used. The second group shall be used for ideographic characters. The character sets used will usually be those from Attribute Specific Character Set (000,000), value through n, and may use ISO 0 escapes. The third group shall be used for phonetic characters. The character sets used shall be those from Attribute Specific Character Set (000,000), value through n, and may use ISO 0 escapes. Delimiter characters ^ and = are taken from the character set specified by value of the Attribute Specific Character Set (000,000). If Attribute Specific Character Set (000,000), value is not present, the default Character Repertoire ISO-IR shall be used. At the beginning of the value of the Person Name data element, the following initial condition is assumed: if Attribute Specific Character Set (000,000), value is not present, the default Character Repertoire ISO-IR is invoked, and if the Attribute Specific Character Set (000,000), value is present, the character set specified by value of the Attribute is invoked. Final Text - //

PART Addenda At the end of the value of the Person Name data element, and before the component delimiters ^ and =, the character set shall be switched to the default character repertoire ISO-IR, if the Attribute Specific Character Set (000,000), value is not present, or if the Attribute Specific Character Set (000,000), value is present, the character set specified by value of the Attribute. The length of value of each component group is characters maximum, including the delimiter for the component group.. Value Multiplicity (VM) and Delimitation Item #- Modify the first item of the second paragraph: 0 When a Data Element has multiple Values, those Values shall be delimited as follows: - For character strings, the character CH (BACKSLASH \ in the case of the repertoire ISO IR-) shall be used as a delimiter between Values. Item # Add following Section.. to Section. Nesting of data sets: Note: Add the following clarification for when Attribute Specific Character Set (000,000), may appear in a sequence item 0.. SEQUENCE INHERITANCE An encapsulated Data Set shall only include the Specific Character Set (000,000) data element if the Attribute Specific Character Set is defined in the IOD for that sequence of items. NOTE An encapsulated Data Set does not include the Specific Character Set data element unless the Specific Character Set Attribute is defined as part of the IOD for that sequence. If an encapsulated Data Set includes the Specific Character Set Attribute, it shall apply only to the encapsulated Data Set. If the Attribute Specific Character Set is not explicitly included in an encapsulated Data Set, then the Specific Character Set value of the encapsulating Data Set applies. Item # Add a Control Character ESC to Annex E (Normative) DICOM default character repertoire. Annex E (Normative) DICOM default character repertoire Final Text - //

PART Addenda The default repertoire for character strings in DICOM is the Basic G0 Set of the International Reference Version of ISO :0 (ISO IR-). In addition, the four Control Characters LF, FF, CR, and ESC are supported. These Control Characters are a subset of the C0 set defined in ISO :0 and ISO :0. The byte encoding of the default character repertoire is pictured in Table E-. This table can be used to derive both ISO column/row byte values and hex values for encoded representations (see Section..). Final Text - //

PART Addenda Table E- DICOM Default character repertoire encoding b 0 0 0 0 0 0 0 0 b 0 0 0 0 b 0 0 0 0 b 0 0 0 0 b b b b 00 0 0 0 0 0 0 0 0 0 0 0 00 SP 0 @ P ` p 0 0 0 0! A Q a q 0 0 0 0 B R b r 0 0 0 # C S c s 0 0 0 0 $ D T d t 0 0 0 % E U e u 0 0 0 & F V f v 0 0 ' G W g w 0 0 0 0 ( H X h x 0 0 0 ) I Y i y 0 0 0 LF * : J Z j z 0 ESC + ; K [ k { 0 0 FF, < L \ l 0 CR - = M ] m } 0. > N ^ n ~ /? 0 _ o Final Text - //

PART Addenda Item # Add Annex I (Informative) Character sets and person name value representation in the Japanese Language: Annex I (Informative) Character sets and person name value representation in the Japanese Language I. Character sets for the Japanese language () JIS X 00 JIS X 00 has the following code elements: ISO-IR ISO-IR Japanese katakana (phonetic) characters ( characters) Japanese romaji (alphanumeric) characters ( characters) 0 0 JIS X 00 defines a -bit romaji code table (ISO-IR ), a -bit katakana code table (ISO-IR ), and the combination of romaji and katakana as an -bit code table (ISO-IR as G0, ISO- IR as G). The -bit romaji ISO-IR is identical to ASCII (ISO-IR ) except that bit combination 0/ represents a yen sign and bit combination 0/ represents an over-line. These are national Graphic Character allocations in ISO. Escape Sequence (for reference) (see PS.) ISO-IR ISO-IR G0 set ESC 0/0 0/0 ESC 0/0 0/0 G set ESC 0/0 0/0 ESC 0/0 0/0 NOTE The G and G sets are not used in DICOM. () JIS X 00 JIS X 00 has the following code element: ISO-IR : Japanese kanji (ideographic), hiragana (phonetic), and katakana (phonetic) characters ( characters, -byte). () JIS X 0 JIS X 0 has the following code element: Final Text - //

PART Addenda ISO-IR : Supplementary Japanese kanji (ideographic) characters ( characters, - byte) Escape Sequence (for reference) (see PS.) ISO-IR ISO-IR G0 set ESC 0/0 0/0 ESC 0/0 0/0 0/0 G set ESC 0/0 0/0 0/0 ESC 0/0 0/0 0/0 0 NOTES : The Escape Sequence for the designation function G0-DESIGNATE -SET, has first I byte 0/0 and second I byte 0/0. There is an exception to this: The second I byte 0/0 is omitted if the Final Byte is 0/00, 0/0 or 0/0. See ISO/IEC 0. : The G and G sets are not used in DICOM. I. Internet Practice The major protocols for the Internet such as SMTP, NNTP and WWW adopt the encoding method for Japanese characters called ISO-0-JP as described in RFC, Japanese Character Encoding for Internet Messages. The method of encoding Japanese characters in the DICOM standard is almost the same as ISO-0-JP, except for the following. Character sets supported for the Japanese language DICOM ASCII (ISO-IR ) JIS X 00 Katakana (ISO-IR ) JIS X 00 Romaji (ISO-IR ) JIS X 00 Kanji (ISO-IR ) JIS X 0 Kanji (ISO-IR ) Control Character set supported DICOM LF (00/0) FF (00/) CR (00/) ESC (0/) ISO-0-JP ASCII (ISO-IR ) JIS-X 00 Romaji (ISO-IR ) JIS-X 00 Kanji (ISO-IR ) ISO-0-JP LF (00/0) CR (00/) SO (00/) SI (00/) ESC (0/) I. Example of Person Name Value Representation in the Japanese Language Final Text - // 0

PART Addenda 0 Character strings representing person names are encoded using a convention for PN value representations based on component groups with components. For languages which use ideographic characters, it is sometimes necessary to write names both in ideographic characters and in phonetic characters. Ideographic characters may be required for official purposes, while phonetic characters may be needed for pronounciation and data processing purposes. For the purpose of writing names in ideographic characters and in phonetic characters, up to component groups may be used. The delimiter of the component group shall be the equals character = (DH). The three component groups in their order of occurrence are: a single byte representation, an ideograph representation, and a phonetic representation. () Example : Value of Attribute Specific Character Set (000,000) is not present. (In this case, ISO-IR is used by default.) (000,000) \ISO 0 IR Character String: 0 Encoded representation: 0/0 0/0 0/ 0/0 0/0 0/0 / 0/0 0/0 0/0 0/ 0/0 0/ 0/ 0/0 0/0 0/ 0/0 0/0 0/0 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/00 0/ 0/0 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/0 0/0 0/ 0/0 0/00 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/ 0/0 0/ 0/0 0/0 0/ 0/0 0/0 Result of representation by an ASCII-based machine: Yamada^Tarou=\0$B;ED\0(B^\0$BB@O:\0(B=\0$B$d$^$@\0(B^\0$B$?$ m$&\0(b Table I- Character sets and Escape Sequences used in Example Character Set Description Componen t Group Value of (000,000) Defined Term ISO Registration Number Standard for Code Extensio n ESC Sequence Character Set: Purpose of Use Final Text - //

PART Addenda Japanese First: Single-byte Second: Ideographi c Third: Phonetic Value : none Value : ISO 0 IR Value : none Value : ISO 0 IR Value : none ISO-IR GL ISO : ISO-IR ISO ESC GL JIS X 00: Japanese 0 0/0 kanji, hiragana, 0/0 katakana ISO-IR ISO ESC GL ISO : for delimiters 0 0/0 0/0 ISO-IR ISO ESC GL JIS X 00: Japanese 0 0/0 hiragana, and katakana 0/0 ISO-IR ISO ESC GL ISO : for delimiters 0 0/0 0/0 () Example : Value of Attribute Specific Character Set (000,000) is ISO 0 IR. (000,000) ISO 0 IR \ISO 0 IR Character String: 0 Encoded representation: /0 / /00 / 0/ /00 / /0 0/ 0/ 0/0 0/0 0/ 0/0 0/0 0/0 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/00 0/ 0/0 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/0 0/0 0/ 0/0 0/00 0/ 0/0 0/0 0/ 0/ 0/0 0/0 0/0 0/ 0/0 0/ 0/0 0/0 0/ 0/0 0/0 Result of representation by an ASCII-based machine: \\l\00\^\00\\=\0$b;ed\0(j^\0$bb@o:\0(j=\0$b$d$^$@\0 (J^\0$B$?$m$&\0(J Table I- Character sets and Escape Sequences used in Example Final Text - //

PART Addenda Character Componen Value of ISO Standard ESC Character Set: Set t Group (000,000) Registration for Code Sequence Purpose of Use Description Defined Term Number Extensio n Japanese First: Value : ISO-IR ISO ESC 0/0 GR JIS X 00: Japanese Single-byte ISO 0 IR 0 0/0 katakana ISO-IR ISO ESC 0/0 GL JIS X 00: Japanese 0 0/0 romaji for delimiters Second: Value : ISO-IR ISO ESC 0/0 GL JIS X 00: Japanese Ideographi ISO 0 IR 0 0/0 kanji, hiragana, c katakana Value : ISO-IR ISO ESC 0/0 GL JIS X 00: Japanese ISO 0 IR 0 0/0 romaji for delimiters Third: Value : ISO-IR ISO ESC 0/0 GL JIS X 00: Japanese Phonetic ISO 0 IR 0 0/0 hiragana, and katakana Value : ISO-IR ISO ESC 0/0 GL JIS X 00: Japanese ISO 0 IR 0 0/0 romaji for delimiters Final Text - //

PART Addenda Digital Imaging and Communications in Medicine (DICOM) PART Addenda: Multi-byte Character Set Support Items to be added or changed in PS.: Information Object Definitions Item # Add the following to Section Normative references: ISO/IEC 0: Information technology - Character code structure and extension techniques Item # Add the following to PS. Section Definitions: 0. Character handling definitions This part of the standard makes use of the following terms defined in ISO/IEC 0:l: a) Coded character set; code b) Code extension c) Escape sequence Item # Make the following correction to Section Symbols and abbreviations: JIRA Item # Japan Industries Association of Radiation Apparatus Make the following changes to Section C.. Patient identification module, Table C.- Patient identification module Attributes: Table C.- Patient identification module attributes Attribute Name Tag Attribute Description Patient s Name (000,000) Patient s full name Final Text - //

PART Addenda Item # Make the following changes to Section C... PATIENT MODULE, Table C.- Patient module Attributes: Note: For use in MIPS standard-, the Attribute Ethnic Group (000,0) has been removed from Table C.-. Table C.- Patient module attributes Attribute Name Tag Attribute Description Patient s Name (000,000) Patient s full name Item # Make the following changes to Section C.. Patient summary module, Table C.- Patient summary module attributes: Table C.- Patient summary module attributes Attribute Name Tag Type Attribute Description Patient s Name (000,000) Patient s full name Item # Make the following changes to Section C. General modules: 0 C. General modules The SOP common module shall be mandatory for all DICOM IODs. C.. SOP common module Table C.- defines the Attributes which are required for proper functioning and identification of the associated SOP Instances. They do not specify any semantics about the real-world object represented by the IOD. Table C.- SOP common module attributes Attribute Name Tag Type Attribute Description SOP Class UID (000,00) see Uniquely identifies the SOP Class. C... See PS.. Final Text - //

PART Addenda SOP Instance UID (000,00) see Uniquely identifies the SOP Instance. C... See PS.. Specific Character Set (000,000) C Character Set that expands or replaces the Basic Graphic Set. Required if an expanded or replacement character set is used. See C... for Defined Terms. Instance Creation Date (000,00) Date the SOP Instance was created. Instance Creation Time (000,00) Time the SOP Instance was created. Instance Creator UID (000,00) Uniquely identifies device which created the SOP Instance. C... SOP COMMON ATTRIBUTE DESCRIPTIONS C... 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. When encoded they shall be equal to their respective attributes in the DIMSE services and the file meta information header (media storage see Part 0). C... Specific character set Item #- Modify the first paragraph: 0 Specific Character Set (000,000) identifies the character set that expands or replaces the basic graphic set (ISO ) for values of data elements that have value representation of SH, LO, ST, PN or LT. See PS.. Item #- Replace second paragraph, and add Table C.- and a note: If the Attribute Specific Character Set (000,000) is not present or has only a single value, Code Extension techniques are not used. Defined Terms for the Attribute Specific Character Set (000,000), when single valued, are International Registration Numbers as per ISO (e.g., IR 00 for Latin alphabet No. ). See Table C.-. Final Text - //

PART Addenda Table C.- Defined Terms for single-byte character sets without Code Extensions Character Set Defined ISO registration Number of Code Character Set Description Term number characters element Default repertoire none ISO-IR G0 ISO : Latin alphabet No. ISO_IR 00 ISO-IR 00 G Supplementary set ISO-IR G0 ISO : Latin alphabet No. ISO_IR 0 ISO-IR 0 G Supplementary set ISO-IR G0 ISO : Latin alphabet No. ISO_IR 0 ISO-IR 0 G Supplementary set ISO-IR G0 ISO : Latin alphabet No. ISO_IR 0 ISO-IR 0 G Supplementary set ISO-IR G0 ISO : Cyrillic ISO_IR ISO-IR G Supplementary set ISO-IR G0 ISO : Arabic ISO_IR ISO-IR G Supplementary set ISO-IR G0 ISO : Greek ISO_IR ISO-IR G Supplementary set ISO-IR G0 ISO : Hebrew ISO_IR ISO-IR G Supplementary set ISO-IR G0 ISO : Latin alphabet No. ISO_IR ISO-IR G supplementary set ISO-IR G0 ISO : Japanese ISO_IR ISO-IR G JIS X 00: Katakana ISO-IR G0 JIS X 00: Romaji NOTE To use the single-byte code table of JIS X00, the value of Attribute Specific Character Set (000,000), value should be IR. This means that ISO-IR is designated as the G code element which is invoked in the GR area. It should be understood that, in addition, ISO-IR is designated as the G0 code element and this is invoked in the GL area. Item #- Add the following paragraph, and Tables C.- and C.-: 0 If the Attribute Specific Character Set (000,000) has more than one value, Code Extension techniques are used and Escape Sequences may be encountered in all character sets. In order to indicate the presence of Code Extension, the Defined Terms for the repertoires have the prefix ISO 0, e.g., ISO 0 IR 00 for the Latin Alphabet No.. See Table - and Final Text - //

PART Addenda Table -. Table - describes single-byte character sets for value to value n of the Attribute Specific Character Set (000,000), and Table - describes multi-byte character sets for value to value n of the Attribute Specific Character Set (000,000). NOTE A prefix other than ISO 0 may be needed in the future if other Code Extension techniques are adopted. Table C.- Defined Terms for single-byte character sets with Code Extensions Character Set Description Defined Term Standard for Code Extensio n ESC sequence Default ISO 0 IR ISO 0 ESC 0/0 repertoire 0/0 Latin ISO 0 IR ISO 0 ESC 0/ alphabet 00 0/0 No. ISO 0 ESC 0/0 0/0 Latin ISO 0 IR ISO 0 ESC 0/ alphabet 0 0/0 No. ISO 0 ESC 0/0 0/0 Latin alphabet ISO 0 IR 0 ISO 0 ESC 0/ 0/0 No. ISO 0 ESC 0/0 0/0 Latin ISO 0 IR ISO 0 ESC 0/ alphabet 0 0/0 No. ISO 0 ESC 0/0 0/0 Cyrillic ISO 0 IR ISO 0 ESC 0/ 0/ ISO 0 ESC 0/0 0/0 Arabic ISO 0 IR ISO 0 ESC 0/ 0/0 ISO 0 ESC 0/0 0/0 ISO registratio n number Number of character s Code element Character Set ISO-IR G0 ISO ISO-IR G Supplementary 00 set ISO-IR G0 ISO ISO-IR 0 G Supplementary set ISO-IR G0 ISO ISO-IR G Supplementary 0 set ISO-IR G0 ISO ISO-IR G Supplementary 0 set ISO-IR G0 ISO ISO-IR G Supplementary set ISO-IR G0 ISO ISO-IR G Supplementary set ISO-IR G0 ISO Final Text - //

PART Addenda Greek ISO 0 IR ISO 0 ESC 0/ 0/0 ISO 0 ESC 0/0 0/0 Hebrew ISO 0 IR ISO 0 ESC 0/ 0/0 ISO 0 ESC 0/0 0/0 Latin ISO 0 IR ISO 0 ESC 0/ alphabet 0/ No. ISO 0 ESC 0/0 0/0 Japanese ISO 0 IR ISO 0 ESC 0/0 0/0 ISO 0 ESC 0/0 0/0 ISO-IR G Supplementary set ISO-IR G0 ISO ISO-IR G Supplementary set ISO-IR G0 ISO ISO-IR G Supplementary set ISO-IR G0 ISO ISO-IR G JIS X 00: Katakana ISO-IR G0 JIS X 00- : Romaji NOTE If the Attribute Specific Character Set (000,000) has more than one value and value is empty, it is assumed that value is ISO 0 IR. Table C.- Defined Terms for multiple-byte character sets with Code Extensions Character Defined Term Standard ESC sequence ISO Number Code Character Set Set for Code registratio of element Description Extensio n number character n s Japanese ISO 0 IR ISO 0 ESC 0/0 ISO-IR G0 JIS X 00: 0/0 Kanji ISO 0 IR ISO 0 ESC 0/0 0/0 0/0 ISO-IR G0 JIS X 0: Supplementary Kanji set Final Text - //

PART Addenda Digital Imaging and Communications in Medicine (DICOM) PART Addenda: Multi-byte Character Set Support Items to be added or changed in PS.: Service Class Specifications Item # Make the following correction to Section Symbols and abbreviations: JIRA JIRA Item # Japanese Industry Radiology Apparatus should read Japan Industries Association of Radiation Apparatus Add note to Section C... Wild card matching: 0 C... Wild card matching If the Attribute is not a date, time, signed long, signed short, unsigned long, floating point single, floating point double, other byte string, other word string, attribute tag, decimal string, integer string or UID and the value specified in the request contains any occurrence of an "*" or a "?", then "*" shall match any sequence of characters (including a zero length value) and "?" shall match any single character. This matching is case sensitive. See PS. for Value Representations. NOTE. Wild-card matching on a value of "*" is equivalent to universal matching.. The wild card matching method specified by DICOM might not be supported by some non-dicom multi-byte character text processors. Item #- Add to Section C... Request Identifier Structure an additional bullet item. C... Request Identifier Structure An Identifier in a C-FIND request shall contain Final Text - // 0

PART Addenda - Key Attributes values to be matched against the values of storage SOP Instances managed by the SCP; - Query/Retrieve Level, element (000,00) which defines the level of the query. - Conditionally, the Attribute Specific Character Set (000,000). This Attribute is required if expanded or replacement character sets are used. Item # Add the third item to the first paragraph of Section C... Response identifier structure: 0 C... Response identifier structure An Identifier in a C-FIND response shall contain - Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request - Query/Retrieve Level, element (000,00) which defines the level of the query. The Query/Retrieve level shall be equal to the level specified in the request. - Conditionally, the Attribute Specific Character Set (000,000). This Attribute is required if expanded or replacement character sets are used. Final Text - //

PART Addenda Digital Imaging and Communications in Medicine (DICOM) PART Addenda: Multi-byte Character Set Support Items to be added or changed in PS.: Conformance Item # Add a note after the first sentence in Section A. Support of extended character sets: 0 0 A. Support of extended character sets Any support for Extended Character Sets shall be described here. NOTE The previous DICOM standard did not specify a method of encoding multi-byte characters, such as Japanese characters. However, the present DICOM standard now allows Code Extension Techniques for multi-byte characters. Therefore every DICOM implementation should take into account this enhancement. It is an implementation choice whether or not an Application Entity supports multi-byte characters. But, when an Application Entity which does not support Code Extension Techniques receives a Data Set which includes multi-byte characters from another Application Entity, misrepresentation of characters may occur. It is the responsibility of the Application Entity which receives the Data Sets to take whatever action is considered necessary to minimize the effect of misrepresented characters. It is not the responsibility of the sending Application Entity to take such action. Final Draft for Letter Ballot - ////

PART Addenda Digital Imaging and Communications in Medicine (DICOM) PART Addenda: Multi-byte Character Set Support Items to be added or changed in PS.: Data Dictionary Item # Make the following change to Section, Registry of DICOM data elements. (The Value Multiplicity of the attribute Specific Character Set (000,000) has been changed from to -n). Registry of DICOM data elements Tag Name VR VM Permitted (000,000) Specific Character Set CS -n Values Final Draft for Letter Ballot - ////