Can I search for a patient and instantly see their full medical timeline?

Yes! Use `search_patients` with name or MRN to find the patient, then chain `list_encounters`, `list_conditions`, and `list_medications` to build a full clinical picture. Your agent compiles everything in seconds — no chart-clicking required.

How do I prepare a patient summary before a care coordination meeting?

Ask your agent to pull everything at once: 'Show me the full medical history for patient ID abc123.' It will call `get_patient` for demographics, `list_conditions` for active diagnoses, `list_medications` for current prescriptions, and `list_allergies` for safety alerts — delivering a structured briefing ready for your meeting.

Is this integration read-only? Can it modify patient data?

This integration is entirely read-only. All 10 tools are query operations — search, list, and retrieve. No tool can create, update, or delete any clinical data. Your Epic FHIR access token controls exactly which patients and resources are visible, enforcing your existing HIPAA access controls.

Epic Fhir MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Epic Fhir
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Epic Fhir through Vinkius, pass the Edge URL in the `mcps` parameter and every Epic Fhir tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Epic Fhir Specialist",
    goal="Help users interact with Epic Fhir effectively",
    backstory=(
        "You are an expert at leveraging Epic Fhir tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Epic Fhir "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Epic Fhir MCP Server

Connect Epic electronic health records to any AI agent and query clinical data through natural conversation instead of navigating complex EHR interfaces.

When paired with CrewAI, Epic Fhir becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Epic Fhir tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Patient Search — Find patients by name, date of birth, or medical record number across your Epic system
Clinical Encounters — Review admissions, ER visits, and outpatient appointments with dates, reasons, and locations
Lab Results & Vitals — Pull observations including blood work, vital signs, and social history with reference ranges
Diagnoses & Conditions — List active and resolved conditions with ICD-10 codes, onset dates, and severity
Medications & Allergies — View current prescriptions, dosage instructions, and documented allergic reactions
Appointments & Immunizations — Check upcoming schedules and full vaccination history with lot numbers

The Epic Fhir MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Epic Fhir to CrewAI via MCP

Follow these steps to integrate the Epic Fhir MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Epic Fhir

Why Use CrewAI with the Epic Fhir MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Epic Fhir through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Epic Fhir + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Epic Fhir MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Epic Fhir for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Epic Fhir, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Epic Fhir tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Epic Fhir against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Epic Fhir MCP Tools for CrewAI (10)

These 10 tools become available when you connect Epic Fhir to CrewAI via MCP:

get_patient

Returns name, DOB, gender, race, ethnicity, address, phone, email, and all identifiers. Get patient details by ID

list_allergies

Includes substance, reaction type, severity, and clinical status. List allergies and intolerances

list_appointments

Includes date/time, provider, location, and status. List patient appointments

list_conditions

Includes ICD-10 codes, clinical status, verification status, onset date, and severity. List diagnoses and conditions

list_diagnostic_reports

Includes report type, results, conclusion, and performing organization. List diagnostic reports

list_encounters

Includes encounter type, period, reason, and location. List patient encounters/visits

list_immunizations

Includes vaccine type (CVX code), administration date, dose, site, and lot number. List immunizations

list_medications

Includes medication name, dosage, frequency, route, prescriber, and status. List medication requests

list_observations

Filter by category: vital-signs, laboratory, social-history. Includes values, units, reference ranges, and interpretation. List clinical observations

search_patients

Returns patient demographics including name, DOB, gender, address, and identifiers. Search patients by name, DOB, or MRN

Example Prompts for Epic Fhir in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Epic Fhir immediately.

"Find all patients named Smith born in 1985."

"Show me the latest lab results for patient e63wACU8F."

"List all active medications for this patient."

Troubleshooting Epic Fhir MCP Server with CrewAI

Common issues when connecting Epic Fhir to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Epic Fhir + CrewAI FAQ

Common questions about integrating Epic Fhir MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.