PHIN Communication and Alerting (PCA) PHIN Exchange

1. PHIN Communication and Alerting (PCA)PHIN Exchange January 20, 2010 The findings and conclusions in this presentation are those of the authors and do not necessarily represent the views of the Centers for Disease Control and Prevention/the Agency for Toxic Substances and Disease Registry.

2. Agenda • What is the new PHIN Exchange? • What is the Cascade Exchange? • What are the next steps?

3. What is the new PHIN Exchange? • PHIN Exchange is a new secure SOAP web service hosted by CDC’s Secure Data Network. • PHIN Exchange replaces PHINMS and Cascade Lite for small payloads (only Cascade Alerting and Directory Exchange initially). • PHIN Exchange consist of the following services: • Cascade Exchange - A hosted version of Cascade Lite; • Cascade Mapper - Create and validate EDXL/CAP payload files; • File Exchange – Supports exchange of payload files; Supports PCA EDXL/CAP XML files; Directory Exchange and other attachments.

4. What is the new PHIN Exchange? • PHIN Exchange provides message exchange between partners with • No local installation – Zero-Footprint; • No open firewall ports required, each node “pulls” or “pushes” message; • Encryption of messages during transport; • Authentication using SDN Digital Certificates; • Routing of messages to multiple partners. • Central management of Routing information.

5. Compare PHINMS to PHIN Exchange Secure and Encrypted Payloads PHINMS and Cascade Lite must be installed locally Each PHINMS instance must be configured to each new cascading partner. Significant support required to implement and support each new PHINMS instance. More appropriate for large payloads of surveillance and reportable diseases. Will migrate to Web Services model in the future. PHINMS PHIN Exchange • Secure and Encrypted Payloads • PHIN Exchange requires no local install (“Zero Foot Print”). • Configuration and Routing information centralized – no partner configuration • Support can focus on implementing web service interface vs. PHINMS setup • Best for small payloads and strongly typed interfaces such as Cascade Exchange • Secure Web Services are the Industry and HIE standard.

6. The PHINMS Model

7. The PHIN Exchange Model Zero Foot Print Centralized Exchange

8. What is the Cascade Exchange? • Implementation of “Cascade Lite” as a CDC hosted web service on the PHIN Exchange. • Cascade Exchange handles all XML marshalling • Strongly typed interface for direct integration with partner alerting applications. • Developed in Java; fully supports .NET • Runs on open source J2EE application server (JBoss) • Standardized interface (WSDL) for commercial alerting vendors

9. What Next? Visit the PCA Wiki at http://www.atl.ciber.com/pca/index.php/Ce:overview The first thing to do is go to the Engagement Planning page to understand the engagement process for integration, testing, and certification of your cascade alerting implementation. You can start coding your application to integrate with Cascade Exchange today. A development instance of Cascade Exchange is available on the internet to begin your coding efforts while the CDC environment is being configured for certification and production. Visit the PHIN Exchange Developer Guide guidelines and examples for interfacing with the Cascade Exchange. The Cascade Exchange Service specification provides detail information about each Cascade Exchange web service method and the Cascade Distribution data model. The Cascade Mapper Service specification provides detail information about each Cascade Mapper web service method.