Skip to main content
DawaHQ
Back to Blog
Clinical Documentationhospital referral EMR Nigeriainternal referral hospital softwaredepartment referral HMS

Hospital Referral EMR Nigeria: Internal Handoff vs Letter

An internal referral is a queue handoff, not a teaching-hospital letter. Here is what Nigerian hospital software should record, and what to test in a demo.

DawaHQ Clinical Team• Hospital Operations & Product9 min read

Monday in a multi-specialty clinic is a stack of “please see surgery,” “send to pharmacy,” and “write a letter for LUTH.” If those three requests share one Word template, the hospital has a handoff gap, not a stationery problem. Hospital referral EMR in a Nigerian EMR or HMS exists so the ask, the named clinician, and the next queue share one chart.

For medical directors, administrators, and OPD leads. Pair it with staff roles, discharge summaries, and who opened the chart. Score the referral on a named consultation that actually routes a patient. This is operational practice, not legal advice, and not an NHIA form catalogue.

What is an internal referral in a Nigerian hospital EMR?

An internal referral is a handoff inside the same facility: this doctor, this patient, this reason, to another department, a named specialist, or the pharmacy queue. The patient does not leave the hospital. The chart should not need to be photocopied.

Buyers mash four different documents into “referral software”:

  1. Internal specialist or department referral. OPD to surgery, paediatrics to physiotherapy, medical to mental health. Same clinic, next clinician.
  2. Internal pharmacy referral. The doctor is sending the patient to collect medication, not asking a consultant for an opinion.
  3. External referral letter. A focused ask to another facility (teaching hospital, specialist centre, reverse referral back to the GP).
  4. HMO / NHIA paper. Pre-auth, claim batch, or a statutory referral form the panel still wants stamped. Related money. Not the clinical handoff.

If a vendor says “we do referrals,” ask which of those they opened. Then make them create one from a saved consultation and show where the patient lands in the queue.

On DawaHQ this sits on the core consultations chart, not a separate SKU. From the consultation, Internal Referral opens the in-clinic handoff. Referral Letter opens the printable external letter. Do not buy one button that claims to do both.

How is an internal referral different from an external referral letter?

Staff already know the split. Vendors blur it.

Internal referral. Same clinic. Destination is a department, a named doctor, or pharmacy. Success is a visit on the receiving queue the same day, with the referring doctor’s name attached. On DawaHQ the types are specialist (named doctor), departmental (next available doctor queue), and pharmacy (pharmacist queue). Doctor-bound referrals skip nurse vitals triage. Pharmacy referrals wait in the pharmacy queue. Priority is routine, urgent, or emergency. Status starts pending.

External referral letter. Another facility. Success is a printable letter with reason, clinical summary, urgency, and a clinic-generated reference. The receiving hospital cannot open your chart from the letter. Print, stamp, and send remain the clinical act.

Related, not the same record: a discharge summary can name a transfer destination; a sick-leave certificate is unfit or fit for a period; an IPD dietitian tick is a care-plan checkbox; a settings “referral code” is a commercial signup, not a patient going to ENT.

If the demo shows only a letterhead PDF, you have not seen an internal referral. If it shows only a queue chip with no letter, you have not seen an external referral.

What should hospital software record on an internal referral?

Ask for fields staff already fight over on paper slips.

| Field | Why it matters | |-------|----------------| | Patient identity | Same chart on the receiving queue, not a duplicate folder | | Referring clinician | Named login, not a shared “Doctor” password. See locum access | | Type | Specialist, department, or pharmacy. Mixing these dumps opinions into the dispensary | | Destination | Department name, or a named doctor for specialist type | | Priority | Routine / urgent / emergency. Emergency should notify the receiving doctor | | Reason | Required clinical why. “See please” is not a reason | | Queue effect | A visit appears where the receiving staff actually work | | List | A clinic-wide list of what is still pending |

On DawaHQ the modal departments include Internal Medicine, Surgery, Obstetrics & Gynaecology, Paediatrics, Orthopaedics, Ophthalmology, ENT, Psychiatry / Mental Health, and Physiotherapy. Specialist selection loads doctor role staff (not clinic admin). Reason is required. Pharmacy hides the department list and sets destination to Pharmacy.

The /referrals board has Internal and External tabs. Internal rows show referring doctor, destination, reason, priority, status, and date. The list is clinic-scoped, last 20, consult-capability gated. The table currently shows a truncated patient id, not the full name: confirm the receiving doctor can still open the chart from the queue visit.

Do not expect, today: a click-through status machine on that board (status is stored; there is no staff PATCH to advance it), incoming referrals from other hospitals, digital chart sharing with LUTH, an NHIA e-referral portal, or a referral analytics dashboard.

Who may create a referral, and what does the queue actually do?

Software roles are not a practising licence.

Internal create and list (POST/GET /api/referrals/internal) require the consult capability. The default matrix gives consult to owner, clinic admin, doctor, dentist, optometrist, physiotherapist, and mental-health practitioner. Nurses, receptionists, cashiers, pharmacists, and laboratory staff do not. The API returns 403 without it. Staff-aware RLS keeps rows inside the clinic.

That gate is wider than “only the registered medical practitioner refers.” Clinic admin can consult in the product. A physiotherapist can consult on their module. Put a clinic SOP on top: the examining doctor writes specialist or department referrals; pharmacy type is for collection, not a consultant opinion.

After save the product writes the internal_referrals row (status: pending), creates a today’s visit (Africa/Lagos date), and, for a named specialist, an in-app notification (emergency labelled high). Doctor/department visits use queue_type=doctor and status=with_nurse so the patient skips a second vitals wait. Pharmacy visits wait on the pharmacist queue (GET /api/pharmacy/referral-queue when the pharmacy module is on; marking dispensed updates the visit). The sidebar Referrals item is on by default; it is not a billed add-on in ALL_CLINIC_MODULES.

External letters (POST /api/referrals) currently require view_patients, which is broader than consult. Do not treat that as an MDCN signing rule. Keep the letter path on the consultation. The form locks the referring doctor name from the signed-in user.

Does software send the patient chart to another hospital?

No.

An external letter is a document your clinic prints. The receiving facility gets paper, WhatsApp text, or whatever your SOP allows. They do not receive a live login to your EMR. “Secure patient record sharing with the receiving facility” is a different product (HIE, FHIR, NDHI). DawaHQ does not ship that, and we do not sell “NDHI compliant” or “national EMR.” See the HMS FAQ.

What the letter does include on DawaHQ: clinic name and address from signed-in metadata; patient name, date of birth, gender, patient code; facility and optional specialist type (free text); urgency; required reason; clinical summary auto-filled from the consultation (chief complaint, diagnosis, plan, vitals, drugs, notes) and editable before save; referring doctor name, locked; clinic code REF- plus six random digits (not an NHIA serial); browser print with an empty stamp box; optional WhatsApp text via wa.me. That text is staff-initiated. It is not official delivery, not the patient portal, and not a substitute for print plus stamp.

One saved letter per consultation. Re-issue from a new consultation if you must. No QR against a national register, no incoming accept/reject from the teaching hospital, no stored PDF vault.

Multi-location sister sites still need documented transfer plus MPI discipline. Internal referral here is same clinic, not automatic Site A to Site B chart push.

What about NHIA, HMO, and official referral forms?

Do not buy “NHIA-integrated referral.”

NHIA / NHIS. A clinic-generated REF- code is not an e-claims submit and not a published NHIA referral form number. We do not invent those numbers. See NHIA e-claims and HMO claim workflows. Pre-auth lives on the HMO module, not inside the Internal Referral modal.

MDCN. Referring is a clinical act. Software cannot look up the public register or print an NMA seal. Stamp the empty box.

NDPA. A WhatsApp summary with a patient name is a controller decision. Prefer NDPA-oriented consent logging and a patient-access audit trail. We do not sell “NDPA certified” or “fully NDPA compliant.” Staff DSAR JSON mentions referral free text on the patient row; it does not currently pack internal_referrals.

PCN / NAFDAC. Pharmacy-type internal referral is a queue, not a controlled-drug register.

What should you test in a hospital-referral demo?

Run this morning’s OPD, not a brochure.

  1. Open a named consultation as a doctor. Tap Internal Referral. Choose departmental, pick Surgery, save. Confirm a visit on the doctor queue without a second vitals wait.
  2. Repeat as specialist: pick a named doctor. Confirm the in-app notification and the same patient chart, not a duplicate.
  3. Repeat as pharmacy (module on). Confirm the pharmacist queue, not the OPD vitals line.
  4. Open /referrals Internal tab. Confirm the row and pending status. On DawaHQ today, treat the board as a list, not a closed-loop workflow.
  5. Tap Referral Letter. Confirm auto-filled summary, locked doctor name, REF- code, browser print, empty stamp box. Treat WhatsApp as staff message, not delivery.
  6. As a receptionist or cashier, confirm they cannot create an internal referral (403 or no consult path). Clinic admin and allied-health consult seats can hit the same API; write that into your SOP.
  7. Ask the vendor to show incoming referrals from another hospital’s EMR. If they cannot, do not let “receive referrals digitally” pass.
  8. Confirm the path: book a demo, request access, custom quote. No self-serve trial.

Bring the Medical Director and the OPD lead, not only IT.

How does DawaHQ support referrals today?

On clinics that run the hospital consultations module (core): Internal Referral (specialist, departmental, pharmacy) via consult-capability /api/referrals/internal; queue routing with referring doctor name; named-doctor notification; /referrals board; Referral Letter with locked issuer, REF- code, browser print, and WhatsApp text. Qualified wording: same-clinic handoff plus a printable external letter. Not an NHIA form, not a national HIE, not incoming e-referrals, not a closed-loop status machine, not “NDPA certified.”

Same HMS as HMO claim workflows. Pricing is sales-led from ₦25,000/month, then a scoped quote.

What to do next

Count last week’s paper slips: patients who sat in vitals twice after a “see surgery,” letters with no diagnosis, and WhatsApp photos of handwriting that the teaching hospital could not read.

Then book a demo or request access. Walk one departmental queue handoff, one named specialist, one pharmacy queue, and one printed letter. Explore HMS for Nigeria, EMR for Nigeria, and the hospital solution. If the product cannot show the examination and the next queue on the same patient, it will not help when the consultant asks why the patient is in their room.

Ready to modernise your clinic?

Join hundreds of Nigerian healthcare providers using DawaHQ to run smarter operations.

Book a Free Demo
Hospital Referral EMR Nigeria: Internal Handoff vs Letter | DawaHQ Blog