Live district view
District team
Acts on source, reason, and freshness before making a public routing decision.
Real-world stakes
The same clinic status update changes district decisions, field reporting, coordinator follow-up, and patient routing.
Live district view
Acts on source, reason, and freshness before making a public routing decision.
Queued field report
Submits the service update even when the report has to queue offline.
Traceable status change
Confirms the service impact without losing the original source record.
18 min avoided
Sees the safer nearby route before spending time travelling to a blocked service.
The operating gap
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.
08:07
Pharmacy disruption is known at the clinic before the district view changes.
08:11
A weak-signal report keeps the source and notes until connectivity returns.
08:13
Patients can still see the clinic as available unless freshness is visible.
08:15
The district console, public finder, and audit ledger receive the same incident state.
Incident flow
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 source
Offline report keeps the incident source attached.
Connected incident path
OPERATIONS / AUD-OPS-MAB-001
Field report
Mabopane Station / Pharmacy / generator failure
District alert
Operational to non-functional from field source
Public finder
Akasia Hills Clinic is best nearby compatible for pharmacy services
Audit ledger
Source, sync, status change, and reroute linked
Product surfaces
Clinic Pulse gives each team the right surface for the same operating record: district visibility, offline reports, patient guidance, and audit-ready evidence.
See service availability, field source, freshness, and routing action in one operating view.
Capture service pressure and notes in weak-signal environments, then sync with source intact.
Warn patients before a wasted trip and recommend the best nearby compatible clinic.
Keep the source, status change, reroute, export, and API evidence attached to the decision.
Trust evidence
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
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