Home / Implementation
Predictable, measurable, low-risk
The biggest risk in replacing a hospital system is not the software — it is the fortnight around cutover. This is the sequence we run, and the rollback path underneath all of it.
The method
Eight phases, each with an exit criterion
Nobody moves to the next phase because the calendar says so. Each one has an output that has to be signed before it closes.
Assessment
Current data, integrations, customizations and workflows inventoried and scored for migration complexity.
Exit: a complexity map and a realistic timeline
Planning
Configuration drafted against your actual rules — numbering, tariffs, approval matrices, pathways — and signed off before build.
Exit: an agreed configuration baseline
Data migration
Historical data moved with checksum verification at every stage and reconciled against source counts and balances.
Exit: a signed reconciliation report
Parallel run
Both systems process the same days. Differences reconciled every morning until the delta is consistently zero.
Exit: daily variance at nil, sustained
Verification
Financial balances, clinical records and statutory reports checked against the legacy system line by line.
Exit: sign-off from finance and clinical leads
Training
Role-based training on the task bar rather than on screens — which is why it takes days rather than weeks.
Exit: competency confirmed per role
Go-live
Cutover to a written runbook with named owners, defined checkpoints and a rollback decision at each one.
Exit: runbook executed, not improvised
Hypercare
On-site and on-call support at elevated intensity until agreed stability metrics hold for a defined period.
Exit: stability criteria met before we stand down
What we need from you
Implementations fail on the hospital side too
Being straight about this before contract is worth more than optimism after it.
What we bring
- A named implementation lead accountable for the whole programme, not a rotating account manager.
- Migration tooling with verification built in, rather than scripts written per customer.
- Configuration of your rules by people who understand hospital operations, not just software.
- An honest status every week, including when we are behind.
What we need from you
- An executive sponsor with authority to decide, not just to escalate.
- Access to the people who actually know your rules — usually not the people in the meetings.
- Time from clinical and finance leads for verification, protected in advance.
- A willingness to change a process where your current one exists only because the old software required it.
We will tell you plainly when a hospital is not ready — including when that is inconvenient for us. A delayed go-live is recoverable; a failed one damages a hospital and takes years to repair. See the migration detail →
Next step
See your hospital running on Ospia
An executive demonstration takes forty-five minutes. We seed a hospital with synthetic data shaped like yours, put the digital workforce on duty, and answer the hard questions with the architecture open.
synthetic data · zero real patients
self-hosted or managed cloud
one database per hospital