2011-12-20 AWG Minutes

2011-12-20 AWG Minutes

20 December 2011 OSEHRA AWG AGENDA-Minutes


Weekly Open-Source EHR - Architecture Work Group (AWG) Telecom

DATE & TIME: Every Tuesday 4:00 pm ET WebEx: https://tiag.webex.com/

PHONE:  +1-408-600-3600      Access code: 629 453 409 or use VOIP

DOCUMENTS at: http://www.osehra.org/node/47/content/documents

DISCUSSION at: http://www.osehra.org/node/47/content/discussions

WIKI at: http://www.osehra.org/node/47/content/wikis

HTML SYSTEM ARCHITECTURE at: http://architecture.osehra.org … can be viewed with a web browser.




  • Joining OSEHRA is free; please join at www.OSEHRA.org .
  • To receive AWG e-mail, join the OSEHRA AWG at: http://www.osehra.org/groups
  • Add your comments and suggestions-for-improvement to the AWG discussion forum or Wiki.



  • 17 Sep 2011           Initial 2011 System Architecture baseline
  • 06 Dec 2011                  
    • validated  2011 System Architecture baseline
    • Product Baseline and Roadmap approach
    • Initial iEHR Software Development Kit (SDK)
    • DRAFT iEHR Services Platform (ESP) Conceptual Architecture
    • DRAFT iEHR Services Platform (ESP) Implementation Guide
  • 17 Mar 2012 “strawman” Product Definition and Roadmap
  • 17 Jun 2011  “ironman” Production Definition and Roadmap.
  • 01 Oct 2012  Product definition & certification for all 128 hospitals



               (Related slides & spread sheets are posted at the “Documents” link given above)

  1. Start: Introductions and Roll Call
  2. Minutes: Approve last week’s minutes and review/update this week’s agenda
  3. Action Items: review open action items
  4. Discussion: (slides at: http://www.osehra.org/node/47/content/documents
    •  “Open Source EHR Re-factoring Services” slides by Afsin Ustundag, Ray Group International, austundag@raygroupintl.com
    • Release Architecture Discussion” slides provided by Dr. Paul Tibbits



Roger Baker, VA CIO on Refactoring

We have heard conflicting statements from Roger Baker on refactoring and reuse of legacy VistA code.

  • Our goals are to bring in as many private sector modules as possible and selecting the same thing to run between VA and DOD so that we end up with a single, common electronic health record system,” Roger Baker, VA CIO said in March.
  • "The key phrase is single common electronic health system. It's two large systems, and... the intention is to get to a point where there is a single repository for all the data related to an individual' s medical record whether generated in DoD or VA, and I might add through the nationwide health information network." Roger Baker, VA CIO said in July.
  • OSEHRA now is involved in the analysis of the refactoring or restructuring of VistA into something that is more easily modified by private sector organizations. That analysis will be posted in the open source community for comment before we move forward based on it.” Roger Baker, VA CIO said in November.


As a result, we are conflicted on where to invest our energies. 1) refactoring of legacy or integration of new iEHR modules. In either case we need to integrate with the Enterprise Service Bus and iEHR data store.

See the Architecture Work Group slides with the 13 & 20 December 2011 AWG minutes (under "Documents") for presentations on refactoring by Talent and Ray Group.

VistA contains approximately 168 packages, 26,000+ routines, 12 million lines of code. As we transition to a 3-tiered interoperable EHR Services Platform architecture, the data store, GUI and EHR Services Platform will be prescribed. Plug-and-play applications can be purchased, built or refactored; what should be the goals, objectives and scope of refactoring?

Your thoughts?