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

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/09/2011
 * Time: ** 3:00PM – 4:00PM EDT

Attendance
David Burgess, Kathryn Calderone, Tara Garrison, Ernest Grove, Freida Hall, Kate Hamilton, Rob Hausam, Lester Keepper, Austin Kreisler, Ken McCaslin, Natalie Menser, Glen Moy, Brian Pech, Zeshan Rajput, Jennifer Sisto, Rob Snelick, Jonathan Tadese, Merideth Vida

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 08/09/2011 || Review IG requirements to confirm that they are testable; Provide feedback. || Rob Snelick || In Progress ||  ||
 * 2 || 08/09/2011 || Discuss IG content and how to best represent conformance requirements with Bob Yencha. || Rob Snelick || In Progress ||  ||
 * 3 || 08/09/2011 || Write up something on the relationships with OBR 50 in conjunction with OBR 29, 26, and other OBX Issues- use spreadsheet comments as guidance (Refer to comment HKM30). || David Burgess || In Progress ||  ||
 * 4 || 08/09/2011 || Reach out to Cindy Johns to schedule time with the Vocab Group so they can provide input on the HL7 Ownership Tables and any sections of the IG that are in question. || Kathryn Calderone || Completed ||  ||

Agenda Items

 * Discuss [|Parent/Child Micro Relationship] .
 * Discuss unresolved issues in the [|Data Types Value Set Table] that are color coded (red).

Meeting Notes

 * **Recap of Last Week: **
 * Request members to not place call on hold because it results in a beeping noise on the line.
 * Last week the group discussed Data Types- on Agenda and Main Page
 * Also discussed parent/child micro relationship
 * **Parent/Child Relationship “Appendix A: ****HL7 Reporting of Cultures and Susceptibilities” of the ELR Document **
 * A concern that was expressed is that where we are using the same identifier for OBX 1, 2, 3, and 4; there may be overlays.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">One possible approach is to ignore the HL7 rules and not allow repeated OBX 3s or other repeated OBXs.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">A question to the group was whether or not anyone is familiar with RELMA (Regenstrief LOINC Mapping Assistant) and can provide some insight?
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;"> Isolate 1 and Isolate 2 reporting? OBX 1, OBX 3?
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">We need to keep in mind the 99 % rule: you will never have everything coded.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">What is here is a good use of OBX3 and OBX 4.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">We need to be as prescriptive as we were about data types in order to really enforce behavior.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">How does Rob’s team develop conformance statements that are appropriate?
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">The draft IG is posted on the main IG Wiki page. It is the first bullet under the to-dos
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Implementation Guide- Last edited by Bob Yencha **
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Rob Snelick made some comments inquiring whether the requirements in the IG were testable; if they seem ambiguous, he will provide feedback.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Updates were made to __Table 6-12 Observation/Result Segment (OBX) //(See highlighted section)://__
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">“OBX 3 in conjunction with OBX 4 Observation Sub ID should uniquely identify this OBX from all other OBXs associated with this OBR.”
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;"> “Repetitions of OBX with the same value in OBX 3.1 with OBX 4 need to make sure the receiver does not overlay or ignore any of the repeats.”
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Rob Snelick will meet with Bob Yencha Thursday to further develop the content of the IG and to discuss how best to represent the conformance requirements.
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Parent/Child Micro Relationship in the IG **
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Seq. 29 in the Table in the IG- need to reconsider the Harmonization condition.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">David Burgess to write something up on the relationships with OBR 50 in conjunction with OBR 29, 26 and other OBX issues. Will use spreadsheet comments as guidance. (Refer to comment HKM30).
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">The IG WG needs to confer with the Vocab WG on whether the following should be included in the IG:. A.2.1. Example of culture results: “Identified, organisms must be reported as coded data instead of text data; Coded data enables machine processing of results. String data can normally be interpreted only by humans.”
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">IG WG also needs the Vocab WG to look at the HL7 Ownership Table document and to complete the areas where there are no suggested values
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Original proposal on managing conformance was modified, and the changes are quite substantial; changes may need to be made to some of the work we have done.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">HL7 Proposal 714 à <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;"> scroll to first table (Conformance Discussion)
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Complex Conditional discussion
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">HL7 V2.X Proposals Database: Go back into the IG guide and modify all conditionals as described here.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">We need to go back and revisit some of the work we have already done: CE has gone away essentially; if you are looking for CE you will be looking for C/RE/X.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Should we include a note saying CE is deprecated and that it is C/RE/X? C also becomes RX.

Next Meeting

 * <span style="font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Date: **<span style="font-family: 'Arial','sans-serif'; font-size: 13.3333px;">08/11/2011
 * <span style="font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Time: **<span style="font-family: 'Arial','sans-serif'; font-size: 13.3333px;">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 style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">[|Data Types Value Set Table]
 * 2) <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">[|Parent/Child Micro Relationship]

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