The HL7 Comprehensive Database: Corrections to Version 6 |
Home -> HL7 -> Comprehensive Database -> Corrections to Version 6 |
The sixth release of the database is available since the May WGM in Orlando 2011.
I have done my best to get it free of errors.
Anyhow, sometimes several minor adjustments are necessary even after its release.
They are listed below.
In order to reduce your amount of efforts to check the details they are sorted chronologously (newest entry comes first).
Version | Type | Entry | Correction | Section | Date |
---|---|---|---|---|---|
v2.3 | table | 0278 | value "BLOCKED": placed usage note in comment field | 10.05.13 | |
all | table | 0287 | value "UC" = "UNCHANGED" (asterisk deleted) | 10.05.13 | |
2.3.1, 2.4, 2.5, 2.5.1, 2.6, 2.7, 2.7.1 | table | 0256 | value "2.5H" = "2 1/2 hours" | 10.05.13 | |
2.3.1, 2.4 | table | 0153 | expand values: "70..72" and "75..79" | 10.05.13 | |
several | table | 0162 | removed asterisk from some values and placed it in the comment field | 10.05.13 | |
2.3 | table | 0175 | expand values: "OM1-OM6" | 10.05.13 | |
2.1, 2.2 | table | 0097 | delete table | 10.05.13 | |
2.2 | table | 0187 | table name: "Provider billing" | 10.05.13 | |
2.6 | table | 0119 | "SN" = "Send order/service number" "NW or RO": delete |
10.05.13 | |
2.1, 2.3.1 | table | 0092 | add value "R" for "Readmission" | 10.05.13 | |
2.1, 2.2 | table | 0095 | unused => delete | 10.05.13 | |
2.2 | table | 0096 | unused => delete | 10.05.13 | |
2.3 | table | 0079 | erroneously assigned to NPU-1 => dissassign from data element (table cannot be found in documents) | 10.05.13 | |
2.3 | table | 0060 | erroneously assigned to ERR-1 => dissassign from data element 00024 and delete entry from table | 10.05.13 | |
2.3 | table | 0084 | consistent name: "performed by" | 10.05.13 | |
2.7.1 | msg structures | SRR_S01 | correct groupname: "RESOURCES" to "RESOURCE" | 09.05.13 | |
2.7.1 | msg structures | RSP_E22 | introduce choice group to keep groupnames | 09.05.13 | |
2.7.1 | msg structures | OML_O21, OML_O33, OML_O35 | change groupname: "TIIMING" to "TIMING" | 09.05.13 | |
2.7.1 | msg structures | CCI_I22, CCM_I21, CCR_I16, CCU_I20, CQU_I19 | change groupname: "RESOURCED_DETAIL" to "RESOURCE_DETAIL" | 08.05.13 | |
2.7.1 | msg structures | CCM_I21 | wrong character in groupname: "ROLE_CLINICAL_HISTORY " | 08.05.13 | |
2.7.1 | msg structures | BRP_O30 | wrong message structure with groups PATIENT and RESPONSE: added closing bracket for PATIENT before closing bracket of RESPONSE | 08.05.13 | |
2.7.1 | msg structures | OPU_R25 | change groupname to not contain blanks: "PATIENT VISIT OBSERVATION" to "PATIENT_VISIT_OBSERVATION" | 05.05.13 | |
2.7.1 | msg structures | OUL_R23, OUL_R24 | change groupname to not contain blanks: "SPECIMEN OBSERVATION" to "SPECIMEN_OBSERVATION" | 05.05.13 | |
2.7.1 | msg structures | DFT_P11 | change groupname to not contain blanks: "FINANCIAL_TIMING QUANTITY" to "FINANCIAL_TIMING_QUANTITY", "FINANCIAL_TIMING QUANTITY" to "FINANCIAL_TIMING_QUANTITY" | 05.05.13 | |
2.7.1 | msg structures | DFT_P03 | change groupname to not contain blanks: "FINANCIAL_COMMON ORDER" to "FINANCIAL_COMMON_ORDER", "FINANCIAL_TIMING QUANTITY" to "FINANCIAL_TIMING_QUANTITY" | 05.05.13 | |
2.7.1 | msg structures | RSP_Z86 | change groupname to not contain blanks: "ENCODED ORDER" to "ENCODED_ORDER" | 05.05.13 | |
2.7.1 | msg structures | OPL_O37 | change groupname to not contain blanks: "OBSERVATION REQUEST" to "OBSERVATION_REQUEST", "PATIENT PRIOR" to "PATIENT_PRIOR", "PATIENT VISIT PRIOR" to "PATIENT_VISIT_PRIOR", "ORDER PRIOR" to "ORDER_PRIOR", "Observation/Result_Group" to "OBSERVATION_RESULT" | 05.05.13 | |
2.7.1 | msg structures | OSM_R26 | change groupname to not contain blanks: "SUBJECT PERSON/ANIMAL IDENTIFICATION" to "SUBJECT_PERSON_ANIMAL_IDENTIFICATION", "SUBJECT POPULATION/LOCATION IDENTIFICATION" to "SUBJECT_POPULATION_LOCATION_IDENTIFICATION" | 05.05.13 | |
2.7.1 | msg structures | MFN_M16 | change groupname to not contain blanks: "MATERIAL ITEM RECORD" to "MATERIAL_ITEM_RECORD" | 05.05.13 | |
2.7.1 | msg structures | SRM_S01, SRR_S01 | change groupname to not contain blanks: "GENERAL RESOURCE" to "GENERAL_RESOURCE", "LOCATION RESOURCE" to "LOCATION_RESOURCE", "PERSONNEL RESOURCE" to "PERSONNEL_RESOURCE" | 05.05.13 | |
2.7.1 | msg structures | CSU_C09 | change groupname to not contain blanks: "COMMON ORDER" to "COMMON_ORDER" | 05.05.13 | |
2.7.1 | msg structures | CCI_I22, CCM_I21, CCR_I16, CCU_I20, CQU_I19 | change groupname to not contain blanks: "APPOINTMENT HISTORY" to "APPOINTMENT_HISTORY" | 05.05.13 | |
2.7.1 | msg structures | EHC_E01 | change groupname to not contain blanks: "PRODUCT/SERVICE LINE_INFO" to "PRODUCT_SERVICE_LINE_INFO", "INVOICE INFORMATION" to "INVOICE_INFORMATION" | 05.05.13 | |
2.7.1 | msg structures | EHC_E10 | some groupnames are missing: "PRODUCT_SERVICE_SECTION" for PSS segment, "PRODUCT_SERVICE_GROUP" for PSG segment | 05.05.13 | |
2.7.1 | msg structures | CRM_C01, RRI_I12, REF_I12 | change groupname to not contain blanks: "PATIENT VISIT" to "PATIENT_VISIT" | 05.05.13 | |
2.7.1 | msg structures | OUL_R22, ORU_R30, ORU_R01, OUL_R23, OUL_R24 | change groupname to not contain blanks: "PATIENT OBSERVATION" to "PATIENT_OBSERVATION" | 05.05.13 | |
2.7.1 | msg structures | ORL_O34, ORL_O36, OML_O39, OUL_R22 | change groupname to not contain blanks: "SPECIMEN OBSERVATION" to "SPECIMEN_OBSERVATION" | 05.05.13 | |
2.7.1 | msg structures | ADT_A60 | change groupname to not contain blanks: "ADVERSE REACTION GROUP" to "ADVERSE_REACTION_GROUP" | 05.05.13 | |
2.3 | msg structures | O01 RGV | the structure was represented with wrong optionality | 26.04.13 | |
2.3 | msg structures | Q06 | the choice structure around OBR is not clearly specified, but should definitely be present | 26.04.13 | |
2.3 | msg structures | M09 | OM1 was missing in the message | 26.04.13 | |
2.3 | msg structures | M10 | MFE + OM1 was missing in the message | 26.04.13 | |
2.6, 2.7 | msg structures for msg types | EHC + QBP + RSP | opening choice brackets are not repeating/optional | 25.11.11 | |
2.5, 2.6, 2.7 | table | 0550 | "external jugular": no proper value | 13.10.11 | |
2.5, 2.6, 2.7 | table | 0550 | corrected table values: CHEST, KIDN | 13.10.11 | |
2.7 | table | 0667, 0682, 0702 | corrected table name: delete dash | 13.10.11 | |
2.6 | table | 0725 | deleted wrong entries | 13.10.11 | |
2.2 | data type | CM_RANGE | data type NM instead of CE_RANGE is correct for both components | 10.9.11 | |
2.7 | data_structure for components | complex data structures | the components refer to the wrong data structure. This can be corrected with this SQL statement: UPDATE HL7Components INNER JOIN (HL7DataStructures INNER JOIN HL7DataStructureComponents ON (HL7DataStructures.version_id = HL7DataStructureComponents.version_id) AND (HL7DataStructures.data_structure = HL7DataStructureComponents.data_structure)) ON (HL7DataStructures.version_id = HL7Components.version_id) AND (HL7Components.version_id = HL7DataStructureComponents.version_id) AND (HL7Components.comp_no = HL7DataStructureComponents.comp_no) SET HL7Components.data_structure = [hl7components].[data_type_code] WHERE (((HL7DataStructures.version_id)=8) AND ((HL7Components.data_type_code)<>[hl7components].[data_Structure])); |
24.7.11 | |
2.7 | table_values | replace specific character for 3 dots "..." by 3 dots | 10.7.11 | ||
2.7 | data element | 00868 | datatype = NM (only SCH-9 is withdrawn, but not ARQ-9) | 10 | 26.5.11 |
2.7 | data element | 00386 | datatype = NM (only DG1-12 is withdrawn, but not DRG-7) | 6 | 26.5.11 |
2.7 | data element | 00387 | datatype = CP (only DG1-12 is withdrawn, but not DRG-7) | 6 | 26.5.11 |
2.7 | data element | 00299 | datatype = LA1 (only RXE-8 is withdrawn, but not RXO-8) | 4A | 26.5.11 |
2.7 | data element | 00248 | datatype = DTM (only OBR-14 is withdrawn, but not SPM-18) | 4 | 26.5.11 |
2.7 | message structure | ORU_R01 | segment groupname ="PATIENT_OBSERVATION" (instead of "PATIENT OBSERVATION") | 7.3.1 | 26.5.11 |
2.7 | message structure | ORU_R01 | segment groupname ="SPECIMEN_OBSERVATION" (second group should have a different name) | 7.3.1 | 26.5.11 |
2.7 | segment | ORC-5 | min length should be 1 | 4 | 22.5.11 |
Some errors are caused by the standard and should therefore be treated as technical corrections:
Version | Type | Entry | Correction | Section | Date |
---|---|---|---|---|---|
some | table | 0255, 0256 | description for value "2.5H" corrected because of character set | 21.8.12 | |
2.3.1 | table | 0333 | table values belong to table 0409, this table is named "Driver’s license issuing authority" | 22.6.12 | |
2.6 | message structure | EHC_E10 | segment groupname ="PRODUCT_SERVICE_LINE_INFO" (instead of "PRODUCT/SERVICE LINE_INFO") | 7.6.11 | |
2.6 | message structure | NMD_N02, NMD_N02 | segment groupname ="CLOCK_AND_STATS_WITH_NOTES" (instead of "CLOCK_AND_STATS_WITH_NOTES ") |
7.6.11 | |
2.5.1, 2.6, 2.7 | message structure | DFT_P03, DFT_P11 | segment groupname ="FINANCIAL_TIMING_QUANTITY" (instead of "FINANCIAL_TIMING QUANTITY") segment groupname ="FINANCIAL_COMMON_ORDER" (instead of "FINANCIAL_COMMON ORDER") |
7.6.11 | |
2.6, 2.7 | message structure | SRM_S01, SRR_S01 | segment groupname ="GENERAL_RESOURCE" (instead of "GENERAL RESOURCE") | 7.6.11 | |
2.6, 2.7 | message structure | EHC_E01 | segment groupname ="INVOICE_INFORMATION" (instead of "INVOICE INFORMATION") | 7.6.11 | |
2.6, 2.7 | message structure | MFN_M16 | segment groupname ="MATERIAL_ITEM_RECORD" (instead of "MATERIAL ITEM RECORD") | 7.6.11 | |
2.7 | message structure | EHC_E24 | segment groupname ="PAYER_ADJUSTMENT" (instead of "PAYER_ADJUSTMENT Begin") | 7.6.11 | |
2.6, 2.7 | message structure | EHC_E15 | segment groupname ="PAYMENT_REMITTANCE_HEADER_INFO" (instead of "PAYMENT_REMITTANCE_HEADER_INFO End") | 7.6.11 | |
2.6, 2.7 | message structure | EHC_E15 | segment groupname ="PAYMENT_REMITTANCE_DETAIL_INFO" (instead of "PAYMENT_REMITTANCE_DETAIL_INFO End") | 7.6.11 | |
2.6, 2.7 | message structure | EHC_E20 | segment groupname ="PSL_ITEM_INFO" (instead of "PSL_ITEM_INFO End") | 7.6.11 | |
2.6 | message structure | QRF_R04 | segment groupname ="QUERY_RESPONSE" (instead of "QUERY_RESPNSE") | 7.6.11 | |
2.5.1, 2.6, 2.7 | message structure | SIU_S12, SRR_S01 | segment groupname ="RESOURCES" (instead of "RESOURCE") | 7.6.11 | |
2.6, 2.7 | message structure | CSU_C09 | segment groupname ="VISIT" (instead of "VISIT end") | 7.6.11 | |
2.6, 2.7 | message structure | OML_O21, OML_O33, OML_O35 | segment groupname ="TIMING" (instead of "TIIMING") | 7.6.11 | |
2.5.1, 2.6, 2.7 | message structure | RSP_Z86 | segment groupname ="ENCODED_ORDER" (instead of "ENCODED ORDER") | 7.6.11 | |
2.5.1, 2.6, 2.7 | message structure | SRR_S01 | segment groupname ="LOCATION_RESOURCE" (instead of "LOCATION RESOURCE") | 7.6.11 | |
2.6, 2.7 | message structure | OPL_O37 | segment groupname ="OBSERVATION_REQUEST" (instead of "OBSERVATION REQUEST") segment groupname ="PATIENT_PRIOR" (instead of "PATIENT PRIOR") segment groupname ="PATIENT_VISIT_PRIOR" (instead of "PATIENT VISIT PRIOR") |
7.6.11 | |
2.5.1, 2.6, 2.7 | message structure | CRM_C01, REF_I12, RRI_I12 | segment groupname ="PATIENT_VISIT" (instead of "PATIENT VISIT") | 7.6.11 | |
2.7 | message structure | SRM_S01 | segment groupname ="PERSONNEL_RESOURCE" (instead of "PERSONNEL RESOURCE") | 7.6.11 | |
2.6 | message structure | SDR_S31 | segment groupname ="ANTIMICROBIAL_DEVICE_DATA" (instead of "ANTI-MICROBIAL DEVICE DATA") | 7.6.11 | |
2.6 | message structure | SDR_S31 | segment groupname ="ANTIMICROBIAL_DEVICE_CYCLE_DATA" (instead of "ANTI-MICROBIAL DEVICE CYCLE DATA") | 7.6.11 | |
message structure | QBP_Q15, QBP_Qnn | correct structure is still unclear | 7.6.11 | ||
v2.6 | message structure |
Msg.Struct. Seq. Grp.Name ADT_A60 10+14 ADVERSE REACTION GROUP 2x CCI_I22 33 APPOINTMENT HISTORY CCM_I21 31 APPOINTMENT HISTORY CCR_I16 60 APPOINTMENT HISTORY CCU_I20 38 APPOINTMENT HISTORY CQU_I19 40 APPOINTMENT HISTORY CQU_I19 143 ROLE_PATHWAY CSU_C09 34 COMMON ORDER OML_O39 54+57 SPECIMEN OBSERVATION 2x OPU_R25 8+12 PATIENT VISIT OBSERVATION 2x ORL_O34 12+15 SPECIMEN OBSERVATION 2x ORL_O36 12+15 SPECIMEN OBSERVATION 2x ORL_O40 23 PACKAGE Begin ORU_R30 7+10 PATIENT OBSERVATION 2x OSM_R26 28+36 SUBJECT PERSON/ANIMAL IDENTIFICATION 2x OSM_R26 37+47 SUBJECT POPULATION/LOCATION IDENTIFICATION 2x OUL_R22 10+13 PATIENT OBSERVATION 2x OUL_R22 23+26 SPECIMEN OBSERVATION 2x OUL_R23 10+13 PATIENT OBSERVATION 2x OUL_R23 23+26 SPECIMEN OBSERVATION 2x OUL_R24 10+13 PATIENT OBSERVATION 2x OUL_R24 32 SPECIMEN OBSERVATION |
8.6.11 | ||
2.6, 2.7 | message structure | BRP_O30 | missing closing bracket: PATIENT | 4.13.4 | 7.6.11 |
2.6, 2.7 | message structure | CCI_I22, CCM_I21, CCR_I16, CCU_I20, CQU_I19 | wrong group name: RESOURCED_DETAIL -> RESOURCE_DETAIL | 11 | 11.6.11 |
2.7 | message structure | OPL_O37 | wrong group name: TIMING -> TIMING2 (XML does not allow for two identical names) Observation/Result_Group -> OBSERVATION_RESULT_GROUP (no special characters) |
13.6.11 | |
2.7 | message structure | REF_I12, RRI_I12 | wrong group name: AUTHORIZATION_CONTACT -> AUTHORIZATION_CONTACT2 (XML does not allow for two identical names) | 13.6.11 | |
2.7 | message structure | RPA_I08, RQA_I08 | wrong group name: AUTHORIZATION -> AUTHORIZATION2 (XML does not allow for two identical names) | 13.6.11 | |
2.7 | segment | IVC-24 | length information in wrong field | 16.4.2.24 | 14.6.11 |
Some errors can only be adjusted by changing (=correcting) the standard:
Version | Type | Entry | Correction | Section | Date |
---|---|---|---|---|---|
2.7 | message structure | ORU_R01 | segment groupname ="PATIENT_OBSERVATION" (instead of "PATIENT OBSERVATION") | 7.3.1 | 26.5.11 |
2.7 | message structure | ORU_R01 | segment groupname ="SPECIMEN_OBSERVATION" (instead of "PATIENT OBSERVATION") | 4.13.5 | 8.6.11 |
Right now, there are no known errors.
Type | Correction | Date |
---|---|---|
Document Generation: Segments |
Please replace "CreateDoc Segments" with SELECT HL7Segments.seg_code, HL7Segments.version_id, HL7Segments.description, HL7Segments.generate, HL7SegmentDataElements.seq_no, HL7SegmentDataElements.data_item, HL7DataElements.min_length, HL7DataElements.max_length, HL7DataElements.conf_length, HL7DataElements.data_structure, HL7SegmentDataElements.req_opt, HL7SegmentDataElements.repetitional, HL7SegmentDataElements.repetitions, HL7SegmentDataElements.section, HL7DataElements.description AS desc_data, HL7DataElements.interpretation AS interpr_data, HL7DataElements.table_id, HL7DataElements.section AS chp_data FROM HL7Segments INNER JOIN (HL7DataElements INNER JOIN HL7SegmentDataElements ON (HL7DataElements.version_id = HL7SegmentDataElements.version_id) AND (HL7DataElements.data_item = HL7SegmentDataElements.data_item)) ON (HL7Segments.version_id = HL7SegmentDataElements.version_id) AND (HL7Segments.seg_code = HL7SegmentDataElements.seg_code) WHERE (((HL7Segments.seg_code) Not In ("{","}","[","]","NUL","?"))) ORDER BY HL7Segments.seg_code, HL7SegmentDataElements.seq_no; In addition you need to change in "CreateDoc Segments" the row with: doc.Tables(nCntTables).Cell(x, 8) = rs("length") & "" to doc.Tables(nCntTables).Cell(x, 8) = rs("max_length") & "" |
18.5.12 |
Document Generation: Tables |
Please replace "CreateDoc Tables" with: |
18.5.12 |
App Generation | The SQL statement "CreateAppA MsgType" must be corrected to also detect message types on the receiving side: PARAMETERS [HL7-Version] Short; SELECT HL7MessageTypes.message_type, HL7MessageTypes.description, HL7EventMessageTypes.section, HL7Events.version_id FROM HL7MessageTypes INNER JOIN (HL7Events INNER JOIN HL7EventMessageTypes ON (HL7Events.event_code = HL7EventMessageTypes.event_code) AND (HL7Events.version_id = HL7EventMessageTypes.version_id)) ON ((HL7MessageTypes.message_type = HL7EventMessageTypes.message_typ_snd) or (HL7MessageTypes.message_type = HL7EventMessageTypes.message_typ_return)) AND (HL7MessageTypes.version_id = HL7EventMessageTypes.version_id) AND (HL7MessageTypes.version_id = HL7EventMessageTypes.version_id) WHERE (((HL7MessageTypes.message_type)<>"NUL") AND ((HL7MessageTypes.version_id)=[HL7-Version])) ORDER BY HL7MessageTypes.message_type, HL7Events.event_code; |
8.12.11 |
XML schema generation | all optional+repeating segment groups did have a max cardinality of "1". This must be adjusted to "unbounded". Furthermore, the handling of length should be discussed. | 22.5.11 |
XML schema generation | segments without any data elements (all are withdrawn) must be generated | 22.5.11 |
Last Update : May 9, 2013