Data Systems Web Integration: A Public Health Approach
•Download as PPT, PDF•
3 likes•728 views
The document discusses public health informatics standards and the Public Health Information Network (PHIN) framework. It outlines how PHIN aims to advance interoperability between public health organizations through selecting relevant data standards, describing minimum IT capabilities, and developing standardized software applications. It then summarizes Houston Department of Health and Human Services' (HDHHS) data systems integration project, which will develop a web portal integrating various applications using PHIN recommendations to facilitate data sharing.
![Outline ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Similar to Data Systems Web Integration: A Public Health Approach
Similar to Data Systems Web Integration: A Public Health Approach (20)
More from Arnulfo Jr Rosario
Recently uploaded
Recently uploaded (20)
Data Systems Web Integration: A Public Health Approach
- 1. Data Systems Web Integration: A Public Health Informatics Approach AJ Rosario, M.D., M.P.H. Vishwa Rao Bureau of Epidemiology Office of Surveillance and Public Health Preparedness Houston Department of Health and Human Services February 1, 2006
- 6. Information component Wisdom Data Data Data Knowledge Information Information
- 9. WHY DO STANDARDS MATTER?
- 10. STANDARDS
- 11. Data Standards in Public Health
- 14. Figure of Speech Source: O’Carroll, Public Health Informatics and Information Systems Chapter 11, Data Standards in Public Health Format Grammar Information Architecture Context Vocabulary Words Data Standard Equivalent Conversation Component
- 15. Data Standards source recipient transmission 1 2 3 INFORMATION IN STORAGE MESSAGE CONTROLLED VOCABULARY A STORAGE FORMAT B MESSAGING STANDARDS C
- 17. Data Standards source recipient transmission 1 2 3 INFORMATION IN STORAGE MESSAGE CONTROLLED VOCABULARY A STORAGE FORMAT B MESSAGING STANDARDS C
- 19. Data Standards source recipient transmission 1 2 3 INFORMATION IN STORAGE MESSAGE CONTROLLED VOCABULARY A STORAGE FORMAT B MESSAGING STANDARDS C
- 20. HL7 Messages Laboratory Pharmacy Admission Imaging Finance HL7 Messages
- 21. Standards Development OVERLAPS IN COVERAGE Medical Dictionary for Regulatory Activities or MedDRA International Conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH) Coding Symbols for a Thesaurus of Adverse Reaction Terms or COSTART Food and Drug Administration Current Procedural Terminology or CPT4 American Medical Association Logical Observed Identifiers Names and Codes or LOINC Regenstrief Institute Systematic Nomenclature for Medicine or SNOMED American College of Pathologists International Classification of Diseases or ICD , WHO Adverse Reaction Terminology or WHO-ART World Health Organization
- 24. Transformations DATA INFORMATION KNOWLEDGE
- 27. Informatics Veterinary Informatics Clinical Informatics Medical Informatics Bioinformatics Health Informatics Nursing Informatics Dental Informatics Public Health Informatics
- 29. What in informatics is important to epidemiologists? Data standards Vocabulary standards Messaging standards Technology standards Interoperability Data models Relational databases
- 45. Current State of HDHHS
- 46. Data Systems Web Integration Project
- 51. Architecture - Web Portal http://www.hphin.com Stage 1
- 52. Architecture - Web Portal http://www.hphin.com Stage 2
Editor's Notes
- Good Morning. It is our absolute pleasure to be here this morning. We thank you for the opportunity to present.
- We will be covering this topic using this outline. I will give a brief introduction, then talk about where standards come into play in public health practice. Then I will talk about how data standards are used in public health. I will talk a little about public health informatics and PHIN and Vishwa will discuss our current state, the proposed project, IT requirements & he’ll give you a brief summary of what we have talked about. Then, let’s save the Q & A after we complete the presentation.
- Public health practice can be viewed as a set of activities that are all information intensive.
- This is the Tenerife Air Disaster in the Canary Islands in 1977. Two jumbo jets collided because one of them, a veteran KLM pilot had a miscommunication with the control while speaking Dutch and non-standard English phrases. From then on, the use of English phrases became the standard for communication between pilots and control towers.
- This is the world with polio in 1988 to CLICK this is how it is in 2004. Instrumental in this dramatic success of the Global Polio Eradication Program is the certification-standard AFP (Acute Flaccid Paralysis) surveillance systems and laboratory networks to detect ongoing transmission in affected countries and give quality feedback to the polio eradication activities in these countries. The common theme in all these examples is the use of STANDARDS. The presence of standards enables men to build great things like the Pyramids of Giza and eradicate disease on a global scale. And the lack of it can cause destruction and failure of great magnitudes and endanger people’s lives.
- This is the web site of the International Standards Organization. CLICK If you ask them why standards matter, they would say if there were no standards, you would soon notice.
- Daily, we live with standards and we oftentimes take them for granted. CLICK They enable: Global telecommunications Innovations in computer hardware and software Communication of measurements in health care Sending messages and retrieving information across the globe through Internet protocols Drug administration in a variety of settings using interoperable components CLICK
- Let us talk about data standards in public health.
- This requires that we are able to consolidate data and information from a variety of sources both from within the health care domain and outside of it.
- To simplify this scenario, we can think of exchange of health information as a set of the following components. The words we use in the conversation The way we put the words together or grammar And the context in which the conversation occurs
- Carrying on that analogy further, we have words, grammar and context with its equivalents in data standards: vocabulary, format and information architecture. Let us discuss each one in detail. In information exchange, the set of words that we use for everyday conversation we call a vocabulary And for a typical conversation in English we use some 500 words. In specific knowledge domains like health care, we also have vocabularies consisting of codes with agreed upon meanings that we use to convey the same message everytime. And once we put these in context we can talk about information architecture, much like putting together construction components to make a building.
- Much more simply, in public health, and specifically in electronic systems, health data and information move from storage source, is transformed into a message and stored in the recipient We talk about two forms of health information: CLICK Information in storage CLICK Information as a message Health information in these forms use three types of standards. There may be more but these ones are important. CLICK Standards for information in storage include Controlled vocabularies Storage formats CLICK And for standards for messages are called Messaging standards CLICK Let us first talk about controlled vocabularies.
- This is another controlled vocabulary called the Systematized Nomenclature of Medicine or SNOMED, developed by the American College of Pathology. As an example we code the following gory pathology report as follows. We code it as CLICK The GALLBLADDER T-63000 CLICK was ENLARGED M-71000 and CLICK RED OR ERYTHEMATOUS M-01780 CLICK with PUS OR PURULENT DISCHARGE M-36880 easily expressed through the site of CLICK we code rupture as RUPTURED ABSCESS M-41611 In this example, SNOMED tries to assign as many distinct codes to terms as possible.
- Going back to this diagram, let us talk about CLICK storage formats.
- Storage formats are fairly easy since we encounter some of these often. We have MS Office formats, tab- and comma-delimited text files and SAS files
- Going back to this diagram, let us talk about CLICK messaging standards.
- Using HL7 Messages, different parts of a health care facility can exchange health information seamlessly without anymore need for manual translations of inputs and outputs from medical devices and computers.
- When people realized they needed standards to achieve interoperability, several standards development organizations or SDOs, even before people called them such, began developing data standards in specific domains: WHO: International Classification of Diseases for classifying causes of mortality American College of Pathologists: Systematic Nomenclature for Medicine Regenstrief Institute: Logical Observed Identifiers American Medical Association: Current Procedural Terminology Federal Drug Administration: Coding symbols for a Thesaurus of adverse reaction terms or COSTART And MedDRA WHO-ART, COSTART and MedDRA are used in vaccine safety studies. CLICK If you think there are too many standards development organizations here, we definitely have overlaps in content coverage. [TOWER OF BABEL NEXT]
- This is chaos at a different level, or a Tower of Babel for data standards. When we use one language and talk to each other we will understand each other but when we start talking in other languages, there will be chaos. What we need is a way to unify all the concepts contained in the vocabularies so we know which codes in one vocabulary correspond to what in others.
- It is somewhat like worrying about how to plug into electric outlets when you travel a lot to different countries.
- Data in public health also undergo transformations so we can create CLICK Information from data, and CLICK Knowledge from information Within the last decade, with advances in computing power and storage, the use of standards in representing information and knowledge has entered mainstream as we see in the terms information architecture, information infrastructure, information network, knowledge representation and knowledge engineering, ontologies.
- Exchange of data, information and knowledge in health care can happen in three ways: Human-to-human as when we present knowledge in conferences Human-to-computer as when we access web sites and emails using computers Computer-to-computer as when web and email servers automatically keep our Internet functioning or when public health information systems talk to each other as we saw earlier between Oregon and Washington And it is every important that as data, information and knowledge are exchanged there is no loss of meaning. When that happens we say we have CLICK Semantic Interoperability or the ability to work together at the level of meaning.
- The ultimate goal of using standards is to achieve interoperability in health information systems. For logical implementation of health information systems with large scale integration in mind we need to think of a grand design or architecture so that the different components will come together in a seamless manner Like Plug and Play
- At the forefront of the work with implementing standards and interoperability in public health are people from the domain of public health informatics. Public health informatics is the systematic application of information and computer science and technology to public health practice, research and learning.
- In summary, these are the uses of Health information standards in public health We use them as building blocks We use them to make health information exchange more efficient They are the foundation upon which innovations in health IT are built
- Let us talk about data standards in public health.
- Let us talk about data standards in public health.
- Stakeholders - designers, developers, end users Requirements – discuss what is needed by HDHHS, BoE, and others Architecture – Software block diagrams Deliverables – Scope, resources, timeline Features – Portal benefits Delivery – Acceptance procedures, scope of delivery Maintenance – hosting, support, modifications,
- End users – Executive team needs summary and progress information, whereas others need domain specific information Data Team – Gathers user requirements, provides initial design, specs, estimates, project manage delivery and acceptance procedures Delivery Team – Based on spec from Data team prepares implementation specs, gets approval from data team, develops, delivers, and maintains the application.
- Web Portal - Will integrate existing apps and add new apps. Provides ability to input data from variety of users, controls access to domain-specific application functionality based on the nature of user and the group to which user belongs Provide customized information for analysis, interpretation, and dissemination Application monitoring - provides status of events, outbreaks in the community The application should have acceptable response time as judged by the end user and have reliable means of backing up and recovering critical data
- Develop HPHIN Portal http:// www.hphin.com Link existing HMMRS and RODS to the main portal Develop new web enabled applications for eHars and casefiles and link it to the portal Generate reports through Crystal Reports Manage Grants- status and progress of deliverables Leverage iWay to provide document uploading through various hospitals
- Add interoperability with CDC for Biosense and NEDSS Systems Web based Client - Server mechanism Use HL7 to process messages. No need to share sensitive patient data to CDC Allow CDC Server to poll our client and share information only on as needed basis Allow Hospitals, schools, and other to participate
- All apps will be 3-tier: Presentation, business logic, and data layer Host each tier on different servers – 3 nos. Group Internet enabled apps on one server behind firewall and Intranet enabled on another server in front of firewall Total duration - 12 months to deliver portal. Detail timeline will be provided shortly. Data Team will gather requirements, prepare software application design specs, project plans, estimates Delivery Team Resources: Programmers, web designer, DBA
- One Web console shows and tells all Main links: * Surveillance software * Grants – status and progress for grant deliverables with time lines, links to grant proposal documents, reports * Reports – BoE epidemiologists can set up various queries and search for information and generate custom reports Other users get hard coded reports * Tools - Contacts and calendar can be managed by creating forms through Web EOC. Documents can be uploaded to our Server from various hospitals via iWay * Notifications – Send automated emails to executive team/ supervisors/contact persons notifying critical information on events Software will use applicable security mechanisms
- Delivery team will provide timelines. Has to go through acceptance testing before delivery. Delivery includes all code in repository, all manuals in CD
- Delivery team is responsible for hosting the site 24x7 and providing customer support Daily telephone support during office hours Off-hour support will be through email, automated voice response systems Any enhancements will be routed through proper steering committee and delivery team will make necessary modifications. Bugs and problems will be routed through a trouble ticket procedure system.