1. Public Health Data Standards Consortium http://www.phdsc.org http://www.phdsc.org

2. Towards Common Work Processes: Business Process Analysis and Functional Requirements Analysis for Public Health Anna Orlova, PhD Public Health Data Standards Consortium aorlova@jhsph.edu aorlova@jhsph.edu PUBLIC HEALTH DATA STANDARDS CONSORTIUM ~ 2009 BUSINESS MEETING OF MEMBERS ~ November 12-13, 2009, Hyattsville, MD

3. Where We Now

4. State Health Department: Organizational Chart

5. All public health activities are supported by customized information systems (databases, registries) developed to address the programmatic needs. Use of IT in Public Health: Where We Now

6. Our information systems do support our programmatic needs Our information systems cannot exchange data between programs within and across public health agencies and with clinical information systems AND…… HIT Standards in Public Health: Where We Now BUT……

7. Towards a Nationwide Health Information Network Where Should We Be in 2014 Why Standards - National Context

8. US Nationwide Health Information Network (NHIN) in 2014 Source: Dr. Peter Elkin, 2006

9. RHIEs as NHIN Components Source: Dr. Peter Elkin, 2006

10. Source: Eileen Koski. Quest Diagnostics. PHIN-2004, May, Atlanta GA Percent of Children Tested for Lead with BLL>10 µg/dL in the USA Vision: PH Surveillance under NHIN

11. Standardizing Health Information Exchanges

12. From Business Processes to Functional Requirements to Standardized IT Solutions

13. PHII Common Grounds Project “ We hope to develop a shared understanding of public health work and identify areas of commonality among public health agencies," said Dave Ross, Sc.D., director of the Common Ground National Program Office at the Public Health Informatics Institute. "The Common Ground program offers public health agencies the opportunity to collaboratively develop requirements for more effective information systems and better data exchange.” Source: Public Health Informatics Institute (PHII). URL:http://www.phii.org/programs/CommonGround.asp Describing Business Processes

14. Describing Functional Requirements

15. The purpose of the requirements elicitation is to specify the information system features from user’s perspectives in a structured Functional Requirements Analysis Document (Functional Standard). FRAD Features: Information System Goals (Tasks) Actors Functions (Actions) Data Sources Workflow and Dataflow High Level Architecture Requirements Elicitation

16. Functional Standard Functional Standard describes work processes that support data exchange between users (e.g., clinicians and public health practitioners) in a format of functional requirements specification for electronic communication between settings (e.g., clinical and public health settings).

17. Functional Standard Functional standard is a vehicle to assure that the work processes of stakeholders (e.g., clinicians and public health practitioners) related to the electronic data exchange are well understood and agreed upon by stakeholders themselves and then communicated clearly to the developers as functional requirements for the information system.

18. “Defining system requirements is the most important step in developing or acquiring any information system. A well-conceived and planned health information system can help organizations understand the need to adjust tasks or processes to be more effective or proactive in protecting community health….” Source: Public Health Informatics Institute (PHII). URL:http://www.phii.org/subjectareas/requirementsdevelopment.asp Defining Requirements

19.  Early Hearing Detection and Intervention Content Profile, 2009-10  Standards for Public Health Data Exchanges: Working with Vendors (Newborn Screening, Diabetes, Quality), 2009  Standards for Public Health Data Exchanges: Functional Requirements Standard for Diabetes Care Management and Surveillance, 2008  Towards a Functional Standards on Electronic Data Exchange between Clinical Care and Public Health, 2007  Developing a Vision for Functional requirements Specification for Electronic Data Exchange between Clinical and Public Health Settings: Examples of School Health and Syndromic Surveillance in New York City, 2006 PHDSC FRAD Projects* *Supported by Health Resources and Services Administration, 2005-2009 URL:http://www.phdsc.org/health_info/com_nhin_activities.asp

20. From Business Processes to Functional Requirements to Standardized IT Solutions Using SOA (Service-Oriented Architecture)

21. Example of Environmental Public Health Tracking

22.  What are the impacts of pesticide exposure on children’s health?  Are changes in the environment related to dramatic increase in asthma?  Are there increases in Systemic Lupus Erythmetosis (SLE) and multiple sclerosis (MS) in communities with hazardous waste sites?  Track health, disease, and risks to target interventions to those populations most affected by environmental hazards and exposures.  Detect new adverse health events associated with environmental exposures.  Detect unusual occurrences, trends, or clusters of specific health events associated with environmental exposures.  Monitor and assess the effects of policies and the efficacy of interventions and established prevention strategies.  Raise awareness about environmental health issues among consumers, policy makers, health practitioners, industry, the public, and the media. Examples of Tasks to be Addressed by the Environmental Health Tracking Network Source: Dr. Nabil Issa, CDC/NCEH Public Health Questions Public Health Actions – Business Processes

23. Environmental Public Health Tracking Network Population Census Environmental Exposure Tracking Environmental Hazards Tracking Health Outcomes Tracking State and National Data Collection Systems Integrated Environmental Health Tracking, Analysis, Evaluation And Dissemination Exposure Hazards  Track health, disease, and risk trends Establish program priorities Develop, implement, and evaluate public health policies and program strategies Develop rapid-response mechanisms to investigate outbreaks and clusters Develop guidelines/standards Generate hypotheses and initiate applied research Public Health Actions Source: Dr. Nabil Issa, CDC/NCEH USER VIEW

24. System Architecture for Environmental Health Risk Detection, Assessment & Management System Architecture for Environmental Health Risk Detection, Assessment & Management GIS/Spatial EpidemiologyRisk AnalysisData Mining & Knowledge DiscoveryStatistical Models Exposure Detection & Risk Analysis Track health, disease, and exposure risk/trends Detect & evaluate risk of exposure to env. hazards Develop & evaluate public health & environmental stewardship policies & programs Develop rapid-response mechanisms to investigate outbreaks and clusters Develop prevention guidelines/standards Generate hypotheses and initiate applied research Environmental Stewardship & Public Health Actions Source: Dr. Nabil Issa, CDC/NCEH (*) Based on risk assessment and national priorities Environmental Hazards, Ecology and Disease Data Collection Systems Disease Tracking * Hospital Discharge Birth Defects BRFSS Cancer Registries Health Surveys Vital Statistics Population Demographi cs * Census Data Exposure Tracking * Human Exposure to Environmental Chemicals Toxic Exposure Surveillance Hazards Tracking * Hazardous Substances- Emergency Event Surveillance Toxic Release Inventory Ecological Tracking * Marine Life Animals Plants Population Disease Indicators Population Demography Health Outcomes Exposure Profile Environmental Hazard Hazardous Material Profile Exposure Integrated Environmental Health Indicators Data Warehouse Biomonitoring Natural Accidental Intentional Ecological Indicators Data Linking/IntegrationMetadataData StandardizationData Quality Assurance Data Integration, Transformation & Geocoding Geocoding Informatician View

25. System Environmental Public Health Tracking Information Exchanges Developer View Source: HITSP, 2009

26. State Health Department: Organizational Chart

27. Use Cases Business Processes Business “Top Down” User Driven (Requirements Driven)

28. Towa rds a Publi c Healt h Doma in at IHE “Top Down” User Driven (Requirements Driven) Use Case Business Processes Use Case Business

29. Towa rds a Publi c Healt h Doma in at IHE “Top Down” User Driven (Requirements Driven) Use Case Business Processes Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Business

30. Towa rds a Publi c Healt h Doma in at IHE “Top Down” User Driven (Requirements Driven) Use Case Business Processes Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Business Working with Developers at the Integrating the Healthcare Enterprise (IHE)

31. Integration Profile Transaction Towa rds a Publi c Healt h Doma in at IHE Content Profile Actor Transaction Actor Transaction Content Profile Actor IHE Technical Frameworks “Bottom-Up” Health IT Solution Driven PIX, PDQ, RFD, XDS

32. Integration Profile Transaction Towa rds a Publi c Healt h Doma in at IHE Content Profile Actor Transaction Actor Transaction Content Profile Actor IHE Technical Frameworks “Bottom-Up” Health IT Solution Driven PIX, PDQ, RFD, XDS “Top Down” User Driven (Requirements Driven) Use Case Business Processes Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Business

33. Task Service Layer Entity Service Layer Utility Service Layer Service Layers Service-Oriented Architecture (SOA)

34. Entity Services Utility Services / IHE Integration Profiles Task Services PIX MgrPDQ MgrRegistryRepositoryAudit IdentityDocument GetPatientLHR Example of Service Layers / Integration Profile Mapping

35. Integration Profile Transaction Towa rds a Publi c Healt h Doma in at IHE Content Profile Actor Transaction Actor Transaction Content Profile Actor IHE Technical Frameworks “Bottom-Up” Health IT Solution Driven PIX, PDQ, RFD, XDS “Top Down” User Driven (Requirements Driven) Use Case Business Processes Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Business

36. IHE & SOA White Paper Integration Profile Transaction Towa rds a Publi c Healt h Doma in at IHE Content Profile Actor Transaction Actor Transaction Content Profile Actor IHE Technical Frameworks “Top Down” User Driven (Requirements Driven) “Bottom-Up” Health IT Solution Driven Task Service Layer Entity Service Layer Utility Service Layer PIX, PDQ, RFD, XDS Use Case Business Processes Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Use Case Functional Requirements/ Capabilities Business

37. Value of SOA SOA links business and functional requirements to standardized interoperable IT solutions For Users (Public Health Professionals and Clinicians) Ability to navigate and select appropriate IT standards/ products for a service that is understandable for a non-technical audience, ie, identity service, document service, etc. Ability to relate user requirements to IHE technical solutions (capabilities) Ability to see commonalities for technical solutions across business processes

38. Value of SOA SOA links business and functional requirements to standardized interoperable IT solutions For Developers Help users and their IT vendors to navigate through interoperability standards Help IT vendors to correctly use interoperability products in their applications Develop new IT products for services requested by users, ie, identity service, document service, etc.

39. Value of SOA SOA links business and functional requirements to standardized interoperable IT solutions So, together we can built interoperable, standards-based IT products that will adhere to user needs to assure “meaningful use” of Health IT

40. Resources: A Service-Oriented Architecture (SOA) View of IHE Profiles – White Paper at the Integrating the Healthcare Enterprise (IHE). (URL: https://sites.google.com/site/projecthrsaphdsc/objective-2 https://sites.google.com/site/projecthrsaphdsc/objective-2

41. Questions?