Last EHR — Medplum

Name: Last EHR — Medplum
Author: cbetz

作者：cbetz版本 0.5.1i★ –i在你的电脑上运行

注册名称io.github.cbetz/last-ehr

安装

概览

作者提供的说明（英文原文）

FHIR chart tools for MCP: read-only by default, with elicitation-gated, human-approved writes.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 诊所与健康
你需要填写：MEDPLUM_ACCESS_TOKEN, MEDPLUM_CLIENT_SECRET, LASTEHR_PRIVATE_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： MEDPLUM_ACCESS_TOKEN, MEDPLUM_CLIENT_ID, MEDPLUM_CLIENT_SECRET, MEDPLUM_BASE_URL, LASTEHR_BACKEND, LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS, LASTEHR_CLIENT_ID, LASTEHR_PRIVATE_KEY, LASTEHR_PRIVATE_KEY_PATH, LASTEHR_KEY_ID, LASTEHR_JWKS_URL, LASTEHR_SCOPES, LASTEHR_FHIR_BASE_URL, LASTEHR_TOKEN_URL, LASTEHR_ENCOUNTER, LASTEHR_PERFORMER

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "last-ehr": {
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ],
      "env": {
        "MEDPLUM_ACCESS_TOKEN": "your-value",
        "MEDPLUM_CLIENT_ID": "your-value",
        "MEDPLUM_CLIENT_SECRET": "your-value",
        "MEDPLUM_BASE_URL": "your-value",
        "LASTEHR_BACKEND": "your-value",
        "LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS": "your-value",
        "LASTEHR_CLIENT_ID": "your-value",
        "LASTEHR_PRIVATE_KEY": "your-value",
        "LASTEHR_PRIVATE_KEY_PATH": "your-value",
        "LASTEHR_KEY_ID": "your-value",
        "LASTEHR_JWKS_URL": "your-value",
        "LASTEHR_SCOPES": "your-value",
        "LASTEHR_FHIR_BASE_URL": "your-value",
        "LASTEHR_TOKEN_URL": "your-value",
        "LASTEHR_ENCOUNTER": "your-value",
        "LASTEHR_PERFORMER": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add last-ehr --env MEDPLUM_ACCESS_TOKEN=your-value --env MEDPLUM_CLIENT_ID=your-value --env MEDPLUM_CLIENT_SECRET=your-value --env MEDPLUM_BASE_URL=your-value --env LASTEHR_BACKEND=your-value --env LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS=your-value --env LASTEHR_CLIENT_ID=your-value --env LASTEHR_PRIVATE_KEY=your-value --env LASTEHR_PRIVATE_KEY_PATH=your-value --env LASTEHR_KEY_ID=your-value --env LASTEHR_JWKS_URL=your-value --env LASTEHR_SCOPES=your-value --env LASTEHR_FHIR_BASE_URL=your-value --env LASTEHR_TOKEN_URL=your-value --env LASTEHR_ENCOUNTER=your-value --env LASTEHR_PERFORMER=your-value -- npx -y @lastehr/mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "last-ehr": {
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ],
      "env": {
        "MEDPLUM_ACCESS_TOKEN": "your-value",
        "MEDPLUM_CLIENT_ID": "your-value",
        "MEDPLUM_CLIENT_SECRET": "your-value",
        "MEDPLUM_BASE_URL": "your-value",
        "LASTEHR_BACKEND": "your-value",
        "LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS": "your-value",
        "LASTEHR_CLIENT_ID": "your-value",
        "LASTEHR_PRIVATE_KEY": "your-value",
        "LASTEHR_PRIVATE_KEY_PATH": "your-value",
        "LASTEHR_KEY_ID": "your-value",
        "LASTEHR_JWKS_URL": "your-value",
        "LASTEHR_SCOPES": "your-value",
        "LASTEHR_FHIR_BASE_URL": "your-value",
        "LASTEHR_TOKEN_URL": "your-value",
        "LASTEHR_ENCOUNTER": "your-value",
        "LASTEHR_PERFORMER": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "last-ehr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ],
      "env": {
        "MEDPLUM_ACCESS_TOKEN": "your-value",
        "MEDPLUM_CLIENT_ID": "your-value",
        "MEDPLUM_CLIENT_SECRET": "your-value",
        "MEDPLUM_BASE_URL": "your-value",
        "LASTEHR_BACKEND": "your-value",
        "LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS": "your-value",
        "LASTEHR_CLIENT_ID": "your-value",
        "LASTEHR_PRIVATE_KEY": "your-value",
        "LASTEHR_PRIVATE_KEY_PATH": "your-value",
        "LASTEHR_KEY_ID": "your-value",
        "LASTEHR_JWKS_URL": "your-value",
        "LASTEHR_SCOPES": "your-value",
        "LASTEHR_FHIR_BASE_URL": "your-value",
        "LASTEHR_TOKEN_URL": "your-value",
        "LASTEHR_ENCOUNTER": "your-value",
        "LASTEHR_PERFORMER": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

MEDPLUM_ACCESS_TOKEN 机密 env
FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action).
MEDPLUM_CLIENT_ID env
FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action).
MEDPLUM_CLIENT_SECRET 机密 env
FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action).
MEDPLUM_BASE_URL env
FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action).
LASTEHR_BACKEND env
epic, oracle, or smart. Requires LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS=1. Sandbox writes are approval-gated and persist because those sandboxes do not support delete.
LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS env
Set to 1 to enable LASTEHR_BACKEND epic, oracle, or smart.
LASTEHR_CLIENT_ID env
SMART Backend Services client id. Not a secret.
LASTEHR_PRIVATE_KEY 机密 env
PKCS#8 PEM for SMART private_key_jwt. Never log it.
LASTEHR_PRIVATE_KEY_PATH env
Path to the PKCS#8 PEM. Alternative to LASTEHR_PRIVATE_KEY.
LASTEHR_KEY_ID env
JWT kid. Must match the public JWKS.
LASTEHR_JWKS_URL env
https URL of the public JWKS. doctor checks that LASTEHR_KEY_ID is present. Optional.
LASTEHR_SCOPES env
Space-delimited SMART scopes. Required for Oracle. Omit for Epic unless overriding the app registration.
LASTEHR_FHIR_BASE_URL env
FHIR base URL. Epic and Oracle default to their public sandboxes when unset.
LASTEHR_TOKEN_URL env
SMART token URL. Epic and Oracle default to their public sandboxes when unset.
LASTEHR_ENCOUNTER env
Encounter/{id} added to Epic observations when the tool call omits encounter.
LASTEHR_PERFORMER env
Practitioner/{id} filed as legal authenticator on Oracle observations.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cbetz 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 870 个服务器的 0%
发布到注册中心的时间比此分类中其他 870 个服务器的 93% 更新
基础检查结果等于或优于此分类中其他 870 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Last EHR — Medplum 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：MEDPLUM_ACCESS_TOKEN, MEDPLUM_CLIENT_SECRET, LASTEHR_PRIVATE_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.5.1）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

作者：thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

在你的电脑上运行★ 1,408Apache-2.06天前更新

安装

FHIR MCP Server

作者：wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

在你的电脑上运行★ 137Apache-2.09天前更新

安装

Google Health MCP

作者：davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

在你的电脑上运行★ 79MIT4个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@lastehr/mcp

FHIR chart tools for MCP clients, over a Medplum project, the Last EHR repository's local HAPI evaluation stack (FHIR_BACKEND=hapi, synthetic data only), or — with LASTEHR_EXPERIMENTAL_FHIR_ADAPTERS=1 — the Epic and Oracle Health sandboxes (LASTEHR_BACKEND=epic|oracle) and a generic SMART Backend Services server (LASTEHR_BACKEND=smart). The sandboxes do not support delete, so an approved write persists. This is not a clinical or compliance claim.

Read-only by default, and the reads are the same ones the Last EHR web agent uses: search patients, show a whole chart, read any of 23 patient-scoped chart sections with filters, and read a document's text. One opt-in, LASTEHR_MCP_WRITES=proposal, adds elicitation-gated write proposals a human approves per action. Nothing is ever saved without that explicit approval, and the write tools are hidden from clients that cannot render approvals.

The registry metadata lives in server.json and is published alongside each verified npm release.

Install

npx -y @lastehr/mcp init

The command prints a portable MCP configuration. For Claude Code, print the registration command instead:

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

Start the stdio server with:

npx -y @lastehr/mcp

Check the installed package version without configuring a backend:

npx -y @lastehr/mcp --version

Configuration

Set one authentication method before starting the server:

MEDPLUM_ACCESS_TOKEN=...

or:

MEDPLUM_CLIENT_ID=...

MEDPLUM_CLIENT_SECRET=...

Set MEDPLUM_BASE_URL for a self-hosted Medplum deployment. For the repository's local no-auth HAPI stack, set FHIR_BACKEND=hapi and FHIR_BASE_URL (or HAPI_BASE_URL) instead — local, synthetic data only. Run npx -y @lastehr/mcp doctor to validate configuration without starting MCP.

In 0.4.0, doctor --connect also checks FHIR R4 metadata and a count-only Patient search for the stdio backend. It makes no chart write and prints no patient data or counts. This does not verify individual chart access, other resource permissions, write permissions, or the MCP client's approval support. HTTP mode remains configuration-only; its --connect check fails explicitly rather than treating a configured URL as a verified OAuth session.

The source checkout can be ahead of npm. Check the installed version with --version. The repository's release process tests the packed artifact in a clean directory before publication.

Safety boundary

By default the package exposes search_patients, show_patient_info, read_chart_section, and read_document, all with the MCP readOnlyHint.

Those reads share one implementation with the web agent, which is deliberate: each of their honesty properties came from a real false negative found against a live FHIR server, and a second implementation would have re-earned them. A reply tells you what it could not see, and an empty result is never proof of absence:

Field	Meaning
`truncated`	The server's window came back full, so older records may exist beyond what was read. Measured at the window, not at the row count.
`codeFilterUnmatched`	The section does hold records; none of them carry the code you filtered by. Text-only `CodeableConcept`s cannot match a coded search.
`includeUnsupported`	The backend refused the reference lookup. Not the same as there being no references.
`unreadable` (documents)	The document exists and its contents were not read: a scan, or a body stored as a pointer rather than inline.

Chart free text arrives wrapped in tags. That content is data, never instructions. read_document decodes an inline text attachment and never dereferences Attachment.url, so it makes no request to an address the FHIR server chose.

With LASTEHR_MCP_WRITES=proposal it additionally offers add_note, record_observation, record_superseding_observation, and create_task as proposals: the exact fields are shown to the human through MCP elicitation and nothing is saved unless they approve; every approved write is tagged https://lastehr.com/mcp|approved-proposal and carries the standard AIAST security label ("Artificial Intelligence asserted") in meta.security, and LASTEHR_WRITE_PROVENANCE=true also emits a Provenance resource naming the agent as author and the reviewer as verifier. Read access can still return PHI. Use a least-privilege identity, review the MCP client's data handling and model-provider agreements, and never treat this package as an authorization layer.

See https://www.lastehr.com/docs/mcp for the complete setup and support boundary.