Most hospital system replacements begin with a migration project. Wellness was built so that yours does not have to.
1 Sep 2026 · 5 min read · Wellness team
Replacing a hospital information system is usually two projects. The first is the software. The second, and the one that actually decides the go-live date, is moving years of patient records, tariffs, stock ledgers and journal entries into a new schema, then proving nothing was lost on the way.
Wellness was designed to remove the second project. Its data model was not drawn on a whiteboard. It was reverse-engineered from a live hospital database: the one the current system reads and writes every day. Every entity in the new application maps to a table that already exists. Go-live creates nothing; it starts from the schema as it stands.
What that means on go-live day
- No cut-over weekend. The new application points at the existing database and starts reading. There is no export, no import and no reconciliation report to sign.
- History stays where it is. A visit from five years ago keeps its medical record number, its invoice number and its journal line.
- Reports keep working. Anything that reads the database, from a finance extract to an insurer's reconciliation file, still finds the same tables.
- Departments can move one at a time. Both applications read and write the same records, so a hospital can bring the laboratory onto Wellness this quarter and the pharmacy the next without splitting its data.
Parity is the standard
Building against a live schema sets a demanding bar. Every calculation the current system makes, whether a tariff lookup, a discount rule, a ward charge or a stock write-back, has to come out identically in the new one. The Wellness team works to a parity rule: each module is traced against the behaviour of the running system, case by case, before it is signed off. Where the old rules were inconsistent, the new ones fix the fault and record the decision.
The screens are new. The rules are new and verified. The data has not moved an inch.
| Layer | On go-live |
|---|---|
| Screens | New |
| Application and business rules | New, verified against the current system |
| Database and schema | Unchanged |
| Medical record numbers, invoices, journals | Unchanged |
| Reports and extracts | Unchanged |
The result is a system that feels new to the people using it and entirely familiar to the data underneath.