SIST-TS CEN/TS 14796:2004

SLOVENSKI STANDARD
01-september-2004
Zdravstvena informatika – Vrste podatkov
Health Informatics - Data Types
Medizinische Informatik - Datentypen
Informatique de santé - Types de données
Ta slovenski standard je istoveten z: CEN/TS 14796:2004
ICS:
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION
CEN/TS 14796
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
June 2004
ICS 35.240.80
English version
Health Informatics - Data Types
Élément introductif - Élément central Medizinische Informatik - Datentypen
This Technical Specification (CEN/TS) was approved by CEN on 9 February 2004 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2004 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 14796:2004: E
worldwide for CEN national Members.

Contents Page
1 Scope 7
2 Normative references 7
3 Terms and definitions 7
4 Abbreviations 8
5 Introduction to abstract data type definitions 9
5.1 Data values and data types 9
5.2 Representation of Data Values 10
5.3 Properties of Data Values 10
5.4 Characteristics of the data types 11
6 Primitive data types 11
6.1 Introduction 11
6.2 Primitive type set 11
6.3 Numeric Types 12
6.4 Set 13
6.5 Sequence 14
6.6 Bag 14
6.7 Array 14
7 Constructed Data Types 15
7.1 DATA_VALUE 15
7.2 Basic data types 15
7.3 Introduction 15
7.4 Encapsulated Data 16
7.5 Instance Identifier 18
7.6 ISO Object Identifier 19
7.7 Universal Resource Identifier 20
7.8 Interval 21
8 Textual and Coded data types 23
8.1 Introduction 23
8.2 TEXT 23
8.3 SIMPLE_TEXT 25
8.4 CODED_TEXT 25
8.5 Coded Value 25
8.6 Coded with Equivalents 26
8.7 Concept Descriptor 27
8.8 Concept Role 28
8.9 Coded Simple Value  Abstract Class 29
9 Quantity Types 29
9.1 UML representation 29
9.2 QUANTITY 30
9.3 Ordinal 31
9.4 Physical Quantity 32
9.5 DURATION 33
9.6 Quantity Ratio 34
9.7 QuantityRange 35
10 Time-RelatedTypes 36
10.1 UML representation 36
10.2 Date 36
10.3 Time point 37
10.4 Interval of Time 39
10.5 Periodic Interval of Time 40
10.6 Event Related Periodic Interval of Time 41
Annex A (normative)  Null Flavors 43
A.1 Introduction 43
A.2 Null flavor structure 44
Annex B (normative) Other CS-defined code lists 45
List of Figures
Figure 1: Packages . 9
Figure 2: UML Representation of Primitive data types . 12
Figure 3: UML Representation of Basic data types . 16
Figure 4: UML Representation of Text data types . 24
Figure 5: UML Representation of Quantity data types. 30
Figure 6: UML Representation of Time-related data types . 36
List of Tables
Table 1: Names and formats of numeric data types . 12
Table 2: Content of 32-bit floating point bit positions. 13
Table 3: Content of 64-bit floating point bit positions. 13
Table 4: Attributes of encapsulated data (ED). 17
Table 5: Attributes of Instance Identifier (II). 19
Table 6: Attributes of the OID data type. 19
Table 7: URI schemes. 20
Table 8: Attributes of the URI data type. 21
Table 9: Attributes of Interval . 22
Table 10: Attributes of the TEXT data type.23
Table 11: Attributes of the CODED_TEXT data type. 25
Table 12: Attributes of the Coded Value (CV) data type. 26
Table 13: Attributes of the Coded with Equivalents (CE) data type. 26
Table 14: Attributes of Concept Descriptor (CD) data type . 27
Table 15: Attributes of Concept Role (CR) data type . 28
Table 16: Attributes of Ordinal data type . 31
Table 17: Attributes of Physical Quantity data type . 32
Table 18: Attributes of Physical Quantity data type . 33
Table 19: Attributes of Quantity Ratio . 34
Table 20: Attributes of Quantity Range. 35
Table 21: Attributes of Date . 36
Table 22: Attributes of TS . 37
Table 23: Attributes of Interval of Time. 40
Table 24: Attributes of Periodic Interval of Time. 41
Table 25: Attributes of Event Related Periodic Interval of Time . 42
Table 26: Null Flavor values. 44
Table 27: MIME media types . 45
Table 28: Character set codes as defined by IANA. 46
Table 29: Compression Algorithms. 47
Foreword
This document CEN/TS 14796:2004 has been prepared by Technical Committee CEN/TC 251 “Health
Informatics”, the secretariat of which is held by SIS.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to announce this Technical Specification: Austria, Belgium, Cyprus,
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland,
Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
Introduction
ISO standards have existed for data types for some time, and especially significant is ISO 11404
(1994) Language Independent Data types. Since 1994 most data typing has been based upon or
harmonised with this standard. However, in healthcare information communication a different source
of ‘data type standardisation’ has arisen, sourced by Health Level Seven (HL7), whose data types
often resemble but are not wholly compatible with ISO 11404.
In developing this Technical Specification there has been the wish to harmonise with the HL7 data
types so that the health informatics industry in Europe and the USA can more easily be aligned. To
this end a collaboration agreement was entered into in March 2000 between CEN/TC 251 and HL7.
The goal was set for a maximum degree of alignment while maintaining their independence and need
to serve the business requirements of the respective markets but also to make the results available to
ISO for possible international standardisation.
This Technical Specification differs from the HL7 abstract data types in two major ways:
• Primitive data types are not re-defined here – they are assumed to be available in any
engineering environment that implements this specification. All other data types are defined
here
• This TS says nothing about operations that are associated with any particular data type.
Where a data type has been inherited from previously issued international standards the
associated operations may be assumed but are not specifically referred to in this document.
In most other respects, this specification may be regarded as a sub set of the HL7 Version 3 abstract
data types although partly described differently due to the fact that CEN is following the ISO rules for
drafting and presentation of standards which HL7 is not.
This version attempts to include insights gained as a result of recent CEN/HL7 harmonisation, and to
correct errors, where they were known to exist, particularly with respect to improving the technical
quality of the underlying abstract models. There are still some incomplete specifications, which are
indicated where appropriate.
The distinction between Primitive and Constructed data types has been tightened up.
Constructed types are divided into 4 packages for convenience (Basic, Text, Quantity, Time
Specification)
It is intended that, following further harmonisation work with HL7, and after there has been an
opportunity to gain implementation experience of using this specification, the TS will be developed into
a full European Standard (EN). By that stage the UML model will be extended to include all necessary
operations and formal invariants, together with attribute optionalities. For information on this process,
see www.centc251.org.
1 Scope
This Technical Specification defines abstract data types for use in communicating healthcare information and
for other health informatics purposes.
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 the referenced
document (including any amendments) applies.
ISO/IEC 11404 Information technology -- Programming languages, their
environments and system software interfaces -- Language-
independent datatypes
ISO 8601:2000(E) Data elements and interchange formats – Information
interchange – Representation of dates and times
Second edition 2000-12-15
ISO/IEC 8824-1 Information technology -- Abstract Syntax Notation One (ASN.1):
Specification of basic notation
ISO/IEC 10646-1
Information technology -- Universal Multiple-Octet Coded
Character Set (UCS) -- Part 1: Architecture and Basic Multilingual
Plane.
IEEE 754-1985 Standard for Binary Floating-Point Arithmetic
ISO 639:1988 (E/F) Code for the representation of names of languages
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply
3.1
data type
a set of distinct values, characterised by properties of those values and by operations on those values
3.2
date
identification of a particular calendar day, expressed by some combination of the data elements calendar year,
calendar month, calendar week, calendar day or day of the year
3.3
implementable technology specification
description of how to implement data types in a particular context (organisation, country, programming
language etc)
3.4
literal form
concise character string representation of information of a certain data type
EXAMPLE: the decimal digit string “1234” as a valid literal form for some number data types
3.5
null flavor
reason for the absence of a valid data value
3.6
period of time ( = time-interval)
portion of time between two time points
NOTE: A period of time is often also referred to as period
3.7
recurring time-interval
series of consecutive time-intervals of the same duration
3.8
time-point
instant in the laps of time regarded as dimensionless
3.9
value domain
set of valid data values for a data type
3.10
vocabulary domain
value domain for coded values
4 Abbreviations
BIN Binary Data
BL Boolean Data Value
CD Concept Descriptor
CE Coded with Equivalents
CR Concept Role
CS Coded Simple Value
CV Coded Value
DV Data Value
ED Encapsulated Data
EIVL Event Related Periodic Interval of Time
HL7 Health Leve
...