Skip to main content

Writing order

Pages are written in six waves. Each wave builds on the words and decisions of the waves before it, so that we don't write the same thing twice or contradict ourselves.

Rules​

  1. A wave can start when the pages of the waves it depends on are at least in review. It doesn't need to wait for their approval. If a later page shows that an earlier one is wrong, open an issue for the earlier page. Don't work around it silently.
  2. Inside a wave, pages are independent and can be written in parallel. Wave 4 is the largest (about 30 pages). The European, national and User Organisation scope teams work on it at the same time.
  3. ADRs are written whenever a decision is taken, in any wave. Chapter 9 is never "finished".
  4. The architecture lead can move a page to another wave. Change wave in its front matter and explain why in the page's issue.

Why this order​

  • Wave 1 fixes the vocabulary and the boundaries. Every other page talks about scopes and actors. If 3.3 and 3.1 are unclear, every page after them will be unclear too.
  • Wave 2 fixes the direction. The legal constraints, the solution strategy and the controller/processor map (8.2) decide what is allowed. Data protection by design and default (8.1) comes this early because it shapes every component and scenario.
  • Wave 3 draws the outline that wave 4 fills in.
  • Wave 4 describes behaviour and components together. A scenario in chapter 6 and the components it uses in chapter 5 inform each other, so their owners should talk.
  • Wave 5 details the concepts that waves 3 and 4 have already referenced. This avoids writing abstract concepts nobody uses.
  • Wave 6 consolidates: deployment, measurable quality scenarios, risks, and a final check that every question in the reader guides has an answer.

Progress per wave​

Generated from the wave and status fields of each page.

Wave 1 — Frame

Agree on the words and the boundaries: scopes, actors, governance principles, glossary.

Approved 0 In review 0 of 6 pages

PageStatusOwnerReviewers
1.3 StakeholdersPlaceholderunassignedunassigned
2.2 Governance principlesPlaceholderunassignedunassigned
3.1 Business contextPlaceholderunassignedunassigned
3.3 European, national and User Organisation scopesPlaceholderunassignedunassigned
ADR-0002 Who decides on access, per type of datasetDraft@brunopacheco1unassigned
12. GlossaryDraftunassignedunassigned

Wave 2 — Direction and legal frame

Say what the system must achieve, under which laws, with which fundamental choices, and who is controller or processor. Starts when wave 1 pages are at least in review.

Approved 0 In review 0 of 10 pages

PageStatusOwnerReviewers
1. Introduction and goalsPlaceholderunassignedunassigned
1.2 Quality goalsPlaceholderunassignedunassigned
1.1 Requirements overviewPlaceholderunassignedunassigned
2.1 Legal and regulatory constraintsPlaceholderunassignedunassigned
2.3 Organisational constraintsPlaceholderunassignedunassigned
4. Solution strategyPlaceholderunassignedunassigned
8.1 Data protection by design and by defaultPlaceholderunassignedunassigned
8.12 Types of datasetDraft@brunopacheco1unassigned
8.2 Controllers, processors and responsibilitiesPlaceholderunassignedunassigned
ADR-0001 Record architecture decisionsDraftunassignedunassigned

Wave 3 — Structure

Draw the outline: technical context, technical constraints, level-1 building blocks and the scope overviews. Starts when wave 1 and 2 pages are at least in review.

Approved 0 In review 0 of 9 pages

PageStatusOwnerReviewers
2. ConstraintsPlaceholderunassignedunassigned
2.4 Technical constraintsPlaceholderunassignedunassigned
3. Context and scopePlaceholderunassignedunassigned
3.2 Technical contextPlaceholderunassignedunassigned
5.1 European scopePlaceholderunassignedunassigned
5. Building block view (level 1)Placeholderunassignedunassigned
5.2 National scopePlaceholderunassignedunassigned
5.3 User Organisation scopePlaceholderunassignedunassigned
9. Architecture decisionsPlaceholderunassignedunassigned

Wave 4 — Behaviour and components

Describe each lifecycle scenario and each level-2 building block. Scope teams work in parallel. Starts when wave 3 pages are at least in review.

Approved 0 In review 0 of 31 pages

PageStatusOwnerReviewers
5.1.2 Access request management and 1+MG DAC supportPlaceholderunassignedunassigned
5.1.5 Connection to HealthData@EUPlaceholderunassignedunassigned
5.1.4 Transparency and reporting servicesPlaceholderunassignedunassigned
5.1.3 User Organisation registryPlaceholderunassignedunassigned
5.1.1 1+MG User Portal and central data cataloguePlaceholderunassignedunassigned
5.2.2 Access review and decision supportPlaceholderunassignedunassigned
5.2.5 1+MG compliant local IT infrastructure (Data Host)Placeholderunassignedunassigned
5.2.4 Data subject servicesPlaceholderunassignedunassigned
5.2.6 Data transformation and documentationPlaceholderunassignedunassigned
5.2.1 1+MG NCP node and national cataloguePlaceholderunassignedunassigned
5.2.3 Secure processing environment (SPE)Placeholderunassignedunassigned
5.2.7 Subject-level discovery endpointPlaceholderunassignedunassigned
5.3.1 User Organisation registration and user managementPlaceholderunassignedunassigned
6.2.3 Data access requestPlaceholderunassignedunassigned
6.2.2 Data discoveryPlaceholderunassignedunassigned
6.2 Data accessPlaceholderunassignedunassigned
6.2.4 Review and decisionPlaceholderunassignedunassigned
6.2.1 Registration of the User OrganisationPlaceholderunassignedunassigned
6.1 Data inclusionPlaceholderunassignedunassigned
6.4 Exercise of data subjects’ rightsPlaceholderunassignedunassigned
6. Runtime viewPlaceholderunassignedunassigned
6.5 Security incident and personal data breachPlaceholderunassignedunassigned
6.3.7 ArchivingPlaceholderunassignedunassigned
6.3.1 Data use agreementPlaceholderunassignedunassigned
6.3.3 Healthcare reusePlaceholderunassignedunassigned
6.3.8 Incidental findingsPlaceholderunassignedunassigned
6.3 Data usePlaceholderunassignedunassigned
6.3.2 Processing in the SPEPlaceholderunassignedunassigned
6.3.5 Reaching back to data subjectsPlaceholderunassignedunassigned
6.3.6 Results, publications, IP and enriched dataPlaceholderunassignedunassigned
6.3.4 Transparency and communication on data usePlaceholderunassignedunassigned

Wave 5 — Crosscutting details

Detail the concepts that the scenarios and components rely on: security, identity, logging, consent, identifiers, output control, versioning, metadata, EHDS. Starts when wave 4 pages are at least in review.

Approved 0 In review 0 of 10 pages

PageStatusOwnerReviewers
8.9 Dataset versioningPlaceholderunassignedunassigned
8.11 EHDS integrationPlaceholderunassignedunassigned
8.7 Key-coded identifiers and data linkagePlaceholderunassignedunassigned
8.4 Identity, authentication and authorisationPlaceholderunassignedunassigned
8. Crosscutting conceptsPlaceholderunassignedunassigned
8.6 Legal basis, consent and objectionPlaceholderunassignedunassigned
8.5 Logging, monitoring and auditPlaceholderunassignedunassigned
8.10 Metadata and semantic interoperabilityPlaceholderunassignedunassigned
8.8 Output controlPlaceholderunassignedunassigned
8.3 Security and risk managementPlaceholderunassignedunassigned

Wave 6 — Deployment, quality and consolidation

Deployment at central, national and local level, quality scenarios, risks, national profile template, and a final check of the reader guides. Starts when wave 4 and 5 pages are at least in review.

Approved 0 In review 0 of 13 pages

PageStatusOwnerReviewers
National implementation profile (template)Placeholderunassignedunassigned
7.1 Central deploymentPlaceholderunassignedunassigned
7. Deployment viewPlaceholderunassignedunassigned
7.3 Local deploymentPlaceholderunassignedunassigned
7.2 National deployment patternsPlaceholderunassignedunassigned
10. Quality requirementsPlaceholderunassignedunassigned
11. Risks and technical debtPlaceholderunassignedunassigned
Guide for data protection officersDraftunassignedunassigned
Guide for ELSI specialistsDraftunassignedunassigned
Guide for implementersDraftunassignedunassigned
Guide for legal expertsDraftunassignedunassigned
Guide for policy makersDraftunassignedunassigned
Guide for security advisorsDraftunassignedunassigned