Open app

Integrations

The layer beneath your software.

Deliver verified, source-cited patient context to the systems you already run — through one API, an MCP surface other agents cite, and FHIR-shaped exports. MedLineage sits beneath your product; it does not replace your EHR.

See the live demoSee proof & safety

03Agent-ready

Grounded answers, by construction.

No SDK, no rewrite. Add one MCP server entry to the agent you already run — Claude Desktop, Claude Code, or any MCP client — and it gains read-only tools that return source-cited, ledger-attested patient context.

mcp.json+9 -0
  {    "mcpServers": {+     "medlineage": {+       "command": "python",+       "args": ["-m", "mcp_server"],+       "env": {+         "MEDRECORD_MCP_ENABLED": "true",+         "MEDRECORD_PATIENT_GRAPH_ENABLED": "true",+         "MEDRECORD_MCP_DEFAULT_PATIENT_ID": "pat_demo_neph"+       }+     }    }  }
+9 LINES · READ-ONLY · PATIENT BOUND BY HEADER, NEVER BY A PROMPT
get_verified_context(decision="oncology_colorectal") →result
  {    "claims": [      { "text": "CEA 8.2 ng/mL (rising)",        "citation": "[obs_4a]",        "source_document_id": "doc_2",        "verification_status": "attested" }, ...    ],    "counts": { "total": 14, "verified": 9 }  }
EVERY CLAIM: CITATION + SOURCE DOC + LEDGER STATUS
01

Add one MCP server

Drop the medlineage entry into your MCP config (Claude Desktop/Code — or run it hosted at /mcp). No SDK, no schema changes.

02

Your agent gains the tools

get_verified_context, get_patient_state, check_claims, ask_patient appear automatically. The patient is bound by the X-Patient-Handle header — never passed in a prompt.

03

Cited & ledger-attested

Every claim returns with an [obs_*] citation, its source document, and a Provenance-Ledger status — compare it with raw-PDF parsing via compare_context.

  • ask_patient
  • get_patient_context
  • assess_readiness
  • list_evidence_gaps
  • resolve_citation
  • verify_claim
  • get_fhir_bundle
  • get_verified_context
  • get_verification_coverage
  • get_patient_state
  • check_claims

Shipped behavior, demonstrated on synthetic cases — flag-gated per deployment.

ONE SERVER ENTRY, EVERY RECORD CITED11 TOOLS · STDIO + HTTP · NO PHI IN PROMPTS

Plugs into your stack

Sits alongside your software. Doesn't replace it.

MedLineage delivers verified patient context through one API to the systems you already run.

  • Clinical CRM

    Give care and sales teams a verified patient history inside the tools they already use.

  • EHR / EMR

    Surface source-cited context beside the chart — no migration, no schema change.

  • Patient portals

    Let patients see a structured, source-cited history they can actually understand.

  • Clinical AI & agents

    Serve context other agents cite over MCP instead of re-parsing PDFs.

Integration categories describe capabilities of the API, MCP, and FHIR layer. No specific vendor integration or partnership is implied.

Inbound paths

HL7 v2, FHIR, CSV labs and the Connect push API — plus the patient's own national health record.

Connect a Fascicolo Sanitario Elettronico