The Medical Data Manager (MDM) is an interface between DICOM compliant storage and the gLite middleware. It aims at (i) providing access to medical data sources for computing without interfering with clinical practice, (ii) ensuring transparency so that accessing medical data does not require any specific user intervention, and (iii) ensuring a high data protection level to preserve patients privacy.
This service is exploiting the DICOM standard for medical image transfers on the clinical side and the Storage Resource Management (SRM) on grids. It bridges these two standards by translating on the fly grid file read accesses into DICOM transactions. It benefits from the EGEE middleware capability to manage distributed files, thus enabling the federation of many DICOM servers geographically distributed and it provides a unified view of the data archived. It exploits state of the art encryption and fine grain ACL-based mechanisms to ensure both data protection and access control.
The video from EGEE User Forum 4 at Catania (March 3rd 2009) :
The MDM runs on top of the gLite middleware stack on Scientific Linux. After the installation, you have to configure the MDM.
The MDM used standard glite middleware. Hence, any gLite 3.1 User Interface can be used as a client. But the specific client is recommended: it provided an easy access to the medical data and metadata. The user may need to configure some files to access to all the components of the MDM. See client configuration for more information.
You should also look at the video that explain the MDM components (277MB) : http://proton.essi.fr/repository-mdm/documentation/external/video/presentation.dv
All the versions of the Medical Data Manager are available. But you should read the installation procedure before downloading the packages.
Two links among many others:
Medical data management working group
The EGEE-III project