# 1upHealth (slim)

> 1upHealth runs FHIR APIs for US health plans, including the CMS Patient Access, Provider Access and Payer-to-Payer APIs, which let member-authorised third-party apps read claims, coverage and clinical data.

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

**D · 46.8/100 · rank #903 of 1076 · #12 in Health records & wellness data · not agent-ready · confidence medium**


Assessment: 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.

## Facts

- Kind: HTTP API · vendor: 1upHealth, Inc. · category: Health records & wellness data · legal entity: 1upHealth, Inc. · provenance 82/100
- Local only (HTTP)
- Auth: OAuth · pricing: Paid · x402: no · licence: Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024)
- Probe metrics: not measured yet (probes haven't run)
- APIs: Patient Access (FHIR R4 read for member-authorised apps), Provider Access and Payer-to-Payer (FHIR Bulk Export), electronic prior authorisation (CRD, DTR, PAS), Provider Directory
- Implementation guides: CARIN Blue Button for claims, US Core for clinical data, Da Vinci PDEX Plan Net and US Drug Formulary
- Endpoints: Demo FHIR at https://api.1uphealthdemo.com/r4 with auth at https://auth.1uphealthdemo.com, client credentials at https://gateway.1up.health
- Credentials: Dev Portal client ID and secret, authorisation code grant for Patient Access, client credentials with scopes for bulk data, 15-minute access tokens, secret regeneration
- Contract: FHIR CapabilityStatement at {baseUrl}/r4/metadata
- Rate limits: None found in the documentation
- SLA: 99 per cent availability in Exhibit A of the terms, credits of 1 to 20 per cent, Severity 1 response in 30 minutes
- Status: status.1up.health on Statuspage, with no components listed and the last incident on 20 October 2025
- Certifications: HITRUST, SOC 2 Type 2, CSA STAR, NIST CSF and HIPAA per the trust centre. The platform overview says HITRUST i1

- Scores: Reliability 52, Performance pending, Schema & documentation 50, Agent ergonomics 32, Security & auth 63, Payments & pricing 20, Task success pending, Maintenance & community 37, Transparency & trust 72 · total over the 7 assessed categories
- Why: Reliability, Read with the hosted lines. · Schema & documentation, A FHIR CapabilityStatement at each server's /metadata and the CARIN, US Core and Da Vinci implementation guides define the resources, with n… · Agent ergonomics, FHIR search and bulk export, with no documented size controls (12 of 25). · Security & auth, OAuth 2.0 with authorisation code for member consent, client credentials with scopes for bulk data, 15-minute tokens and secret regeneration… · Payments & pricing, Read with the hosted rubric. · Maintenance & community, Release 26.09.2 is the latest, numbered for September 2026 but undated (20 of 30). · Transparency & trust, Closed service under Terms of Service effective 1 August 2024 (15 of 30).
- Sources: 11, open questions: 3, both in the full twin
- Capabilities: health.records, health.fhir, health.consent
- JSON: https://www.anchorterminal.com/api/v1/tools/1uphealth.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/1uphealth.svg` or a link to https://www.anchorterminal.com/tools/1uphealth from a page on 1up.health 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. 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

## Connect

```bash
GET https://api.1uphealthdemo.com/r4/ExplanationOfBenefit
Authorization: Bearer <access-token>
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/1uphealth

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| 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 |
| Zus Health | C | 56.6 | health.records, health.fhir, health.consent | https://www.anchorterminal.com/tools/zus-health.min.md |
| Medblocks | D | 52.7 | health.records, health.consent, health.fhir | https://www.anchorterminal.com/tools/medblocks.min.md |
| Metriport Medical API | D | 50.1 | health.records, health.fhir, health.consent | https://www.anchorterminal.com/tools/metriport.min.md |


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