Digitizing Hospital Records in Nigeria: Progress and Pitfalls

The Push Toward Digitization

Nigerian hospitals have faced mounting pressure to digitize patient records over the past five years. The National Health Insurance Scheme (NHIS) increasingly requires electronic documentation for claims processing. State and federal teaching hospitals in Lagos, Abuja, and Enugu have invested in electronic health record (EHR) systems, driven partly by accreditation requirements and patient demand in urban centers. A tertiary facility in Yaba might handle 2,000 outpatient visits weekly—managing those volumes on paper is operationally broken. Private hospitals and diagnostic centers, competing for middle-class patients willing to pay out-of-pocket, have moved faster; chains like Reddington and Nnamdi Azikiwe Specialist Hospital adopted systems earlier than public counterparts. The business case appears straightforward: reduce staff time spent retrieving files, improve clinical decision-making, and enable data-driven resource planning. Yet the reality across most of Nigeria's healthcare landscape remains fragmented and incomplete.

Where Digitization Is Actually Working

Success clusters around three scenarios. First, large private facilities in Abuja and Lagos with in-house IT teams have deployed vendor solutions—often customized versions of systems like OpenMRS or proprietary platforms built by regional health IT vendors. These hospitals manage integration with laboratory and pharmacy systems, maintain regular backups, and train staff systematically. A composite example: a 200-bed hospital in Ikoyi might employ two dedicated health IT staff, enforce password protocols, and audit access logs monthly. Second, public facilities that received government funding or donor backing—such as state-funded projects supported by development partners—implemented systems with ongoing technical support embedded in their grants. The Edo State Hospital Management Board's push to digitize primary health centers is one such example, where external technical teams built capacity locally. Third, specialist diagnostic chains offering imaging and pathology have standardized around PACS (Picture Archiving and Communication Systems) and LIS (Laboratory Information Systems) because these services inherently generate digital output—scans and test results. Integration with referring hospitals remains limited, but within their own walls, data flows cleanly.

Infrastructure Bottlenecks That Stall Projects

Power and connectivity are the primary culprits. Many secondary and tertiary hospitals in tier-2 cities like Ibadan, Kano, and Uyo experience daily power cuts lasting 4–6 hours. A hospital's EHR system becomes unusable when the internet drops—and in much of Nigeria, connectivity is unreliable even in cities. A mid-tier hospital in Maiduguri might have reasonable broadband during peak hours but face bandwidth throttling that makes uploading patient scans impractical. Battery backup and local server infrastructure are expensive; a complete offline-first system with syncing when connectivity returns costs roughly ₦15–40 million for a 100-bed facility, plus recurring maintenance. Many hospitals neither budget for this nor plan for it. Second, data centers suitable for healthcare are sparse outside Lagos and Abuja. Hospitals that cannot afford dedicated infrastructure often resort to cloud vendors without understanding data sovereignty requirements—the NDPA (which replaced NITDA's data protection mandate) lacks clear guidance on where health data must reside. Third, legacy systems don't communicate. A hospital's financial management software, pharmacy system, and new EHR are often islands. Building integrations requires custom API development or expensive middleware—costs that overtax already-strained IT budgets in public hospitals.

The Vendor and Regulatory Puzzle

Nigeria's health IT vendor ecosystem is immature and fragmented. There is no dominant local player; hospitals choose between a handful of regional vendors (some based in South Africa, Kenya, or Ghana), unvetted small startups, or expensive international solutions. Few vendors have formal security audits or compliance certifications meaningful to healthcare. NITDA's cybersecurity regulations exist but are not healthcare-specific, and the nascent NDPA has not published detailed guidance for patient data handling. This leaves hospital administrators uncertain about what compliance actually means, so they delay investment or make piecemeal purchases without a roadmap. Additionally, vendor lock-in is a real risk. A hospital might invest heavily in a system that includes custom workflows, only to discover the vendor lacks the resources to maintain or upgrade it. Several hospitals have experienced vendor abandonment after initial deployment. Public procurement rules, which should theoretically encourage competition, instead slow decision-making—a hospital seeking a formal tender might wait 18 months for budget approval, by which time technology requirements have shifted. Private hospitals move faster but often lack the scale to negotiate favorable terms with international vendors.

Adoption and Cultural Resistance

Even when infrastructure is sound and software is deployed, clinicians don't always adopt it. Doctors and nurses accustomed to paper workflows view EHRs as adding administrative burden, especially if the system is poorly designed or slow. A teaching hospital in Lagos that rolled out an EHR reported that senior consultants continued requesting paper summaries of patient notes because they didn't trust electronic speed or accessibility. Training is often inadequate—many hospitals conduct a single 2-3 hour training session and expect staff to operate the system proficiently. Night-shift staff, part-time personnel, and those with minimal computer literacy fall behind. High staff turnover in public hospitals means continuous onboarding pressure; by the time half a department is trained, the other half has moved on. Additionally, data quality suffers when staff are skeptical. If clinicians perceive the system as a compliance checkbox rather than a tool to improve patient care, they enter incomplete data, use placeholder notes, or maintain dual paper and digital records—defeating the purpose and creating liability. Changing this mindset requires visible buy-in from medical leadership and evidence that the system actually improves workflows—a slow process.

Interoperability: The Missing Link

Perhaps the most critical failure point is the lack of interoperability between hospitals and across care settings. A patient treated at a private diagnostic center in Lekki, then referred to a federal medical center in Lagos Island, cannot have their prior imaging or lab results transferred digitally. Each facility maintains separate records. This fragmentation increases clinical risk—duplicate tests, missed diagnoses, and medication errors—and wastes resources. Solving this requires standardized data formats (like HL7 or FHIR), agreed-upon identifiers (a national patient ID scheme, which Nigeria lacks), and secure data-sharing agreements. The Health Insurance Providers Association and CBN have discussed frameworks but not implemented them. State and federal health authorities lack the coordination structures to enforce interoperability standards. Without a mandate from above—backed by regulatory muscle—hospitals have little incentive to invest in bridges to competitors' systems. Some regional initiatives, such as the Lagos State Digital Health Program, are attempting to build local interoperability networks, but these remain limited in scope and largely unproven.

What Works: A Practical Path Forward

Hospitals succeeding with digitization typically follow a pragmatic sequence. They start with high-impact, manageable modules—pharmacy and laboratory—rather than attempting whole-system deployment. They invest in reliable power and connectivity before installing software. They secure executive sponsorship and dedicate staff to change management. They choose vendors willing to support implementation on-site and customize workflows around the software rather than the reverse. Most importantly, they treat digitization as a multi-year program with realistic budgets for infrastructure, training, and maintenance—not as a one-time IT project. For hospitals wrestling with legacy systems or planning first-time digitization, several options exist. Building custom solutions in-house, while expensive, gives full control but requires sustained IT capacity. Adopting proven open-source platforms like OpenMRS reduces licensing costs and avoids vendor lock-in but requires local technical expertise to implement and maintain. Partnering with implementation consultants experienced in the Nigerian healthcare context can compress timelines and avoid costly missteps, particularly in navigating infrastructure constraints and vendor evaluation. The most mature facilities are those that combine a realistic assessment of their current infrastructure, a phased implementation roadmap, and ongoing technical support—whether in-house or through external partners with healthcare domain knowledge.