1. Public Health Reporting Initiative April 4, 2012

2. Agenda TopicTime Allotted Welcome / Agenda Overview - John Stinn4:00 - 4:05 Communications Update4:05 - 4:15 Data Mapping Process Overview and Progress Update – Nikolay Lipskiy FHIM Update – Steve Wagner 4:15 – 4:35 Functional Requirements Template – John Stinn4:35 – 4:45 Face-to-Face Meeting – John Stinn4:45 – 4:50 Discussion4:50 – 5:00 Adjourn4:50 – 5:00

3. Communications Update Communications team has been working to develop and refine a communications strategy Developing materials to enhance outreach and communication within the Initiative and outside of the Initiative

4. DATA MAPPING PROCESS Wiki page: http://wiki.siframework.org/PHRI+- +Data+%26Terminology+Harmonization+Sub-Workgrouphttp://wiki.siframework.org/PHRI+- +Data+%26Terminology+Harmonization+Sub-Workgroup

5. Introduction What is the purpose of the data mapping workgroup? – Provide an implementation-neutral view of existing options for data elements and formats – Move towards harmonization and consolidation of data elements and formats, where possible – Identify gaps between public health and clinical care data elements Who should participate? – User Story submitters (identify and verify data elements) – Initiative Members / Public Comment – verify and validate data elements in terms of formats and value sets – Individuals with an interest in or skills related to data modeling and data element identification To join the Data Mapping sub-workgroup, email Lindsay Brown (lrbrown@cdc.gov)lrbrown@cdc.gov

6. Data Harmonization Timeline FebruaryMarchAprilMay Develop / Collect Data Elements from each User Story Populate domain-level Data Element spreadsheets (including formats and value sets) Validate domain-level spreadsheets with community – Public Comment Map Public Health Data Elements to Clinical Care Data Elements – Identify Gaps Develop Content Profile – including Common Public Health Data Elements across all domains You Are Here Content IdentificationData MappingData Modeling

7. Process 1.Collect Data Elements from User Story submitters 2.Consolidate and Expand Data Element Information at the Domain level 3.Validate Data Element Information 4.Identify Gaps with Clinical Care 5.Develop “Content Profile”

8. Collect Data Elements from User Story Submitters User Story submitters compiled lists of their data elements, including the following information (where possible): – Data Element Name and Description – Programmatic vision of optionality – Programmatic vision of format and/or value set User Story Data Elements submitted to Domain leads Completed at the end of February

9. Consolidate Data Elements Domain leads review User Story Data Elements and consolidate information for each story into Excel Templates, including: – Data Element Name – Data Element Description – Optionality – Standardized Definitions of Required/Optional (R/O) 1 = Required and Null Flavor NOT allowed 2 = Required and Null Flavor is allowed 3 = Required data field to be collected, may be empty 4 = Required data field if you collect it, but may be empty 5 = Shall not / not allowed – Format If not provided by the user story submitter, domain leads looked to value sets to find an appropriate format for data elements – Value Set Complete: Communicable Disease (including HAI and Syndromic Surveillance) Child Health In Progress: Chronic Disease Adverse Events Vital Statistics

10. Example: Consolidated Data Element spreadsheet (required elements) Data Element Name Data Element Description OptionalityFormatValue SetNotes Identifier Identifier of the subject of the report CX Unique Patient Identifiers related to individual identifiers based on HL7 Table 0203; Subset of HL7 2.x Identifier Type table (excluding organization identifier) ISDS category Patient Demographics, data element: Unique Patient Identifier Name Name of the subject of the report XPNHL7 Table 0440 Address Address of the subject of the report AD (Address) Syndromic has separate data elements for city/town, ZIP code, state, country and county Phone Phone number of the subject of the report TN (Telephone Number) Email address Email address of the subject of the report NET (Network/Emai l address) Date of birth Date of birth (DOB) of the subject of the report 3 DT (Date) Age Age of the subject of the report at the time of diagnosis 3 Integer Gender Current gender of the subject of the report 2 CE (Coded Element) Administrative Sex (HL7 v2.x) Another option for consideration is the Administrative Gender (HL7 V3)

11. Validate Data Elements Consolidated spreadsheets returned for User Story submitter review Consolidated spreadsheets posted for Public Comment Coming up in the next few weeks

12. Identify Gaps with Clinical Care Compare consolidated spreadsheets with clinical care data elements (e.g., C83, FHIM, etc.) Identify gaps between public health and clinical care Coming up over the next month

13. Develop Content Profile Identify the Common Core Data Elements for Public Health Reporting across domains Preserve content and data element spreadsheets at lower levels (e.g., HAI, syndromic, child health) Develop content narrative Coming up in May

14. FHIM Update Steve Wagner – Update on FHIM work as part of the Data Mapping Sub-Workgroup

15. Functional Requirements Have developed a template on the wiki: http://wiki.siframework.org/PHRI+Functional+ Requirements http://wiki.siframework.org/PHRI+Functional+ Requirements Working through user stories and domain custodians to identify and review functional requirements Will be posted for review and comment, when draft is developed

16. Face-to-Face Meeting Update from John Stinn