Skip to Content
CMSIntroduction

Introduction

What is an organisation?

An organisation is a clinic as a tenant of Medbot CMS: its own staff, its own locations, its own patients, and, crucially, its own Medplum server. Everything the CMS does happens inside exactly one organisation at a time.

Medbot CMS is multi-organisation. Any signed-in user can create an organisation (or ask Medbot to host one), add staff to it with roles, and run every clinic workflow (patients, queue, sessions, results, documents, rostering, inventory, billing) scoped to the organisation they have chosen for this sign-in. A user who belongs to more than one switches between them.

This is a change from the single-tenant CMS. There is no “first admin” bootstrap step and no Medplum credentials in environment variables any more: the first admin is whoever creates the organisation, and each organisation’s Medplum credentials are entered through the app (or set up by Medbot) and stored encrypted.

Key concepts

ConceptWhat it is
OrganisationThe tenant. Carries a name, a slug, a country and time zone, an active flag, a join code, and its own Medplum server details.
Self-managed or Medbot-hostedA self-managed organisation brings its own Medplum project and credentials. A Medbot-hosted one has its Medplum project set up and managed by Medbot.
MembershipA person’s place in one organisation, with exactly one role there. The same person can be a member of several organisations, with a different role in each.
Current organisationThe one the CMS is rendering right now. Chosen on the welcome screen at every sign-in and changed from the sidebar switcher. See Choosing & Switching.
Join codeA short code an admin hands to a new hire so they can request access from the app. See Join an Organisation.
Access requestA pending request to join, filed by join code and resolved by an admin from the staff screen.
Medplum credentialsThe client id, client secret and base URL of the organisation’s own Medplum server. Held encrypted by the backend; never exposed to the browser. See Medplum Credentials.
Country-specific integrationsNational services available to organisations in one country. Today that means SmartCMS for organisations in Singapore.

What you can do

  1. Create an organisation with your own Medplum server and become its first administrator: Create an Organisation.
  2. Ask Medbot to host one if you have no Medplum server: Medbot-Hosted Organisations.
  3. Join an existing one with a join code, or have an admin invite you by email: Join an Organisation.
  4. Belong to several and choose which one to work in: Choosing & Switching.
  5. Bring in staff and patients, one at a time or in bulk from a CSV file: Members & Roles and Seeding Staff & Patients.
  6. Administer the organisation: rename it, set its country and time zone, choose its integrations, rotate its join code, manage its Medplum connection: Organisation Settings.
  7. Connect to Singapore’s national systems through SmartCMS: verify CHAS at check-in, claim CHAS, Medisave and other subsidies from the bill, and send registry and disease reports: SmartCMS.

The organisations screen

/organisations lists every organisation the signed-in user belongs to, with their role in each and a Current badge on the active one. From it they can switch to another, open Settings on any they administer, or Create organisation. A Requests section above the list shows any Medbot-hosted organisation requests they have made.

Unlike every other staff page, this one does not require an organisation to be chosen: a brand-new user with no memberships lands here. With no memberships at all, the empty state suggests creating one with your own Medplum server, asking Medbot to host one, or asking an administrator for a join code.

Where to go next

Last updated on