Locum Doctor EMR Access in Nigeria: Named Logins Across Clinics

Weekend cover is how many Nigerian hospitals stay open. The failure mode is not “we could not find a locum.” It is the consultant’s password on a sticky note, a locum who can still open charts on Monday, or two sites sharing one login. Locum doctor EMR access should mean a named staff account, a role that can consult, and a deactivate action that removes dashboard access when the block ends.

This guide is for medical directors, clinic administrators, and superintendents buying EMR or HMS in Nigeria. Pair it with multi-location hospital software, who opened the chart, and staff handover on night duty. Score locum access on a named person, not a slide titled “workforce mobility.”

What is locum doctor EMR access in a Nigerian hospital?

In procurement language, locum access is revocable membership of this clinic’s staff table, not a roaming national login.

At minimum you should be able to:

• Invite a named clinician by email, with a real role (usually doctor; dentist or optometrist when that is the cover).
• Let them log in as themselves. SOAP notes, prescriptions, and chart opens carry that account, not “Dr Shared.”
• Give the minimum role. An OPD locum should consult and prescribe. They should not invite staff, change tariffs, or sit in the owner seat.
• Deactivate the row when the block ends, without deleting what they already wrote.
• Keep Clinic A’s patients out of Clinic B. A locum at two independent hospitals is two memberships, not one mega-chart.

Buyers mash four different products into the phrase “locum EMR”:

1. A named doctor account at this clinic. Invite, accept, work, deactivate. This is the DawaHQ public claim.
2. A location label inside one hospital group. Staff can be assigned a location_id when that clinic has two or more sites. That is not a second hospital.
3. A header clinic-switcher so one person flips between tenants in one session. DawaHQ does not ship that UI.
4. A locum marketplace or MDCN licence checker. Not a product. Practising certificates stay with the Medical Director and the clinician.

If a vendor says “we do locums,” ask which of those four they just opened. Then make them invite a test doctor, chart as that login, and deactivate the row before you leave the room.

DawaHQ treats locums as ordinary staff on hospital / general practice: Team and Roles, email invite, assignable role. There is no separate locum product role. Do not buy a “locum module” that cannot show the same SOAP, invoice, and patient-access audit trail as your permanent doctors.

Why do shared consultant logins fail locum coverage?

Administrators already know the Saturday night pattern. Vendors still demo owner accounts.

Shared passwords destroy attribution. When a prescription is queried, you cannot say which human wrote it. Night locums and weekend dentists should never inherit the consultant’s credentials. MDCN clinical responsibility stays with the person who treated the patient.

Named accounts are this email, this role, this clinic. DawaHQ invites go out by email. The invitation link expires in seven days if unused. Acceptance creates the staff member’s own login. Owner and clinic admin can deactivate or reactivate from Team and Roles. Deactivation sets the row inactive. Dashboard access ends. Notes they already signed stay on the chart. That is the revoke to demand. DawaHQ does not auto-expire tenure at 08:00 Monday.

Role minimums: a DawaHQ doctor can consult, prescribe, see the queue, request labs, and view patients. They cannot manage staff or settings. Do not invite a locum as clinic admin “so they can see everything.” Dental cover needs dentist; eye cover needs optometrist. Specialty modules still have to be on for that clinic.

Locums count as real staff seats against the plan cap. Invite increments the count; deactivate decrements it. Budget weekend density, then book a demo if the quote must include it.

Shared ward tablets fail the audit-trail question on Monday. Named locum logins are how you survive that question.

How should a locum get access to more than one clinic?

This is where “multi-clinic” in the search query splits. Treat the two geometries as different products.

Two sites, one hospital brand (one tenant). Flagship and satellite share one clinic identity. DawaHQ can assign a staff member to a location when that clinic has two or more sites. The label helps rostering. It is not a “need-to-know only this building” ACL. Clinical boards are clinic-wide for roles that may use that module. Bed-limit enforcement by location is not something to buy from a slide. See the multi-location scorecard.

Two independent hospitals (two tenants). Friday at Clinic A and Sunday at Clinic B means two staff rows, two roles, two deactivates. Data stays clinic-scoped. A user may have more than one staff row without breaking lookups. That is tenant hygiene, not a clinic picker in the header. Session clinic resolution uses an active staff row. If two memberships are active, do not assume the session picked the hospital you meant. Confirm it in the demo. Do not demo “flip between hospitals” unless the vendor shows that control.

Invite vs existing email. Clinic-owner invite-accept is built for a new login on that invitation email. An already registered address will not silently attach a second hospital. Linking an existing user onto another clinic’s staff row is an operations/admin repair, not self-serve locum SSO. Ask for that path in the demo.

Regional manager is not a locum. DawaHQ’s regional manager flag is platform oversight (assigned regions, clinic drill-down). It is not how Hospital A grants weekend OPD cover.

What should locum EMR software record and revoke?

Ask for fields administrators already fight over on WhatsApp.

| Field | Why it matters | |-------|----------------| | Named email login | Stops “the locum used Dr Ade’s phone” | | Assignable clinical role | Doctor vs dentist vs nurse; not owner | | Invite + seven-day link expiry | Stops stale links living in inboxes | | Deactivate / reactivate | Block ends Friday; access must end | | Staff activity log | Who invited, who deactivated | | Chart attribution | SOAP and prescriptions under that user | | Patient-access rows | Who opened which patient, in which role | | Clinic scope | Clinic A must not browse Clinic B | | Optional location label | Group sites, not a second tenant |

Useful extras: specialisation, consultation fee, and slot length on doctor invite; optional weekday availability for booking; staff chat when that core module is on. Registration number fields exist on the staff API. Team and Roles does not run an MDCN licence check. Do not buy “we verify practising certificates.”

Do not buy a “time-bound locum SKU,” auto-off at end of shift, or “one login for every hospital” unless those screens are in the demo. DawaHQ’s revoke is owner/admin deactivate. Invitation expiry is the invite link, not the contract.

Prefer NDPA-oriented consent logging and patient-access audit trails. Locum access should be intentional and clinic-scoped. We do not sell “NDPA certified,” “NDHI ready,” or a national locum directory.

Does a locum see every patient in the hospital?

Usually yes, inside that clinic, for a clinical role. That surprises buyers who wanted assignment-only ACL.

DawaHQ doctors (and other clinical roles allowed on a module) see the clinic-wide queue, patient list, and boards for modules that clinic has enabled. Capabilities still block a cashier from ICU notes. They do not hide Mrs A from a locum doctor because she “belongs to Consultant B.” Coverage and emergency takeover are the design. There is no break-glass product: clinic-wide clinical read is the default for those roles.

What locums must not see:

• Another hospital’s charts. Tenant isolation, not a courtesy filter.
• Owner settings and staff invite. Wrong role.
• HMO national portals. DawaHQ ships HMO claim workflows inside the clinic. That is not NHIA e-submit, and a locum login is not an NHIA integration.
• Raw portal analyser dumps. The patient portal is for patients. Locums work in the staff EMR.

If your governance policy requires “only my assigned ward,” say so in the demo script and score the vendor honestly. Do not pretend a clinic-wide doctor role is need-to-know ACL.

What should we test in a locum demo?

Bring the operations lead who actually finds weekend cover, not only HQ IT.

1. Invite a test doctor by email. Show the role list. Refuse owner.
2. Accept the invite on a second browser. Confirm the locum cannot open Team and Roles.
3. Write a SOAP and a prescription as that login. Refresh. The author is the locum, not the owner.
4. Open a named patient. Show a patient-access row with that user and role. Then show Reports audit as a different log (staff activity).
5. Deactivate the row. Confirm the locum cannot enter the dashboard. Confirm the SOAP is still on the chart.
6. If you are a group: assign a location on a two-site clinic. That is not a second independent hospital.
7. Ask for the clinic switcher. If there is none, write that down. Cross-tenant locums are two memberships.
8. Ask how an already registered email joins a second hospital. Score a “sign up again” answer as a process gap.

Offline support for key workflows is a separate demo (offline hospital software). Do not assume a locum on flaky LTE has a full offline EMR. Optional AI notes are not the locum’s clinical judgement.

The Medical Director still owns who may treat patients this weekend. Software stores membership and the trail. It does not replace credentialing, indemnity, or a handover that names unstable patients (night-duty handover). Do not buy “AI locum” or “automatic privileging.” Dental or eye cover needs the specialty surfaces that ship (dental, eye clinic) with those /solutions/* modules enabled. A general doctor role will not grow FDI charts by magic.

What to do next

List this month’s locum shifts: who covered, which login they used, and whether that login is still live. If the answer is a shared password or an account nobody deactivated, the EMR is not the locum product yet.

Then book a demo or request access. Walk one invite, one SOAP, one deactivate, and one patient-access row on the same morning. Explore HMS for Nigeria, EMR for Nigeria, and the hospital solution. If the product cannot name the locum on the note and kill the login when the block ends, it will not help when the question is asked in writing.