Agenda

1. Public Health Reporting InitiativeStage 3 Sprint: Implementation Guide DevelopmentPhone: 800-857-9362 x93830 1

2. Agenda • New Member Introductions • PHRI Background & Process • Common Core Data Elements • Approach • Review Draft • Discussion & Proposed Modifications • Next Steps & Homework • Questions

3. Suggested Ground Rules • Everyone may speak • ID your name & user story (report type) • Listen carefully • Read assigned work and minutes before each meeting • Limit “back-pedalling” to critical issues • Yield when it is “good enough”- do not let perfection threaten good • Seek consensus quickly; let moderator test consensus • If consensus fails, Tier 2 steps back to see if consensus can procede for this first version of the specification • Concerns about process? Immediately bring to Foldy’s attention • 678-733-4289 • skf6@cdc.gov

4. PHRI Process • Scope of the PHRI is limited to a provider-initiated report sent from an EHR system to a public health agency system directly OR through an ‘intermediary system’ such as an HIE • 30+ “User Stories” from the public health community were developed and submitted for consideration in the PHRI Use Case • The PHRI developed Use Case and Functional Requirements documents based on the submitted User Stories and with the support and input from PHRI membership • Initial set of data elements captured at a domain or user story level (e.g., Cancer data elements) • Where possible, data elements harmonized within particular reporting scenarios or domains (e.g., “Communicable & Syndromic” Data Elements) • The Data Mapping Workgroup has taken the data elements and worked to harmonize along common requirements and create a set of common core data elements • Proposing common core data elements to Sprint group • Finalizing the Data Harmonization Profile with more detail

5. Recap: Public Health Report Structure Public Health Report = Common Core Data Elements + Report-type Specific Data Elements + Implementation Specific Data Elements

6. Data Harmonization Approach • Determine “categories” of Data Elements • Common Core - Harmonized data elements that are widely shared across several report types • Expect EHR systems to be able to produce these data elements • PH systems may or may not consume these specific elements, based on their specific requirements • Focus of the Data Harmonization Profile (forthcoming) • Report Type Specific - Harmonized data elements that are broadly required across public health for a particular report type (e.g., communicable disease case report, birth record report, etc.) • Harmonization across report types and/or domains where possible • These data elements will be sent along with the common core to satisfy reporting needs • Implementation Specific - Additional, relatively unique, or non-harmonized elements required by a particular jurisdiction or public health program • Unique to specific sender / receiver workflows • Should be considered and included for specific implementations • Define approach to identify common core data elements • Propose common core data elements to Stage 3 Sprint group for review and acceptance • Modifications from the Stage 3 Sprint group should be suggested to the Data Mapping group to reach appropriate resolution • Incorporate common core data elements into the Implementation Specification

7. Identifying the Common Core • Data Elements were collected from participants, identified through previously submitted user stories, and consolidated from other published lists of data elements (e.g., CSTE common data elements) • Data Elements were then mapped to clinical concepts (via the Clinical Element Data Dictionary – an abstract model of clinical information) to begin identifying commonalities

8. Identifying the Common Core • Once all of the data elements were consistently mapped to the same terminology, an analysis was performed to assess commonality by examining the number of times a data element appeared across report types or across domains • A proposed set of common core data elements for public health reporting was compiled to include any data element that: • Appeared in 3+ report types(out of 13) • Appeared in 2+ domains (out of 5) • Appeared in a previously published set of core data elements (e.g., CSTE or ISDS) • This proposed set has been reviewed by the Data Mapping Workgroup, as well as the PHRI co-leads, to identify and address gaps or inconsistencies

9. Reviewing the Common Core • The Stage 3 Sprint group needs to reach consensus on the set of data elements presented as the Common Core • Is anything missing? • Is anything included that should not be? • A spreadsheet has been created to include • Data Element Names • Data Element Descriptions • Classification (i.e., Common Core, Report Type, Implementation Specific) • This spreadsheet is organized into “objects” – each object is a ‘bucket’ that holds a set of related data elements • For example, the “Patient Information” object includes data elements such as “Patient Name,” “DOB,” and “Gender” • These objects can be mapped to the CEDD, CDA, FHIM, and other implementation models

10. Review • Spreadsheet • Posted to wiki, here: http://wiki.siframework.org/PHRI+-+Data+%26Terminology+Harmonization+Sub-Workgroup 10

11. Next Steps • Identify proposed formats, value sets, and optionality for each of the common core data elements • Data Harmonization Profile • Reach consensus among the Stage 3 Sprint group about the common core data elements • Create implementation guidance for the common core data elements for both CDA and 2.x messaging • Identify report type specific data elements and create report type specific implementation guidance for at least one public health report 11

12. Stage 3 Sprint- Activity Timeline • Kick-off Meeting • Consensus • Consensus

13. Questions / Discussion? • Wiki Page • http://wiki.siframework.org/PHRI+Implementation+Guide • Or click “Implementation Guide” button from any PHRI wiki page • Will post presentations, meeting minutes, “homework”, and documents for review • Homework • Attend the PHRI Call on Wednesday, August 8, from 4-5 PM ET (if possible) to hear more about CDA and messaging from experts in health IT • Review the proposed common core data elements and document your comments/suggestions/revisions to discuss on the next call • Additional Questions? Contact Lindsay Brown (lrbrown@cdc.gov) 13