Skip to content

Last EHR v0.2.1 — read-only Medplum MCP

Choose a tag to compare

@cbetz cbetz released this 11 Jul 14:47
· 211 commits to main since this release

A safe MCP entry point for FHIR chart context

v0.2.1 makes Last EHR’s bounded chart-reading surface available as a public,
installable MCP server. The division is deliberate: MCP reads charts; the web
app keeps clinical writes proposal-shaped and approval-gated.

Install the MCP server

npx -y @lastehr/mcp init --client claude-code

@lastehr/mcp@0.1.1 is now
listed in the Official MCP Registry.

It exposes exactly two Medplum tools:

  • search_patients
  • show_patient_info

Both tools carry MCP’s readOnlyHint. The published package has no write tools
and no environment switch that enables them.

Try the complete workflow locally

npm install
npm run demo:local

This starts local HAPI FHIR, seeds synthetic records, and demonstrates a fixed
approval-gated observation flow without a Medplum account or external model
key.

The local route is an evaluation tool—not a general local clinical agent or a
PHI-ready deployment path.

For FHIR implementers

Last EHR includes a bounded backend adapter seam, a reusable FHIR REST
transport, executable adapter starter, and contract harnesses. Medplum is
supported for the MCP package; local HAPI remains available for synthetic
web-app evaluation.

Safety boundaries

  • Read-only MCP access can still return PHI. Use a least-privilege Medplum
    identity and review your MCP client and model provider’s data handling.
  • @lastehr/mcp supports hosted or self-hosted Medplum authentication today.
    It does not claim generic FHIR, HAPI, SMART launch, or browser-approval
    parity.
  • The package is not an authorization layer.
  • Clinical writes remain in the web app’s approval-gated flow; direct MCP
    writes require a future reviewable confirmation protocol and safety review.

See the MCP guide,
quickstart, and
adapter guide for setup and support
boundaries.