Skip to main content

Handoff (I-PASS)

Shift handoff fails when it becomes either too long (noise) or too short (missing contingencies). Clinical Corvus helps teams produce a consistent I-PASS-style handoff draft that clinicians can quickly edit.

caution

AI-generated handoffs are drafts that require clinical review. Always verify patient identifiers, active problems, and contingency plans before sharing. I-PASS is a structured communication tool - its effectiveness depends on accurate, personalized content.

When To Use​

  • End of shift sign-out
  • Inter-team transfers (ICU ↔ ward)
  • High-acuity patients where contingency planning matters

The Workflow​

  1. Confirm the patient context and refresh it with the most recent note/labs if needed.
  2. Generate or open the handoff draft.
  3. Review each I-PASS block:
    • Illness severity (simple, explicit)
    • Patient summary (short problem representation)
    • Action list (concrete tasks for next shift)
    • Situation awareness + contingency plans (“If X happens, do Y”)
    • Synthesis by receiver (what the next clinician should repeat back)
  4. Apply Check-to-Accept and adjust wording to local conventions.

Workflow​

Legend:

  • 🔵 Blue: User actions
  • 🟡 Yellow: System analysis
  • 🟣 Purple: Draft generation
  • 🔴 Red: Verification and control
  • 🟢 Green: Finalization and export

I-PASS Components:

  • Illness Severity
  • Patient Summary
  • Action List
  • Situation Awareness
  • Synthesis by Receiver

What Good Handoff Output Looks Like​

  • A patient summary that is stable across shifts (no drift in key facts).
  • An action list that is specific and time-bound.
  • At least one explicit contingency for each major risk.

Common Pitfalls (And How To Avoid Them)​

  • Overlong summary → enforce a strict “one paragraph” limit.
  • Missing contingencies → ask explicitly: “What are the top 2 risks overnight?”
  • Ambiguous ownership → add who/when for each action item.