An architecture designed as a living organism: capture signals, model decisions, act with consent, secure every transmission. Palantir-inspired, redesigned for European healthcare.
Decision-first, not data-first. You at the centre — not your data.
Four interconnected dimensions running through the whole system. None is bolt-on: every one is woven into the architecture.
Data
Your health data unified through FHIR R4 (clinical) + OMOP (research). Whatever the source — lab, hospital, pharmacy, national health record — they speak one language.
Logic
Granular consents, sharing policies, predictive scores, orchestrations — all logic is explicit, modifiable, never a black box.
Action
Six patient verbs. Every action is a signed, traced, reversible event with cryptographic proof admissible in court.
Security
End-to-end encryption, key on your device, immutable consent ledger, verifiable audit trail. Not a layer added on top — a thread woven through every dimension.
Most health platforms list features. We prefer to list what you can do.
Granular access — by data, by professional, by duration. You choose exactly what Dr. Smith sees.
“I share my lab results with the cardiologist in Lyon, for 30 days, read-only.”
One tap, and access stops. Revocation is recorded on the ledger — admissible even in court.
“I revoke access for the insurer I just left — instant effect, proof archived.”
Contribute to research on a specific condition. Anonymous donation, revocable, full control.
“I donate my diabetes data to the CNRS national registry — anonymised, revocable for life.”
One click, and you get your passport in signed FHIR R4 format. Portable across Europe — no permission needed.
“I download my full record before a long trip to the United States.”
Designate the person who will inherit governance of your data in case of incapacity or death.
“I appoint my daughter as digital executor — multi-jurisdiction, European family law.”
Hand management of your data to a relative or carer, with a precise, time-bound mandate.
“During my hospital stay, my partner can accept urgent shares — but cannot edit my history.”
Patient → Clinician → AI → Ledger → Patient. Every link feeds the next, every action is returned to the patient — readable, verifiable, revocable.
Patient
The patient emits a signal — symptom, measurement, sharing consent, donation to research.
Clinician
The professional receives the signal in context (FHIR), acts, prescribes, observes, returns a traced decision.
Predictive AI
AI analyses the trajectory, suggests alert thresholds, protocols, relevant research cohorts — always reviewable by a human.
Ledger
The permissioned ledger seals every consent, revocation, donation — immutable proof, admissible to patient and third parties.
This loop turns a static medical record into a living care journey. The patient is not the end of the chain — they are its centre.
We build exclusively on international standards and European or neutral open-source bricks. No dependency on a US or Asian vendor on the critical layer.
Open-source · TypeScript
Modular, typed, testable Node.js backend framework. Core of our API — auth, RBAC, consent orchestration.
Open-source · Vercel
Modern React front-end framework. App Router, Server Components, native performance. Patient, doctor, admin, landing apps.
Open-source · PostgreSQL Global Group
Reference relational database, ACID, proven at scale. Stores our encrypted data + Prisma metadata.
Open-source · BSD
Cache + real-time pub/sub + BullMQ queues. Notifications, sessions, secure messaging throughput.
Hosting · France · HDS
Health-Data-Hosting (HDS) certified provider, sovereign French infrastructure, GDPR + Ségur compliant. No health data ever leaves the EU.
Standard · HL7 international
Open multi-vendor interoperability models. Real portability guarantee to any HIS or research registry.
Every critical component is open-source or standardised. If needed, you (or we) can rebuild elsewhere without rewriting the business layer.
See real portability of your passport, or learn more about the mission driving MDMC.
Engineering view
Prefer a standard technical view? Our digital-twin architecture lays out the components from an engineer's standpoint — data/logic/action/security layers, open stack, data flows.