Provenance
Verifiable by design
- Every claim cites its document, page and source language
- Every agent run is logged
- Clinicians attest each finding — verdicts stamp the next build
For clinics today · for every healthcare agent next
MedLineage reads a clinic's inbound records — PDFs, HL7 v2 messages, FHIR observations, CSV labs, in five languages — into a source-cited patient graph that clinicians attest and other AI can query.
100% provenance coverage · 1.00 extraction F1 on our published synthetic benchmark — raw JSON public, drift fails CI. JSON →
Prepares records for clinician review. Does not diagnose, does not recommend treatment, does not replace clinicians. Best-effort de-identification, not certified anonymization.
Measured on synthetic complex-care demo
See the full metric grid, scoreboard, and what we don’t claim on Proof & Safety.
How it runs
Records arrive as PDFs, HL7 v2 messages, FHIR resources or CSV labs — in any of five languages.
Deterministic passes build the patient graph. LLMs only verbalize — they never rank, score or invent structure.
Clinicians sign verdicts into a tamper-evident provenance ledger — every claim carries its verification status.
Specialist packets, FHIR bundles, signed data rooms — and MCP tools other agents cite instead of re-parsing PDFs.
Agent-ready
An MCP surface exposes the verified patient graph to any agent runtime — eight read-only tools, every payload deterministic and citation-stamped.
MCP tools
The citation contract: every factual sentence an agent gets back carries a graph ID it can resolve — uncited sentences are stripped before they ship.
Shipped behavior, demonstrated on synthetic cases — flag-gated per deployment.
> tools/call get_verified_context
{
"patient_id": "pat_3f9c…",
"claims": [
{
"citation": "obs_a41d…",
"kind": "observation",
"text": "Creatinine 1.8 mg/dL (2024-03-02) [H]",
"source_document_id": "doc_77e2…",
"verification_status": "attested"
},
…
],
"counts": { "total": 23, "verified": 19,
"documents": 3, "observations": 14, "events": 6 },
"deterministic": true
}Measured, not promised
Synthetic multilingual gold set — not a clinical study. The scoreboard is committed to the repo and pinned in CI: any drift fails the build.
253 synthetic gold facts · 5 languages
every recovered fact cites its source document
no synthetic case tripped the safety net
Live clinical pilot
Sanity Health is a small private clinic in Milan with around 500 patients. The clinic pushes its inbound clinical records straight into MedLineage Connect — we turn them into a source-cited patient-context layer its clinicians can review and attest, with every finding tracing back to the document, page, and source language it came from.
Free-text clinical artifacts pushed straight from the clinic into MedLineage Connect.
Every finding traces back to its document, page, and source language.
Records flow under an opaque patient handle — best-effort de-identification, not certified anonymization.
Pilot in progress. MedLineage prepares records for clinician review — it does not diagnose, recommend treatment, or replace clinicians.
05Trust & control
Provenance
Data
Interoperability
Not a medical device. Not certified for FHIR, GDPR or EHDS conformance. No diagnostic capability or guaranteed anonymization is claimed.
Generate a clinician-ready PDF today. Re-upload tomorrow to thicken the same Patient Graph. Let safe agents open the next review task and prepare a signed Data Room when you're ready to integrate — every step gated for human approval.
Working with hospitals or second-opinion services? Bring 5 real cases — we run them de-identified and you sign off the packets. Run a de-identified pilot
Coordinates record-preparation work. Does not diagnose, does not recommend treatment, does not replace clinicians. No certified FHIR / GDPR / EHDS / MDR / CE conformance is claimed.