Skip to main content

1+MG Reference Architecture

1+ Million Genomes (1+MG) initiative aims to enable secure access to genomics and the corresponding clinical data across Europe for better research, personalised healthcare and health policy making.

Start reading

Structure

This document provides a comprehensive view on the architecture of the 1+MG Network, following the guidelines of the arc42.org template. It is organized as follows:

  1. Introduction and goals: Short description of the requirements, driving forces, extract (or abstract) of requirements. and roles.
  2. Constraints: Anything that constrains teams in design and implementation decisions or decision about related processes.
  3. Context and scope: Delimits the system from its (external) communication partners (neighboring systems and users). Specifies the external interfaces.
  4. Solution Strategy: Summary and fundamental decisions or solution strategies that shape the architecture.
  5. Data Subject Onboarding: Detailed description of the architecture for Data Subject Onboarding.
  6. Data Provider Onboarding: Detailed description of the architecture for Data Provider Onboarding.
  7. Data Onboarding: Detailed description of the architecture processes for Data Onboarding, including building block, runtime, and deployment views.
  8. User Organisation Onboarding: Detailed description of the architecture for User Organisation Onboarding.
  9. Data Discovery: Detailed description of the architecture for Data Discovery.
  10. Access Request Submission: Detailed description of the architecture for Access Request Submission.
  11. Access Request Review: Detailed description of the architecture for Access Request Review.
  12. Data Use Agreement Signature: Detailed description of the architecture for Data Use Agreement Signature.
  13. Access Preparation: Detailed description of the architecture for Access Preparation.
  14. Data Provisioning: Detailed description of the architecture for Data Provisioning.
  15. Data Analysis: Detailed description of the architecture for Data Analysis.
  16. Output Review: Detailed description of the architecture for Output Review.
  17. Output Peer-review: Detailed description of the architecture for Output Peer-review.
  18. Project Archival: Detailed description of the architecture for Project Archival.
  19. Output Contesting: Detailed description of the architecture for Output Contesting.
  20. Extended Data Analysis: Detailed description of the architecture for Extended Data Analysis.
  21. Healthcare Contact: Detailed description of the architecture for Healthcare Contact.
  22. Clinical Trials Contact: Detailed description of the architecture for Clinical Trials Contact.
  23. Cross-cutting Concepts: Overall, principal regulations and solution approaches relevant in multiple parts (→ cross-cutting) of the system.
  24. Architectural Decisions: Important, expensive, critical, large scale or risky architecture decisions including rationales.
  25. Quality Requirements: Quality requirements as scenarios, with quality tree to provide high-level overview. The most important quality goals should have been described in section 1.2. (quality goals).
  26. Risk and Technical Debt: Known technical risks or technical debt. What potential problems exist within or around the system? What does the development team feel miserable about?
  27. Glossary: Important domain and technical terms that stakeholders use when discussing the system.