インストール不要。2分以内に動きます。
cloud.anythingmcp.com で無料トライアルを開始し、FHIR R4 をワンクリックで追加して、AI クライアント（Claude、ChatGPT、Copilot、Cursor）を生成された MCP エンドポイントに向けるだけ。Docker も git clone も、開発経験も不要です。
Summary
Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.
こう聞いてみよう
FHIR R4 のサンプルプロンプト
プロンプトをクリックでコピー。Claude / ChatGPT / Cursor / Gemini / Copilot / OpenClaw に貼り付けて、このコネクターで実行できます。
Claude は AI のため誤ることがあります。回答をご確認ください。
💡 インストール不要? cloud.anythingmcp.com を直接利用してください。 サインインし、Connectors → FHIR R4 をクリック、認証情報を貼り付け、MCP API キーを発行 — 完了です。Docker も
git cloneもローカルサーバーも不要。
FHIR R4
Any HL7 FHIR R4 server: search and read Patients, Observations, Conditions, Encounters, MedicationRequests, DiagnosticReports and any other resource type, plus the server's own capability statement. Bearer-token auth.
セットアップ
This is a generic FHIR R4 client, not a vendor connector. Point it at any R4 server — a hospital's HAPI instance, a national test server, a vendor's sandbox — and it speaks the standard.
- Set
FHIR_BASE_URLto the server's base, the URL that answers/metadata. No trailing slash. - Set
FHIR_ACCESS_TOKENto a bearer token. Most real deployments use SMART on FHIR, whose authorisation flow issues short-lived tokens; obtain one and paste it here, or use a long-lived service token if the server offers one. A server that needs no auth still needs a placeholder here — put anything.
…(continued in the in-app connector instructions)
前提条件: FHIR_BASE_URL, FHIR_ACCESS_TOKEN
ローカルでコネクタをインストール
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
http://localhost:3000/connectors/store を開き、 FHIR R4 を選択し、前提条件に記載された環境変数を入力します。
利用可能なツール
| Tool | What it does |
|---|---|
fhir_get_capability_statement | Read the server's CapabilityStatement: which resource types it holds, which interactions and search parameters each supports, and its FHIR v |
fhir_search | Search any resource type with FHIR's standard parameters |
fhir_read_resource | Read one resource instance by type and id, returning the full resource rather than a Bundle entry |
fhir_search_patients | Search Patients by name, identifier, birth date or family name |
fhir_get_patient_observations | Read the Observations recorded for one patient — vital signs, laboratory results, measurements — optionally narrowed to one LOINC code or ca |
fhir_get_patient_conditions | Read the Conditions recorded for one patient — the problem list — with their clinical and verification status |
fhir_get_patient_encounters | Read the Encounters for one patient — admissions, visits and consultations — with their class, period and the practitioners involved |
fhir_get_patient_medications | Read the MedicationRequests for one patient — what has been prescribed, in what dosage, by whom and with what status |
fhir_get_patient_reports | Read the DiagnosticReports for one patient — laboratory panels, imaging reports and pathology — with their category, status and conclusions |
fhir_get_patient_everything | Run the $everything operation on one patient: every resource the server associates with them, in one Bundle |
次のステップ
このガイドは役に立ちましたか?
