Inside the Pre-Flight Check: Catching Missing Documentation Before Notes Generate
product
A deep dive into the WoundScribe AI pre-flight dialog — the validator step that flags missing intake, wound, and order data before the scribe drafts the note.
The pre-flight check is the last thing that runs before Generate Notes hands work to the summarizer. It exists because a downstream SOAP note is only as clean as the intake, wound list, and order set feeding it.
What the pre-flight actually inspects
The validator sweeps every tab in the encounter workspace:
- Intake: vitals, allergies, attachments, intake checklist
- Wounds: at least one wound selected, measurements present
- Orders and Rx: every order has a linked ICD-10, every Rx has sig and quantity
- Clinical Note: dictation or typed note is present
The dialog itself
When you click Generate Notes, missing items appear as a checklist. Each row deep-links back to the tab that owns the gap. You can fix and return, or click Generate Anyway if the omission is intentional (for example, a follow-up visit with no new imaging).
Why this matters for compliance
Medicare audits flag missing measurements, absent diagnosis-to-order links, and undocumented offloading. The pre-flight surfaces those gaps before they become claim denials. Pair it with WISER claims and compliance for post-visit audit readiness.
How it fits with the other agents
The verification agent runs a second pass after generation to catch inconsistencies the pre-flight can't see — like an assessment that contradicts wound measurements. Pre-flight prevents; verification corrects.
What clinicians see in practice
Most encounters clear pre-flight with zero flags once vitals and orders are captured up front. When flags appear, they take seconds to resolve, and the resulting note requires fewer edits before signature.