Standard 11 — Critical Care
Criteria in this standard
11.2 — Nurse-to-Patient Ratio Matches Acuity
11.3 — Rapid Response and Deterioration Recognition System
11.4 — Sedation and Delirium Management Protocol
11.5 — Family Communication and Presence Policy
11.6 — End-of-Life and Withdrawal of Care Protocol
Continuous Physiological Monitoring Appropriate to Acuity
Non-Negotiable
In plain terms: Every critical care patient is genuinely watched continuously, with alarm settings actually tailored to them — and alarms get a real response, not silenced because staff have grown used to tuning them out.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
Alarm fatigue — where the sheer volume of alarms, many clinically insignificant, leads staff to delay response or mentally tune them out — is a well-documented and specific patient safety risk in critical care settings. Generic factory-default alarm parameters, left unadjusted to the individual patient’s actual clinical baseline, can be essentially meaningless for that specific patient, triggering either excessive false alarms or missing genuinely significant changes.
What good looks like
- Alarm parameters are individually set for each patient’s actual condition.
- A documented, genuine response time standard exists, verified against practice.
- Equipment is checked and calibrated on a fixed schedule with a failure process.
Common failure modes
- Alarm parameters are left on generic factory defaults.
- Alarms are frequently silenced or ignored due to alarm fatigue.
- No documented process exists for monitoring equipment failure.
Worked example
If you are starting from zero — do this first
- Check whether alarm parameters are currently individualized or left on defaults.
- Build a required individualization step at shift start.
- Build a documented response time standard and track actual response.
Self-assessment questions
Evidence: Alarm parameter record
Evidence: Response time log
Evidence: Calibration and failure-process documentation
Common reasons for a PARTIAL answer
- Parameters are individualized at admission but not revisited as condition changes.
- A response time standard exists but isn’t actually monitored.
Implementation plan
| When | What |
|---|---|
| Week 1 | Audit current alarm parameter practice across the unit. |
| Week 2 | Build a required individualization step at shift start. |
| Week 3 | Build a response time standard and tracking method. |
| Ongoing | Review alarm response logs periodically for fatigue patterns. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| OBSERVE | Unit observation | Observes alarm parameter individualization and actual staff response to alarms during a unit visit. |
Evidence base
Nurse-to-Patient Ratio Matches Acuity
Non-Negotiable
In plain terms: The defined nurse-to-patient ratio genuinely holds at all hours, including nights and weekends — with a real, used escalation path when it can’t be met, not a ratio that exists on paper but erodes under pressure.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
Off-hours staffing — nights, weekends — is specifically where nurse-to-patient ratios most commonly erode under pressure, precisely because oversight tends to be lighter during these periods than during well-staffed daytime weekday shifts. A ratio with no genuine escalation process for when staffing falls below the standard functions, in practice, as merely an aspiration rather than a real operational requirement — the escalation process is what distinguishes the two.
What good looks like
- The ratio is maintained and verified across all shifts, not only daytime weekdays.
- A documented escalation process exists for below-ratio staffing.
- A documented instance exists of this escalation process actually being used.
Common failure modes
- The ratio holds on weekdays but quietly erodes on nights and weekends.
- No real escalation process exists for below-ratio situations.
- No example exists of the escalation process ever actually being used.
Worked example
If you are starting from zero — do this first
- Check actual staffing records across all shifts, not just daytime weekdays.
- Build a required escalation and documentation process for below-ratio staffing.
- Apply the process identically regardless of time of day.
Self-assessment questions
Evidence: Staffing record across shift types
Evidence: Escalation procedure
Evidence: Escalation event record
Common reasons for a PARTIAL answer
- The ratio holds on weekdays but staffing records for nights/weekends aren’t closely tracked.
- An escalation process exists but has never actually been used or tested.
Implementation plan
| When | What |
|---|---|
| Week 1 | Audit staffing records across all shift types for the past quarter. |
| Week 2 | Build a formal escalation and documentation process. |
| Week 3 | Brief all shifts, with particular attention to off-hours staff. |
| Ongoing | Track escalation events specifically for off-hours patterns. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Staffing record review | Reviews staffing records specifically for off-hours and weekend consistency against the defined ratio. |
Evidence base
Rapid Response and Deterioration Recognition System
Non-Negotiable
In plain terms: A real, structured tool catches early deterioration, and any staff member can trigger rapid response directly — not after working through several layers of approval first.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
A structured, scored early-warning system catches subtle but genuine deterioration considerably more reliably than relying on informal clinical impression, particularly for trends that develop gradually rather than presenting as a sudden, obvious event. A rapid response mechanism that requires working through multiple layers of approval before activation directly undermines its own purpose — the entire value of “rapid” depends on the person who notices deterioration being able to act immediately, not after a delay for permission.
What good looks like
- A structured, scored early-warning system is actually used, not informal impression.
- Any staff member can activate rapid response directly, without multi-layer approval.
- A documented, verified response time exists from activation to team arrival.
Common failure modes
- Deterioration detection relies on informal clinical impression alone.
- Activation requires working through a chain of approval before help arrives.
- Response time is assumed rather than genuinely measured.
Worked example
If you are starting from zero — do this first
- Adopt a validated, scored early-warning tool if not already in use.
- Explicitly grant and publicize direct activation authority to all staff.
- Measure and document actual rapid response team arrival time.
Self-assessment questions
Evidence: Early-warning scoring documentation
Evidence: Activation policy
Evidence: Response time log
Common reasons for a PARTIAL answer
- A policy grants direct activation but an informal culture still expects prior consultation.
- Response time is assumed rather than genuinely measured and tracked.
Implementation plan
| When | What |
|---|---|
| Week 1 | Adopt or confirm a validated early-warning scoring tool. |
| Week 2 | Explicitly grant and publicize direct activation authority. |
| Week 3 | Build a response time measurement and tracking system. |
| Ongoing | Review activation events for any sign of hesitation or delay. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Junior staff interview | Asks a junior staff member directly whether they can activate rapid response without prior approval. |
Evidence base
Sedation and Delirium Management Protocol
Core
In plain terms: Sedation is kept to a specific, deliberately targeted level, and delirium is genuinely, actively screened for on a schedule — not assumed absent just because nobody happened to notice anything obvious.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
Sedation deeper than clinically necessary carries its own well-documented risks, which is why a defined, deliberately targeted sedation goal — rather than a default “keep comfortable” approach without a specific target — matters as a genuine clinical practice, not just a documentation exercise. Delirium, particularly its hypoactive form, is frequently subtle and easily missed without active, scheduled screening using a validated tool; assuming its absence because nothing seemed obviously wrong is a specific, well-documented detection gap.
What good looks like
- Sedation is targeted to a defined, documented goal, not a vague default.
- Delirium is actively screened for with a validated tool on a defined schedule.
- A positive delirium screen triggers a documented clinical response.
Common failure modes
- Sedation follows a general “comfortable” approach with no specific target.
- Delirium screening happens only informally, if a patient seems obviously affected.
- A positive screen is noted but doesn’t trigger a genuine clinical response.
Worked example
If you are starting from zero — do this first
- Adopt a validated delirium screening tool covering both hyperactive and hypoactive presentations.
- Build a defined sedation target documented for each patient.
- Build a required response process for a positive delirium screen.
Self-assessment questions
Evidence: Sedation target documentation
Evidence: Screening record
Evidence: Response-to-screen traceability
Common reasons for a PARTIAL answer
- A screening tool is used but not consistently on every shift.
- Positive screens are documented but the follow-up response is inconsistent.
Implementation plan
| When | What |
|---|---|
| Week 1 | Adopt a validated delirium screening tool. |
| Week 2 | Build a defined sedation target requirement per patient. |
| Week 3 | Build a required response process for positive screens. |
| Ongoing | Review screening consistency and response traceability. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Screening-to-response traceability review | Traces a specific positive delirium screen to a resulting documented clinical response. |
Evidence base
Family Communication and Presence Policy
Core
In plain terms: Families get genuinely regular updates they can actually understand, and the visiting policy is applied the same way no matter which staff member is on shift — not a lottery depending on who’s working.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
Inconsistent family communication, dependent on which clinician happens to be available at a given moment, is a well-documented source of significant family distress in critical care settings, independent of the clinical outcome itself. A family presence policy that varies meaningfully by which staff member is on shift functions, in practice, as no real policy at all — families experience this inconsistency directly and it erodes trust in the unit’s overall care.
What good looks like
- Families receive genuinely regular updates in understandable terms.
- The presence policy is applied consistently, not varying by staff member.
- A structured family conference process exists at defined clinical points.
Common failure modes
- Updates are sporadic, dependent on which clinician happens to be available.
- Presence policy application varies meaningfully depending on who’s on shift.
- Family conferences happen only if family specifically requests one.
Worked example
If you are starting from zero — do this first
- Build a required daily family update with a structured content format.
- Write a clear, specific presence policy and brief all staff on it.
- Build a structured family conference trigger at defined clinical points.
Self-assessment questions
Evidence: Family communication log
Evidence: Family interview
Evidence: Family conference trigger policy
Common reasons for a PARTIAL answer
- Updates happen but content and consistency vary by clinician.
- The presence policy exists but staff apply it with meaningful individual variation.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build a structured daily family update format. |
| Week 2 | Write and distribute a clear, specific presence policy. |
| Week 3 | Build a structured family conference trigger process. |
| Ongoing | Interview families periodically for consistency feedback. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Family interview | Asks a current patient’s family directly about communication consistency and presence policy experience. |
Evidence base
End-of-Life and Withdrawal of Care Protocol
Standard
In plain terms: End-of-life decisions follow a real, consistent protocol — with genuine ethics support and palliative care woven in alongside active treatment, not left to vary by whichever clinician happens to be in charge.
| Facility category | Crisis | Transitional | Small | Standard |
|---|---|---|---|---|
| Applicability | Where applicable | Full | Full | Full |
Why this matters
Significant, unexplained variation in end-of-life decision-making approach between individual clinicians, absent a genuine shared protocol, raises real concerns about consistency and fairness in some of the most consequential decisions a critical care unit makes. Palliative support treated as a separate referral that only happens after active treatment has fully stopped, rather than genuinely integrated alongside ongoing treatment decisions, misses the real value palliative expertise can add earlier in a patient’s course.
What good looks like
- A written protocol genuinely guides end-of-life decision-making consistently.
- Ethics consultation is genuinely accessible and actually used when needed.
- Palliative support is integrated alongside active treatment, not only after.
Common failure modes
- Approach varies significantly by individual clinician, absent a shared protocol.
- Ethics consultation exists on paper but is rarely actually used.
- Palliative support is treated as a separate step only after treatment stops.
Worked example
If you are starting from zero — do this first
- Build a written protocol standardizing family involvement and decision steps.
- Simplify and promote the ethics consultation referral process.
- Build a trigger point for palliative involvement alongside, not after, active treatment.
Self-assessment questions
Evidence: Written protocol
Evidence: Ethics consultation usage record
Evidence: Palliative involvement timing
Common reasons for a PARTIAL answer
- A protocol exists but adherence varies in practice.
- Ethics consultation is available but staff rarely actually use it.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review current variation in end-of-life decision-making approach. |
| Week 2 | Build a written, standardized protocol. |
| Week 3 | Simplify the ethics consultation referral process. |
| Ongoing | Review end-of-life cases periodically for protocol adherence. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Case review | Reviews several end-of-life cases across different treating clinicians for protocol consistency. |