# Fetch a person's own records from their providers with their consent

> Fetch a person's own records from their providers with their consent: 1 companies fully do it, 2 with a limit, 12 carry the tag. Every listing in Health records & wellness data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/health-data.patient-records/
- Markdown: https://www.anchorterminal.com/niches/health-data.patient-records/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/health-data.patient-records/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/health-data.patient-records/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 2 | 12 | 14 | 5 |

## What counts as done

After the person signs in and consents, the tool returns their records as FHIR R4 resources (conditions, medications, labs, encounters) from each named provider it reaches, says which providers it could not reach, and has a documented revoke that stops further retrieval.

Measured, for our own tests: records available within 10 minutes of consent.

How agents ask for it: get my records from my hospital; pull my lab results from all my doctors; what medications have I been prescribed over the years; connect my health insurer's data

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Medblocks (Medblocks Inc.)**: search_health_systems finds hospitals, clinics and insurers, the patient approves at each portal by SMART on FHIR, records.sync.completed fires when a background pull settles, get_health_records returns stored FHIR resources with their source EHR, connection status shows failures, and disconnect_health_system revokes. The 10-minute bar is the suite's.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **1upHealth (1upHealth, Inc.)**: A member signs in to their health plan's auth app and the app reads FHIR R4 from 60+ plans, but some plans return only claims and coverage, no revoke call is documented, and Patient Connect (provider records) sunsets on 2026-12-31. Apps need 1up vetting before production.
- **Health Gorilla (Health Gorilla, Inc.)**: IAS gives person-authorised retrieval through the QHIN after verified identity, asynchronously, but it returns DocumentReference bundles with the original C-CDA files rather than conditions, medications and labs as FHIR resources, and no revoke call is described.

- not this job: Aidbox (Health Samurai, Inc.): A FHIR server an organisation runs; it can expose its own data through a SMART Patient Access API but does not fetch a person's records from outside providers.
- not this job: Medplum (Orangebot, Inc.): A headless EHR and FHIR server; it does not fetch a person's records from their providers.
- not this job: Metriport Medical API (Metriport Inc.): Production requires a covered entity with an NPI querying for treatment; there is no patient-mediated sign-in flow.
- not this job: Particle Health (Particle Health, Inc.): Exchange runs under HIPAA treatment, payment and operations purposes for covered entities; no patient-mediated sign-in or individual access flow is documented.
- not this job: Redox (Redox, Inc.): Built for software vendors and covered entities connecting to EHRs and networks; no patient-mediated sign-in flow.
- not this job: ROOK (Rookeries Development Corp.): Wearable and phone health data only; the EHR/EMR API is on a waitlist per the listing.
- not this job: Terra API (Terra Enabling Developers Inc.): Wearable, app and lab-test data; no provider record retrieval.
- not this job: Validic Inform (Validic, Inc.): Device and app data only; no provider records.
- not this job: Zus Health (Zus Health, Inc.): Built for care organisations it onboards; patients appear through opt-out sharing, not a patient sign-in and consent flow.

## What stops agents finishing

- provider not reachable, so the record comes back empty
- the person must sign in to each portal; the agent cannot
- older records exist only as faxed or scanned PDFs

## Around it

Before: personal-assistants.connect. After: document-extraction.extract, personal-assistants.answer.

## Where this comes from

Weight 14 of 100 in Health records & wellness data: 5 of 36 use-case citations across 34 accounts, scaled to 100

As data: https://www.anchorterminal.com/api/v1/use-cases/health-data.patient-records.json, or the MCP tool get_use_case with id health-data.patient-records. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
