Skip to main content
PlaceholderWave 3Owner: TBDReviewers: unassignedLast review: not yet reviewed
Who should read this:Policy makersLegal expertsELSI specialistsSecurity advisorsData protection officersImplementers

9. Architecture decisions

In short
  • To be written: three plain-language bullets that answer the questions below.

What this page must answer​

  • The list of architecture decision records (ADRs), their status and their date.

Sources to start from​

Decision log​

ADRTitleStatus
ADR-0001Record architecture decisionsProposed
ADR-0002Who decides on access, per type of datasetProposed

Candidate decisions to record​

These choices are already made in the governance or in GDI. They should become ADRs so that their reasons are visible:

  • Consent (or a specific legislative act) as the legal basis for making data available DG III.
  • Federated processing in national SPEs instead of pooling data centrally DG II.2.
  • No download of personal data; only non-personal results leave the SPE DG II.2.
  • "Key-coded identifier" instead of "pseudonym" DG I.
  • Interfaces first: components described by function, interfaces and standards, with the GDI Starter Kit and the GDI central services as reference implementation (documentation decisions D-007, D-020).
Placeholder

This page has no content yet. The owner replaces this note and the questions above with the content.