Niches · Health records & wellness data
Fetch a person's own records from their providers with their consent
One company's docs show a full fit.
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. No docs we read state these figures, so they don't count against a listing here.
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 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Medblocks D 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. source |
Does the job, with a limit 2
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.
| Listing | Why |
|---|---|
| 1upHealth D 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. source |
| Health Gorilla C 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. source |
Doesn't do this job 9
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Aidbox B 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. source |
| Medplum B Orangebot, Inc. | A headless EHR and FHIR server; it does not fetch a person's records from their providers. source |
| Metriport Medical API D Metriport Inc. | Production requires a covered entity with an NPI querying for treatment; there is no patient-mediated sign-in flow. source |
| Particle Health E 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. source |
| Redox C Redox, Inc. | Built for software vendors and covered entities connecting to EHRs and networks; no patient-mediated sign-in flow. source |
| ROOK C Rookeries Development Corp. | Wearable and phone health data only; the EHR/EMR API is on a waitlist per the listing. source |
| Terra API B Terra Enabling Developers Inc. | Wearable, app and lab-test data; no provider record retrieval. source |
| Validic Inform D Validic, Inc. | Device and app data only; no provider records. source |
| Zus Health C Zus Health, Inc. | Built for care organisations it onboards; patients appear through opt-out sharing, not a patient sign-in and consent flow. source |
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
The same as data: /api/v1/use-cases/health-data.patient-records.json, or the MCP tool get_use_case with id health-data.patient-records. Other jobs in this category: /api/v1/niches?category=health-data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.