Heka for longevity
The AI-native longevity clinic, built from the ground up.
Heka is building a new operating model where AI continuously understands the state of every patient, determines what should happen next, and helps move their care forward — without relying on staff to manually remember and coordinate every step.
Not AI layered onto the clinic. A clinic designed around AI from day one.
Start with the operating model
Most healthcare AI starts with an existing clinic. We’re starting with a blank sheet of paper.
Healthcare workflows were built around humans reading charts, remembering follow-ups, moving information between systems, creating tasks, chasing responses, and deciding what to look at next.
Most AI companies inherit those workflows and automate pieces of them.
Heka has an unusual opportunity to do something different. We are piloting inside a physician-owned longevity clinic where our team works directly with the clinic’s operators to rethink the care model itself, before patient volume and legacy processes become entrenched.
If AI were foundational from day one, how should this clinic actually operate?
Two ways to build
Automate the old model, or design a new one.
The usual approach
- Existing staffing
- Existing workflows
- Existing task lists
- Existing EMR
- Existing patient experience
Then add AI — automate pieces of the existing model.
The Heka approach
Design the service and the intelligence system together.
We’re not asking which existing administrative tasks AI can perform. We’re asking which tasks should continue to exist at all.
The operating problem
Longevity promises proactive care. Operating it manually is anything but simple.
To run a proactive panel, a clinic operator needs to answer all of this, for every patient, continuously:
- Has this patient seen the dietitian?
- Have they seen the exercise physiologist?
- When did they last speak with their physician?
- What are they actively working on?
- Should their bloodwork be repeated?
- Which biomarkers are being monitored?
- Which screenings are due?
- Which referrals are unanswered?
- Has enough time passed that we should reach out?
Today much of that means clicking from a patient panel into individual charts, reading through notes to find the last interaction, and manually creating tasks for physicians or coordinators.
The challenge isn’t storing patient information. It’s continuously operationalizing it.
Persistent patient state
The EMR remembers the past. Heka keeps track of the present.
In the EMR
- Visit note
- Lab result
- Referral
- Phone call
- Prescription
- Consultation letter
- Another lab result
Accurate, complete, and entirely historical. Every question about right now has to be reconstructed by a person.
In Heka
Continuous, not on demand
Imagine a coordinator who never forgets a patient.
Traditional software waits for somebody to open it. Heka’s agents run continuously against the state of the whole panel — checking what has changed, which obligations remain open, which deadlines are approaching, and where action is required.
Heka at work
The clinic doesn’t wait for somebody to remember.
Preventive obligations
Preventive care shouldn’t depend on someone creating a reminder.
Mammograms, cervical screening, colon screening, bone density, vaccination review — most of it is standardized by age, sex or clinic protocol. It should appear on its own, not be recreated by hand in a task inbox.
- ✓Cervical screeningCompleted Jan 2026
- ✓MammogramCompleted Apr 2026
- ○Colon screeningNext due May 2028
- ○DEXADue soon
- ○Vaccination reviewDue November
Biomarkers as threads
A biomarker isn’t just a number in a chart.
A result belongs to a thread: what is being worked on, what the target is, when it should be repeated, and who is waiting on it. The care team should see that without digging through the chart.
Heka tracks the thread and the timing. The clinic defines the targets and the intervention pathway.
Executable care plans
What if the care plan didn’t end as text?
Notes already contain the plan — concern, intervention, repeat in three months, follow up afterward. Today that stays documentation until a human turns it into tasks.
Patient communication
White-glove shouldn’t mean manually written every time.
Today this is often a document of templates, copied, personalized and sent by hand, one patient at a time.
The goal isn’t to make copy-and-paste faster. It’s to eliminate the need for copy-and-paste.
The agentic difference
Dashboards tell people what work exists. Heka is being built to do the work.
01
Understand
New information enters the clinic.
02
Maintain state
Heka determines what changed.
03
Determine next step
Clinic-defined rules and workflows establish what should happen.
04
Act
Heka prepares or performs the operational work it can own.
05
Escalate
Humans enter where judgment or approval is appropriate.
06
Keep watching
Heka remains responsible for the unresolved outcome.
Heka doesn’t complete an automation and forget the patient. It acts, updates state, and keeps watching.
Built with operators
We’re discovering the workflow before we automate it.
Heka’s team works directly with the clinic’s operators to map how care actually happens, rather than digitizing the manual process that exists today.
We don’t want to automate a bad process. We want to determine whether that process should exist at all.
- What does the care team look at every morning?
- What creates a follow-up?
- What should happen when a result arrives?
- Which timelines matter?
- Which communication should happen automatically?
- Which events require physician judgment?
- Which administrative steps should disappear entirely?
A live environment for building AI-native care
Build the operating model before the legacy model takes over.
Heka is piloting this model inside a physician-owned longevity clinic in Alberta. The clinic is early enough in its development that we can work directly with physicians and operations leadership before patient volume, staffing structures and legacy workflows become entrenched.
Rather than asking an established clinic to reorganize itself around new technology, the clinic and the technology can evolve together.
- 1Observe clinic operation
- 2Identify manual coordination
- 3Question whether it should exist
- 4Design AI-native workflow
- 5Deploy inside the clinic
- 6Observe patient and operator experience
- ↻Refine the operating model
Scope
AI-native means redesigning more than the software.
Patient experience
How does a patient experience a clinic that proactively knows what is happening?
Care model
Which touchpoints should occur proactively rather than only when patients initiate them?
Coordination
Which referrals, results, screenings and follow-ups can Heka manage continuously?
Communication
Which patient interactions should be automatically initiated, prepared, personalized or routed?
Staffing
What work remains uniquely human when routine coordination moves into Heka?
Physician attention
How do we concentrate physician time on judgment and relationships rather than operational reconstruction?
Attention is the scarce resource
The goal isn’t to replace the care team. It’s to stop wasting their attention.
Today · operator attention
- Check charts
- Remember deadlines
- Create tasks
- Copy templates
- Call offices
- Check referral status
- Review inbox
- Reconstruct patient history
Heka
- Maintains state
- Monitors time
- Tracks open loops
- Prepares communication
- Chases routine status
- Updates patient context
Humans
- Clinical judgment
- Patient relationships
- Complex decisions
- Escalations
- Care design
What we’re trying to prove
More patients should not mean proportionally more coordination.
The near-term goal is to prove that a clinic designed around this model can provide a meaningfully more proactive, white-glove experience while allowing each physician and care team to effectively maintain more patient relationships.
Traditional model
- More patients
- More tasks
- More coordinators
- More complexity
AI-native model
- More patients
- More states maintained by Heka
- More coordination absorbed by agents
- Human attention remains concentrated
From software to operating model
If this works, Heka isn’t just software used by the clinic. Heka becomes part of how the clinic operates.
Our goal is to prove a repeatable model where persistent patient intelligence and agents absorb much of the operational work required to deliver proactive longevity care. The result is not a better dashboard or a more efficient task list. It is a different way to organize the service itself.
The operating model for an AI-native clinic.
Heka for longevity
We’re building the clinic around what AI can do from day one.
See the operating model, the agentic system behind it, and what we’re learning as we build it inside a real longevity clinic.