SterilFejl
Fault-reporting platform for a hospital's sterile supply department of 50+ staff. Commissioned by department leadership to replace phone calls and memory with structured reporting, realtime dashboard visibility, and notifications.
Equipment in a sterile supply department gets flagged, repaired, replaced - or it falls through the cracks. SterilFejl keeps every fault visible: staff report issues from their phones, new reports appear on the dashboard immediately, and every report carries a status until it’s resolved.
Commissioned by department leadership, built for a department of 50+ staff, with rollout underway in 2026.
Why I built it
The department director wanted a data-driven system instead of a process that relied on phone calls and memory. He wanted to see exactly which machines broke, why they broke, how often it happened, and how long each case took to resolve. SterilFejl turns that into structured reporting: one place to file a report, one place to check status, and a clear record of what happened.
How it works
A report takes about 10 seconds to file through a mobile-first, PIN-protected form. Staff choose area, category, machine, and fault type, with an optional comment. Reports appear on the technician dashboard immediately, with realtime updates and push notifications so new faults do not sit unseen. Critical fault types are highlighted so urgent issues stand out faster.
Status changes (open -> in progress -> resolved) update in real time, so anyone can check where a report stands without chasing anyone down.
Technicians can filter and sort active faults, add technician comments, inspect recent equipment history, export resolved history to CSV, and use statistics to see patterns across machines, fault types, categories, and resolution time.
Built to run in production
Beyond the reporting flow, SterilFejl includes the operational layer a hospital tool needs: an admin panel for areas, categories, machines, fault types, users, settings, statistics, and recurring maintenance tasks. It is installable as a PWA, supports offline queueing for reports, and has a completed security review covering Supabase row-level security, privileged function exposure, auth hardening, rate limits, and production diagnostics. Built with Next.js, Supabase, and Vercel.