Enrollment and consent
Intake forms that write to the patient record, with consent stored as a FHIR resource.
Care programs and patient outreach
Enrollment, consent, reminders and follow up, tracked in one place. When a patient goes quiet or asks for help, the program routes them to a coordinator with the full history in view.
Hi Sofia, your refill is due Friday. Reply 1 if you have it, 2 if you need help.
2. Pharmacy says prior auth is needed
Routed to coordinator queue · reason: access issue
This is Jordan from the support team. I can help with that today.
What you build
Programs fail in the gaps between steps. HealthTable keeps every patient, step and conversation in the same record so nothing falls through.
Intake forms that write to the patient record, with consent stored as a FHIR resource.
Reminders and check ins driven by dates on the record, not a spreadsheet someone has to remember.
Rules that move a patient into a coordinator queue the moment they need help.
Conversations by text and AI voice, logged against the patient.
Enrollment, response and escalation counts that respect each viewer's permissions.
Eligibility and check in questions stored as FHIR questionnaire responses.
Journeys
A program is a sequence of steps with branches for what the patient does. Today journeys are built as automations. A visual journey canvas for program teams is being built now, and you can see it working in the demo.
Starts with
Every solution is packs and patterns on the same platform. Nothing here is a separate product to buy or integrate.
People, organizations, tasks, activities and events.
Patient, Consent, Questionnaire responses and the resources programs touch.
Schedules, record triggers, branches, email and webhook actions.
Text and voice steps with consent checks In development
Other solutions
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.