Selected work

Digital health · Production system

Building complex workflows for a production electronic health record

Full-stack product work on a secure electronic health record used by more than 2,500 general practitioners in Belgium.

Role

Full-stack development, functional and technical design, production problem-solving and progressive modernisation.

Timeline

2022 — 2025

Team

Product & engineering team

Status

In production

Impact

Used by 2,500+ general practitioners

Clinical software has to translate dense domain rules and connected care workflows into an interface that remains clear during real consultations.

Who it was for

Healthcare professionals working in Belgium.

Why it was difficult

Balancing product change with the safety, continuity and domain precision expected from clinical software.

Full-stack development, functional and technical design, production problem-solving and progressive modernisation.

  • Sensitive medical data and regulated workflows
  • End-to-end encryption and per-user private keys
  • A mature application already used in production
  • Belgian eHealth interoperability requirements
  • Many interconnected business rules
  1. 01

    Model workflows across frontend and backend instead of treating the interface in isolation.

  2. 02

    Improve the existing system incrementally to protect production continuity.

  3. 03

    Prioritise maintainability, interoperability and observable production behaviour.

One product, several connected layers.

Conceptual public diagram — no confidential product detail.

Clinical, administrative, reporting and interoperability features shipped to a production product used by more than 2,500 general practitioners.

What I learned

Complex domains reward careful modelling, close collaboration with domain experts and changes that can be safely introduced over time.

  • Angular
  • TypeScript
  • RxJS
  • Nx
  • Spring Boot
  • CouchDB
  • End-to-end encryption
  • FHIR
  • KMEHR
  • MyCareNet