Feature
Revenue Leak Controls for Hospitals
A consultation is charged the moment an OPD visit is created, and if a patient still owes money when pharmacy dispenses, a lab result is released, or a patient is discharged, staff must record why — and it lands in a review queue instead of disappearing.
Trisvio closes four places hospitals typically lose money — unbilled consultations, underpaid pharmacy sales, underpaid lab releases and discharges with dues — by asking for a reason the moment money is missed, and giving an owner a queue to review every one.
- Who uses it
- Front desk, pharmacists, lab staff and the discharge desk record the reason at the point of care; admins and owners review the queue, decide discount requests, and run doctor payouts.
- What it records
- A revenue exception per gap — the expected amount, what was collected, the reason given and who gave it — plus discount requests/approvals and daily cash-close counts.
- What it prints / exports
- A revenue-control dashboard and review queue on screen, with a CSV export of the revenue-control figures — none of it is a statutory form.
What you get
- Every consultation is charged automaticallyAn OPD or follow-up visit and its consultation charge are created in the same step — a visit can’t exist without a charge or a recorded waiver, so a patient can’t be seen off the books.
- Pharmacy, lab and discharge gates catch underpaid moneyIf a pharmacy sale, a released lab result, or a discharge would go ahead with money still payable, Trisvio asks for a reason before letting it proceed. A hospital can choose to go further and refuse an underpaid counter sale or a routine discharge until the bill is settled; a lab result is never withheld for payment.
- A review queue, not a debt listEvery recorded exception lands in a queue an admin can review and resolve — payment collected, authorised credit, insurance, a data correction, or another named outcome — and nobody can resolve their own exception without a documented reason for doing so.
- Discounts need a second personA discount is requested at the counter and approved separately by someone with the authority to approve it — never by the person who asked for it, even if they hold both permissions on their own account.
- Day-close and doctor payouts close the loopCashiers count the drawer against the system total at day-end (informational, never blocking), and doctor payout runs are drafted from each doctor’s collected payments at a snapshotted revenue-share percentage, tracked from draft to paid.
How it works
The charge is born with the visit
Starting an OPD or follow-up encounter creates its consultation charge in the same step — there is no path that creates one without the other.
A gate watches the next three moments money can go missing
Pharmacy dispensing, a lab result release, and a patient discharge each check whether money is still payable before they complete.
Staff give a reason, once
If money is outstanding, staff type a reason before the action can finish; a lab release only asks the first time an order is underpaid, not on every later check of the same order.
The gap is recorded, not hidden
Trisvio records a revenue exception with the expected amount, what was collected and the reason given, then lets the clinical or billing action complete.
An admin reviews the queue
The pending queue groups every open exception by type — unbilled visits, pharmacy shortfalls, lab shortfalls, discharge shortfalls — for an admin to resolve with a named outcome.
Discounts, day-close and payouts run alongside it
Discount approvals, per-cashier day-close counts and doctor payout runs (draft to paid) use the same billing ledger, so the whole revenue picture stays in one place.
Who uses it
- Front desk / OPDA consultation is charged the moment a visit is created — nothing to remember to bill separately.
- Pharmacist / lab technicianIf a sale or a result release would go out with money still payable, you’re asked for a reason before it completes — and it’s recorded, not silently lost.
- Discharge deskA routine discharge with dues outstanding asks for a reason before it finalises, after any advance balance is applied first.
- Admin / ownerReview the pending exceptions queue, decide discount requests raised by someone else, close the day’s cash count, and run doctor payout batches.
In detail
What counts as a revenue leak vector today
Trisvio tracks four live leak vectors on its revenue-control dashboard, under the heading "Revenue leak vectors — pending review": unbilled visits (a consultation with no bill on record), pharmacy shortfalls (medicine dispensed underpaid), lab shortfalls (a result released underpaid) and discharge shortfalls (a patient discharged with dues outstanding). Each tile shows a count and an amount, and the oldest gate-caught exception is called out so nothing sits unreviewed for long.
The dashboard is a summary, not the workflow itself — the actual review queue lives on its own screen, titled "Revenue exceptions" with the subtitle "Billing gaps recorded at the point of care — a review queue, not a debt list." When nothing is pending, it says so plainly rather than showing an empty grid.
How a gap gets resolved
An admin resolves a pending exception with a named outcome — payment collected, authorised credit, insurance, an emergency, a data correction, a cancellation, a duplicate, or another reason — and every outcome is treated as an ordinary result, not a red flag. The person who first recorded the exception normally can’t resolve it themselves; on a single-admin hospital, resolving your own exception is still possible, but only with a separate, documented reason for doing so.
The same no-self-approval principle governs discounts: a discount is requested with a reason, and only someone holding the separate approval permission can accept or reject it — never the person who asked for it, even if they hold both permissions on their own account.
What doesn’t block care
None of these gates stop a doctor from treating a patient, medicine being dispensed to an admitted patient, or a lab from releasing a result. By default the only thing asked for is a typed reason at the moment money is missed, so the hospital has a record instead of a silent gap. A hospital can choose a stricter setting that refuses an underpaid pharmacy counter sale, or a routine discharge, until the bill is settled — a death, a LAMA, an abscondment or a referral always goes ahead with a reason. Day-end cash close works the same way: it compares counted cash against the system total per cashier, and it’s informational — it never blocks the day from closing.
Further reading
Frequently asked questions
Does a revenue exception stop a doctor from seeing a patient, or a pharmacist from dispensing medicine?
No check stops a doctor from seeing a patient, and dispensing to an admitted patient or releasing a lab result is never held for payment. A consultation is always charged automatically at the point a visit is created. By default, pharmacy counter sales and discharges only ask for a typed reason when money is still payable; a hospital can instead choose to refuse an underpaid counter sale, or a routine discharge, until the bill is settled.
Who can resolve a revenue exception?
Anyone with the right permission, except the person who originally recorded it — they can’t resolve their own exception without giving a separate, documented reason, which exists as a narrow escape hatch for a single-admin hospital rather than a routine path.
Can a staff member approve their own discount?
No. Requesting a discount and approving one are two different permissions, and the rule is absolute — even someone who holds both permissions on their account cannot approve a discount they requested themselves.
What happens if a patient’s advance deposit covers the discharge bill?
The patient’s unapplied advance balance is applied to the bill first. If that clears the amount payable, discharge completes with no reason required — the reason prompt only appears when money is still owed after the advance is used.
Is the day-end cash close mandatory, or can it block closing the register?
It’s informational only. It compares what a cashier counted against what the system expects for that day and records the variance — it never blocks or refuses a day close, even if the two numbers don’t match.