Technical architecture

Six coordinated layers. One governed rail.

This page gives technical and institutional evaluators a published view of Curela’s architecture boundaries. Detailed specifications, assurance profiles and implementation documents are available through a controlled request route.

View interactive model
Architecture position

Foundation-aware. Institution-controlled.

Curela is designed to sit above foundational identity infrastructure, not to replace 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.

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 does not hold sovereign keys.

Published layer model

What each layer is responsible for.

The separation of concerns is deliberate: personhood, identity, entitlement, authority, information exchange and funding continuity are not collapsed into one credential or one application.

01

TrustRules & institutions

Defines who may issue, verify and rely on credentials; how organisations enter or leave the network; which assurance levels apply; and how exceptions and disputes are governed.

  • Government- or institution-owned trust registry
  • Operating rules and assurance profiles
  • Issuer and verifier governance
  • Revocation and exception processes
02

IdentityPortable credentials

Links the person to a national or institutional identity source and issues portable health credentials that can be presented, recovered, updated and revoked across online and offline environments.

  • Configurable identity anchor
  • Biometric and non-biometric assurance
  • Recovery and re-issuance
  • Offline presentation pathways
03

ExchangeAuthorised information flow

Curela enables consented, standards-based exchange between authorised systems. Clinical records remain with the institutions that hold them; Curela verifies who may access what, and records that it happened.

  • Standards-based system exchange
  • Structured summary references
  • Access-event evidence
  • No clinical-record custody
04

AccessVerification & consent

Provides role-appropriate presentation, verification, consent, notification and revocation tools for people, providers, field teams and regulated relying parties.

  • Citizen passport
  • Provider and institutional verifier
  • Offline QR verification
  • Consent and access history
05

ApplicationsCare at the endpoint

Allows Curela and approved third parties to build community, provider, emergency, travel and other workflows on a shared trust foundation rather than recreating identity and integration for each service.

  • Community and provider workflows
  • Emergency and travel contexts
  • Approved third-party integration
  • Application portability
06

SustainabilityEntitlement, verification economics and funding continuity

Health systems rarely fail at build. They fail at year three, when programme funding ends and no domestic budget line carries the recurring cost. Curela treats funding continuity as an architectural problem, not an afterthought. The same rail that verifies identity also records verification events, so the infrastructure can be operated under a transparent, auditable cost structure — and so that verification by private institutions can contribute to the cost of public service delivery rather than sitting outside it. Public bodies verify without charge at the point of use. Entitlement rules remain the property of the funder. Curela never holds or moves money.

  • Funder-owned entitlement rules
  • Auditable verification events
  • Transparent operating-cost structure
  • No custody or movement of money
Published principles

Boundaries that govern implementation.

These principles are public. Detailed controls, profiles and specifications are released under the appropriate evaluation process.

01

Governance before technology.

Institutional roles, authority, liability, assurance and exception handling are defined before production credentials are issued.

02

Built for trust, not lock-in.

Identity anchors, clinical systems and operating partners remain replaceable through governed interfaces and portability commitments.

03

Offline inclusion.

Verification and field workflows account for interrupted connectivity, shared devices, assisted access and retrospective synchronisation.

04

Accountable refusals.

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

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, apply entitlement rules and coordinate care.

Controlled documentation route

Request detailed architecture specifications.

For government architecture teams, regulated providers, development institutions and approved delivery partners undertaking a substantive evaluation.

Technical enquiry

Request specifications.

Tell us about the institution, evaluation context and architecture questions you are working through.