Inspiration
New technology (MCP) becoming popular. FHIR standard is complicated, because every field is optional, so it’s hard to handle all cases in API. MCP is perfect here, because AI is much better at choosing which tool (endpoint) to use and which parameters should be included.
What it does
FHIR MCP Server implements a complete Model Context Protocol (MCP) server, designed to facilitate seamless interaction between LLM-based agents and a FHIR-compliant backend. It provides a standardized interface that enables full CRUD operations on FHIR resources through a comprehensive suite of tools - accessible from MCP-compatible clients such as Claude Desktop, allowing users to query and manipulate clinical data using natural-language prompts.
How I built it
With FastMCP framework and microservice architecture.
Challenges I ran into
The hardest part is authorization and authentication with external EHR. Claude Desktop have a lot of issues with Auth Discovery (someone said it’s not supported at all).
Accomplishments that I'm proud of
Learning how to build MCP servers, when it was still an early concept.
What I learned
Building MCP servers, how tools work, FHIR data format, OAuth standard deeper understanding, how EHR works.
What's next for FHIR MCP Server
We need to solve Authorization issues somehow to make this server available as an embedded solution for medical systems (like CDSS).
Log in or sign up for Devpost to join the conversation.