HL7 - Version 2.4 Final Standard

Suggested Corrections to the Standard Documents

 
 

Changes to the documents for checking reasons

To run the checking and extract utilities some changes to the documents are necessary. They can be regarded as typos. Only a few minor remarks are left.

Chapter Text Change
(the message structure identifiers are double checked, they are NOT mistyped)
4.4.3   dto.
5.3.1.2 RSP^Z84RSP_K13 RSP^Z84^RSP_K13
5 Z87 distribute the contents of input field description onto more cells (in separate rows) to avoid truncating inside the database
7.18.1 NIC Delete paragraph break for description
9 property  
10 property  
10   check header and footer
11 property  
11   check footer
12 property  
12   check footer
13.2.3.26   insert 1st graphic as object
13.4.4 INV insert graphic as object

Segments with variable number of fields (repetition of last fields)

Some segments allow to repeat the last field as often as necessary. The database now considers this fact, but the required additions must be done by hand:

Changes to the documents for consistency reasons

To increase consistency some more changes are necessary. These are allowed to, because those elements are new for v2.4.

Chapter Text Change
(the message structure identifiers are double checked, they are NOT mistyped)
4.5.3
4.5.3.5
OBR-5 "Priority" instead of "Priority - OBR"
9.6.2 OBX-5 length 65535 instead of "*"
data type "varies" instead of "*"
12.4.3.10 ROL-10 Orgaization Unit Type - ROL
15.4.4 01276 Increase length to 250 to be consistent with CE data types
15.4.4   use new data element identifier to resolve conflict with ROL-10:
data element id 01625 instead of 01461
15.4.6 01276 Increase length to 250 to be consistent with CE data types
15.4.6.20 STF-20 Add component definition for CE data types

Changes to the documents for consistency reasons (not applied)

This table sums up the changes applied to the database. Perhaps it is possible to apply these changes, but this must be decided by the editors of the corresponding chapters.

Chapter Text Change
(the message structure identifiers are double checked, they are NOT mistyped)

4, 7

OBX-5

different lengths according to use, consistently set to 65536
data type: different values according to use, consistently set to "varies"
4.11.2 RQ1-2 assign table 0385, see 13.4.4.2
5.5.2 QAK-3 Message query name: assign table 0471
See QIP-2 and QPD-3
13.4.3 SAC-6
OBR-15
assign tables 0070/0163/0369
see OBR-15
5.10.5.3.9
10.5.3
table 0048 maintain only one list
6.5.5.20
15.4.4.11
table 0066 maintain complete list in chapter 6 and refer to it
check for values
3.4.10.19
6.5.7.14
table 0140 maintain complete list in chapter 3 and refer to it
4.5.3.24
7.4.1.24
table 0074 maintain complete list in chapter 4 and refer to it
4.20.2
7.18.3
table 0070 maintain complete list in chapter 4 and refer to it

Events not listed in table 0003 (chapter 2)

example events: Z73-Z79
other events: Q11/K11, Q13/K13, Q15/K15

Indicated Events without closer specification (chapter 5 + 7)

CNQ, R03, R05, R06, W01, W02
P09

Missing message structure identifiers listed in table 0354

SIU_S12: S12 - S24

Corrections since October 20, 2000

The next sections list necessary changes detected since last edits to chapters (shortly before distribution).

Wrong message specifications

Chapter Text Change
4.4.4   before FT1: "}]" => "]}"
4.4.6   last closing bracket must be "}" instead of "]"
4.7.2   second but last row: "}]"
5.9.1.1.1   insert into 3rd last row = "]" (check structure)
5.9.1.2.1   insert into 3rd last row = "]" (check structure)
5.9.2.1.1   insert into 3rd last row = "]" (check structure)
7.3.2   delete one closing bracket behind PV2
11.4.1   move bracket from 2nd to 1st column
11.5.1   move bracket from 2nd to 1st column
12.3.x OBR, etc.? Specify in detail
12.3.1   delete last closing bracket behind last VAR segment
12.3.8   2nd but last NTE segment: correct sequence of closing brackets
12.3.10   insert "[" before 3rd NTE segment
12.3.12   move brackets from 2nd column to first

Additional typos

Chapter Text Change
4.13.13
4.13.14
4.13.15
4.13.16
4.13.17
ROR
RAR
RDR
RER
RGR
QRY^Q26^QRY_Q01
QRY^Q27^QRY_Q01
QRY^Q28^QRY_Q01
QRY^Q29^QRY_Q01
QRY^Q30^QRY_Q01
Add conformance statement header to these five events
5.5.8.1 datatype "Variable" "varies"
5.6.3.2 event CNQ? CNQ is a message type! The examples in the text notes "QCN" as the message type, the text says to use "CNQ". This needs clarification.
Anyhow, this event/message type is only for backward compatibility.
15.3.7. QRY/PRM the correct message type specification must be "QBP/RSP"

Corrections to message structures (table 0354 chp.2.17.3)

RDE_O01 => delete
RPI_I0I => RPI_I01
RQI_I0I => RQI_I01
RRA_O02 => delete
TBR_R09 => delete

Message structures in table 0354 (without definition?)

Following message structure identifier is listed in table 0354, but the use is quite unclear:
QCK_Q02

Message structures missing in table 0354

RPI_I04: I04
RSP_K24: K24
RSP_K25: K25

Duplicate table values

These tables are difened twice, therefore delete in higher chapter and refer to the other:

0070: 4.20.2 + 7.18.3 (VITF (vitreous fluid) in one table (4.20.2) missing)
0074: 4.5.3.24 + 7.4.1.24 (IMG (diagnostic imaging) in one table missing)
0140: 3.4.10.19 + 6.5.7.14
0191: 2.9.37.3 + 9
0200: 2.9.54.7 + 3
0223: 3.4.10.1 + 6.5.5.33
0363: 2.9.5.4 + 3.4.2.3

Indicated Message types without closer specification (chapter 2)

MCF

 

 

Last Update: December 7, 2000