1 / 24

The Washington Conversation

The Washington Conversation. Communication with the Ecology Node to Support for a Healthier Washington State. Washington Department of Health. Environmental Integration and Exposure Impact Observation System (EIEIO)

josiah-evans
Download Presentation

The Washington Conversation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Washington Conversation Communication with the Ecology Node to Support for a Healthier Washington State

  2. Washington Department of Health Environmental Integration and Exposure Impact Observation System (EIEIO) W-EPHTN has developed a computer application to access fish contamination data from the  Department of Ecology to provide advice for the public on how to choose fish that are low in contaminants. This effort is a model of how to tap in to environmental data using the National Environmental Information Exchange Network which has been implemented by Ecology. W-EPHTN is the Washington – Environmental Public Health tracking Network http://www.doh.wa.gov/EHP/ephtn/W-EPHTN_in_Action.htm

  3. Problem Description: Silos do not communicate with each other. How do we share the data we have? ? Dept of Health Data and Application Dept of Ecology EIM Database

  4. Solution #1 – SneakerNet Devise some method to move data once in a while from one to another.

  5. Solution #2 – Build a ‘bridge’. Hard-wired application interface where I read your data. Works but there are a few problems with this as a generic approach.

  6. Solution #3 – Build a ‘Super Silo’ Build one monster system that does it all and eliminates the need for sharing of data.

  7. Solution #4 – Thinking really out of the box. NOT!

  8. The Solution – An Application Level Node Flow! Build a Department of Health application that will invoke the Dept of Ecology Node and request data.

  9. What are the advantages to a Node Solution? • You do not have to rely on manual processes. It can be full automated. • You did not have to invest and build a ‘one time’ solution for every interface into your data system. • You can supply service on demand, 24X7X365 • You have a secure interface. NAAS as well as what level(s) of security the flow includes.

  10. Advantages (cont) • You build only the technology you need to serve the data. You do not have to build an entire bridge. • You do not have to re-engineer your technical architecture nor you data architecture. • Using a standard XML Schema you know what data to supply and what data you get.

  11. Any Disadvantages? • You do not get to visit folks at the other office when you carry over the files. • You might get rusty on you FTP skills. • You might have to clean up your data since it will be used more. • In reality there is little downside.

  12. What we did to make this work. • Analyze the PNW Flow. • Plug-in based architecture • Flow was based on Water Quality Data • Copied the node plugin and modified it for the project. • Created a couple of new database tables and stored procedures. • Started the Testing process.

  13. What we did (cont). • We installed the prototype in the development environment. • Worked with DOH to initiate the flow. • When DOH saw what they were getting, they wanted more, so we added the requested data to the flow. • Installed and are running.

  14. DOH EIEIO Application Fish Tissue Contamination and Birth Defects Assessment Application Linking Environmental Monitoring & Human Health Data Leveraging information published for multiple purposes How does WA DOH access and use WA DOE data?

  15. DOH EIEIO – Step 1 – Query Results List of Studies/Projects

  16. DOH EIEIO – Step 2 – Query Results List of Results

  17. DOH EIEIO – Step 3 – Query Results Date Range, Location, Taxon, Analyte

  18. What have we done in establishing this application to node communication? • Proved a secure service on demand. • Insure that the service supports loose coupling for diverse software agents • Supplied a prescribed piece of work • Provided the user a response to the request in a non-proprietary data string.

  19. So where does that leave us now?

  20. The node using this architecture can serve data to any authorized requestor from any location.

More Related