Bitme
Hospital Cashier
Designed "Bitme" to Help Hospital Cashiers Stop Recording the Same Transaction Twice
Bitme is a hospital cashier system that connects patient queues, payment processing, and transaction reporting in one workflow, reducing the need for cashiers to manually record the same transaction again in Excel.
Company
PT Cipta Integrasi Nusantara
Role
Product Designer
Timeline
2023
Platform
Desktop Web Application
As the Product Designer, I worked alongside the Product Owner and Product Manager to turn the hospital's cashier requirements into an end-to-end product experience. I owned the user research, workflow exploration, interaction design, UI, and prototype for the cashier transaction and reporting flow.
Problem & Goals
Payments were digital. Recording them wasn't.
Completing a patient payment did not mean the cashier's work was finished. After the payment, they still had to manually document the same transaction in Excel, including the bill number, medical record number, patient information, amount paid, and payment method. One transaction effectively created two jobs: process the payment, then record the payment.
Patient and billing information that already existed had to be typed again into Excel.
A payment could already be completed while its transaction record was still missing from the spreadsheet.
Manual entry meant formats could vary between cashiers, making the data harder to search and reconcile.
The daily report was only as reliable as the spreadsheet that had been maintained throughout the shift.
Opportunity
The cashier was essentially recording the same transaction twice.
Replacing the spreadsheet with another form would only move the same manual work somewhere else.
" If Bitme already knows the patient, bill, amount, and payment method, there is no reason to ask the cashier to enter the same information again."
How might we...
How might we let cashiers process a patient payment once, while Bitme handles the transaction record automatically?
Solution
Solution
One patient. One active action.
In the cashier queue, only the patient currently being served can be processed. I intentionally kept the Process button disabled for everyone else. The cashier already knows who they are handling, so giving every row the same active action would only create more room for mistakes. Instead of relying on a warning after the wrong patient is selected, Bitme prevents that choice from happening in the first place. Once the current transaction is completed, the next patient becomes active and their Process button is enabled automatically. This keeps the workflow simple, sequential, and easier to follow during a busy shift.
Process without losing the queue
The slide-out side panel provides a dedicated workspace for completing detailed tasks while keeping users connected to the main interface or parent view. By reducing unnecessary page transitions, it creates a smoother experience, improves efficiency, and helps users maintain workflow continuity with greater ease.
Only ask for what Bitme doesn't already know
By the time the cashier reaches payment, Bitme already knows the patient, the bill, and how much needs to be paid. For a cash transaction, the only new information the cashier needs to provide is how much cash they received. Bitme uses the existing bill amount to calculate the change automatically, instead of asking the cashier to enter information the system already has.
Applying a payment doesn't immediately close the patient's transaction. The cashier can still review the payment details and print the proof of payment first. Complete Transaction is different. It closes the current patient, creates the transaction record, and moves the cashier forward in the queue. Because that action changes the state of the workflow, I added one final confirmation before Bitme proceeds.
