The healthcare app platform

Build the apps your care teams run on.

HealthTable is one engine for tables, interfaces and automations, with FHIR R4 data, AI agents and HIPAA hosting built in. Start from a healthcare pack, shape it to how your team works, and change it the day the workflow changes.

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

FHIR shaped tables your team edits like a spreadsheet.

  • FHIR R4A FHIR server behind every clinical app
  • 54 FHIR tablesCore, Clinical and Financial packs
  • BAA covered AIPrompts only reach models under a BAA
  • Dedicated cellsYour own database and network when you need it
  • SOC 2 Type 2 reportSelah Digital, the team behind HealthTable (2025)

One engine

Three building blocks. Every healthcare app.

A triage queue, a referral tracker and a patient program look different on screen. Underneath they are the same three things, so you learn the platform once and build on it for years.

Tables

Typed fields, links between records and FHIR datatypes. Grid, kanban, calendar, gallery and form views. Every edit is versioned.

Interfaces

Pages built from lists, record details, forms and charts. Give people one screen without giving them the whole app.

Automations

Triggers on records, schedules, forms and webhooks. Actions that create tasks, send email, call APIs or run an AI step.

Template packs

Start from a pack, not a blank page.

Packs install a ready shape on the engine: tables, fields, pages and automations. The FHIR packs map every table to an R4 resource, so clinical data is standard from the first record.

  • Common pack: people, organizations, tasks, activities and events
  • FHIR Core, Clinical and Financial packs: 54 tables in total
  • CRM and outreach packs In development
How the engine works

How it works

From a workflow on a whiteboard to an app your team uses.

  1. 01

    Install a pack

    Pick the closest starting point. FHIR tables, pages and sample automations arrive in one step.

  2. 02

    Shape it to your workflow

    Add fields, pages and rules by hand, or describe the change and let the builder agent propose it for your review.

  3. 03

    Run it with guardrails

    Permissions, audit and patient data rules are on from day one. Every change is logged and can be traced or undone.

FHIR apps

Every clinical app is also a FHIR R4 server.

Install the FHIR packs and the app gets its own R4 endpoint: read, search, create, update, history, transactions and terminology. Your team works in tables and pages. Your partners integrate through the standard.

  • Search with chains, _include and _revinclude
  • Version history for every resource, straight from the event log
  • SNOMED CT, LOINC, RxNorm and ICD 10 lookups
Explore FHIR apps

AI agents

AI that works through the same doors your team does.

Agents call the same APIs as the web app, under the permissions of the person asking. They propose, a person approves, and every change lands in the event log with a name on it.

Builder agentDescribe an app, review the proposed tables and pages, apply or undo.
Analyst agentAsk in plain language. It shows the query it ran and never writes.
How the agents work

Developers

REST. FHIR. Webhooks. MCP.

Scoped API keys, an OpenAPI 3.1 spec, signed outbound webhooks and a read only MCP server for every app. Build your own product on HealthTable, or plug it into the tools you already run.

Read the developer overview
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"]
    }
  }'

Security

Governance is in the foundation, not added at the end.

The controls that are painful to retrofit are part of the engine, and they hold for every app you build.

Dedicated cells

One customer, its own database and network, pinned to a region.

Complete audit

Every write, and every read of patient data, recorded with who did it.

Field level access

Roles, row rules, field rules and grants for a single page.

No PHI in logs

Record contents never reach application logs.

Built by Selah Digital

Software, and a team that runs programs on it.

HealthTable is built by Selah Digital, a technology firm that works only in healthcare. The same team can configure, launch and operate your program, so you are never left alone with a blank platform.

About Selah Digital
  • Healthcare onlyEvery client and every project is in healthcare.
  • SOC 2 Type 2 reportSelah Digital, 2025.
  • Program operationsConfiguration, launch and day to day running, if you want it.
  • Working demoA full patient program built by the team, ready to walk through.

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.