Client access
Web companion, service discovery, booking, approved information.
Digital health & client engagement
CHIKARA Health
for Tebelopele
CHIKARA digital health platform — demonstration configured for Tebelopele Wellness Centre. Simulated data. Not a live clinical system.
Stock sequences for demonstration atmosphere · not Tebelopele staff photography
Care operations
Appointments, escalations, referrals, demonstration analytics.
Intelligence & governance
Safety decisions, traces, knowledge governance, trust centre.
Offline-aware shell · Human-centred · Governed · Interoperable (planned)
Client companion
Health access with a safety gate first
Find services, book, and read approved topics. High-risk patterns escalate to humans.
Enterprise event detail
Mature systems show identifiers, actors, and audit — not only success toasts.
Example confirmation shape
Appointment confirmed
APPT-2026-#####
Channel: Web
Workflow: Appointment
Audit event recorded
Services (seed)
- HIV Testing & Counselling
- ART Adherence Support
- Sexual & Reproductive Health
- General Wellness Visit
Same intelligence. Different channel.
Illustrative WhatsApp experience using the same safety gate patterns as web chat.
CHIKARA Health Companion · Demo
Channel strategy
Web and WhatsApp share: safety gate → workflow → audit. Labels remain honest about what is simulated versus planned production integration.
LIVE DEMOWeb companion flows
SIMULATEDWhatsApp conversation UI
PLANNEDMeta Cloud API send path & templates
Care operations
24
Appointments (incl. sim baseline)
7
Open referrals
2
Active escalations
18
Feedback (sim)
Service demand Illustrative
Platform health
Client services — Operational (demo)
Knowledge service — Operational (demo)
Appointment workflow — Operational (demo)
Referral workflow — Operational (demo)
Audit service — Operational (demo)
WhatsApp integration — Demonstration
DHIS2 integration — Planned
Appointments
| ID | Service | When | Status | Channel |
|---|
Escalations
| ID | Trigger | Status | At |
|---|
Referrals
| ID | To | Status | At |
|---|
Intelligence & safety
AI decision trace
User messageInbound text from client channel
Intent detectionService / booking / information / other
Safety screenEscalate when urgent symptom patterns match policy gate
Knowledge retrievalApproved articles only when allowed
Policy checkScope, refusal, human-oversight rules
Response generationSuppressed on escalate; otherwise constrained reply
Audit eventImmutable demonstration log entry
Intelligence stack
L5Governance — clinical review, audit, policy, access control
L4Intelligence — reasoning, retrieval, safety classification
L3Workflow — appointments, referrals, follow-up, escalation
L2Services — HIV, maternal, wellness, screening
L1Access — WhatsApp, web, mobile, SMS
Sky blue and the black–white harmony stripe signal local rootedness; depth comes from structure, not chrome.
Governance & trust
Knowledge objects
| Article | Status | Source | Review | AI usage |
|---|---|---|---|---|
| HIV Testing — pre-test information | ● Approved | Programme knowledge base | Current | Permitted |
| Antenatal care — overview | ● Approved | Clinical review | Current | Permitted |
| TB symptoms — public info | ● Review | Clinical review | Pending | Blocked |
| Family planning — overview | ● Approved | Programme knowledge base | Current | Permitted |
HIV Testing — Pre-test information
AI may retrieve this object only while status is Approved.
Trust Centre
Privacy
Data minimisation · access control · retention policies
Safety
Human escalation · clinical governance · boundaries
AI governance
Approved knowledge · traceable decisions · oversight
Security
Authentication · encryption architecture · audit trails
AI does not replace clinical care.
Role permission matrix enforced at the gateway
Not a UI courtesy — the API rejects calls a role isn't permitted to make. Probe it live from the Insights view.
| Capability | Client | Front desk | Health worker | Programme | Admin |
|---|
Audit stream hash-chained · tamper-evident
Platform overview
Connected care. Governed intelligence. Human oversight.
Client accessWhatsApp · Web · SMS · Mobile
24/7 digital entry (target)
24/7 digital entry (target)
CHIKARA intelligenceUnderstand · Assess · Retrieve
Guide · Escalate
Guide · Escalate
Care operationsAppointments · Referrals
Follow-up · Feedback
Follow-up · Feedback
GovernanceClinical review · Audit · Security · Analytics
Offline-aware · Human-centred · Governed · Interoperable
Architecture
CLIENT CHANNELS STAFF CHANNELS
Web / WhatsApp / SMS Operations console
\ /
\ /
CHIKARA INTELLIGENCE
Knowledge · Safety · Workflow
|
HEALTH SERVICES
Appointments / Referrals
|
DATA & AUDIT LAYER
Illustrative care funnel
Not operational statistics
Client contacts1,000
Service enquiries720
Appointments410
Completed services330
Referrals94
Follow-up events61
Today → target state
Illustrative comparison — not a claim about any named facility’s current tools
Fragmented channels (illustrative)
Phone · paper · spreadsheets · ad-hoc chat
Platform target
One client journey · one workflow · one governance model · one audit trail
MVP → scale roadmap
PHASE 01 · MVP
Client engagement, appointments, knowledge, referrals, safety escalation, ops dashboard
PHASE 02 · PILOT
WhatsApp/SMS, advanced analytics, identity hardening
PHASE 03 · SCALE
DHIS2 interoperability, mobile apps, expanded services
PHASE 04 · NATIONAL LAYER
Multi-site, multi-programme, interoperable infrastructure
Case timeline
One coherent story: access → book → inform → safety → human → referral → audit.
Closing line for evaluators
One client journey. One operational view. Governed intelligence throughout.
System & architecture
Live layer map
Every gateway call tags the layer it touched. Use the platform — watch the counters move.
Platform health computed live
WhatsApp templates
| Template | Status | Lang |
|---|
admin role required — everyone else gets a real 403
API console gateway log
Request IDs, latency, status, error codes — the same observability a production gateway emits.
Database inspector debug console
A production system would never expose this — which is exactly why showing it in a demo is powerful. All rows persist across refresh.
Insights
What this evaluator cares about
In production this same engine turns real usage into product decisions. Here it reads the room, live.
Probe the access boundary
One-click proof that permissions are enforced by the gateway, not hidden in the UI.
Co-pilot: improve it in front of them
Type an improvement the evaluator asks for — e.g. “what about SMS?”, “can it speak isiZulu?”, “DHIS2?” — and watch it land on the roadmap with an inferred phase.