1 / 23

PHINMS: Application Integration

PHINMS: Application Integration. Raja Kailar, Ph.D. Overview. PHINMS – brief overview and history Application Integration View Summary. What is PHINMS? (Business Perspective). Secure, reliable message transport Used by PH agencies to send data to CDC

casey
Download Presentation

PHINMS: Application Integration

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. PHINMS: Application Integration Raja Kailar, Ph.D.

  2. Overview • PHINMS – brief overview and history • Application Integration View • Summary

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

  4. PHINMS Usage

  5. What is PHINMS?(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. PHIN - Operational Environment

  7. State Private Key (Decrypt) State Public Key (Encrypt) HL7 HL7 DB Q DB Q PHINMS – Typical Message Flow State Lab Internet Proxy Server PHINMS Receiver PHINMS Sender DMZ Firewall Firewall

  8. Application Integration View

  9. Overview • Provide guidelines for business and technical decisions on messaging • Analyze application interfacing considerations • Explore ways to leverage messaging infrastructure to satisfy new data sharing needs

  10. Data Sharing Models

  11. To Message Or Not To Message? • When to message? • Periodic, un-attended data exchange • Data latency acceptable • When not to message? • Data latency not acceptable (synchronization needed) • Manual confirmation is necessary

  12. What Are Your Messaging Requirements? • Is there a need for automated B2B data sharing? • Is sensitive data being shared via the Internet? • Is guaranteed delivery of messages important? • Do you have a mix of small / large agencies (some with only “outbound” connections to Internet)?

  13. Is PHINMS the Right Tool For You? Requirement:Secure, Reliable Messaging over Internet

  14. PHINMS - Application Interfaces

  15. Sending Side - Interfacing Steps

  16. Sending Interface Considerations

  17. Receiving Interface Options

  18. Receiving Interface Considerations

  19. PHINMS - Messaging Models Peer-to-Peer (Direct-Send) Messaging Gateway (Route-not-Read)

  20. Leveraging Existing PHINMS For New Data Sharing

  21. PHINMS - Scaling Considerations

  22. Summary • Data sharing needs determine suitability of messaging, architecture and tools • PHINMS is a “pluggable” component that enables secure/reliable data sharing • Many public health organizations have PHINMS • Can leverage infrastructure for new data sharing • As usage goes up, need to scale up your infrastructure

  23. Questions?

More Related