Skip to main content

GDPR Art. 9 (opens in a new tab) · GDPR Art. 7 (opens in a new tab) · Humanitarian health data

When refugee-camp health data moves between organisations, the receiving organisation has to be able to show the consent behind its use.

Modern Miracle built consent records bound to a decentralised identity, with encrypted health data.

Status: Delivered in 2024. The smart-contract and API documentation is published on GitHub under the AGPL-3.0 licence.

Operating constraint

Health data recorded in refugee-camp clinics moves on to other organisations, and each receiving organisation has to be able to show the consent behind its use under GDPR Art. 7(1). A consent record kept inside the collecting clinic's system gives the receiving organisation nothing it can check independently.

How it was built.

Consent bound to decentralised identity remains checkable as cryptographically protected health-data records move across chains.
Project
LED-UP
Programme
NGI TrustChain, Open Call 2
Delivered
2024
Setting
Health-data governance in refugee-camp settings
Timeline
Selected · January 2024Delivered · 2024

Decisions, and the obligation or standard each one meets.

  1. Consent is bound to a decentralised identity.

    MeetsGDPR Art. 7(1) requires a controller relying on consent to demonstrate it. The architecture makes the consent record checkable. Whether consent is the right basis where there is a clear imbalance (Recital 43) is the controller's call. (opens in a new tab)

  2. Cryptographic privacy mechanisms on health records.

    MeetsGDPR Art. 9(1) places health data in a special category, and GDPR Art. 32(1)(a) names encryption among the security measures. (opens in a new tab)

  3. Multi-chain interoperability.

    MeetsConsent stays checkable across the different record systems that organisations in one humanitarian response use.

Design response

LED-UP was built as a governance layer on top of the LEVEA patient record system already running in the camps. Consent is bound to a decentralised identity held by the person, so the consent record travels with the data and a receiving organisation can check it. Solidity smart contracts carry the governance: a consent contract lets the data producer grant, revoke and query a provider's consent, a data-registry contract records medical-resource metadata and checks consent before data is shared, and a compensation contract verifies payments to data producers and manages their balances. Further contracts cover a token and zero-knowledge proof verification, and cryptographic privacy mechanisms protect the health records themselves.

Result

LED-UP was delivered under NGI TrustChain, Open Call 2, in 2024. It gives a receiving organisation a consent record it can check against the person's own identity, and its smart-contract and API documentation is published for inspection.

The record behind this engagement.

Funded under NGI TrustChain, Open Call 2.

View evidence — LED-UP (opens in a new tab)

Licence: AGPL-3.0

Tell us what you're building and the regulation it has to meet.

You will speak with one of the two founders.