Reference · Bizmed
An ongoing engineering partnership in healthcare software.
We are moving a desktop platform used by dozens of hospitals to a modern web and microservice architecture without taking institutional data off-site.
- Duration
- 2+ years · ongoing
- Deployment
- On-premises
The work
Over a partnership of more than two years, we have been migrating the desktop application to a modern web platform without interrupting hospital operations.
The new .NET microservices run on each hospital’s own servers. Docker and GitHub Actions provide controlled releases across institutions, while Oracle performance and schema migrations are also in scope.
The partnership continues with team augmentation and a React Native app for doctors and nurses.
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.
Scope
- Desktop-to-web migration
- Microservices
- On-premises CI/CD
- Oracle
- Mobile application
Technologies
- .NET
- Docker
- GitHub Actions
- Nginx
- Oracle
- React Native
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