Trust architecture.
Eight connected layers shape how PULSE is designed, configured and operated. Select a layer to see what it covers.
Security
System-of-record boundary.
PULSE coordinates operational work and evidence. Authorised clinical and enterprise systems can remain authoritative for their respective records and decisions. PULSE connects the operational work between them rather than replacing them.
What assurance evidence may include.
Assurance is built from controlled work products that make state, ownership, safety and release decisions visible and reviewable.
Examples of controlled assurance work products. Final artefacts depend on deployment scope and client governance. No certification, regulatory approval, POPIA compliance, completed independent audit or customer acceptance is claimed.
AI where it helps.
Human accountability where it matters.
PULSE uses AI for administrative and analytical support within approved boundaries — never as the sole authority for clinical decisions.
Interaction Support
- Conversational administrative intake
- Multilingual support
- Voice assistance
Knowledge Support
- Approved knowledge retrieval
- Administrative classification
Operational Intelligence
- Operational summarisation
- Workflow recommendation
Analytics
- Demand forecasting
- Anomaly detection
- Wait estimation
AI is not the sole authority for: emergency disposition, formal clinical triage, diagnosis, prescribing or treatment decisions.
Where AI is never the sole authority.
PULSE does not position a generative model as the sole authority for the following decisions. Accountable human authority and approved protocols remain in control.
Release and rollback.
Every capability moves through a controlled chain — from intended use to a deliberate decision to scale, hold, disable or roll back.
Named authorities for every deployment.
Each deployment requires named client authorities across the following areas so that safety, privacy and accountability are owned, not assumed.
What a PULSE discovery discussion covers.
The initial discussion is intended to understand the operational problem and determine whether a structured discovery or first-site pilot is appropriate.
- Selected facility or service
- Current patient journey
- Common delay and hand-off points
- Staff roles and operational ownership
- Existing systems
- Integration boundaries
- Devices and connectivity
- Potential pilot scope
- Candidate success measures
- Next-step options


