July+25,+2012+Agenda+and+Meeting+Minutes

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


 * Date: July 25, 2012**
 * Name:** Public Health Reporting Initiative Web Conference


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

**Agenda/Objectives:**

 * **Topic** ||= **Time Allotted** ||
 * Welcome / Agenda Overview - Lindsay Brown ||= 4:00 - 4:05 ||
 * Public Comment Update - Lindsay Brown ||= 4:05 - 4:10 ||
 * Data Harmonization - Nikolay Lipskiy
 * Definitions
 * Impact
 * Approaches ||= 4:10 - 4:40 ||
 * Stage 3 Sprint - Seth Foldy ||= 4:40 - 4:50 ||
 * Discussion / Action Items ||= 4:50 - 5:00 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**

 * __Minutes__**
 * Functional Requirements Document and Data Elements for User Stories have been posted for public comment on the PHRI wiki: http://wiki.siframework.org/PHRI+Public+Comment
 * To provide comments:
 * Use the discussion boards linked to on the wiki page (note: instructions for using discussion boards are included as well)
 * Email Lindsay Brown (lrbrown@cdc.gov) with additional comments
 * Timeline
 * Public Comment & Consensus on Functional Requirements and Domain-level Data Elements
 * Through week of 8/15
 * Develop ‘core common’ data elements
 * Through this week (7/27)
 * Develop Implementation Specification, focusing on PH reporting scenarios that are ready for Stage 3 of Meaningful Use
 * Through September
 * Stage 3 Pilot Planning
 * Beginning in September
 * Ongoing identification, maintenance, and harmonization of data elements, vocabularies, and standards for public health reporting (beyond Stage 3 of MU)
 * Beginning now
 * Ongoing modeling of PH reporting data elements
 * Beginning now
 * Data Harmonization
 * Working to develop definitions for classifications (Core common, Report-type specific, and Jurisdiction specific)
 * Core Common data elements to be identified by the end of this week
 * Harmonized
 * Highly reused by many reports across several domains
 * EHR systems should use these elements
 * PH reporting systems may or may not use all core common elements
 * Report Type Specific
 * Harmonized when possible
 * Reused when appropriate
 * Implementation Specific
 * Specific to local or program-specific elements
 * Minimized in favor of report type specific elements
 * Impact of definitions
 * Legislative (MU S2 & S3): Include in MU certification criteria for PH reporting, updating test procedures and conformance rules
 * EHR vendors: Products must support these data elements and interfaces to support PH reporting
 * PH Information System vendors: Products meet requirements of PH program. Should be aware of what is available in EHR for inclusion in PH report, and potentially PH system.
 * S&I PHRI: Primary content for harmonization across all PH domains (i.e., focus of Data Harmonization Profile)
 * National and State PH Programs: Primary focus of cross-domain harmonization
 * Defining “common”
 * Data Element shared by 3+ user stories
 * Data Element shared by 2+ domains
 * Data Element shared by 3+ domains
 * Next steps
 * Thursday Data Mapping Call (12-2 PM EST): Select an approach and propose a set of ‘core common’ data elements
 * Homework to Stage 3 Sprint group: Review proposed set of ‘core common’ data elements to identify any gaps, questions, concerns
 * Stage 3 Sprint group: Make any modifications to the ‘core common’ data elements, in conjunction with Data Mapping group, to support the development of an implementation specification
 * Stage 3 Sprint – Implementation Guide
 * Focused on stories ready for Stage 3
 * Weekly starting 7/26/12

Presentation


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