# Zus Health (slim)

> Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.

- Full: https://www.anchorterminal.com/tools/zus-health.md (~5,600 tokens) · this version ~1,430 tokens · JSON https://www.anchorterminal.com/tools/zus-health.json · canonical https://www.anchorterminal.com/tools/zus-health
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-14

**C · 56.6/100 · rank #669 of 1076 · #7 in Health records & wellness data · not agent-ready · confidence medium**


Assessment: FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.

## Facts

- Kind: HTTP API · vendor: Zus Health, Inc. · category: Health records & wellness data · legal entity: Zus Health, Inc. · provenance 71/100
- Local only (HTTP)
- Auth: OAuth · pricing: Paid · x402: no · licence: Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum
- Probe metrics: not measured yet (probes haven't run)
- Endpoints: FHIR R4 at https://api.zusapi.com/fhir (sandbox https://api.sandbox.zusapi.com/fhir), GraphQL at https://fqs.zusapi.com/query, Auth Service, Patient History and ZAP Data Subscriptions APIs
- Data sources: EHR data through CommonWell and Carequality, pharmacy fills through Surescripts, ADT through PointClickCare and Bamboo Health, labs through Quest
- FHIR: Most FHIR R4 resource types, POST, PUT, JSON Patch and DELETE, transaction Bundles, conditional create, update and delete by identifier, `Zus-If-Match` version checks
- Pagination: Ordered by lastUpdated, 10 per page by default and up to 500
- Rate limits: 2,000 FHIR requests a minute per customer, 200 token requests an hour per App Client, one Patient History request per patient per 24 hours and 10 priority jobs a minute per customer
- Webhooks: ZusHooks push events such as ADTs, and Data Marts export to customer warehouses
- EHR integrations: Epic, athenahealth, Elation, eClinicalWorks, Salesforce Health Cloud, Healthie, Canvas and Medplum
- SLA: 99.5 per cent monthly uptime for Builder Services, credits 2, 5 or 10 per cent of the month's invoice
- Status: status.zusapi.com on StatusPal with components for the app, EHR integrations, FHIR and Patient History APIs, each network, ZusHooks and the Auth Service

- Scores: Reliability 66, Performance pending, Schema & documentation 77, Agent ergonomics 67, Security & auth 49, Payments & pricing 5, Task success pending, Maintenance & community 64, Transparency & trust 59 · total over the 7 assessed categories
- Why: Reliability, Read with the hosted lines. · Schema & documentation, Each reference page carries an OpenAPI 3.0.3 fragment with enums and required fields, with no single specification file found (18 of 25). · Agent ergonomics, `_count` up to 500, and GraphQL selects only the fields requested, though GraphQL is beta (20 of 25). · Security & auth, OAuth 2.0 with one-hour tokens, machine-to-machine App Clients managed in the app, token exchange from the customer's identity provider and… · Payments & pricing, Read with the hosted rubric. · Maintenance & community, The Builder Data Integration role change took effect on 14 October 2026 and the last dated entry is 21 September 2026 (30). · Transparency & trust, Closed service with published Builder Terms, Developer Sandbox Terms, BAA and SLA (15 of 30).
- Sources: 12, open questions: 3, both in the full twin
- Capabilities: health.records, health.fhir, health.ehr, health.consent
- JSON: https://www.anchorterminal.com/api/v1/tools/zus-health.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/zus-health.svg` or a link to https://www.anchorterminal.com/tools/zus-health from a page on zushealth.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429
2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint
3. Use conditional create by identifier so a retried write doesn't duplicate a resource
4. Send `Zus-If-Match` with the resource's ETag on PUT and PATCH
5. Set `_count` up to 500 on searches, since the default page is 10

## Connect

```bash
GET https://api.sandbox.zusapi.com/fhir/Patient?_count=50
Authorization: Bearer <access-token>
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/zus-health

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Medblocks | D | 52.7 | health.records, health.consent, health.ehr, health.fhir | https://www.anchorterminal.com/tools/medblocks.min.md |
| Metriport Medical API | D | 50.1 | health.records, health.fhir, health.consent, health.ehr | https://www.anchorterminal.com/tools/metriport.min.md |
| Aidbox | B | 64.2 | health.fhir, health.records, health.consent | https://www.anchorterminal.com/tools/aidbox.min.md |
| Health Gorilla | C | 59.3 | health.records, health.fhir, health.consent | https://www.anchorterminal.com/tools/health-gorilla.min.md |
| Redox | C | 58.3 | health.ehr, health.fhir, health.records | https://www.anchorterminal.com/tools/redox.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)