Case study
Clinical platform running in a hundred hospitals — all on their own servers.
Bizmed
In the health sector, institutional scale and on-premise constraints apply at the same time. The platform had to operate in each hospital's own data center, without extracting data.
- Sector
- Healthcare
- Our role
- Architecture, development, distribution
- Deployment
- On-premise
Problem
A single platform, face installation independent of each other.
Clinical data cannot leave the hospital. This eliminates a centralized SaaS installation from the beginning: the platform needs to run on top of its own Oracle installation, in each organization's own data center.
The challenge is not to stand up a single installation, but to keep the same platform running and updating in about a hundred different environments. Each environment has its own hardware, its own network constraints, and its own maintenance window.
Approach
Divide it into services, package it, pass it through the line.
We divided the platform into .NET microservices. We have drawn service boundaries based on clinical workflows so that one module is updated while the others are not affected.
The data layer stayed on-premise on Oracle — we sat on them instead of replacing existing installations. Moving schema changes by versioning and verifying.
We packaged the services with Docker and set up CI/CD line. The same image goes to every hospital, regardless of the environment; only the configuration is specific to the installation.
Stack
What we used.
- Application
- .NET
- microservices
- Data
- Oracle
- on-premise
- Distribution
- Docker
- CI/CD
Result
He works in about a hundred hospitals.
Today, the platform is used in about a hundred hospitals; each institution on its own server, with its own data. Adding a new hospital has become a configuration job, not an infrastructure project.
- Each institution in its own data center, before the data goes out
- Service-based update — without stopping the entire platform
- The same image applies to every installation regardless of the environment
Are you working with a similar constraint?
If the corporate scale, the on-premise imperative, an untouchable database — it sounds familiar, let's talk.