Every LIS migration produces two types of report. The first is the technical report: systems integrated, data exported, operations stabilized on schedule. The second is rarely formalized — because no one commissions it. It would answer a different question: of the results that existed in the previous system, how many are clinically comparable to results produced by the new one? In most cases, the answer is unknown. And that's a problem.
The Brazilian diagnostics industry is moving through an accelerated consolidation cycle. In the North American market alone — a leading indicator for trends that typically reach Brazil two to three years later — the diagnostics sector recorded more than USD 64 billion across 445 transactions through mid-2025.¹ Every acquisition brings an inevitable infrastructure decision: which LIS survives, which gets decommissioned, and what happens to the data in every system that goes offline. That decision is almost always treated as an IT project. It is rarely treated for what it also is: a clinical continuity project.
ANVISA, through RDC No. 302/2005, requires traceability and documented quality control in clinical laboratories.² The regulation doesn't define what happens to that traceability when the system storing it is replaced. In that regulatory silence, each laboratory resolves the problem as best it can — and the most common solution is exporting reports in static format, which preserves the document but destroys the semantic equivalence necessary for any subsequent clinical or analytical use. The result is a category of loss that appears in no migration report: data that exists, but isn't usable.
LIS replacements: more frequent than the industry acknowledges
The decision to change Laboratory Information Systems is, in theory, driven by progress: a more modern system, better integrated, with improved technical support or superior analytical capabilities. In practice, it happens more often than the industry typically acknowledges. Laboratories that grow through acquisition may operate three, four, or five distinct LIS systems simultaneously — and eventually need to consolidate. Groups that sign contracts with large hospitals are required to adapt their system to the client's standard. Vendors that end support for legacy versions force upgrades.
In the Brazilian market, with more than 23,500 registered clinical laboratories and a sector in rapid consolidation, system turnover is structurally high.³ In networks that grow through acquisition — the dominant model among major national diagnostic groups — LIS migration is not an isolated event but a near-continuous process, with some unit of the network always in transition. What rarely appears in any migration scope is a simple but critical question: what happens to the data that exists in the system being replaced?
What a LIS migration actually migrates — and what it doesn't
The technical migration of a LIS typically involves transferring patient registrations, test tables, equipment configurations, and in many cases a subset of historical reports in exportable format. What is rarely migrated with semantic fidelity are the relationships that give those data clinical value: the equivalence between test nomenclature in the old system and the new, the correspondence between the reference ranges used by each platform, and the traceability of analytical methodology over time.
A concrete example: serum creatinine may have been recorded as "Creatinine" in the previous LIS and "Serum CREA" in the new system. For a human who knows both systems, the equivalence is obvious. For any algorithm, automated report, or longitudinal analytics platform that depends on exact field identity, they are two distinct tests. The time series that should show the evolution of a patient's renal function over five years is interrupted at the moment of migration — not from data loss, but from semantic equivalence loss.
The problem multiplies when reference ranges change between systems. A hemoglobin result of 12.5 g/dL may have been classified as within normal range by the previous LIS and flagged as slightly below normal by the new system, if the lower reference limits adopted by each platform differ. The value is identical. The clinical interpretation the system automatically produces is different. Differences in reference intervals between laboratories and systems are documented in the literature as a source of diagnostic discrepancies in up to 25% of cases for certain tests.
The clinical cost of the broken history
Longitudinal continuity of laboratory data is not a clinical luxury. It is the necessary condition for chronic patient monitoring to function as it should. Programs for managing diabetes, renal insufficiency, autoimmune diseases, and hematological disorders depend on serial biomarker analysis over months and years. When that series is interrupted by a system migration, the physician loses the context that transforms an isolated value into clinically relevant information.
The same fasting glucose of 126 mg/dL carries completely different meanings depending on the history preceding it: in a patient whose prior readings were consistently below 100 mg/dL, it signals a change requiring immediate investigation; in another whose readings oscillated between 120 and 135 mg/dL over two years, it is stability. Without comparable access to pre-migration history, that distinction must be reconstructed manually — or simply isn't made.
International patient safety guidelines, such as those published by the Joint Commission International, emphasize that longitudinal traceability of laboratory data is a necessary condition for early identification of clinical deterioration.⁵ That traceability requires, by definition, that data produced before and after any system change be clinically comparable.
The impact extends beyond individual care. Population health programs, epidemiological analyses, and predictive models built on historical data lose validity when the data foundation is interrupted by an unharmonized migration. Research indicates that only 18% of laboratories operate in a truly integrated manner with electronic health records, pharmacies, and surveillance systems.⁶ Migrations that don't address semantic continuity widen that gap — creating discontinuities that invalidate years of data accumulation precisely when the institution would most benefit from using them.
The flawed premise at the center of the problem
Most LIS migrations are conducted from an implicit premise that is rarely questioned: that the patient's clinical history belongs to the laboratory information system. If the LIS changes, the history changes with it — or gets left behind.
This premise is operationally convenient but clinically incorrect. A patient's laboratory history is not the property of the system that recorded it. It is a clinical asset that must exist independently of any technology platform — comparable, traceable, and accessible regardless of how many migrations the laboratory has undergone.
The distinction points to the right place where the problem must be solved. The solution is not to conduct migrations "more carefully" or to invest in data mapping projects at each system change. It is to separate the semantic data management layer from the laboratory's operational management layer. When clinical equivalence between tests, validated reference ranges, and the semantic identity of each biomarker are managed in a LIS-independent layer, they survive any migration — because they never depended on the system being replaced.
Data that outlasts the system
This architecture has a name: clinical and semantic harmonization of laboratory data. It is the layer that ensures "Creatinine" in LIS A and "Serum CREA" in LIS B are recognized as the same test, with the same clinical identity, mapped to the same LOINC code, with documented equivalent reference ranges.⁷ When that equivalence is persisted in an independent layer, it isn't lost in a migration. The new LIS inherits the equivalence already established. Pre-migration history exists in a comparable and accessible form.
For diagnostic groups that grow through acquisition — and therefore face LIS migrations recurrently — this layer stops being a one-off project and becomes permanent strategic infrastructure. Each new LIS integrated into the network doesn't create a semantic rupture: it contributes data to a unified timeline that transcends any individual platform.
The value of this continuity extends beyond clinical care. Contracts with hospitals and insurers requiring longitudinal population analytics, quality audits depending on historical result traceability, and AI initiatives that need consistent time series to train models — all presuppose that today's data is comparable to data from five years ago. A LIS migration without semantic harmonization creates a gap in that continuity that compromises every one of these uses.
This is the context in which OpenHealth Technologies operates. The platform functions as the clinical and semantic harmonization layer that exists independently of the LIS — and therefore survives any system change. By automatically correlating multiple data streams with rigorously validated logical layers of laboratory tests, the solution ensures that results produced in different systems, in different periods, are clinically equivalent and longitudinally comparable. For expanding diagnostic groups, each LIS migration ceases to be a rupture in patients' clinical histories and becomes, simply, an operational platform upgrade — with no consequences for the continuity of the data that actually matters.
Learn how your laboratory can transform data into a new revenue stream.