Customer and task
Help a fictional hospital improve administrative follow-up after discharge. Check contact consent, verified details, plan completeness, language and available escalation staff before proceeding. The system supports administrative work, not diagnosis or treatment.
Try it
Check contact consent and verification first. For missing plans or tasks requiring a nurse, describe pausing and handoff, then verify that the receiving team can stop and restore the workflow independently.
How to use this data
The data contains no diagnoses, names, contact details or clinical text. Use it for administrative workflow practice, not clinical judgments or inferences about real patients.
The dataset contains 18 practice records. Use paper or a spreadsheet to count and compare task groups, then list possible causes and questions to test. No coding is required.
Download synthetic JSON dataSample distribution
View chart data
| status | Records |
|---|---|
Queued queued | 9 |
Blocked blocked | 5 |
Do not contact do_not_contact | 2 |
Urgent queue urgent_queue | 2 |
Field reference
| Field | Meaning and limitation |
|---|---|
id | Synthetic event identifier for cross-referencing. |
ward | Fictional ward label, with no correspondence to real patients. |
due_hours | Administrative follow-up deadline in hours. |
language | Task language code, such as zh, en, de or ja. |
contact_consent | Whether contact consent is recorded; not authorization for clinical decisions. |
contact_verified | Whether contact details are verified; no real contact details are included. |
plan | Administrative plan state, such as complete or missing. |
status | Task state, such as queued or blocked. |
escalation | Escalation role, such as nurse; none means no escalation is flagged. |
What to write down
Write a one-page analysis: which tasks to address first, supporting records, questions to test, owners and pause conditions. End with a specific next step. Mark missing evidence for follow-up rather than inventing facts.