EN ISO 21549-5-2008 5853 Health informatics - Patient healthcard data - Part 5 Identification data《医疗信息学 病人医疗卡资料 第5部分 鉴定资料》.pdf

1、BRITISH STANDARDBS EN ISO 21549-5:2008Health informatics Patient healthcard data Part 5: Identification dataICS 35.240.80g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g4

2、4g42g43g55g3g47g36g58Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-BS EN ISO 21549-5:2008This British Standard was published under the authority of the Standards Policy and Str

3、ategy Committee on 30 May 2008 BSI 2008ISBN 978 0 580 55977 8National forewordThis British Standard is the UK implementation of EN ISO 21549-5:2008.The UK participation in its preparation was entrusted to Technical Committee IST/35, Health informatics.A list of organizations represented on this comm

4、ittee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations.Amendments/corrigenda issued s

5、ince publicationDate CommentsCopyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-EUROPEAN STANDARDNORME EUROPENNEEUROPISCHE NORMEN ISO 21549-5April 2008ICS 35.240.80English VersionHe

6、alth informatics - Patient healthcard data - Part 5:Identification data (ISO 21549-5:2008)Informatique de sant - Donnes relatives aux cartes desant des patients - Partie 5: Donnes didentification (ISO21549-5:2008)Medizinische Informatik - Patientendaten auf Karten imGesundheitswesen - Teil 5: Identi

7、fizierungsdaten (ISO21549-5:2008)This European Standard was approved by CEN on 14 March 2008.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date

8、lists and bibliographical references concerning such nationalstandards may be obtained on application to the CEN Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the res

9、ponsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as theofficial versions.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Ice

10、land, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre: rue de Sta

11、ssart, 36 B-1050 Brussels 2008 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN ISO 21549-5:2008: ECopyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking perm

12、itted without license from IHS-,-,-Foreword This document (EN ISO 21549-5:2008) has been prepared by Technical Committee ISO/TC 215 “Health informatics“ in collaboration with Technical Committee CEN/TC 251 “Health informatics” the secretariat of which is held by NEN. This European Standard shall be

13、given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by October 2008, and conflicting national standards shall be withdrawn at the latest by October 2008. Attention is drawn to the possibility that some of the elements of this document

14、may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austr

15、ia, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Endorsemen

16、t notice The text of ISO 21549-5:2008 has been approved by CEN as a EN ISO 21549-5:2008 without any modification. BS EN ISO 21549-5:2008Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IH

17、S-,-,-iii Introduction With a more mobile population, greater healthcare delivery in the community and at patients homes, together with a growing demand for improved quality of ambulatory care, portable information systems and stores have increasingly been developed and used. Such devices are used f

18、or tasks ranging from identification, through portable medical record files, and on to patient-transportable monitoring systems. The functions of such devices are to carry and to transmit person-identifiable information between themselves and other systems; therefore, during their operational lifeti

19、me they may share information with many technologically different systems which differ greatly in their functions and capabilities. Healthcare administration increasingly relies upon similar automated identification systems. For instance prescriptions may be automated and data exchange carried out a

20、t a number of sites using patient transportable computer readable devices. Healthcare funding institutions and providers are increasingly involved in cross-region care, where reimbursement may require automated data exchange between dissimilar healthcare systems. Administrative data objects may requ

21、ire linkage to external parties responsible for their own domains which are not within the scope of this part of ISO 21549. For instance, cross-border reimbursement of healthcare services are usually regulated by law and intergovernmental agreements which are not subject to standardization. The adve

22、nt of remotely accessible data bases and support systems has led to the development and use of “Healthcare Person” identification devices that are also able to perform security functions and transmit digital signatures to remote systems via networks. With the growing use of data cards for practical

23、everyday healthcare delivery, the need has arisen for a standardized data format for interchange. The person-related data carried by a data card can be categorised in three broad types: identification (of the device itself and the individual to whom the data it carries relates), administrative and c

24、linical. It is important to realise that a given healthcare data card “de facto”has to contain device data and identification data and may in addition contain administrative, clinical, medication and linkage data. Device data are defined to include: identification of the device itself; identificatio

25、n of the functions and functioning capabilities of the device. Identification data can include: unique identification of the device holder (and not information of other persons!). Administrative data can include: complementary person(s) related data; identification of the funding of healthcare, whet

26、her public or private, and their relationships, i.e. insurer(s), contract(s) and policy(ies) or types of benefits; identification of other persons as a part of the insurance contract (e.g. a family contract); other data (distinguishable from clinical data) that are necessary for the purpose of healt

27、hcare delivery. BS EN ISO 21549-5:2008Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ivClinical data may include: items that provide information about health and health events;

28、their appraisal and labelling by a healthcare provider; related actions planned requested or performed. Medication data may include: a record of medications received or taken by the patient; copies of prescriptions including the authority to dispense records of dispensed medication; records of medic

29、ation bought by the patient; pointers to other systems that contain information that makes up an electronic prescription and the authority to dispense. Because a data card essentially provides specific answers to definite queries whilst having at the same time a need to optimize the use of memory by

30、 avoiding redundancies “high level” Object Modelling Technique (OMT) has been applied with respect to the definition of healthcare data card data structures. This part of ISO 21549 describes and defines the Identification Data objects used within or referenced by patient-held health data cards using

31、 UML, plain text and Abstract Syntax Notation (ASN.1). This part of ISO 21549 does not describe and define the common objects defined within ISO 21549-2 even though they are referenced and utilized within this document. BS EN ISO 21549-5:2008Copyright European Committee for Standardization Provided

32、by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1Health informatics Patient healthcard data Part 5: Identification data 1 Scope This part of ISO 21549 establishes a common framework for the content and the structure of identification da

33、ta held on healthcare data cards. This part of ISO 21549 specifies the basic structure of the data, but does not specify particular data-sets for storage on devices. The detailed functions and mechanisms of the following services are not within the scope of this part of ISO 21549 (although its struc

34、tures can accommodate suitable data objects elsewhere specified): security functions and related services that are likely to be specified by users for data cards depending on their specific application, e.g. confidentiality protection, data integrity protection and authentication of persons and devi

35、ces related to these functions; access control services that may depend on active use of some data card classes such as microprocessor cards; the initialization and issuing process (which begins the operating lifetime of an individual data card, and by which the data card is prepared for the data to

36、 be subsequently communicated to it according to this part of ISO 21549). The following topics are therefore beyond the scope of this part of ISO 21549: physical or logical solutions for the practical functioning of particular types of data card; the form that data take for use outside the data card

37、, or the way in which such data are visibly represented on the data card or elsewhere. 2 Normative references 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

38、 the referenced document (including any amendments) applies. ISO 3166-1, Codes for the representation of names of countries and their subdivisions Part 1: Country codes ISO 8601, Data elements and interchange formats Information interchange Representation of dates and times ISO 21549-1, Health infor

39、matics Patient healthcard data Part 1: General structure ISO 21549-2, Health informatics Patient healthcard data Part 2: Common objects BS EN ISO 21549-5:2008Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted w

40、ithout license from IHS-,-,-2 ISO 21549-6, Health informatics Patient healthcard data Part 6: Administrative data ISO/IEC 5218, Information technology Codes for the representation of human sexes ISO/IEC 7816-6, Identification cards Integrated circuit cards Part 6: Interindustry data elements for int

41、erchange ISO/IEC 8824-1, Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation Part 1 ISO/IEC 8825-1, Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)

42、 Part 1 ISO/IEC 10646, Information technology Universal Multiple-Octet Coded Character Set (UCS) 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 21549-1 apply. 4 Symbols and abbreviated terms ASN.1 Abstract Syntax Notation One CRT Cardholder Related

43、Template L Length (ASN.1) LDS Logical Data Structure of machine-readable travel documents N Numeric NET National Extensions Template UCS Universal Multiple-Octet Coded Character Set UML Unified Modelling Language UTF8 UCS Transformation Format 8 5 Identification objects 5.1 Introduction objects and

44、data structure For identification of the cardholder, information about the following objects is needed: person; address; telecom; miscellaneous. BS EN ISO 21549-5:2008Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking pe

45、rmitted without license from IHS-,-,-3The structure of the identification information is derived from the LDS set used for machine-readable travel documents (LDS document of ICAO). No separate objects are introduced for healthcare. The following paragraph contains the table with the definitions of t

46、he identification data set. 5.2 Definition of the identification data set Table 1 shows the definition of identification data according to the ASN.1 basic notation and basic encoding described in ISO/IEC 8824-1 and ISO/IEC 8825-1, respectively. The corresponding ASN.1 definition is given at the end

47、of this document. In the ASN.1 definition the ASN.1 data type UTF8String (see ISO/IEC 10646) is used for the coding of alphanumeric data elements. Since the UTF8 encoding uses 1 to 6 bytes for each character, the number of storage bytes which should be provided by the card may be greater than the de

48、noted length in characters. The use of UTF8 should be restricted to a limited international character set, since it does not make sense to provide each country with any unfamiliar character set of another country. The formation of this international character set as a subset of the UCS has to be discussed. Figure 1 shows the UML class diagram. Figure 2 shows the CRT Template of Identification data with embedded NET. Figure 1 UML class diagram Figure 2 CRT Template of Identification data with embedded NET BS EN ISO 21549-5:2008Copyright European Committee