What is PHINMS? Secure and reliable transport for any data type. (HL7, xml, bmp, jpg, zip, etc.) 30+ Applications using PHINMS. Examples: BioSense, Cancer, NEDSS, LRN, FoodNet, PHLIP, etc. Labs using PHINMS: Labcorp, Mayo, Bostwick, etc. States using PHINMS internally: NYS, NYC, MN, OK, CA, SC, WI, FL, IN, AL, etc. 7-year old product deemed “mission critical” by CDC. Over 500 PHINMS nodes used in U.S.
PHINMS Roadmap Version 2.1 (2003) Core Transport System developed Version 2.5 (2005) Added User Interface Version 2.6 (2006) Improved UI and Performance, Load Balancing Version 2.7 (2007) Folder Polling, Alerts, Configuration Wizards Version 2.8 (2008) New UI for improved usability. Support for multiple database queues. Version SP1 (Fall 2010) Support for Windows 7 and 2008 Minor enhancements and defect fixes Updated Tomcat engine
Central Auth Route-not-Read Direct-Send RNR and Direct Send
VeriSign Direct Send LabDOH Proxy Server PHINMS Receiver Internet DB Q PHINMS Sender Firewall HL7 DMZ Pub Key Firewall Private Key
Direct Send To CDC
LabDOH PHINMS Poller Internet DB Q PHINMS Sender Firewall Prvt Key CDC DMZ Auth / Firewall Route Not Read
FeatureDirect-SendRoute-not-Read ScalabilityUnlimitedLimited Standards ComplianceComplies with ebXML2.0PHINMS specific extensions to ebXML 2.0 ReliabilityHigh – provides end-to-end transport status Medium – provides link-level (not end-to-end) transport status Single point of failureNoneYes Liability for Intermediary Organization (R-N-R Hub) LowHigh Privacy for Messaging Nodes HigherLower Deployment CostHigh (almost 5 times that of route-not-read) Low Infrastructure NeedsHighLow Dynamic CollaborationHarder, since peer-to-peer collaborations needed Easier, since all parties talk via a single central hub
NHIN CONNECT is data exchange… … and a whole lot more. Patients can query their own health records from NHIN Hospitals can query patient data from other orgs to increase quality of care. Docs can query EHR data for an unconscious individual in the ER to determine best method of care. Agencies and Labs can “ publish/subscribe to ” data that can be queried for real-time data sharing. What is NHIN CONNECT?
The CDC NHIN Implementation is currently restricted to specific functionalities designed to meet push based data exchange models. The CDC NHIN Team is working to extend the NHIN C&A to include full NHIN functionality. CDC & NHIN CONNECT
NHIN CONNECT
Gautam Kesarinath – CDC Business Steward Andreea Bealle – Project Manager Travis Mayo – Tech Lead Dawn Fama – Deployment Lead Tavan Jones – Operations Lead PHINMS Team Information Support: Project: