1. WP 10 ATF meeting April 8, 2002 Data Management and security requirements of biomedical applications Johan Montagnat - WP10

2. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Data u Public biological data n Genomics databases such as SwissProt, TrEMBL, yeast genome…, usually available through web portals u private biological data n Databases owned by private companies, usually disconnected from the outside world. In a grid context they should not be accessible to any system administrator. u Medical data n Every data is protected. Nominative data are only accessible to a very limited number of persons. Images contain both nominative and anonymous data. u No well established standard format / no standard data structure n flat files for biological data n DICOM3 for medical images

3. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Users u Public n Anybody an access public databases in read-only mode. u Owners n A limited number of users can modify/update data. u Patients (individuals) n A patient has free access to its medical data. u Physicians (groups) n A physician has complete read access to its patients data. Few persons have read/write access. u Researchers (groups) n Researcher may obtain read access to anonymous medical data for research purposes. Nominative data should be blanked before transmission to these users.

4. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Data management requirements u Data requirements n Very large databases (Tb/database) n Long term storage u Biological data n Frequent data updates n Data indexing (c.f. BLAST) n versioning (CVS-like) mechanism needed to restore older data version u Medical data n Metadata storage (information on patient, acquisition type, medical file…) n Access right on a medical department (group) basis n Read-only access to raw scanner data, R/W to processed data n Record data processing

5. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Use cases u Web portal access to public data n e.g. NPS@ web portal u Private access to public biological data n A private database is compared against a public database. The kind of research should not be known from the outside. u Private biological data n data are only available from, and can only be replicated to, an limited number of resources u Queries on medical databases n A physician retrieves all images from a patient n A researcher assess an algorithm on a dataset obtained by querying the data storage system on non nominative metadata

6. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Use cases u Delegation of credential n A physician needs the expert advise of a colleague. He grants access to some image. He could not have grant access to a non accredited user. u Patient access to its data n A patient can query its data, meaning that he can query a database on nominative data, only for data he owns.

7. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Security requirements u Security is a central issue for a large scale deployment of WP10 applications n sensitive data should not be accessible by third parties (encryption is one mean). u Data access security n Read-only access for most users n No read access to private data by any third party user (including system administrators) n The replication mechanism should not make replicated data more accessible than masters n Quoting D7.5: “it should be difficult for someone to make sensitive data accessible to non accredited users” n Sensitive data should not be accessible while being transmitted over the network (secured/encrypted protocols needed)

8. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Security requirements u Biological data security issues n An explicit control of sites where private data may be replicated should be possible n A third party should not be able to know what is done with the data (impossible to log other users jobs on the grid) u Medical data security issues n Image nominative metadata should be stored in secured/trusted databases n Nominative metadata should be encrypted when transmitted over the network n Images should not be replicated outside hospital without blanking headers n It should be possible for an accredited user to delegate access right for some data to another accredited user.

9. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Raid 5 Client DICOM Server DICOM DICOM jE cache Hospital Meta Data jE jE: an interface to medical data servers

10. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Foreseen medical data infrastructure u Split nominative and anonymous data to allow data replication on unsecured sites. Untrusted data servers with blanked images jE Authentication and Authorization Metadata interface SE-DICOM interface Confidential data Non-confidential data Header blanking hospital SE DICOM Server SE European DataGrid

11. qmsg/shm LAN WAN SE Interface jE/SE Interface hdS jE User Interface jE Dicon Client jE Dicon Server spitfire security (GSI) jE Cache hdS OK phase 1 phase 2 jE Spitfire Int ATF April 8, 2002, H. Duque, WP10 Detailed jE architecture

12. ATF April 8, 2002, H. Duque, WP10 TCP / IP hdS dicom Srv jEdi spitfire jE hdS Daemons ( metadata; jE; images ) jEspi jEcache http http/xml jEus.php TCP / IP SE jEse image Srv jE communication layer

13. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Questions to WP2 u How to interface the jE with Spitfire ? n jwget is a command line tool... n Should we wait for an API ? n Should we use direct XSQL queries through HTTP ? n Which port? u We need a jE User Interface (to query both local and remote Spitfire databases). What protocol should we use? n Http via tomcat server? s Could Spitfire tomcat server be reused? n Are there any plan to distribute spitfire? n Should we use our own protocol? u Should a jE manage its own RC to make its medical files visible to the outside world?

14. ATF April 8, 2002, H. Duque, WP10 jE/SE interaction

15. WP 10 ATF April 8, 2002, J. Montagnat, WP10 Questions to WP5 u How to interface a jE as an SE? n Should we consider the jE as a MSS? n What is the SE interface? n What is a SE? u Which API should use the SE client? n RB, RM, JSS, IS, communicate with SEs... n Will there be a user application API? n Will jE be considered like a user application?