FHIR R4 data layer
A FHIR server per app with search, history, transactions and terminology.
Digital health builders
A FHIR backend and the admin tools around it.
Spend your engineering time on the product your patients see. HealthTable gives you the FHIR data layer, the operations tools your clinical team needs and the audit and hosting rules your customers will ask about.
Create a record
curl https://api.healthtable.example/api/v1/tables/$TABLE_ID/records \
-H "Authorization: Bearer $HT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"data": {
"fld_reason": "Medication question",
"fld_due_at": "2026-11-02T16:00:00Z",
"fld_patient": ["rec_pt482"]
}
}'What you build
The parts every health product rebuilds.
Use them from HealthTable and keep your own code focused on what makes your product different.
Internal tools
Admin, support and clinical ops pages built on the same data, without a separate admin app.
Events to your stack
Signed webhooks when records change, with retries and backoff.
Scoped API keys
Keys limited to the tables and actions each service needs.
HIPAA hosting cells
Shared or dedicated cells, with your own database and network when a customer requires it.
Mobile shell In development
One mobile app that renders your interfaces.
Standards
Integrate through the standard, not a custom mapping.
Your product writes FHIR resources. Your clinical team sees tables and pages. Your customers' systems read the same data through FHIR R4 or the REST API.
- OpenAPI 3.1 spec for the REST surface
- SMART configuration discovery and OAuth endpoints
- Bulk Data $export for analytics
- HL7 v2, CDA and X12 Roadmap
GET /metadata
CapabilityStatement · 19 resources from Core
Clinical installed · 45 resources
GET /Patient?family=Okafor
Bundle · searchset · 1 match
POST / transaction
Patient + Observation · 2 created
GET /Observation/obs82/_history
3 versions from the event log
GET /ValueSet/$expand
LOINC vital signs · 9 codes
Starts with
What you start from on day one.
Every solution is packs and patterns on the same platform. Nothing here is a separate product to buy or integrate.
FHIR Core, Clinical and Financial packs
54 tables mapped to R4 resources.
REST and FHIR APIs
Scoped keys, an OpenAPI spec and a FHIR endpoint per app.
Webhooks and MCP
Signed outbound events and a read only MCP server per app.
Dedicated cell
Your own database and network, in the region you choose.
Other solutions
Show us the workflow. We will show you the app.
Bring a process your team runs today. We will walk through how it looks on HealthTable, what is ready now and what is still on the roadmap.