Rosters and shifts
Duties, shifts and agendas for every department, in the same system as everything else.
HealthcareSoftware studio · Utrecht
A hospital system, scaled 30×.
From 5 users to 150, serving thousands of patients.
The intranet a Dutch hospital runs on, built hands-on as Head of Engineering at a software studio in Utrecht, and part of the organisation’s ISO certification.
- ROLE
- Head of Engineering (hands-on)
- WHEN
- Oct 2023 – May 2026
- WHERE
- Utrecht, Netherlands
- CLIENT
- Shared on request
THE HEADLINE
5 → 150
Users, serving thousands of patients
- 86
- backend modules
- ISO
- part of the organisation’s certification
- EPD
- integrated with patient records
01 · The problem
A hospital runs on rosters, records and paperwork.
Staff needed one place for rosters, documents, patient information, emergencies and requests, connected to the hospital’s patient records and fit for an ISO-certified organisation. In Dutch first, and in English.
02 · What I built
One intranet for the whole hospital.
Documents
Policies and templates in one place, generated from Word to PDF and ready for audits.
Patient information
Versioned patient leaflets with reviewers, so nothing reaches patients unchecked.
Helpdesk ticketing
Ticket types, custom fields, locations, assignments and outside collaborators, tracked start to finish.
Emergency messages
Emergency broadcasts with templates, and the in-house emergency response team on call.
Daily life
News, polls, a knowledge base, a phonebook, chat and notifications for every member of staff.
03 · Key decisions
Connect, don’t replace.
Work with the patient records
Instead of rebuilding what the hospital already trusted, the intranet integrates with the existing electronic patient records.
Ready for audits
Versioning, reviewers and generated documents were designed to support the organisation’s ISO certification.
Typed from end to end
A code-first GraphQL API with generated types and hooks per module, so 30 frontend modules stayed in step with the backend.
Releases through UAT
Every change goes from dev to UAT to production through reviewed pull requests and Docker builds on Azure Pipelines.
04 · Stack
Under the hood.
Backend
- NestJS
- GraphQL
- TypeORM
- PostgreSQL 16
- Redis
- WebSockets
Frontend
- Next.js
- React
- Chakra UI
- Apollo Client
- next-intl
Delivery
- Docker
- Azure Pipelines
- Azure Blob Storage
- Papertrail
05 · Results
What it added up to.
- 5 → 150
- Users
- Thousands
- Of patients served
- 850+
- Pull requests merged on the backend
Next case study · 06
Running a clinic, on web and mobile
Need software a hospital can rely on?
I build healthcare systems hands-on, from architecture to release.