The backstage service that holds up the rest of the group's systems: 21 scheduled routines that process medical images, fire notifications, generate documents and centralise the logs of every application.
The challenge
Every growing ecosystem of systems ends up with the same problem: each application has its own background processes, each one logs in its own way, and when something fails at three in the morning nobody knows where to look. On top of that, there is heavy work that simply cannot happen inside the user's request — processing a medical imaging study, generating a batch of documents, firing hundreds of notifications. Run it alongside the screen and the screen freezes.
The solution
Pipa concentrates that work. It is a service of scheduled routines — 21 of them — that runs separately from the front-end applications and takes care of what has to happen in the background. The heaviest routine is medical image processing: it receives the studies in DICOM format, processes them and leaves them ready for viewing, without any clinic having to wait. Alongside that, Pipa is the single logging point of the ecosystem. Every application in the group — AeroMeter, iASO, Panaceia, Lyd, Kuti — sends its messages to it, which gives a unified view of what is happening across the whole operation, instead of five different places to look. It is also the route for the WhatsApp notifications and the PDF document generation that the other systems request.
Results
21 routines in production supporting five of the group's systems. A single logging and notification point for the whole operation, with medical image processing decoupled from the front-line applications.