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

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

LRI IG Analysis WG Meeting Minutes

 * Date:** 09/08/2011
 * Time:** 3:00PM-4:00PM EDT
 * Dial in: ** 1-408-600-3600 **| Passcode:** 660 071 157


 * Meeting Agenda:**

Announcements

 * Fill out LRI IGs Analysis Face to Face Survey  with your attendance by 9/13 (Kathryn Calderone)
 * The next version of the IG for review and comments will be posted to the wiki on Saturday - please be on the lookout and make comments as necessary (Kathryn Calderone). Please note that we have a very short window for review and comment due to the 9/15 submission deadline to HL7, details will be posted with the draft document.

Discussion Items

 * Decision on Section 6 table format (Bob Yencha)
 * Determine next week's meeting schedule/logistics given the HL7 conference in CA (Hans Buitendijk)
 * 1:00-1:45 PM PDT (4:00-4:45 PM EDT) daily, directly following lunch break
 * 7:00-8:00 AM PDT (10:00-11:00 AM EDT) daily, before sessions begin
 * Discuss [|LRI-ELR_Dataelements_Vocab.xlsx] (Hans Buitendijk/Riki Merrick)
 * Continue discussion on [|HL7251ImplementationGuidesAnalysisMatrixWorkingDocumentLRI-IG-Analysis20110906hjb.xls] (Hans Buitendijk)

Attendance
Jitin Asnaani, Hans Buitendijk, Kathryn Calderone, Ernest Grove, Freida Hall, Kate Hamilton, Austin Kreisler, Natalie Menser, Riki Merrick, Glen Moy, Zeshan Rajput, John Roberts, Jennifer Sisto, Rob Snelick, David Susanto, Ashley Swain, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 09/10/2011 || Review IG v0.4.2 and post comments to the wiki by COB 9/13 || All || Open ||  ||
 * 2 || 09/06/2011 || Update F2F survey with your F2F attendance for IG by 9/13 || All || Open ||  ||

Meeting Notes
>>
 * **IG Matrix Working Document **- working through the comparison to the base standard
 * Since we already voted not to support truncation in any field in the guide, what value do we put in the guide for conformance length? Leave it blank? Does it hold that nothing can be truncated? Not in all cases – will state in the fields for now, just in case - //need to clean up language in the guide//
 * OBR.7 cannot have a conformance length, other than the = for no truncation allowed
 * Discussion of Specimen Segment
 * MSA Message Acknowledgement Segment
 * ERR Error Segment
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Red highlighted sections - **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Once we go through the data types, are there fields in which we need to look at adjusting the length? The red highlights denote an area to which attention should be paid to data type length
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Yellow highlighted sections **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">are ones that are general for addressing
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Discussion of Data Types **
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Need to look at lengths, and determine if there is any reason to constrain further
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Encapsulated Data - a note was made that this can be very big due to large documents, images, etc.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">ID, IS, NM - “Base Standard is Askew”
 * For FT data type, allow based on underlying standard
 * SPM.1 = same as standard
 * SPM.4 : ELINCS has 250 restriction
 * SPM.17 = same as OBR.7; DR second component mirror the first here
 * MSA segment:
 * MSA.1 = R in base standard – length = 2
 * MSA.2 = R in base standard – length 1..199= - should match what is in MSH.10 – check the base standard to see, if CLen is 199= ; should ask the base standard why it is different in the base standard
 * MSA.3 = row missing;
 * MSA.4 = O, 0..1 – datatype is NM and no length given, but in standard is 1-18 – needs to line up with MSH. – no sequence number in our MSH
 * MSA.7 and 8 – delete rows, they don’t exist in v2.5.1
 * ERR segment:
 * ERR.2: HITSP – once you hit one error, will you report out, so we meant to report after the first error found. O, 0..1 ok
 * ERR.3: is R, 1..1 in base standard
 * ERR.4: is R, 1..1 in base standard – length for ID
 * ERR.5: O, 0..1
 * ERR.6: O, 0..10, which is max repeatability in base standard – length in base is 80+ - need to find out what that means
 * ERR.7: RE, 0..1
 * ERR.8: O, 0..1 in base standard - TX datatype use base standard length
 * ERR.9: O, 0..* in base standard
 * ERR.10: O, 0..1 in base standard
 * ERR.11: O, 0..* in base standard
 * ERR.12: O, 0..* in base standard
 * Field length on datatype level:
 * CE: not defined in Base v2.7, so copied first 6 fields from CWE in v2.7
 * HD in the CX datatype has a length defined in the base standard column – should have none; was copy paste error
 * ED.5 – what about restricting length, because this is where all the data will be – this datatype requires partner agreement prior to usage – only used in OBX.5 – added text to OBX.2 to clarify that
 * EI-GU EI.4 should be 3..3 as we chose literal ‘ISO’
 * HD-GU HD.3 should be 3..3 as we chose literal ‘ISO’
 * ID C Length has 15= - does this make sense everywhere – should notify the standard folks about this
 * Same for IS – discuss procedure for this next week at HL7 WGM
 * NM – Numeric was previously marked red - why restricted to 16 in the standard? - also ask standard about this
 * PRL.2 need to match length for OBX.4 – it does
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">The WG got through almost all the data types - Bob Yencha will follow base definitions unless otherwise specified
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">The WG needs to review lengths to confirm accuracy. Everything that is highlighted in yellow - follow the basic data type definition. Everything that is highlighted in red - if someone has a very good use case that indicates the length should be different than the base standard, then there is need for discussion. Red focuses on lab content; yellow focuses on general messaging structure.
 * //<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">Start at SI - Sequence ID next time //


 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Decision on Section 6 table format**
 * Bob Yencha will remove the Future Use column, as well as the GU and NG profile columns
 * He will move Component Name to be directly next to sequence number for easier readability


 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">IG v0.4.2 **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">will be uploaded to the wiki on Saturday - all S&I Initiative members should review and comment on it before COB 9/13/2011. Commemorators are encouraged to focus on technical details before spelling or formatting issues.
 * The IG is must be submitted to HL7 by noon Thursday 09/15/2011.


 * Due to the HL7 meetings next week, we will not be having our regularly scheduled Tuesday/Thursday calls from 3:00PM - 4:00PM EDT. Instead, we will meet 10:00AM-11:00AM EDT (7:00AM-8:00AM PDT). Please watch the wiki calendar for WebEx and dial in information.

Next Meeting

 * Date:** Wednesday 09/14**/**2011
 * Time:** 10:00AM-11:00AM EDT
 * Dial in:** <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13.3333px;">1-408-600-3600 | **Passcode:** See wiki calendar

Reference Materials

 * [|HL7251ImplementationGuidesAnalysisMatrixWorkingDocumentLRI-IG-Analysis20110908.xls]
 * LRI IGs Analysis Face to Face Survey

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