Updated 3 min read

What does granular consent actually look like?

Much of what passes for “consent” online is a wall of text with one button: a 2020 study of consent pop-ups on the 10,000 most visited UK websites found that only 11.8% met minimal legal requirements. You agree once, to everything, forever, and you never find out what was done under that agreement. Granular consent is the opposite design, and it is precise enough to be described mechanically; researchers in biomedical ethics call it dynamic consent.

The four properties

Specific. A consent names what data is shared (which streams, not “your data”), with whom, for what purpose, and for how long. That is the legal standard too: the GDPR requires consent to be specific and informed, and the European Data Protection Board insists on granularity, purpose by purpose. On the Health Data Safe platform, when a clinician or researcher requests access, the patient receives a plain-language explanation of exactly that, and approves or declines with a single action.

Revocable. Consent that cannot be withdrawn is not consent; it is a transfer, and the law agrees: withdrawing consent must be as easy as giving it. Every access grant can be revoked at any time, and revocation takes effect on the infrastructure, not in a customer-service queue.

Auditable. Every access event is logged with a timestamp, the accessor’s identity, and the scope of data accessed, the same fields Swiss law requires in a data-protection log. The log is invariant: it can be read, never rewritten. You can verify, not just hope, that your terms were honoured.

Structural. The consent is not a policy sitting next to the data; it is the mechanism through which data flows. That is what data protection by design means in practice. Each connection is mediated by an Access object: no data flows without a corresponding, time-limited, purpose-specific consent record. The architecture makes it structurally impossible to use data without one.

Why partners want this too

For a clinic or research team, granular consent is not overhead; it is inherited compliance. A partner integrating with HDS inherits the consent management, the invariant audit log (from which the record of processing activities required by GDPR Art. 30 can be generated on demand), and the rights of access, erasure and portability (GDPR Art. 15/17/20, HIPAA 45 CFR §164.524 for access, nLPD Art. 25/28/32) as built-in capabilities rather than obligations to implement.

How each patient right under HIPAA, GDPR and the Swiss nLPD is honoured, and who is responsible for it, is set out publicly in the Compliance Matrix, published in June 2026.

See it from the patient’s side in How it works, or from the partner’s side in Join as a partner.

Sources