Public Health Reporting Initiative

January 11, 2012

AgendaTopic Time Allotted

Welcome / Agenda Overview - John Stinn 4:00 - 4:05

Announcements - Mike Coletta• Abstracts• Anything community members need?

4:05 - 4:10

Definitions Workgroup - Riki Merrick 4:10 - 4:20

Presentation of Reconciled "Consolidated User Story Template" - Lise Stevens

4:20 - 4:30

Public Health Reporting Initiative Use Case Document Review - John Stinn / Lindsay Brown

4:30 - 4:40

Roadmap - John Stinn 4:40 - 4:50

Discussion / Action Items 4:50 - 5:00

Adjourn 5:00

Definitions WG Update

Consolidated User Story: Child Health, Birthing Facility

1. Child is delivered. If live birth follows steps 3-9, 2. Clinician conducts initial physical exam

3. Newborn is due for <immunization, hearing test, metabolic test, birth defect assessment, birth registration, etc.>

4. Clinician orders an <immunization, hearing test, metabolic test, additional birth defect testing, etc.>

5. Hospital staff administers <immunization> and conducts <hearing test> and collects <blood specimen> and conducts <birth defect testing>

6. Hospital staff enter data on the <immunization, hearing test, birth defects, lab order> in the EHR database

7. EHR pre-populate information to the Birth/Fetal Death Facility Worksheet8. Hospital staff and clinician review the Birth/Fetal Death Facility Worksheet

9. Information is electronically sent on <immunization, hearing test, metabolic test order, birth defect, birth registration/fetal death registration, etc.> to the PH IS directly or via HIE

10. PH program IS <IIS, EHDI IS, Metabolic IS (LAB), Birth Defect IS, Vital Records> receives notification of report availability

11. PH programs’ staff reviews the report and create PH IS record on a child in <IIS, EHDI IS, Genetic IS, Birth defect IS, Vital records>

12. PH IS sends Acknowledgement of Receipt of the Report to EHR directly or via HIE.

Use Case Name:

Actors:Flow of Events:

Information Exchange Artifacts

1&2 Demographics, Antepartum Record, Prenatal record, Labor & Delivery Record, Postpartum record, Newborn EHR3. Consent (not for birth

registration)4. Test Order or Standing Order5. Immun. Record, Test Results, Birth Defect Record

6. Immun. Record, Hearing Test Results, Birth Defect Record, Birth Record, Heelstick Lab Order7&8. Birth/Fetal Death Facility Worksheet

9. Initial PH Report

10. Notification of Report Availability

11. Updated PH Record

12. Acknowledgement of receipt

Vital Records, Hearing, Immunization, Birth Defects, Metabolic Screening

Newborn, Caregiver, Clinician, Hospital staff, Public health program staff

Pre-Conditions:

Post-Conditions:

Preferred Timing

EHR System, Health Information Exchange (HIE)

Public Health Information System <IIS, EHDI IS, Birth Defect, Vital Records, Metabolic Screening, etc.>

Daily updates

Use Case Document Review

Use Case Schedule/Development

Check out the “User Stories” page on the wiki for more information about the consolidated use case

Action Date

User Story working groups will present a draft of the harmonized user story for each domain

12/21/11 - COMPLETE

Domain User Story Template Harmonization 1/18/12

Harmonized Use Case Draft for member review 1/25/12

Final Draft of Harmonized Use Case 2/8/12

Phase 1 (September-December 2011)

• Charter has been finalized • All participants work together on - assessment of needs for the process - building a consensus on public health reporting definitions - building a consensus on a scope of the Public

Health Reporting HIT Standardization Framework

- development of criteria and selection use cases

- defining a list of WGs• Forming workgroups and starting assessment of

existing artifacts in a scope of the initiative• Development of detailed work plan

August September October November December January February March April

Initiation

S&I Public Health Reporting Roadmap

2011 2012

User Story Validation / Consolidation

Final version of the Charter

FR / ModelingStds Harm

Phase 2(January-May 2012)

• Harmonization of selected use cases into a single use case• Identification of core data elements and data classes• Working on harmonization of FHA and segment enterprise

architecture for public health reporting• Working on terminology• Identification and Harmonization of vocabulary / content

exchange Standards• Development of implementation documentation • Completion of assessment of business process, policy barriers• Proposing public health objectives for Stage 3 MU• Environmental scan of existing shared utilities for public health

reporting and development of a vision on a public health hub for collection, sharing and maintenance

• Development of a vision on a purpose and scope of testing and certification of systems for public health reporting

Use Case Documentation

Spec Development

/ Pilot Planning

8

Potential Artifacts for Phase 2Name of Artifact Description of Artifact Format

Standards Harmonization Analysis Document

Standards harmonization is the iterative process of consolidating selected standards to achieve consensus on a new standard unique to a particular initiative.

Word Document, Process

High Level Data Model The High Level Data Model is used to define the data elements, data

types and cardinality within a Use Case.Excel Document, Template

CEDD

A Clinical Element Data Dictionary (CEDD) defines the data elements and corresponding definitions that are necessary to convey the clinical perspective of Initiative Use Case requirements in a way that is understandable to a variety of stakeholders including functional and technical experts.

Word Document, Process

Implementation Guide

An implementation guide is the final output of the Harmonization process. The document provides implementation guidance for Initiative Use Case requirements aligned to an Initiative Recommended Standard. The template provides suggested sections to include in the document. This template will likely be modified to fit an initiative's needs.

Word Document, Template

Ballot Reconciliation (if necessary)

Ballot reconciliation is the formal process for addressing the comments submitted by the Health Level Seven (HL7) participants and involves both HL7 and the S&I Framework. The S&I Framework serves as a channel to leverage additional healthcare experts for feedback on how to disposition comments.

Word Document, Process

Exchange ProfileAn Exchange Profile documents the preferences and requirements for developers creating EHR systems. The profiles provide non-prescriptive, informative guidance to early adopters who implement the requisite information exchanges.

Word Document, Process