February+8,+2012+Agenda+and+Meeting+Minutes

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


 * Date: February 8, 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 ||
 * Review of Use Case Comments - John Stinn ||= 4:05 - 4:25 ||
 * Sub-Workgroup Updates
 * Definitions - Riki Merrick
 * Data Modeling / Terminology - Nikolay Lipskiy ||= 4:25 - 4:35 ||
 * Phase 2 Roadmap - John Stinn ||= 4:35 - 4:50 ||
 * Discussion / Action Items ||= 4:50 - 5:00 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**

 * __Review of Use Case Comments__**
 * Will begin to review comments about the Use Casetoday - comments can be provided through February 22nd (updated Use Case drafts will be posted to the wiki)
 * Will follow-up with comment submitters to ensure comments are addressed appropriately
 * If you have a question about your comments, please email lrbrown@cdc.gov
 * As a reminder, comments can be posted using the discussion boards. In addition, there is a comment log to help manage comments – to track follow up and review of submitted comments; this log was the basis for discussion.
 * Comment Review
 * Value of PH IE (David Birnbaum comment) – should the value statement request further research around value chain; this language has been added to the Use Case
 * Concern that the Use Case could be oversimplifying requirements for HAIs (David Birnbaum comment); language has been added to explain that there will be more complexity in the functional requirements to allow this analysis to take place at the requirements stage, rather than with the Use Case
 * Support for these additions from Tiffany Colarusso - not just applicable to communicable disease, can be applied across all activities (included Communicable disease reporting) and keep the HAI example
 * Document uses EHR and EHR system in a manner that is confusion; needs to be clarified; the document has been reviewed and updated accordingly
 * Different user stories use terms differently; the definitions work group will review and provide definition to be applied consistently
 * HIE as part of the component based HER; HIE in any capacity is considered part of the architecture; is it possible that we are talking about a broader set of entities – is an HIE an outer boundary for EHR, but that isn’t always the case. Seth offered the suggestion that this should consider not other Meaningful Use (preparedness, PH programs, etc) -- John and Cindy will discuss this offline.
 * One of the challenges with Use Case is capturing the harmonization across each user stories; keep in mind we have gone from 30 to 5 and then form harmonized standards and models leading to a standardized implementation guide. This is a very good comment, and we are working towards standardization, but still working through that process. Noam indicated that his key concern is – what happens next, what do we do with this use case? Get the user stories consolidated into the five domains, then identify common elements and standards that can be used to move towards implementation guide. Seth suggested, that at the end of the year (this year) we have some data elements to illustrate some reports (but not all); Noam is concerned that if we move forward without a single ‘something’ we will have to go back and revisit it later. -- John and Noam will connect this week to discuss.


 * __Sub-Workgroup Updates__**
 * Definitions Workgroup
 * Working through public health reporting definitions - current spreadsheet can be found on the wiki page
 * Some definitions have been accepted, others are still being discussed
 * There is some concern about the title of the use case - should "Provider-Initiated" Public Health Report replace "Initial" Public Health Report. Riki will facilitate a discussion with the co-leads and then share with members.
 * Data Modeling / Terminology
 * Next meeting is February 9 from 12-2 PM EST - more information can be found on the wiki page
 * Want to leverage what was done by other initiatives and programs to support our work
 * reviewed FHIM - Federal Health Information Model
 * Began discussing the CEDD - Clinical Element Data Dictionary (to which our data elements will be added)
 * Currently discussing the scope, process, deliverables, and value-add of this sub-workgroup


 * __Phase 2 Roadmap (slides posted at the bottom of the page)__**
 * Value for Stage 2 – identify data elements and structures to streamline development of implementation guides, core elements, and interoperability
 * Goal is the development of an implementation guide that can be piloted with a vendor and provider with PH system
 * These items may have some overlap (not a strict waterfall), this is just a high level picture, there may be iterations within each; there will be time to revisit in upcoming weeks
 * Step 1: Domain functional requirements document – date TBD – capture the requirements in a way that aligns to five domains; tie user stories to desired implementation workflows and data elements
 * Are these requirements expected to cross all reports (Seth)? - we may have to see how it plays out
 * Domain leads will look at all of the requirements, but will need to identify what is common to create a single data flow for the implementation guide; if there is a single domain that falls out, that will need to be addressed
 * If we are talking about PH receipt, those should be common across (Cindy V); these need to be differentiated from EHR requirements (which may have more variation across domains)
 * Domain working groups need to determine importance of machine readable elements (Seth); previous discussions indicate that we are constrained to a machine readable vocabulary; where best to focus vocabulary code specification and where to do without.
 * Can this group make this decision without assuming how/ why data is needed and what PH will do with it? (Cindy) This needs to go into high and moderate priority items.
 * Is the charge of this project to create a platform/ machine independent model for flow between clinical and PH world (David)? At this phase, we are heading towards platform independent level in the form of an implementation guide; once at the pilot, will get to machine specific model.
 * Step 2: Updated Clinical Elements Data Dictionary, repository of these elements and value sets of the 5 domains
 * Step 3: S&I Data Model updates using other Domain Analysis Models

__**Presentation**__ This powerpoint was shared during the meeting to share/discuss the stage 2 roadmap and describe the next steps in the work of the initiative. [|Post comments about this presentation][|here][|.]

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