Clinical Handoff Structuring Chain

validated medical chain v1.0.0 cc-by-sa

Block ID: 53add2aa-3cd5-4430-8f1e-b129804f0c6b

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. This block operates in a regulated domain. Nothing generated using this block constitutes professional medical, legal, or financial advice. User assumes all responsibility for use.

This block carries additional risk (risk level: medium) and requires a stronger domain-specific disclaimer when used.

Template

Structure a clinical handoff for the patient situation in {handoff_context} as an educational communication exercise, since most handoff failures are omissions of the critical thing, not excess detail. (1) Situation: state concisely who the patient is and the immediate reason for the handoff — the one-line framing that orients the receiver before any detail. (2) Background: give only the context needed to act, the relevant history and course, filtering ruthlessly, because burying the receiver in the full chart is as dangerous as omitting key facts. (3) Assessment: state the current clinical status and your interpretation of what's going on, including your degree of certainty — a handoff that reports data without synthesis forces the receiver to re-derive it, wasting time. (4) Recommendation and to-do: state explicitly what needs to happen, what you're asking the receiver to watch for, and the specific triggers that should prompt action or escalation — anticipated problems named in advance are the highest-value part of a handoff. (5) Highlight the can't-miss item deliberately and confirm the receiver has it, using read-back for critical information. (6) Close the loop: state pending results, open questions, and who to contact. Emphasize this is a communication-structure framework to support safe care among clinicians; it is educational, does not itself make clinical decisions, and does not replace professional judgment.

Structure a clinical handoff for the patient situation in {handoff_context} as an educational communication exercise, since most handoff failures are omissions of the critical thing, not excess detail. (1) Situation: state concisely who the patient is and the immediate reason for the handoff — the one-line framing that orients the receiver before any detail. (2) Background: give only the context needed to act, the relevant history and course, filtering ruthlessly, because burying the receiver in the full chart is as dangerous as omitting key facts. (3) Assessment: state the current clinical status and your interpretation of what's going on, including your degree of certainty — a handoff that reports data without synthesis forces the receiver to re-derive it, wasting time. (4) Recommendation and to-do: state explicitly what needs to happen, what you're asking the receiver to watch for, and the specific triggers that should prompt action or escalation — anticipated problems named in advance are the highest-value part of a handoff. (5) Highlight the can't-miss item deliberately and confirm the receiver has it, using read-back for critical information. (6) Close the loop: state pending results, open questions, and who to contact. Emphasize this is a communication-structure framework to support safe care among clinicians; it is educational, does not itself make clinical decisions, and does not replace professional judgment.

Variables

Name	Type	Required	Trust level
handoff_context		yes

handoffsbarcommunicationchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18