160 likes | 344 Views
Public Health Reporting Initiative. April 4, 2012. Agenda. 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.
E N D
Public Health Reporting Initiative April 4, 2012
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
Wiki page: http://wiki.siframework.org/PHRI+-+Data+%26Terminology+Harmonization+Sub-Workgroup Data Mapping Process
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)
Data Harmonization Timeline Develop / Collect Data Elements from each User Story You Are Here 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
Process • Collect Data Elements from User Story submitters • Consolidate and Expand Data Element Information at the Domain level • Validate Data Element Information • Identify Gaps with Clinical Care • Develop “Content Profile”
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
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
Example: Consolidated Data Element spreadsheet (required elements)
Validate Data Elements • Consolidated spreadsheets returned for User Story submitter review • Consolidated spreadsheets posted for Public Comment • Coming up in the next few weeks
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
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
FHIM Update • Steve Wagner • Update on FHIM work as part of the Data Mapping Sub-Workgroup
Functional Requirements • Have developed a template on the wiki: 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
Face-to-Face Meeting • Update from John Stinn