H

healthex.io

HealthEx is a patient-directed health data platform that helps individuals access, unify, and share their medical records with healthcare organizations, apps, and AI agents. It provides consent management and record access infrastructure, including standardized FHIR-based data retrieval.

3 integrations · MCP · REST

HealthEx exposes authenticated REST APIs, a separate FHIR R4 HTTP API, and an MCP server at `https://api.healthex.io/mcp`; auth is via organization-issued JWTs from API key/secret, MCP OAuth 2.0 client registration for patient-authorized MCP access, and test-patient credentials for development flows.

discovered 1d ago
MCP servers1
REST · OpenAPI2
Credentials
Organization API key and secretcompoundGet key ↗

Log in to the HealthEx app with an administrator account, open the Admin tab, then Manage API Keys, click Create New, and save the generated API key and API secret. HealthEx notes the secret is shown only once. The docs say these credentials are used to call POST https://api.healthex.io/v1/auth/token to mint a JWT for API use.

OAuth 2.0oauth2
OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Test patient email and passwordbasicGet credentials ↗

Create a test patient through the HealthEx Test Patients workflow using organization admin access. The docs show organization admins creating test patients via the API after first minting an admin token; each created test patient gets an auto-generated email and password, and the password is only returned once. Use that email/password pair with POST https://api.healthex.io/v1/auth/token to obtain a patient JWT for testing, optionally including projectId for MCP project context.

conventions · 0/8 published

Publish these signals → /publishing