· 2026
ED consultation and documentation generator
Single-file web tool used daily in our emergency department. Generates consult messages, clinical notes, and transfer paperwork from ten templated chief complaints, with embedded clinical scoring.
The problem
Junior doctors rotating through our emergency department spend a substantial portion of every shift on three documentation tasks: composing the consult message that goes to the receiving service over WhatsApp, writing the formal clinical note in the hospital’s HBYS system, and filling out the sevk belgesi (transfer document) that has to accompany any patient sent to a tertiary center. The information overlaps almost entirely across the three artifacts, but the formats don’t, so the same facts get re-entered three times under time pressure. Errors propagate. Junior doctors learn to dread the paperwork before they learn to dread the patients.
Compounding this, decisions about clinical scoring — HEART for chest pain, Wells for PE, CURB-65 for pneumonia, Alvarado for appendicitis — happen in parallel with the documentation, often in a different browser tab on a different calculator site. The cognitive switching cost is real and the resulting notes often omit the score that supported the disposition decision.
What I built
A single self-contained HTML file. Opens in any browser, no install, no server, runs from a USB drive or a hospital intranet share. Ten chief-complaint templates cover roughly 90% of our actual ED case mix: chest pain, dyspnea, abdominal pain, headache, syncope, trauma, GI bleed, altered mental status, pediatric fever, extremity injury.” Each template structures history, exam, workup, and disposition. A drawer on the side gives quick access to fifteen clinical scores, and the result of any score the user runs is automatically stitched back into the generated note.
Output comes in three forms simultaneously, from one set of inputs:
- A WhatsApp-formatted consult message. Compact, the format the receiving service actually expects, with the receiving doctor’s name and the consultant question front-loaded.
- A full clinical note formatted for HBYS, paste-ready.
- A sevk belgesi PDF, generated client-side, with the relevant fields prefilled.
Disposition options are deliberately constrained to what our hospital actually offers — no cardiology service, no ICU step-up — so the tool reflects the real decision space rather than a generic textbook one.
What was technically interesting
The decision to keep it as a single file. Every piece of infrastructure I’d normally reach for — a build step, a framework, a server — is also a piece of infrastructure that has to keep working in five years on hospital computers I don’t control, behind firewalls I can’t reason about, with browser versions I can’t predict. A 200KB HTML file with inlined CSS and JS sidesteps all of that. It works the same in 2024 as it will in 2030. No package updates, no dependency graph, no broken-tooling silences.
The clinical scoring drawer reuses logic from an earlier scoring toolkit I’d built. That earlier project’s surface area (fifteen self-contained scoring functions, each with its own UI and validation) was small enough to copy over wholesale, which is how a “predecessor” tool ended up being structurally part of the successor.
Outcome
In daily use across all shifts since deployment. Documentation time per patient encounter has dropped substantially — our junior doctors notice it most, since they have the steepest learning curve to overcome. The tool has also become a soft teaching artifact: junior doctors who use it get exposed to structured scoring as a default rather than as something they remember to do.