Patient Orchestration

Product vision and a coded prototype that made the patient — not the product queue — the primary object across Tennr's workflows. Adopted by sales within weeks.

2026 · Staff Product Designer

Patient Hub: fifty patients in one list with status, stage, and recent activity

Tennr sold intake, eligibility, and qualification as separate products — a patient cleared one and started the next with nothing carrying state between them. Patient Hub makes the patient, not the queue, the primary object.

A patient record showing the care journey stage by stage, missing information, and open tasks

One record holds what operations teams used to reconstruct by hand every day — where the patient is, what is blocking them, which documents are missing, and who owns the next action.

The workspace home: a welcome screen with an Ask Tennr prompt and starting templates

Ask Tennr works in levels of intervention: routine findings resolve quietly, recommendations are proposed, conflicts escalate with their sources. Consequential decisions stay with a person.

The Ask Tennr dock over Patient Hub, surfacing qualified patients for an outreach campaign with evidence and one confirm action

The same record turns into action — opportunities surface with the evidence behind them, and outreach happens without leaving the workflow. Sales adopted the coded prototype within weeks, and the Patient Hub architecture shipped.