Daily operations · Six signals · one working queue
Open one queue. Know what needs attention now.
Bring unsigned consent, unbilled care, outstanding balances, overdue lab cases, post-op instructions and proposal follow-up into one working list. Open the source and decide the next step.
CLINIC CONTEXTAcross your clinicSix sources · staff decisions
ConnectedOpenSnoozeResolve
01Groups urgent, today, follow-up, billing, clinical, lab and patient-moment work
02Routes each item back to the relevant patient or workflow
03Supports done, dismiss and snooze decisions with a visible completed state
04Keeps the queue scoped to the clinic and permissions of the signed-in user
Why this workflow matters
THE CLINIC MOMENT
The work appears only after it is late.
Across the clinic, a consent still needs a signature, completed care needs an invoice and a lab case has passed its due date. A balance, post-op instructions and a proposal follow-up need owners too. The work already exists; it needs one visible starting point.
×Clinic work is often spread across memory, paper notes, inboxes and separate reports. Important work becomes visible only after it is late.
×The next owner and source record are unclear.
✓Bring unsigned consent, unbilled care, outstanding balances, overdue lab cases, post-op instructions and proposal follow-up into one working list. Open the source and decide the next step.
✓Open the record you need without searching for the patient again.
HOW IT WORKS
Surface the signal, make the decision, continue in context.
Follow the task from its first entry to the next person who needs it.
- 01
Surface
Recorded consent, treatment, invoice, lab, post-op and proposal states generate eligible tasks under the clinic’s rules.
- 02
Decide
Open the source, snooze the item, dismiss it or mark the work done.
- 03
Continue
Open the patient, invoice, appointment, lab case or clinical workflow without searching again.
ONE WORKFLOW · 4 CHECKPOINTS
Follow one action from clinic signal to source record.
The queue is useful because it preserves the context needed to decide and continue—not because it creates another list.
The work already exists in six source records.
An unsigned consent, completed unbilled care, open balance, overdue lab case, unsent required aftercare and due proposal follow-up can each create work under the clinic’s rules.
CLINIC CONTEXTAcross your clinicSix sources · staff decisions
ConnectedOpenSnoozeResolve
The work sorts into a day the team can read.
Eligible items keep their patient, reason and source context. Organised does not mean completed.
CLINIC CONTEXTAcross your clinicSix sources · staff decisions
ConnectedOpenSnoozeResolve
Open, snooze or mark handled deliberately.
The user reviews the task and chooses the next step. Surfacing an item does not send a message or silently complete operational work.
CLINIC CONTEXTAcross your clinicSix sources · staff decisions
ConnectedOpenSnoozeResolve
Open the record that can settle the action.
Continue in the consent, treatment, invoice, lab case, post-op instructions or proposal without searching again.
CLINIC CONTEXTAcross your clinicSix sources · staff decisions
ConnectedOpenSnoozeResolve
One working list
Turn operational signals into a day your team can act on
Thirty2OS builds a day view from appointments, treatments, invoices, lab work, prescriptions, recalls and patient occasions. The result is a working queue rather than another static dashboard.
Items retain their record context, so staff can open the relevant workflow instead of copying names and identifiers between systems.
- Consent awaiting the patient’s signature
- Completed treatment awaiting an invoice
- Outstanding invoice balance requiring follow-up
- Lab case past its expected date
- Required post-op instructions not yet shared
- Treatment proposal with a follow-up date due
Controlled actions
Keep the decision with the person doing the work
Team members can open the source record, complete an item, snooze it or dismiss it when it is not relevant. Completed work stays visible in the done group for the day.
Permissions and selected-clinic context still apply. A surfaced task does not grant access that the user does not already have.
Evaluate it honestly
Test the queue against your real exceptions
During a trial, compare the generated queue with the work your front desk and clinicians already track. Review false positives, missing local routines and the ownership model before making it the team’s starting point.
Permissions and workflow boundaries
ROLES & PERMISSIONS
The queue respects role and clinic boundaries.
The queue respects the signed-in user’s selected clinic and existing permissions. Surfacing an item does not grant access to its underlying record.
WHERE IT STOPS
What your team still decides.
The Action Engine organises signals recorded in Thirty2OS. It cannot see work kept outside the system, guarantee every follow-up or complete a task without a staff decision.
Plan your trial
TRIAL PLAN
Run the queue beside the paper list for five days.
Try these tasks with fictional patient details and the roles your team uses. Note any setup question or step that needs a different process.
- Compare the queue with the clinic’s paper list for five working days
- Open each action and verify its source record
- Test snooze, dismiss and done states
- Sign in with a restricted role
- Document any local signal the trial does not represent
QUESTIONS TO ASK
Does it complete clinic work automatically?
No. It surfaces eligible work and routes a user to context; staff choose and complete the action.
Can it guarantee that every follow-up happens?
No. It organises recorded signals and action state, while the clinic remains responsible for ownership and outreach.
YOUR CLINIC · YOUR EXCEPTION
Bring the handoff that keeps breaking.
Start free to test the workflow yourself, or book a guided demo when you want help mapping the exception.