X12N+274+Workstream+Meeting+9-9-2011

**Time:** 10:00AM – 11:00AM EDT **Dial-in:**1-408-600-3600 | **Passcode:** 661 919 002
 * Electronic Service Information Discovery – X12N 274 Workstream Call**
 * Date: ** 09/09/2011

Ken Pool, Gail Kocher, Richard Eshbach, Tynisha Carter, Margaret Weiker, Zeshan Rajput, Chris Andreou, Naveen Amiruddin, Kelly Conlin, Ernest Grove
 * Attendance:**


 * Action Items:**
 * External:
 * For the next call, Gail Kocher will make an attempt to populate the X12 data mapping spreadsheet.


 * Meeting Minutes:**
 * Introduction
 * Goal of call is to Review x12 directory and see how it matches to Section 12 of Use Case.
 * Discussion regarding alignment of the X12 mapping to the other workstreams’ mapping:
 * Perhaps aligning all workgroups should be a secondary step after the initial X12 mapping is complete.
 * Review of Column Headers
 * Decision: “Loop ID” column added.
 * Decision: Change “Match” to “Support.”
 * Decision: Change “Segment” to “Segment ID.”
 * Decision: Change “Data Element” to “Data Element ID.”
 * Multiplicity
 * X12 elements can repeat more than once but the repeat is based off of either the loop or the segment; discussion regarding exactly how the ‘multiplicity’ column should be most logically populated.
 * Decision: Multiplicity is not applicable to X12. Change to “Repeat.”
 * Proposed Changes/Extensions
 * The purpose of this workgroup should be to identify whether or not there is a gap; the standards body should be proposing how to fixthe gap.
 * Much of the information in the ‘notes and extensions’ columns are suggestions from the workgroup as how to bridge the gaps.
 * We should be careful in prescribing fixes in the X12 realm as there are not many participants on the call who understand the syntax.
 * All participants in agreement that the spreadsheet is adequate for beginning to map the data elements to the standard.
 * Data Elements
 * Cannot define Loop ID, Segment ID, or Data Element ID values until data element is clearly defined
 * Unique Reference for Individual
 * Using the NPI as the individual ID is an acceptable way to identify an individual however some organizations may not be identifiable via the NPI.
 * NPI for an individual will be unique; organizations could hold multiple NPI or none.
 * If NPI is used, consider using Organization to Organization mechanism to handle organizations with multiple NPI.
 * Transactions under HIPPA allowances may have bearing on decisions in this capacity.
 * Action Item: Gail Kocher will make an attempt to populate this spreadsheet offline.