Meeting Lead: James Proctor

VistA Evolution Program VistA Immunization Enhancements, Phase 1 VIMM Sprint 2 Planning Meeting Minutes

Date: Tuesday, April 22, 2014 Time: 9:30 PM EST

MS LYNC: 855-767-1051 & Online Access Code: 8739 5862 Meeting Facilitator/Scribe: Dennis Kemp/Jacquie Meeting Lead: James Proctor Marian

Invitees:

X Keith Magoon VA VIMM Project Manager Cheryl Latham Program Manager, Clinical Capabilities X John Karas VA Information Security Officer X Robert Silverman Business Owner Linda Hebert IT Resource Management (ITRM) Linda Kinsinger Project Sponsor Rhonna Clark Security Engineer, Information Security (IS) Thomas Grimm Service Delivery and Engineering (SDE) Vicki Bowman Privacy Officer X Brian Frederickson VA Planner X Mike Montali VA Development Manager X Chuck Link VA M Developer X Alan Monosky VA M Developer Seema Chaudhry VA Functional Analyst X Sridevi Uppalapati PMO Support Project Manager X Erik Vazquez PMO Support Requirements X Dennis Kemp PM Support Project Manager X James Proctor PM Support Release Manager X Jacquie Marian PM Support Business Analyst X Helena Gilbert PM Support Technical Writer

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

1 Discussion:

Topic: Opening Comments Presenter: Dennis Kemp Discussion:  Purpose of meeting o To discuss and validate the requirements scheduled for Sprint 2

Topic: Product Backlog for Sprint 2 Presenter: James Proctor Discussion:  There were several sessions between Rob and the developers (Alan and Chuck) on the priority of these requirements; most likely will accept these requirements designated for sprint 2 as is, but the purpose of this meeting is for validation of these IDs.  Rob stated there were several emails yesterday with the developers regarding 1001 needing to be part of the same sprint with 0242 and 1002; they decided against that and the sprint will remain as planned. The requirement 1001 because of its time and effort would have disrupted sprint 2 so it stays in sprint 3 and the functionality will not be fully demonstrable until sprint 3. Chuck agreed with Rob’s statement.  0242, 1002, 0202 requirements were displayed. Chuck will be working on these 3 requirements in sprint 2.  0272, 0274, 0288, 0289 are to be developed concurrently with 1 programmer o 0272 and 0288 are the same requirement of capture information related to the Immunization Provider o 0274 and 0289 are the same requirement of render information related to the Immunization Provider o Rob mentioned these requirements appear to be same requirement and reviewed older documentation of requirements to see if anything was lost o Keith mentions the Business Process Activity column (C&D on Short Term Tab) is different for the like requirements in the Business Requirements Matrix . 0274 is Complete Immunization Documentation->Document Immunization. Clarification states immunization provider is always the vaccinator not associated with standing order policy. . 0288 is Complete Immunization Documentation->Document Immunization->Document Immunization Administration; so Business Process Activity is an additional one and Clarification is different between the two. Clarification states standing order policy.

2 . Not sure from a business flow stand point what the difference is; Rob states in the developer’s notes document there is reference to 3 different roles being captured: ordering provider, administering provider, and documenting provider. In many cases, there will be 1 or 2 people filling all 3 of those roles; for example, a physician placing the order and a nurse both administering and documenting that administration. In order to meet the requirements completely, those are captured in 3 separate fields just in case they are not the same administering and doing the documentation, which can happen where you have an ordering provider based on standing order protocol where that ordering provider is being named on behalf of the overall process so it may even be the Chief of Staff of the facility. . 0288 is capturing the ordering provider where we are dealing with a standing policy where the ordering provider did not have a direct interaction with the patient that day . 272, 274 is based on when that order comes from a direct clinical action that day . Keith asks James to add additional info to this document for the 4 requirements so there is clarification of what the actual requirement is fulfilling . Chuck refers to development notes where this is all covered  Rob is in agreement of the requirements presented today  Keith requested a cancellation of the Technical Resources meeting for today at 11am EST  1 feedback received from the sprint 1 document that was shared out widely yesterday; Rob will be sending to Chuck and Alan for their awareness. It is mostly questions nothing has changed as a result of it. Looks like we are getting some validation of that document.  The typo pointed out yesterday is on a list to be corrected probably today.  Chuck to work on the first 3 requirements; final 4 will be Alan  Keith asked if the burndown charts for sprint 2 be updated for Thursday’s SCRUM meeting. James will get the information from Chuck and Alan by COB tomorrow in order to get their burndown from this week.  Chuck stated he owed a document that will be out today with all the updates. Topic: Presenter: Discussion: o Topic: Open Forum/Action Items Presenter: Dennis Kemp

Discussion:

3 Action Items:

Assigned To Date Due Date Action Item Disposition/Status Assigned James to obtain the work James Proctor 4/22/14 4/23/14 completed from developers to update Sprint 2 burndown charts Update requirements 0272, James Proctor 4/22/14 4/23/14 0274, 0288, and 0289 in the product backlog to add clarification of what is being fulfilled