healthchainai/HealthChain

[![Stars][stars-badge]][stars]
[![Downloads][downloads-badge]][pypistats]
[![License][license-badge]][license]
[![Python Versions][python-versions-badge]][pypi]
[![Build Status][build-badge]][build]
[![AI-Assisted Development][ai-badge]][claude-md]
[![Substack][substack-badge]][substack]
[![Discord][discord-badge]][discord]
Open infrastructure for healthcare data applications.
Connect Python pipelines and applications to live FHIR APIs, build and validate structured output, and deliver it through REST, CDS Hooks, CDA, MCP, or LangChain.
Installation
What HealthChain Does
HealthChain puts a consistent FHIR boundary around your Python code: live data in, your own logic in the middle, and validated FHIR out. Built for research software, healthcare data, and AI teams.
🔌 Connect to Live FHIR APIs
Connect to Epic, Cerner, Medplum, and other FHIR R4 servers through one interface that handles authentication, source routing, and common FHIR operations.
Getting Started →
🔥 Build and Validate FHIR
Build typed resources without hand-writing deeply nested FHIR. Structured validation identifies failing fields and invalid required codes before delivery.
Getting Started →
🤖 Use the Same Tools with Agents
Expose the same build, validate, read, and terminology operations over MCP or LangChain, with structured errors an agent can inspect and correct.
Getting Started →
💬 Build FHIR-Backed Applications
Use live or local FHIR data in research software, patient-facing applications, analytics, decision support, and AI-assisted workflows.
Getting Started →
Why HealthChain?
Every healthcare data team rebuilds the same integration layer. Whether your logic is rule-based, a logistic regression, or an agent, it needs authenticated access to real FHIR APIs and a reliable way to turn output into coded FHIR. Pipelines tied to one site's warehouse don't travel, and structural or coding errors may only be discovered downstream.
HealthChain handles that layer so you can focus on your logic and your domain.
- **Live data, not exports** — Connect to live FHIR APIs instead of site-specific warehouse queries and stale extracts
- **Keep connection details out of pipeline logic** — Load endpoints and credentials from environment-backed configuration
- **Build FHIR with less boilerplate** — Use flat, typed helpers instead of manually assembling deeply nested resources
- **Catch errors early** — Get structured validation reports with failing field paths and actionable diagnostics
- **Resolve codes instead of guessing them** — Map free text through a swappable terminology lookup before building a resource
- **Choose how to deliver the result** — Expose output through FHIR REST services, CDS Hooks, SOAP/CDA, MCP, or LangChain
🏆 Recognition & Community
**Featured & Presented:**
- Featured in TLDR AI Newsletter (900K+ developers)
- Featured by Medplum for open source integration with Epic
- Presented at NHS Python Open Source Conference (watch talk)
- Built from NHS AI deployment experience – read the origin story
🤝 Pilots & Partnerships
Exploring HealthChain for your product or organization? Get in touch to discuss integrations, pilots, or collaborations, or join our Discord to connect with the community.
Usage Examples
Build a FHIR Service
Expose Multiple FHIR Sources [Docs]
Scaffold with the CLI