Genome EDIC System Architecture
This is a working draft of the Genome EDIC system architecture taskforce. It is not an adopted document.
This site describes the IT system of the Genome EDIC: the European, national and User Organisation parts that together let people find, request and use genomic and related health data across borders.
It shows how the system implements the 1+MG Data Governance (the Genome EDIC Secondary Use Framework) and how it applies data protection by design and by default.
Start with your guide​
Pick the guide for your role. Each one lists the questions people in that role usually ask and links to the sections that answer them.
| I am… | Start here |
|---|---|
| A policy maker (e.g. a ministry backing the initiative) | Guide for policy makers |
| A legal expert | Guide for legal experts |
| An ELSI specialist | Guide for ELSI specialists |
| A security advisor | Guide for security advisors |
| A data protection officer | Guide for data protection officers |
| An implementer (architect, developer, operator) | Guide for implementers |
How this documentation is organised​
It follows the arc42 template, with twelve chapters. arc42 was created by Gernot Starke and Peter Hruschka, and its structure is used and adapted here under the CC BY-SA 4.0 licence. The page recipes list where we depart from it. Three rules make it easier to navigate:
- Three scopes. The system has a European scope (what the Genome EDIC is responsible for), a national scope (what each Member Country is responsible for: its 1+MG NCP, 1+MG Data Holders, 1+MG Data Providers and 1+MG Data Hosts) and a User Organisation scope (the User Organisation and its Users). Chapter 5 is split by scope; chapter 7 by where things run (central, national, local). See 3.3 Scopes.
- Runtime follows the governance. Chapter 6 walks through the data lifecycle in the same order as the governance: data inclusion, data access, data use.
- Every page shows its governance links. The box at the top of each page lists the governance sections it implements. The governance traceability page shows the reverse view: for every governance section, the pages that implement it, and the gaps.
Each page also shows who owns it, who reviews it, and its status. See document status.