1 / 13

Public Health Reporting Initiative: Stage 2 Draft Roadmap

Public Health Reporting Initiative: Stage 2 Draft Roadmap. Stage 2 Roadmap. Value Timeline / Phases Phase Descriptions Outcomes / Deliverables. Stage 2 Value Proposition. Identify the reusable data elements and structures to streamline development of implementation guides

ferris-wheeler
Download Presentation

Public Health Reporting Initiative: Stage 2 Draft Roadmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Public Health Reporting Initiative: Stage 2 Draft Roadmap

  2. Stage 2 Roadmap • Value • Timeline / Phases • Phase Descriptions • Outcomes / Deliverables

  3. Stage 2 Value Proposition • Identify the reusable data elements and structures to streamline development of implementation guides • Define the core functional infrastructure required to both send and receive public health reports • Promote interoperability across health information systems critical to public health reporting

  4. Following the S&I Framework Process – Use Case to Standards Harmonization to Specification 8/1 5/23 4/25 1/3 5/9 2/1 6/20 4/11 3/28 3/14 2/29 6/6 7/4 7/18 8/15 8/29 2/15 1/17 User Story / Use Case Development Functional Requirements You Are Here Data Dictionary Update Data Model Analysis and Update Standards Analysis & Harmonization Implementation Guide Development Pilot Readiness Assessment

  5. Step 1: Functional Requirements Analysis • Assess functional requirements for public health reporting and make updates that are based on input from 5 domains • Domain Working Groups • Timeline: TBD • Deliverables: Domain Level Functional Requirements

  6. KEY DECISION: Which data elements must be machine-readable? • Based on the definition and user needs • Determine which data elements are important to be machine-readable before 2018 • If Public Health information management systems are NOT expected to be READY to manage reports based on the machine readability of a data element by 2018, it is a LOW priority • If Public Health information management systems ARE expected to be ready to manage reports based on machine readability by 2018 it is a • HIGH priority if it greatly improves report routing and subsequent action • MODERATE priority if it would only somewhat improve these factors • Functional Requirements workgroups • Deliverable: list of high & moderate priority data elements. High, and possibly moderate, will be targeted to be constrained to machine-readable code in Stage 3

  7. Step 2: Identify data elements and add to S&I Clinical Elements Data Dictionary • Identify data elements for each user story • For example, this can be done by reviewing forms in current use and through further dialog with submitters • Identify data elements that appear in multiple user stories and harmonize their names and definitions • Identify data elements not in Clinical Element Data Dictionary • Add data elements and definitions to CEDD • Vocabulary and Terminology Group • Timeline: TBD • Deliverable: updated (augmented) CEDD, Repository of data elements and value sets for 5 domains (e.g. RCMT), Map to EHR Source Information (e.g. CSTE Common Core List of Data Elements; Structured CSTE Position Statements)

  8. Step 3: Data Modeling and Analysis • Map data elements to existing functional public health and clinical domain models • Where necessary, add terms and concepts to those models • Identify requirements for significant model enhancements • Data Modeling / Terminology workgroup • Timeline: TBD • Deliverable: proposed updates to key data models (e.g. S&I data models, FHA Public Health Reporting Model, HL7 DAM)

  9. Step 4: Standards Analysis and Harmonization • Scan harmonization artifacts for reuse (data elements, value sets, concepts, S&I simplification) • Develop list of candidate standards applicable to use case requirements, including relevant vocabularies • Make recommendations to SDOs if needed (responsible: Vocabulary and Terminology Group) • Timeline: TBD • Deliverables: Inventory of candidate standards; Harmonization Criteria; Standards Fit Analysis; Recommendations for potential SDO modifications

  10. Step 5: Technical Implementation Guide / Specification • Develop Implementation Guide with added reconciled data elements. • Define value sets for all Common Elements • Compare available code sets for their alignment to priority public health data elements • Pick the code set with the greatest alignment • ID missing values from the selected code sets, and submit these to the code set SDO • Vocabulary and Terminology Harmonization WG • Duration: TBD • Deliverables: Technical Implementation Guide (TIG); Test tools and procedures; Value sets to be assigned for each required data element

  11. Step 6: Pilot Readiness Assessment • Determine which partners and systems will be ready to receive standardized electronic reports by 2016 • This work will be done by Domain Working Groups Timeline: TBD • Deliverable: Readiness Profile / Pilot Engagement Plan

  12. Following the S&I Framework Process

  13. Following the S&I Framework Process (cont.)

More Related