100 likes | 224 Views
Public Health Reporting Initiative – Stage 3 Sprint. SPRINT Objective. Create an implementation specification for public health reporting that can be tested and implemented in time for Stage 3 Testing by late fall-early winter 2012 Implementation of reporting by Oct 2015
E N D
SPRINT Objective • Create an implementation specification for public health reporting that can be tested and implemented in time for Stage 3 • Testing by late fall-early winter 2012 • Implementation of reporting by Oct 2015 • Specification can serve multiple report types: focused on shared “core” elements • Supports collection of an “extended” set of data elements • Largely compatible with needs of a larger number of report types
What Maximizes Benefit to All? • An implementation specification required for certification of Stage 3 EHRs that • Provides immediate benefit to some reporting programs • Establishes conditions that will benefit other reporting programs
Proposal • Tier 1: 7 stories appear with relatively high level of readiness; focus on unidirectional; broad national scope • Tier 2: 5 stories with either less readiness and/or more complex scope (e.g., bidirectional exchange, referral)
Stage 3 Readiness Sub-workgroup:Goal • Create an implementation specification for consideration to be included in stage 3 • “Core” spec + Extensions • 7 Tier 1 candidates • 5 Tier 2 participants (defer to Tier 1 consensus) EHR, PH, and Intermediary System Vendors Tier 2 Agencies & Associations Tier 1 Agencies & Associations
Possible Process • Set ground rules • Build consensus on common “core” data elements • Develop consensus on format - HL7 2.x, CDA or both • Address how “core” elements and different “extension” elements are managed • Address how “trigger” and “filter” knowledge base should function • Document decisions in Implementation Guide (support team) • Review progress in weekly checkpoints
Members and Support Team • Lead: Seth Foldy • Members: • User Story Submitters • Federal Agency Reps • Association / Member Reps • EHR Vendors / PH IT vendors / staff • Support Team • Erik Pupo, SME • Brian Castor, PM • Lindsay Brown, Business Analyst • Ashley Swain, ShalinaWadhani – IG Technical Writing
Timeline / Commitment • Estimated time commitment: • Meeting: 1.5 – 2 hours per week • Homework: 1 - 2 hours per week • If you are interested in helping with this work, email lrbrown@cdc.gov
Risks / Dependencies • Aggressive timeline • Member (or proxy) participation • Possibility of forking • Base Standard “fit” • Future dependency: Pilot setting