violet-fhir
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@violet-fhirList all medications for patient 123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
violet-fhir
Status: Pre-build — the MCP tool layer is in progress. Nothing here works yet.
1. What this is
A FHIR data substrate plus a guideline retrieval layer, connected by an agent loop.
Two halves:
Context layer — an MCP server exposing a FHIR endpoint as deterministic tools. Read-only. This is the foundation everything else sits on.
Guideline layer — retrieval with citations over public clinical practice guidelines. Never sees patient data.
The output is always a cited draft for a pharmacist, never an assertion and never an action.
Related MCP server: FhirMCP
2. Why it exists
A portfolio artifact that demonstrates MCP, RAG, agent loops, and A2A in a clinical context.
VA/DoD Clinical Practice Guidelines are authoritative, freely published documents — and they live as PDFs. A June 2026 VA OIG review of generative AI chat tools in clinical use found that VA does not curate the prompts staff use for clinical care and documentation, with sharing happening informally instead. The demand for AI assistance at the point of care is real and already being met without provenance. VA OIG 26-00182-140
3. What this is NOT
Not clinical decision support. This is retrieval with provenance. The pharmacist remains the decision-maker; the system's job is to show its work.
Not write-enabled. Read-only against FHIR. No order placement, no chart write-back, ever.
Not PHI-touching in development. Synthetic data only (SMART sandbox, HAPI public server, Synthea).
Not a product. Portfolio artifact and community contribution. If it becomes a product later, that's a separate decision made on purpose.
This server cannot be deployed
Maintenance
Related MCP Connectors
- mcpOAuthcom.medplum
Securely access and manage FHIR healthcare data stored in Medplum.
Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.
Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Read-only U.S. lab-test catalog, collection-site search, and reference-range context.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables seamless integration with FHIR APIs for healthcare applications, allowing users to search, retrieve, create, update, and analyze clinical information through natural language interactions. Supports SMART-on-FHIR authentication and works with various healthcare systems like EPIC and HAPI FHIR servers.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.MIT
- FlicenseAqualityDmaintenanceProvides read/write access to any FHIR-compliant healthcare API with built-in validation, supporting resource management, search operations, and granular permissions through natural language.51-
- AlicenseAqualityCmaintenanceProvides seamless integration with FHIR APIs, enabling AI/LLM tools to search, retrieve, and analyze clinical healthcare data with support for SMART-on-FHIR authentication and multiple transport protocols.7120 PyPI134Apache 2.0