HEALTHCARE.
Patient-facing and clinical-adjacent systems where data protection is an architectural constraint rather than a policy document, and residency decisions precede the schema.
- SECTOR
- 02 of 06
- DEFINING CONSTRAINT
- Data protection & residency
- DISCIPLINES APPLIED
- Products · Blockchain · Security
- DOCUMENTED WORK
- 1 engagement
02 / THE CONSTRAINT — DATA PROTECTION & RESIDENCY
RESIDENCY ISAN ARCHITECTURE.
Health data carries obligations that follow it across every system it touches. Where it is stored, which jurisdiction governs it, who may read it, how long it is retained and how it is destroyed are all questions with legal answers and engineering consequences.
Retrofitting those answers is expensive because they reach into the data model, the hosting topology and the access control layer at once.
We establish the residency and consent model before the schema, and we design so that a change of jurisdiction is a configuration decision rather than a migration project.
03 / What it means in code
FOUR DECISIONS.
RESIDENCY
Storage topology decided against jurisdiction, not against convenience.
CONSENT
Recorded as data, versioned, and enforceable at query time.
MINIMISATION
Fields collected because they are needed, with retention defined at creation.
ACCESS
Role and purpose-based, with reads logged to the same standard as writes.
04 / DISCIPLINES APPLIED
Digital Products · Blockchain Engineering · Security Engineering · Applied AI
Most engagements in this sector draw on more than one discipline. The combination is decided by the constraint above rather than by a service menu.
05 / Selected work
PROOF.
25K+
A decentralised health wallet scaled past 25,000 users
AN AFRICAN HEALTH-TECHNOLOGY COMPANY
XRPL · React Native · Consent management
All client work is anonymised by sector and geography. Named references are available under NDA during a live engagement discussion.