Home What’s inside

Everything you’d otherwise have to take on faith.

Every module, every integration, exactly how your data is protected, and what the first four weeks actually look like — so you know what you’re buying before you sign.

The difference

One system, so your numbers finally agree with each other.

A purchase order and a journal entry match because they were never two separate products stitched together after the fact. One record, one set of books, one login — nothing to reconcile at month end.

Counted in the demonstration database

0
Patientsacross 4,966 visits, 755 admissions and 3,865 triage assessments
0
Ledger entriesfrom 5,914 double-entry transactions, posted by billing and procurement
0
Logged writesevery create, update and delete, with actor, IP and before/after values
0
Diagnostic orders2,546 lab, 1,685 imaging and 3,365 procedure orders, all on the same visits
Clinical Pharmacy Lab Imaging Supply Ledger Roster Messages ONE RECORD
Every module writes to the same record — and is logged doing it.

Modules

Thirteen modules, grouped the way the software is.

These are the four areas of the application’s own navigation, and every module inside them.

Clinical

Dashboard & Patients

The whole of a person’s care on one timeline, and the state of the building on one screen.

  • Dashboard — occupancy, waiting times, staff on duty and revenue, live
  • Patients — demographics, identifiers and medical history
  • Visits, admissions and discharge on the patient record
  • Triage assessments with ESI acuity scoring
  • Clinical notes, diagnoses, allergies and vitals
  • Lab, imaging and procedure results filed back to the patient
  • Insurance providers and claims against a visit

Operations

Wards, Visits, Pharmacy & Procurement

The day-to-day: who is in which bed, what was given to them, and what it consumed.

  • Wards — facilities, departments, rooms, beds and bed categories
  • Visits — triage, physician queue, procedure orders and visit charges
  • Pharmacy — medications, prescriptions and dispensing
  • Inventory with batches, expiry and stock-take sessions
  • Procurement — suppliers, purchase orders and goods receipt
  • Vendor bills and their payments, posted to the ledger
  • Equipment and medical device registers per facility

Finance

Accounting, Payroll & Pricing

Double-entry underneath, so the statements come out of the same books the wards write to.

  • Accounting — chart of accounts, journals and financial statements
  • Invoices, payments, receipts and expenditure
  • Payroll — runs, payslips, PAYE bands and locum rates
  • Pricing — the price list behind procedures, labs and imaging

Administration

Staff, Shifts, Catalogues & Settings

Who works where, when — and every list the rest of the system chooses from.

  • Staff — directory, facility postings and secondments
  • Shifts — station templates, rosters, swap requests and leave
  • Data catalogues — lab tests, imaging, procedures, devices, templates
  • Settings — users, permissions, tax, currency, time zone, messaging

Across every module

Communication, audit and access

Not a module of its own — these run underneath all thirteen.

  • Email, SMS and WhatsApp from any patient or staff record
  • Automatic receipt and invoice delivery on payment and issuance
  • Reusable message templates with attachments
  • Activity trail on every write: actor, IP, before and after
  • Role-based access with per-account permission overrides
  • Six interface languages, and per-facility regional settings

Integrations

Meet the systems you already run.

Native where it matters, and the same authenticated API the interface itself uses for everything else.

Analysers & lab systems

An HL7 gateway takes orders out to your analysers and middleware and brings results back in, with the chain of custody recorded at every hop.

Pharmacy & stock

Dispensing and administration deduct from inventory as they happen, so stock levels are a consequence of the clinical record rather than a separate count.

Payments

M-Pesa, PayPal and Stripe alongside cash, card and bank transfer — recorded as payments against an invoice, with receipts issued automatically.

Email, SMS & WhatsApp

Your own SMTP relay, Twilio or Africa’s Talking for SMS, and WhatsApp — invoice delivery, receipts and reminders go out on whichever you configure.

Accounting

The ledger is built in rather than synced to: procurement and billing post their own double-entry journals, and the statements come out of the same books. Export to CSV for your auditor.

REST API & webhooks

Every module is reachable over the same authenticated API the interface uses, with webhooks for pushing events out to systems of your own.

Working with something not listed here? Tell us what it is — the API is the same one the product is built on, so most things are reachable.

Security

So no one can quietly change a record on you.

Not a wall of badges — the specific protections built in, and what each one means for your liability if something ever goes wrong.

01

Every write is logged

Not per-screen, and not opt-in: the audit trail is written at the database layer, so every create, update and delete is captured with the actor, their IP address, and the before and after values.

02

Clinical chain of custody

Lab results and imaging studies carry their own trail on top of that one — received, processed, sent, viewed, amended — so you can answer who saw a result, and when.

03

Passwords are never stored

PBKDF2-HMAC-SHA256 at 210,000 iterations with a per-password salt — OWASP’s current floor. The cost is recorded alongside each hash, so it can be raised later without invalidating anybody’s password.

04

Permissions, not just roles

Every endpoint is gated on a named permission rather than a job title, and any account can be granted or denied one individually — so the ward clerk who also does the banking does not need a second login.

05

Sessions you can end

Access tokens are short-lived and refresh tokens are revocable, rotated on every use and cancelled wholesale if a spent one is replayed. Disabling an account cuts off its sessions on the very next request.

06

Guessing gets you nowhere

Sign-in is rate limited per address and each account locks itself after repeated failures — tuned so a shift change arriving together is not mistaken for an attack.

Certification against a specific standard — HIPAA, ISO 27001, SOC 2 — is a property of a deployment and its operator, not of software on its own. If you need to reach one of those, talk to us about what your environment would have to look like.

Rollout

Live in two to four weeks, without disrupting your wards.

Four stages, in order, with an onboarding specialist who knows healthcare data and won’t make you learn ours.

  1. Week 1

    Discovery

    • Understand your current workflow and pain points
    • Map your existing data structure
    • Identify integration requirements
    • Scope customisations
  2. Week 1–2

    Setup & configuration

    • Provision your environment
    • Configure tax, currency and time zone
    • Set up user roles & permissions
    • Customise workflows & forms
  3. Week 2–3

    Data migration

    • Prepare exports from legacy systems
    • Validate & transform data
    • Staging environment testing
    • Dry run and reconciliation
  4. Week 3–4

    Training & cutover

    • Staff training by role & workflow
    • Super-user certification
    • Final production migration
    • Go-live support & stabilisation

For larger deployments: multi-facility implementations may extend to six to eight weeks, with parallel environments and a phased rollout.

Ready to see your numbers agree for once?

Half an hour, live, on the workflows you actually run.

Book a walkthrough