Niches · Health records & wellness data
Read and write patients and observations in an organisation's own FHIR server
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A search returns only the requested resources and fields with working paging links, a conditional create on an identifier does not duplicate the patient, a write the policy forbids is refused with an OperationOutcome, and the written observation reads back unchanged.
Measured, for our own tests: a patient summary read within 20,000 tokens. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: find this patient's last three blood pressure readings
, record this observation
, create the patient if they do not exist
, what does this patient's chart say
Does the job, with a limit 4
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. | The 1up FHIR Server validates posted resources against base R4 (400 on invalid), writes Provenance on every create and update, and publishes /r4/metadata. It is a payer platform under an order form; conditional create, _elements and access-policy docs were not found in the pages read. source |
| Aidbox B Health Samurai, Inc. | Search takes _elements, _count and _page with first, next and last links, the MCP has conditional update and create with headers plus validate, and SMART scopes and AccessPolicy deny with 403. The MCP module is alpha, and scopes are enforced only when the token's atv claim is 2. source |
| Medplum B Orangebot, Inc. | Search pages with _count up to 1,000 and _cursor next links, access policies grant read-only per resource, and fhir-request does full CRUD with conditional headers. But fhir-request returns the raw bundle, which overflowed context for a real patient, and search and fetch are stubs (acc-15, issue 9616 open). source |
| Zus Health C Zus Health, Inc. | The FHIR R4 API supports conditional create, update and delete by identifier, Zus-If-Match on updates, transaction Bundles and summarising lenses, and writes go back for the builder's own patients. No error body format or read-only scope enforcement was found in the pages read. source |
Doesn't do this job 8
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Health Gorilla C Health Gorilla, Inc. | A network retrieval and lab API with writeback for supported resources, not an organisation's own FHIR store. source |
| Medblocks D Medblocks Inc. | Medblocks stores pulled records and can export them to a destination FHIR R4 server, but it is not an organisation's own read-write FHIR store. source |
| Metriport Medical API D Metriport Inc. | Consolidated data can be read and written as a Bundle, but every API key has full access including destructive operations, so a policy-forbidden write cannot be refused. source |
| Particle Health E Particle Health, Inc. | Returns retrieved data as FHIR datasets; it is not an organisation's own read-write FHIR store. source |
| Redox C Redox, Inc. | Redox translates and routes data between systems and destinations; it is not the organisation's own FHIR store. source |
| ROOK C Rookeries Development Corp. | Not a FHIR server; data arrives in ROOK's own sleep, physical and body schema. source |
| Terra API B Terra Enabling Developers Inc. | Not a FHIR server; data uses Terra's own data models. source |
| Validic Inform D Validic, Inc. | Not a FHIR server; records use Validic's own summary, sleep, workout and measurement resources. source |
What stops agents finishing
- MCP returns raw bundles that overflow the context
- MCP tool can delete or overwrite anything the token allows
- self-hosted OAuth for a CLI client not documented
Around it
Before: health-data.network-records, health-data.patient-records. After: scheduling.book, messaging.sms.
Where this comes from
Weight 22 of 100 in Health records & wellness data: 8 of 36 use-case citations across 34 accounts, scaled to 100
The same as data: /api/v1/use-cases/health-data.fhir-store.json, or the MCP tool get_use_case with id health-data.fhir-store. 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.