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

• 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

PHRI User Story Implementation Guide Candidates

User Story ProposedTier

Reportable condition case reporting 1

Healthcare acquired infection reporting 1

Cancer registry reporting 1

Early Hearing reporting 1

Birth and fetal death reporting 1

Drug adverse event reporting 1

Medical device adverse event reporting 1

Vaccine adverse event reporting 2

Natl. Hospital Care Survey 2

Immunization registry exchange 2

Tobacco quit line exchange 2

BRCA counselling registry reporting 2

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)

Tier 1 Agencies &

Associations

Tier 2 Agencies & Associations

EHR, PH, and Intermediary System Vendors

Possible Process

1. Set ground rules2. Build consensus on common “core” data elements3. Develop consensus on format - HL7 2.x, CDA or both4. Address how “core” elements and different

“extension” elements are managed5. Address how “trigger” and “filter” knowledge base

should function6. 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, Shalina Wadhani – 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

Task Due Date

Meetings with User Story Submitters, Federal Partners, and Association Partners to introduce PHRI, Implementation Guide development, gain buy-in and survey the vendor landscape

6/26 – 7/10

Weekly Meeting Kick-off Thursday 7/262-4 PM EST(weekly Thursday meetings)

Final Implementation Guide completed 9/25 (tentative)

Risks / Dependencies

• Aggressive timeline• Member (or proxy) participation– Possibility of forking

• Base Standard “fit”• Future dependency: Pilot setting