Additional Errata Identified in ELR IG

5/28/2013 - Voted 9 1 0 :

Additional Errata identified in ELR IG

Approach is to review and approve errata below, format like earlier ELR Errata and Clarifications ( see figure below) and publish.

1)  OBR-2 (Placer Order Number): Cardinality should be [0..1] instead of [1..1] as published. (typo)

2)  HD.2 (Universal ID): Comment should read ( eh- bold is to highlight the error) : “Must be an OID except for ELR Sending Facility for MSH-4 where a CLIA identifier is allowed”, instead of “for ELR Receiver for MSH-3 where a CLIA identifier is allowed.” (technical correction)

3)  HD.3 (Universal ID Type): Comment should read ( eh- bold is to highlight the error):”Constrained to the value ‘ISO’ except for ELR Sending Facility for MSH-4 where the value ‘CLIA’ is allowed”, instead of “for ELR Receiver for MSH-4 where the value ‘CLIA’ is allowed.” (technical correction)

4)  MSH-2 (Encoding characters): Although the truncation character (#) is present in MSH-2, it is not used in the ELR v2.5.1 message as such. ( Suggest change comment to ‘Constrained to the literal values ‘^~\&’ or ‘^~\&#’, always appearing in the same order.’ – eh this may be too substantive change? ) too substantive/harmful – NIST implementing. - Conclusion is not an errata.

5)  TQ1 segment (Timing/Quantity): ELR guide erroneously marked as ‘O’ optional, but it is a required segment per the underlying HL7 v2.5.1 standard. This has no bearing on the testing as it is part of an optional group, but it should be corrected in the next release. (technical correction) add Comment to state this to meet the technical requirement – however Group is optional. Only if the Group is popualated then TQ1 Is requireed

6)  OBR-22 (Results Rpt/Status Chng - Date/Time): Need to correct the error in the timestamp notation to YYYYMMDDHHMM[SS[.S[S[S[S]]]]]+/-ZZZZ (typo)

7)  Typographical error in Implementation Guide in Comments field for Timestamp format in OBR.7 and OBX.14. Should be changed to YYYYMMDD[HH[MM[SS[.S[S[S[S]]]]]]][+/-ZZZZ]. (typo)

8)  CE datatype usage is O in Table 6.1.1.1 but X in Table 2-2 and not defined for ELR –Receiver in table 2-3. ( EH – regarding table 2-3 this may be too substantive a change to be an errata?) too substantive a change table 2-2 is correct. – Instead of Errata provide Clarification intent not to allow CE in OBX.5 rather CWE. (Note for EH release remove CE from CWE ? )

9)  The value set listed in the ELR IG for PRL.1 should be “Laboratory Observation Identifier Value Set” instead of “Laboratory Observation Value Set”. (typo)

10)  SPM-1 Add text to comment to comment attribute reflect the constraint for ELR to 1 specimen per message as outlined in the specimen group “For ELR: Literal Value ‘1’” ( clarification)

11)  In the table 2.3.17 HD – Hierarchic Designator the term “Local” should be removed from the first row of the ”Value Set” column since it does not describe a defined value set. (technical correction) move to comment attribute

12)  In Table 6.1 the value set for OBX-5 coded values is named “Laboratory Coded Observation Value Set” while in Table 5.12 the same value set is named “Coded Laboratory Observation Value Set” – Change table 5.12 to “Laboratory Coded Observation Value Set”. (typo)

13)  6.1.1.4 HL7 Table 0301 - Universal ID Type represents the V2.5.1 table instead of the V2.7.1 as is listed in table 6-1 and therefore is missing “CLIA” as an O Usage for MSH-4.3. Change 6.1.1.4 HL7 Table 0301 to V2.7 value set and set “CLIA” as an O Usage for MSH-4.3.

V2.7.1

14)  The length of XCN.13 is listed as 2..5 in the guide and refers to the unconstrained HL7 table 203 (Identifier Type) - the smallest value in that table has only 1 character and currently causes an error - example 'U' for 'Unspecified Identifier'. Change length to 1..5. Added comment: Based on underlying standard so need to take to HL7 Standard as well.

15)  (SAME as 15) The length of CX.5 is listed as 2..5 in the guide and refers to the unconstrained HL7 table 203 (Identifier Type) - the smallest value in that table has only 1 character and currently causes an error - example 'U' for 'Unspecified Identifier'. Change length to 1..5. Added comment: Based on underlying standard so will to take to HL7 Standard as well.

16)  (SAME as 15)The length of XON.7 is listed as 2..5 in the guide and refers to the unconstrained HL7 table 203 (Identifier Type) - the smallest value in that table has only 1 character and currently causes an error - example 'U' for 'Unspecified Identifier'. Change length to 1..5. (technical correction) - double check with underlying standard first (2.7.1) Added comment: Based on underlying standard so will take to HL7 Standard as well.