Skip to main content
This section is for the NduMed platform operators who run the service for many hospitals. Each hospital (a “tenant”) has its own isolated data and its own address, <slug>.<base domain>. Operators manage hospitals in the operator console or through the platform API.

Sign in to the console

Open /platform/console/login and sign in with the operator console credentials configured for your deployment. If no console credentials are configured, the console cannot be signed into.

Onboard a hospital

1

Open Onboard a hospital

Enter the hospital’s slug (lowercase letters and digits, starting with a letter, 3 to 30 characters; NduMed checks it is free as you type), name, timezone, currency and the first administrator’s name and email.
2

Choose whether to email the invitation

Email invite is on by default. Turn it off to copy the link and send it yourself.
3

Create

NduMed creates the hospital’s data store, seeds reference data (roles, departments, diagnosis codes, price list items) and issues a 72-hour invitation for the first administrator.
The hospital is available at its address straight away. The administrator then follows First administrator setup.

Manage a hospital

The hospitals list can be searched and filtered by status. Each hospital’s page shows usage counts (patients, encounters, admissions, active users) and these actions:
  • Re-issue invitation: emails a new first-administrator link, or shows it to copy. The old link stops working.
  • Modules: switch Lab, Pharmacy, Wards, Billing, Reporting and AI scribe on or off, or use Enable all modules / Disable all modules. All except AI scribe are on for new hospitals. A module that is off disappears from the hospital’s menus and its pages are unavailable.
  • Suspend hospital, Reactivate hospital, Archive hospital.
  • Sync ICD-11 codes: refreshes the ICD-11 diagnosis list in every hospital from the WHO service, when configured.

Hospital status

Archiving, and reactivating an archived hospital, require you to type the hospital’s slug to confirm. Read it carefully: this is what stops the right action being applied to the wrong hospital.
Status changes take effect on the very next request. Repeating a change that is already in effect does nothing. Every change is recorded with who made it, when, and the reason.
Renaming a hospital, and exporting or permanently deleting an archived hospital’s data, are not available yet.