● 社群 the-momentum ⚡ 即開即用

FHIR MCP Server

Name: FHIR MCP Server MCP Server
Author: the-momentum

作者 the-momentum · the-momentum/fhir-mcp-server

Query and write to any FHIR-compliant healthcare server via MCP.

FHIR (Fast Healthcare Interoperability Resources) is the standard API for clinical data. This MCP lets Claude query any FHIR server — patient records, observations, medications — and follow the spec's resource references like a real EHR app.

▶ 觀看演示 📦 安裝 💡 使用場景

為什麼要用

核心特性

All FHIR R4/R5 resource types: Patient, Observation, MedicationRequest, etc.
Search by parameter (date range, code, identifier)
Reference traversal — follow Patient → Observation → Encounter chains
Bulk export for cohort queries
Works against any FHIR server (Epic, Cerner sandbox, HAPI, Aidbox)

即時演示

實際使用效果

fhir-mcp-server.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "fhir-mcp-server": {
      "command": "uvx",
      "args": [
        "fhir-mcp-server"
      ]
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "fhir-mcp-server": {
      "command": "uvx",
      "args": [
        "fhir-mcp-server"
      ]
    }
  }
}

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "fhir-mcp-server": {
      "command": "uvx",
      "args": [
        "fhir-mcp-server"
      ]
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "fhir-mcp-server": {
      "command": "uvx",
      "args": [
        "fhir-mcp-server"
      ]
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "fhir-mcp-server",
      "command": "uvx",
      "args": [
        "fhir-mcp-server"
      ]
    }
  ]
}

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

{
  "context_servers": {
    "fhir-mcp-server": {
      "command": {
        "path": "uvx",
        "args": [
          "fhir-mcp-server"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

claude mcp add fhir-mcp-server -- uvx fhir-mcp-server

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： FHIR MCP Server

Build a chronological clinical timeline for one patient

👤 Clinical informatics, research teams ⏱ ~15 min intermediate

何時使用： You need a summary of one patient's encounters, meds, and labs across visits.

前置條件

Server/skill installed and authenticated — See repo README

步驟

Get the patient

Find Patient with identifier MRN-12345 and return name, DOB, and active conditions.✓ 已複製

→ One Patient + Condition list
Build the timeline

Retrieve all Encounters and MedicationRequests for that patient in the last 12 months. Sort chronologically and summarize.✓ 已複製

→ Time-sorted list with encounter type + meds prescribed

結果： A clinician-readable summary you can paste into a chart note.

注意事項

Real PHI — Real PHI — never connect this to a chat that's also pasting screenshots to a third-party service. Use a HIPAA-compliant Claude deployment.

搭配使用： filesystem · memory

組合

與其他 MCP 搭配，撬動十倍槓桿

fhir-mcp-server + filesystem

Pair with filesystem for complementary capabilities

Use this server together with filesystem to complete a multi-step task.✓ 已複製

fhir-mcp-server + memory

Pair with memory for complementary capabilities

Use this server together with memory to complete a multi-step task.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫	成本
fhir_search	resource_type, params	Find resources matching criteria	1 API call
fhir_read	resource_type, id	Read one specific resource	1 API call
fhir_create	resource_type, body	Write a new clinical resource	1 API call

成本與限制

運行它的成本

API 配額: See provider docs for rate limits
每次呼叫 Token 數: Varies by tool
費用: See repo README for pricing details
提示: Cache tool results and avoid repeated identical calls.

安全

權限、密鑰、影響範圍

憑證儲存： Use environment variables; never commit secrets

資料出站： Tool calls go to the provider's API as documented

故障排查

常見錯誤與修復

401 from FHIR server

Most FHIR servers use SMART-on-FHIR. Generate a token via your EHR's auth flow and set FHIR_TOKEN.

驗證： fhir_search Patient?_count=1 returns a Bundle

Unsupported resource type

Different servers implement different subsets. Check the CapabilityStatement: GET /metadata.

驗證： Confirm the resource type is in CapabilityStatement.rest.resource

替代方案

FHIR MCP Server 對比其他方案

替代方案	何時用它替代	權衡
wso2/fhir-mcp-server	You're on the WSO2 stack	Tighter WSO2 integration

資源

📖 閱讀 GitHub 上的官方 README

🐙 查看未解決的 issue

🔍 瀏覽全部 400+ MCP 伺服器和 Skills