Discovered via unknown and last synced 1mo ago.
Install instructions not detected yet
Check the source repository for the latest setup steps.
Healthcare software engineers and API developers building applications that integrate with FHIR-compliant systems. Clinical data managers and interoperability specialists who need programmatic access to standardized medical records. Backend developers working on health platforms benefit from having a structured interface to query, validate, and transform FHIR resources without manual protocol implementation.
Access patient data stored in FHIR format through Claude, enabling natural language queries against medical records. Useful for building clinical decision support tools or extracting relevant patient information for analysis.
Ensure medical data payloads conform to FHIR specifications before persisting to production systems. Helps catch schema violations and malformed resources early in the development pipeline.
Convert non-standard medical data formats into compliant FHIR resources. Facilitates data migration projects and system integration between healthcare platforms with different data models.
Leverage Claude's reasoning capabilities with structured medical data to generate clinical summaries, identify patterns, or support documentation automation within HIPAA-aware applications.
The MCP server provides FHIR data handling capabilities, but authentication and HIPAA compliance depend on your deployment context and how you configure access controls. You must implement security measures appropriate for handling protected health information in your own infrastructure.
Specific version support isn't detailed in the current documentation. Check the server's configuration options or repository to confirm which FHIR versions (R4, STU3, etc.) your deployment supports.
This MCP server handles FHIR data format translation and validation. Connecting to EHR systems requires those systems to expose FHIR APIs or implement FHIR export capabilities on their end; this server bridges Claude to FHIR-formatted data.
You'll run the MCP server locally or remotely, then configure Claude or your application to connect via the Model Context Protocol. Detailed setup instructions should be in the server's documentation or GitHub repository.
LOINC account password
Any FHIR Resource
Master encryption key
LOINC API search endpoint
Description
Pinecone API key
Hugging Face embedding model name
Retrieves metadata about a specified FHIR resource type, including its supported search parameters and custom operations.
The FHIR resource type name (e.g., "ServiceRequest", "Appointment", "HealthcareService").
A mapping of FHIR search parameter names to their desired values (e.g., {"category":"laboratory","issued:"2025-05-01"}).
Performs a FHIR "read" interaction to retrieve a single resource instance by its type and resource ID, optionally refining the response with search parameters or custom operations.
The name of a custom FHIR operation or extended query defined for the resource (e.g., "$expand").
Executes a FHIR "create" interaction to persist a new resource of the specified type.
Performs a FHIR "update" interaction by replacing an existing resource instance's content with the provided payload.
Execute a FHIR "delete" interaction on a specific resource instance.
The logical ID of a specific FHIR resource instance.
Executes a standard FHIR search interaction on a given resource type, returning a bundle or list of matching resources.
The complete JSON representation of the FHIR resource, containing all required elements and any optional data.
Observation
Manage FHIR DocumentReference resources
<p align="right">(<a href="#readme-top">back to top</a>)</p> ## 🛠️ MCP Tools The FHIR MCP Server provides a comprehensive set of tools for interacting with FHIR resources and document management: ### FHIR Resource Tools
Medication
Performs semantic search across indexed documents using vector embeddings
Condition
Ingests documents into the vector database for semantic search
AllergyIntolerance
Encounter
Retrieves standardized LOINC codes for medical observations and laboratory tests
Patient
Description
No
Immunization
FamilyMemberHistory
accepts a raw LOINC code (`8867-4`) **or** a friendly name
(Optional) An array of FHIRPath expressions (e.g., `["Patient.name", "Observation.valueQuantity"]`) to filter the returned single resource (or entries when using custom operations like `$everything`).
Retrieves the currently authenticated user's FHIR resource (for example the linked `Patient` resource) and returns a concise profile containing available demographic fields such as `id`, `name`, and `birthDate`.