HL7 - Version 2.6 Final Standard

Corrections to the standard and changes within the HL7 database

1. Unsolved Issues

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

1.1. Problems detected so far without any solution

This table lists the issues without any solution. It should be used for discussion:

Section	Issue	Comment	Status	Resolution
8	MFK_M01	UAC segment is missing in some messages!Insert?	Closed	Not allowed M01 is retained for backward compatibility
2A	datatype TQ	which is the correct length? a lot of long components	open	Still need clarification. Where is this inconsistent?12.4.1.15
4.5.3.15 7.4.1.15	OBR-15	assign table 0070?	open	Do you mean in the table at 4.5.3? yes
7.4.3.4 + 7.18.4	table 0487	user or HL7 table? User-defined because CWE!	open	Getting feedback from Hans
5.4.1	QBP_Q11	EVN is used, nowhere else	open	Waiting on feedback from co-chairs
5.9.1.2.1 5.9.1.1.1 5.3.3.2 5.9.2.1.1 5.4.1 8.4.5.1 5.9.2.4 4.13.20	QBP_Q11	different structure:5.4.1: uses EVN(see above)	open	Waiting on feedback from co-chairs
8.4.5.1	RSP_Q11	wrong message structure ID	open	What do you think it should be?fo: don't know, is specific to this query; replace Znn by something else
2.A.9.7	table 0360	Message Type with different definitions	open	Inconsistent Definition between chapters or within same chapter for same field. Would recommend errata.
7.4.3.4 + 7.18.4	table 0487	different definitions for same value:DRN, AUTOC, GRAFT	open	There are no definitions in 7.4.3.4. How is this different?fo: 7.4.3.4 should refer to 7.18.4
4.23.6	table 0550	different definitions for same valueNP, NOSE, PAROT, THORA, UMBL	V2.7 proposal	Would recommend V2.7 proposal to vocab. Some of these look valid to me and published like this in 2.5.1.
7.15.1+2		define message structure for ORU_W01 and QRF_W02	V2.7 proposal	Would recommend V2.7 proposal. This was published like this in 2.5.1. Waiting for feedback from co-chair

1.2. old, but unsolved issues

Section	Issue	Comment	Status	Resolution
7.11.2:	ED	is an unknown segment - this is a very old issue	Closed	N/A - this may be a technical error, this event and message are deprecated. No change allowed.

2. Changes within the docs and database

2.1. Problems solved by changing the documents

This section is still in discussion whether to apply the changes or to rollback.

Section	Issue	Comment	Status	Resolution
2.16.1	table 0076	deleted: SDS, SLS, SMS, STS	clear technical correction as this table reflects the rest of the chapters.
2.16.2	table 0003	corrected comment: E30, E31corrected description: S28, S29	clear technical correction as this table reflects the rest of the chapters.
2.16.3	table 0354	OMN_O07: 007 to O07 ORL_O22: 022 to O22 QBP_E03: added event QBP_E22: added event RSP_E03: added event RSP_E22: added event added RSP_Q11 corrected structures for S28, S29, S30, S31, S34, S35, S36, S37	clear technical correction as this table reflects the rest of the chapters. (see also next rows)
2.16.3	table 0354	changed value ADT_A13 to ADT_A12		Waiting on response from co-chairs. I sent email to respond.
2.16.3 + 3.3.55	table 0354	changed MsgStructID from ADT_A55 to ADT_A54		Waiting on response from co-chairs. I sent email to respond.
2.16.3	table 0354	changed ORP_O38 to OPR_O38 (see 4.4.15)This is a clear typo.	clear typo	Waiting on response from co-chairs. I sent email to respond.
2	table 0396	replaced by Ted's version + German additions.(Discussed in TCs and several emails.)	accepted by Vocab	Added to 0396 on HL7 website
2 + 8:	table 0396	adjusted years for ICD, OPS, GDRG (German Modifications) to 2006/2007/2008	accepted by Vocab	Added to 0396 on HL7 website.
2.14.8:	MSA-2	message control id: set length to 199 to be in sync with MSH-10, otherwise the standard cannot work.	technical correction	Waiting on response from co-chairs. I sent email to respond.
3.4.2.5	table 0200:	added "K" = artist name	clear typo	Waiting on response from co-chairs. I sent email to respond.
4.5.3.15	table 0369:	added E, F, G, L, O, V (see 7.4.3.11)		Waiting on response from co-chairs. I sent email to respond.
4.5.1.7 + 7.4.1.27 + 4.5.3.27:		set length to 705	Closed	Not allowed - retained for backward compatibility. This change will have to be backed out.
9.9.4.18:	table 0296	renamed table 0296 to be in sync with 3.4.2.14 and changed value to "no suggested values"		Ok, but the reference is still incorrect in the message definition above the table.

2.2. Problems detected and corrected by ARB/TSC decision

Section	Issue	Comment	Status
15.4.8.17:	00119:	Marital Status STF-17: length to 705	accepted
15.4.8.27:	00113: Race	STF-27: length to 705	accepted
15.4.8.28:	00125: Ethnic Group	STF-28: length to 705	accepted
15.4.8.30:	00129: Citizenship	STF-30: length to 705	accepted
16:	RFI	RFI segment is used in messages, but is never defined. Instead RTI segment is defined with the same name.The less amount of changes is to use RTI in messages as well, but the correct solution should be to use RFI!	accepted

2.3. Problems detected and corrected after our discussion in db only

This changes should be brought forward as proposals for v2.7.

2.3.1. Chapter 16 uses logical groups without any indication

Adding "<" and ">" (as a choice out of one) into the segment column for messages solves this problem.

Section	Message Structure
16.3.1	EHC_E01
16.3.2	EHC_E02
16.3.3	QBP_E03
16.3.4	RSP_E03
16.3.5	EHC_E04
16.3.9	EHC_E15
16.3.10	EHC_E20
16.3.11	EHC_E21
16.3.12	QBP_E22
16.3.13	RSP_E22
16.3.14	EHC_E24

2.4. problems detected and corrected after our discussion in db and docs

Section	Issue	Comment
16.3.2:	EHC_E02:	wrong grouping for PSS, one "{" too much
16.3.5:	EHC_E04:	groupname PSG => PRODUCT_SERVICE_GROUP
16.3.10:	EHC_E20:	ADJ has wrong closing bracket
9.5.2/6/8/10:	MDM_T02:	adjusted opening bracket for OBX.Groupname still missing

3. Changes within the database on v2.6 only

3.1. RSP_K11

Different Message structures are defined:

RSP_K11
MSH
[{ SFT }]
[UAC]
MSA
[ERR]
QAK
QPD
5.4.1	5.3.3.2	5.9.6.1	5.3.1.2
[			[
...	[...]	DSP	RDF
			[{RDT}]
]			]
[DSC]	[DSC]	[DSC]	[DSC]

Section 5.4.1 is selected to be correct for the database.

3.2. QBP_Q13

Seq No	5.3.1.2	5.3.3.1	5.4.2	5.9.3.1.1	5.9.3.2.1	5.9.4.1.1	5.9.7.1	5.9.7.2
1	MSH	MSH	MSH	MSH	MSH	MSH	MSH	MSH
2	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]
3	[UAC]	[UAC]	[UAC]	[UAC]	[UAC]	[UAC]	[UAC]	[UAC]
4	QPD	QPD	[EVN]	QPD	QPD	QPD	QPD	QPD
5	[RDF]	[RDF]	QPD	[RDF]	[RDF]	[RDF]	PID	RCP
6	RCP	RCP	[	RCP	RCP	RCP	RCP	[RDF]
7	[DSC]	[DSC]	...	[DSC]	[DSC]	[DSC]	[RDF]	[DSC]
8			]				[DSC]
9			[RDF]
10			RCP
11			[DSC]

Section 5.3.1.2 seems to be correct for the database.

3.3. QBP_Q15

Seq no	5.3.3.3	5.4.3	5.9.5.1	5.9.6.1
1	MSH	MSH	MSH	MSH
2	[{SFT}]	[{SFT}]	[{SFT}]	[{SFT}]
3	[UAC]	[UAC]	[UAC]	[UAC]
4	QPD	EVN	QPD	QPD
5	RCP	QPD	RCP	RCP
6	[DSC]	...	[DSC]	[DSC]
7		RCP
8		[DSC]

Section 5.3.3.3 seems to be correct for the database.

3.4. ADT_A30

Section	Comment	Status
3.3.30:	added ARV behind first PD1deprecated event	error
3.3.34	correct - no change necessary though this event is deprecated event	ok
3.3.35:	added ARV behind first PD1	error
3.3.36	correct - no change necessary though this event is deprecated event	ok
3.3.47	in use - no change necessary	ok
3.3.48:	added ARV behind first PD1deprecated event	error
3.3.49:	added ARV behind first PD1	error

3.5. ADT_A01

Section	Comment	Status
3.3.13:	added ARV behind first PD1should be in sync with A01 as the master.	error

3.6. ADT_A43

Section	Comment	Status
3.3.43:	added ARV behind first PD1to be in sync with A44	error

3.7. ACK^A18

Section	Comment	Status
3.3.18:	ACK^A18: added UACThe event is deprecated. Nevertheless, the acknowledgement should be in sync with all others.	error(typo)

3.8. MFK_M01

Section	Comment	Status
8.4.1	added UAC
8.8.2	added UAC

3.9. QRY^PC4

Section	Comment	Status
12.2.5:	added SFT + UAC to QRY^PC4

3.10. RRE_O12

Section	Comment	Status
4.13.14:	vinserted [{NTE}] after RXE to be in sync with 4.13.64.13.6 is the master message definition. It seems that the change hasn't been applied to all occurrences.

3.11. ORU_R01

Section	Comment	Status
5.7.3.1	added ROL behind NTE to be in sync with 7.3.1
5.7.3.1	added OBX in PATIENT group

Last Update: November 18, 2007