Metriport Medical API vs Zus Health

Metriport Medical API

One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.

Zus Health

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.

Metriport Medical API

1. Check the errors array after Start Network Query. It returns 2XX even when some sources fail
2. Wait for network-query.* webhooks or poll Get Network Query Status before reading consolidated data, which is cached from the last query
3. Send the resource's eTag in If-Match on updates to avoid overwriting newer data
4. Keep patient creates under 15 a minute and network queries under 20 a minute per source
5. In sandbox, create patients whose first name matches a pre-defined persona to get example records

Zus Health

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