Agent Care: An MCP Server for EMRs like Cerner and Epic
A Model Context Protocol (MCP) server that provides healthcare tools and prompts for interacting with FHIR data and medical resources on EMRs like Cerner and Epic using Claude Desktop and Goose Desktop.
Demo
Features
- EMR integrartion using SMART on FHIR APIs
- Uses OAuth2 to authenticate with EMRs
- Anthropic Claude Desktop integration
- Medical research integration (PubMed, Clinical Trials, FDA)
- Response caching
- Error handling
- Null-safe data formatting
- Comprehensive clinical analysis
Screenshots
Tools
FHIR Tools
find_patient- Search for a patient by name, DOB, or other identifiers
get_patient_observations- Retrieve patient observations/vital signs
get_patient_conditions- Get patient's active conditions
get_patient_medications- Get patient's current medications
get_patient_encounters- Get patient's clinical encounters
get_patient_allergies- Get patient's allergies and intolerances
get_patient_procedures- Get patient's procedures
get_patient_careteam- Get patient's care team members
get_patient_careplans- Get patient's active care plans
get_vital_signs- Get patient's vital signs
get_lab_results- Get patient's laboratory results
get_medications_history- Get patient's medication history
clinical_query- Execute custom FHIR queries
Medical Research Tools
search-pubmed- Search PubMed articles related to medical conditions
search-trials- Find relevant clinical trials
drug-interactions- Check drug-drug interactions
Usage
Each tool requires specific parameters:
Required Parameters
- Most tools require
patientId
- Some tools have additional parameters:
Development Configuration
- To use with Cerener: Go to https://code-console.cerner.com and create a sandbox account, create a new provider app and get the clientId/secret. (note: ec2458f2-1e24-41c8-b71b-0e701af7583d below is the tenant id for cerner developer sandbox)
- To use with Epic: Go to https://fhir.epic.com/Developer/Apps , sign up as developer and create a new app and get the clientId/secret.
- For PubMed, Clinical Trials and FDA, you need to get the API keys from the respective websites.
For local testing Create a
.env file in the root directory or use these environment variables in claude desktop launch configuration.Cerner
Epic
Start MCP Server Locally
Use claude desktop
Use MCP Inspectopr
(MCP Server using inspector. Make sure to update the .env file with the correct values.)
Test User Logins
(commonly used for sandbox/dev)
- Cerner: portal | portal
- Epic: FHIRTWO | EpicFhir11!
Troubleshooting:
If Claude desktop is running it uses port 3456 for Auth. You need to terminate that process using the following command:
Use Goose
Goose is an open Source AI Agent frameowrk from Block(Stripe) that works with MCP servers. Goose Desktop is like Claude Desktop that can work with MCP servers. But Goose can be configured to use models other than Anthropic as well. More info: https://block.xyz/inside/block-open-source-introduces-codename-goose
See below how Goose Desktop works with Agent Care:
(goose extension will be configured with command:
/Users/your-username/{agentcare-download-path}/agent-care-mcp/build/index.js)
Agent Care: An MCP Server for EMRs like Cerner and Epic
A Model Context Protocol (MCP) server that provides healthcare tools and prompts for interacting with FHIR data and medical resources on EMRs like Cerner and Epic using Claude Desktop and Goose Desktop.
Demo
Features
- EMR integrartion using SMART on FHIR APIs
- Uses OAuth2 to authenticate with EMRs
- Anthropic Claude Desktop integration
- Medical research integration (PubMed, Clinical Trials, FDA)
- Response caching
- Error handling
- Null-safe data formatting
- Comprehensive clinical analysis
Screenshots
Tools
FHIR Tools
find_patient- Search for a patient by name, DOB, or other identifiers
get_patient_observations- Retrieve patient observations/vital signs
get_patient_conditions- Get patient's active conditions
get_patient_medications- Get patient's current medications
get_patient_encounters- Get patient's clinical encounters
get_patient_allergies- Get patient's allergies and intolerances
get_patient_procedures- Get patient's procedures
get_patient_careteam- Get patient's care team members
get_patient_careplans- Get patient's active care plans
get_vital_signs- Get patient's vital signs
get_lab_results- Get patient's laboratory results
get_medications_history- Get patient's medication history
clinical_query- Execute custom FHIR queries
Medical Research Tools
search-pubmed- Search PubMed articles related to medical conditions
search-trials- Find relevant clinical trials
drug-interactions- Check drug-drug interactions
Usage
Each tool requires specific parameters:
Required Parameters
- Most tools require
patientId
- Some tools have additional parameters:
Development Configuration
- To use with Cerener: Go to https://code-console.cerner.com and create a sandbox account, create a new provider app and get the clientId/secret. (note: ec2458f2-1e24-41c8-b71b-0e701af7583d below is the tenant id for cerner developer sandbox)
- To use with Epic: Go to https://fhir.epic.com/Developer/Apps , sign up as developer and create a new app and get the clientId/secret.
- For PubMed, Clinical Trials and FDA, you need to get the API keys from the respective websites.
For local testing Create a
.env file in the root directory or use these environment variables in claude desktop launch configuration.Cerner
Epic
Start MCP Server Locally
Use claude desktop
Use MCP Inspectopr
(MCP Server using inspector. Make sure to update the .env file with the correct values.)
Test User Logins
(commonly used for sandbox/dev)
- Cerner: portal | portal
- Epic: FHIRTWO | EpicFhir11!
Troubleshooting:
If Claude desktop is running it uses port 3456 for Auth. You need to terminate that process using the following command:
Use Goose
Goose is an open Source AI Agent frameowrk from Block(Stripe) that works with MCP servers. Goose Desktop is like Claude Desktop that can work with MCP servers. But Goose can be configured to use models other than Anthropic as well. More info: https://block.xyz/inside/block-open-source-introduces-codename-goose
See below how Goose Desktop works with Agent Care:
(goose extension will be configured with command:
/Users/your-username/{agentcare-download-path}/agent-care-mcp/build/index.js)