LRI+Implementation+Guide+Ballot+Reconciliation

include component="page" wikiName="siframework" page="LRI Header" The "HL7 Version 2.5.1 Implementation Guide: S&I Framework Lab Results Interface, Release 1- US Realm" was submitted to HL7 for review and comment Friday 9/16/2011, and this out-of-cycle HL7 balloting period will close on 10/17/2011.

The ballot document is here:

To sign up for submitting comments through the HL7 ballot process please visit the HL7 Ballot page. About halfway down the page you will find an entry for the "HL7 Version 2.5.1 Implementation Guide: S&I Framework Lab Results Interface, Release 1- US Realm", the far right column has a zip file containing the ballot spreadsheet to use.

Please follow the instructions for submitting comments for members and/or non-members (Note: non-members may participate in official HL7 ballots for a nominal $50 fee). Alternately, you can edit this page and insert comments in the table below, however note that the cut-off for comments submitted via the wiki is 8:00AM ET October 13 so we have time to transcribe them to the official HL7 ballot documents and submit before the deadline.

The S&I Framework strongly encourages participants to submit comments directly to HL7 to retain full control of their vote type (ability to withdraw, accept dispositions, etc).


 * HL7 BALLOT POOL SIGN-UP DEADLINE: ** Monday, October 10, 11:59PM ET - If you intend to vote directly via HL7 you MUST sign-up by this date or you will not be permitted to submit a vote.

**HL7 COMMENT DEADLINE:** Monday, October 17, 11:59PM ET

**WIKI COMMENT DEADLINE:** Thursday, October 13, 8:00AM ET.

Notes on the use of the Comments Section below
Vote and Type - please use the following values for the Vote and Type column: //**Negative Votes:**// 1. (Neg-Mj) Negative Vote with reason, Major. Use this in the situation where the content of the material is non-functional, incomplete or requires correction before final publication. All Neg-Mj votes must be resolved by committee. 2. (Neg-Mi) Negative Vote with reason, Minor Type. Use this when the comment needs to be resolved, but is not as significant as a negative major. //**Affirmative Votes:**// 3. (A-S) Affirmative Vote with Comment - Suggestion. Use this if the committee is to consider a suggestion such as additional background information or justification for a particular solution. 4. (A-T) Affirmative Vote with Comment - Typo. If the material contains a typo such as misspelled words, enter A-T. 5. (A-Q) Affirmative Vote with Question. 6. (A-C) Affirmative Vote with Comment.

If you wish to be present when your comment is discussed, please put a (Y) followed by your email and/or phone number. The committee will contact you and let you know how and when you can participate in the comment resolution discussions.

We recommend ACK and not ACK_R01. ||  || Specimen Type. For Example - Union of HL70487 and SNOMED CT Specimen hierarchy ||  ||  For Instance NPI and Taxonomy ID could be used for the following elements. PVI.52 -- Other Healthcare Provide. ORC.12 - Ordering Provider. ||  || For Example - HL7 V3 Healthcare Service Location codes. ||  || For Example – PV1.4-Admission Type - We could use National Uniform Billing Committee (NUBC) codes as referenced in Meaningful Use Stage -1 Measures. ||  || Shouldn't it read "LRI-EI.a-1: EI.4 (Universal ID Type) SHALL contain the value “ISO”." ? ||  || Shouldn't it read "LRI-EI.a-2: IE.2 (Namespace ID) SHALL be valued with an ISO-compliant OID." ? ||  || Actually, OBR.12 is "Danger Code", not "Ordering Provider" ||   ||
 * **Reviewer's Name** || **Organization** || **IG Section** || **IG Page Number** || **Vote and Type*** || **Current Wording** || **Proposed Wording** || **Comment** || **In Person Resolution** ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 3.3.12 || 72 ||  ||   ||   || There is a brief mention of SNOMED, UCUM and LOINC in the IG Page 84, but the value sets are not included. Our recommendation is to include the value set. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team ||  ||   ||   ||   ||   || We recommend the Implementation Guide (IG) should consider the inclusion of local or home grown codes for CLIA and EHR certification purpose only (EHR and LIS system). ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 3.3.12 || 74 ||  ||   ||   || Implementation Guide (IG) uses HL7 v3 for Observation Method. This adds an additional constraint on LIS and EHR to implement HL7 v 3 value sets. Also most of the LIS systems still use HL7 v 2.x. We recommend the Implementation Guide (IG) should find an alternative code set to the use of HL7 V3 Observation Method. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.6 || 87 ||  ||   ||   || HL7 Table 0354 – MESSAGE STRUCTURE is constrained to ORU_R01 and ACK_R01.
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.1 || 88 ||  ||   ||   || Value set for HL70487 to be referenced to HL7 2.7 instead of HL7 2.5.1. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.1 || 89 ||  ||   ||   || We recommend the Implementation Guide (IG) to determine the value set for Laboratory Observation Identifier. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.1 || 89 ||  ||   ||   || We recommend the Implementation Guide (IG) to determine the value set for Laboratory Coded Observation. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.1 || 89 ||  ||   ||   || We recommend the Implementation Guide (IG) to determine the value set for New codesystem in the OBR field. ||   ||
 * || ONC-S&I Framework -- Validation Suite Support Team || 4.1 || 90 ||  ||   ||   || We recommend the Implementation Guide (IG) to determine the value set for
 * || ONC-S&I Framework -- Validation Suite Support Team || 3.7 || 59 ||  ||   ||   || We recommend the Implementation Guide (IG) to reference National Provider ID (NPI) or Taxonomy to identify any Healthcare Provider, Facility, etc.
 * || ONC-S&I Framework -- Validation Suite Support Team ||  ||   ||   ||   ||   || We recommend the Implementation Guide (IG) should identify the value set for Assigned Patient Location.
 * || ONC-S&I Framework -- Validation Suite Support Team || 3.3.7 || 57 ||  ||   ||   || We recommend the Implementation Guide (IG) to identify the value set for Admission Type.
 * Tom Boal || ONC Contractor (Lockheed Martin) || 2 || 14 || Neg-Mi ||  ||   || Datatype "FN" is referenced three times in the the LRI IG v0.6 (pp.36, 38, 42), but there is no FN entry in the Datatypes section (see p. vi of the LRI IG v0.6). ||   ||
 * Tom Boal || ONC Contractor (Lockheed Martin) || 2 || 14 || Neg-Mi ||  ||   || In Table 2.1 (p. 14) "CE – CODED ELEMENT", the "DT" and "Use" columns are reversed (all of the other tables have DT as the left-most column: "CE – CODED ELEMENT" has "Use" as the left-most column) ||   ||
 * Tom Boal || ONC Contractor (Lockheed Martin) || 2.32 || 34 || Neg-Mi ||  ||   || In the LRI IG, in Table 2.32 (p. 34), the first field of XAD is "Street Address" of datatype SAD. However, the datatype SAD is not included in the LRI IG v0.6. ||   ||
 * Tom Boal || ONC Contractor (Lockheed Martin) || 2.10 || 24 || Neg-Mi ||  ||   || In section 2.10, page 24 of the LRI IG, it states "LRI-EI.a-1: CE.4 (Universal ID Type) SHALL contain the value “ISO”."
 * Tom Boal || ONC Contractor (Lockheed Martin) || 2.10 || 25 || Neg-Mi ||  ||   || In section 2.10, page 25 of the LRI IG, it states "LRI-EI.a-2: CE.2 (Namespace ID) SHALL be valued with an ISO-compliant OID."
 * Tom Boal || ONC Contractor (Lockheed Martin) || 3.3.10 || 69 || Neg-Mi ||  ||   || On p 69 of the LRI IG v 0.6, there are two entries with the same label: LRI-OBR-3 ||   ||
 * Tom Boal || ONC Contractor (Lockheed Martin) || 3.3.10 || 69 || Neg-Mi ||  ||   || On p. 69 of the LRI IG v0.6, it says "LRI-OBR-7: The value of OBR.12 (Ordering Provider) SHALL be identical to the value of OCR.3 (Ordering Provider)".
 * Tom Boal || ONC Contractor (Lockheed Martin) || 3.3.11 || 71 || Neg-Mi ||  ||   || On page 71 of the LRI IG v0.6, it states "LRI-TQ1-3: OBR.9 (Priority) SHALL be valued using the CWE – Coded with Exceptions – All Fields Except OBX-5 datatype definition and constraints." I think you mean to say "LRI-TQ1-3: TQ1.9 (Priority) SHALL be valued using the CWE – Coded with Exceptions – All Fields Except OBX-5 datatype definition and constraints." ||   ||
 * Tom Boal || ONC Contractor (Lockheed Martin) || 3.3.12 || 76 || Neg-Mi ||  ||   || On p. 76 of the LRI IG V0.6, it twice has a heading of "Conformance Statement: LRI-GU Profile". The second instance should probably read "Conformance Statement: LRI-NG Profile" ||   ||

Documents that will be incorporated into the next version of the IG
The following documents have been identified as useful information to be discussed and potentially inserted into the guide.
 * **Document Name** || **Description** ||
 * [[file:NLM Example UCUM Codes.zip]] || Examples of UCUM coding ||

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"