GoldenOutline

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

Page updated

Google Sites

Report abuse