introduction motivation federal policy and others see interoperability as central interoperability...

INTRODUCTION

Motivation

Federal policy and others see interoperability as central

Interoperability is key to public health Public health has a low level of representation in the

national discourse Public health is at risk at not getting its unique and

important needs met Doing work better Achieving better population health in jurisdiction

Only public health professionals can advocate adequately for public health

Can we increase the participation of public health in this national discouse?

Outline

Present our conception of the business case for public health participation in national standardization efforts

Outline our plan for increasing participation Present the development of a resource we

are making publicly available Demonstrate the use and updating of the

resource

MAKING THE BUSINESS CASE

PHDSC PLAN FOR INCREASING PARTICIPATION

BUILDING THE “STORIES” RESOURCE

Interactive Model Module 1 (M1): HIT Adoption’s Stories

Identifying and documenting best practices in HIT adoption in public health

Module 2 (M2): HIT Standards Resource Center Educating the public health workforce on public health

informatics and HIT standards Module 3 (M3): Public Health Needs for HIT Projects

Identifying and documenting business processes and functional requirements for interoperable EHR-PH systems

Module 4 (M4): Public Health Participation in HIT Standardization Process Developing on-line tools to enable local and state public health

participation in the national HIT standardization process, including participating in on-line surveys, tracking participation, the experience with participation, and lessons learnt

Functional Requirements Analysis Specification Document (FRAD)

Goal Participants

Actors, i.e., users - public health practitioners, clinicians, vendors

Functions Actions, i.e., rolebased

Activities in relation to each module e.g., Story submitter,

reviewer, reader, etc.

Nonfunctional requirements e.g., Content update

schedule, role-based access to the web-site content revisions/updates

Software and hardware requirements

Evaluation plan Timeline

Bruegge B. and Dutoit A.H. Object-Oriented Software Engineering. Pearson Prentice Hall. Upper Saddle River,NJ. 2nd Edition. 1-172.

Method

1. Design of repository2. Search by public-health knowledgeable

searchers3. Categorization by team members4. Redesign5. Publication

1. Design: Entity-Relationship Diagram for Resource Database

PHDSC


Entity-Relationship Diagram for Resource Database

PHDSC


Educating the public health workforce on public health informatics and HIT standards


Developing on-line tools to enable local and state public health participation in the national HIT standardization process

Entity-Relationship Diagram for Resource Database: PHDSC

Method



2. Search by Searchers

Students at Johns Hopkins Staff at HLN Wide range of domains Wide range of functions Mostly domestic Active Web site Some documents

Method



3. Categorization

CDC Domain Public Health Essential Function Informatics function Standardization phase Standardization Activities

Domains: CDC +

Bioterrorism Chronic Disease Communicable

Disease Dental Health Emergency

Response Environmental

Health Epidemiology Global Health

Immunization Injury Maternal and Child

Health Mental Health Occupational Health Public Health

Informatics Vital Statistics Zoonotic, Vector-

Borne, and Enteric

Business Processes: Public Health Essential Functions

Assess Assure Connect Develop Diagnose Educate Empower Enforce

Evaluate Exchange Identify Inform Investigate Manage Mobilize Monitor Research

Informatics Functions

Analyze Data Collect Data Code Data Generate Reports

Reminders, Notifications, Alerts, Summaries

Integrate Data Manage Data

Store, Verify

Standardization Phases

Needs and Priorities Standards Development Standards Harmonization Standards Trial Implementation (Testing) Standardized HIT Products Certification Standardized HIT Products Adoption

Standardization Activities

Identify domain need

Establish functional requirement

Develop spec Identify overlap/gap Resolve overlap/gap

Select standard Implement standard Test standard spec Deploy standard Establish

compliance Establish

conformance Certify HIT product

Entity-Relationship Diagram for Resource Database

PHDSC


Educating the public health workforce on public health informatics and HIT standards


Developing on-line tools to enable local and state public health participation in the national HIT standardization process

3. Categorization

CDC Domains 15 Public Health Essential Function x 17 Informatics function x 6 Standardization phase x 6 Standardization Activities x 12 = a lot!

Method



4. Redesign

All systems, as well as those dependent on standards

While not exhaustive, accept multiple examples

Must be active (updated) Must be interactive (not just a report) Must be current Must be accessible (not subscription) Must have substantive information (not just

“brochures”)

Method



THE “STORIES” RESOURCE

For more information please contact Centers for Disease Control and Prevention1600 Clifton Road NE, Atlanta, GA 30333Telephone, 1-800-CDC-INFO (232-4636)/TTY: 1-888-232-6348E-mail: [email protected] Web: www.atsdr.cdc.gov

introduction motivation federal policy and others see interoperability as central interoperability...

Documents