The Post-Op Fever Call

Cut to the Chase: General Surgery Survival Series — Post 15

The call comes at 2 a.m. Bed 14, post-op day two from a colectomy, temp of 38.7. The nurse wants to know what you'd like to do.

You're 20 minutes into a four-hour nap, and your brain hands you two thoughts in the same breath: it's nothing, go back to sleep, and also, it's a leak and you're about to be the reason a chart gets reviewed.

Your thumb is already drifting toward the order set.

Here's the problem. You think the fever is the emergency. It isn't.

The fever is a question, and the answer is never in the thermometer. It's in the patient.

The number told you to go look — it did not tell you to fire off orders from a dark call room while the real information is two hundred feet down the hall in a bed.

Start with what that temperature means on day two. A comfortable patient on the second night after a big operation runs warm.

You opened them up, moved their organs around, and asked their immune system to start the largest cleanup job it's done all year. Inflammation makes heat. That isn't infection. That's healing being loud.

An early fever is usually the operation talking. A late fever is usually a complication talking. The post-op day tells you which conversation you're in before you've laid a hand on the patient.

That 38.7 on day two from a colectomy is, more often than not, physiologic — the body doing what bodies do after a laparotomy. Move it to post-op day five and the picture changes entirely.

Day five is when the anastomosis starts to declare itself. A fever that shows up late, after the patient had been trending the right way, is the one that can foretell a leak, a collection, a wound starting to turn.

While you're there, let go of the reflex you were handed in medical school. You were taught atelectasis causes the early fever; it doesn't. A systematic review of eight studies found no real association, and the teaching has been picked apart for years.

Look at the lungs anyway. Just don't close the case the moment you've blamed them.

Early fevers are usually physiologic. Late fevers foretell. A POD 5 fever after a colectomy is a sentence that ends in a complication until you've proven it doesn't.

Whatever the day, the fever is one data point, and in isolation it means almost nothing. You read it against the rest of the page: the exam, the fever curve, the vitals trend, the urine output, the drain outputs, where the labs sat yesterday versus tonight.

A 38.7 in someone sitting up asking for ice chips, heart rate steady, good urine output — that patient you can watch. The same number in someone whose heart rate is climbing through 120, whose pressure is sliding, who guards when you press on the belly — that's a different human being, and the fever was the smallest thing they were telling you.

One vital sign is a dot. The trend is a direction. Read the direction.

The fever rarely declares the emergency. The heart rate, the urine output, and the mental status do.

None of this gets sorted from the nurses' station, and the later in the course you are, the less forgivable it is to try. So go look. The single most useful thing you can do on a fever call is the thing the order set never prompts you for: shoes on the floor, hands on the abdomen.

The other 2 a.m. reflex is the shotgun: pan-culture everything, order the film, go back to bed, sort it on rounds. It feels like diligence.

It's mostly noise, and the cultures you draw on a stable patient with a benign fever will grow a contaminant that earns them three days of vancomycin they never needed. Culture what you're actually worried about.

A test you ordered to feel safe is a test that will eventually lie to you.

I still remember a leak that was almost missed by an intern. Day five, colectomy, a temp written off as the usual.

The patient looked a little off and on 'checkout' we were told it was pain. We laid eyes on them a few minutes later on rounds and had a CT ordered before leaving the room.

The patient was fine, because we didn't wait for the next temperature check. What stayed with me wasn't the fever. It was that the intern looked straight at the answer and talked themselves out of it.

You're a doctor now — you're supposed to walk in with a thought, not hand someone a thermometer reading and wait for instructions. Information is what the nurse already gave you. Your job is to add a plan to it.

Not "the patient has a fever, what do you want to do." Closer to this: "Post-op day two from a colectomy, fever to 38.7, heart rate 96, pressure stable, lungs clear, belly soft, incision clean, making urine. I'm thinking early post-op fever over a source I can't find, so I'm holding cultures and rechecking in the morning unless something changes."

That's a surgical call. It says you're thinking in patterns instead of panicking at the thermometer like it insulted your family.

And when the patient looks worse than the chart says they should — tachycardic, hypotensive, altered, not making urine — that is not a fever you manage from the call room. That's a phone call, made early, made out loud, made without apology. Calling about a sick patient is never the thing that gets you in trouble.

The dangerous fever isn't the highest number on the board. It's the one in the patient who looks worse than their chart says they should.

The call will always come the same way: a bed number and a temperature. But that was never the question.

The question is the patient at the end of the hall, and the only way to answer it is to stand at the foot of their bed and read the whole picture, not the one number that woke you.

---

What to Read Next: Post 16 — Before the Patient Goes to the OR. The fever call is reactive medicine, made in the dark with half the information. The next one is the other side of the work: the quiet preparation before a case that decides how smoothly everything after it goes.