Appearance
How Verabase fits together
Verabase has two halves. Each has its own people, its own app and its own database.
- Verabase Cloud (the control plane). Our team runs it. It decides who is a customer, what they have paid for, and whether their system is healthy. It never sees a patient record.
- The hospital system (the tenant). Each customer hospital gets its own. It holds every patient, order, dose and naira, and it is where hospital staff spend their whole day.
Everything in this guide sits on one side of that line or the other. If you remember one thing, remember this: the control plane grants, the hospital system does the work.
┌──────────────────────────── VERABASE CLOUD (control plane) ────────────────────────────┐
│ platform-admin · Operations console for the Verabase team │
│ Tenants · Licences · Module grants · Devices · Support · Audit · Security │
│ │
│ platform-api + Postgres Owns: who the customer is, what they may use, │
│ whether their runtime is healthy. No clinical data. │
└───────────────┬───────────────────────────────────────────────────────────────────────┘
│ module grants + licence ──▶ (the tenant server's installation plan)
│ ◀── runtime heartbeat, health, version
▼
┌──────────────────────────── ONE HOSPITAL (tenant) ─────────────────────────────────────┐
│ tenant-server · one database per hospital (hosted on Turso for MVP) │
│ │
│ facility-web · the app every hospital role signs in to │
│ Patients · Clinical · Diagnostics · Revenue · Operations · Administration │
│ │
│ Roles: Facility Admin, Front Desk, Nurse, Provider, Pharmacist, Lab Technician, │
│ Lab Supervisor, Radiology Technologist, Billing Officer, … (see Reference) │
└───────────────────────────────────────────────────────────────────────────────────────┘The three layers of permission
A person can do something in a hospital only if all three layers allow it. When something is "missing", this is where to look, in this order.
| Layer | Set by | Where | Example |
|---|---|---|---|
| 1. Licence plan | Verabase ops | platform-admin → Tenant → License | The Standard plan does not include Pharmacy, Lab or Inpatient. A hospital needs Professional or higher. |
| 2. Module grant | Verabase ops | platform-admin → Tenant → Module provisioning | Pharmacy can only be granted once Core and Inventory are granted, and only if the licence includes it. |
| 3. Role | Facility Admin | facility-web → Administration → Staff | A Billing Officer never sees the chart; a Nurse cannot verify a prescription. |
A module that is licensed and granted still has to be set up inside the hospital. For example, pharmacy only receives chart prescriptions once a Facility Admin turns on Provider orders (FAC-OPD-01, step 0).
Who uses what
| Audience | Uses | Start with |
|---|---|---|
| Verabase operations and support | platform-admin | Control-plane journeys |
| Implementers and sales engineers | Both: platform-admin to provision, facility-web to configure and demo | CP-02 Onboard a hospital, then FAC-OPD-01 |
| Hospital IT and Facility Admins | facility-web → Administration | FAC-OPD-01 step 0, then the Facility Admin handbook |
| Hospital staff | facility-web, one workspace per role | Your role's handbook |
Five ideas that explain the whole hospital system
- The queue is the day. Reception puts people in the queue; everybody else works from it. Almost nobody starts by searching.
- The patient follows you. Pick a patient once and they stay selected as you move from Clinical to Lab to Billing.
- Nothing is retyped. A test ordered on the chart appears on the lab bench. A verified prescription appears at the pharmacy counter. Both appear on the bill. Every line traces back to the order that created it.
- A refusal means the system is working. When Verabase blocks something, it says what matched and what it needs. See each journey's What Verabase will refuse section.
- Who and when, twice. The time care happened and the time it was typed are separate facts, and the author always comes from the login.
Deployment, in one paragraph
For the MVP every hospital is hosted. The tenant server and its database run in our cloud, and staff use facility-web in a browser. On activation, the control plane provisions the hospital's database and issues its first Facility Admin credentials. After that it sends licence and module-grant updates, which the hospital picks up on its next runtime refresh. An on-premises "edge" mode (a local box that keeps working offline) is designed but comes after the MVP.