ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-06-30

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

ToC Architecture Implementation RQ WG Meeting Minutes

 * Date:** 06-30-2011
 * Time:** 2:00-3:00pm
 * Dial-in:** 1-408-600-3600 | **Passcode**: 662 868 333
 * Meeting Agenda: Click here for the agenda!**

Attendance
Mark Bamberg, Amy Brantley, Tom Caruso, Laura Heermann, Allen Hobbs, Lester Keepper, Lester Keepper, Ron Kolwitz, Al Laronne, Cynthia Levy, Ken Lord, Mayuri Patel, Steve Rushing, Andriy Selivonenko, David Tao, Liz Westbrook, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 06-30-2011 || Provide feedback on RI Arch Scope through consensus page || All || Open ||  ||
 * 2 || 06-30-2011 || Make edits to RI Arch Scope and Mayuri Patel to review || Cindy Levy and Mayuri Patel || Open ||  ||
 * 3 || 06-30-2011 || Bring RI Arch Scope to consensus and discuss comments || All || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Consensus on RI Architecture Scope (Mayuri and Cindy)
 * 3) Review the RI Architecture Overview and Workflow (Mayuri and Cindy)
 * 4) Discuss Next Steps (Meredith Lewis)

Meeting Notes

 * Consensus on RI Architecture Scope**
 * Voting closed 6/30
 * If you did not vote that is by default a yes vote
 * Methodology based on model-driven architecture
 * Specifics on what is being referenced under CIM WG works in progress
 * Hyperlinks will be provided
 * The way divided: there are data elements that are always required no matter what transaction
 * From clinical perspective they thought vital that physicians be given necessary latitude, this is where B (optional)elements
 * Current clinical info model does include things not currently in standards (this gets into C and D elements)


 * Architecture Drivers and Principles**
 * TOC expanding to include lab test results and assuring data elements are the same where possible across domains
 * Use of software patterns
 * Can’t be specific to data elements


 * Architecture Assumptions**
 * We are using abstract model
 * Infrastructure is outside of arch scope
 * Transition of care input may require ability to input multiple docs into EHR
 * Possibly need to create multiple outputs
 * Computable models
 * Should we redefine data elements/def layer to add 2 boxed for future data elements


 * Data Structure Layer**
 * Definitions should be future-looking


 * Data Element Services Layer**
 * Validate or constrain by vocabulary
 * As we move into stage 2 this will be further addressed
 * Delete stretch goal language

Next Meeting

 * Date:** 07-07-2011
 * Time:** 2:00-3:00pm
 * Dial-in:** 1-408-600-3600 | **Passcode**: 662 868 333

Reference Materials

 * 1) ToC RI Architecture Scope

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