This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Product ITS DT"

From HL7Wiki
Jump to navigation Jump to search
(New page: =Product Brief - Data Types= __TOC__ back to Main_Page<br/>back to Product_List ==Product Name== Data Types - Abstract Specification ===Standard Category=== *Health Information Ex...)
 
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
=Product Brief - Data Types=
+
<big>'''Product Brief - Implementation Technology Specifications for Data Types'''</big>
 
__TOC__
 
__TOC__
 
back to [[Main_Page]]<br/>back to [[Product_List]]
 
back to [[Main_Page]]<br/>back to [[Product_List]]
−
==Product Name==
+
 
−
Data Types - Abstract Specification
+
 
 +
 
 +
<!---==========================================================================================
 +
|                                                                                            |
 +
|  XX  XX  MM    MM  LL      IIIIII  TTTTTT  SSSSS  DDDDD    TTTTTT    RRRRRR  111      |
 +
|    XX XX  MMM  MMM  LL        II      TT    SS      DD  DD    TT      RR  RR  11      |
 +
|    XXX    MM MMM MM  LL        II      TT    SSSS  DD  DD    TT      RRRRR    11      |
 +
|    XX XX  MM  M  MM  LL        II      TT        SS  DD  DD    TT      RR  RR    11      |
 +
|  XX  XX  MM    MM  LLLLLL  IIIIII    TT    SSSSS  DDDDD      TT  _____RR  RR  1111    |
 +
|                                                                                            |
 +
===========================================================================================--->
 +
 
 +
==Product Name - HL7 V3: Implementation Technology Specification - XML Data Types ==
  
 
===Standard Category===
 
===Standard Category===
Line 11: Line 23:
 
===Type===
 
===Type===
 
Normative, ANSI Standard
 
Normative, ANSI Standard
 +
===Topics===
 +
 +
*XML Implementation Technology Specification - Data Types
 +
===Releases===
 +
*ANSI/HL7 V3 XMLITSDT, R1-2004: HL7 Version 3 Standard: XML Implementation Technology Specification - Data Types, R1; 4/8/2004
 +
 +
 +
===Summary===
 +
This document specifies the HL7 Version 3 Data Types in the context of their XML Implementation Technology Specification (ITS).
 +
 +
This document is based on the Data Types Abstract Specification, which defines the data types on an abstract layer independent from representation.
 +
 +
What is a Data Type? Data types are the basic building blocks used to construct messages, computerized patient record documents, business objects and their transactions. Data types define the meaning of any given field's value. Without knowing a field's data type, it is impossible to interpret the field's value.
 +
 +
===Description===
 +
The communication of health information about individuals requires the accurate identification of specific entities and concepts, as well as the expression of complete, frequently complex semantic phrases. On an abstract layer, independent from representation, data types define properties of values. When values are represented, some of their properties are directly represented as atomic literal forms or as data structures. At that point we call those properties "components". On the representation layer we can also distinguish simple data types, represented as atomic literal forms, from complex ones, represented as structures with components. For the implementor, it is important to realize that data types have more properties than shown as components, and that it only depends on the implementation technology and ITS specification what data types are simple or complex and which of their properties are represented as "components" and which are inferred from those components.
 +
 +
===Business Case (Intended Use, Customers)===
 +
 +
===Benefits===
 +
 +
===Implementations/ Case Studies (Actual Users)===
  
 +
===Resources===
 +
 +
'''Work Groups'''<br/>
 +
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
 +
 +
'''Education'''<br/>
 +
* See more at http://www.hl7.org/implement/training.cfm
 +
 +
'''Presentations'''<br/>
 +
*
 +
===Relationship to/ Dependencies on, other standards===
 +
*ISO 11404
 +
===Links to current projects in development===
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=484 Project Insight ID # 484], Health informatics - Harmonized data types for information interchange (ISO Ballot Project)
 +
 +
----
 +
<!---===================================================================
 +
|                                                                      |
 +
|  RRRRRR    2222        GGGGG  UU  UU  IIIIII  DDDDD    EEEEEE    |
 +
|  RR  RR  22  22      GG      UU  UU    II    DD  DD  EE        |
 +
|  RRRRR      22        GG  GGG  UU  UU    II    DD  DD  EEEE      |
 +
|  RR  RR    22          GG  GG  UU  UU    II    DD  DD  EE        |
 +
|  RR  RR  222222        GGGGG    UUUU  IIIIII  DDDDD    EEEEEE    |
 +
|                                                                      |
 +
====================================================================--->
 +
 +
 +
==Product Name - HL7 V3 ITS, R2; XML Implementation Technology Specification R2 Guide, Release 1 ==
 +
 +
===Standard Category===
 +
*Health Information Exchange Standards
 +
===Integration Paradigm===
 +
*Foundation
 +
===Type===
 +
Informative
 +
===Topics===
 +
*
 
===Releases===
 
===Releases===
−
ANSI/HL7 V3 DT, R1-2004; currently balloting HL7 V3 DT R2 -
+
*HL7 V3 ITS, R2 Informative 2008 May
−
HL7 Version 3 Standard: Data Types - Abstract Specification, Release 2<br/>
 
−
Normative Ballot 4 - September 2009
 
  
 
===Summary===
 
===Summary===
−
Every data element has a data type. The data type defines the set of valid values that can be assigned to a data element and their meaning (semantics). Meaningful exchange of data requires that we know the definition of values so exchanged. This is true for complex "values" such as timing specifications as well as for simpler values such as character strings or integer numbers. An instance of a data type is a data value.  
+
There are two parts to this guide, a section specifically about the ISO datatypes and then a general guide to the New ITS.
 +
 
 +
This document describes the rationale for the decisions taken when developing and maintaining the ITS. This information is provided to support the use of the specification, and is not intended to restrict or extend the meaning of that specification. <br/>
 +
Where there is a difference, the specification takes priority over this document.
 +
 
 +
In addition, the guide provides additional implementation existence, including examples and discussions of common design and implementation issues.
 +
 
  
 
===Description===
 
===Description===
−
This standard provides the semantic definitions for the data types used in the creation of HL7 V3 specifications. These "abstract" semantic definitions are also able to be used as constraints in the creation of implementation guides, and implementation technology specifications that enable actual exchange of data are based on these semantic definitions.
+
The primary change to this document since the last release is the addition of the Datatypes sections.
 +
 
 +
The New ITS uses the ISO datatypes, which were designed in tandem with the New ITS. The New ITS is required to fully utiltise the ISO datatypes, and the ISO datatypes are required to fully leverage the benefits of the ISO datatypes. This guide is broken into two parts, the ISO datatypes guide, which is presented first, and then the New ITS Guide.
  
−
The data types defined in this specification are not intended to be implemented based on the details presented herein. For example, this specification does not differentiate between the information that should be represented in a payload and the information that should be derived from the payload. This document corresponds broadly to the RM-ODP informational view. The ISO data types specification is an ITS for these data types that corresponds to the RM-ODP computational view.  
+
This is the first draft of the ISO data types Guide. The guide provides additional information that is required or useful for using the ISO data types as an implementation of the abstract data types. In particular, this guide provides the direct conformance statement for the ISO data types. Also this guide contains background design for the ISO data types and implementation guidance.
  
−
According to ISO 11404, a data type is "a set of distinct values, characterized by properties of those values and by operations on those values." A data type can be defined by intension or by extension, or by a combination of these approaches. Intensional definition specifies the properties that the set of valid values must have: e.g. a definition that stipulates that a "string" is "an ordered collection of legible characters from a defined character set." Extensional definition enumerates the values deemed valid: e.g. the assertion that the boolean type consists of the values "true" and "false". While extensional definitions are useful for coded attributes, almost all abstract data types are defined intensionally.  
+
The ITS specification describes the method for creating HL7 implementation models using UML diagrams, XML schema, and (when desired) mappings between an alternative view of a message model and its ’parent’ RIM-Based Model (e.g. RMIM).  
  
−
A semantic property of a data type is referred to by a name and can be evaluated for any value of data type. The value of a data value's property must itself be a value defined by a data type - no data value exists that cannot be defined by a data type.
+
It uses the same mechanisms to deliver two very different XML representations of RIM-based information structures:
  
−
Data types are thus the basic building blocks used to construct any higher order meaning: messages, computerized patient record documents, or business objects and their transactions. What, then, is the difference between a data type and a message, document, or business object? Data type values stand for themselves: the value is all that counts. Neither identity nor state or changing of state is defined for a data value. Conversely in business objects, we track state and identity; the properties of an identical object might change between now and later. Not so with data values: a data value and its properties are constant. For example, number 5 is always number 5: there is no difference between this number 5 and that number 5 (no identity distinguished from value), number 5 never changes to number 6 (no change of state). One can think of data values as immutable objects where identity does not matter (identity and equality are the same).  
+
Stable, more consistent serialization using generic patterns such as Clinical Statement for the XML element names. This builds on the success of the stability of the CDA approach to serialization.  
 +
Reshaped structures where a RIM-based model (e.g. RMIM) is 'simplified' to meet an implementer view requirement (e.g. mapping to local data models or supporting domain expert review).  
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
  
−
The audience for this document is anyone who uses HL7 V3 data types - both implementers and designers of HL7 specifications. For implementers, this document should be treated as secondary supplemental information to the ITS data types, which provide an basis for actual implementation of the data types.
+
===Benefits===
 +
The ITS data types guide provides supporting information for the joint ISO / HL7 healthcare data types specification. The ISO healthcare data types is developed jointly by HL7 and ISO to provide a platform independent data type specification for general use in healthcare specifications, and in particular to be used as part of the ITS in the context of HL7 V3.
 +
 
 +
This guide outlines the design principles that drove the development of the ISO data types specification; specifies the conformance statement for the ISO data types standard for HL7 V3 (mapping from the ISO data types to the V3 modeling framework) as required by the ISO specification; provides reference and tutorial information to help implementors that are experienced with the previous HL7 V3 XML ITS and provides as yet incomplete documentation for the requirements that supported the design of the data types.
 +
 
 +
 
 +
===Implementations/ Case Studies (Actual Users)===
 +
 
 +
===Resources===
 +
'''Work Groups'''<br/>
 +
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
 +
 
 +
'''Education'''<br/>
 +
* See more at http://www.hl7.org/implement/training.cfm
 +
 
 +
'''Presentations'''<br/>
 +
*
 +
===Relationship to/ Dependencies on, other standards===
 +
*ISO 11404
 +
===Links to current projects in development===
 +
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=484 Project Insight ID # 484], Health informatics - Harmonized data types for information interchange (ISO Ballot Project)
 +
 
 +
 
 +
----
 +
<!---=============================================================
 +
|                                                                |
 +
|  XX  XX  MM    MM  LL          RRRRRR  111      111      |
 +
|    XX XX  MMM  MMM  LL          RR  RR  11        11      |
 +
|    XXX    MM MMM MM  LL          RRRRR    11        11      |
 +
|    XX XX  MM  M  MM  LL          RR  RR    11        11      |
 +
|  XX  XX  MM    MM  LLLLLL      RR  RR  1111  ..  1111    |
 +
|                                                                |
 +
==============================================================--->
 +
 
 +
==Product Name - HL7 V3 XML ITS Data Types R1.1 ==
 +
HL7 Version 3 Standard: XML Implementation Technology Specification for V3 Data Types, Release 1
 +
===Standard Category===
 +
*Health Information Exchange Standards
 +
===Integration Paradigm===
 +
*Foundation
 +
===Type===
 +
Informative
 +
===Topics===
 +
 
 +
===Releases===
 +
*HL7 V3 XMLITS_DT1.1, R1; 2010Jan
 +
 
 +
===Summary===
 +
This is XML ITS R1.1 for datatypes. It differs from the XML ITS for R2 of the datatypes, which is the ISO Healthcare Datatypes (ISO 21090), in that it only introduces those changes and features of data types R2 that can be introduced into the existing XML ITS R1 without non-backwards change or otherwise creating a requirement for new infrastructure. It is offered as an informative specification to assist with consistency with R2 feature pre-adoption.
 +
 
 +
What is a Data Type? Data types are the basic building blocks used to construct messages, computerized patient record documents, business objects and their transactions. Data types define the meaning of any given field's value. Without knowing a field's data type, it is impossible to interpret the field's value.
 +
 
 +
===Description===
 +
On an abstract layer, independent from representation, data types define properties of values. When values are represented, some of their properties are directly represented as atomic literal forms or as data structures. At that point we call those properties "components". On the representation layer we can also distinguish simple data types, represented as atomic literal forms, from complex ones, represented as structures with components. For the implementor, it is important to realize that data types have more properties than shown as components, and that it only depends on the implementation technology and ITS specification what data types are simple or complex and which of their properties are represented as "components" and which are inferred from those components.
 +
 
 +
===Business Case (Intended Use, Customers)===
  
 
===Benefits===
 
===Benefits===
−
Why does this specification make such a big issue about its being abstract from representation syntax as well as operational implementation?
+
 
 +
 
 +
===Implementations/ Case Studies (Actual Users)===
 +
 
 +
===Resources===
 +
'''Work Groups'''<br/>
 +
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
 +
 
 +
'''Education'''<br/>
 +
* See more at http://www.hl7.org/implement/training.cfm
 +
 
 +
'''Presentations'''<br/>
 +
*
 +
===Relationship to/ Dependencies on, other standards===
 +
*
 +
===Links to current projects in development===
 +
*
  
−
HL7 needs this kind of abstract semantic data type specification for a very practical purpose. One important design feature of HL7 version 3 is its openness towards representation and implementation technologies. All HL7 version 3 specifications are supposed to be done in a form independent from specific representation and implementation technologies. HL7 acknowledges that, while at times some representation and implementation technologies may be more popular than others, technology is going to change - and with changing technology, representations of data values will change. HL7 standards are primarily targeted to healthcare domain information, independent from the technology supporting this information. HL7 expects that specifications defined independent from today's technology will continue to be useful, even after the next technological "paradigm shift".
 
  
−
Why does HL7 need its own data type standard? Why can't HL7 simply adopt a standard defined by some other body?
 
  
−
As noted in the previous section, all HL7 implementation technologies have some data type system, but there are differences among the data type systems between implementation technologies. In addition, many implementation technologies' data type systems are not powerful enough to express the concepts that matter for the HL7 application layer.  
+
----
 +
<!---==================================================
 +
|                                                    |
 +
|  IIIIII  SSSSS  OOOOO        DDDDD    TTTTTT    |
 +
|    II    SS      OO  OO      DD  DD    TT      |
 +
|    II    SSSS  OO  OO      DD  DD    TT      |
 +
|    II        SS  OO  OO      DD  DD    TT      |
 +
|  IIIIII  SSSSS    OOOOO        DDDDD      TT      |
 +
|                                                    |
 +
===================================================--->
 +
 
 +
==Product Name - HL7 V3: Implementation Technology Specification - ISO-Harmonized Data Types, Release 1 ==
 +
 
 +
===Standard Category===
 +
*Health Information Exchange Standards
 +
===Integration Paradigm===
 +
*Foundation
 +
===Type===
 +
Normative
 +
===Topics===
 +
 
 +
 
 +
===Releases===
 +
 
 +
*HL7 V3 ISO DT, R1-2009: HL7 Version 3 Standard: XML Implementation Technology Specification R2; ISO-Harmonized Data Types, Release 1
 +
 
 +
===Summary===
 +
This standard provides a globally harmonized (ISO/CEN/HL7) set of representations for data used in the presentation and communication of health care information. This standardized set will be an internationally agreed upon, proper sub-set of data types currently adopted by national and trans-national health care standards development organizations.  This document provides a UML and XML implementation of the datatypes, and is in effect Release 2 of the XML ITS datatypes. This document is shared and jointly balloted between HL7, CEN, and ISO.
 +
 
 +
===Description===
 +
The communication of health information about individuals requires the accurate identification of specific entities and concepts, as well as the expression of complete, frequently complex semantic phrases. Experience has shown that representation of such data requires that a rich set of data types be built upon the primitive types normally specified for computer software. The set to be specified in this standard will provide the structures necessary to meet the basic requirements of health care information communication.
 +
 
 +
===Business Case (Intended Use, Customers)===
 +
 
 +
===Benefits===
 +
The market for and the supply of healthcare software systems is global. There is an increasing demand to be able to communicate health care data between jurisdictions. Following requests from national health informatics programmes, the vendor community and, also, extensive discussion of previous ISO, HL7 and CEN work on data types, an advanced draft of a new International Standard has now been prepared. This standard will promote a common representation that meets these needs and is being advanced as common draft standard in all three communities. 1. updated datatypes for new requirements from HL7 2. simplified technical implementation path as a result of user feedback 3. shared content between HL7, CEN, and ISO.
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
  
 
===Resources===
 
===Resources===
 +
'''Work Groups'''<br/>
 +
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
  
−
====Work Groups====
+
'''Education'''<br/>
−
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
 
−
====Education====
 
 
* See more at http://www.hl7.org/implement/training.cfm
 
* See more at http://www.hl7.org/implement/training.cfm
  
−
====Presentations====
+
'''Presentations'''<br/>
 
*
 
*
 
===Relationship to/ Dependencies on, other standards===
 
===Relationship to/ Dependencies on, other standards===
−
*RIM
+
*ISO 11404
 
===Links to current projects in development===
 
===Links to current projects in development===
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=484 Project Insight ID # 484], Health informatics - Harmonized data types for information interchange (ISO Ballot Project)
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=484 Project Insight ID # 484], Health informatics - Harmonized data types for information interchange (ISO Ballot Project)
−
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=455 Project Insight ID # 455] Complete Balloting of V3 Abstract Data Types R2, by Modeling and Methodology Work Group
+
 
 +
 
 +
----
 +
<!---====================================================
 +
|                                                      |
 +
|  UU  UU  MM    MM  LL          DDDDD    TTTTTT    |
 +
|  UU  UU  MMM  MMM  LL          DD  DD    TT      |
 +
|  UU  UU  MM MMM MM  LL          DD  DD    TT      |
 +
|  UU  UU  MM  M  MM  LL          DD  DD    TT      |
 +
|    UUUU  MM    MM  LLLLLL      DDDDD      TT      |
 +
|                                                      |
 +
=====================================================--->
 +
 
 +
 
 +
==Product Name - HL7 V3: Implementation Technology Specification - UML Data Types==
 +
 
 +
===Standard Category===
 +
*Health Information Exchange Standards
 +
===Integration Paradigm===
 +
*Foundation
 +
===Type===
 +
Normative, ANSI Standard
 +
 
 +
===Releases===
 +
*ANSI/HL7 V3 UMLITSDT, R1-2004: HL7 Version 3 Standard: UML Implementation Technology Specification - Data Types, Release 1; 4/23/2004
 +
 
 +
===Summary===
 +
The Abstract Data Types specification includes a Unified Modeling Language (UML) diagram that presents the semantic declarations of these data types in a standard UML fashion.
 +
 
 +
This UML ITS implements the semantics of the Abstract Data Types specification using UML in such a way that HL7 data types are mapped into the core UML and OCL kernel data types where such mappings are appropriate. In addition, this representation uses only established object-orientated formalisms. Since this specification shows how to implement the HL7 data types using the UML core data types and methodology, this specification is an ITS for the data types in UML.
 +
 
 +
===Description===
 +
The desired outcomes from this specification include:
 +
*A formally correct UML declaration of the HL7 Data Types
 +
*Enable the use of Computer-Aided Software Engineering (CASE) tools for model validation, code generation, instance validation, etc
 +
*Enable these same outcomes for downstream HL7 UML artifacts such as the RIM and message structures.
 +
 
 +
===Resources===
 +
'''Work Groups'''<br/>
 +
[http://www.hl7.org/Special/committees/xml/index.cfm Implementable Technology Specifications]
 +
 
 +
'''Education'''<br/>
 +
* See more at http://www.hl7.org/implement/training.cfm
 +
 
 +
'''Presentations'''<br/>
 +
 
 +
===Relationship to/ Dependencies on, other standards===
 +
*
 +
===Links to current projects in development===
 +
*None
 +
[[Category:Products]]

Latest revision as of 19:37, 23 June 2010

Product Brief - Implementation Technology Specifications for Data Types

Contents

back to Main_Page
back to Product_List



Product Name - HL7 V3: Implementation Technology Specification - XML Data Types

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Foundation

Type

Normative, ANSI Standard

Topics

  • XML Implementation Technology Specification - Data Types

Releases

  • ANSI/HL7 V3 XMLITSDT, R1-2004: HL7 Version 3 Standard: XML Implementation Technology Specification - Data Types, R1; 4/8/2004


Summary

This document specifies the HL7 Version 3 Data Types in the context of their XML Implementation Technology Specification (ITS).

This document is based on the Data Types Abstract Specification, which defines the data types on an abstract layer independent from representation.

What is a Data Type? Data types are the basic building blocks used to construct messages, computerized patient record documents, business objects and their transactions. Data types define the meaning of any given field's value. Without knowing a field's data type, it is impossible to interpret the field's value.

Description

The communication of health information about individuals requires the accurate identification of specific entities and concepts, as well as the expression of complete, frequently complex semantic phrases. On an abstract layer, independent from representation, data types define properties of values. When values are represented, some of their properties are directly represented as atomic literal forms or as data structures. At that point we call those properties "components". On the representation layer we can also distinguish simple data types, represented as atomic literal forms, from complex ones, represented as structures with components. For the implementor, it is important to realize that data types have more properties than shown as components, and that it only depends on the implementation technology and ITS specification what data types are simple or complex and which of their properties are represented as "components" and which are inferred from those components.

Business Case (Intended Use, Customers)

Benefits

Implementations/ Case Studies (Actual Users)

Resources

Work Groups
Implementable Technology Specifications

Education

Presentations

Relationship to/ Dependencies on, other standards

  • ISO 11404

Links to current projects in development


Product Name - HL7 V3 ITS, R2; XML Implementation Technology Specification R2 Guide, Release 1

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Foundation

Type

Informative

Topics

Releases

  • HL7 V3 ITS, R2 Informative 2008 May

Summary

There are two parts to this guide, a section specifically about the ISO datatypes and then a general guide to the New ITS.

This document describes the rationale for the decisions taken when developing and maintaining the ITS. This information is provided to support the use of the specification, and is not intended to restrict or extend the meaning of that specification.
Where there is a difference, the specification takes priority over this document.

In addition, the guide provides additional implementation existence, including examples and discussions of common design and implementation issues.


Description

The primary change to this document since the last release is the addition of the Datatypes sections.

The New ITS uses the ISO datatypes, which were designed in tandem with the New ITS. The New ITS is required to fully utiltise the ISO datatypes, and the ISO datatypes are required to fully leverage the benefits of the ISO datatypes. This guide is broken into two parts, the ISO datatypes guide, which is presented first, and then the New ITS Guide.

This is the first draft of the ISO data types Guide. The guide provides additional information that is required or useful for using the ISO data types as an implementation of the abstract data types. In particular, this guide provides the direct conformance statement for the ISO data types. Also this guide contains background design for the ISO data types and implementation guidance.

The ITS specification describes the method for creating HL7 implementation models using UML diagrams, XML schema, and (when desired) mappings between an alternative view of a message model and its ’parent’ RIM-Based Model (e.g. RMIM).

It uses the same mechanisms to deliver two very different XML representations of RIM-based information structures:

Stable, more consistent serialization using generic patterns such as Clinical Statement for the XML element names. This builds on the success of the stability of the CDA approach to serialization. Reshaped structures where a RIM-based model (e.g. RMIM) is 'simplified' to meet an implementer view requirement (e.g. mapping to local data models or supporting domain expert review).

Business Case (Intended Use, Customers)

Benefits

The ITS data types guide provides supporting information for the joint ISO / HL7 healthcare data types specification. The ISO healthcare data types is developed jointly by HL7 and ISO to provide a platform independent data type specification for general use in healthcare specifications, and in particular to be used as part of the ITS in the context of HL7 V3.

This guide outlines the design principles that drove the development of the ISO data types specification; specifies the conformance statement for the ISO data types standard for HL7 V3 (mapping from the ISO data types to the V3 modeling framework) as required by the ISO specification; provides reference and tutorial information to help implementors that are experienced with the previous HL7 V3 XML ITS and provides as yet incomplete documentation for the requirements that supported the design of the data types.


Implementations/ Case Studies (Actual Users)

Resources

Work Groups
Implementable Technology Specifications

Education

Presentations

Relationship to/ Dependencies on, other standards

  • ISO 11404

Links to current projects in development


Product Name - HL7 V3 XML ITS Data Types R1.1

HL7 Version 3 Standard: XML Implementation Technology Specification for V3 Data Types, Release 1

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Foundation

Type

Informative

Topics

Releases

  • HL7 V3 XMLITS_DT1.1, R1; 2010Jan

Summary

This is XML ITS R1.1 for datatypes. It differs from the XML ITS for R2 of the datatypes, which is the ISO Healthcare Datatypes (ISO 21090), in that it only introduces those changes and features of data types R2 that can be introduced into the existing XML ITS R1 without non-backwards change or otherwise creating a requirement for new infrastructure. It is offered as an informative specification to assist with consistency with R2 feature pre-adoption.

What is a Data Type? Data types are the basic building blocks used to construct messages, computerized patient record documents, business objects and their transactions. Data types define the meaning of any given field's value. Without knowing a field's data type, it is impossible to interpret the field's value.

Description

On an abstract layer, independent from representation, data types define properties of values. When values are represented, some of their properties are directly represented as atomic literal forms or as data structures. At that point we call those properties "components". On the representation layer we can also distinguish simple data types, represented as atomic literal forms, from complex ones, represented as structures with components. For the implementor, it is important to realize that data types have more properties than shown as components, and that it only depends on the implementation technology and ITS specification what data types are simple or complex and which of their properties are represented as "components" and which are inferred from those components.

Business Case (Intended Use, Customers)

Benefits

Implementations/ Case Studies (Actual Users)

Resources

Work Groups
Implementable Technology Specifications

Education

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development


Product Name - HL7 V3: Implementation Technology Specification - ISO-Harmonized Data Types, Release 1

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Foundation

Type

Normative

Topics

Releases

  • HL7 V3 ISO DT, R1-2009: HL7 Version 3 Standard: XML Implementation Technology Specification R2; ISO-Harmonized Data Types, Release 1

Summary

This standard provides a globally harmonized (ISO/CEN/HL7) set of representations for data used in the presentation and communication of health care information. This standardized set will be an internationally agreed upon, proper sub-set of data types currently adopted by national and trans-national health care standards development organizations. This document provides a UML and XML implementation of the datatypes, and is in effect Release 2 of the XML ITS datatypes. This document is shared and jointly balloted between HL7, CEN, and ISO.

Description

The communication of health information about individuals requires the accurate identification of specific entities and concepts, as well as the expression of complete, frequently complex semantic phrases. Experience has shown that representation of such data requires that a rich set of data types be built upon the primitive types normally specified for computer software. The set to be specified in this standard will provide the structures necessary to meet the basic requirements of health care information communication.

Business Case (Intended Use, Customers)

Benefits

The market for and the supply of healthcare software systems is global. There is an increasing demand to be able to communicate health care data between jurisdictions. Following requests from national health informatics programmes, the vendor community and, also, extensive discussion of previous ISO, HL7 and CEN work on data types, an advanced draft of a new International Standard has now been prepared. This standard will promote a common representation that meets these needs and is being advanced as common draft standard in all three communities. 1. updated datatypes for new requirements from HL7 2. simplified technical implementation path as a result of user feedback 3. shared content between HL7, CEN, and ISO.

Implementations/ Case Studies (Actual Users)

Resources

Work Groups
Implementable Technology Specifications

Education

Presentations

Relationship to/ Dependencies on, other standards

  • ISO 11404

Links to current projects in development



Product Name - HL7 V3: Implementation Technology Specification - UML Data Types

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Foundation

Type

Normative, ANSI Standard

Releases

  • ANSI/HL7 V3 UMLITSDT, R1-2004: HL7 Version 3 Standard: UML Implementation Technology Specification - Data Types, Release 1; 4/23/2004

Summary

The Abstract Data Types specification includes a Unified Modeling Language (UML) diagram that presents the semantic declarations of these data types in a standard UML fashion.

This UML ITS implements the semantics of the Abstract Data Types specification using UML in such a way that HL7 data types are mapped into the core UML and OCL kernel data types where such mappings are appropriate. In addition, this representation uses only established object-orientated formalisms. Since this specification shows how to implement the HL7 data types using the UML core data types and methodology, this specification is an ITS for the data types in UML.

Description

The desired outcomes from this specification include:

  • A formally correct UML declaration of the HL7 Data Types
  • Enable the use of Computer-Aided Software Engineering (CASE) tools for model validation, code generation, instance validation, etc
  • Enable these same outcomes for downstream HL7 UML artifacts such as the RIM and message structures.

Resources

Work Groups
Implementable Technology Specifications

Education

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development

  • None
Retrieved from "https://wiki.hl7.org/w/index.php?title=Product_ITS_DT&oldid=38505"