The Ward Round That Goes Wrong Without Current Records
You arrive at ward 14 for morning rounds. The night shift team made a medication change, added an investigation result to the file, and updated the assessment plan. You know none of this because the handoff note was verbal, made at 0630, and the registrar who wrote it down wasn't the one who received the update. By the time you're standing at the bedside, you're working from a clinical picture that's six hours stale. The patient tells you something that contradicts your mental model of their trajectory. You spend the next twenty minutes reconstructing what happened overnight instead of making the decisions you came to make.
That is the ward round failure mode. It happens in systems where clinical notes exist in one place, assessment plans in another, and investigation results get photographed and texted to whoever needs them. The data exists — it's just distributed across three media in a sequence nobody can reconstruct cleanly.
How the Audio Fields Change the Documentation Habit
The deliberate design decision in this template is the dual-track documentation structure. For Clinical Notes & Progress, Assessment Notes & Plan, Treatment Notes & Plan, and Discharge Diagnosis & Plan, there are both text fields and audio fields. That's not redundancy — it's a recognition that clinical documentation happens under time pressure.
A physician finishing a complex assessment at the bedside can dictate the assessment note in forty-five seconds. The same note typed on a phone takes three minutes and gets abbreviated or deferred. The audio field captures the complete thought in real time. The text field captures the distilled, structured version when there's time to write it properly. In an HDU or CCU context, where the acuity of multiple patients is shifting simultaneously, the audio field is what gets updated; the text field is what gets reviewed at the next handoff.
The Attach Any Remarkable Finding/Result image field works the same way — an ECG trace, an imaging result, a wound photograph taken at dressing change. It lives in the record alongside the clinical notes that reference it, not in a separate WhatsApp group or a folder on someone's personal phone.
The File Number Is the Record's Foundation
Every clinical interaction in a real ward system traces back to a file number. The File Number field here is an integer — not a text string — which means it sorts correctly and can be searched exactly without partial-match errors. When a patient is transferred from ward 17 to ICU, the file number follows them. When they're discharged and readmitted six weeks later, the previous record is accessible by the same number.
The Patient Place dropdown covers ward 14 through 28, HDU, ICU, and CCU. A query filtered on ICU with an empty Discharge Date gives you your current ICU census, sorted by Date of Admission. That's your acuity list. Filter for CCU patients admitted more than seven days ago and you have your long-stay review queue before you've walked into the unit.
Discharge Date closes the record lifecycle. An admission record without a discharge date is an active patient. An admission record with both dates and a Discharge Diagnosis & Plan is a completed episode. The difference matters for patient load calculations, audit compliance, and the basic sanity check of knowing how many active inpatients your team is actually managing.
The Treating Unit field sits outside the dropdown logic precisely because treating team configurations change — staff rotations, cross-covering teams, subspecialty consultations taking over primary management. A text field captures that fluidity without forcing every possible configuration into a dropdown that becomes unmanageable within a few months.