HealthEx

HealthEx is a patient-centric health-data-rights platform that securely unifies an individual's medical records across places of care into one connected history, and lets them share that record — under explicit, patient-initiated consent — with providers, apps, and AI services. It operates as an Information Access Services (IAS) Provider on the TEFCA network, complies with HIPAA privacy rules, and reaches records across more than 80% of U.S. care providers. For developers HealthEx exposes a REST admin API (patient outreach, consent checking and auditing, record-location search, usage), a FHIR R4 server ($everything, USCDIv3), and a hosted Model Context Protocol server that gives AI agents governed, consent-scoped access to a patient's health record.

HealthEx publishes 1 API on the APIs.io network. Tagged areas include Company, Healthcare, Health Records, FHIR, and Patient Consent.

HealthEx’s developer surface includes documentation, API reference, getting-started guide, support, signup flow, authentication, changelog, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub

39.8/100 thin ▬ flat Agent 38/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5

AccessSelf serve

1 APIs 1 MCP Servers

CompanyHealthcareHealth RecordsFHIRPatient ConsentData SharingInteroperabilityTEFCAMCPAgents

Kin Score

Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5

Composite quality — 39.8/100 · thin

Contract Quality 0.0 / 25

Developer Ergonomics 14.3 / 20

Commercial Clarity 5.8 / 20

Operational Transparency 5.1 / 13

Governance 0.0 / 12

Discoverability 9.3 / 10

Agent readiness — 38/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 15

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/healthex: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

HealthEx API

REST API for patient outreach, consent checking and auditing, record-location search, test-patient creation, and usage reporting, plus a FHIR R4 server ($everything) for standar...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Healthex Scopes

5 scopes · authorizationCode

5 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

TrustCenter

Compliance

Authentication

OAuthScopes

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

StatusPage

Deprecation

ChangeLog

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: healthex
name: HealthEx
description: HealthEx is a patient-centric health-data-rights platform that securely unifies an individual's medical records
  across places of care into one connected history, and lets them share that record — under explicit, patient-initiated consent
  — with providers, apps, and AI services. It operates as an Information Access Services (IAS) Provider on the TEFCA network,
  complies with HIPAA privacy rules, and reaches records across more than 80% of U.S. care providers. For developers HealthEx
  exposes a REST admin API (patient outreach, consent checking and auditing, record-location search, usage), a FHIR R4 server
  ($everything, USCDIv3), and a hosted Model Context Protocol server that gives AI agents governed, consent-scoped access
  to a patient's health record.
url: https://raw.githubusercontent.com/api-evangelist/healthex/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://framerusercontent.com/assets/91Fl8WPMZvfgNsG45g8tmHf88w.png
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Healthcare
- Health Records
- FHIR
- Patient Consent
- Data Sharing
- Interoperability
- TEFCA
- MCP
- Agents
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: HealthEx API
  description: REST API for patient outreach, consent checking and auditing, record-location search, test-patient creation,
    and usage reporting, plus a FHIR R4 server ($everything) for standards-based access to a consented patient's medical record.
  humanURL: https://docs.healthex.io/
  baseURL: https://api.healthex.io
  properties:
  - type: Documentation
    url: https://docs.healthex.io/
  - type: APIReference
    url: https://docs.healthex.io/api
  - type: GettingStarted
    url: https://docs.healthex.io/authentication
  - type: Authentication
    url: authentication/healthex-authentication.yml
  - type: OAuthScopes
    url: scopes/healthex-scopes.yml
  - type: Sandbox
    url: sandbox/healthex-sandbox.yml
  - type: ChangeLog
    url: changelog/healthex-changelog.yml
  - type: MCPServer
    url: mcp/healthex-mcp.yml
common:
- type: DomainSecurity
  url: security/healthex-domain-security.yml
- type: Website
  url: https://www.healthex.io/
- type: DeveloperPortal
  url: https://docs.healthex.io/
- type: Documentation
  url: https://docs.healthex.io/
- type: APIReference
  url: https://docs.healthex.io/api
- type: GettingStarted
  url: https://docs.healthex.io/authentication
- type: Support
  url: https://support.healthex.io/kb
- type: SignUp
  url: https://app.healthex.io/
- type: Login
  url: https://app.healthex.io/
- type: StatusPage
  url: https://status.healthex.io/
- type: TrustCenter
  url: https://trustcenter.healthex.io/
- type: Compliance
  url: https://trustcenter.healthex.io/
- type: Authentication
  url: authentication/healthex-authentication.yml
- type: OAuthScopes
  url: scopes/healthex-scopes.yml
- type: WellKnown
  url: well-known/healthex-well-known.yml
- type: MCPServer
  url: mcp/healthex-mcp.yml
- type: LLMsTxt
  url: llms/healthex-llms.txt
- type: Conventions
  url: conventions/healthex-conventions.yml
- type: ErrorCatalog
  url: errors/healthex-problem-types.yml
- type: Lifecycle
  url: lifecycle/healthex-lifecycle.yml
- type: StatusPage
  url: lifecycle/healthex-lifecycle.yml
- type: Deprecation
  url: lifecycle/healthex-lifecycle.yml
- type: ChangeLog
  url: changelog/healthex-changelog.yml
- type: Sandbox
  url: sandbox/healthex-sandbox.yml
- type: Conformance
  url: conformance/healthex-conformance.yml
- type: DataModel
  url: data-model/healthex-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence