Convert clinical handoff notes into reviewable documentation

Why use this

1. A physician may receive rough handoff notes containing abbreviations, uncertain statements and missing context. Turning them into polished documentation can accidentally make tentative information sound confirmed or fill a clinically important gap with plausible prose.

2. This job could prepare structured drafts that preserve uncertainty and explicitly ask for missing information. Keeping release control with the clinician allows the draft to improve organization without becoming an independent clinical decision or an unreviewed patient communication.

Why an agent / simpler alternative

Useful judgment

Organize supplied facts by documentation purpose, preserve attribution and identify gaps without inventing clinical content.

Simpler alternative

Use a standard documentation template when the notes are already complete and structured.

Unsuitable when

Patient data cannot stay within approved systems or the workflow would diagnose, prescribe or release content without clinician review.

Proposed inputs

1. Name

   Authorized note excerpt

   Owner

   Treating clinician

   Minimum scope

   Minimum relevant clinical facts with privacy controls

   Quality check

   Separate confirmed, reported and uncertain statements

2. Name

   Documentation brief

   Owner

   Clinician

   Minimum scope

   Requested draft types and approved audience

   Quality check

   Define missing-information handling and release boundary

Access and setup — proposed or unknown

Proposed minimum

1. Use synthetic nonclinical placeholders first; no real patient records, external model transfer or messaging.

Compatibility unknowns

1. Current secure environment, documentation formats, model routing and runtime compatibility are unknown.

External actions requiring approval

1. Patient-data access/transmission, record updates, referrals and patient communications require explicit governance and clinician authorization.

Expected deliverable and review checks

Proposed artifact

Draft-document structure with source-linked facts, uncertainty labels and clinician questions; release remains pending.

Critical checks

1. Preserve negation, chronology and attribution; avoid expanding ambiguous abbreviations; check each audience-specific draft against the same facts.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   An uncertain note becomes a definitive diagnosis

   Why it matters

   Polished wording changes clinical meaning

   Proposed response

   Retain uncertainty and ask the clinician to resolve it.

2. Signal

   A copied sentence loses negation

   Why it matters

   The draft reverses an important fact

   Proposed response

   Compare against the original and hold release.

Effort and cost — unknown

Setup work

1. Define privacy boundaries and documentation conventions.

Ongoing review

1. Clinician verifies every material statement before any record or communication use.

Unknowns

1. Input completeness, abbreviation ambiguity, secure tooling and review effort are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent a placeholder handoff with an uncertain finding, explicit negation and missing time; outline draft sections and questions only.

Acceptance checks

1. Preserve uncertainty/negation; flag missing time; offer no clinical interpretation or release.

Stop conditions

1. Stop if real patient data lacks approved handling or a gap requires clinical inference.

Limits

1. Organized drafts cannot establish clinical correctness, completeness or authorization to communicate medical information.