Triage the patient, not the paperwork.

An emergency department is the one part of a hospital where every other department's work converges in real time and under pressure. A patient walks in or arrives by ambulance and within minutes needs triage, registration (possibly as a medico-legal case), vitals, an initial clinical assessment, and then a disposition decision: treat and release, admit to a ward, transfer to OT, or refer elsewhere. In most tier-2 and tier-3 Indian hospitals, this process still runs on a paper register, a wall-mounted whiteboard, and the memory of whichever nurse happens to be on duty. OneCity's emergency department module replaces that with structured, colour-coded triage, time-stamped clinical documentation, and a clean electronic handoff to whatever comes next, without the patient needing to re-register at a second counter when the decision to admit is made.

Why the ED is the hardest module to get right

Every other hospital module, from OPD to pharmacy to billing, operates on the assumption that there is time: time to fill a form, time to look up a patient's history, time to confirm an allergy before dispensing. The emergency department operates on the assumption that there is not. The clinical workflow moves from triage to intervention to disposition in minutes, not hours, and any system that slows that flow, even by requiring a nurse to fill six fields before the screen lets her proceed, is a system the ED will stop using on its second busy night.

This is not an abstract design consideration. It is the concrete reason why most generic hospital management systems fail in the ED even when they work adequately everywhere else. An OPD queue system can afford a 30-second registration step because the patient is stable and waiting. An ED system that adds 30 seconds between a red-category patient's arrival and the first clinical intervention is 30 seconds too many. OneCity's ED module is built with this constraint as the design premise, not an afterthought: the triage screen captures category and chief complaint in under ten seconds, and everything else (demographics, history, contact details) can be filled in after the patient is stabilised, not before.

Colour-coded triage: how it actually works on screen

Triage in an Indian hospital context follows a colour-coded framework that India's National Medical Commission (NMC) has specified for teaching hospitals and that aligns with the broader international standard reflected in the WHO Interagency Integrated Triage Tool. The three primary categories are red (immediate: the patient cannot survive without immediate intervention), yellow (urgent/observation: needs care soon but is not in immediate danger of death), and green (non-urgent: can safely wait). NMC's own specifications for emergency departments in medical colleges allocate beds by these exact categories: 4 red, 15 yellow, 5 green out of 24 ED beds, which gives a concrete sense of the expected acuity distribution.

In OneCity's ED module, the triage nurse selects the category with a single tap on arrival. The patient's record is immediately colour-tagged across every screen in the department, so any clinician who pulls up the patient, whether on the ED dashboard, the lab results screen, or the IPD admission form, sees the triage category without having to ask. The category can be escalated or de-escalated as the patient's condition changes, with each change timestamped and attributed to the clinician who reassessed. The dashboard sorts patients by acuity, not arrival order, so the red-category patient who arrived after the green-category patient is always visible at the top, not buried below whoever came in first.

MLC registration: structured, not scribbled

A significant fraction of emergency department arrivals in Indian hospitals are medico-legal cases (MLCs): road traffic accidents, assaults, poisonings, burns, attempted suicides, and any case where the cause of injury or illness has potential legal consequences. Indian law requires hospitals to maintain an MLC register, record the time of arrival, notify the police, and preserve the documentation chain for potential court proceedings. For a deeper look at MLC register requirements and how they connect to the rest of the hospital's compliance obligations, see our MLC register software guide.

In OneCity's ED module, when a case is flagged as medico-legal at triage or registration, the system captures the MLC number, time of arrival (to the minute, since this is often contested in court proceedings), nature and mechanism of injury, brought-by details (police, ambulance, self, bystander), police intimation status, and the name of the treating doctor, all as structured fields rather than free-text entries in a notebook. This record is linked to the patient's main clinical file, so the MLC documentation and the clinical documentation are the same record viewed through different lenses, not two separate paper trails that may or may not agree with each other when someone checks months later.

The resuscitation log: documenting what happened, when

When a patient arrives in cardiac arrest or deteriorates into one in the ED, the priority is the resuscitation itself, not the documentation. But after the event, whether the outcome is ROSC (return of spontaneous circulation) or death, the clinical record must reflect what actually happened: which interventions were performed, in what order, at what time, and by whom. A paper-based resuscitation record is almost always reconstructed from memory after the event, which means timings are approximate, drug doses are recalled rather than recorded, and the sequence of interventions may not match what actually occurred.

OneCity's resuscitation log is designed to be used during the event itself, not after. A nurse or a dedicated scribe taps interventions (CPR initiated, intubation, defibrillation, adrenaline administered) as they happen, and the system timestamps each one automatically. Drug doses and routes are recorded against the timestamp. The result is a clinical record that holds up to scrutiny, which matters not just for quality review but for medico-legal documentation in cases where the outcome is contested. This same log feeds into the mortality review and clinical audit processes that NABH accreditation expects every hospital to maintain.

Handoff to IPD, OT, or ICU without re-registration

The disposition decision, admit, operate, transfer, or discharge, is where most paper-based ED workflows break down. A doctor decides to admit the patient. The patient (or their attendant) is sent to the IPD registration counter to start a new admission form. The clerk asks for the same demographics the ED already collected. The ward nurse asks for the same vitals the ED nurse already took. The patient's triage category, their initial assessment, the interventions already administered, and the treating doctor's notes exist only in the ED register, not in the IPD file, because the two systems are not connected. The patient has effectively re-entered the hospital.

In OneCity, the disposition triggers a handoff, not a re-registration. When the ED doctor selects "admit to ward" or "book for OT," the system generates the admission or the OT booking from the same patient record, carrying forward everything already captured: demographics, vitals, triage category, allergies flagged at triage, interventions administered, and the ED doctor's clinical impression. The receiving ward or OT sees the patient arrive digitally before they arrive physically, and the clinical record is continuous from the moment of ED arrival through admission, rather than restarting at the ward door. This continuity is what NABH's continuity-of-care standards are actually asking for, and it is also what makes a meaningful difference to patient safety when a critically ill patient is moving between departments.

For patients discharged from the ED without admission, the discharge record (diagnosis, treatment given, medications prescribed, follow-up instructions) is generated from the same workflow, and the visit becomes a closed record in the patient's longitudinal file rather than a loose entry in the ED register that nobody can find six months later.

Mass casualty and disaster preparedness

A routine ED workflow handles patients one at a time: triage, assess, treat, disposition. A mass casualty incident (MCI), whether a road accident with multiple victims, a building collapse, or a festival stampede, overwhelms that workflow because the number of patients arriving exceeds the ED's normal capacity within minutes. The triage system itself changes under MCI conditions: routine triage optimises for the best outcome per individual patient, while MCI triage allocates scarce resources to patients most likely to benefit, which is a fundamentally different decision calculus.

OneCity's ED module supports an MCI mode that can be activated by the on-duty senior when the trigger criteria are met. In MCI mode, registration is stripped to bare essentials (a temporary ID, triage category, and chief complaint), the dashboard reorganises to show patients by acuity across the entire available bed and trolley capacity rather than by department, and the system generates the batch documentation the hospital will need afterward: a timestamped log of all arrivals, triage categories assigned, and dispositions made, which feeds into the hospital's disaster preparedness review and meets the documentation expectations of both NABH and the Clinical Establishments Act for emergency preparedness.

ED-specific compliance requirements that most hospitals miss

Beyond the general NABH accreditation standards that apply to every department, NABH runs a standalone Emergency Department certification programme specifically for EDs. This certification evaluates the ED as a distinct clinical unit, not as part of the hospital's overall accreditation, and it checks for things the broader accreditation standards cover only in passing: documented triage protocols with evidence of consistent application, time-stamped arrival-to-assessment intervals, a disaster preparedness plan that has actually been drilled (not just written), MLC documentation compliance, and structured handoff protocols for patients transferring from the ED to other departments. A hospital pursuing this certification alongside or independently of its broader NABH hospital accreditation needs its ED documentation to stand on its own, which is a higher bar than most manual systems can sustain.

On the regulatory side, NMC's 2020 amendments made an Emergency Medicine department mandatory in all medical colleges from the 2022-23 academic year onward, with specific structural requirements: a casualty area with triage facilities, a registration counter with MLC registration capability, a defined bed allocation by triage category (4 red, 15 yellow, 5 green out of 24 total in the NMC specification), and a minimum 6-bed ICU adjacent to the emergency department. While these requirements apply directly to teaching hospitals, they set a benchmark that private hospitals increasingly reference when planning or upgrading their own EDs, because the same clinical logic applies regardless of whether the facility teaches residents.

The Clinical Establishments Act, applicable in states that have adopted it, requires every registered hospital to maintain emergency preparedness plans and to have the capacity to stabilise emergency patients before transfer if a case exceeds the facility's capability. This stabilise-before-transfer obligation carries real legal weight: a hospital that turns away an emergency patient without stabilisation can face action under both the Clinical Establishments Act and, depending on the state, under consumer protection law. The ED module's documentation trail, which captures the patient's presenting condition, the stabilisation interventions performed, and the clinical rationale for transfer or referral, is directly relevant to defending against such claims.

How the ED connects to the rest of the hospital record

A common failure pattern in hospitals that use one system for the ED and a different system (or a paper register) for the rest of the hospital is the clinical handoff gap. The ED record says one thing; the IPD admission note says something slightly different; the OT record starts fresh with no reference to what happened in the ED. When a patient's family or a legal proceeding asks what actually happened between arrival and the operating table, these discrepancies become a problem that no amount of after-the-fact reconciliation can fully fix.

OneCity's ED module is not a standalone product. It is part of the same hospital ERP that runs IPD and bed management, OT scheduling, the ICU module, the pharmacy, the lab, and billing. When a patient moves from the ED to a ward, to the OT, to the ICU, and eventually to discharge, the record is one continuous file, not a chain of handoff documents stapled together after the fact. That continuity is the difference between a clinical record that survives scrutiny and one that does not.

Overcrowding and boarding: the problem no ED module can solve alone, but can make visible

ED overcrowding happens when the department has more patients than it has capacity to move forward, most commonly because admitted patients are "boarding" in the ED waiting for an inpatient bed to become available. This is not a uniquely Indian problem, but it is a particularly acute one in busy tier-2 and tier-3 hospitals where bed turnover is slow and the ED has nowhere else to send patients who have already been decided as admissions. A boarding patient occupies an ED bed that a newly arriving emergency case needs, and the longer boarding continues, the more the entire department's throughput degrades.

No software module can conjure inpatient beds that do not exist. What OneCity's ED module can do is make the boarding problem visible in real time rather than invisible until it becomes a crisis: the dashboard flags any patient whose disposition decision was made more than a defined threshold ago (commonly two hours) but who has not yet physically left the department, cross-referenced against the bed management module's live occupancy view so the charge nurse can see exactly which ward has a bed opening up and push the transfer the moment it does, rather than discovering the delay only when a family member complains. For hospital administrators, the boarding-time metric itself becomes a genuine operational lever: a persistent boarding problem in a specific ward is usually a discharge-planning issue in that ward, not an ED problem, and having the data to show that distinction changes which department gets asked to fix it.

Shift handover: where clinical information most often gets lost

Emergency departments run around the clock, and every shift change is a moment where clinical continuity is at risk. A patient who arrived at 9pm and is still in the department at the 8am shift change has now been assessed, treated, and monitored by an entirely different set of nurses and doctors than the ones who saw them arrive, and every detail that lives only in the outgoing team's memory rather than in the record is a detail the incoming team starts without. This is a well-documented source of clinical error in emergency medicine generally, and it is worse in departments still relying on a verbal handover plus a paper Kardex that may or may not be fully updated.

OneCity's ED module generates a structured handover summary for every patient still in the department at shift change: triage category, time in department, interventions administered, pending results (labs, imaging), and the outstanding disposition decision if one has not yet been made. The incoming shift reviews this list at the start of their shift rather than relying entirely on a verbal report from whoever is leaving, and any patient flagged as high-acuity or with a pending critical result is surfaced at the top rather than buried in a list sorted by arrival time. This does not replace a verbal handover between clinicians, which remains clinically important, but it ensures the verbal handover is backed by a record both parties can actually see, rather than one person's memory of a busy night.

Pain management and analgesia tracking

Pain assessment and management is a specific area NABH and most clinical quality frameworks expect emergency departments to track deliberately, not as an afterthought to the primary complaint. A patient triaged as yellow-category for a fracture may not be in immediate danger of death, but leaving significant pain unaddressed for an extended period is itself a quality failure, and it is one that is straightforward to miss when the department's attention is focused on the red-category patients.

OneCity's ED module includes a pain score field (commonly a 0 to 10 numeric scale) captured at triage and reassessed at defined intervals, alongside a log of analgesia administered, the time given, and the route. This gives the treating team a visible signal when a patient's pain score has not improved despite treatment, and it gives administrators a data point for a metric that quality reviews increasingly ask for: time from triage to first analgesia for patients presenting with significant pain, and whether that pain was reassessed and managed through to discharge or admission, not just addressed once and left undocumented.

What administrators see beyond the clinical workflow

The ED is one of the most data-rich departments in a hospital, but in most tier-2 and tier-3 facilities, almost none of that data is captured in a usable form. Average door-to-doctor time, the split between red, yellow, and green arrivals, the proportion of ED visits that convert to admissions versus discharges, the busiest hours by day of week, the most common presenting complaints, and the MLC case volume are all operationally important numbers that a paper register simply does not produce without a manual tally that nobody has time to do.

OneCity captures all of this as a byproduct of the clinical workflow already running, not as a separate reporting exercise. The administrator's dashboard shows real-time ED occupancy (how many patients are in the department right now, by triage category), daily and weekly trends in arrival volume and acuity mix, average wait-to-triage and triage-to-doctor times, conversion rates from ED visit to admission, and left-without-being-seen rates, which are one of the strongest indicators of whether the ED is adequately staffed for its actual demand. For hospitals planning staffing levels, justifying an additional night-shift doctor, building a case for ED expansion, or reporting ED volumes to their governing body or state registration authority, this data already exists rather than needing to be assembled from a paper register after the fact.