Zus Health
Zus Health is a next-generation shared health data platform that brings information speed to healthcare. Its flagship Zus Aggregated Profile (ZAP) consolidates a patient's longitudinal medical record — encounters, conditions, medications, labs, and transitions of care sourced from EHR, pharmacy, ADT, and lab networks plus TEFCA — into a single, deduplicated, FHIR R4-native view accessible via a standalone app, embeddable UI, or API. Zus exposes a FHIR R4 REST API and a read-only FHIR GraphQL Query Service (FQS) over 128 FHIR resource types, an Auth Service for machine-to-machine and user authentication, Patient History APIs for network enrollment and querying, Zushooks event webhooks, and SQL-friendly relational data marts on Snowflake and Databricks. The platform is SOC 2 Type 2 compliant and HIPAA-compliant.
Zus Health publishes 2 APIs on the APIs.io network. Tagged areas include Company, Health, Healthcare, FHIR, and Interoperability.
The Zus Health catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Zus Health’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 23 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Zus FHIR & Platform API
Zus FHIR R4 REST API plus Auth Service and Patient History APIs. Implements FHIR R4 (v4.0.1) across 128 resource types with instance-level CRUD, transaction Bundles, conditional...
Zus FHIR GraphQL API (FQS)
The Zus FHIR Query Service (FQS) is a read-only GraphQL API over the FHIR data model, exposed at a single endpoint. Supports UPID-scoped (one-human) and builder-scoped queries a...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
zus-health-mcp.yml
MCP SERVEREvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Zus Health Zushooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API