INDUSTRY FIELD GUIDE
Hospital discharge packet version and handoff data for AI
A hospital can evaluate whether software distinguishes a drafted discharge packet from the approved version and a separate receiving acknowledgment.
NAICS 622110 · General Medical and Surgical Hospitals
A hospital can evaluate whether software distinguishes a drafted discharge packet from the approved version and a separate receiving acknowledgment. Federal hospital conditions address discharge planning. HealthBench provides a public example of physician-written grading criteria for health tasks. Federal discharge planning requirements · OpenAI HealthBench
Create an original fictional stay with two packet versions and a receipt for only the earlier version. Ask which copy the source identifies as current and whether the receiving team acknowledged it. Score version, destination and missing evidence separately. Use administrative content only.
Keep patient records, dates of real stays, discharge instructions, conversations and system exports out. Ask hospital privacy and clinical staff to review any separate real-data proposal.
Describe a fictional discharge handoff sample
Original Fiund exercise
Acknowledgment of an earlier packet does not acknowledge its approved replacement
A fictional administrative handoff has two original packet covers and inert destination aliases. It contains no stay details, discharge instructions, patient conversation or hospital export.
| Record | Source | What it records |
|---|---|---|
| HD1 | Packet versions | Episode DEMO-E: V1 approved day 1; V2 approved day 2 and explicitly supersedes V1. Administrative field ROOM-LABEL changes from A to B. |
| HD2 | Receiving acknowledgment | Destination D acknowledges DEMO-E/V1 on day 1. No V2 acknowledgment supplied. |
| HD3 | Delivery note | V2 sent to D on day 2. Separate draft V3 unsigned; no supersession authority. |
Question for the model
Which packet is the current approved version, and has the receiving team acknowledged that exact version?
Show the reference answer and checks
HD1 identifies V2 as the current approved replacement for V1, while HD3's unsigned V3 does not supersede it. HD2 acknowledges only V1. HD3 documents sending V2 to D but supplies no matching receiving acknowledgment, so receipt of the current version remains unverified. Keep approval, dispatch and acknowledgment as separate states rather than transfer an earlier receipt to a changed packet or infer a clinical handoff outcome.
- Treating a prior-version acknowledgment as receipt of a replacement packet.
- Selecting an unsigned draft or equating dispatch with confirmed receipt.
Fields to preserve
- Episode and approved packet version
- Defines the current source.
- Supersedes reference and changed field
- Limits the amendment.
- Destination, sent event and acknowledged version
- Supports the handoff state.
Test another case
Add a V2 acknowledgment from destination D2 instead of D. Require a destination mismatch rather than complete the intended handoff.
Use original administrative covers only. Exclude patients, instructions and actual stays; hospital privacy and clinical staff review any later real-data proposal.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.