When You Get a Code Stroke Page Overnight: What to Do First

A code stroke page at 2:17 a.m. is not the time to be clever. It is the time to be fast, organized, and boringly reliable.

Your job in the first few minutes is simple: figure out whether this is a true acute stroke pathway patient, whether they are potentially time-sensitive for thrombolysis or thrombectomy, and whether anything immediately reversible is being missed. That is it. Not a complete neurologic masterpiece. Not a twenty-minute chart dive. Not a philosophical debate about stroke mimics.

I have seen residents lose ten precious minutes because they started with the wrong question. They asked about the full headache history before they asked last known well. They opened old MRI reports before checking glucose. They ordered a CT before making sure transport was even coming. Dumb delays. Avoidable delays.

Here is how to fix it.

Start With the 60-Second Triage

When the page comes, your first task is to clarify what you are actually walking into.

Not every “stroke alert” page is a stroke alert. Sometimes it is a nurse worried about slurred speech in a septic patient who has been encephalopathic for twelve hours. Sometimes it is a chronic facial droop that the family just noticed. Sometimes it is a true large-vessel occlusion that needs movement now. You need to sort that out immediately.

In the first 60 seconds, get answers to three questions:

1. What are the symptoms right now?

   • Weakness
   • Aphasia
   • Facial droop
   • Vision loss
   • Neglect
   • Altered mental status
   • Seizure activity

2. When was the patient last known well?

   • Exact clock time if possible
   • “Found down at 1 a.m.” is not last known well
   • “Family last spoke to him normal at 10:15 p.m.” is useful
   • If wake-up symptoms, document that clearly

3. Is this an active deficit or a resolved event?

   • Ongoing
   • Fluctuating
   • Improving
   • Already resolved

Then run the rapid mental checklist that keeps you from missing the obvious:

• Airway: Protecting it or not?
• Breathing: Any hypoxia or respiratory distress?
• Circulation: Severe hypotension? Arrhythmia? No pulse problem?
• Blood glucose: Checked yet? If not, get it now
• Vitals: Blood pressure, heart rate, oxygen saturation, temperature
• Current status: Deficits present now, waxing and waning, or gone

If the page comes from the floor or ED, make the first calls early. Do not wait until after your exam if the story already sounds real.

Your first calls:

• Bedside nurse or charge nurse: confirm symptoms, timing, glucose, vitals
• Stroke attending / neurology backup / senior: based on your hospital protocol
• CT: let them know a code stroke may be coming
• Pharmacy: if thrombolysis is realistically on the table

This is not overcalling. This is what functional residents do. You can always de-escalate later. What hurts patients is under-activating because you wanted to “just take a quick look first” and then discovered an hour later that the patient was actually in window.

A practical script helps:

• “I am on my way.”
• “What exact time was the patient last known well?”
• “What are the deficits right now?”
• “Get point-of-care glucose now if it is not already done.”
• “Please have transport ready and the chart open when I arrive.”

That alone cuts out a surprising amount of overnight chaos.

Do the First Five Actions in the Right Order

This is where people either run a clean stroke response or create their own delay.

Do these five things in order.

1) Go to the bedside immediately

Do not manage a possible stroke from the hallway phone. Go see the patient.

You need one look at:

• Level of consciousness
• Whether they can protect their airway
• Whether the deficits are obvious and disabling
• Whether this looks like a mimic, seizure, toxic-metabolic problem, or true focal event

A patient with dense hemiplegia and gaze deviation looks different from a sleepy patient with global weakness and a glucose of 38. That distinction matters fast.

2) Confirm last known well and symptom onset

Ask this before you get seduced by details.

Get the best available timeline from:

• Patient
• Nurse
• Family
• EMS
• Chart timestamps
• Staff who actually saw the patient normal

Be precise:

• Last known well = last time definitely at neurologic baseline
• Symptom discovery time = when deficits were first noticed
• These are not the same thing

If symptoms were present on waking, say so clearly. If the patient was already abnormal earlier in the shift, document that. If nobody knows, do not invent certainty. State the uncertainty plainly and move on.

3) Check glucose and vitals immediately

If glucose has not been checked, ask for point-of-care glucose now. Not “with next labs.” Now.

This is one of the highest-yield fixes in all of overnight medicine. Hypoglycemia is a classic stroke mimic, and residents still miss it because they assume somebody else already checked. Do not assume.

Also verify:

• Blood pressure
• Heart rate
• Oxygen saturation
• Temperature

You need these because they change both diagnosis and treatment:

• Severe hypertension may affect thrombolysis eligibility
• Hypoxia may explain or worsen deficits
• Fever may push you toward infection
• Hypotension should make you question the whole picture

4) Perform a focused neurologic exam

This is not the moment for a leisurely comprehensive consult exam. You need a quick, decision-driving exam.

Start with FAST/BE-FAST basics:

• Balance
• Eyes/vision
• Face
• Arm
• Speech
• Time

Then hit the practical priorities:

• Level of consciousness
• Ability to follow commands
• Gaze deviation
• Visual field cut
• Facial droop
• Dysarthria or aphasia
• Arm drift
• Leg weakness
• Neglect or inattention
• Ataxia if relevant

If your center uses NIHSS routinely, do it. If not, at least generate a focused deficit summary that clearly states what is disabling and what is not.

A good one-line exam sounds like this:

• “Alert, left gaze preference, expressive aphasia, right facial droop, no antigravity movement in right arm, drift in right leg, neglect present.”

That is useful.
“Neuro exam grossly abnormal.” Useless.

5) Activate the stroke pathway

Once you have timing, deficits, and basic stability, activate the pathway.

That usually means:

• Stroke alert order set
• Non-contrast head CT
• CTA head/neck if indicated by protocol
• Neurology/stroke attending notification
• Pharmacy alert if thrombolysis possible
• Transport mobilized before the order sits there untouched

This is where avoidable delays multiply. Fix them aggressively:

Common delay fixes

• Tell the nurse to get point-of-care glucose immediately
• Have someone pull the chart and MAR while you examine the patient
• Ask specifically about anticoagulants
• Make sure transport is physically ready
• Call CT directly if your hospital workflow requires it
• If contrast is likely needed, confirm there is no preventable bottleneck around IV access

Here is the clean overnight workflow:

If you remember nothing else, remember this sequence:

Bedside. Time. Glucose. Exam. Imaging. Escalate.

That is the backbone.

Avoid the Common Nighttime Mistakes

Night stroke pages go wrong in very predictable ways. The mistakes are not mysterious. They are usually process failures.

Mistake 1: Anchoring on stroke too early

Not every focal symptom is stroke.

Common mimics:

• Hypoglycemia
• Post-ictal Todd paralysis
• Migraine with aura
• Toxic-metabolic encephalopathy
• Functional neurologic symptoms
• Baseline old deficits being rediscovered at 3 a.m.

You should treat stroke seriously without becoming blind to alternatives. That balance is the job.

Mistake 2: Forgetting anticoagulants

Always verify:

• Apixaban
• Rivaroxaban
• Dabigatran
• Warfarin
• Heparin products
• Recent procedures or bleeding history

Do not rely on “I do not think so.” Check the MAR, the med list, family report, and recent notes.

Mistake 3: Missing pregnancy or hypoglycemia

In younger patients, pregnancy status matters. So does glucose in every patient, every time. I am repeating glucose because people still skip it, and that is indefensible.

Mistake 4: Delaying imaging to gather the perfect history

You do not need the entire social history before the scanner moves.

Get what changes immediate management:

• Last known well
• Current deficits
• Anticoagulants
• Major contraindications
• Stability for transport

The rest can follow.

When not to improvise

If the patient is:

• Hemodynamically unstable
• Not protecting the airway
• Actively seizing
• Profoundly encephalopathic without focal findings
• Clearly outside the standard treatment window
• Trauma-associated or obviously another emergency first

Then escalate appropriately and stop pretending this is a routine code stroke. Stabilize first, involve the right teams, and adapt the pathway. Forced protocol is bad medicine.

Practical overnight “do not miss” checklist

Before thrombolysis conversations move forward, make sure somebody has addressed:

• Exact last known well
• Anticoagulant use
• Blood pressure
• Glucose
• Recent bleeding or surgery
• Pregnancy status when relevant
• Seizure at onset
• Migraine history if symptoms fit
• Toxic-metabolic causes
• Baseline neurologic deficits

This list prevents dumb errors. Use it.

What to Document, Communicate, and Hand Off

A messy stroke note creates real clinical harm. It delays decisions, confuses consultants, and wrecks the morning handoff. Good documentation is not clerical busywork. It is part of treatment.

Minimum documentation

Your note or event documentation should include:

• Time page received
• Time you arrived
• Last known well
• Time symptoms discovered
• Who provided the history
• Symptom timeline
• Focused neurologic findings or NIHSS
• Blood glucose
• Vital signs
• Anticoagulant status
• Imaging ordered
• Who was notified and when
• Disposition of the pathway
  • thrombolysis considered
  • thrombectomy evaluation considered
  • alternate diagnosis suspected
  • neurology recommendations pending

Do not bury the key facts in a wall of text. Put the timing and deficits where everyone can find them in seconds.

Use a concise call script

When calling neurology, radiology, or your senior, use a one-line problem representation.

A clean script:

• “This is a code stroke on a 68-year-old man with last known well 22:10, found at 01:05 with aphasia, right facial droop, and right arm weakness, glucose 112, BP 184/96, on apixaban per MAR, non-contrast CT being obtained now. My question is whether you want full stroke activation with CTA and thrombectomy evaluation despite anticoagulant use.”

That is good communication. Specific. Action-oriented. Easy to respond to.

For radiology or CT:

• “Code stroke, last known well 22:10, active focal deficits, transport en route, need non-contrast head CT now and CTA per protocol.”

For your senior:

• “Code stroke active, bedside now, likely true focal event, within possible treatment window, glucose normal, imaging pending, neurology notified.”

Hand off like the next person matters

If this case runs into shift change, the handoff must be crisp.

Include three buckets:

1. What was done

• Seen at bedside
• Last known well confirmed
• Glucose checked
• Neuro exam documented
• CT/CTA ordered or completed
• Neurology/pharmacy/senior notified

2. What is pending

• CT read
• CTA result
• Neurology callback
• Blood pressure control
• Decision on thrombolysis or thrombectomy
• Family collateral history

3. The exact decision point This is the most important part. Say the sentence clearly:

• “If CTA shows LVO, activate thrombectomy transfer pathway.”
• “If no contraindication is confirmed and BP is controlled, patient may still be thrombolysis candidate.”
• “If imaging is negative and deficits resolve, evaluate TIA versus mimic.”

That last line tells the incoming team where the hinge in the case actually is.

Here is the communication loop you want:

If your handoff ends with “they are getting worked up,” you have not handed off a stroke case. You have dumped a problem.

Build a Reliable Overnight Stroke Page Protocol

The residents who handle overnight code strokes well are not geniuses. They are systematic.

Build yourself a repeatable protocol.

Keep a one-page pocket script

Mine would include:

• First three questions
• Stroke pager tree
• Where to call CT
• Pharmacy number
• Thrombolysis contraindication reminders
• Your hospital imaging sequence
• Transfer pathway for thrombectomy if relevant

You do not need to memorize everything if you have built a tool you will actually use.

Memorize the first three questions

Every single time:

1. What are the deficits right now?
2. What exact time was the patient last known well?
3. Has glucose been checked?

Those three questions rescue bad pages constantly.

Build shift-proof habits

Before your shift starts, know:

• Where the stroke cart is
• Which CT scanner your code strokes go to
• Whether your hospital wants non-contrast CT first or bundled CT/CTA
• How to reach the stroke attending, neurology backup, and pharmacy
• What the transfer process is if thrombectomy is not done in-house

This is boring prep. It is also what makes you look competent at 3 a.m.

Do a post-call follow-up

After a code stroke, review:

• What was the actual diagnosis?
• Was the timeline documented correctly?
• Where did delay happen?
• Did you miss a contraindication?
• Did your communication work?

That is how you get sharper. Not by just surviving the night and forgetting the case.

The goal is not to feel less stressed. The goal is to be reliable while stressed.

Key takeaways

• Your first job is not to diagnose everything; it is to verify timing, stabilize the patient, and activate the right stroke pathway fast.
• A simple, repeatable sequence prevents missed steps: bedside, glucose, focused neuro exam, imaging, and clear escalation.
• Good documentation and concise communication are part of treatment because they prevent delays and protect the handoff.

The fix is straightforward. Build your own overnight code stroke algorithm. Put it on one page. Review it before your next call shift. Then when the pager goes off in the middle of the night, you will not need inspiration. You will need a protocol.