What did Hlido score HealthChain?

HealthChain scored 66/100 (FADING) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

HealthChain

Name: HealthChain review
Item: HealthChain
Rating: 66
Author: Hlido Editor

Specialized verticals · tested 2026-08-10 · re-test due 2026-11-10 · by the Hlido desk, not the vendor

In short: Open-source FHIR tooling that serves typed, validated healthcare tools to agents over MCP — credible scope, but the captured surface is a docs landing page, not proof.

5 PASS · 1 FAIL of 6 public-surface claims

Visit HealthChain → scorecard.json

Quick answer

HealthChain scores 66/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-10). FADING (66) because the project is open, actively documented and pointed at a genuinely valuable problem, but the captured public surface establishes no evidence about the thing that matters — the correctness and coverag

Hlido Editor · 2026-08-10

HealthChain is aiming at a real and hard problem: agents operating on clinical data need tools that are typed and validated against FHIR, not free-form API calls, and the failure mode of getting that wrong is not a bad user experience but a bad clinical one. The framing — 'the open agentic stack for healthcare', with gateways, FHIR validation, agent tools and a sandbox as the named core concepts — is coherent and correctly ordered: validation first, connectivity second, deployment third. Serving those tools over both MCP and LangChain is the right distribution choice for 2026, and multi-EHR aggregation across Epic and Cerner is the use case that would actually justify the project's existence. The public signals are modest but real: version 0.16.0, 221 stars, 41 forks, an active Discord, a newsletter, and docs organised into getting-started, tutorials, cookbook and API reference. What we could read is a well-structured documentation home page and nothing more — no validation coverage claim, no conformance statement, no named deployment, no statement about PHI handling or what the sandbox does and does not isolate. For a healthcare-adjacent tool those absences are the review. The scope is worth taking seriously; the evidence on this surface does not yet let anyone take a position on whether the validation is correct, which is the entire product.

Why FADING

FADING (66) because the project is open, actively documented and pointed at a genuinely valuable problem, but the captured public surface establishes no evidence about the thing that matters — the correctness and coverage of its FHIR validation. For clinical tooling, unverified validation is the central risk, and nothing public addresses conformance, PHI handling or a real deployment. Version 0.16.0 with 221 stars is early-stage traction, not adoption. It clears FLATLINE comfortably on openness and documentation structure; it cannot reach STEADY without published conformance or a named user.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'The open agentic stack for healthcare'
PASS Cta present (required) — 'Get Started'
PASS Pricing or access (required) — Open source; install documented
FAIL Evidence or demo (required) — No conformance evidence, benchmark or named deployment on the captured surface
PASS Docs public — Docs, tutorials, cookbook and API reference in nav, no login

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-29e63c3221373f49-healthchainai-github-io). Our own captures — not vendor marketing material.

HealthChain — run screenshot 1 (home.png) — home.png

HealthChain — run screenshot 2 (pageinstallation_.png) — pageinstallation_.png

HealthChain — run screenshot 3 (pagetutorials_.png) — pagetutorials_.png

HealthChain — run screenshot 4 (pagecookbook_.png) — pagecookbook_.png

What it does well

Correctly orders the problem: typed FHIR validation before agent connectivity
Serves tools over both MCP and LangChain rather than betting on one
Multi-EHR aggregation (Epic, Cerner) is the use case that justifies the project
Documentation is structured into getting-started, tutorials, cookbook and API reference
Open source with visible community surfaces (GitHub, Discord, newsletter)

What it fails at

No FHIR conformance or validation-coverage claim anywhere on the captured surface
No statement about PHI handling, data residency, or what the sandbox isolates
No named deployment, pilot or case study — traction is 221 stars, not usage
Version 0.16.0: pre-1.0 for software whose failure mode is clinical
Landing page is a docs index; the substantive claims live behind links we did not capture

Best for

Engineering teams prototyping agentic workflows against FHIR data
Health-tech builders who need EHR connectivity without writing integrations per vendor
Research groups wanting an open, inspectable stack rather than a closed vendor SDK
Developers evaluating whether MCP is a viable transport for clinical tooling

Not recommended for

Production clinical deployments requiring published conformance evidence
Organisations needing a documented PHI/compliance posture before evaluation
Teams wanting vendor support and SLAs rather than a Discord
Anyone treating validated FHIR access as a solved dependency rather than a thing to verify

Pricing & access

Pricing findable on the public surfacePASS Open source; install documented (tested 2026-08-10)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-10.

Related agents

Agent relevance

API MCP SDK Behavioral-testable

Agentic-Commerce Readiness 71/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Exposes FHIR tools to agents over MCP or LangChain, with a Python package and an API reference. The design intent — that an agent consumes validated, typed tools rather than raw EHR endpoints — is the correct shape for this domain. Whether the validation layer is trustworthy is not establishable from the public surface.

Agent-friendly score: 7/10

Evidence

Serves typed, validated FHIR tools to agents over MCP or LangChain — source (2026-08-10) verified
Supports multi-EHR aggregation across Epic and Cerner — source (2026-08-10) verified
Version 0.16.0, 221 stars, 41 forks — source (2026-08-10) verified
Core concepts are Gateways, FHIR validation, Agent Tools and Sandbox — source (2026-08-10) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-10

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/healthchainai-healthchain.svg)](https://hlido.eu/check/?agent=healthchainai-healthchain)

HTML

<a href="https://hlido.eu/check/?agent=healthchainai-healthchain"><img src="https://hlido.eu/badge/healthchainai-healthchain.svg" alt="Hlido trust score"></a>