The HL7 Comprehensive Database: Corrections to Version 2 |
| Home -> HL7 -> Comprehensive Database -> Corrections to Version 2 |
The database sold by Health Level Seven, Inc. is unfortunately not free of errors. Nevertheless this homepage should provide a means to inform about necessary corrections which should by applied to the database. This page is updated as soon as new errors are reported and verified.
In order to reduce the amount of effort the are sorted chronologously (newest at first).
I have been aware, that in some cases the link between a form and its subform for message definitions might be corrupt. Please check that for form "SubformEvents with Messages":
| link from: | event_code;hl7_version;message_type |
| link to: | event_code; hl7_version;message_typ_snd |
First the latest corrections:
| Version | Correction |
|---|---|
| v2.3.1 | OBX-2 + OBX-4: R -> C; OBX-6 - OBX-10: X -> O OBX-12 - OBX-17: X -> O |
| 2.4 | NA + MA: the components can "repeat", i.e. the same one can occur quite often. This can't be stored in the database without a change in the db structure. Therefore this issue is left open. |
| 2.4 | CX.2 NM -> ST |
| 2.3.1 | PPN.1 NM -> ST |
| 2.2 | FT1-11/12/15 MO => NM |
| 2.3 | FT1-11/12/15 NM/PL/NM => CP |
| 2.3 | RXA-5: assign table 0292 |
| 2.3 | RXA-1: don't assign a table |
| 2.3 | RXA-21: use data element 01224 instead of 00816 |
| 2.3 | RXA, RXD-7, RXD-19: req./opt. |
| 2.2 | OM2-4/6/7: rep. |
| 2.3 | PDC: req./opt. |
| 2.3.1, 2.4 | checked for CM data types: CD, DLT, RFR, TQ, PN, PPN, XCN and XPN |
| 2.3.1, 2.4 | STF-20 + ORG-10: data element 01276 length corrected 250 -> 2 |
| 2.3.1, 2.4 | addendum for CM data types checked: PEN -> MOP, NDL.1, RFR.1, DLT.1 |
| 2.3.1, 2.4 | delete data type CM |
| 2.3, 2.3.1 | OBR in ORR_O02 is not optional |
Next some corrections as identified by the HAPI project in Canada (thanks to Brian Tipp):
| Version | Correction |
|---|---|
| 2.2 | Components table, component #12: change code identifing error-> code identifying error |
| 2.2 | Components table, component #1: change message typ -> message type |
| 2.3 | DataStructureComponents table, CM_RFR: lfd_nr= 6: change component 436 -> 437; lfd_nr = 7: change component 437 ->438 |
| 2.3, 2.3.1 | Components table, component #315 change "sample 2 from channel 1" to "sample 2 from channel 3" |
| 2.3.1, 2.4 | DataElements table, D-item 18 change "Acknowledgment Code" to "Acknowledgement Code" |
| 2.4 | MsgStructIDSegments table, ORU_R01 several changes of field #, to be consistent with numbering in EventMessageTypeSegments (so that union query doesn't produce duplicates) change 33 to 36 change 35 to 38 change 37 to 40 change 41 to 44 change 44 to 47 change 45 to 50 change 47 to 55 change 50 to 58 change 51 to 59 change 53 to 61 |
| 2.3.1 |
MsgStructIDSegments table: ORM_O01 added several segments and changed numbering of later segments. The existing database entries reflect the message structure in section 4.2.1, but there appears to be a conflicting definition in section 4.8.1 that refers to additional segments. These changes accommodate both 4.2.1 and 4.8.1: change 56 to 58 change 59 to 61 change 60 to 62 change 63 to 76 change 64 to 77 change 65 to 78 change 68 to 81 change 71 to 84 change 72 to 85 change 73 to 86 change 76 to 89 change 80 to 93 change 82 to 95 add 56 | add 57 RXO moved from 50/51 |
| 2.3, 2.3.1 | Components table, Comp=302 change "data subtype" to "data" |
| 2.3, 2.3.1 | Components table, Comp=340 change "data" to"data subtype" |
| 2.3, 2.4 | SegmentDataElements table OBX-5 (not sure about v2.1, v2.2) rep = Y |
| 2.1 | DataStructureComponents table: added components 1-6 for CE (used comp #144-149) |
| 2.1 | Components table: added components 144 (ID) and 145-149 (ST) for CE components |
| 2.1 | DataElements table: element 00581 changed "PATIENT ID (EXTERNAL ID)" to "PATIENT ID EXTERNAL (EXTERNAL ID)" because we're eliminating everything in the brackets -- most often the datatype |
| 2.1 | DataElements table: element 00034 changed "PATIENT ID (INTERNAL ID)" to "PATIENT ID INTERNAL (INTERNAL ID)" because we're eliminating everything in the brackets -- most often the datatype |
| Type | Version | Comment | Correction |
|---|---|---|---|
| message | 2.4 | check message structure for ORM^O01 and ORR^O02 | |
| 2.3.1 and 2.4 | new release of the database to introduce technical corrections | ||
| CM replacement | 2.3.1 2.4 |
The CM replacement project proposes changes to the different CM datatypes, i.e. replace them individually. | replace as proposed |
| datatype CE | 2.4 | The first component of CE data types should be ST | Execute the following SQL-statement: "UPDATE DataStructures INNER JOIN DataStructureComponents ON (DataStructures.hl7_version = DataStructureComponents.hl7_version) AND (DataStructures.data_structure = DataStructureComponents.data_structure) SET DataStructureComponents.comp_nr = 391 WHERE (((DataStructures.hl7_version)="2.4") AND ((DataStructures.data_type_code)="CE") AND ((DataStructureComponents.lfd_nr)=1) AND ((DataStructureComponents.comp_nr)=3));" |
| datatype CF | 2.4 | The fourth component should be ID | |
| datatype TS | 2.2 - 2.4 | it is a complex data type | define a first and second component |
| datatype XPN | 2.4 | renumber the components, since the 2nd one is skipped | |
| datatype CM_FAM_NAME | 2.4 | delete it (it is not used) | |
| segment OBX | 2.4 | the specification of required/optional is wrong in some places | components 2,5: "X" -> "C"; 6-10, 12-17: "X" -> "O" |
Last Update : October 07, 2003