Patient Portal for Nigerian Hospitals: What Patients Can Do Online

Procurement conversations in Nigerian hospitals still jump from “we need an HMS” to “can patients see results on their phone?” Those are different questions. A patient portal is the patient-facing slice of the same record: login, appointments, selected results, invoices, and prescriptions. It is not a second EMR, and it is not a native app store product.

This guide is for medical directors, administrators, and front-desk leads evaluating a hospital patient portal in Nigeria. Use it as a demo script. Pair it with the clinic software buyer’s guide and the EMR clinic checklist.

What is a hospital patient portal in Nigeria?

A patient portal is a clinic-branded web page patients open on a phone browser. They prove identity, then see a short list of actions the hospital has chosen to expose. In a competent hospital solution, the portal reads the same patient, appointment, lab, invoice, and prescription tables staff already use. It does not invent a parallel chart.

Typical surfaces (when the clinic enables them):

• Next appointment and a booking form
• Completed laboratory requests the facility is willing to show
• Invoice history, outstanding balance, and downloadable receipts
• Selected prescriptions the clinic chooses to expose (typically items already at the dispensary)
• A short health summary (allergies, listed conditions, current medications) when those fields exist

What it is not: a video consult product, a radiology PACS viewer, a full numeric lab analyser printout, or a replacement for the OPD queue. If a vendor demo starts with “download our app,” ask whether the same journeys work in the mobile browser. Nigerian patients already carry WhatsApp; they will not install a fifth hospital icon.

How do patients log in without creating another password?

Password portals fail in this market. Patients forget them, reception resets them, and shared family phones leak access. Prefer a one-time code (OTP) sent to the phone number already on the registration card.

A defensible login path looks like this:

1. Patient enters the clinic’s portal URL (or a QR on the receipt).
2. They type the phone number on file.
3. The clinic’s chosen channel delivers a six-digit code (SMS, WhatsApp, or SMS then WhatsApp fallback).
4. The session is a time-bounded cookie, not a forever password.

Ask the vendor to show what happens when the number is not on file, when the code expires, and when two people in a household share one line. Those edges are where privacy incidents start. Prefer vendors who write OTP and portal events to a clinic-scoped table and can show a working list or export. An empty “Recent Activity” tile is not an audit control.

Do not treat OTP as “NDPA certified.” It is an access-control pattern. The hospital remains the data controller. See patient consent in the EMR for the registration-side controls that should already exist before you open a portal.

Can patients book appointments online without a mobile app?

Yes, if the clinic turns booking on. A useful portal booking form captures date, time, and visit type (general, follow-up, specialist, lab, procedure) and writes into the same appointments list reception already manages. Patients should also see upcoming and past visits without calling the front desk.

HMO patients need a second pass in the same form: select the panel and, where policy requires, an enrollee identifier. That is not “NHIA connected.” It is HMO claim workflow hygiene so the visit is tagged before the doctor starts. Demo this against a real panel tariff, then walk the same visit through HMO claims.

Limits you should expect (and prefer):

• Slots still need clinic rules; a portal is not an unbounded public calendar
• Specialist routing may land as a general consultation type until a clerk assigns the clinician
• Same-day walk-ins still belong on the live queue, not only in the portal

Online booking reduces phone congestion. It does not remove the need for a visible departmental queue. That distinction is how you cut wait times without pretending the waiting room vanished.

What lab results should a portal show?

Release only completed requests the clinician is willing to share, and label them as ready. Showing test name, dates, ordering doctor, and a short report note is useful. Dumping raw analyser values and reference ranges into a phone without counselling is a clinical-safety problem, not a feature.

Medical Director bar: a portal is a notification and continuity surface. Interpretation stays with the clinician. If a vendor boasts “full lab graphing for patients,” ask who explains a critical potassium at 21:00 on a Sunday.

Also confirm:

• Pending and cancelled requests stay hidden
• Radiology images are out of scope unless you have a dedicated viewer and a reporting workflow
• Abnormal-value conversations happen at the next visit or a documented call, not as unexplained red numbers

The EMR layer should already flag abnormal values for staff. The portal should not try to be a second laboratory information system.

Can patients pay hospital bills from the portal?

Ask this in the demo and believe the billing screen, not the homepage slogan.

What a responsible portal can ship today (and what DawaHQ’s portal screen actually shows):

• Outstanding balance in Naira
• Invoice list with paid / partial / unpaid status
• Receipt download for settled invoices
• Clear copy that settlement still happens at the cashier or by a clinic-initiated payment path

What you should not assume until you see it work end to end: card or transfer checkout inside the portal, automatic Paystack capture from the patient phone, or “pay bills in one tap.” If the billing page says contact the clinic, write that into the RFP as a known gap. Cashier discipline still lives on the hospital billing and HMO path.

Honesty here protects finance. Patients who think they paid online when they only viewed an invoice create night-duty arguments at the gate.

How should administrators enable and govern a portal?

Treat the portal as a module you switch on per clinic, not a default public website. Governance checklist:

| Control | Why it matters | |---------|----------------| | Master enable flag | Dark until registration data quality is acceptable | | Feature toggles | Appointments, results, billing, prescriptions independently | | Branding | Clinic name, logo, colour so patients know they are not on a phishing clone | | OTP channel | Match the SMS or WhatsApp capability you actually operate | | Staff roles | Only owners and clinic admins change portal settings | | Session logging | Events written server-side; demand a working list or export, not an empty placeholder tile |

A dental-only site and a multi-ward hospital should not inherit the same feature mix. Multi-location groups need one patient identity story first (multi-location HMS); a portal on the wrong slug is worse than no portal.

WhatsApp reminder preferences on a profile page are not the same as a live notification programme. Messaging add-ons (clinic-owned WhatsApp or SMS) are configured separately. Do not sell “automated WhatsApp hospital” from a checkbox patients can tick.

What NDPA questions belong in the demo?

Trust & Risk vetoes slogans. Walk this script:

1. Show NDPA-oriented consent logging at registration before you open portal access.
2. Show unique staff logins and a patient-access audit trail for a named chart.
3. Show portal OTP and session expiry.
4. Ask who can query portal session or activity rows, and for how long they are retained. An empty “Recent Activity” tile is not evidence.
5. Refuse “NDPA certified,” “fully NDPA compliant,” and “national EMR ready” language.

The hospital still owns NDPC-facing duties. Software can make those duties easier to evidence. It cannot file them for you. Background: NDPC registration.

How a portal reduces front-desk pressure

Front desks in Lagos, Abuja, and secondary cities spend mornings on three call types: “is my result ready?”, “what time is my card?”, and “how much do I still owe?” A portal that answers those three (with the limits above) frees clerks for the patients standing in front of them.

It will not:

• Replace triage or ESI in the emergency department
• Discharge an inpatient
• Reconcile an HMO rejection
• Fix a duplicate hospital number

If those are your real pains, start with the HMS scorecard, not a QR code on the wall.

Buyer scorecard (print this)

| Question | Pass | |----------|------| | Clinic-branded mobile web, no mandatory app | Demo on a phone | | OTP to the registered number | Live send on a test patient | | Booking writes the staff appointments list | Reception sees it immediately | | HMO fields optional but available | Panel + enrollee captured | | Results = completed only, no raw analyser dump | Copy matches clinical policy | | Invoices and receipts visible | Online pay not assumed | | Feature toggles (appointments, results, billing, prescriptions) | Admin screen, not a slide | | Precise privacy language | No certification stickers |

Score vendors on the same patient. Do not award points for a consumer wellness app bolted on the side.

Competitive noise to ignore

Directory listicles will promise “patient apps” and “AI health companions.” Ask whether the companion writes into your legal record and your cashier queue. If it does not, it is a marketing site. DawaHQ’s portal is the patient window on the same 30+ module hospital OS: OPD, billing, lab, pharmacy, and HMO on one identifier. Evaluate it with the same pencil you use on everyone else.

What to do next

Pick ten active patients with clean phone numbers. Enable the portal on a staging or pilot clinic first. Measure: bookings that arrived without a phone call, result questions that stopped at reception, and invoice disputes that vanished because the receipt was downloadable.

When you are ready to walk OTP login, booking, completed results, and invoice visibility on DawaHQ, book a demo or request access. Sales-led onboarding, not a self-serve trial that skips clinic configuration.