io.github.langcare/langcare-mcp-fhir
An MCP FHIR server written in Go for EMR systems like Epic and Cerner
Ask AI about io.github.langcare/langcare-mcp-fhir
Powered by Claude Β· Grounded in docs
I know everything about io.github.langcare/langcare-mcp-fhir. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
LangCare MCP FHIR Server
Enterprise-grade MCP Server for FHIR-based EMRs. Fully written in Go with enterprise-grade security and 4 generic FHIR operations that work with any FHIR R4 resource type. Supports EPIC, Cerner, OpenEMR, GCP Healthcare API, and any generic FHIR R4 server.
Ships with a 40+ Clinical Skills Library β agent-agnostic workflow guides covering medication management, lab interpretation, clinical decision support, documentation, population health, and more. Extend with β¨ New: Claude Managed Agents (9 production-ready clinical AI agents on the Anthropic Managed Agents API), MCP Apps (interactive clinical UIs inside Claude Desktop), a Healthcare Voice Agent (real-time voice AI over FHIR), and a LangCare CLI for agent frameworks that don't speak MCP natively.
Installation
Install via npm:
npm install -g @langcare/langcare-mcp-fhir
Or use directly without installation:
npx @langcare/langcare-mcp-fhir -config /path/to/config.yaml
Quick Configuration
LangCare MCP FHIR connects Claude to your FHIR-based EMR system. You need a YAML configuration file pointing to your backend.
1. Get a Config Template
Choose your backend:
- EPIC: config.epic.example.yaml
- Cerner: config.cerner.example.yaml
- OpenEMR: config.openemr.example.yaml
- GCP Healthcare API: config.gcp.example.yaml
- Any FHIR R4 Server: config.base.example.yaml
2. Configure Claude Desktop
Add to your Claude Desktop config file (~/.config/Claude/claude_desktop_config.json):
{
"mcpServers": {
"langcare-mcp-fhir": {
"command": "langcare-mcp-fhir",
"args": ["-config", "/path/to/your/config.yaml"]
}
}
}
On macOS, the config is typically at:
~/Library/Application\ Support/Claude/claude_desktop_config.json
3. Restart Claude Desktop
Close and reopen Claude Desktop. The FHIR tools will now be available.
Need detailed setup help? See the Local Testing Guide.
Architecture
This MCP server acts as an intelligent proxy between AI agents and FHIR R4 servers. It exposes 4 generic FHIR operations through the Model Context Protocol (MCP), enabling AI-powered workflows for any FHIR resource type.
Key Design:
- MCP SDK: Official
github.com/modelcontextprotocol/go-sdk(Anthropic/Google maintained) - FHIR Client: Generic HTTP client working with any FHIR R4 server
- Transport: stdio and Streamable HTTP
- Backend: Proxy to existing FHIR server (no database)
- Language: 100% Go for high performance and reliability
4 Generic MCP Tools
All tools work with any FHIR resource type (Patient, Observation, Medication, etc.):
1. fhir_read
Read a FHIR resource by type and ID.
{
"resourceType": "Patient",
"id": "example-123"
}
2. fhir_search
Search FHIR resources with query parameters.
{
"resourceType": "Patient",
"queryParams": "name=John&birthdate=gt1990-01-01"
}
3. fhir_create
Create a new FHIR resource.
{
"resourceType": "Observation",
"resource": {
"resourceType": "Observation",
"status": "final",
"code": { ... },
"subject": { "reference": "Patient/123" }
}
}
4. fhir_update
Update an existing FHIR resource.
{
"resourceType": "Patient",
"id": "example-123",
"resource": {
"resourceType": "Patient",
"id": "example-123",
"name": [{ "family": "Smith" }]
}
}
Security Architecture
LangCare MCP FHIR implements a two-layer security model for HIPAA-compliant healthcare data access:
βββββββββββββββ ββββββββββββββββ βββββββββββββββ
β Claude β Auth1 β MCP Server β Auth2 β FHIR API β
β Client ββββββββββΆβ (Go) ββββββββββΆβ (EMR) β
βββββββββββββββ ββββββββββββββββ βββββββββββββββ
Auth1: MCP Client Authentication (Bearer Token/API Key)
Auth2: FHIR Backend Authentication (Bearer/OAuth2/SMART on FHIR)
Security Features
- β TLS 1.3 encryption for HTTP transport
- β PHI Scrubbing in logs (enabled by default)
- β HIPAA-compliant audit logging
- β No persistent PHI storage (stateless proxy)
- β Secrets via environment variables (never in config files)
- β OAuth 2.0 with automatic token refresh
- β mTLS support for service-to-service communication
- β Rate limiting per client
Supported Authentication Methods
- Bearer Token - Simple API key authentication
- OAuth2 - Full OAuth2 flow with token refresh
- SMART on FHIR Backend Services -
private_key_jwt(RS384) for EPIC, OpenEMR, and other SMART-conformant EMRs - SMART on FHIR - EPIC, Cerner, OpenEMR, and other EMR standards
- Basic Auth - Username/password authentication
- Custom - Extensible for additional auth methods
For complete security documentation, see Security Guide:
- HIPAA compliance checklist
- OAuth configuration for EPIC/Cerner/GCP
- Kubernetes security manifests
- Credential management procedures
- Audit logging implementation
MCP Apps (Interactive UIs)
LangCare MCP FHIR ships with built-in MCP Apps β interactive, rich UI views that run directly inside MCP-capable hosts like Claude Desktop. Unlike traditional chat-based tool output, MCP Apps render full React-based interfaces with charts, tables, and interactive controls while using the same underlying FHIR tools.
How it works: Each app is a single-file HTML bundle (React + TypeScript, compiled with Vite) that gets embedded into the Go binary at compile time via go:embed. At runtime the MCP server registers each app as both an MCP Resource (text/html;profile=mcp-app) and a dedicated MCP Tool linked via _meta.ui.resourceUri. When an MCP host calls the tool, it fetches the resource and renders the UI. The app calls back into the server's generic FHIR tools (fhir_search, fhir_read, etc.) through app.callServerTool() β no LLM round-trips for data fetching.
Advantages over plain tool output:
- Rich visualization β SVG charts, color-coded cards, expandable detail panels
- Interactive controls β search fields, date range pickers, click-to-expand rows
- Deterministic data fetching β apps call FHIR tools directly, no LLM involvement in data retrieval
- Zero external dependencies β everything inlines into a single HTML file, embedded in the binary
- Works offline β no CDN, no external scripts, no network requests beyond FHIR API calls
Built-in Apps
| App | Tool | Description |
|---|---|---|
| FHIR Explorer | fhir_explorer | Interactive FHIR resource browser. Search, read, create, and update any FHIR R4 resource type with JSON detail views. |
| Patient Chart Review | patient_chart_review | Clinical dashboard with patient demographics, active conditions, medications, vitals, labs, and vitals trend charts (BP + weight over time). |
Both apps are reference implementations demonstrating the MCP Apps pattern. See apps/README.md for architecture details and how to build new apps.
Patient Chart Review running inside Claude Desktop
Agent Usage
AI agents use LangCare MCP FHIR Server to help healthcare professionals access and manage patient health records through 4 FHIR tools. The server handles EMR authentication, allowing agents to focus on clinical workflows while maintaining strict privacy and accuracy standards.
Agent capabilities:
- Search, Read, Create, Update - Any FHIR R4 resource (Patient, Observation, Medication, etc.)
- Patient privacy - Use partial identifiers, confirm identity before updates
- Clinical accuracy - Verify data, use standard codes (LOINC, SNOMED, RxNorm)
- Professional communication - Structure responses with context, findings, and next steps
Common workflows:
- Patient lookup: Search by name/DOB β verify identity β read full details
- Clinical review: Retrieve labs, vitals, medications β present with reference ranges
- Documentation: Extract structured data β map to FHIR resources β confirm β create
- Updates: Verify existing resource β modify β confirm changes β update
System support:
- Works with any FHIR R4 resource type (60+ types including DocumentReference, Binary, Media)
- Automatic authentication and token refresh to EPIC, Cerner, OpenEMR, GCP Healthcare API
- HIPAA-compliant PHI handling with audit logging
- Comprehensive OAuth2 scopes for clinical data access
π Complete guide: Agent Prompt Guide - System prompt, tool examples, workflows, and error handling
Clinical Skills Library (Optional)
40+ agent-agnostic clinical workflow guides that teach AI agents how to perform complex healthcare tasks using the MCP server's 4 FHIR tools (fhir_search, fhir_read, fhir_create, fhir_update).
- Optional - The MCP server works without them
- Portable - Work with Claude, ChatGPT, Gemini, or any AI agent
- Evidence-based - Built on USPSTF, ADA, ACC/AHA, CDC, ACOG, KDIGO, and other society guidelines
- Copy-paste ready - Add a skill's
SKILL.mdto your agent's system prompt or custom instructions
Skill Categories (40 Skills)
| Category | Skills | Examples |
|---|---|---|
| Patient Data & Summary | 5 | Demographics, clinical summary (CCD-style), problem list audit, allergy review, insurance coverage |
| Medication Management | 5 | Med reconciliation, drug interactions (CYP450), adherence (MPR/PDC), Beers Criteria, opioid risk (ORT/MME) |
| Lab & Diagnostics | 5 | Lab interpretation, critical values (CAP/CLIA), pre-op labs, diabetes panel (ADA), renal function (KDIGO) |
| Clinical Decision Support | 5 | Sepsis (qSOFA/SOFA), cardiovascular risk (ASCVD/HEART), VTE (Wells/Caprini), fall risk (Morse), pneumonia (CURB-65) |
| Care Coordination | 5 | Discharge planning (LACE), referrals, care gaps (USPSTF), transitions of care (I-PASS), follow-up tasks |
| Documentation | 5 | SOAP notes, H&P, progress notes, discharge summaries, procedure notes |
| Population Health | 5 | Panel overview, quality measures (HEDIS), chronic disease registries, immunization status (CDC), preventive care compliance |
| Specialty | 5 | Prenatal (ACOG), pediatric growth (WHO/CDC), mental health (PHQ-9/GAD-7), oncology (TNM/RECIST), chronic pain |
Full catalog with links: skills/README.md
How to Use Skills
- Browse the skills/core/ directory and pick a skill
- Copy the skill's
SKILL.mdcontent into your AI agent's system prompt or custom instructions - Reference files in each skill's
references/subdirectory contain detailed clinical knowledge (scoring criteria, code tables, thresholds) that can optionally be included for deeper clinical accuracy
# Example: Add medication-reconciliation skill to your agent
skills/core/medication-management/medication-reconciliation/
βββ SKILL.md # Copy this into agent instructions
βββ references/
βββ reconciliation-process.md # Joint Commission standards
βββ high-risk-medications.md # ISMP high-alert drug list
Integration guides: Claude | ChatGPT | Gemini
Community contributions welcome - see CONTRIBUTING.md for guidelines.
Development & Testing
Build from Source
make build
Run Locally (stdio mode)
make run
# or
./bin/langcare-mcp-fhir -config configs/config.local.yaml
Run in HTTP Mode (Streamable HTTP)
make run-http
# or
./bin/langcare-mcp-fhir -http -port 8080 -config configs/config.yaml
Starts the server with Streamable HTTP transport on /mcp and health check on /health.
Run Tests
make test
Lint Code
make lint
Deploy to Fly.io (Remote Streamable HTTP)
Deploy as a remote MCP server with Streamable HTTP transport, accessible by any MCP-compatible AI agent from anywhere.
# Install Fly CLI
brew install flyctl
fly auth login
# Create app
fly apps create --name langcare-mcp-dev
# Set CONFIG_FILE in fly/fly.dev.toml [env] block for your provider (EPIC or GCP)
# Then set secrets (EPIC example):
fly secrets set \
EPIC_BASE_URL="https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4" \
EPIC_CLIENT_ID="your-client-id" \
EPIC_TOKEN_URL="https://fhir.epic.com/interconnect-fhir-oauth/oauth2/token" \
EPIC_PRIVATE_KEY_B64="$(base64 < keys/epic/private-key.pem)" \
MCP_AUTH_TOKENS="your-token" \
--app langcare-mcp-dev
# Deploy
fly deploy -c fly/fly.dev.toml --app langcare-mcp-dev
# Verify
curl https://langcare-mcp-dev.fly.dev/health
Connect any MCP client to:
URL: https://langcare-mcp-dev.fly.dev/mcp
Auth: Authorization: Bearer your-token
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"langcare-fhir": {
"url": "https://langcare-mcp-dev.fly.dev/mcp",
"headers": {
"Authorization": "Bearer your-token"
}
}
}
}
Supports EPIC and GCP Healthcare API providers. See fly/README.md for provider setup, secrets, and full deployment guide.
Local Testing with EPIC
For step-by-step instructions on setting up EPIC credentials and testing locally:
This guide covers:
- Generating RSA keys and JWKS
- Configuring EPIC credentials
- Running the server locally
- Testing with Claude Desktop
- Troubleshooting common issues
Quick credential test:
# Test your EPIC credentials before running the server
go run test/test_epic_token.go "your-client-id" "/path/to/private-key.pem"
Project Structure
langcare-mcp-fhir/
βββ cmd/
β βββ server/
β βββ main.go # Entry point
βββ internal/
β βββ apps/ # MCP Apps (embedded UIs)
β β βββ embed.go # go:embed directive for HTML bundles
β β βββ registry.go # App metadata, tool names, resource URIs
β β βββ dist/ # Built HTML bundles (copied by build)
β β βββ fhir-explorer.html # FHIR Explorer single-file bundle
β β βββ patient-chart-review.html # Patient Chart Review single-file bundle
β βββ audit/
β β βββ logger.go # HIPAA audit logging
β βββ config/
β β βββ config.go # YAML configuration loading
β βββ fhir/
β β βββ client.go # FHIR HTTP client interface
β β βββ types.go # FHIR client types
β β βββ providers/ # Backend implementations
β β βββ base.go # Base HTTP provider
β β βββ epic.go # EPIC OAuth2 provider
β β βββ cerner.go # Cerner OAuth2 provider
β β βββ openemr.go # OpenEMR SMART Backend Services provider
β β βββ gcp.go # GCP Healthcare API provider
β βββ mcp/
β β βββ server.go # MCP server + app registration
β βββ middleware/
β β βββ auth.go # MCP authentication
β β βββ rate_limit.go # Rate limiting
β βββ tools/ # MCP tool implementations
β β βββ registry.go # Tool registry
β β βββ fhir_read.go # Read FHIR resource
β β βββ fhir_search.go # Search FHIR resources
β β βββ fhir_create.go # Create FHIR resource
β β βββ fhir_update.go # Update FHIR resource
β βββ transport/
β βββ stdio.go # stdio transport (Claude Desktop)
β βββ http.go # Streamable HTTP transport (production)
βββ apps/ # MCP App source code (React + TypeScript)
β βββ README.md # App development guide
β βββ package.json # Shared dependencies (React 19, MCP Apps SDK)
β βββ vite.config.ts # Vite build config (single-file output)
β βββ tsconfig.json # TypeScript config
β βββ fhir-explorer/ # FHIR Explorer app
β β βββ index.html
β β βββ src/
β β βββ app.tsx
β β βββ global.css
β βββ patient-chart-review/ # Patient Chart Review app
β βββ index.html
β βββ src/
β βββ app.tsx
β βββ global.css
βββ scripts/
β βββ build-apps.sh # Build all apps β internal/apps/dist/
β βββ create_jwks.sh # Generate JWKS from public key (EPIC)
β βββ create_jwks_openemr.sh # Generate JWKS from public key (OpenEMR)
βββ pkg/
β βββ types/
β βββ errors.go # Custom error types
βββ configs/
β βββ config.epic.example.yaml # Example configuration for EPIC
β βββ config.cerner.example.yaml # Example configuration for Cerner
β βββ config.openemr.example.yaml # Example configuration for OpenEMR
β βββ config.gcp.example.yaml # Example configuration for GCP
β βββ config.base.example.yaml # Example configuration for any FHIR R4 server
βββ docs/
β βββ AGENT_PROMPT.md # AI agent system prompt
β βββ EPIC-APP-SECURITY.md # EPIC authentication setup
β βββ OPENEMR-APP-SECURITY.md # OpenEMR SMART Backend Services setup
β βββ EPIC-SCOPES.md # OAuth2 scopes reference
β βββ LOCAL-TESTING.md # Local development guide
β βββ SECURITY.md # Production security guide
βββ test/
β βββ README.md # Test documentation
β βββ test_epic_token.go # EPIC OAuth2 token tester
βββ fly/
β βββ Dockerfile # Multi-stage Go build for Fly.io
β βββ docker-entrypoint.sh # Key materialization + server startup
β βββ fly.dev.toml # Fly.io dev deployment config
β βββ config.fly.epic.yaml # Fly.io EPIC provider config
β βββ config.fly.gcp.yaml # Fly.io GCP provider config
β βββ README.md # Fly.io deployment guide
βββ bin/ # Build output (gitignored)
β βββ langcare-mcp-fhir # Compiled binary
βββ go.mod # Go module definition
βββ go.sum # Go module checksums
βββ Makefile # Build commands
βββ README.md # This file
Note: The following are gitignored and not committed:
keys/- Private keys and credentialsconfig.local.*.yaml- Local configuration filesbin/- Compiled binaries.env- Environment variablesapps/node_modules/,apps/dist/,apps/dist-tmp/- App build artifacts
Healthcare Voice Agent
Real-time voice AI that lets patients ask about their health records and get spoken answers pulled directly from their EMR.
The stack: PipeCat (open-source, Daily.co) for the voice pipeline β STT, LLM orchestration, TTS with sub-3-second latency. Claude for clinical reasoning and tool calling. LangCare MCP FHIR Server (open-source, Go) as a stateless proxy to any FHIR R4 EMR β Epic, Cerner, GCP Healthcare API.
MCP is the glue. PipeCat's native MCP client auto-discovers FHIR tools at startup. Patient asks "What medications am I on?" β Claude calls fhir_search β PipeCat routes it to the MCP server β data comes back β Claude responds in natural speech. No manual tool schemas needed.
Three-layer HIPAA auth: Caller identity verified before the session starts, bearer token to MCP, OAuth2/SMART on FHIR to EMR. Zero PHI storage.
Everything is swappable. Replace Claude with Gemini, DeepGram with Google STT, Daily with WebSocket. The MCP FHIR layer and clinical prompts stay the same.
Full documentation and setup guide
LangCare CLI
Command-line interface that wraps the 4 FHIR MCP tools (fhir_search, fhir_read, fhir_create, fhir_update) as CLI subcommands over HTTP. Built for AI agent frameworks that don't speak MCP natively β LangChain, smolagents, CrewAI, AutoGen, and any framework that can call a subprocess. The CLI handles the MCP session handshake internally, so agents get clean JSON on stdout with no protocol knowledge required.
# Install
pip install "langcare-cli @ git+https://github.com/langcare/langcare-mcp-fhir.git#subdirectory=cli"
# Use
langcare fhir search Patient --query "name=John"
langcare fhir read Patient 123
langcare fhir create Observation --data @obs.json
langcare fhir update Patient 123 --data @patient.json
The 40+ clinical skills in the Skills Library work as-is β skills reference abstract tool names, not transport. Register the CLI as subprocess tools in your agent framework and skills run without modification.
Full documentation and setup guide
Documentation
Getting Started
- π Local Development & Testing Guide - Complete guide for local setup and testing
- π Installation & Configuration - Quick setup guide above
Agent Integration
- π€ Agent Prompt Guide - Complete guide for AI agents using LangCare MCP FHIR (tool examples, workflows, best practices)
Security & Authentication
- π‘οΈ Security Documentation - Complete security architecture and HIPAA compliance
- π EPIC Setup Guide - JWT authentication, key generation, and JWKS registration
- π OpenEMR Setup Guide - SMART on FHIR Backend Services (
private_key_jwt/RS384) setup, JWKS generation, and OpenEMR API client registration - π EPIC Scopes Reference - Complete OAuth2 scopes guide for FHIR resources
- π Authentication Methods - Supported auth methods
Deployment
- Fly.io Deployment Guide - Remote Streamable HTTP deployment, provider configs, secrets, Docker
Development & Testing
- π§ͺ Testing Methods - Claude Desktop, MCP Inspector, manual testing, and automation
- π¦ Project Structure - Directory layout and architecture
- π§ Build Commands - Development workflow
Dependencies
github.com/modelcontextprotocol/go-sdk- Official MCP SDKgopkg.in/yaml.v3- Configuration parsinggolang.org/x/oauth2- OAuth2 client librarygithub.com/golang-jwt/jwt/v5- JWT signing and verification- Go 1.25+
HIPAA Compliance
- PHI scrubbing enabled by default
- Never logs patient identifiers
- TLS support for HTTP transport
- Proper error sanitization
- Audit logging ready
- Stateless proxy design (no persistent storage)
Testing
Public Test Server
Default configuration uses HAPI FHIR public test server (https://hapi.fhir.org/baseR4) for immediate testing without setup.
Test Your Setup
- π Local Development & Testing Guide - Complete guide for setup, testing with Claude Desktop, MCP Inspector, and automation
- π EPIC Security Setup - Detailed EPIC authentication guide
- π‘οΈ Security Documentation - Production deployment and security
Claude Managed Agents
9 production-ready clinical AI agents built on the Anthropic Managed Agents API. Each agent connects to a LangCare MCP FHIR Server and uses a curated set of domain-specific clinical skills drawn from the 40+ Clinical Skills Library. Sessions are persistent, visible at platform.claude.com/workspaces/default/sessions, and can be run interactively or driven by a single prompt.
| Agent | Domain |
|---|---|
| Medication Management | Reconciliation, drug interactions, Beers Criteria, opioid risk, adherence |
| Care Coordination | Discharge planning, referrals, care gaps, transitions of care, follow-up tasks |
| Clinical Decision Support | Sepsis qSOFA, cardiovascular risk, VTE, fall risk, CURB-65 |
| Clinical Triage | Clinical summary, acuity, vitals review, sepsis indicators |
| Documentation | SOAP notes, H&P, progress notes, discharge summaries, procedure notes |
| Lab & Diagnostics | Critical values, diabetes panel, lab interpretation, pre-op labs, renal function |
| Patient Data | Demographics, allergy review, clinical summary, insurance coverage, problem list |
| Population Health | Chronic disease registries, immunization status, preventive care, quality measures |
| Specialty Care | Chronic pain, mental health, oncology, pediatric growth, prenatal |
Quickstart
# 1. Set environment variables
export ANTHROPIC_API_KEY=sk-ant-...
export LANGCARE_MCP_URL=https://langcare-mcp-dev.fly.dev/mcp
export LANGCARE_MCP_TOKEN=your-bearer-token
# 2. Upload skills, create environment + vault, deploy all 9 agents
cd cma/scripts
./setup.sh dev
# 3. Run a session
./run-session.sh <agent-id> <env-id> <vault-id> "Show active medications for patient ID d886a934-5568-42b3-9324-0f0b05fc018c"
setup.sh is idempotent β safe to re-run. At the end it prints the Environment ID and Vault ID needed for sessions.
Full guide: cma/README.md β env vars, all scripts reference, troubleshooting.
Contributing
We welcome contributions from healthcare professionals, developers, and informaticists!
There are three main ways to contribute:
1. Core MCP Server (Go Development)
- Bug fixes and performance improvements
- New FHIR provider implementations (AllScripts, Athenahealth, etc.)
- Security enhancements and observability features
- Testing and CI/CD improvements
2. Clinical Skills (Healthcare Workflows)
- Evidence-based clinical workflows using FHIR
- Specialty-specific protocols (cardiology, oncology, etc.)
- Population health and quality measure workflows
- Clinical decision support algorithms
Skills are agent-agnostic workflow guides that work across Claude, ChatGPT, and Gemini. No coding required - just clinical expertise and FHIR knowledge!
3. MCP Apps (Interactive UIs)
- New clinical or administrative UI apps
- Enhancements to existing apps (FHIR Explorer, Patient Chart Review)
- Reusable components and patterns for healthcare UIs
See apps/README.md for the development guide.
4. Agent Integrations (Platform Setup)
- Setup guides for new AI platforms
- Deployment examples (Docker, Kubernetes, cloud)
- Monitoring and observability setups
- CI/CD pipelines
Get started: Read CONTRIBUTING.md for detailed guidelines, code standards, and submission process.
Recognition: Contributors are credited in README, release notes, and skill/integration author credits. Outstanding contributors may be invited as maintainers.
Questions? Open a GitHub Discussion or issue!
Community
- GitHub Discussions - Ask questions, share ideas: https://github.com/langcare/langcare-mcp-fhir/discussions
- GitHub Issues - Report bugs, request features: https://github.com/langcare/langcare-mcp-fhir/issues
- Contributing Guide - How to contribute: https://github.com/langcare/langcare-mcp-fhir/blob/main/CONTRIBUTING.md
- Skills - Clinical workflows: https://github.com/langcare/langcare-mcp-fhir/blob/main/skills/README.md
License
See LICENSE file.
Built with β€οΈ by the LangCare team and contributors.
Improving healthcare through better AI infrastructure.
