Connector guide2-minute read10 MCP toolsEN · DE · IT

FHIR R4 zu MCP — FHIR R4 aus jedem KI-Agent steuern

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.

HCBy HelpCode teamAktualisiert 2 min read Open Source auf GitHub

Keine Kreditkarte · 7 Tage Test · Self-Hosting-Alternative verfügbar

FHIR R4

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.

Tools

10

Region

INTL

Kategorie

Healthcare

Authentifizierung

Bearer Token

Benötigte Env-Vars

FHIR_BASE_URLFHIR_ACCESS_TOKEN
Mit einem Klick in der Cloud installieren

7 Tage kostenlos testen · Keine Kreditkarte

  • 7 Tage kostenlos
    Keine Kreditkarte nötig
  • GDPR & SOC 2 ready
    EU-Datenhaltung, Audit-Logs
  • Open Source auf GitHub
    Open-Source · AGPL-3.0
  • Funktioniert mit ChatGPT, Claude, Gemini
    Jeder MCP-kompatible Client

Installation überspringen. In unter 2 Minuten einsatzbereit.

Starte eine kostenlose Testphase auf cloud.anythingmcp.com, füge FHIR R4 mit einem Klick hinzu und richte deinen KI-Client (Claude, ChatGPT, Copilot oder Cursor) auf den erzeugten MCP-Endpoint. Kein Docker, kein git clone, keinerlei Entwicklungserfahrung nötig.

Kostenlos testen

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.

Frag einfach

Beispiel-Prompts für FHIR R4

Klick auf einen Prompt, um ihn zu kopieren. In Claude, ChatGPT, Cursor, Gemini, Copilot oder OpenClaw einfügen — und gegen diesen Connector laufen lassen.

FHIR R4 · live via MCP
Teilen
Opus 4.7

Claude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.

💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → FHIR R4 klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein git clone, kein lokaler Server.

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.

Einrichtung

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.

  1. Set FHIR_BASE_URL to the server's base, the URL that answers /metadata. No trailing slash.
  2. Set FHIR_ACCESS_TOKEN to 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)

Voraussetzungen: FHIR_BASE_URL, FHIR_ACCESS_TOKEN

Connector lokal installieren

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

Öffne http://localhost:3000/connectors/store, wähle FHIR R4 und trage die unter Voraussetzungen aufgelisteten Variablen ein.

Verfügbare Tools

ToolWhat it does
fhir_get_capability_statementRead the server's CapabilityStatement: which resource types it holds, which interactions and search parameters each supports, and its FHIR v
fhir_searchSearch any resource type with FHIR's standard parameters
fhir_read_resourceRead one resource instance by type and id, returning the full resource rather than a Bundle entry
fhir_search_patientsSearch Patients by name, identifier, birth date or family name
fhir_get_patient_observationsRead the Observations recorded for one patient — vital signs, laboratory results, measurements — optionally narrowed to one LOINC code or ca
fhir_get_patient_conditionsRead the Conditions recorded for one patient — the problem list — with their clinical and verification status
fhir_get_patient_encountersRead the Encounters for one patient — admissions, visits and consultations — with their class, period and the practitioners involved
fhir_get_patient_medicationsRead the MedicationRequests for one patient — what has been prescribed, in what dosage, by whom and with what status
fhir_get_patient_reportsRead the DiagnosticReports for one patient — laboratory panels, imaging reports and pathology — with their category, status and conclusions
fhir_get_patient_everythingRun the $everything operation on one patient: every resource the server associates with them, in one Bundle

Nächste Schritte

War dieser Guide hilfreich?

Your FHIR R4 agent is one click away.

Install the connector, paste the key, prompt any MCP client. Free for 7 days, no credit card.

Verwandte Anleitungen

connectors

FHIR R4 mit ChatGPT verbinden — über MCP

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.

connectors

FHIR R4 mit Claude verbinden — über MCP

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.

connectors

FHIR R4 mit Cursor verbinden — über MCP

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.

connectors

FHIR R4 mit Gemini verbinden — über MCP

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.

connectors

AFAS Profit zu MCP — AFAS Profit aus jedem KI-Agent steuern

AFAS Profit — Dutch ERP and HR: read any published GetConnector, list what is available, and inspect a connector's metadata. Token auth with AFAS's base64-wrapped XML token.

connectors

Aruba Fatturazione Elettronica zu MCP — Aruba Fatturazione Elettronica aus jedem KI-Agent steuern

Aruba Fatturazione Elettronica: send and track Italian e-invoices through the Sistema di Interscambio, read received invoices and their SDI notifications. Token auth against Aruba's B2B gateway.