Works with EPIC, Cerner, and any FHIR R4 system.
Works with EPIC, Cerner, and any FHIR R4 system.
AI Agents shipped faster. Developers skip the FHIR plumbing. Clinicians build Agents.
Agents shipped faster. Developers skip FHIR plumbing. Clinicians build Agents.
⭐ New: LangCare now supports Claude Managed Agents (CMA), Claude MCP Apps, Voice AI Agents and CLI
One MCP server. Any FHIR backend. Every AI agent. Connect Claude, ChatGPT, Gemini, or your custom agent to clinical data in minutes.
Connect to EPIC, Cerner, GCP Healthcare API, or any FHIR R4 server with automatic OAuth2 and SMART on FHIR authentication.
PHI scrubbing, TLS 1.3, OAuth 2.0, audit logging, and zero persistent storage. Stateless proxy architecture by design.
Read, search, create, and update any of the 60+ FHIR R4 resource types including Patient, Observation, and MedicationRequest.
Evidence-based workflow guides for medication management, lab interpretation, clinical decision support, and specialty care.
Enterprise-grade performance. Works with Claude, ChatGPT, Gemini, and any AI agent. Supports stdio and HTTP/SSE transports.
MIT licensed and community-driven. Fully extensible for custom workflows, new FHIR providers, and integrations.
Whether you're building healthcare AI products, deploying clinical agents, or creating your own workflows.
Build clinical applications with FHIR data access out of the box. Use the 4 generic MCP tools to read, search, create, and update any FHIR resource.
Build your own agentic workflows in Claude, ChatGPT, or Gemini — no coding required. Use 40+ ready-made clinical skills.
Deploy a HIPAA-compliant MCP server on your infrastructure. Supports Kubernetes, Docker, and managed hosting with full audit logging.
Three steps to connect any AI agent to your FHIR-based EMR system.
Global install via npm and start the server.
Point to your FHIR backend with a simple YAML.
Add to your AI agent's MCP config and restart.
Agent-agnostic workflow guides built on USPSTF, ADA, ACC/AHA, CDC, and other society guidelines.
Med reconciliation, drug interactions, adherence tracking, Beers Criteria, opioid risk
Lab interpretation, critical values, pre-op labs, diabetes panels, renal function
Sepsis scoring, cardiovascular risk, VTE assessment, fall risk, pneumonia severity
SOAP notes, H&P, progress notes, discharge summaries, procedure documentation
Panel management, quality measures, chronic disease registries, preventive care
Discharge planning, referrals, care gaps, transitions of care, follow-up tasks
Demographics, clinical summaries, problem list audits, allergy reviews, insurance
Prenatal care, pediatric growth, mental health screening, oncology staging, chronic pain
Stateless proxy architecture with enterprise-grade security at every layer.
End-to-end encryption for all HTTP transport communications
HIPAA-compliant audit trail for every FHIR operation with PHI scrubbing
Native support for EPIC, Cerner, and standard OAuth2
Stateless proxy — no patient data is ever stored
Rich clinical dashboards that render directly inside MCP-capable hosts like Claude Desktop. No LLM round-trips — apps call FHIR tools directly and deterministically.
Full clinical dashboard with demographics, active conditions, medications, allergies, vitals trend charts (BP + weight), labs, and recent encounters — all in one view.
Interactive FHIR resource browser. Search, read, create, and update any of the 60+ FHIR R4 resource types with JSON detail views and inline editing.
SVG charts, color-coded cards, expandable detail panels
Search fields, date pickers, click-to-expand rows
Apps call FHIR tools directly — no LLM in the data loop
Single HTML file, embedded in the Go binary
No CDN, no external scripts — just FHIR API calls
Build your own apps with React + TypeScript, compiled with Vite
MCP Apps are the first official extension to the Model Context Protocol — pushing MCP beyond text into true interactive experiences. The interface comes to the conversation, not the other way around.
Patients talk to their health records over phone or browser. Built on PipeCat, powered by Claude, with FHIR R4 access via LangCare MCP.
Five layers, three auth boundaries. Speech flows through DeepGram STT → Claude → Cartesia TTS while clinical data is fetched from your EMR via LangCare MCP — all in real time.
WebRTC, PSTN dial-in, or native app — patients connect however they prefer
DeepGram STT → Claude LLM → Cartesia TTS — orchestrated in real time
Claude reasons over the request and calls FHIR tools for labs, meds, conditions
FHIR R4 operations over Streamable HTTP to EPIC, Cerner, or any FHIR server
Pre-authenticated, DOB verification, or unknown caller — automatic patient matching
"What were my last lab results?" — patients ask in plain language, get spoken answers
Labs, meds, conditions, allergies, vitals — fetched and spoken in seconds
DeepGram, Google, Azure STT — Claude, Gemini, OpenAI — Cartesia, ElevenLabs TTS
PipeCat Cloud, GCP Cloud Run, GKE, or any container platform
Genesys AudioHook, PSTN dial-in, contact center integration
LangCare's 40 clinical skills run natively as CMA custom skills — progressive disclosure, versioning, and composability on Anthropic's managed agent platform. 9 lean agents, each referencing 5 skills, connected to your EMR via the LangCare MCP Server. Read More →
| Concept | Description |
|---|---|
| Agent | The model, system prompt, tools, MCP servers, and skills. 9 lean agents — one per clinical category + 1 general triage agent. |
| Environment | A configured container template with packages, network access to the LangCare MCP Server, and mounted files. |
| Session | A running agent instance within an environment, performing a specific clinical task and generating outputs. |
| Skills | 40 CMA custom skills mapped from LangCare's Clinical Skills Library — progressive disclosure, versioned, workspace-wide. |
| MCP Connector | Connects agents to the LangCare MCP Server for fhir_search, fhir_read, fhir_create, and fhir_update operations. |
40 clinical skills with progressive disclosure — metadata always loaded, instructions on demand
No agent loop to build — Anthropic handles tool execution, sandboxing, and runtime
Agents connect to LangCare MCP for real-time FHIR R4 access to your EMR
Orchestrate specialist agents — medication, labs, CDS — in a single session thread
One agent per category: meds, labs, CDS, docs, population health, care coord, specialty
Vaults for credentials, isolated containers, HIPAA-compliant audit trail
Wraps 4 FHIR operations as CLI subcommands over HTTP, handling the MCP session handshake internally. Built for AI agents that don't speak MCP natively — LangChain, smolagents, CrewAI, AutoGen, and any framework that can call a subprocess.
Start free with the full-featured open source server. Scale with enterprise support when you need it.
Join healthcare organizations worldwide using LangCare to connect AI agents to FHIR-based EMRs.