Real-world stakes

One status change affects everyone.

The same clinic status update changes district decisions, field reporting, coordinator follow-up, and patient routing.

district operations desk reviewing clinic status information

Live district view

District team

Acts on source, reason, and freshness before making a public routing decision.

field care context used for an offline clinic status report

Queued field report

Field worker

Submits the service update even when the report has to queue offline.

clinic status context for a public availability update

Traceable status change

Clinic coordinator

Confirms the service impact without losing the original source record.

patient care context connected to safer clinic routing decisions

18 min avoided

Patient

Sees the safer nearby route before spending time travelling to a blocked service.

The operating gap

Clinic status changes before district systems catch up.

Calls, messages, and late reports make stale data look confident. Clinic Pulse connects field signal, district visibility, public routing, and audit history in one operating record.

clinic status context for a public availability update

08:07

Service pressure starts locally

Pharmacy disruption is known at the clinic before the district view changes.

08:11

Field report queues offline

A weak-signal report keeps the source and notes until connectivity returns.

08:13

Stale public data creates risk

Patients can still see the clinic as available unless freshness is visible.

08:15

ClinicPulse updates the operating record

The district console, public finder, and audit ledger receive the same incident state.

Incident flow

From field signal to operating record.

One availability incident moves from an offline field report to the district console, patient reroute, and sealed audit trail without splitting the source record.

field care context used for an offline clinic status report

Field source

Offline report keeps the incident source attached.

Connected incident path

OPERATIONS / AUD-OPS-MAB-001

01Queued offline

Field report

Offline report queued

Mabopane Station / Pharmacy / generator failure

02Fresh - 2 min ago

District alert

Clinic status changed

Operational to non-functional from field source

0318 min avoided

Public finder

Wasted trip avoided

Akasia Hills Clinic is best nearby compatible for pharmacy services

04AUD-OPS-MAB-001

Audit ledger

Operating record sealed

Source, sync, status change, and reroute linked

Product surfaces

The operating surfaces behind the decision.

Clinic Pulse gives each team the right surface for the same operating record: district visibility, offline reports, patient guidance, and audit-ready evidence.

42 clinics monitored

District command center

See service availability, field source, freshness, and routing action in one operating view.

District console
live
SourceField worker
Freshness2 min ago
ActionOpen alert
3 reports queued

Offline field reports

Capture service pressure and notes in weak-signal environments, then sync with source intact.

Field report
offline
ClinicMabopane Station
ServicePharmacy
DisruptionGenerator failure
Sync stateQueued offline
18 min avoided

Patient rerouting

Warn patients before a wasted trip and recommend the best nearby compatible clinic.

Mabopane pharmacy pickup
ClinicBest nearby compatible
ServicePharmacy accepting
5 events linked

Audit and export readiness

Keep the source, status change, reroute, export, and API evidence attached to the decision.

Audit ledger
recording
SourceOffline field report
RerouteAkasia Hills Clinic
ExportCSV ready

Trust evidence

Public-sector trust lives in the evidence chain.

Every operating decision keeps its source, permissions, freshness, audit reference, export state, and partner handoff visible for public-sector review.

Source and permissions

field_worker / district_manager

actor=field_worker

permission=publish_status

source=offline_sync

Freshness and audit

AUD-OPS-MAB-001

status=non_functional

freshness=2m

route=Akasia Hills Clinic

Offline queue

3 reports queued

queue=offline_reports

sync=when_signal_returns

source_notes=preserved

District export

CSV ready

report=incident_summary

district=Tshwane North

rows=42 clinics

API/status endpoint

200 OK

GET /v1/clinics/mabopane-station/status

payload=status_incident

freshness=2m

Webhook preview

partner handoff

webhook=preview_sent

recipient=partner_app

retry=false

Operations walkthrough

Walk through the Mabopane Station incident.

Follow one clinic disruption from district triage through field confirmation, public routing, admin review, and monitoring.

Scenario data is local to the walkthrough and mirrors the operating model clearly.

Live incident summary

STATUS_INCIDENT / NON_FUNCTIONAL

Source clinic

Mabopane Station Clinic

Reroute

Akasia Hills Clinic

Audit record

AUD-OPS-MAB-001