A workflow carries the whole visit — protocols, pharmaceuticals, procedure maps — segment by segment. The note assembles itself along the way, and nothing enters the record until the provider approves it.
Live · walk a visit through
HRT — Pellet Insertion, segment by segment.
Click Advance (or any segment) to move the visit forward. Watch what each segment stages before anyone asks for it.
APPROVED
REAL STRUCTURE · segments, gates, and note assembly mirror the product workflow engine
Live · make it yours
Segments are settings, not code.
Toggle optional segments and watch the workflow restructure. Clinics tune this per service — in workflow settings, no engineers involved.
THIS SERVICE'S WORKFLOW
Reorder, add, or remove — each service carries its own workflow. Clinical segments keep their gates wherever they sit.
Setting it up
Set once, per service.
A workflow belongs to the service, not to whoever happens to be working. Every step below is a setting, not a release.
Services → the service → Workflow.Every service carries its own. Start from the one it ships with.
Order the segments.Consent, labs, prescription, treatment, note, follow-up — reorder, add or remove per service. Segments are settings, not code.
Stage the medicine in each segment.Protocols, the pharmaceuticals that segment needs, and the procedure map — injection, insertion — belong to the segment rather than to someone’s memory.
Set what fails closed.A treatment without valid consent does not start. A lab result out of range holds the booking until a provider reviews it.
Leave the note alone.It assembles itself from the segments as they complete. The provider edits and approves; nothing enters the record without their sign-off.
Where the edges are
What it does not do.
The boundaries, so nothing here is a surprise after you sign up.
A segment can be optional; a gate cannot. Clinical photos, a telehealth pre-visit, a membership offer — yours to include or skip. Consent and required labs are not: they fail closed by design.
The note is a draft until a provider signs it. Auto-populated is not auto-filed. After signing, a correction is an addendum, never an edit.
Workflows are per service, not per clinic. An HRT pellet insertion and a Botox visit carry different segments, because they are different medicine.
Changing a workflow does not rewrite history. A signed note keeps the template version, signer and timestamp it was signed against.
Questions people ask
Before you ask us.
And if the answer you want is not here, ask — questions are free.
Can we skip consent for a quick visit?
No. Clinical gates fail closed, so a treatment without valid consent does not start. Optional segments are optional; gates are not.
Do we need an engineer to change a workflow?
No. Segments are settings, not code — reorder, add or remove them per service.
What happens to notes signed under an older workflow?
Nothing. A signed note keeps the template version, signer and timestamp it was signed against.
Does the note write itself without us?
It drafts itself from the segments. The provider edits and approves, and nothing enters the record without that sign-off.
Walk your own service through.
Your treatments, your protocols, segment by segment.
CURRENTLY IN A CLOSED BETA · ONLINE DEMO COMING SOON