5. MM2 Early Prototype

The Architecture described in this document considers the requirements for the whole EUCAIM infrastructure, and it is expected that the components, user stories and requirements will be updated along the project.

EUCAIM has an early Milestone (MM2 - Early prototype) which will demonstrate a basic functionality of the platform. This section describes the functionality for each one of the components.

5.1. Demonstration Storyboard

A user accesses the Dashboard and interests to request data. She accesses the federated catalogue which contains data from collections in several repositories. She clicks on the collections and retrieves their metadata. Then she registers in EUCAIM using the Life Sciences Login and performs a federated search on data collections from prostate cancer with MRI data, retrieving the number of cases per collection that matches the request. Then she requests access to the collections and provides a project, the ethical approval and a specification of resources requested. Once the proposal is accepted, the researcher gets access to the processing service, in which she runs a basic processing that computes the average and standard deviation of the noise/signal ratio of the images, using the python program in appendix A.

5.2. AAI

The expected functionality will cover the following Platform Use Cases:

• Register through the Life Sciences (LS) AAI.

• Assign Permissions in the LS AAI to the registered users.

• Use the LS AAI to authenticate users in the Dashboard.

5.3. Public Catalogue

The expected functionality will cover the following Platform Use Cases:

• Register the metadata of a collection in the Federated Catalogue.

• Browse the collections available in the Federated Catalogue.

• Filter collections according to criteria in the metadata.

• Add a collection to Mylibrary.

• Remove a collection from Mylibrary.

• Request access to a collection.

• Browse the collections for which the user has access to.

At least four providers will be linked: CHAIMELEON.

5.4. Federated Query

The expected functionality will cover the following Platform Use Cases:

• Search for the images in the collections of the federated catalogue according to the following criteria: age, sex, image modality and cancer type.

• Query will be expressed in a structured language.

• The query will be run through the mediator on the different providers.

• The providers will return the number of studies that match the searching criteria.

At least two providers will support the federated query.

5.5. Access Negotiation

The expected functionality will cover the following Platform Use Cases:

• Request access to a collection, providing a project plan, ethical approval and institutional authorisation.

• Forward the request to the evaluation committee.

• Follow-on the status of the application.

• Interact with the applicant.

5.6. Federated Processing

The expected functionality will cover the following Platform Use Cases:

• Define the job parameters: container application, site, data indexes, arguments.

• Run a distributed job on a provider of the federation.

• Monitor the progress of a job.

• Cancel a job.

• Retrieve the results of the execution.

5.7. Central Repository

The expected functionality will cover the following Platform Use Cases:

• Create a project/community in the repository.

• Upload Medical Imaging Data in the repository.

• Upload clinical data related to the medical imaging studies.

• Manage collections (create, update, invalidate).

5.8. Dashboard

The Dashboard will include:

• Landing page and instructions page for data requesters, data providers and tool providers.

• User registration, log in and log out.

• Federated Catalogue.

• Data request.

• Data access.

• Basic Federated Processing.