Replacing a legacy hospital information system
Start with one patient record that sits above the systems you already run. Then move patient-facing steps such as booking and results, and retire each hospital information system (HIS) one unit at a time. The first release goes live with every clinical system still running.
Last reviewed:
Signs it is time
- Every acquired hospital has its own HIS, so the group cannot see one patient's full history.
- The vendor no longer issues updates, or your version has left support.
- Patients give their history again at every desk.
- Accreditation or national health-record requirements ask for evidence the system cannot produce.
- Billing, insurer and clinical systems disagree, and staff reconcile them by hand.
The order of work
- Unify the patient record. Add one patient index and identity layer on top of the current HIS platforms. Clinicians get one view and no running system is touched.
- Move patient-facing steps out. Booking, registration, test results and reminders can all run without a new HIS.
- Replace by unit. One hospital at a time, with the shared record already in place. A group-wide clinical cutover on one date is a risk with no gain to set against it.
- Retire on evidence. The old HIS turns read-only and is then shut down, after the new system has carried a full cycle that includes month-end billing and a data pull of the kind an accreditation audit requests.
National standards that shape the design
ABHA linking and consent-based sharing under ABDM belong in the shared layer, so they are built once and outlast any single HIS. Reports that NABH audits ask for are designed in at the beginning. The requirements themselves are set out in what modern hospital management software must do in India.
Data from an unsupported system
When the vendor offers no export tool, data usually has to be extracted from the database directly. It is slow, and teams often under-estimate it, so it is scoped as its own work item. Each extract is checked against the source with checksums before it is trusted.
When to leave the HIS as it is
- The HIS is supported and current, and the complaint is the screens. That is a design project.
- You operate one site on one system that does its job.
- An acquisition is under way. Wait until the estate you will design for is settled.
See it in practice
A multi-city hospital network put a patient app and one scheduling layer over three HIS vendors. The case page gives the results.
Related: legacy modernisation.
Questions buyers ask
Yes. The new layer takes its data from the current systems, and nothing clinical is turned off for the first release.
In the shared layer, so each future HIS replacement inherits it.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.