VistA Evolution Program, VistA Immunization Enhancements (VIMM) Technical Resource Meeting Minutes MEETING DETAILS

DATE: Tuesday, October 28, 2014

MS LYNC: 855-767-1051 & Online Meeting

MODERATOR: Keith Magoon

TIME: 11:00 – 11:30 AM EDT

ACCESS CODE(S):

6627 7038

FACILITATOR: Dennis Kemp

SCRIBE: Jacquie Marian

INVITEES:

ATTENDEES & ROLES

ATTENDED NAME ROLE

X Alan Monosky VA M Developer

Alan Montgomery Product Support – Clinical Reminders

X Asha Amritraj STS Java Dev/Architect

X Barbara Baskett STS SQA

X Brian Frederickson VA Planner

Brian (Bo) Newman

X Carolyn Kron PM Support Senior Test Engineer

Chris Pryor

Christine Donovan STS Program Manager

Chuck Link VA M Developer

Connie Ray VA M Developer

Page 1 of 9

X Dan Cramer STS Terminologist Analyst/NTRT

X Dennis Kemp PM Support Project Manager

George Lilly VistA Expertise Network & CIO, WorldVistA

Gianni LaRosa PM Support Senior Trainer

X Jacquelyn Marian PM Support Requirements Analyst

X James Proctor PM Support Release Manager

Janelle Moore PMO Support Acquisition

Jeff Udell STS Project Manager

X Jeffrey Nienhaus VA SQA

Joan Cohen Program Specialist, OHI

X Joseph Bircher PMO Support Planner

X Jyothi Siddabathula PM Support Test Engineer

X Kathryn McGuyer VA Technical Analyst

X Kathy Steele PM Support Technical Writer

Katie Carr PMO Support Acquisition

X Keith Avery PM Support Senior Developer

X Keith Magoon VA VIMM Project Manager

Lenna Scott VA Implementation Manager

X Lisa Goddard

Mike Henderson OSEHRA Director Open Source Product Management

X Mike Montali VA Competency Manager

Nancy Anthracite President, CMO & Director, WorldVistA

Peter Li OSEHRA CISSP Director, Engineering

Page 2 of 9

X Radhika Yakkali PM Support Test Engineer

X Randy Stewart STS Terminologist

Raymond Steele VA Technical Writer

X Richard Ohlmann PM Support Test Engineer

Roger Gorkhalee PMO Support Risk Manager

X Sandeep Karuturi STS Requirements Analyst

X Seema Chaudhry VA Functional Analyst

Shauneen Miranda PMO Support Ancillary Product Line PM

X Shelita Davis PM Support Technical Writer

Thomas May Enterprise Architecture (EA)

X Vikas Sharma STS Java Dev

X – Present. O – Excused absence. Blank – no report.

MEETING TOPICS PRESENTER: Keith Magoon

TOPIC: Project Status

DISCUSSION: Primavera, and PMAS Dashboard updates (Brian Frederickson)

Brian stated 7Delta provided the IMS meeting on Monday and will be coordinating between VIMM, 7Delta, SBG, and Jeff Udell. No PMAS Dashboard updates to be made at this time. There are a couple of outstanding timesheets and Brian asked that those be submitted as soon as possible.

Primavera tasks that had a due date of 10/24:

Keith sent the below tasks in an email out to the group with the appropriate tasks that are listed under the VIMM project for documenting non-project time. It was requested everyone add those to their list of Primavera tasks by last Friday for their weekly submission.

o Medical 21st Century Development Core Generic Leave: 01-02-01-98-11-00015.1.1.2 Medical 21st Century Development Core Non-Work Time FY15

Page 3 of 9

o Medical 21st Century Development Core Holiday: 01-02-01-98-11-00015.1.1.2 Medical 21st Century Development Core Non-Work Time FY15

o Medical 21st Century Development Core Non-Project Travel: 01-02-01-98-11-00015.1.1.3 Medical 21st Century Development Core Non-Project Time FY15

o Medical 21st Century Development Core Non-Project Related Meetings: 01-02-01-98-11-00015.1.1.3 Medical 21st Century Development Core Non-Project Time FY15

o Medical 21st Century Development Core Non-Project Related Training: 01-02-01-98-11-00015.1.1.3 Medical 21st Century Development Core Non-Project Time FY15

o Medical 21st Century Development CoreVA Ops and Configuration Time Non-Project Related: 01-02-01-98-11-00015.1.1.3 Medical 21st Century Development Core Non-Project Time FY15

Status of PX*1*201 IOC (Keith)

PRESENTER: Keith Magoon

TOPIC: Technical Tasks

DISCUSSION:

Update on the status of PX201 defects and IOC site comments (Chuck Link, Jeff Nienhaus)

Keith stated the IOC period is completed and the IOC Exit documentation and the National Release request were submitted. The weekly Wednesday meetings with the IOC sites were cancelled since the IOC period completed with no defects reported from T14.

Keith stated there is a request from our Release Manager to make the appropriate comment in FORUM in regards to PX*1.0*201 and will be forwarding that message to Jeff Nienhaus. Keith stated it requests a hold of the patch in FORUM while Release Management does their review of the documentation on the patch and requested Jeff to reply all to when the task is completed.

Jeff requested a meeting to discuss SQA and testing of VIMM 2.0 increment 1. Dennis Kemp has established that meeting; if anyone would like to attend, please send Dennis an email. This is an introductory or beginning call to make sure everybody is aligned with the tasks and requirements of our next patch (number will be requested when we are closer to deployment); talk about testing and SQA activities.

Page 4 of 9

Status of Requirements elaboration on VIMM 2.0 RTM to change requirements from Business to Software Developer verbiage (Seema, Dennis)

Keith stated there was a meeting yesterday afternoon; he felt it was very productive. Seema stated she will be updating the requirements and passing out the latest updated RTM.

ICE / CAT 508 Conformance analysis status (Raymond Steele)

Raymond stated they have had contact from Zach Rich, who is a lead analyst with the VA Section 508 team; he has about 7 people that are studying and learning about testing applications and starting to utilize some of the new software that they have in their office for testing for this. Raymond has made contacts within the VA team as well as the outside team on the open source side. Rather than just download what they have on the website, Raymond was advised that there are some items they would want to load and things that they would not want to load so he is in the process of trying to coordinate that today.

Keith asked if Raymond has seen the communications today about the ProPath documentation 508 conformance. Raymond stated he has received several emails about the same subject asking that the ProPath templates be compliant. This is good because our contractors go out there and expect the templates to have the content desired to be developed and in a format that is wanted. When that isn’t the style that meets the OI&T technical writing standards and when the template is filled with unnecessary tables and problems for Section 508 it is not good. Raymond stated he has been in touch with and working with Jim, who is training right now on the CommonLook Office Suite, and expect to have a new series of templates available in the next few weeks.

Keith mentioned the presentation Raymond provided and suggested Raymond would want to include the ProPath 508 non-conformance. Keith stated it shows our commitment to 508 when we want to make sure all templates available to projects is conformant. ProPath is not just for OI&T, it has been designated for every project in the VA regardless of the organizational pillar it is under. Keith stated the work Raymond has done to get us to this point is worth noticing. It would be nice to let everyone else know that we have found a critical deficiency and pointing out that it needs to be rectified; Raymond stated he will add it to the presentation next week.

Status of the interim process for updating standardized files (Keith)

Keith is waiting for a response from Deborah Migliore so her comments or any advice provided can be added to our draft process that is currently at Product Support Release Management for review.

Review of VIMM Standardization requirements by STS Team and requirements to be added to VIMM 2.0. (Jeff Udell)

Page 5 of 9

Asha stated they are making progress on modeling the fields/files.

Keith stated there is a scheduled call titled VIMM Interface Meeting with STS on November 3rd at 9am EST. Based upon the 2 calls that were held already and facilitated by ASD, there are major risks and issues coming out of this meeting. Meeting we had yesterday with API 2.0 and eHMP, which is not scheduled to start until increment 3, resulted in identifying some major issues and risks. The meeting with STS is scheduled for Nov 3rd and hopefully we won’t have major issues and risks; it is encouraged that if you have an input to the interface between VIMM and STS, if there are questions lingering, questions about who has responsibility or who has sustainment, or what the future is Keith recommends your attendance.

ESE CPE Capacity Evaluationo Concerns

Inadequate Performance Requirements Capacity Planning

o Recommendations Performance Requirements Capacity Plan Integration Plan

Keith stated this is what came out of the ORR review for VIMM 1.0; because VIMM 1.0 basically has dormant files that are not going to be accessed by anyone until VIMM 2.0, this was not a major concern for them. This will be a major concern going forward specifically Inadequate Performance Requirements and Capacity Planning. STS will have processes and automation going on in the background and whenever you do that you increase network traffic, you increase the load on hardware, you decrease system performance the more of a load you put on that system. T

These are concerns to Keith moving forward to our March IOC that we address performance requirements and capacity for our application the best that we can. We create Performance Requirements, Capacity Plan, and Integration Plan based upon those results we find.

Keith has requested services through SD&E and have 2 network engineers that are assigned to this project to look at what we are doing, look at the software that we have, our deployment plan or implementation plan, and determine the effects on the network, effects on capability, and effects on performance. Need all the team members to think about this and start getting inputs now. We need to generate our Master Test Plan now even though we are only 5 weeks into the project. We need to start collating data, we need to discuss the outcomes, and make sure that we test to these going forward because we have to submit a SEDR and the STS has to submit a SEDR and both our answers need to be the same.

Page 6 of 9

Keith asked Dennis who the Test Engineers that are assigned to VIMM 2.0. Dennis stated Carolyn, Radhika, and Jyothi are the test engineers assigned. Keith would like this added as an agenda item for meetings going forward and get status. Keith stated we need to determine performance requirements and capacity for VIMM and STS. Keith has no idea on capacity and performance requirements of STS, but VIMM and STS need to be synced together when we are determining what needs are going to be. We need to come up with a way to test against it, how to test, and where we are going to test. Carolyn stated she had some concern about capacity planning and performance requirements due to all the auditing; she will take that and start planning for it in the near future. Keith would like this to be an agenda item so if there are questions that you are not getting answered or information and input needed that it can be listed in the action items for tracking.

Mike stated once we have the auditing features in place, we will be able to say how much space it takes to store the record in the V IMMUNIZATION file along with the audit information. For the changes in between, he is not sure if you will be able to tell; maybe we will come up with an average of the storage space for a single record in the V IMMUNIZATION file and have someone tell us how many immunization records would exist each year to know the full storage amount for that data. Keith stated that is exactly what we need to discuss and we also need to discuss network traffic because we do not know how many instances of the STS servers there are, but with 130+ VistA instances and if we have to do an update, how long is it going to take; how much network traffic does that utilize, does it reduce the performance of the VistA when it is trying to do the update. If we are affecting anything with V IMMUNIZATION do we have to have the same performance specs as the Patient Safety application or do we follow the performance specifications for a regular patch. Carolyn mentioned that some of the performance would have to come from when actual users are accessing the VistA system during testing; Keith stated the network engineers from SD&E can help us with this.

We have to identify these items to make decisions on and what is applicable and what are our specifications for performance; we also have to figure out a way to test it. We can even ask Scope and Source to test on their VistA; there are multiple ways to go about it, but we want to make it the most efficient and most effective solution as a group on how we do this. It is going to get worse going forward with Meaningful Use coming up with our work with VLER DAS in increment 2, our work with API 2.0 in increment 3, and then especially CDS solution coming up in increment 4. There are things we have to think about and this is the proper time to start thinking about them.

PRESENTER: All

TOPIC: Open Forum

Page 7 of 9

DISCUSSION:

__________________________________________________________________________________________________________________________________________________________________________________________________________________

PRESENTER: Keith Magoon

TOPIC: Action Item Update

DISCUSSION:

See action items listed below

PRESENTER: All

TOPIC: Closing Comments

DISCUSSION: __________________________________________________________________________________________________________________________________________________________________________________________________________________

ACTION ITEMS

ASSIGNED TO ASSIGN DATE

DUE DATE

ACTION ITEM DISPOSITION / STATUS

Keith Magoon 10/14/14 Update or modify Brian Fredrickson’s resource request for VIMM 2.0

Email request sent to Management Analyst.Brian’s manager stated she will be correcting it.Closed

Keith Magoon 10/14/14 Secure a Kernel resource for increment 1 to meet the needs of the project and STS.

In Progress.Sent request to James Campbell on 10/16.

Page 8 of 9

STS has sent info for resource determination.Keith stated he will need to follow-up to get a status.

Shelita Davis 10/21/14 Schedule meeting with VIMM developers and STS team

Closed

Keith Magoon 10/21/14 Contact Deborah Migliore for additional information on interim update process

In Progress.Waiting for response.

Keith Magoon 10/21/14 Create distribution list on the listserv from CDC

Closed.

Keith Magoon 10/21/14 Email Seema the CDC distribution site

Closed.

Jacquie Marian 10/28/14 Add items to agenda: Test Scripts status and Discuss Performance Requirements and Capacity Planning

Closed

Page 9 of 9