1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58Format of length limited globally unique string identifiersICS 35.240.80Health Informatics Messages
2、 and communication BRITISH STANDARDBS ISO 18232:2006BS ISO 18232:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 May 2006 BSI 2006ISBN 0 580 48302 9The British Standards which implement international publications referred to in this do
3、cument may be found in the BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online.This publication does not purport to include all the necessary provisions of a contract
4、. Users are responsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations.Summary of pagesThis document comprises a front cover, an inside front cover, the ISO title page, pages ii to v, a blank page, pages 1 to 9 and a back cov
5、er.The BSI copyright notice displayed in this document indicates when the document was last issued.Amendments issued since publicationAmd. No. Date CommentsA list of organizations represented on this committee can be obtained on request to its secretary.Cross-referencesenquiries on the interpretatio
6、n, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK.National forewordThis British Standard reproduces verbatim ISO 18232:2006 and implements it as the UK national standard.The UK participation in its prepar
7、ation was entrusted to Technical Committee IST/35, Health informatics, which has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any Reference numberISO 18232:2006(E)INTERNATIONAL STANDARD ISO18232First edition2006-04-01Health
8、Informatics Messages and communication Format of length limited globally unique string identifiers Informatique de sant Messages et communication Format des identifiants uniques universels cods en caractre et limits en longueurBS ISO 18232:2006ii iiiContents Page Foreword iv Introduction v 1 Scope .
9、 1 2 Normative references . 1 3 Terms, definitions and abbreviated terms . 1 3.1 Terms and definitions. 1 3.2 Abbreviated terms 2 4 Globally unique string identifier field . 2 5 ISO/IEC data object identifier GUSI exchange format. 2 5.1 General. 2 5.2 Logical data format. 2 5.3 Character representat
10、ion . 3 5.4 Encoding 3 5.5 Integer component representation . 3 5.6 Integer component separator 3 5.7 Interpretation of the data object identifier string 3 6 128 bit globally unique string identifier format . 3 6.1 General. 3 6.2 Logical data format. 3 6.3 Character representation . 3 6.4 UUID compo
11、nents. 3 6.5 Encoding 3 Annex A (informative) Scenarios 4 Annex B (informative) Nature and application of Data Object Identifiers 5 Annex C (informative) ASN.1 specification for the exchange of OID and UUIDs 8 BS ISO 18232:2006iv Foreword ISO (the International Organization for Standardization) is a
12、 worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represente
13、d on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are draf
14、ted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Sta
15、ndard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 18232 was prepared
16、by Technical Committee ISO/TC 215, Health informatics. BS ISO 18232:2006vIntroduction Data objects used in medicine include reports and results of diagnostic procedures which are stored and exchanged in electronic form, and objects such as templates. Applications must be able to find the location an
17、d the identification of such objects. Object identifiers are often numeric in form. This International Standard provides a means of exchanging globally unique identifiers expressed as character strings. It is not concerned with the specification of the location from which a data object may be retrie
18、ved. A healthcare service for a patient is delivered in identifiable parts which may be termed healthcare service items. A healthcare service item can be performed for a patient by a healthcare professional, or a healthcare professional may request a healthcare service item to be performed by anothe
19、r healthcare professional or by a healthcare service department such as a medical imaging service department. Healthcare service item results arise from numerical measurement or assessment by a healthcare professional. Individual numerical results may be included within report text, perhaps in a tab
20、le. Sets of numerical results may be presented visually e.g. waveform (graph) or image (picture). Results that consist of a large number of measured values such as a waveform or digital image are known as data objects. To allow safe use in medicine, all data objects must be identified by a globally
21、unique identifier (GUI), such as an ISO OID or binary MS GUI. The GUI allocated to a data object is attached to the data object (e.g. by including it within a computer file header section). The reference to a data object includes the GUI of the data object as well as the path to the data object. The
22、 application that retrieves the data object can verify that the correct data have been retrieved by matching the GUI in the reference to the GUI attached to the data object. See Annex A for relevant scenarios. It may be noted that: a) the issue of the location of a data object is separate from the i
23、ssue of its identity; indeed several identical copies of the object may exist; b) a globally unique data object identifier is intended for machine use and may be quite large; c) a short, user-friendly, locally unique identifier is often required in addition to the globally unique identifier for huma
24、n use. (This is outside the scope of this International Standard.) Globally unique identifiers are already specified in various standards and the intention of this International Standard is to provide a specification for a common format for the exchange of commonly used globally unique identifiers e
25、xpressed as alphanumeric strings. A logical data format for globally unique identifiers constructed from a sequence of integers is defined by ISO/IEC 8824-1. Identifiers based on ISO/IEC 8824-1 are widely used in medical imaging. 128 bit universal unique identifiers (UUIDs) are widely used in the MS
26、 Windows environment. This International Standard specifies the format of alphanumeric string fields for the exchange of globally unique string identifiers (GUSI) BS ISO 18232:2006blank1Health Informatics Messages and communication Format of length limited globally unique string identifiers 1 Scope
27、This International Standard specifies the encoding and length for globally unique identifiers for data objects used in healthcare exchanged as alphanumeric strings. The technologies used for data storage, location and communication are outside the scope of this International Standard. 2 Normative re
28、ferences The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 646, Information technology ISO
29、7-bit coded character set for information interchange ISO/IEC 8824-1:2002, Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation Part 1 ISO/IEC 9834 (all parts), Information Technology Open Systems Interconnection Procedures for the operation of OSI Registratio
30、n Authorities DICOM PS 3.3, Digital Imaging and Communications in Medicine Part 3: Information Object Definitions DICOM PS 3.4, Digital Imaging and Communications in Medicine Part 4: Service Class Specifications DICOM PS 3.5, Digital Imaging and Communications in Medicine Part 5: Data Structures and
31、 Encoding 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions 3.1.1 information object well-defined piece of information, definition, or specification which requires a name in order to identify its use in communication NOTE Adapted from ISO/IEC 8824-1. 3.1.2 object identifier OID va
32、lue (distinguishable from all other such values) that is associated with an information object NOTE Adapted from ISO/IEC 8824-1. BS ISO 18232:20062 3.1.3 data object identifier sequence of integer components constructed as specified in ISO/IEC 8824-1, having a root sequence of components issued by a
33、 national standards body and sequence of following integer components whose uniqueness is guaranteed by the organization that defined it NOTE Which is guaranteed to be globally unique by that national body registered as specified by ISO 9834. 3.1.4 unique identifier identifier that is different from
34、 any other such identifier within a given namespace 3.1.5 globally unique identifier identifier that is different from any other such identifier in any domain namespace 3.1.6 globally unique string identifier alphanumeric string of maximum length 64 characters, which is different from any other alph
35、anumeric string that has been or will be exchanged according to the provisions of this International Standard 3.2 Abbreviated terms GUI globally unique identifier OID object identifier UID unique identifier (DICOM) GUSI globally unique string identifier UUID universal unique identifier 4 Globally un
36、ique string identifier field When communicated by means of electronic data exchange the field containing the GUSI shall conform to the following: a) length: 64 octets; b) type: alphanumeric. NOTE The object identifier field might be included as part of the data object metadata or might be part of a
37、“wrapper” containing the data object. However this issue is outside the scope of this International Standard. 5 ISO/IEC data object identifier GUSI exchange format 5.1 General Applications that conform to this clause shall support the use of object identifiers (OIDs) as specified by ISO/IEC 8824-1 a
38、nd shall be constructed and encoded according to 5.2 to 5.7. 5.2 Logical data format Data object identifiers shall be constructed from a sequence of integer components in accordance with the provisions of ISO/IEC 8824-1 and ISO/IEC 9834-7. BS ISO 18232:200635.3 Character representation Data object i
39、dentifier integer components shall be represented as a character string using the following characters: “0“, “1“, “2“, “3“, “4“, “5“, “6“, “7“, “8“, “9“, “.“ NOTE See Annex A for an example. 5.4 Encoding A data object identifier shall be encoded as an alphanumeric string of 8 bit octets as specified
40、 by ISO/IEC 646. 5.5 Integer component representation An integer component shall not start with a zero character unless the component consists of a single zero. 5.6 Integer component separator A single full stop (2E hexadecimal) character shall separate sequential components. NOTE There is no leadin
41、g or trailing full stop. 5.7 Interpretation of the data object identifier string The root components allocated by a national body for use by an organization as the leading components of all data object identifiers created by that organization may carry meaning for the national body. However, applica
42、tions shall not infer any semantic information from any component of the data object identifier. 6 128 bit globally unique string identifier format 6.1 General The alphanumeric field specified in Clause 4 may also be used to hold a 128 bit binary number encoded using hexadecimal notation constructed
43、 as an alphanumeric string as specified in 6.2 to 6.5. See Annex C.3. Applications that conform to this International Standard and exchange 128 bit identifiers shall conform to the indications given in 6.2 to 6.5. 6.2 Logical data format The logical data format shall be a 128 bit binary number. 6.3
44、Character representation 128 bit data object identifiers shall be represented by a sequence of octets using the following characters: “0“, “1“, “2“, “3“, “4“, “5“, “6“, “7“, “8“, “9“, “a“, “b“, “c“, “d“, “e“, “f“, “-“ 6.4 UUID components The character string shall consist of a sequence of 5 componen
45、ts of lengths 8, 4, 4, 4 and 12 octets respectively, separated by a hyphen octet (2D hexadecimal) 6.5 Encoding A data object identifier shall be encoded as an alphanumeric string of 8 bit octets as specified by ISO/IEC 646. NOTE This clause supports the identifiers as given in the specifications of
46、universal unique identifiers (UUIDs). See Annex B. BS ISO 18232:20064 Annex A (informative) Scenarios A.1 Verification of the identity of a referenced data object A diagnostic procedure report may reference procedure products such as curves, waveforms, histograms and images recorded in electronic fo
47、rm. The observer of the results presented must be confident that the data presented are that which were selected by the clinician who created the report. The appropriate use of OSI object identifiers as defined by ISO/IEC 8824-1 and ISO/IEC 9834-7 can enable the implementation of procedures to facil
48、itate this aspect of security. For example, a report may include a pointer to a data object such as an image that comprises a unique identifier, the name of the file containing the image file and the path to the local copy of the file. When the application retrieves the file it can verify that the O
49、ID associated with the file is the same as the OID specified within the pointer. The UID associated with the file might be stored within a data header area or be incorporated in a “wrapper” containing the file. A.2 Merging of patient records from different institutions Records in electronic from are received by an institution and it is required to merge these with existing records. The availability of a globally unique identifier constitutes a unique database key field value, which facilitates the merging of data fr
