Kenya-ready digital hospital platform · SHA claim workflows · M-Pesa and eTIMS aware · Certification-ready architecture
Built for Kenyan hospitals

One hospital. One patient record. One intelligent operating system.

AfyaCare 360 connects registration, clinical care, diagnostics, pharmacy, revenue cycle and executive intelligence in a single governed platform — calm enough for a new receptionist, deep enough for a hospital CEO.

This environment runs on a persisted synthetic dataset and is clearly badged as demo data.

Executive Command Centre

Patients attended

1,284

+6.2%

Bed occupancy

88.4%

Above target

Revenue billed

KES 8.9M

+4.1%

Claims at risk

KES 12.3M

Ageing 90d+

Patient journey · today

Arrived100%
Triaged83%
Consulted66%
Pharmacy49%
Completed32%

What changes in the first quarter

Operational outcomes the platform is designed to produce. No borrowed customer statistics.

Shorter queues

Every arrival has a stage, an owner and a wait clock the whole hospital can see.

Safer handovers

One patient record follows the patient from triage to discharge without re-keying.

Clearer revenue

Charges capture at the point of care, so billing stops chasing yesterday's activity.

Fewer stock surprises

Consumption forecasts flag stockouts before they cancel theatre or dialysis lists.

One clinical-to-cash thread

Every step writes to the same record. Nothing is re-typed, nothing is lost between departments.

  1. 01

    Registration

    Master patient index dedupes before a file is created.

  2. 02

    Check-in and queue

    Paperless tokens, service point routing, live wait clocks.

  3. 03

    Triage

    Vitals, acuity and escalation captured on tablet at the bedside.

  4. 04

    Consultation

    Structured notes, diagnoses, orders and prescriptions in one pass.

  5. 05

    Diagnostics

    Lab and imaging orders with verified results and critical escalation.

  6. 06

    Pharmacy

    Dispense against live stock with interaction and allergy checks.

  7. 07

    Charge to cash

    Invoice, M-Pesa payment or SHA claim draft, then receipt.

  8. 08

    Patient 360

    Everything written back to one longitudinal record.

A home screen per role

People sign in to the work in front of them, not a generic dashboard.

Chief Executive

Hospital pulse, cash position and the exceptions that need a decision today.

Medical Director

Unsigned notes, unacknowledged results, pathway variance and clinical risk.

Matron

Live bed board, ward acuity, nursing coverage and discharge barriers.

CFO

Billed versus collected, receivables ageing, denials and leakage.

Clinician

Their list, their patients, their orders — with decision support at the point of care.

Pharmacist

Prescription queue, clarifications, stock availability and near expiry.

The Executive Command Centre

A governed metric catalogue sits under every card: definition, formula, numerator, denominator, exclusions, owner, refresh frequency and version. Click a number and you land on the records behind it, with your filters intact.

  • Attention strip of real exceptions with owner, SLA and drill-through
  • Eight direction-aware KPIs — rising is not automatically good
  • Flow, capacity, cash, claims, clinical operations, quality and workforce
  • Executive brief separating fact, threshold alert and forecast
Open the live command centre

Flow

Arrivals by hour, journey funnel, queue heatmap

Capacity

Bed board, occupancy trend, discharge outlook

Cash

Billed vs collected, waterfall, channel mix

Claims

Pipeline, ageing, denial reasons, value at risk

The connected module set

Built on one identity, one permission model and one metric layer.

Patient 360 and EMR
Appointments and queues
Inpatient, wards and eMAR
Laboratory and imaging
Pharmacy and medication safety
Billing and cashier
SHA and insurance claims
Stores and supply chain
Quality and patient safety
Governed AI intelligence
Executive command centre
Granular permissions and audit

Security and trust

Health data deserves a stricter default. Access is enforced at the server and the database, not only in the interface.

  • Granular, editable permissions enforced on every route, server function and database policy.
  • Immutable audit events treated as evidence — never replayed as executable commands.
  • Separate, tightly whitelisted safe-operations retry service for failed jobs.
  • Consent, privacy and representative handling built into the patient identity layer.
  • Truthful integration adapters: no invented connection is ever shown as successful.

See your hospital as one connected system.

Walk through the command centre, the clinical-to-cash thread and the permission model with our team.