LRI+IGs+Analysis+WG+Meeting+2011-08-4

include component="page" wikiName="siframework" page="LRI Header" =LRI IGs Analysis WG Meeting Minutes=  **Dial-in:** 1-408-600-3600 **| Passcode:** 660 071 157
 * Date: ** 08/4/2011
 * Time: ** 3:00PM – 4:00PM EDT

Attendance
David Burgess, Kathryn Calderone, Ernest Grove, Freida Hall, Hal Jiang, Austin Kreisler, Diana Massey, Ken McCaslin, Glen Moy, Brian Pech, John Roberts, Jonathan Tadese, Merideth Vida

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 8/2/2011 || Refer to the discussion page for [|parent/child and micro relationship] to post comments. || All || In Progress ||  ||
 * 2 || 8/4/2011 || For any additional changes on the [|Data Types - Value Set Table], please email Jonathan Tadese or Kathryn Calderone; you can also post changes to the discussion tab on the wiki. || All || In Progress ||  ||
 * 3 || 8/4/2011 || Check uniqueness for order numbers. ||  ||   ||   ||
 * 4 || 8/4/2011 || Post an example from implementation guide || Austin Kreisler || In Progress ||  ||

Agenda Items

 * Discuss unresolved issues in the [|Data Types Value Set Table] that are color coded (red).
 * Discuss [|Parent/Child and Micro Relationship] .
 * Discuss the maximum length of field elements (truncation is no longer mentioned (v.2.8). Austin Kreisler to lead this discussion.

Meeting Notes
To access HL7 documents, please follow instructions located here.

**Data Types Value Set Table Discussion ** Please refer to the [|Data Types Value Set Table Document] for changes, decisions, and discussion items.

**Parent/Child and Micro Relationship ** Please refer to the [|discussion page] to make comments. This is an attempt to get a structure for micro reporting into this implementation guide.

The Parent/Child and Micro Relationship approach takes an appendix from HITSP implementation guide for how to report Micro. This proposes an alternate mechanism to make sure that senders are capable of sending parent/child results and receivers can receive information in this format. The parent/child identifiers are dependent on the identifiers in OBR 2 and 3.

EHR vendors, when there are repeat identifiers, are overlaying rather than sequencing identifiers. There is a repeat at the OBR and OBX level for the identifiers. When they are repeated, vendors may overlay data rather than string data together, causing the reports to be incomplete and incorrect.There needs to be two flavors: one for order numbers are unique and one where order number and universal service order numbers are unique.

There is concern over if we can handle producing results the way it is set up in HITSP. Continue this discussion at beginning of Tuesday call (Rob Hausam to attend)

**Next Meeting **
 * <span style="color: black; font-family: 'Arial','sans-serif'; font-size: 10pt;">Discuss Parent/Child and Micro Relationship at the beginning of the call on 8/9.
 * <span style="color: black; font-family: 'Arial','sans-serif'; font-size: 10pt;">Discuss unresolved issues in the Data Types Value Set Table that are color coded (red).

Next Meeting
**<span style="font-family: 'Arial','sans-serif'; font-size: 10pt;">Date: ** <span style="font-family: 'Arial','sans-serif'; font-size: 10pt;">Tuesday 08/09/2011 **<span style="font-family: 'Arial','sans-serif'; font-size: 10pt;">Time: ** <span style="font-family: 'Arial','sans-serif'; font-size: 10pt;">3:00 PM-4:00 PM EDT
 * Dial in:** <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">1-408-600-3600

Reference Materials

 * 1) <span class="wiki_link_ext">[|Data Types - Value Set TBL]
 * 2) <span style="color: black; font-family: 'Arial','sans-serif'; font-size: 10pt;">[|Parent/Child and Micro Relationship Discussion]
 * 3) <span style="color: black; font-family: 'Arial','sans-serif'; font-size: 10pt;">Guidance for accessing HL7 Documents

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