fhir-journey-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FHIR_TOKEN | No | Bearer token used to authenticate with the configured FHIR server. | |
| FHIR_BASE_URL | No | The base URL of the FHIR R4 server. If unset, the public HAPI test server is used, which holds synthetic data only. | https://hapi.fhir.org/baseR4 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fhir_search_patientsA | Find patients by name, phone, identifier (e.g. MRN or ABHA number, as |
| fhir_get_patient_journeyA | One patient's encounters and appointments merged into a dated timeline, plus when they were last seen, their next upcoming appointment, and no-show/cancellation counts. Use this before contacting a patient so the agent knows their context. |
| fhir_list_appointmentsA | Appointments filtered by patient, practitioner, status and date range, soonest first. At least one of patientId, practitionerId, from or tag is required. |
| fhir_find_open_slotsA | Free Slots in a date range, earliest first, for one practitioner or one schedule. Defaults to the next 7 days. Read-only: it does not hold or book the slot. |
| fhir_find_followups_dueA | Finished encounters that ended in a date range with no live follow-up appointment booked within |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.