Animal HospitalWiki
⚠️ Community-reported

Anomaly

Fainting Patient (Detection)

Updated:

Anomaly: a patient collapses on their own in the waiting area. Detection-focused entry; for the emergency-carry mechanic triggered by fire/gunshot, see /wiki/events/patient-fainted.

Overview

Fainting Patient (Detection) is the AH-specific anomaly tracking spontaneous patient collapses in the waiting area. This is distinct from the emergency-triggered Patient Fainted event covered at /wiki/events/patient-fainted — that event fires in response to fire damage or gunshot in the waiting area, while this anomaly fires with no preceding cue. Same surface symptom (patient on the floor); different trigger; different counter.

The Fandom main anomalies page doesn't catalogue this — Fandom focuses on intake-window detection and post-treatment hostility, while AH tracks the in-waiting-room anomaly behaviour as a distinct category alongside Mad Patient. The confidence flag in the AH JSON is 'uncertain' — the cues and counter are documented but cross-source verification is limited.

The risk profile is low compared to other anomalies because the collapse itself isn't immediately destructive — it's a window for the player to respond before the patient escalates into a Skinwalker or worse. The catch is that leaving the patient unattended too long lets the anomaly manifest from the body.

How to Spot It

Audio first: a 'thud' sound followed by silence is the earliest cue. Distinct from ambient hospital noise — the thud is specifically associated with patient collapse.

Visual confirmation: patient animation freezes in a prone position on the waiting room floor. Watch the waiting area periodically; the prone patient is visible against the standing-or-seated baseline.

Discriminator from the Patient Fainted event: this anomaly fires with no preceding fire or gunshot. If a patient collapses immediately after a fire emergency in the waiting area, that's the event, not the anomaly. The trigger absence is the key tell.

Confidence note: AH JSON marks this entry as 'uncertain' — treat the mechanics as 'likely correct' rather than 'guaranteed.' Cross-source verification limited.

Video Guide

Detection demo video coming soon.

Mechanics & Behavior

  • Detection: Audio (thud + silence), Visual (prone animation)
  • Trigger: spontaneous (no preceding fire / gunshot)
  • Counter: Smelling Salts or water — verify Skinwalker risk first
  • Risk: leaving unattended allows anomaly manifestation from the body
  • AH-specific entry not in Fandom's main 14

Easy vs Hard Calls

Pros

  • ✓ Audible thud from the waiting area
  • ✓ Patient in prone animation on the waiting room floor
  • ✓ No preceding fire or gunshot cue (distinguishes from emergency event)

Cons

  • ✗ Easy to conflate with the Patient Fainted event — check for preceding trigger to discriminate
  • ✗ Confidence marked 'uncertain' in AH JSON — cross-source verification limited
  • ✗ Low risk profile means players may deprioritise response and let manifestation trigger

At a Glance

At a Glance

Detection method
Visual
Sanity damage
—
First appears
Shift 1
Risk level
low

How to Handle This Anomaly

When you hear the thud audio, scan the waiting area for the prone patient. Confirm visually, then check for the trigger context — if a fire or gunshot just happened, you're dealing with the Patient Fainted event (different workflow, see /wiki/events/patient-fainted). If there's no preceding trigger, this is the Fainting Patient anomaly.

Before approaching, verify the patient isn't a Skinwalker — the AH JSON specifically calls out the Skinwalker verification step. A Skinwalker faking a faint can trigger combat the moment you get close.

If clear: administer Smelling Salts or provide water to revive. The counter restores the patient to normal waiting status.

Do not leave the patient unattended for an extended period. The AH JSON warns that prolonged inaction allows an anomaly to manifest from the body — the specific mechanic isn't fully documented but the risk is real.

If the patient transforms into a Skinwalker (either because it was a Skinwalker-faking-faint or because the manifestation triggered from inaction), see /wiki/enemies/skinwalker for the combat counter.

Patch History

No documented balance changes to the Fainting Patient anomaly mechanic. AH JSON confidence flag is 'uncertain' — the entry exists but cross-source verification is limited.

Frequently Asked Questions

How is Fainting Patient different from the Patient Fainted event?
Fainting Patient (anomaly) fires spontaneously with no preceding cue. The Patient Fainted event fires in response to fire damage or gunshot in the waiting area. Same surface symptom (patient on the floor), different trigger and different counter.
What's the counter for Fainting Patient?
Smelling Salts or water. Verify the patient isn't a Skinwalker before approaching — the AH JSON specifically calls out the Skinwalker risk.
What happens if I leave a fainting patient unattended?
AH JSON warns that prolonged inaction allows 'an anomaly manifesting from the body.' The specific mechanic isn't fully documented but the risk is real. Respond reasonably promptly.
How do I detect Fainting Patient?
Audio: a thud sound followed by silence. Visual: patient in prone animation on the waiting room floor. The trigger context (no preceding fire/gunshot) discriminates from the Patient Fainted event.
Why isn't Fainting Patient in Fandom?
AH-specific entry. Fandom's main anomalies page focuses on intake-window detection. Fainting Patient operates in the waiting room and is tracked in AH's behavioural-anomaly category.
What's the risk level for Fainting Patient?
Low. The collapse itself isn't immediately destructive — it's a response window for the player. The risk escalates only if you ignore the patient long enough for manifestation to trigger.
Why is the confidence flag 'uncertain'?
Cross-source verification limited. The cues and counter are documented in AH content but the specific mechanics (manifestation timing, exact Skinwalker risk) aren't fully cross-referenced from independent sources.
When does Fainting Patient first appear?
Shift 1 per AH documentation. Part of the default rotation from the opening shift.

A legacy entry, kept on purpose

This entry documents the spontaneous-collapse scenario — a patient who drops in the waiting area on their own, with smelling salts as the revive path. It's distinct from the Patient Fainted event, which is the 60-second carry-to-bed emergency triggered by fire contact, gunshot, or check-in stress.

Two scenarios, same visual collapse, different counters. The carry-emergency is the canonical mechanic documented across community guides; the spontaneous-collapse-revive variant has weaker source coverage and is kept here at confidence: uncertain for that reason.

When to apply each counter

If a patient drops before admit (in the waiting area, no prior fire / gunshot / stress event) → smelling salts, optionally verify it's not a Skinwalker setup. This entry.

If a patient drops during or after admit, triggered by fire / gunshot / failed check-in → that's the event. Carry them to a bed within 60 seconds. See the Patient Fainted event entry.

A note on the general anomaly rule

Per the game's uniform admit-anomaly rule, any anomalous patient processed at intake becomes a Skinwalker on the floor. That rule applies if this collapse is itself a disguised admit-time anomaly. If it's the post-admit emergency variant, the Skinwalker rule doesn't apply — the patient is real, just incapacitated.

Sources: existing in-game documentation (legacy entry), Pro Game Guides emergencies guide for the event-variant counter.