1 Health-e-Child project Konstantin Skaburskas CERN IT/GD University of Tartu, Estonia 16 March 2007, CERN 2 Establish Horizontal and Vertical integration of data, information and knowledge Develop a Grid-based biomedical information platform, supported by sophisticated and robust search, optimisation, and matching techniques for heterogeneous information, Build enabling tools and services that improve the quality of care and reduce its cost by increasing efficiency Integrated disease models exploiting all available information levels Database-guided decision support systems Large-scale, cross-modality information fusion and data mining for knowledge discovery Knowledge RepositoryPaediatrics A Knowledge Repository for Paediatrics Project Objectives 3 Instrument:Integrated Project (IP) of the Framework Program FP6 Project Identifier:IST Coordinator:Siemens AG, Dr. Jrg Freund Partner:14 European (companies, hospitals, institutions) Timetable: 01-Jan-06 to 31-Dec-09 (4 years) Total cost: 16.7 Mio. EC funding: 12.2 Mio. Web page:http://www.Health-e-Child.org Project General Info 4 Project Map GOSH NECKER UWE CERN IGG SIEMENS ASPER UOA INRIA LYNKEUS UCL EGF FGG MAAT R&D site hospital Clinical Institutions GOSH - University College London, Great Ormond Street Childrens Hospital, London, UK NECKER - Assistance Publique Hopitaux de Paris, Paris, France IGG - I.R.C.C.S. Giannina Gaslini, Genoa, Italy 5 A1: Project Management WP1 Project management A2: User Requirements Specifications WP2 User requirements specifications A3: Ethical, Legal and Social Issues WP3 Legal, ethical, and regulatory issues WP4 Privacy and security A4: Platform Development, Vertical Data Integration and Knowledge Representation WP5 Grid platform (Maat, CERN, UWE, Siemens) WP6 Medical vertical knowledge representation WP7 Data management layer and data integration mechanisms WP8 Medical query processing A5: Data Collection, Annotation and Knowledge Gathering WP9 Data collection WP10 Ground truth (annotated data) and clinical knowledge gathering A6: Disease Modelling, Decision Support and Knowledge Discovery based on Integrated Biomedical Information WP11 Integrated disease modelling WP12 Decision support systems WP13 Biomedical knowledge discovery A7: System Integration WP14 Deployment of the data management system and Grid gateway (Maat, CERN, UWE, Siemens) A8: Dissemination Policy and Broader Impact WP15 Training WP16 Dissemination Activities and Work Packages 6 Grid platform (Maat, CERN, UWE, Siemens) Provide gLite-based infrastructure for HeC developments, integration and testing training for Gateway and client application developers in the use of gLite services Develop grid interface(s) to gLite services for the HeC Gateway components and client applications HeC Infrastructure related work Deploy the HeC Platform (at medical and non-medical institutions that make up the end-user community) EGEE gLite middleware, HeC Gateway, HeC Client apps. Ensure stable and secure production environment for the clinical users automated Platform administration controllable upgrades/(re-)config. Provide feedback to the HeC Platform developers Integrate client applications and ensure they can interact with/use the underlying components appropriately Deployment of HeC Platform (Maat, CERN, UWE, Siemens) HeC Platform 7 Cardiology Rheumatology NeuroOncology Knowledge Discovery Decision Support Systems Disease Models Health-e-Child Gateway Ontological Layer Query Processing Data Management Grid Middleware IGGNeckerGOSH Common Client Applications HeC System Overview 8 Security - Interconnecting Hospitals through the Internet - Providing Services & Data Online Usability - End-users: Clinicians - Providing a rapid and efficient access to the Platform Privacy - Connecting a Research Platform to Hospitals Information Systems - Manipulating Patient Data Distribution, Scalability - Coping with geographically distributed sites across Europe (France, UK, Italy) - Building a scalable system for a future expansion Heterogeneity - Dealing with several imaging devices, technologies, protocols, data, environments Challenge Problem Description 9 HeC Approach Workstation Gateway User Hospital X One Access Point Per Institution One Key To enter the system 10 HeC Approach Workstation Gateway User Hospital X One Access Point Per Institution 11 Platform & Grid Middleware The Health-e-Child Access Point One Access Point Hosting Domain 1 Stable & Secure Environment Hosting Domain 2 Stable & Secure Environment Security & Registration Job Managnt HeC Gateway Storage HeCScheduling Monitoring Info System Computation Unit Data Unit HeCDBMS 200GB50GB1TB Health-e-Child EGEE gLite HeC Gateway Virtualization (current approach - Xen) 12 The Platform The Health-e-Child Gateway (1) Inside the box Client Applications One Access Point HeC Gateway Computing Resources Functionality Access Infrastructure Abstraction 13 The Platform The Health-e-Child Gateway (2) Security Services gLite API Ongoing Client Applications One Access Point HeC Gateway GT4* OGSA-DAI* Portal Service & Factory Data Integration Grid Abstraction DB Abstraction Ongoing - GT4: Globus Toolkit 4 (WSRF Container) - OGSA-DAI: Data Access & Integration gLite Infra Knowledge Repository Hospitals IS Inside the box Current Prototype & Investigation 14 HeC Approach Workstation Gateway User Hospital X One Key To enter the system 15 Entering the Platform User Authentication HeC GatewayGrid Services HeC Access Point Authentication Factory Authentication 2. Authentication request Resource 3. Instantiates VOMS 1. Generate Grid Proxy 4. Returns Endpoint 5. Authentication Part1 6. PIN Code Request 7. Authentication Part2 8. VOMS Request 9. Check VO membership 10. Returns VOMS blob 11. Store Proxy 12. Authentication OK Client Workstation HEARTBEATS Note: - Tunnels: HTTPS + GSI Secure Conversation - Heartbeat = resource & proxy lifetime extension 16 Platform Connectivity Client Application - User Session HeC GatewayGrid Services Authentication Portal 3. IP Check Client Workstation HEARTBEATS Portal Factory Resource 2. Instantiates 1. Portal Request 4. Returns Endpoint 5. Portal Call HEARTBEATS VOMS LFC SE CE Note: - Tunnels: HTTPS + GSI Secure Conversation - Heartbeat = resource lifetime extension HeC Access Point 17 Common Development Environment CDE HeC Platform Software Process PDI Platform Development & Integration HeC Gateway Development, Integration & Early Testing PP Pre-Production Client Applications Development & Integration Environment HeC Gateway Final Testing, before Deployment in Production PROD Production Stable environment for end-users Mainly Clinical Institutions Beta releases Stable releases Feedback 18 Current status Beta releases Stable releases Feedback Development Environment Subversion (SSL-enabled + ACLs); Bugzilla; HeC technical Web server HeC CA OpenCA HeC VO gLite VOMS HeC PDI gLite-based test-bed HeC PP deployments at Siemens 19 Test-bed Grid Platform Virtualization applied Being deployed 20 Common Development EnvironmentMar 2006 Common Development EnvironmentMar 2006 Certificate AuthorityApril 2006 Certificate Authority in placeApril 2006 GridInfrastructureoperationalMay 2006 Grid Infrastructure is operationalMay 2006 gLite Interface already half the way Security Client & ServicesJun 2006 Security Client & Services availableJun 2006 P2P3 Prototype demo Feb 2007 P2P3 Prototype demo Feb 2007 GatewayPrototype demo Dec 2006 Gateway Prototype is on its waydemo Dec 2006 demo Jan 2007 Client Base availableFeb 2007 Client Base availableFeb 2007 get practical hands-on! Beyond demonstration purposes, it allows us to get practical hands-on! production deployments and more ambitious functionality! We are now ready to proceed with production deployments and more ambitious functionality! SecurityPrivacy HeterDistribUsability Conclusion 21 THANK YOU FOR YOUR ATTENTION 22 Future Work Decentralized Architecture Grid Platform Working out a possible alternatives to decentralize key components of the grid middleware Autonomous Sites 23 Future Work Opening the Platform to External Institutions Where modularity & scalability play their role