The Public Health Information Network Messaging System

Size: px

Start display at page:

Download "The Public Health Information Network Messaging System"

Kathlyn Ferguson
10 years ago
Views:

1 The Public Health Information Network Messaging System Tim Morris Director, Division of Informatics Shared Services (DISS) National Center for Public Health Informatics (NCPHI) Centers for Disease Control and Prevention (CDC)

Services (DISS) National Center for Public Health

2 Overview PHIN Messaging System Secure and Reliable Messaging Overview Direct-Send vs. Route-not-Read

3 Mission To support applications sending public health data across the PHIN network which help accomplish CDC s mission: Preventing & controlling disease Preparedness & emergency response By providing these applications a common platform for secure message transport that is: Secure, reliable, easy to use, easy to support Well performing, feature-rich De-facto standard for secure message transport Available at no cost to users

applications a common platform for secure message transport that is: Secure, reliable, easy to use, easy

4 What is? (Business Perspective) Secure, reliable message transport Used by PH agencies to send data to CDC Applications using include: BioSense, ELR, LRN, NBS, HCN, NND, NHSN Some states using internally: NYS, NYC, MN, OK, CA 4-year old product deemed mission critical by CDC

5 What is? (Technical Perspective) CDC s implementation of the ebxml 2.0 messaging standards Runs on Windows, Linux, Solaris (platform independent) Can be used by any application that can write and read database tables (language independent)

6 Usage Increase in Messages ~800,000 Increase in Senders ~ , , (est.) (est.)

7 Roadmap Version 2.1: Core Transport System (June 03) Version 2.5: Deployment engine (Tomcat), Graphical configuration, chunking (May 05) Version 2.6: Upgrade wizard, enhanced feature set (Feb 06) Version 2.7: Transport Folder polling, Auto upon fatal sender error, Registry lookup (Fall 06)

Version 2.6: Upgrade wizard, enhanced feature set (Feb 06) Version 2.

8 What is ebxml? ( ebxml Messaging Service is a robust messaging framework for commerce Can send all types of files, not just XML HL7 has proposed an ebxml DSTU (Draft Standard for Trial Use) as a transport mechanism for all HL7 messages.

org) ebxml Messaging Service is a robust messaging framework

9 PHIN - Operational Environment PHIN Node (CDC) Data PHIN Node (State) PHIN Node (Lab) Data Data

10 Placement within PHIN Application Data Component Application Data Component Message Transformation Component (Creation) Message Transformation Component (Parsing)

11 Architecture Other Sites, Systems ebxml, XMLDSIG, XMLENC, LDAP, X.509 PHIN MS Q U E U E S Apps Platform Neutral

12 Business/Electronic Agreements, Trust, CPAs State Lab Client Server Hospital System Client State HD Client Server National Labs Client CDC Client Server

13 Message Flow LDAP CDC HL7 Lab CDC Public Key (Encrypt) CDC Private Key (Decrypt) Internet HL7 DB Q Sender Proxy Server DMZ Receiver DB Q Firewall Firewall

14 Message Routing Message Sending Application Service=X Action=Y Application In-Queue A Message Receiving Application A Out-Queue Sender Route Message (Service=X, Action=Y) Receiver Service=P Action=Q Application In-Queue B Message Receiving Application B Service=M Action=N Application In-Queue C Message Receiving Application C

(Service=X, Action=Y) Receiver Service=P Action=Q Application In-Queue B Message

15 Reliable Messaging Transport Queue Sender Receiver Once and Only Once Delivery Worker Queue Connection Retries Data Submit Retries Delayed Retries Duplicate Message Detection Persistent Cache

16 Message Chunking Message Size limit <= 10Mb Sender can be configured to send larger files in chunks Chunking is transparent to sending and receiving applications With chunking, tested up to a 4 Gb file

Chunking is transparent to sending and receiving

17 Two Ways of Sending Data Direct- Send Point to point transmission, no intermediary Adv: very reliable, no single point of failure Disadv: higher deployment + maint costs Route-Not-Read Intermediary holds message w/o reading Adv: lower deployment + maint costs Disadv: single point of failure

higher deployment + maint costs Route-Not-Read Intermediary holds

18 What is Direct-Send? Node A (Sender) Encrypt, Send Node B (Receiver) Receive, Decrypt Impact on Deployment - At message sending end - minor - At message receiving end - major

19 What is Route-not-Read? Intermediate Node C (Receiver) Store/ Retrieve Encrypt, Send Poll Receive, Decrypt Node A (Sender) Node B (Sender)

20 Why is Direct-Send Better? Route-not-Read Direct-Send

21 and Tracking Network Many public health departments using currently Transport of notifiable disease case messages sent to CDC via Secure point to point messaging Tracking Network use depends on requirements Tracking network may require some grid query and some point to point Could use for some data flows

22 and Tracking Network Public Health Department CDX Node Client Local EPD Health Data Source CDX Node Aggregate data analysis

23 Questions?

Secure, Reliable Messaging Comparisons between PHINMS, SFTP, and SSH. Public Health Information Network Messaging System (PHINMS)

Secure, Reliable Messaging Comparisons between PHINMS, SFTP, and SSH Public Health Information Network Messaging System (PHINMS) Version: 1.0 Prepared by: U.S. Department of Health & Human Services Date: