The platform
Four layers.
One patient identity.
Lyvra is a continuity and trust layer between the systems that hold health information. It does not replace EHRs or payer systems; it lets trusted context move between them, under the patient’s control.
01 · LAYER
Patient
The health identity people carry: their wallet, family, emergency profile, travel and Aya, the record-grounded assistant.
Health WalletFamilyEmergencyTravelAya
02 · LAYER
Trust
The core. Every exchange is tied to a verified identity, scoped by the patient’s consent, authorized by the server, attributed to its source and audited.
IdentityConsentAuthorizationProvenanceAudit
03 · LAYER
Clinical
The longitudinal record and the clinician’s view of it: records, visits, prescriptions as issued by the prescriber, and exchange with EHRs.
RecordsVisitsPrescriptionsEHR exchangeClinician workspace
04 · LAYER
Coverage
The administrative side of the same journey: insurance, eligibility, requirements, prior authorization, claims and adjudication, through market-specific rails.
InsuranceEligibilityRequirementsPrior authorizationClaimsAdjudication
Interoperability
FHIR moves data. Lyvra governs trust around it.
Standards make systems connectable. Lyvra turns what they exchange into a longitudinal context the patient controls, with the origin of every item preserved.
Source systems
EHRs, laboratories and documents, through FHIR R4 interfaces or patient upload
Normalisation
Mapped into one canonical clinical model
Provenance
Each item keeps its source, date and origin
Longitudinal context
One record across visits, years and providers
Patient-controlled sharing
Scoped, time-limited and audited
Architecture
Modular today. Designed to scale into services where needed.
One modular core keeps security, audit and releases simple to reason about. Clear internal interfaces let modules be extracted into services as scale requires.
Patient app
Installable web app
Clinician Workstation
Web workspace
Lyvra core · modular services in one controlled process
Data
Relational core · encrypted document storage · managed keys
Integrations
EHR / FHIR connectors · payer adapters
Design principles
- Authorization is decided on the server for every request.
- Provenance travels with every record.
- Machine-checkable contracts define every interface.
- Storage, keys, inference and audit sit behind internal interfaces, so providers stay replaceable.
- Lyvra follows the prescription; it does not create it.
Coverage
One canonical payer model. Market-specific rails.
Coverage, eligibility, requirements, authorization and claims are modelled once. Each market connects through its own adapter, so a new market is an adapter, not a rewrite.
Patient
One identity and the coverage that goes with it
Provider
Care delivered with the right context
Lyvra trust layer
Consent, authorization and provenance on every exchange
Coverage workflow
Payer and administrator systems, market by market
- 01Coverage
- 02Eligibility
- 03Requirements
- 04Prior authorization
- 05Claims
- 06Adjudication
Payer interface
Patient and provider requests
Orchestrator
Routes each request by capability
Canonical payer domain
One model for coverage and claims
Adapter registry
Knows what each rail supports
Market rails
National schemes, insurers and administrators
Payer connections are activated market by market with institutional partners.
Designed for regulated healthcare environments
Built like healthcare infrastructure, not a demo.
The foundation is engineered with the discipline regulated care expects: explicit contracts, verification, controlled change and recoverability.
Server-enforced authorization
Every request is checked against the patient’s active authorization on the server, not in the interface.
Provenance by design
Each record carries its origin from import to display, and through every share.
Automated verification
Machine-checkable contracts and automated unit, database and browser tests on every release.
Controlled migrations
Reviewed, ordered schema changes released through gated steps with rollback plans.
Encryption and key management
Health data and documents encrypted at rest, with keys held in a managed key service.
Restore and erasure safeguards
Protected backups and a tested restore procedure that keeps erasures in force.
Lyvra Health
A platform built for how people actually move through care.
Talk to us about integration, partnership or the platform roadmap.