March+7,+2012+Agenda+and+Meeting+Minutes

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


 * Date: March 7, 2012**
 * Name:** Public Health Reporting Initiative Web Conference

Live Meeting: []
 * Location:** Conference Call: 1-866-842-6975; passcode: 218840#

**Agenda/Objectives:**

 * **Topic** ||= **Time Allotted** ||
 * Welcome / Agenda Overview - John Stinn ||= 4:00 - 4:05 ||
 * Use Case Update - John Stinn ||= 4:05 - 4:15 ||
 * Data Mapping Working Group Update - Nikolay Lipskiy ||= 4:15 - 4:20 ||
 * Stage 3 Deployment Working Group Update - Seth Foldy ||= 4:20 - 4:35 ||
 * Face-to-Face Working Meetings - John Stinn ||= 4:35 - 4:45 ||
 * Open Discussion ||= 4:45 - 5:00 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**

 * __Use Case Update:__**
 * Still need to complete the Adverse Events and Child Health user stories
 * Will replace "initial" with "provider-initiated" report
 * Final document will be posted to the wiki by 3/14/12


 * __Data Mapping Update:__**
 * Started mapping CSTE common core data elements to C83 document
 * Awaiting further user story data element submissions
 * Submissions due by 3/9/12
 * During the data mapping call on 3/8/12, will discuss how core elements can map to the CEDD - would like user input


 * __Stage 3 Deployment Workgroup Update:__**
 * At the last meeting we discussed several activities in parallel – data mapping and requirements gathering then also consider readiness for stage 3 MU and IG inclusion – had a small group formed, are drafting the readiness tool
 * 3 main questions for the readiness tool
 * Clear path for obtaining consensus within community around user stories, data elements and value sets
 * Likelihood of participating in a pilot this year
 * Universal readiness of PH receivers by October 2015
 * Can we share the timeline slide for the rest of this calendar year – HITSC will discuss the standards readiness in 4QTR 2012 – so would need to have guides done in time for the HIT policy committee a few months sooner;
 * Final decision will be in the middle of 2013 – proposed rule expected by end of 2013
 * EP and EH/CAH testing for stage 3 begins Oct2015 – John will put together as slide
 * David: Don’t abandon if something has been ready, it can still be in stage 2 – get HAI reporting into stage 2 – Need support from all on this call

__**Face to Face meeting options:**__
 * S&I F2F: 4/11-4/13 in Alexandria, VA – PH-Reporting Initiative is invited,
 * Who may be able to attend?
 * Kosta will be there, leadership team: Seth, Mike, Anna, Nikolay will attend to have ears at the table for intra-initiative coordination and the related tools
 * Meeting would be helpful for our work – either face to face or at least virtual conference
 * Looking for future time for virtual conference
 * CSTE – Rita is going, there should be space, Bill, David B may be. John will send out a poll about CSTE participation.

__**Other Topics?**__
 * A place to get more information about the HAI effort? Letter template which was sent out via CSTE and CDC to all HAI programs,
 * HAI material has been balloted – vendors have been using – legal mandate is ongoing
 * Send email to David to get the template letter: David.birnbaum@doh.wa.gov
 * Cindy: When are we starting to work on the functional requirements?
 * Starting with data elements
 * Lise – Folks that have submitted references to existing implementation guides / activity diagram, for AE we will start with those
 * Define the functional requirements from the use case document instead of from existing standards.
 * Date element mapping covers some information, but there information flows will need to be better understood,
 * Also need to look on the PH side – are receiver systems different – does that constitute separate flows or not?
 * Trigger timing and reporting process is very important – ability for the EHRsystem to gather and then apply the rules for each report that needs to be sent out – the criteria may overlap between different programs, so we need to articulate the logic needed to be able to create each specific report
 * Need to classify the requirements – can base on simplification group work
 * To do to organize the Next steps and present at the next meeting
 * Co-leads are expected to collate data elements for their domain and that can kick start some of requirements discussion
 * Therese: PH receives messages from all over – sometimes we use a router using the header to route, but it will be different here, as we are looking at using the same format for all user stories
 * We’ll have to accommodate in the report to have the type of report identified ahead of time – this is a good requirement to keep in mind

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