LRI+IG+Analysis+WG+Meeting+2012-02-16

include component="page" wikiName="siframework" page="LRI Header"

LRI IG Analysis Meeting Minutes
**WebEx:** **@http://www.mymeetings.com/siemens/nc/join.php?i=741301183&p=&t=c ** **Dial-In:** **1-888-998-2663** **Access Code:** **2410512** **WebEx Passcode:** **HL7OO**
 * __Thursday 2/16 2:00PM ET-4:00PM ET __ **

**Meeting Agenda:**
[|LRI DateTime Patterns 2012-02-14.doc] || 15 Minutes || Hans Buitendijk ||
 * = **ID** ||= **Key Discussion Items** ||= **Duration** ||= **Presenter** ||
 * 1 || Approach to Addressing Pilot Comments for Review || 5 Minutes || Shalina Wadhwani ||
 * 2 || Date/Time Discussion Beginning With OBR.22
 * = 3 ||= Ballot Reconciliation via the Project Management Wiki Page ||= 100 Minutes ||= Hans Buitendijk ||

Hans Buitendijk, David Burgess Ernest Grove, Freida Hall, Les Keepper, Austin Kreisler, Ken McCaslin, Riki Merrick, Brian Pech, Rob Snelick, Shalina Wadhwani
 *  Meeting Attendance: **

Action Items

 * **#** || **Action** || **Owner** || **Status** || **Due Date** ||
 * 1 || Date/Time Pattern Analysis - Documentation of REs || All Members || Open ||  ||
 * 2 || Review of Yellow Highlights on Date/Time Pattern Analysis || All Members || Open ||  ||
 * 3 || Create Order Parent/Observation Parent Matrix (Rob Snelick Follow-Up) || Hans Buitendijk || Open ||  ||

Meeting Notes

 * Pilot Comments – Shalina Wadhwani **
 * March 1 from 4:00 – 5:00 is the preferred timeslot for the group


 * Use Case Comments – Shalina Wadhwani **
 * Use Case group decided on Simplification call to discuss the LRI Assumption Document on March 1 from 2:00 – 3:00


 * Feedback from Hans Buitendijk **
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">No. 313
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">Reaplce the MSH.21 Comment with “This field shall include either a valid combination of three profile components as defined in Section 1.5.6.1, or one of the four profiles defined in Section 1.5.6.2. Trading partners may define additional profiles or profile components and include them in this field in accordance with Section 1.5.6.3. The sender asserts that the message conforms to all of the profiles identified.”
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">Create another conformance statement to match
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">Rob Snelick moves, Les Keepper seconds; 0 against, 0 abstain, 9 for
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">No. 320
 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">See Comment 313


 * <span style="background-color: white; font-family: Arial,sans-serif; font-size: 10pt;">Date/Time Pattern Analysis **
 * Revisit PID.7
 * “Base Profile”
 * TS-0
 * YYYY R
 * MM RE
 * DD RE
 * HH O RE
 * MM O RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] O
 * “New Born Screening Profile”
 * TS-0
 * YYYY R
 * MM RE
 * DD RE
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] O
 * If we find a use case part of the new born screening profile, we create it separately
 * Followup on Table 3-6: Patient Identification Segment – someone checks into what the list looks like so we can validate them
 * Everyone will use v20. Wherever there is documentation of an RE, we will determine which needs to be dealt with through a different profile. What can we come up with to get flexibility in play. Which REs are out of scope – they will flip to O’s
 * Create one list to determine which should be accommodated - will be reviewed on 2/28


 * Intro 1.5.8
 * Receivers shall support TimeZone Offset Profile and Senders should support Timezone Offset Profile
 * Need to include in MSH.7 that if the timezone offset is included, and subsequent timestamps do include the timezone, those timestamps are assumed to have the same timezone offset as MSH.7
 * MSH.7
 * “Base Profile”
 * TS-1
 * YYYY R
 * MM R
 * DD R
 * HH R
 * MM R
 * [SS[.S[S[S[S]]] R
 * {+/-ZZZZ] C(R/O) if Timezone Offset Profile
 * Come back to OBR.7
 * TQI.7
 * TS-3
 * YYYY RE
 * MM RE
 * DD RE
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] C(RE/O) if Timezone Offset Profile
 * TQI.8
 * TS-O
 * YYYY RE
 * MM RE
 * DD RE
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] C(RE/O) if Timezone Offset Profile
 * OBX.2/OBX.5
 * Include with the CWE-CR use note for in OBX.2/5 that TS-0 should be used for the timestamp. Table 4-4 for the appropriate data types
 * OBX.14
 * YYYY R
 * MM R
 * DD R
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] C(RE/O) if Timezone Offset Profile
 * OBR.19
 * TS-3
 * YYYY R
 * MM R
 * DD R
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] C(RE/O) if Timezone Offset Profile
 * SPM.17
 * Change length to 4.24
 * Relax the assertion that OBR.7, SPM.17, and OBX.14 shall/must be the same
 * TS-3
 * YYYY R
 * MM R
 * DD R
 * HH RE
 * MM RE
 * [SS[.S[S[S[S]]] O
 * {+/-ZZZZ] C(RE/O) if Timezone Offset Profile


 * Next Week **
 * Will decide whether to make a motion on Tuesday
 * WG participants will think about the yellow highlighted area
 * Riki had a conversation with Virginia Sturmfels on Colony Counts
 * Ken McCaslin agreed with the work they produced and have agreed not to have a SNOMED colony count discussion
 * Tuesday – pick up with Date/Time and go into Comment # References/Misc
 * Should not take the entire 2 hour session
 * Hans will create a matrix for next week – order parent, observation parent, OBX point to another parent

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