New Digital-Health Work Is Waiting on Records Only an Old System Can Read.
An old system kept running only for its records holds back reporting, AI and connected health records. Here is what waits, the four ways to deal with the archive, and the benchmark for the decision.
In the corner of the IT room there is a server that does one thing. It runs the hospital’s previous system, so that old records can be looked up.
Nobody enters new data into it. It is used perhaps twice a week. It needs its own old database, its own licence and its own backups.
The same month, the digital team brings a plan: connected health records, a reporting tool, perhaps an AI assistant for discharge summaries. Every one of them wants the hospital’s history. The history is on that server, in a form only the old system can read. Moving it is risky, someone says. Leave it for now.
The paradox: To avoid the risk of moving its old records, the hospital keeps them where none of its new work can reach them.
What We Found
We looked at why old systems stay in place, and at what India’s digital-health programme now asks of hospital systems. We found no healthcare evidence on data held in old formats itself, so the facts below are cross-sector or from nearby parts of the record.
The old system stays because it still works. In one survey of around 500 IT professionals in the US, across industries, asked why their organisations had not modernised old systems, half said the current system still works and about a third named data migration concerns. The survey was run by a vendor and published in 2025.
The store under the records ages anyway. For SQL Server 2012, extended support ended on 12 July 2022 and the paid updates sold after that ended on 8 July 2025. For SQL Server 2016, extended support ended on 14 July 2026.
Old stores left running are reached. One vendor-written article reports that at a large health record supplier, an attacker used stolen login details to reach old migration servers that had not yet been moved to the supplier’s newer platform, and copied data out. Old servers waiting to be migrated were the way in.
India’s digital-health programme now asks for connected records. On 17 July 2026 the National Medical Commission directed medical colleges to implement an “Ayushman Bharat Digital Mission (ABDM)-compliant Health Management Information System (HMIS)” in their hospitals, and published lists of medical colleges, including colleges “still not using ABDM-enabled HMIS software”.
There is also a reward for connected records. A government backgrounder of 6 July 2026 says that under the Digital Health Incentive Scheme, hospitals “earn cash incentives for creating interoperable digital health records”. By 18 June 2026 the scheme had paid hospitals more than 107 crore rupees.
What our review does not show: The survey is cross-sector, US-only, vendor-run and not about records. The supplier case is one vendor-written article with no year and no impact figure. The Commission’s direction is addressed to medical colleges, not to every hospital, and it is about connected record systems, not old records; the incentive is a reward, not a penalty. No source ties either to a hospital’s old archive. We found no figure for what an archive costs, how long an old record takes to find, or how often a migration loses data. We did not research how long medical records must be kept, who may see them, or what data protection rules require.
The Work That Waits on a Locked Archive
The yearly question is usually framed as a risk: what if something is lost in the move? The question that decides the matter is different: what can the organisation not do while its history stays where it is?
Connected records. Our reading is that a hospital linking its records to the national network starts with the records it can read. History held in an old system’s own codes is the hardest place to start.
The incentive. A hospital whose systems cannot create interoperable records cannot earn the incentive for creating them. That is our reading of the scheme’s own wording.
Reporting and AI. A reporting tool or AI assistant shows only what it can reach. With the history locked in, it starts from the year the new system went live.
Switching off. The old system cannot be retired, because it is the only way into the archive. Its database ages and its cost returns each year.
The gap we see: judged as a migration risk, “leave it for now” always wins. Set beside the reporting, AI and connected-records work that waits on the same history, it is a different decision. The opportunity is to make the old records readable and movable once, so new work starts from the whole history and the old system can go.
This is our reading of the evidence. It is not a measured market figure, and we do not put a rupee value on it here. That figure has to come from your own organisation.
Four Ways to Deal With the Archive, Weighed
| Option | When it fits | What it risks |
|---|---|---|
| Keep the old system running as an archive | Lookups are rare and the archive has a firm end date | The database goes out of support, the cost returns each year, and none of the new work can reach the history |
| Dump the old tables to files and switch the system off | The data is simple and its codes are already written down | Files of codes with no meaning attached; new tools still cannot make sense of them, and nobody can show the dump is complete |
| Move every old record into the new system at once | The old data is small, recent and well understood | One date carries every mismatch between old and new, decided under pressure, with no way to show what arrived |
| Write down what the old data means, then move it with each module and check each stage | The records are old, coded, and still needed by clinicians, finance and the new work | Two systems run side by side for a time, and for a time you pay for both. Clinicians and records staff must give time to decide mismatches |
Our recommendation: write down what the old data means first, as part of the specification: each table, field and code, confirmed by the staff who used it, with a list of what nobody can explain. Then move the data module by module as the system is replaced, starting with what the planned work needs first, and check each stage before the next begins. Your clinicians and records staff decide how old entries appear in the new record. The old system keeps running until the last stage is accepted, and then switching it off is your decision. We do not run archives, and we do not decide which records you must keep.
Where You Are Now, and Where You Should Be
Before the next year’s archive costs are signed, we would set a benchmark for the decision itself.
| Measure | Typical starting point | Where it should be | How it is checked |
|---|---|---|---|
| The cost of staying | The licence alone | The licence, old hardware, backups and staff time for the archive, in one place | The cost comparison |
| The cost of leaving | One large figure, never broken down | A price for each stage | The staged plan and quote |
| The new work waiting on old records | Not linked to any data | Each planned piece listed against the old data it needs | The staged plan |
| What the old system holds | Known to a few people | Each table, field and code written down | The specification |
| The check on each stage | ”Something might be lost” | Counts compared and samples read side by side, signed off by your records staff | Set in the benchmark before work starts, reviewed after each module |
| The archive’s end date | None | A date the organisation chose, tied to the last stage | The staged plan |
The starting points above are what we expect to find. In an engagement they are replaced by your own position, taken in the first review. The targets are what we would work towards with you. They are not results we have already achieved for a healthcare organisation.
How We Work With You
- We listen: a free Reliability Review. A first conversation about the old system, the records it holds, and the work that is waiting on them. You leave with a short written note of what we found.
- We research. We research your sector, the regulator’s position and what the public record says about firms in your situation. This article is an example of that work.
- We read the system and propose: the Legacy System Specification Assessment. It produces a written specification of what the system does, a risk register, a cost comparison between keeping and replacing the system, and a staged plan with a fixed quote. AI does a first pass, our senior engineers review it and trace it to the code, and your own experts confirm it. Code access is read-only and logged, never used for training, and deleted within 30 days of the evaluation ending unless we engage. You get the options and our recommendation.
- If you approve, we build. We replace a system one module at a time while the old one keeps running. We never do a single cutover. A traceability matrix links each old function to its replacement. The work is billed by milestone, each milestone tied to a module you accept, and you can pause after any accepted module. Where a module touches clinical work, accepting it is your clinicians’ decision.
- We review against the benchmark. Before work starts we set the benchmark. After each module we show you where each measure stands, and the filled-in benchmark is yours at the end.
The Review is free. Every paid step is fixed price, agreed at scoping. Stop after any step. The findings are yours. The assessment fee is credited in full against the first build stage if it starts within 90 days of the report.
The traceability matrix shows that each function moved. It does not by itself show that every record arrived, which is why the check on the records is a measure in the benchmark, set with you before the first module.
What you need to bring: read-only code access once the assessment begins; time from the people who used the old system; clinicians and records staff to decide mismatches; and your own team keeping the old system running until the last stage is accepted. Who may see any real patient record is for you and your advisers to decide.
Meeting the Commission’s direction where it applies to you, or any rule on keeping or sharing records, is your organisation’s own work; we do not offer a compliance or legal service.
What changes for the business:
| Role | What they gain |
|---|---|
| CEO | The old system can finally be switched off. It is no longer carried for the sake of its archive. |
| CTO or CIO | A migration checked stage by stage against the original, so nobody has to say on faith that nothing was lost. |
| CFO | The running cost of a system kept only as an archive comes to an end. |
| Medical head | Past and present records sit in one place, so a patient’s story is not split across two screens. |
| Risk and compliance | A record of what was moved, what was left and why, to show when asked. |
The cases in this article, and what IOanyT does about that kind of problem:
| The case | What IOanyT does |
|---|---|
| At one large health record supplier, an attacker reached old migration servers that had not yet been moved. | Our part is narrower than this case, and we do not work on packaged health record products or secure servers. For an organisation’s own applications, we stage the move off the old system so its team can switch the old server off. |
| On 17 July 2026 the National Medical Commission published lists of medical colleges, including colleges “still not using ABDM-enabled HMIS software”. | Our assessment shows which application and which old data stand in the way, and what moving them would take. Meeting the direction is the college’s own work. |
IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. The old records can stop being the reason the old system stays, and start being what the new work is built on.
Sources
- A vendor's survey, 2025
- Microsoft, SQL Server 2012
- Microsoft, SQL Server 2016
- Vendor-written article in trade press, 2026
- Medical Dialogues, 18 July 2026
- PIB backgrounder, Ayushman Bharat Digital Mission, 6 July 2026
In this issue
Data locked in old formats
Research note 1
Hospitals Keep Every Old Record. What Goes Missing Is What the Records Mean.
Old hospital records are kept, but their meaning goes out of reach. What the public record shows, why it happens, four ways forward and a benchmark.
Research note 3
Data a New Tool Cannot Read Is Not Ready. Here Is the Benchmark for Ready.
A new reporting or AI tool sees only the years it can reach. The benchmark we would set before old hospital data goes to any new tool, and the path.
Issue study
When the Old System Is the Only Way Into the Archive
Hospital records only an old system can read: what the thin public record shows, what digital health now rewards, the options and our benchmark.
More from Healthcare
Harm to patients when systems go down
How Much of What Care Rests On Have You Mapped? Four Measures, Now and Where They Should Be.
Dependence on an outside suppliers systems
How Much of Your Own System Do You Hold? Four Measures, Now and Where They Should Be.
Replacement is costly and risky