Indigenous Health Data Sovereignty

Health data governed by the people it belongs to

A decentralized identity and data sovereignty platform that enables First Nations citizens to control their health information—from credentials to clinical records—under their Nation's authority.

Scroll to explore

The Problem
A system built on someone else's identity is a system built on borrowed ground
First Nations citizens in British Columbia access health services and benefits using credentials issued by federal and provincial authorities. None of these credentials represent the Nation's own authority. The result is friction, fragmentation, and a fundamental compromise of data sovereignty.
01

Identity Misalignment

Every benefits interaction requires aligning an ISC status card number, a BC health care number, and Pacific Blue Cross member information. Name discrepancies, expired status, and address changes cause rejected claims and manual resolution. Citizens must translate between governance regimes using credentials none of which represent their Nation's authority.

02

Records Fragmentation

Clinical records are scattered across nursing stations, community clinics, provincial hospitals, specialist offices, and pharmacies. A citizen who receives care in a remote community and later visits an emergency department in Vancouver arrives as a stranger to the system. No single view of their health record exists.

03

Data Custody Inversion

Conventional health IT assumes institutional custody of patient data. But First Nations governance requires the opposite: data custody must rest with the Nation or the individual citizen. Adding a patient portal to an existing system does not solve a custodial architecture problem.

04

Interoperability Without Sovereignty

Existing interoperability efforts rely on centralized EHR viewers and point-to-point integrations that never address the fundamental question: who controls the data and where it physically resides. Data Possession requires infrastructure the citizen or Nation controls—not a vendor's cloud.


Governance Foundation
OCAP® as architectural constraint
The First Nations principles of OCAP® are not aspirational guidelines—they are governance standards that any system touching First Nations data must satisfy. Each principle translates directly into a technical requirement.
O

Ownership

Data is owned collectively by the Nation and individually by the citizen. Data stores must be governed by Nation-defined policies, not vendor defaults.

C

Control

The Nation controls identity issuance. The citizen controls access permissions. A dual-authority permission model operating at two governance levels.

A

Access

Citizens and Nations can access data regardless of where it was created. Cross-jurisdictional portability without bilateral data-sharing agreements.

P

Possession

Data physically resides in Nation- or citizen-controlled infrastructure. It must not transit or persist on servers outside sovereign control.


Technical Architecture
Three layers, each delivering value independently
The architecture integrates three technology layers at different levels of maturity. Earlier layers deliver immediate value with proven technology. Later layers advance the state of the art in decentralized data governance.
Layer 1
Digital Identity
Production-ready

Nation-Issued Verifiable Credentials for Health Benefits

A First Nation issues digital membership credentials to its citizens as W3C Verifiable Credentials, using Decentralized Identifiers as the cryptographic foundation. Health service providers accept these credentials for eligibility verification at the pharmacy counter, dental office, and optometrist—replacing the current multi-credential alignment process with a single, Nation-issued digital proof.

W3C Verifiable Credentials Decentralized Identifiers BC Wallet AnonCreds / Aries
Layer 2
Clinical Credentials
Emerging

Portable Clinical Records as Verifiable Credentials

After clinical encounters, care providers issue verifiable credentials summarizing the visit—diagnoses, medications, referrals, immunizations. Citizens hold these in their digital wallet and can present them to any provider. Clinical VCs use FHIR-aligned data structures for interoperability with the Canadian health system while maintaining OCAP® governance constraints.

HL7 FHIR SMART on FHIR Clinical VC Schemas FHIR-VC Encoding
Layer 3
Sovereign Data Storage
Pre-production

Decentralized Web Nodes for Patient-Controlled Records

Each citizen's health records are stored in a Decentralized Web Node—a personal, encrypted data store under the citizen's control. Care providers authenticate via VC, receive scoped access, and read or write clinical data. Nations can host DWN infrastructure for their citizens, ensuring data Possession under OCAP®. Offline-first operation with conflict resolution supports remote and low-connectivity communities.

Decentralized Web Nodes DIF Protocols OCAP® Permission Model Offline-first / CRDTs

How It Works
From Nation authority to point of care
Credential Issuance
Nation Governance Defines schemas · Manages issuance
Verifiable Credential Membership · Eligibility · Status
Citizen's Wallet Self-custody · Selective disclosure
Health Service Access
Citizen's Wallet Presents proof of eligibility
Benefits Verifier Pharmacy · Dental · Vision · Mental Health
Clinical VC Issued Encounter summary returns to wallet
Sovereign Data Storage
Clinical Records FHIR-encoded health data
Citizen's DWN Encrypted · Nation-hosted · Citizen-controlled
Scoped Provider Access VC-authenticated · Time-limited

Regulatory Landscape
Why now
Two concurrent developments create both the urgency and the infrastructure for this work.

BC Digital Credentials Infrastructure

British Columbia has deployed production infrastructure for digital credentials. BC Wallet is a live application for storing and presenting verifiable credentials, with open-source issuer tools available. Provincial pilots are underway across business registration, worker qualifications, and property ownership. The technology stack is proven—its application by a First Nation as identity issuer has not yet been attempted.

Connected Care for Canadians Act

Bill S-5, re-introduced in February 2026, would require health IT vendors to adopt common interoperability standards and prohibit data blocking. A platform built natively on decentralized storage and verifiable credentials is architecturally aligned with what incumbent vendors are being forced to retrofit. Patient-controlled health data stores become a legitimate endpoint for health information exchange.


Roadmap
Phased delivery, incremental value
Each phase delivers standalone value while building toward the full sovereignty stack. The system interoperates with existing community health platforms—it augments them, it does not replace them.
Phase 1
Summer 2026

Nation-Issued Digital Identity

Governance framework design, credential schema development, and pilot deployment with one Nation for health benefits eligibility verification. Citizens present a single Nation-issued digital credential at the pharmacy, dental office, and optometrist.

Phase 2
Fall 2026

Portable Clinical Credentials

FHIR-to-VC schema design, clinical workflow integration, and provider-side testing. After encounters, clinical summaries are issued as verifiable credentials that citizens carry in their wallet and present at any point of care.

Phase 3
Winter 2027

Sovereign Health Data Storage

DWN architecture with OCAP®-compliant permission models, offline-first design for remote communities, and privacy-preserving aggregate analytics for community health planning. Full data sovereignty from identity to records.


Scope
The sovereignty layer that existing systems lack
This is not a complete EMR system. EMRs are clinical workflow engines with decades of accumulated domain knowledge. The contribution here is the sovereignty and data governance layer—the infrastructure that enables Nations and citizens to control health data that existing systems generate. The platform interoperates with existing community health systems through FHIR-native middleware, providing the governance and data custody capabilities they were never designed to include.