LRI+IGs+Analysis+WG+Meeting+2011-07-12

include component="page" wikiName="siframework" page="LRI Header" =LRI IGs Analysis Meeting Minutes= **Dial-in:** 1-408-600-3600 **| Passcode:** 660 071 157
 * Date: ** 07/12/2011
 * Time: ** 3:00PM – 4:00PM EDT

Attendance
Tom Boal, Hans Buitendijk, David Burgess, Freida Hall, Kate Hamilton, Lester Keepper, Natalie Menser, Riki Merrick, Brian Pech, John Roberts, Scott Robertson, Jennifer Sisto, Rob Snelick, Jonathan Tadese, Merideth Vida, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 07/12/11 || NOTE in RED: Field Analysis- Ordering Provider: Want to validate that a profile that would change the CE in the data type to a C is a valid constraint. – For group members to ponder. || All Members || In Progress ||  ||
 * 2 || 07/12/11 || Review [|Implementation Guides Analysis Matrix Working Document] || All Members || In Progress ||  ||

Agenda Items

 * 1) Continue discussion of the  [|Implementation Guides Analysis Matrix Working Document] (Data Type Component Variance Analysis) with “Filer Order Number” (in yellow).
 * 2) Discuss Bob Yencha's starting point implementation guide.

Meeting Notes

 * **Implementation Guide update: **We are developing the data type tables and migrating information over to the draft guide.
 * Will follow the format of an existing guide, using an existing HL7 document.
 * Suggestion from the group to include a separate column: additional conformance requirements.
 * Something to consider, do we want to adopt a numbered conformance statement approach? Every conformance statement would have a unique ID.
 * **<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Implementation Guide Analysis Matrix Working Document: Data Types and Field Analysis **
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Ex. XCN GU, XCN NG
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Duplicate tables or make use of a conformance statement to illustrate the duplicated information?
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Every time we have different usage codes, we need to use different tables.
 * <span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">NOTE in RED: Field Analysis- Ordering Provider: Want to validate that a profile that would change the CE in the data type to a C is a valid constraint. – For group members to ponder.

Next Meeting

 * <span style="font-family: 'Arial','sans-serif'; font-size: 13px;">Date: **<span style="font-family: 'Arial','sans-serif'; font-size: 13px;">07/14/2011
 * <span style="font-family: 'Arial','sans-serif'; font-size: 13px;">Time: **<span style="font-family: 'Arial','sans-serif'; font-size: 13px;">3:00 PM-4:00 PM EDT
 * Dial in:**<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;"> 1-408-600-3600

Reference Materials

 * 1) [|Implementation Guides Analysis Matrix Working Document]

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