LRI+IG+Analysis+WG+Meeting+2011-07-07

include component="page" wikiName="siframework" page="LRI Header" =LRI IG Analysis WG Meeting Minutes=
 * Date:** 07/07/2011
 * Time:** 3:00PM-4:00PM EDT
 * Dial in:** 1-408-600-3600 | **Passcode**: 663 719 832
 * Meeting Agenda: **IG Analysis Meeting Agenda 07-07-2011

Attendance
Hans Buitendijk, David Burgess, Kathryn Calderone, Ernest Grove, Freida Hall, Kate Hamilton,Rob Hausam, Lester Keepper, Austin Kreisler, Ed Larsen, Diana Massey, Ken McCaslin, Natalie Menser, Merideth Merive, Riki Merrick, Glen Moy, Brian Pech, John Roberts, Scott Robertson, Jennifer Sisto, Rob Snelick, David, Susanto, Jonathan Tadese, Bob Yencha

Agenda Items

 * 1) Continue to work through the [|HL7251Implementation Guides Analysis Matrix Working Document] and verify any of the pending data types
 * 2) Discuss OIDs
 * 3) Discuss base guide to use when creating a new IG

Meeting Notes
Building the new IG
 * In creating a starting point for building the new IG, Bo b Yencha began with the Public Health guide because it has multiple profiles built in
 * Once this starting point is available, it will be posted on the Works in Progress area of the IG Analysis wiki. Bob will also include some background information on OIDs

HL7 Updates
 * Version 2.7.1 accepted; now on final stop at Technical Steering Committee (TSC); then we can start to announce the process of the HL7 Ballot
 * TSC meets on Monday, so by Tuesday we should know the verdict

Data Type Component Variance Analysis
 * Message Profile Identifier: We started using profile GU ("Global Unique" - all profiles must use OIDs) and NG ("Not Global" - any type of identification that is unique between systems)
 * If the profile is GU, then all profiles listed in the GU must use OIDS, even if not in this IG
 * If the profile is NG, could be OIDs or not, could be uniquely define within a system or not
 * If NG, the HL7 could or does use OIDs (the group still needs to decide this); all local profiles can use locally agreed to identification.
 * Could lengthiness of OID influence system ability to accept identifier?
 * We may need a third profile: e.g. NO (No OIDs whatsoever. More of an issue regarding the length of the OID which means that the receiver can’t handle an OID). We will postpone this part of the conversation until the use case is further defined- we can also keep this off the table until someone has this situation and can speak to it.
 * We may end up having an OID for a profile, and then a less specific identifier.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Vote on being comfortable with three categories - Yes
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">The sender selects the profile being sent.

<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Continue next week’s discussion with Filler Order Number (in yellow)

Next Meeting

 * Date:** 07/12/2011
 * Time:** 3:00PM-4:00PM EDT
 * Dial in:** 1-408-600-3600

Reference Materials

 * 1) [|HL7 2.5.1 Implementation Guides Analysis MatrixWorking Document 20110707]

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