Your health. Wherever life happens.

One patient identity.
Across care and coverage.
Wherever life happens.

Lyvra is patient-controlled health infrastructure that brings together trusted health context and makes it portable across providers, systems and borders.

Patient appClinician WorkstationConsent built into every exchange
Lyvra Patient app home: Lyvra Health ID with emergency, insurance and travel, and health trends. Synthetic demo data.
Clinician Workstation: the active authorization, with its scope, reason and end time. Synthetic demo data.

An illustrative story

Casablanca

Alena needs urgent care. Her allergy record is sitting in Geneva.

Geneva clinic

Holds her penicillin allergy record

Closed

Alena

Cannot carry verified health context

Unverified

Casablanca ER

Treating with incomplete information

Deciding now

Healthcare is local.People are not.

The Lyvra idea

The patient becomes the continuity layer.

Hospitals, labs, insurers and clinics each hold a piece of the story. Lyvra connects them through the one participant present at every step: the patient, with consent, provenance and audit built in.

  • Hospitals
  • Clinics
  • EHRs
  • Labs
The patient

Lyvra Health

Patientlayer

Health WalletFamilyEmergencyTravelAya

Trustlayer

IdentityConsentAuthorizationProvenanceAudit

Clinicallayer

RecordsVisitsPrescriptionsEHR exchange

Coveragelayer

InsuranceEligibilityRequirementsAuthorizationClaims

  • Imaging
  • Payers / TPAs
  • Cross-border providers

Explore the platform

How it works

Your context moves with you.

Six steps, from a scattered history to continuity that follows the patient wherever care happens next.

  1. 01

    Build

    Bring records and health context together in one longitudinal record, each item kept with where it came from.

    Patient app Records, organised by visit, each record showing its source. Synthetic demo data.
  2. 02

    Control

    Choose what is shared, with whom, for what reason and for how long. Nothing moves without the patient’s yes.

    Patient app share review: hospital, reason, what they can see and for how long. Synthetic demo data.
  3. 03

    Care

    Clinicians receive the relevant context in a time-limited session, scoped to exactly what was authorized.

    Clinician Workstation: an authorized visit view with access time remaining. Synthetic demo data.
  4. 04

    Continue

    Results return to the patient’s longitudinal record, so the next clinician starts from the full picture.

    Patient app: HbA1c results over time from several sources. Synthetic demo data.
  5. 05

    Coverage

    The same identity extends to insurance and administrative workflows: coverage, eligibility, requirements, authorization and claims.

    Patient app Insurance: the policy kept with the patient’s health identity. Synthetic demo data.
  6. 06

    Anywhere next

    Wherever life happens next, the patient carries continuity forward to the next clinic, city or country.

    Patient app home with an upcoming trip on the Lyvra Health ID. Synthetic demo data.

The product

Already built around the patient.

These are real Lyvra screens, shown with a demo patient. The patient app and the clinician workstation are built, working software.

Patient app home: Lyvra Health ID, emergency, insurance, travel and health trends. Synthetic demo data.

Everything that matters, at a glance.

The Lyvra Health ID brings emergency information, insurance and upcoming travel together, with health trends drawn from the patient’s own results.

  • An emergency profile with a high-contrast screen to show when it matters
  • Insurance and travel kept with the health identity
  • Trends that mark results the source flagged

For clinicians

The right context.
Only after the patient says yes.

The Lyvra Workstation gives clinicians the patient-authorized record in a focused, time-limited view, alongside the systems they already use.

Lyvra Clinician Workstation: a patient’s visit with orders, results, prescriptions and notes, under an active, time-limited authorization. Synthetic demo data.

Verified patient identity

The clinician knows whose record this is before reading anything.

Consented access

Access starts with the patient’s authorization, never with a search.

Longitudinal context

Visits, results and documents in time order, across sources.

Record provenance

Every item shows the system or person it came from.

Visit context

Orders, results, notes and updates grouped by the visit they belong to.

Clinical filtering

Labs, vitals, imaging and documents, each in its own view.

Bounded sessions

Access is time-limited and ends on schedule or on demand.

Audit

Every view is recorded in the patient’s activity log.

Lyvra complements existing clinical systems by bringing patient-authorized context into the care journey.

Explore Lyvra for providers

Care and coverage

Care does not stop at the clinical record.

Every patient journey also runs through insurance: coverage, eligibility, requirements, prior authorization, claims and adjudication. Lyvra carries the same identity and the same trust rules into that side of care.

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

  1. 01Coverage
  2. 02Eligibility
  3. 03Requirements
  4. 04Prior authorization
  5. 05Claims
  6. 06Adjudication

One canonical platform. Market-specific rails.

See the platform architecture

Why now

Healthcare infrastructure is finally opening.

Regulation and standards are making health data more connected. Connectivity alone does not create continuity for the patient; that is the gap Lyvra fills.

Europe

A legal framework for portable health data

The European Health Data Space regulation entered into force in March 2025. Cross-border exchange of patient summaries and ePrescriptions is scheduled from 2029.

Source: Regulation (EU) 2025/327

United States

Machine-readable access is becoming mandatory

Federal rules require impacted payers to offer patient, provider and prior-authorization APIs, with the main API requirements applying from January 2027.

Source: CMS-0057-F fact sheet

Global

A common structure for care across borders

The HL7 International Patient Summary gives clinicians in different countries a shared structure for the essentials: allergies, medications, problems and more.

Source: HL7 FHIR IPS

304 millionpeople lived outside their country of birth in 2024. Source: UN DESA, International Migrant Stock 2024

Trust

Patient control must be infrastructure, not a promise.

In Lyvra, consent is enforced by the server on every request. The interface reflects the rules; it does not replace them.

  • Scoped access

    Share only what is relevant: the whole record, one visit or selected items.

  • Time-bound authorization

    Access expires on schedule, and the patient can end it at any moment.

  • Provenance

    Know where every piece of information came from, and who added it.

  • Auditability

    Every access is recorded and visible to the patient.

  • Encryption and resilience

    Encrypted storage with managed keys, deletion that holds after a restore, and protected backups.

How Lyvra protects health data

Lyvra Health

Health information should move as easily as people do.

Lyvra is building the patient-controlled trust layer for healthcare, across systems, providers and markets.

Mohamed BouchaabFounder & CEO
Mariyam BouchaabCo-founder & CFO

Contact mohamed.bouchaab@lyvra.health