What Happens When an On-Call Surgeon Doesn't Answer a Page

A page goes out to the on-call general surgeon in the middle of the night. No answer at four minutes. No answer at eight. Somewhere in that gap, someone has to decide who gets called next, and how long the emergency department is supposed to wait before making that call. In a well-run hospital that decision was made weeks or months earlier, on paper, by people who never expected to be awake for it. In a lot of hospitals it wasn’t, and the decision gets made on the fly by whoever’s standing at the desk when the clock starts feeling uncomfortable.

The direct answer: yes, hospitals maintain backup-call coverage for exactly this situation, and federal law requires any hospital with an emergency department and a Medicare provider agreement to keep a roster of specialists reachable for cases the emergency staff can’t handle alone. What varies enormously, hospital to hospital and specialty to specialty, is whether that backup arrangement is a real, engineered fallback or just a second phone number written under the first one. A dispatch list that dials down a roster until someone answers shows up in plenty of other jobs too, but a hospital’s version carries a different weight: the question isn’t just who answers next, it’s whether the system can prove, after the fact, that it did what it was supposed to do.

What “Backup Call” Means in Practice

Surgical and anesthesia call schedules typically run at least two names deep. The person listed first is “first call,” “primary call,” or just “on-call” for the night, the one whose pager gets paged first for anything in their service. Behind them sits a “backup call” or “second call” physician, whose entire job most nights is to not be needed. Larger academic centers often run three-deep coverage for busy services like trauma or obstetrics; a rural hospital with two general surgeons on staff might have a backup list with exactly one other name on it, and no third option if that name doesn’t pick up either.

There’s a second distinction, separate from first-call versus backup, between “in-house call” and “home call.” In-house call means the physician is physically inside the hospital for the shift, reachable down a hallway. Home call means they’re paged at home and have to travel in, which is where response-time expectations start mattering in a concrete way — the same basic bargain, reachable and present at an hour you don’t control, that shows up in far lower-stakes work too, like a wedding photographer whose contract turns on actually waking up for a specific sunrise call time. Anesthesiology tends to lean in-house more than general surgery does, because an obstetric hemorrhage or a crashing airway in the operating room can’t wait for someone to find parking; a service with a lower rate of true middle-of-the-night emergencies can often run home call safely, on the assumption that a modest travel window is an acceptable trade against not paying a physician to sit in a hospital room all night waiting for nothing to happen. That trade-off, made once at the departmental level, quietly sets the outer bound on how fast a backup can possibly arrive no matter how the paging itself is handled.

Several published hospital call policies put numbers on that bound. A 2016 anesthesia department call policy from MedStar Health and a trauma backup-call plan published by Deaconess Health System both land on the same figure independently: the operating-room team, including a backup anesthesiologist or surgeon called in from home, is expected to be physically present within thirty minutes of being contacted. Other hospital medical staff rules split the number in two, requiring a phone callback within fifteen minutes and, only if the case truly needs it, an in-person arrival within sixty. Neither figure is a national rule. Both are examples of the same convention a lot of individual hospitals landed on separately, in roughly the same range, without coordinating with each other.

The American College of Surgeons pushes this further for its highest-acuity trauma centers. To be verified as a Level I or Level II trauma center, a hospital has to publish a call schedule that names a backup trauma surgeon alongside the primary one. What the ACS standard notably leaves undefined is exactly when that backup gets called in: the decision to pull a second surgeon off the bench, rather than wait on the first, is left to each trauma program to write for itself, and some programs have never put that decision rule on paper at all.

The Federal Floor Underneath All of This

The reason any of this is written down at all, instead of left to professional courtesy, traces to a fairly blunt piece of federal law. The Emergency Medical Treatment and Labor Act requires any hospital with a dedicated emergency department that accepts Medicare to keep an on-call list of physicians who can stabilize patients the ED staff can’t manage alone, and, in the detail that tends to surprise people outside medicine, that on-call physician generally has to show up in person when the treating ED physician asks for it, rather than consulting by phone instead. A remote consult is allowed for judgment calls about whether a case needs the specialist at all; it isn’t a substitute for appearing once the treating physician has decided it does.

EMTALA doesn’t attach a number to how long a physician can take to respond. Enforcement guidance treats something in the neighborhood of a half hour as the rough edge of reasonable, but the statute itself just says “a reasonable period of time,” which leaves room for argument in any individual case and has produced exactly that argument in real enforcement actions over the decades. What isn’t ambiguous is the consequence on either end. A hospital with inadequate on-call coverage, or a physician who refuses or fails to respond within a reasonable window, can each be investigated separately by the HHS Office of Inspector General, and each can face a civil monetary penalty that has grown, through routine annual inflation adjustments, to well over $100,000 per violation, on top of whatever ordinary malpractice exposure follows if a patient was harmed by the delay. The hospital and the individual physician are investigated as two separate questions, which matters here for a reason that has nothing to do with dividing blame: it means regulators can examine the backup-call arrangement itself after the fact, beyond just the single decision made on any given night. The same in-house-versus-home split that sets a department’s travel window also determines a much more mundane question that follows the physician home: whether that waiting-at-home time counts as paid work at all under federal wage-and-hour rules built around a very different kind of overnight waiting.

Four Questions a Backup-Call Chain Has to Answer

Strip away the hospital setting and a backup-call arrangement is a fairly plain piece of infrastructure: a way of routing an urgent request to a person, and re-routing it if the first attempt doesn’t land. Looking across enough of these policies, the ones that hold up under real pressure share four properties in common, and the ones that don’t are missing at least one of them, almost always silently, until the night it’s needed.

The response window is a number, not a feeling

“Give her a bit to call back” is not a policy; it’s a description of whatever the person at the desk decides to do that particular night, which will vary with how busy the ED is and how much authority that person feels they have to push past a senior physician. A written window, fifteen minutes to return a page, thirty to be reachable by phone, removes that judgment call from whoever happens to be on shift and gives everyone a shared number to point to instead of a shared guess.

The backup already agreed to be the backup

This sounds obvious and is routinely skipped. A schedule that lists a name under “backup call” without that person having confirmed in advance that they’re reachable and expecting the call is a schedule with a hole in it nobody notices until the hole matters. Physicians who’ve served as a backup describe knowing, walking into the week, which nights they’re it, not finding out for the first time when the phone rings at 2 a.m.

Somebody confirms the handoff landed

Sending a second page is not the same as knowing the backup received it, is awake, and is now on the way in. A 2025 quality-improvement project out of Massachusetts General Hospital’s surgery department, published in BMJ Open Quality by Michael Kochis and colleagues, redesigned exactly this gap on two general surgery units: every page got classified as STAT, Urgent, Please Call, or FYI, each carrying its own expected response window and its own defined next step if that window closed without a reply. The point wasn’t only faster paging. It was replacing a quiet assumption, someone will notice if this doesn’t get answered, with a step that confirms it did, and moves the page automatically to a named alternate contact when it doesn’t.

Someone owns the gap, both while it’s open and afterward

Between the moment a page goes unanswered and the moment a backup arrives, care is either delayed, handled by whoever’s already in the building, or the patient is transferred to a different facility altogether. That’s not a hypothetical; it’s the ordinary outcome of an unanswered page most nights, usually resolved with nothing worse than a slower few minutes than anyone would prefer. Afterward, if the delay mattered, the question of who’s accountable for it stops being abstract. It becomes the same question EMTALA enforcement and ordinary malpractice claims both end up asking, aimed first at whether the on-call arrangement itself was adequate, only second at what any one person did on one particular night. Most hospitals also run an internal version of that same question through a morbidity and mortality conference, where a delayed case gets reconstructed in front of the department: who was paged, when, and what happened in between. In most states those discussions carry a peer-review privilege that keeps the transcript out of a plaintiff’s hands even if the underlying facts still come out through the medical record, which is one reason the four questions above tend to get asked seriously only after a bad outcome forces the conversation, rather than as routine maintenance on a schedule nobody’s tested yet.

A phone list, sitting on a shared drive somewhere, can satisfy none of these four and still look identical to a real backup-call chain right up until the first time it’s tested for real. That resemblance is why the gap tends to surface during a bad outcome rather than during an ordinary staff meeting, when nobody has any reason to ask the four questions in the first place.

Where the Chain Actually Fails

The places this breaks down aren’t usually the big academic trauma centers with three-deep coverage and a dedicated communications desk. They’re the specialties and the smaller hospitals where there’s no real next name to call. A hospital with a single covering neurosurgeon doesn’t have a backup-call problem it can fix with a better policy; it has a coverage problem, because the third question above, who’s next, has no real answer once the first name doesn’t pick up. In that situation the real fallback runs through a transfer to a different facility that does have someone reachable, which is slower, harder on the patient, and precisely the kind of thin coverage EMTALA’s rules exist to catch when a hospital’s published call schedule turns out to promise more than its staffing can deliver.

The other common failure sits inside otherwise well-staffed departments that simply never wrote the escalation step down. The backup exists. The response window exists too, informally, inside everyone’s head. What’s missing is the confirmation piece: nobody’s job is specifically to notice, at minute thirty-one, that the chain has gone quiet and the next name needs a call. That gap can survive for years precisely because most nights nothing tests it, the way a fire exit nobody has ever used can go unnoticed as rusted shut. The pager gets answered. The surgeon shows up. Whatever loose arrangement was never actually built gets credit for working anyway, right up until the one night the first name doesn’t answer and there’s no defined next step, just people improvising in real time with a sick patient in front of them and a clock that doesn’t pause for the improvising.

This isn’t an argument that on-call physicians are unreliable. Most pages, most nights, get answered by exhausted people doing precisely what they signed up to do, often after a stretch of the same kind of thin, interrupted sleep that nurses working overnight shifts have spent years building informal workarounds for without much of a written policy behind them either. The question this piece means to answer is narrower: on the small number of nights a page doesn’t land, was the hospital’s response to that moment built in advance, or invented on the spot. Two hospitals can share an identical org chart and a nearly identical call schedule and still be entirely different institutions on that one measure, and the difference is usually invisible from outside until the night it counts.

I don’t have a clean number for what share of U.S. hospitals have all four pieces written down, response window, pre-confirmed backup, closed-loop confirmation, and an owner for the gap, rather than assumed. Nobody appears to have published that survey, and it would be a useful one for someone to run. What the EMTALA enforcement record and the handful of public hospital call policies suggest, more modestly, is that the space between “there’s a backup-call schedule” and “there’s an escalation chain that’s actually been tested” is wide, uneven across specialties, and, per the broader pattern of institutions where a named person other than you carries the consequences of a missed moment, mostly invisible until the one bad night makes it visible for everyone at once.