- Introduction
- Historical System Approach
- Need for Services
- CDC approach
- Partner approach
- Funding tsunami for NHIN implementation (everybody on it by 2015?)
- Goal - coherent service runtime strategy for use by CDC/NCPHI/Partners as extension to NHIN (phCONNECT)
- Existing CDC efforts
- PHGrid - Globus/Tomcat
- Cardea - Whatever/Glassfish
- PHIN-SRM / PHINMS - Glassfish/Globus
- PHINVADS/PHINDir - WebLogic/Probably Glassfish
- .Net stuff (don't know much about this)
- Public Health Scenario - GIPSE used for Biosurveillance post-PHIN future
- HIEs collect event data from health care provider using Cardea
- HIEs transmit scheduled GIPSE extract objects to collector node using PHIN-SRM through NHIN Connect
- Collector node provides access to summary data using Grid Publisher
- Remote analysis is performed using distributed GIPSE query based on Service Registry
- Aggregate analysis is visualized using GIPSE module Grid Viewer / RODS / ESSENCE
- Parallel Government efforts
- NHIN CONNECT- Glassfish
- HealthGrid - Globus/Tomcat
- EPA ExchangeNetwork- Open (.Net/WebSphere/WebLogic/Tomcat/JBoss/others)
- caBIG - Globus/Tomcat
- NBIS - Network of networks (no specific container)
- Long-term vision for Population extension (phCONNECT)
- Population services for public health (GIPSE, PHR, GIS, TheFuture)
- Installable package for NHIN nodes/partners to provide & access population services
- Integration of public health into clinical processes & vice versa through NHIN
- Transition existing SOA-based services to consolidated technology runtime 100% compatible with expected NHIN connect installations over next 6 years
- What service engine to use? (maybe scrap this and keep 1-5_
- Glassfish
- pros:
- There will be familiarity based on CONNECT installs at each Federal agency
- Perceived requirement (that agency services must run inside same physical process as CONNECT gateway/adapter)
- cons:
- No grid services (must be built by PH community)
- No user/role security (yet)
- Tomcat/Globus
- pros:
- International community
- grid services
- strong security implementation
- tools
- cons:
- Tomcat only (from community)
- Glassfish/Globus
- pros
- Runs in Glassfish
- cons
- Doesn't exist yet, functionality must be build
- Something else