/ 디렉터리 / 플레이그라운드 / FHIR MCP Server
● 커뮤니티 the-momentum ⚡ 바로 사용

FHIR MCP Server

제작: 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.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

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
흐름
  1. Get the patient
    Find Patient with identifier MRN-12345 and return name, DOB, and active conditions.✓ 복사됨
    → One Patient + Condition list
  2. 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와 조합해 10배 효율

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
호출당 토큰
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-serverYou're on the WSO2 stackTighter WSO2 integration

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기