External work, internal visibility · Case due before patient arrives
See which lab case is due before the patient arrives.
Keep the patient, treatment, lab, due date and case status together. Record the lab cost, payments and remaining balance before deciding what needs a follow-up.
PATIENT CONTEXTPatient 024Crown delivery · connected records
Connected01Patient, doctor, treatment and lab links
02Work, order and expected-date context with configurable statuses
03Cost, paid and balance fields with payment ledger
04Optional synchronisation into the clinic expense workflow
Why this workflow matters
THE CLINIC MOMENT
The calendar says ready. The crown is still overdue.
Patient 024 is booked for crown delivery, but the overdue lab slip is still on paper and the vendor balance is recorded elsewhere. The schedule looks ready while the external dependency is not.
×Lab cases become difficult to chase when due dates, patient context, vendor cost and payment notes are kept in different places.
×The next owner and source record are unclear.
✓Keep the patient, treatment, lab, due date and case status together. Record the lab cost, payments and remaining balance before deciding what needs a follow-up.
✓Open the record you need without searching for the patient again.
HOW IT WORKS
Open due context, reconcile the case and route the action.
Follow the task from its first entry to the next person who needs it.
- 01
Link the case
Connect patient, treatment, doctor, laboratory and expected date.
- 02
Track progress
Review supported case status and due-date context before the patient arrives.
- 03
Reconcile money
Record costs and payments with balance validation and optional expense linkage where configured.
ONE WORKFLOW · 4 CHECKPOINTS
Carry the crown case from due date to accountable action.
Patient, treatment, due date, status, cost and payment context stay around the same lab case.
The crown is overdue before the 11:30 visit.
The due signal remains tied to Patient 024 and the crown treatment.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedOpen patient, treatment and laboratory context together.
The team can review what the case is for before contacting anyone.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedUpdate status and money from verified information.
Status, cost and payment fields still depend on authorised clinic entries.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedSurface the overdue case before the visit.
The Action Engine can route a user back to the case; it does not imply a laboratory integration.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedCase context
Keep the lab order attached to the clinical record
A lab-work entry can link the patient, doctor, treatment and lab with work details, dates, status, cost and notes. Treatment linking can carry relevant context into the order rather than relying on a manually typed patient reference.
Due work
Surface cases that need attention
Expected dates and status make due or overdue lab work available to the action engine. Staff can open the source workflow and update the record after contacting the laboratory.
Cost and payments
Connect lab cost to the clinic’s expense picture
Record the lab charge, payments and remaining balance on the case. Where expense linking is enabled, the related expense stays connected; changes must follow the supported editing process.
The lab ledger records what the clinic owes the laboratory. It is separate from what the patient owes on an invoice; lab tracking does not imply a direct lab-to-patient-invoice integration.
Case cost, payment and balance
Case cost, payment and balance
- 01Record the case cost
Keep the laboratory’s charge with the patient-linked work and expected date.
- 02Record each payment
Preserve partial-payment entries under the case’s balance validation.
- 03Review what remains
Check the remaining lab balance and any supported expense link before reconciliation.
A clearer lab handoff
Share the lab order from its recorded case
Use the supported WhatsApp lab-order workflow with the laboratory’s saved contact. Review the clinic case reference, work details and expected date before sending. Update the case after the laboratory responds; a message does not change its status by itself.
Permissions and workflow boundaries
ROLES & PERMISSIONS
The record cannot replace the laboratory handoff.
Lab, clinical and finance access can follow different permissions. The source patient and treatment remain protected by their existing access rules.
WHERE IT STOPS
What your team still decides.
No live laboratory integration, courier tracking or automatic vendor update is claimed unless it is separately demonstrated for the deployment.
Plan your trial
TRIAL PLAN
Rehearse an overdue case and part-payment.
Try these tasks with fictional patient details and the roles your team uses. Note any setup question or step that needs a different process.
- Create a treatment-linked case
- Move it into an overdue state
- Record a partial lab payment
- Test balance validation
- Review optional expense linkage separately
QUESTIONS TO ASK
Can the laboratory update the case directly?
Not unless a separate supported workflow is demonstrated for the deployment.
Is expense synchronisation mandatory?
No. Treat any supported expense linkage as an optional workflow to verify.
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.