Why this server?
This server is explicitly designed for communication with Electronic Health Records (EHR) using SMART on FHIR, which is the standard for secure access to EHR data. This aligns directly with the user's request to interact with EHR systems like Epic via FHIR API.
Alicense-qualityCmaintenanceA Model Context Protocol server that connects AI tools to Electronic Health Records using SMART on FHIR, allowing secure searching, querying, and analysis of patient data from compatible EHRs.Last updated76MITWhy this server?
This TypeScript-based MCP server directly connects to FHIR servers, allowing access to healthcare data using FHIR URIs, and providing FHIR resource search capabilities, fulfilling the FHIR API aspect of the user's query.
Alicense-quality-maintenanceA TypeScript-based MCP server that connects to FHIR servers, allowing access to healthcare data via fhir:// URIs and providing search capabilities for FHIR resources.Last updated65Why this server?
This server offers standardized interaction with Azure Health Data Services FHIR servers, enabling healthcare data operations specifically through MCP tools, making it relevant for accessing EHR data within the Azure ecosystem.
AlicenseAqualityCmaintenanceA Model Context Protocol server that enables standardized interaction with Azure Health Data Services FHIR servers, allowing healthcare data operations through MCP tools.Last updated118MIT