Mednote
Healthcare · by Oadbox
The operating system for modern hospitals
Hospital management from OPD to IPD — appointments, pharmacy, lab, billing and claims in one system.
At a glance
- ABDM / ABHA ready
- FHIR integration
- 80+ permissions
Built for
Mid to large hospitals and multispeciality networks.
Live at
mednote.inThe problem
Used by the registration desk, the ward nurse and the billing clerk.
Everything downstream of a hospital visit inherits whatever the front desk captured in ninety seconds — and the discharge summary, the pharmacy issue and the insurance claim are each retyped from a record that already exists.
Mednote consolidates the departments a hospital usually runs on separate software: front desk, clinical care, pharmacy, laboratory, billing, HR and analytics. One patient record moves through all of them.
An AI layer watches the operational data and flags what a monthly report would miss — patients dropping off between visits, revenue leaking in the billing cycle, consultation slots going unused.
A day on Mednote
From the first token to the last discharge
Hospital software gets demoed in the director's cabin, but it earns its keep at the registration counter, the pharmacy window and the billing desk on discharge day. This is where Mednote sits in a normal working day.
What we counted first
Mednote began the way every Oadbox product does — standing at the front desk through OPD hour, at the lab bench and at the billing window while a family waited to go home. Four numbers kept coming back:
19
Registers between desk and ward
OP register, admission register, ward census, lab register, pharmacy stock book, claim tracker — each hand-ruled, each owned by one person who could never take leave.
31%
Consultation slots that sat empty
Counted off the appointment diary over a fortnight. Afternoons ran half empty while the morning queue stood in the corridor.
₹1.2L
Charges that never reached billing
A month of consumables and ward items written on loose slips that never made the walk from the ward to the billing desk.
26 days
Discharge to claim settlement
Claim files assembled by hand after the patient had gone home, then returned by the TPA for one missing document.
Counted during our own early site visits, before Mednote existed. Every hospital differs — your numbers are the first thing we ask about.
- 8:00 am
The registration counter
The front-desk clerk opens the queue as the shutters go up. Yesterday's reminders have gone out, so most of the booked list turns up, and walk-ins join the same queue instead of a second paper list. The OP slip prints with a token, and the ABHA number is linked once — at the first visit, not every visit.
- 9:30 am
Consulting room 4
A follow-up patient sits down and her record is already open — the last visit, the prescription written then, the reports that came back after. What the doctor records here goes onto the same file, and the lab order reaches the collection room before she has walked down the corridor. Nobody sends a runner to the records room for an old case sheet.
- 10:40 am
The lab bench
Samples arrive with the order already against them — no register entry, no slip pinned to a bottle. Results are entered, someone with the rights to validate signs them off, and the report lands on the patient's record rather than in a tray at the collection window. Who entered it and who validated it stays on the record.
- 1:15 pm
The pharmacy window
The counter bills against the prescription already on the record, with batch and expiry picked at the point of sale instead of written into a stock book after closing. The shelf count falls as each strip goes out, and the evening indent is raised against what was actually consumed — not against what someone remembers running short of.
- 4:00 pm
The bed board
A patient moves from the general ward to a semi-private room, and the bed board changes as the transfer is recorded — the ward census is not rebuilt by hand at shift change. The duty nurse taking over at four is the one on the roster, and her attendance is already marked against that shift.
- 6:30 pm
The billing window
A patient's son waits at the window while the discharge bill assembles from what actually happened — room days, pharmacy, lab, and the package rate where one applies. The discharge summary comes off the same record. The insurance portion goes to the TPA as a claim file built from that record, so nothing is left off because a slip stayed in the ward.
- Month-end
The month-end review
Collections, claim ageing, bed occupancy and slot usage sit on one screen, instead of four departments compiling for a week. Alongside them the system points at what a monthly report would miss — the consultation slots that sat empty on Tuesday afternoons, the follow-ups never rebooked, and the charges that never reached a bill.
What quietly disappears
None of this is dramatic. It is the same hospital day — minus the artefacts everyone assumed were permanent.
The OP register at the front desk
The case sheet hunted for before a follow-up
The pharmacy stock book written up after closing
The loose consumable slips that never reached billing
The photocopied claim file couriered to the TPA
Key workflows
What it actually runs.
Appointments and reminders
Doctor-wise slots, walk-in queues and automated reminders that cut no-shows.
OPD and IPD
Consultations, prescriptions, ward and bed management, transfers and discharge summaries.
Pharmacy point of sale
Counter billing with batch, expiry and stock tracking, and indents raised against actual consumption.
Laboratory
Order to report — sample collection, result entry, validation and delivery to the patient record.
Billing and claims
Package and tariff handling, insurance claims and revenue cycle management end to end.
Workforce management
Rosters, attendance and payroll for clinical and non-clinical staff.
AI operational insights
Patient drop-off detection, revenue-leak identification and slot optimisation, surfaced as actions.
Compliance by default
ABDM/ABHA alignment, FHIR interoperability, 80+ granular permissions and complete audit logging.
Why Oadbox
We know the industry
Mednote was designed inside healthcare operations, not adapted from a horizontal tool.
How healthcare worksIt runs on our core
Tenancy, permissions, statutory compliance, offline mobile and audit trails are inherited, not rebuilt for each product.
Inside the platformWe still operate it
The team that built Mednote runs it — monitoring, support, releases and the next version.
How we workMore from Oadbox
11 other products, same foundation.
Want to see Mednote on your own data? That is the only demo worth having.
Thirty minutes with someone from the product team — how you work today, and an honest answer on whether this fits.