The health trust layer

Trusted health identity.
Connected care.

Curela is infrastructure for portable health identity and verified care continuity — built to connect people, providers and public systems without replacing the institutions that already exist, and designed to remain funded after the programme that built it has ended.

Explore the architecture
Sovereign-aligned Offline-first Interoperable by design
Verification recordIllustrative · not live data
Subjectpr_pv_4K2M·9QX7
PurposeDispense against programme cover
BasisProgramme cover · recorded
VerifierCommunity pharmacy · authorised
NetworkOffline · signed trust package
DisclosedIdentity match · cover status
No name, national identifier, diagnosis, medicine or clinical record crossed. The person can see who verified them, and why.
Minimum disclosurePerson-visible purpose
01

Health systems do not need another closed app. They need a shared trust layer.

The funding problem

Health systems rarely fail at build.
They fail at year three.

Most digital health infrastructure fails when programme capital is spent and no domestic budget line carries the recurring cost.

Programme capital pays for design, hardware and rollout. Then it ends. Certificates lapse, support contracts stop, registries drift, and an asset that worked is quietly written off — not because the technology failed, but because no domestic budget line was ever designed to carry it.

Curela treats funding continuity as an architectural question, not an afterthought. The rail that verifies identity is the same rail that makes the cost of running it transparent and accountable — so the infrastructure has a route to being paid for after the grant closes.

Curela is designed to be funded after the grant ends.
Funding continuityIllustrative · shape only
funding ends Y1Y3Y7
Programme-funded build Net public cost, Curela model
The platform

Identity is the missing infrastructure between fragmented health systems.

A person's history is scattered across institutions, devices and borders. Curela creates a verifiable connection between identity, entitlement and authorised care — so information travels with the person while control stays with the institutions that hold it.

01

Establish trust

Align governance, identity anchors, participating organisations and assurance rules — before any technology is deployed.

02

Issue identity

Create a portable, verifiable health identity bound to the person, not to a single provider or programme.

03

Connect systems

Enable consented, standards-based exchange between authorised systems. Records stay where they are.

04

Enable care

Support public, private and community applications without locking the ecosystem to one app or supplier.

The architecture

One rail. Six coordinated layers.

Each country or network keeps its own governance, identity systems, clinical platforms and delivery partners.

Foundational identity

Curela sits above foundational identity infrastructure rather than replacing it. Where a country already operates a national identity platform — including open-source foundational identity systems — Curela integrates with it as the authorised identity source. The identity anchor is a configuration, not a dependency.

Layer 01

Governance before technology.

Define who may issue, verify and rely on credentials; how disputes are resolved; and which assurance levels apply to each use case. The trust registry is owned by the government or institution that governs it — Curela operates the infrastructure and admits no issuer and no sender. Identity remains anchored to the national or institutional authority; Curela does not become the identity authority and holds no sovereign keys.

  • Trust framework and operating rules
  • Government- or institution-owned trust registry
  • National or institutional identity anchor
Design principles

Built for trust, not lock-in.

These choices protect institutional sovereignty while making health identity practical in real operating environments — shared devices, interrupted connectivity, assisted access and multiple funders.

01

Sovereign control

Public authorities and participating institutions retain control over policy, identity anchors and regulated data. Curela operates infrastructure and holds no sovereign keys.

02

Offline inclusion

Core verification and field workflows assume interrupted connectivity, shared devices and assisted access — not as a fallback, but as the normal case.

03

Interoperability

Curela connects existing systems and standards rather than forcing wholesale replacement, and sits above foundational identity infrastructure instead of competing with it.

04

Selective access

People and institutions disclose the minimum information required for a specific, authorised purpose — and nothing beyond it.

05

Modular deployment

Start with one corridor, district or use case, then extend the same governed foundation without rebuilding it.

06

Institutional accountability

Issuers, verifiers and relying parties operate under explicit roles, tamper-evident audit trails and defined exception processes.

08

Replaceability

Credentials use open standards and remain verifiable independently of Curela. A country that changes operator should not lose its rail.

07

Accountable refusals

Where cover or authorisation is declined, the person is told which programme and which funder decided, why, and what to do next. A funder’s policy is never experienced as a failure of the person’s credential.

Use cases

One identity across many care contexts.

Curela makes identity, consent and continuity reusable. Care models stay adaptable to local institutions and need.

Community health

Connect the last mile to the health system.

Equip authorised community teams to identify people, capture structured care events and connect referrals — without turning the field worker into the owner of the record, and without assuming a network connection that is not there.

Assisted accessOffline workflowsReferral continuityShared devices
Who Curela serves
01

Governments & public institutions

National, regional and municipal health authorities building trusted digital public infrastructure that has to remain affordable after the build.

Explore deployment
02

Providers & health networks

Hospitals, clinics, laboratories, pharmacies and community networks that need reliable identity and continuity at the point of care.

Technical architecture
03

Development & financing partners

Institutions funding health access and system modernisation that need infrastructure with a credible route to domestic sustainability.

Deployment model

Start with a bounded problem. Build a reusable institution.

Deployments begin with governance and operating reality, not a generic technology rollout. The environments we build for are demanding by design: island and rural geography, intermittent connectivity, shared handsets, community health workers, and more than one funder in the same programme.

01

Discover

Map institutions, regulation, identity anchors, workflows and the specific continuity failure to be solved.

02

Design

Define the trust framework, assurance levels, architecture, operating model and commercial boundaries.

03

Pilot

Launch a controlled corridor, population or provider network with measurable service and trust outcomes.

04

Scale

Extend institutions, use cases and geography on the same governed rail — without a second build.

Operating environment

Built for island and rural health systems where infrastructure is uneven but accountability cannot be.

The operating environment includes island and rural geography, intermittent connectivity, shared or institution-managed devices, community health workers, multiple public and donor funding programmes, and providers at different levels of digital maturity. Curela treats these as baseline architectural conditions rather than edge cases.

Island & rural geographyIntermittent connectivityShared devicesCommunity health workersMultiple funders
C

Curela is not a replacement for national identity, hospital systems or clinical judgement.

It is the governed infrastructure that helps them recognise the same person, exchange authorised context and coordinate care.

About Curela

Infrastructure for health systems that must work across institutions, geography and imperfect connectivity.

Curela is a UK-founded health infrastructure company developing a trust, identity and verification layer for connected care, with initial focus on East Africa and work oriented toward public institutions, provider networks and development partners.

We believe the durable health platform is not the application that owns every interaction. It is the trusted rail that lets many institutions and applications coordinate safely — and that a country can still afford to run in its seventh year.

HeadquartersUnited Kingdom
FocusHealth identity & verification infrastructure
Initial regionEast Africa
ApproachInstitution-led deployment
Identity anchorNational — never Curela
MoneyNever held or moved by Curela
Build the trust layer

Discuss a national, regional or network deployment.

For public institutions, health networks, development partners and regulated infrastructure providers. Technical documentation is available to institutional counterparties on request.

Strategic enquiry

Discuss a deployment.

Tell us about the institution, geography and continuity problem you are working on.