A hospital cannot pause. Unlike almost every other ERP migration, there is no quiet weekend where nothing is happening, and the cost of a data gap is not commercial — it is clinical.
That constraint shapes everything about how this is sequenced.
Patients admitted across the cutover
This is the defining problem. On cutover day there are in-patients mid-admission, with orders placed, medications given and investigations pending in the old system, who will be discharged from the new one.
Three workable approaches, in order of preference:
- Migrate active episodes fully. Best clinical outcome, most work. Every in-patient's current admission — orders, administrations, notes, pending results — recreated in the new system before go-live.
- Old system read-only, new system for everything from cutover. Clinicians consult two systems for those patients until discharge. Acceptable for a short, deliberately chosen window when the census is low.
- Discharge everyone first. Only possible for a very small facility or a planned shutdown. Rarely realistic.
Whichever is chosen, the ward staff need to be told explicitly which system holds truth for which patients, on paper, at every nursing station.
Medical record numbers must remain continuous
A patient returning after five years has to be found. If the new system issues fresh MRNs without carrying the old identifier as a searchable alias, that patient becomes a new patient with no history, and their prior admissions are effectively lost to whoever is treating them.
Carry the legacy MRN as a searchable field even where the new system uses its own numbering. Test it by searching for a real historic patient before go-live, not after.
Interfaces are the long pole
Lab analysers, radiology, PACS, pharmacy dispensing, insurance and scheme portals. Each is a separate integration and each can fail independently. Order them by clinical impact and start with the ones that cannot be worked around manually.
For anything not ready on day one, agree the manual fallback in advance — who transcribes a result, where it is recorded, how it reaches the chart. An undocumented fallback becomes a verbal instruction that half the shift never hears.
Statutory and scheme reporting cannot lapse
Birth and death registers, notifiable disease reporting, blood bank records, controlled substance registers, and returns under whichever government health schemes the hospital participates in. These have legal deadlines that do not pause for a migration.
Confirm before cutover that the new system can produce each required format, and keep the old system reachable for any period it must still report on.
Train by role, on the ward
Classroom training does not survive contact with a busy OPD. Train registration staff at registration, nurses at the nursing station, and billing at the billing counter, using their own workflows.
Then staff the first week heavily — someone physically present on each shift for the first several days, including nights. The night shift is consistently under-supported in these projects and is where workarounds get invented that then persist for years.
A short go-live checklist
- Every nursing station has written instructions on which system to use for which patients
- Legacy MRN search tested against real historic records
- Manual fallback documented for every interface not live
- Statutory report formats verified, not assumed
- Named support person per shift, including nights, for the first week
- A stated rollback decision point and who makes the call
About the author. Kislay Chandan has worked with schools since 2014. Rather than gathering requirements from the outside, he worked inside a school to see what actually goes wrong day to day, and built what he found into the software. He still works with Shemrock Glitters in Patna — most changes to the product start with something that came up there.
Gallery
