Skip to content
Writing
Industry playbooks

The hospital front desk is the real EMR

Hospital software is sold on clinical features and lived at the registration counter. Everything downstream — the consultation note, the pharmacy issue, the discharge summary, the insurance claim — inherits whatever the front desk captured in ninety seconds while a queue built up behind the patient.

2 min readOadbox

One patient, one identity, forever

The single most expensive defect in hospital data is the duplicate patient. The same person registers in 2023 as a walk-in, in 2024 through a camp, and in 2026 as an inpatient, and the system holds three records with three histories.

Preventing it is a front desk design problem: search before create, search on phone number and partial name rather than exact spelling, surface likely matches with last visit date, and make merging a two-click operation an administrator can perform without a support ticket.

The queue is part of the record

Registration, token, consultation, investigation, pharmacy, review — a patient touches the desk four or five times in a single OPD visit. If each touch is a fresh lookup, the desk spends its day re-establishing context and the patient spends their day repeating themselves.

Treating the visit as a single moving object solves this. The token carries the state; the desk sees where the patient is, what is pending and what has been paid, without opening four screens.

  • Registration to consultation: does the doctor see the vitals the nurse took?
  • Consultation to investigation: does the lab get the order, or a paper chit?
  • Investigation to review: is the report on the same visit, or a new one?
  • Visit to billing: is the bill assembled from what happened, or re-entered?

Billing is a clinical record with a rupee sign

Every billable line is also a clinical fact: a procedure performed, a drug issued, a bed occupied for a night. When billing is a separate system fed by hand, the two diverge — and the version with the money in it is the one that gets defended.

Assembling the bill from recorded events instead of from memory has a second benefit at claim time. A discharge summary, an itemised bill and an investigation trail that agree with one another is a claim that does not come back for query.

Design for the third shift

The daytime front desk has three trained people and a supervisor. The 2am front desk has one person who joined last month, handling an emergency admission. The system has to be usable by that person, on that night, with nobody to ask.

That means safe defaults, no destructive action without confirmation, and every screen readable by someone who has not been trained on it. It is a low bar, and most hospital software fails it.

HealthcareOperationsRecords

Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.

Eleven products, already running. One of them probably fits how you work.

See it on your own data rather than in a slide deck — thirty minutes with someone from the product team.