2012-01-17 AWG Minutes

2012-01-17 AWG Minutes

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



DATE & TIME: Every Tuesday 4:00 pm ET

NEW GoToMeeting: https://www3.gotomeeting.com/join/444698214  (accommodates 100)

PHONE:  +1 (510) 443-0602      Access code: 444-698-214 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

Web Browser HTML SYSTEM ARCHITECTURE at: http://architecture.osehra.org


    http://code.osehra.org/dox/  for 2011-9-6 release  

    http://code.osehra.org/dox_beta/ for 2012-12-6 FOIA release

E-MAIL DISTRIBUTION LIST: architecture@groups.osehra.org – you must be registered to post/receive. Please register with Architecture Group

  • 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 to the AWG “discussion forum” or “Wiki”.



  • 17 Sep 2011           Initial 2011 System Architecture baseline
  • 06 Dec 2011           validated  2011 System Architecture baseline
  • 17 Mar 2012 “strawman” Product Definition and Roadmap
  • 17 Jun 2012  “ironman” Production Definition and Roadmap.
  • 01 Oct 2012  Product definition & certification for all 126 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 ) under AWG minutes
  • Refactoring WG status update
  • Product Definition WG status update
  • Architectural Certification &  Visual Cross Reference Tool status.
    • A separate OSEHRA work group will be created to harmonize various open source VistA versions, e.g., OpenVistA, WorldVistA, VxVistA, and RPMS.  They will likely start with the inner core of the “onion model” as the initiate set of modules to harmonize.  This is a separate process from the 10-1 initiative; how this effort will intersect with the 10-1 product definition is not clear.
    • Questions were raised regarding the steps after obtaining the architectural certification report from the “diff” process at the individual VAMC.   What if there are thousands of differences? How do we process these massive amount of information?
  • Identify issues for 7-9 Feb lockdown


STRATEGIC VISION: Moving VistA to an open source environment will increase innovation and software quality.


STRATEGIC OBJECTIVE: Having Vista modules at OSEHRA by 1 October 2012, so that VA hospitals can download software modules from the open source environment.


REQUESTED ACTION: Identify issues for 7-9 Feb lockdown

  • Patch Release process
  • ICR process
  • Class 3 software inclusion process(es)




Issues discussed related to Product Definition:

  • What are the selection criteria for the OSEHRA “Core” modules.
  • What is the process for introducing Class III software into the OSEHRA repository where the Class III software requires modifications to the “Core” Class I modules.
  • Keith Cox of VA mentioned that VA management has put on hold the internal VA process for converting Class III software to Class I because the new process will now involve OSEHRA. 
  • There are many questions related to the 10-1 initiative in regards to the Class III software.  We know that there are differences between the local VistA instance vs. the “Gold” Class I version because the Class I module had to be modified to interoperate with the Class III software.   Since the Class III software are integral part of the clinical operation, i.e., patient safety, does it make sense to update local instance to OSEHRA “Gold” and then re-patch them for Class III software operation? 



About the 24th VistA Community Meeting

The goal of VistA Community Meetings is for those involved in the VistA Community to network & collaborate, i.e., to share ideas and work, with the objective of moving VistA & the VistA community forward.

Compared to most meetings, VistA Community Meetings are relatively unstructured. The agenda is always a draft agenda, because attendees are free to change it – even during the meeting – in order to better meet their objectives. VistA Community Meetings were originally almost exclusively technical meetings. Over time, the balance shifted, so that although there are technical presentations, there are more discussions on other aspects, including implementation, support, demonstration, education, training, and community collaboration.

Info at http://worldvista.org/Conferences/24th_VistA_Community_Meeting





VA Issues Request for Information on Scheduling Module


VA seeks new patient scheduling system

RFI is at  https://www.fbo.gov/?s=opportunity&mode=form&id=0ff8b0e488cacc30749b2b1e6d50a349&tab=core&_cview=0

By Bob Brewin 01/03/2012

The Veterans Affairs Department has kicked off the contracting process to develop its new patient scheduling system, a follow-up to a nine year, $167 million project that collapsed in March 2009 and led VA Secretary Eric Shinseki to call for a review of all the department's information technology projects by February 2012.

VA frankly acknowledged the problems with the original project in a request for information for the new medical scheduling system project released in December 2011.

The department said the original project was marred by lack of planning, competition and detailed requirements, and was plagued by poor internal oversight.

The new scheduling system will be built on the department's Veterans Health Information Systems and Technology Architecture. It will be open source software, according to VA, and will be delivered in increments.

VA has eyed Web and mobile technologies for the new scheduling system. "There is significant growth in the younger veteran population that is comfortable using Web-enabled technology and expects to be able to do business online. Other veterans prefer traditional methods of engaging with VA," the RFI noted.

"Veteran-enabled scheduling would allow veterans to determine desired interactions with VHA and support VHA's response to those preferences," the RFI said. "Veterans should be able to engage with VHA through the Internet, phone, automated phone systems and mobile devices when scheduling appointments, verifying appointments, and receiving reminders and updates."

Interested vendors should reply to the RFI by Jan. 31.