Request a demo

Platform

One engine for tables, interfaces and automations.

Every HealthTable app is built from the same parts. Learn them once, then build the next app in a fraction of the time, with the same audit, permissions and data rules underneath.

Request a demoDeveloper overview
Triage · Patients
Patientsfhir.r4.PatientGridKanbanCalendar
Acuity is anySorted by acuity6 records
NameAcuityStatusNext stepOwner
Maya OkaforHighCall backNurse call by 2:30CR. Chen
Imani BrooksHighNewReview intakePJ. Patel
Daniel PryorMediumIn reviewLab follow upRA. Ruiz
Owen WalshMediumNewMedication questionPJ. Patel
Sofia MarinLowScheduledVisit Thu 10:00CR. Chen
Grace LiuLowClosedNoneRA. Ruiz

Tables

Structured data your team can actually edit.

Tables feel like a spreadsheet and behave like a database. Fields are typed, records link to each other, and every change is kept.

  • Text, number, date, select, checkbox, currency, link, lookup, rollup, formula and FHIR datatype fields
  • Grid, kanban, calendar, gallery and form views on the same records
  • Record history from the event log, down to the field
  • Filters, sorts and groups saved per view
Triage · Kanban
New 2
Imani BrooksFever 103.1 F
Owen WalshMedication question
Call back 1
Maya OkaforChest tightness
In review 1
Daniel PryorLab follow up
Scheduled 1
Sofia MarinVisit Thu 10:00
Triage · Patient detail
MO
Maya OkaforFemale, 54 · Primary care · Consent on file
High
Blood pressure142/91Above range
Heart rate88bpm
SpO297%Normal
Timeline

Intake note: chest tightness, 2 hrs

Categorized as cardiac by automation

Task created for on call nurse

Callback note
Reached patient, symptoms easing
Disposition: Same day visit
Save to Encounter

Interfaces

Give each person the one screen they need.

Interfaces are pages built from components: lists, record details, forms, charts and buttons. They are stored as structured definitions, so they can be reviewed, versioned and reused.

  • Interface grants for people who should only see one page
  • Public forms that write straight into a table
  • Charts and counts that respect the viewer's permissions

Automations

The busywork runs itself. People handle the judgment.

Build automations from triggers, conditions and actions. Each run is recorded step by step, so when something looks wrong you can see exactly what happened.

Triggers

Record created or updated, record matches a condition, schedule, form submitted, incoming webhook, button.

Actions

Create, update or find records, send email, call a webhook, run a sandboxed script, branch, loop.

AI steps

Categorize, extract fields and draft text, through the model gateway and its limits.

Triage · Automations
TriggerRecord created in Intake
AI stepCategorize the intake note
BranchCategory is cardiac or acuity is High
ActionCreate task for the on call nurse
ActionEmail the care team lead
Recent runs

Maya Okafor5 steps · 1:12 PM

Owen Walsh3 steps · 12:48 PM

Imani Brooks5 steps · 12:31 PM

Daniel Pryor3 steps · 11:57 AM

Packs and applications

Packs give an app its shape.

An application is a set of tables, pages and automations with its own permissions. Packs install a proven shape into it. Standard apps start from the Common pack. FHIR apps add Core, Clinical and Financial, and get their own R4 server.

  • Organizations hold many applications, each isolated from the others
  • Packs are versioned, and you add your own tables and fields on top
  • CRM and outreach packs In development
See what FHIR apps add

Under every app

The parts you would otherwise build yourself.

Most healthcare teams rebuild these for every tool. On HealthTable they come with the engine.

Event log

Every change is an event with an author, a time and the before and after. History, undo and audit all read from it.

Permissions

Roles, table rules, row and field rules, and interface grants. Row level security in the database keeps each app apart.

AI, governed

Builder and analyst agents, plus AI steps, all through one model gateway with budgets and BAA rules.

Mobile In development

Build it once. It shows up on the phone.

Because interfaces are stored as structured pages, one HealthTable app for iOS and Android will render them directly. A new page reaches the phone without an app store release.

  • Offline work for nurses in the field, synced when they reconnect
  • Push notifications that say nothing sensitive
  • Encrypted local storage and remote sign out

The mobile app is being built now and is not yet available.

Standards

Standards in. Standards out.

HealthTable speaks the formats healthcare already runs on, and works alongside the EHR rather than replacing it.

Clinical data

FHIR R4SNOMED CTLOINCRxNormICD 10

Developer surface

REST APIOpenAPI 3.1Scoped API keysWebhooksMCPZapier

Exchange formats Roadmap

HL7 v2Consolidated CDAX12 eligibility and claims

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.

Request a demoExplore the platform