Skip to main content
Glama
Ath404

fhir-journey-mcp

by Ath404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fhir-journey-mcp

No user-submitted related servers found.

    Related Servers

    • LangCare MCP FHIR Server by mosaic-care

      LangCare MCP FHIR Serverofficial

      mosaic-care
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely interact with FHIR R4-based EMRs, supporting read, search, create, and update operations on any FHIR resource type across systems like Epic, Cerner, and OpenEMR.
      186 npm
      MIT

    • his-tools

      markl-a
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to query de-identified FHIR-shaped hospital data through audited, read-only tools for patients, encounters, conditions, observations, medications, and interaction checks, while any medication write stays a draft that a clinician must confirm out-of-band.
      MIT

    • FHIR MCP Server

      brianbastian01
      A
      license
      A
      quality
      C
      maintenance
      Provides safe read-only access to synthetic healthcare data via FHIR R4, enabling AI assistants to search patients, retrieve vitals, and summarize conditions using a public sandbox.
      4
      33 npm
      MIT

    • FHIR MCP Server

      sungchanmazur409
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents to connect to a FHIR-compliant healthcare backend and query or manipulate clinical data with natural-language prompts. Provides full CRUD operations on FHIR resources, AI-powered document ingestion and semantic search, RAG-ready retrieval, and LOINC terminology lookup.
      -

    • MCP FHIR Server

      mrosata
      F
      license
      A
      quality
      D
      maintenance
      Provides read/write access to any FHIR-compliant healthcare API with built-in validation, supporting resource management, search operations, and granular permissions through natural language.
      5
      1
      -

    • FHIR MCP Server

      the-momentum
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.
      13
      102
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct resource or workflow: patient search, patient timeline, appointment listing, open slots, and follow-up detection. The only mild overlap is that get_patient_journey already embeds a patient's appointments while list_appointments offers a filtered appointment view, so an agent could occasionally hesitate on which to use for appointment data.

    Naming Consistency5/5

    All tools use a uniform fhir_ prefix followed by a consistent verb_noun pattern (search_patients, get_patient_journey, list_appointments, find_open_slots, find_followups_due). The convention is predictable and readable throughout.

    Tool Count5/5

    Five tools is well-scoped for a focused patient-journey server; each one earns its place covering search, context, appointments, availability, and follow-up detection without redundancy.

    Completeness3/5

    The read-only surface covers discovery and identification well, but the implied workflow dead-ends: find_open_slots explicitly cannot hold or book, and find_followups_due returns patients to contact with no tool to actually schedule the follow-up. Booking/rescheduling operations are notable gaps for the scheduling workflow the tools describe.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources