DOCSLIB.ORG

DICOM PS3.5 2013 - Data Structures and Encoding Page 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DICOM PS3.5 2013 - Data Structures and Encoding Page 2 PS3.5 DICOM PS3.5 2013 - Data Structures and Encoding Page 2 PS3.5: DICOM PS3.5 2013 - Data Structures and Encoding Copyright © 2013 NEMA - Standard - DICOM PS3.5 2013 - Data Structures and Encoding Page 3 Table of Contents Notice and Disclaimer ........................................................................................................................................... 11 Foreword ............................................................................................................................................................ 13 1. Scope and Field of Application ............................................................................................................................. 15 2. Normative References ....................................................................................................................................... 17 3. Definitions ....................................................................................................................................................... 19 3.1. Reference Model Definitions ......................................................................................................................... 19 3.2. ACSE Service Definitions ............................................................................................................................. 19 3.3. Presentation Service Definitions .................................................................................................................... 19 3.4. Object Identification Definitions ...................................................................................................................... 19 3.5. DICOM Introduction and Overview Definitions .................................................................................................. 19 3.6. DICOM Conformance Definitions ................................................................................................................... 19 3.7. DICOM Information Object Definitions ............................................................................................................. 19 3.8. DICOM Service Class Specifications Definitions ............................................................................................... 20 3.9. DICOM Network Communication Support For Message Exchange Definitions ......................................................... 20 3.10. DICOM Data Structures and Encoding Definitions ........................................................................................... 20 3.11. Character Handling Definitions .................................................................................................................... 21 4. Symbols and Abbreviations ................................................................................................................................. 23 5. Conventions ..................................................................................................................................................... 25 6. Value Encoding ................................................................................................................................................ 27 6.1. Support of Character Repertoires ................................................................................................................... 27 6.1.1. Representation of Encoded Character Values ............................................................................................ 27 6.1.2. Graphic Characters .............................................................................................................................. 28 6.1.2.1. Default Character Repertoire ........................................................................................................... 28 6.1.2.2. Extension or Replacement of the Default Character Repertoire ............................................................... 28 6.1.2.3. Encoding of Character Repertoires .................................................................................................... 29 6.1.2.4. Code Extension Techniques ............................................................................................................ 30 6.1.2.5. Usage of Code Extension ................................................................................................................ 30 6.1.2.5.1. Assumed Initial States .............................................................................................................. 30 6.1.2.5.2. Restrictions for Code Extension ................................................................................................. 31 6.1.2.5.3. Requirements ......................................................................................................................... 31 6.1.2.5.4. Levels of Implementation and Initial Designation ............................................................................ 31 6.1.3. Control Characters ............................................................................................................................... 32 6.2. Value Representation (VR) ........................................................................................................................... 32 6.2.1. Person Name (PN) Value Representation ................................................................................................. 39 6.2.1.1. Examples of PN VR and Notes ......................................................................................................... 39 6.2.1.2. Ideographic and Phonetic Characters in Data Elements with VR of PN ..................................................... 40 6.2.2. Unknown (UN) Value Representation ....................................................................................................... 41 6.3. Enumerated Values and Defined Terms .......................................................................................................... 41 6.4. Value Multiplicity (VM) and Delimitation ........................................................................................................... 42 7. The Data Set .................................................................................................................................................... 43 7.1. Data Elements ........................................................................................................................................... 43 7.1.1. Data Element Fields ............................................................................................................................. 44 7.1.2. Data Element Structure with Explicit VR .................................................................................................... 44 7.1.3. Data Element Structure with Implicit VR .................................................................................................... 45 7.2. Group Length ............................................................................................................................................ 46 7.3. Big Endian Versus Little Endian Byte Ordering ................................................................................................. 46 7.4. Data Element Type ..................................................................................................................................... 47 7.4.1. Type 1 Required Data Elements .............................................................................................................. 47 7.4.2. Type 1C Conditional Data Elements ......................................................................................................... 47 7.4.3. Type 2 Required Data Elements .............................................................................................................. 47 7.4.4. Type 2C Conditional Data Elements ......................................................................................................... 48 7.4.5. Type 3 Optional Data Elements ............................................................................................................... 48 7.4.6. Data Element Types Within A Sequence ................................................................................................... 48 7.5. Nesting of Data Sets ................................................................................................................................... 48 7.5.1. Item Encoding Rules ............................................................................................................................. 49 7.5.2. Delimitation of The Sequence of Items ..................................................................................................... 49 7.5.3. Sequence Inheritance ........................................................................................................................... 51 - Standard - Page 4 DICOM PS3.5 2013 - Data Structures and Encoding 7.6. Repeating Groups ...................................................................................................................................... 51 7.7. Retired Data Elements ................................................................................................................................. 51 7.8. Private Data Elements ................................................................................................................................. 52 7.8.1. Private Data Element Tags ...................................................................................................................
Load more

Recommended publications
  • International Code Council 2009/2010 Code Development Cycle Proposed Changes to the 2009 Editions Of
    INTERNATIONAL CODE COUNCIL 2009/2010 CODE DEVELOPMENT CYCLE PROPOSED CHANGES TO THE 2009 EDITIONS OF THE INTERNATIONAL BUILDING CODE® INTERNATIONAL ENERGY CONSERVATION CODE® INTERNATIONAL EXISTING BUILDING CODE® INTERNATIONAL FIRE CODE® INTERNATIONAL FUEL GAS CODE® INTERNATIONAL MECHANICAL CODE® INTERNATIONAL PLUMBING CODE® INTERNATIONAL PRIVATE SEWAGE DISPOSAL CODE® INTERNATIONAL PROPERTY MAINTENANCE CODE® INTERNATIONAL RESIDENTIAL CODE® INTERNATIONAL WILDLAND-URBAN INTERFACE CODE® ® INTERNATIONAL ZONING CODE October 24 2009 – November 11, 2009 Hilton Baltimore Baltimore, MD First Printing Publication Date: August 2009 Copyright © 2009 By International Code Council, Inc. ALL RIGHTS RESERVED. This 2009/2010 Code Development Cycle Proposed Changes to the 2009 International Codes is a copyrighted work owned by the International Code Council, Inc. Without advanced written permission from the copyright owner, no part of this book may be reproduced, distributed, or transmitted in any form or by any means, including, without limitations, electronic, optical or mechanical means (by way of example and not limitation, photocopying, or recording by or in an information storage retrieval system). For information on permission to copy material exceeding fair use, please contact: Publications, 4051 West Flossmoor Road, Country Club Hills, IL 60478 (Phone 1-888-422-7233). Trademarks: “International Code Council,” the “International Code Council” logo are trademarks of the International Code Council, Inc. PRINTED IN THE U.S.A. TABLE OF CONTENTS PAGE
    [Show full text]
  • 1 Introduction 1
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • Edit Bibliographic Records
    OCLC Connexion Browser Guides Edit Bibliographic Records Last updated: May 2014 6565 Kilgour Place, Dublin, OH 43017-3395 www.oclc.org Revision History Date Section title Description of changes May 2014 All Updated information on how to open the diacritic window. The shortcut key is no longer available. May 2006 1. Edit record: basics Minor updates. 5. Insert diacritics Revised to update list of bar syntax character codes to reflect and special changes in character names and to add newly supported characters characters. November 2006 1. Edit record: basics Minor updates. 2. Editing Added information on guided editing for fields 541 and 583, techniques, template commonly used when cataloging archival materials. view December 2006 1. Edit record: basics Updated to add information about display of WorldCat records that contain non-Latin scripts.. May 2007 4. Validate record Revised to document change in default validation level from None to Structure. February 2012 2 Editing techniques, Series added entry fields 800, 810, 811, 830 can now be used to template view insert data from a “cited” record for a related series item. Removed “and DDC” from Control All commands. DDC numbers are no longer controlled in Connexion. April 2012 2. Editing New section on how to use the prototype OCLC Classify service. techniques, template view September 2012 All Removed all references to Pathfinder. February 2013 All Removed all references to Heritage Printed Book. April 2013 All Removed all references to Chinese Name Authority © 2014 OCLC Online Computer Library Center, Inc. 6565 Kilgour Place Dublin, OH 43017-3395 USA The following OCLC product, service and business names are trademarks or service marks of OCLC, Inc.: CatExpress, Connexion, DDC, Dewey, Dewey Decimal Classification, OCLC, WorldCat, WorldCat Resource Sharing and “The world’s libraries.
    [Show full text]
  • Base64 Character Encoding and Decoding Modeling
    Base64 Character Encoding and Decoding Modeling Isnar Sumartono1, Andysah Putera Utama Siahaan2, Arpan3 Faculty of Computer Science,Universitas Pembangunan Panca Budi Jl. Jend. Gatot Subroto Km. 4,5 Sei Sikambing, 20122, Medan, Sumatera Utara, Indonesia Abstract: Security is crucial to maintaining the confidentiality of the information. Secure information is the information should not be known to the unreliable person, especially information concerning the state and the government. This information is often transmitted using a public network. If the data is not secured in advance, would be easily intercepted and the contents of the information known by the people who stole it. The method used to secure data is to use a cryptographic system by changing plaintext into ciphertext. Base64 algorithm is one of the encryption processes that is ideal for use in data transmission. Ciphertext obtained is the arrangement of the characters that have been tabulated. These tables have been designed to facilitate the delivery of data during transmission. By applying this algorithm, errors would be avoided, and security would also be ensured. Keywords: Base64, Security, Cryptography, Encoding I. INTRODUCTION Security and confidentiality is one important aspect of an information system [9][10]. The information sent is expected to be well received only by those who have the right. Information will be useless if at the time of transmission intercepted or hijacked by an unauthorized person [7]. The public network is one that is prone to be intercepted or hijacked [1][2]. From time to time the data transmission technology has developed so rapidly. Security is necessary for an organization or company as to maintain the integrity of the data and information on the company.
    [Show full text]
  • Consonant Characters and Inherent Vowels
    Global Design: Characters, Language, and More Richard Ishida W3C Internationalization Activity Lead Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 1 Getting more information W3C Internationalization Activity http://www.w3.org/International/ Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 2 Outline Character encoding: What's that all about? Characters: What do I need to do? Characters: Using escapes Language: Two types of declaration Language: The new language tag values Text size Navigating to localized pages Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 3 Character encoding Character encoding: What's that all about? Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 4 Character encoding The Enigma Photo by David Blaikie Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 5 Character encoding Berber 4,000 BC Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 6 Character encoding Tifinagh http://www.dailymotion.com/video/x1rh6m_tifinagh_creation Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 7 Character encoding Character set Character set ⴰ ⴱ ⴲ ⴳ ⴴ ⴵ ⴶ ⴷ ⴸ ⴹ ⴺ ⴻ ⴼ ⴽ ⴾ ⴿ ⵀ ⵁ ⵂ ⵃ ⵄ ⵅ ⵆ ⵇ ⵈ ⵉ ⵊ ⵋ ⵌ ⵍ ⵎ ⵏ ⵐ ⵑ ⵒ ⵓ ⵔ ⵕ ⵖ ⵗ ⵘ ⵙ ⵚ ⵛ ⵜ ⵝ ⵞ ⵟ ⵠ ⵢ ⵣ ⵤ ⵥ ⵯ Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 8 Character encoding Coded character set 0 1 2 3 0 1 Coded character set 2 3 4 5 6 7 8 9 33 (hexadecimal) A B 52 (decimal) C D E F Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 9 Character encoding Code pages ASCII Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 10 Character encoding Code pages ISO 8859-1 (Latin 1) Western Europe ç (E7) Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 11 Character encoding Code pages ISO 8859-7 Greek η (E7) Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 12 Character encoding Double-byte characters Standard Country No.
    [Show full text]
  • File Formats
    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • SUPPORTING the CHINESE, JAPANESE, and KOREAN LANGUAGES in the OPENVMS OPERATING SYSTEM by Michael M. T. Yau ABSTRACT the Asian L
    SUPPORTING THE CHINESE, JAPANESE, AND KOREAN LANGUAGES IN THE OPENVMS OPERATING SYSTEM By Michael M. T. Yau ABSTRACT The Asian language versions of the OpenVMS operating system allow Asian-speaking users to interact with the OpenVMS system in their native languages and provide a platform for developing Asian applications. Since the OpenVMS variants must be able to handle multibyte character sets, the requirements for the internal representation, input, and output differ considerably from those for the standard English version. A review of the Japanese, Chinese, and Korean writing systems and character set standards provides the context for a discussion of the features of the Asian OpenVMS variants. The localization approach adopted in developing these Asian variants was shaped by business and engineering constraints; issues related to this approach are presented. INTRODUCTION The OpenVMS operating system was designed in an era when English was the only language supported in computer systems. The Digital Command Language (DCL) commands and utilities, system help and message texts, run-time libraries and system services, and names of system objects such as file names and user names all assume English text encoded in the 7-bit American Standard Code for Information Interchange (ASCII) character set. As Digital's business began to expand into markets where common end users are non-English speaking, the requirement for the OpenVMS system to support languages other than English became inevitable. In contrast to the migration to support single-byte, 8-bit European characters, OpenVMS localization efforts to support the Asian languages, namely Japanese, Chinese, and Korean, must deal with a more complex issue, i.e., the handling of multibyte character sets.
    [Show full text]
  • Etsi En 300 468 V1.16.1 (2019-08)
    ETSI EN 300 468 V1.16.1 (2019-08) EUROPEAN STANDARD Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems 2 ETSI EN 300 468 V1.16.1 (2019-08) Reference REN/JTC-DVB-376 Keywords broadcasting, digital, DVB, MPEG, service, TV, video ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format at www.etsi.org/deliver. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]
  • Unicode and Code Page Support
    Natural for Mainframes Unicode and Code Page Support Version 4.2.6 for Mainframes October 2009 This document applies to Natural Version 4.2.6 for Mainframes and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © Software AG 1979-2009. All rights reserved. The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners. Table of Contents 1 Unicode and Code Page Support .................................................................................... 1 2 Introduction ..................................................................................................................... 3 About Code Pages and Unicode ................................................................................ 4 About Unicode and Code Page Support in Natural .................................................. 5 ICU on Mainframe Platforms ..................................................................................... 6 3 Unicode and Code Page Support in the Natural Programming Language .................... 7 Natural Data Format U for Unicode-Based Data ....................................................... 8 Statements .................................................................................................................. 9 Logical
    [Show full text]
  • 14 * (Asterisk), 169 \ (Backslash) in Smb.Conf File, 85
    ,sambaIX.fm.28352 Page 385 Friday, November 19, 1999 3:40 PM Index <> (angled brackets), 14 archive files, 137 * (asterisk), 169 authentication, 19, 164–171 \ (backslash) in smb.conf file, 85 mechanisms for, 35 \\ (backslashes, two) in directories, 5 NT domain, 170 : (colon), 6 share-level option for, 192 \ (continuation character), 85 auto services option, 124 . (dot), 128, 134 automounter, support for, 35 # (hash mark), 85 awk script, 176 % (percent sign), 86 . (period), 128 B ? (question mark), 135 backup browsers ; (semicolon), 85 local master browser, 22 / (slash character), 129, 134–135 per local master browser, 23 / (slash) in shares, 116 maximum number per workgroup, 22 _ (underscore) 116 backup domain controllers (BDCs), 20 * wildcard, 177 backups, with smbtar program, 245–248 backwards compatibility elections and, 23 for filenames, 143 A Windows domains and, 20 access-control options (shares), 160–162 base directory, 40 accessing Samba server, 61 .BAT scripts, 192 accounts, 51–53 BDCs (backup domain controllers), 20 active connections, option for, 244 binary vs. source files, 32 addresses, networking option for, 106 bind interfaces only option, 106 addtosmbpass executable, 176 bindings, 71 admin users option, 161 Bindings tab, 60 AFS files, support for, 35 blocking locks option, 152 aliases b-node, 13 multiple, 29 boolean type, 90 for NetBIOS names, 107 bottlenecks, 320–328 alid users option, 161 reducing, 321–326 announce as option, 123 types of, 320 announce version option, 123 broadcast addresses, troubleshooting, 289 API
    [Show full text]
  • SAS 9.3 UTF-8 Encoding Support and Related Issue Troubleshooting
    SAS 9.3 UTF-8 Encoding Support and Related Issue Troubleshooting Jason (Jianduan) Liang SAS certified: Platform Administrator, Advanced Programmer for SAS 9 Agenda Introduction UTF-8 and other encodings SAS options for encoding and configuration Other Considerations for UTF-8 data Encoding issues troubleshooting techniques (tips) Introduction What is UTF-8? . A character encoding capable of encoding all possible characters Why UTF-8? . Dominant encoding of the www (86.5%) SAS system options for encoding . Encoding – instructs SAS how to read, process and store data . Locale - instructs SAS how to present or display currency, date and time, set timezone values UTF-8 and other Encodings ASSCII (American Standard Code for Information Interchange) . 7-bit . 128 - character set . Examples (code point-char-hex): 32-Space-20; 63-?-3F; 64-@-40; 65-A-41 UTF-8 and other Encodings ISO 8859-1 (Latin-1) for Western European languages Windows-1252 (Latin-1) for Western European languages . 8-bit (1 byte, 256 character set) . Identical to asscii for the first 128 chars . Extended ascii chars examples: . 155-£-A3; 161- ©-A9 . SAS option encoding value: wlatin1 (latin1) UTF-8 and other Encodings UTF-8 and other Encodings Problems . Only covers English and Western Europe languages, ISO-8859-2, …15 . Multiple encoding is required to support national languages . Same character encoded differently, same code point represents different chars Unicode . Unicode – assign a unique code/number to every possible character of all languages . Examples of unicode points: o U+0020 – Space U+0041 – A o U+00A9 - © U+C3BF - ÿ UTF-8 and other Encodings UTF-8 .
    [Show full text]
  • Unicode Overview.E
    Unicode SAP Systems Unicode@sap NW AS Internationalization SupportedlanguagesinUnicode.doc 09.05.2007 © Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world.
    [Show full text]