1upHealth vs Metriport Medical API

1upHealth

Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.

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.

1upHealth

1. Hand the Patient Access sign-in to the member, who must authorise in the health plan's auth app
2. Exchange the authorisation code within five minutes, and refresh before the 15-minute token expires
3. Email payer-patient-access@1up.health with the client ID to get the app synced to the demo environment
4. Expect only claims and coverage resources from some payers, and read /r4/metadata first

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