Before You Buy Another Hospital Information System, Ask This Question: Who Really Owns Your Health Data?

CDR

Every few years, healthcare organizations invest millions of naira in new hospital software. The new system promises faster registration, electronic prescriptions, better reporting and happier clinicians. For a while, everything looks promising. Then, a few years later, another procurement begins. The software changes, vendor changes, technology changes but patient historical data is stuck in legacy systems. Unfortunately, this happens more often than many healthcare leaders realize.

Whether you manage a teaching hospital, a private hospital, a State Ministry of Health or an NGO supporting hundreds of facilities, you have probably experienced one or more of the following situations.

Story 1: “Our old vendor still has our patient records.”

A Federal Teaching Hospital decides to replace its Hospital Information System after nearly ten years. The hospital has grown. Clinical services have expanded. Management wants a modern Electronic Health Record (EHR). A new vendor wins the contract. The implementation goes well. Then reality sets in.

The hospital discovers that years of patient history are trapped inside the old system.

The previous vendor charges additional fees to migrate the data. Some information cannot be exported at all. Doctors suddenly find that patients who have attended the hospital for years appear to have no previous history in the new system. Patients are asked the same questions again. Old laboratory trends are unavailable. Previous treatment decisions are difficult to review. The hospital has invested in a better system — but lost continuity of care.

A Health Data Platform (HDP) ensures that every clinical system sends patient information into a central repository owned by the healthcare organization — not the software vendor. The hospital can change vendors whenever necessary without leaving decades of patient history behind.

Story 2: “Our laboratory has the results, but the doctor cannot see them.”

A State Specialist Hospital has invested heavily in technology. The laboratory has its own Laboratory Information System. Radiology uses a PACS. The pharmacy uses dispensing software. Dentists use Open Dental. Finance uses a billing application. The hospital recently introduced telemedicine. Every department is proud of its system.

Yet every morning, the same frustrations continue, Doctors call the laboratory asking whether results are ready. Data clerks manually copy laboratory results into the Electronic Health Record. Patients carry printed radiology reports — or CDs — from one building to another because the consulting doctor cannot access the images electronically. The same patient demographic information is entered into four different systems.

Everyone is working. Nobody is working together (Fragmented data systems that are not interoperable).

A Health Data Platform (HDP) connects these systems together. Each department continues using the software best suited for its work, while sharing information through a common clinical data (HDP) repository. Information shared to the HDP is automatically available to all other systems. The doctor no longer searches five different systems before treating a patient.

Story 3: “We support over 300 facilities, yet reporting takes weeks.”

Imagine an NGO implementing an HIV programme across more than 300 health facilities, A State Ministry of Health coordinating services across multiple Local Government Areas. Every facility submits reports. But not every facility uses the same software. Some use OpenMRS, others LAMIS or Facility custom EHR solutions, Some still rely partly on paper. Every reporting cycle becomes a familiar routine.

Teams collect spreadsheets.

Data analysts clean duplicate records.

Different facilities use different names for the same clinical concepts.

Programme staff spend days reconciling numbers before they can answer simple questions. How many patients started treatment this month in our state? Which facilities are experiencing stock-outs? Which Local Government Areas require additional support? By the time reports are ready, managers are already preparing for the next reporting cycle. A Health Data Platform receives information from every participating system, standardizes terminology, validates data quality and creates a single trusted source for dashboards, programme monitoring and decision-making. Instead of spending time preparing data, organizations spend more time improving healthcare.

Story 4: “The Commissioner asks a simple question — but nobody has the answer.”

A Commissioner for Health wants to know:

“How many pregnant women received antenatal care across our state last month?”

“How many diabetic patients are currently receiving treatment?”

“Which Local Government Areas have the highest maternal mortality?”

The information exists. Some of it is in teaching hospitals. Some is in General Hospitals. Some is in Primary Healthcare Centres. Some is in disease programmes. Some is in laboratory systems. Some is in community health programmes. Unfortunately, it is scattered across dozens of disconnected databases. Different teams begin making phone calls. Facilities are asked to resend reports. Excel files arrive from different departments. Days — or even weeks — pass before management receives an answer. Sometimes, different departments produce different numbers for the same indicator. Decision-making slows because the data is fragmented.

A State or National Health Data Platform continuously receives information from hospitals, laboratories, community health programmes and other health information systems.

Decision makers gain one trusted source for planning, budgeting, disease surveillance, research and policy development.

Story 5: “Accreditation is next week. Everyone is searching for data.”

Many healthcare managers know this feeling. A hospital is preparing for accreditation. An NHIA assessment is approaching. A donor verification visit has been scheduled. Researchers request historical patient information. Immediately, different departments begin searching for data. The Quality Assurance team requests reports from Health Records. Finance sends one set of numbers. The laboratory sends another. Programme teams produce Excel spreadsheets. IT extracts data from multiple applications. Meetings are held to explain why different reports show different figures. Staff who should be caring for patients spend days searching for information instead. There is no single trusted source of truth.

A Health Data Platform continuously consolidates information from across the organization, making trusted reports available whenever they are needed. Accreditation, audits, research and programme reporting become much faster because everyone is working from the same data.

The Pattern Behind Every Story

These stories come from different parts of the healthcare system.

A Teaching Hospital.

A Private Hospital.

A State Ministry of Health.

An NGO.

A National Programme.

Yet they all share the same underlying problem. Healthcare organizations have invested heavily in software applications. Very few have invested in managing their health data as a long-term organizational asset. Software applications will come and go. Vendors will change. Technology will evolve. Healthcare data, however, should remain accessible for the lifetime of the patient — and often beyond. That requires separating the organization’s clinical data from the applications that create it.

This is the role of a Health Data Platform, also known as a Clinical Data Repository (CDR).

Rather than replacing existing systems, it allows them to work together while ensuring that the healthcare organization — not individual software vendors — owns, controls and benefits from its most valuable digital asset: its health data.

References

• Arcadia.io. (2026). Healthcare data platform considerations + options in 2026. Arcadia Resources. https://arcadia.io/resources/healthcare-data-platform
• Better Care. (2025). Transform healthcare delivery with Digital Health Platforms. Better Care Solutions. https://www.better.care/better-platform/
• G7 Health Ministers. (2021). G7 Open standards and Interoperability final report. G7 Research Group, University of Toronto. https://g7.utoronto.ca/healthmins/G7-Open-Standards-and-Interoperability-Final-Report.pdf
• HiGHmed. (2024). Introduction to openEHR: Future-proofing health data sharing. HiGHmed Consortium Ecosystem. https://www.highmed.org/en/en/introduction-openehr
• HISP Centre. (2025). DHIS2: Supporting Local Health Information Systems Worldwide. University of Oslo. https://dhis2.org/
• Medblocks. (2025). What is openEHR and why does healthcare need it? Medblocks Architecture Blog. https://medblocks.com/blog/what-is-openehr-and-why-healthcare-needs-it
• openEHR Foundation. (2025). We’re open: Vendor-neutral platforms for health records. openEHR International. https://openehr.org/were-open-for/