HL7 - Version 2.8.1 Final Standard

Suggested Corrections to the Standard Documents


In order to provide the original standard in a database, several changes to the official documents are required. In principal, this version of the standard is mostly in sync with v2.8, because only a few chapters have been changed due to the S&U Framework by adding a few fields.

Corrections to the standard and changes within the HL7 database

Quite happily, during balloting and in the pre-publication process most of the open issues - which were highly related to typos - have been resolved, so that this list is pretty short. Nevertheless, there are still some issues to report.

For the old issues, the user should check for the resolution of previous versions.

1. Unsolved Issues

This document summarizes the discrepancies of the database to the standard documents.

1.1. Problems detected so far without any solution

An important issue to mention is the appearance of withdrawn elements. Here no information about the different attributes is available any more. Nevertheless, for some usages in other segments they are still necessary. Hence, they are listed in the database.

Where in one of the message structures all or at least Z-segments are possible, a placeholder like "Hxx" for HL7-defined segments and "Zxx" for Z-segments is introduced.

1.2. old, but unsolved issues

An old but still open problem is with the different message structures for Q11 (5.4.1)/Q15 (5.4.2,, (5.4.3) and K11 (RDF and RDT segment) events. They are still not consistent due to "unknown extensions" to the proposed structure.
However, within the db the structures must be reconciled. It is recommended to check with the original documents.

1.3. problems without any impact

As before, some segments are specified, but never used:

On the other hand, some messages do use segments which are deleted. To solve this problem, the segment is defined in the database:

It is unclear how to create these messages without using a (required) segment?

Some messages refer to "etc" as alternative segments. These are replaced by "Hxx":

2. Changes within the docs and database

There are no explicit changes because the standard has been published already.

3. Changes within the database on v2.8.1 only

 table 0936not definedopendefine table in chp. 2C
allwrong group names in message structures (blank) or wrong bracketing:
ADT_A50, BPR_O30 CCI_I22, CCM_I21, CCU_I20, CQ_I19, CSU_C09, DEO_O45, DFT_P03, DFT_P11, EHC_E10, EHC_E15, EHC_E20, NMD_N02, OML_O21, OML_O33, OML_O35, OML_O39, OPL_O32, OPU_R25, ORL_O34, ORL_O36, ORL_O40, ORL_O42, ORL_O43, ORL_O44, ORU_R01, OSU_O41, OUL_R22, OUL_R23, _OUL_R24, RDE_O11, REF_I12, RSP_Z86, SRM_S01, SRR_S01, CCR_I16
no commentopencorrect item

Last Update: November 6, 2014