LRI+IG+Analysis+WG+Meeting+2011-7-05

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


 * Meeting Agenda:**
 * 1) Continue to work through the [|Data Type Component Variance Analysis] and verify any pending data types.
 * 2) Discuss OIDs and vote on IG proposed recommendation.
 * 3) Discuss base guide to use when creating the new IG.

Attendance
Jitin Asnaani, Hans Buitendijk, Tom Boal, David Burgess, Kathryn Calderone, Frieda Hall, Rob Hausam, Austin Kreisler, Ken McCaslin, Riki Merrick, Glen Moy, Cindy Johns, Hal Jiang, Erik Pupo, John Roberts, Scott Robertson, Rob Snelick, Jonathan Tadese, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Owner** || **Status** || **Date Closed** ||
 * 1 || Create a first draft on the OID assignment process (problems, how it should work, what could the IG contain, etc.) || Ken McCaslin || In Progress ||  ||
 * 2 || For policy issues, get as much detail sent to contractors as to what needs to be done on OIDs || Bob Yencha || In Progress ||  ||
 * 3 || Circulate spreadsheet containing fields that require OIDs; add to data type analysis file || Austin Kreisler || In Progress ||  ||
 * 4 || Add spreadsheet as a tab to the data segment variance analysis || Hal Jiang || In Progress ||  ||

Meeting Notes

 * Baseline IG Discussion**

1. Discuss which guide to use as a baseline for creating the new one:
 * Reference CDA Consolidation approach: Take templates to create a general US specific realm.
 * Have templates for section and entries grouped for each document template.
 * Identify which sections apply to each document template.


 * OIDS Discussion - Global Unique Identifiers**

1. Review of IG Proposed Recommendation:
 * Recommend that global identification is the target and that OIDS are the desired end state.
 * Have different profiles:
 * Globally identified profile for organizations that are ready; OIDs are required.
 * Non-Global profile for organizations who are not prepared to use OIDs; OIDs are optional. This implies that you would have to negotiate which mechanism to use for the profile.
 * Value: Allow two alternatives to accommodate current state and to prepare organizations for OIDs requirement.
 * Recommend pilot to drive implementation. This is both a Sender and Receiver Requirement.

2. IG Proposed Recommendation Vote: 11 Total - 9 Yes | 2 Abstain

3. Multiple Assigning Authorities
 * There are multiple ways that OIDs are assigned; For example, organizations can assign OIDs on behalf of other organizations.
 * Need to differentiate between the assigning authority and the business partner.
 * Consider including a section in the IG to provide guidance to organizations.


 * Implementation Guides Analysis Matrix Working Document**

1. IG Analysis:
 * Element Name: No changes
 * Field Separator: No changes
 * Sending Facility
 * If Profile GU - HD.1 RE (e.g., extension), HD.2 R (OID string), HD.3 R ("ISO"). If profile NG - HD.1 O, C, C
 * Defines the usage in the case of global and non-global profiles
 * If the first component for the HD data type is present, the second and third components are optional. If the third component is present, then the second must also be present. This second and third components must either both be valued (both non-null), or both be not valued (both null).
 * If all three components of the HD are valued, the entity identified by the first component is the same as the entity identified by components two and three taken together.
 * Implementers may choose, by site agreement, to specify that if all three components of the HD are valued, the first component defines a member in the set defined by the second and third components.
 * Receiving Facility: No changes
 * Timestamp: TimeZone Offset; HITSP and ELINCS both require time zone offset.
 * Message Type: No changes
 * Message Control ID: No changes
 * Processing ID: No changes
 * Version ID: No changes
 * Acknowledgment ID: No changes
 * Message Profile Identifier: do we want HL7 identifying OIDs for profiles in this guide?
 * If Profile GU, all profiles must use OIDs, including the profiles not defined in this IG. If Profile NG, only the HL7 issues profiles use OIDs, all others can be mixed.
 * Mark as red and revisit pending Ken McCaslin's input.
 * Set ID - NTE: No changes
 * Comment: No changes
 * Patient Identifier List:
 * If Profile U, CX.4 R, HD-GU
 * If Profile NG, CX.4 RE, HD - NG
 * Create this at the datatype level instead of at each field; revisit here on Thursday.

Next Meeting

 * Date:** 07/07/11
 * Time: **3:00 PM-4:00 PM EDT
 * Dial-in: ** 1-408-600-3600 **| Passcode:** 663 719 832

Reference Materials
[|Data Type Component Variance Analysis]

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