SwaspsSwasps Hospital OS
A coordinated patient journey from arrival to triage.
Design Partner Program Starting with patient access.
Explore the vision ↓The problem
The patient journey is fragmented before care even begins.
Patients move through multiple people, systems, queues, and handoffs.
This creates:
- Duplicate data entry
- Unclear task ownership
- Hidden waiting time
- Manual status chasing
- Limited operational visibility
3. What happens today
One patient. Multiple handoffs. Limited visibility.
Arrival →Registration →Intake →Queue →Triage
Show the target hospital's actual workflow, including:
- Systems used
- Staff involved
- Manual handoffs
- Waiting points
- Information repeated
- Where ownership becomes unclear
Evidence: workflow observation + staff interviews.
4. What Swasps changes
From disconnected tasks to one coordinated workflow.
Swasps:
- Detects workflow events
- Surfaces the next action
- Routes work to the right person
- Tracks completion
- Maintains a continuous patient journey record
Staff stay in control. Swasps coordinates the work.
5. The pilot workflow
One workflow. Clearly defined.
Arrival →Registration →Intake →Triage Queue →Clinical Handoff
Included
- Patient arrival
- Registration workflow
- Intake
- Triage queue coordination
- Clinical handoff visibility
Excluded
- Diagnosis
- Clinical decision-making
- Treatment
- Billing
- Pharmacy
- Inpatient workflows
6. How it fits
Swasps works with the hospital's existing infrastructure.
Hospital systems →Integration layer →Swasps Hospital OS →Staff workflows
Integration through available: FHIR · HL7 · DICOM · REST APIs
For the design-partner hospital, map:
- HIS/EMR
- Registration system
- Queue management
- Patient identity system
- Other relevant APIs
No rip-and-replace.
7. What the hospital gets
A measurable view of the patient access workflow.
- Fewer duplicate entries
- Clearer task ownership
- Better queue visibility
- Less manual status chasing
- Visibility into waiting and drop-off points
Outcome: a more coordinated patient journey from arrival to triage.
8. Pilot design
A 1–4 week controlled workflow pilot.
| Duration | 1–4 weeks |
|---|---|
| Departments | OPD / Patient Access + Triage |
| Systems | HIS/EMR + Registration/Queue systems |
| Swasps provides | Configuration, workflow mapping, integration, training & measurement |
| Hospital provides | Operational owner, staff input, system/data access & feedback |
Success metrics
Measure the workflow before and after Swasps.
Track 3–5 agreed metrics:
- Arrival → Registration time
- Registration → Triage time
- Manual handoffs per patient
- Duplicate data-entry events
- Staff time spent chasing status
Baseline →Pilot →Measured change
Safety and control
Swasps coordinates. Hospital staff remain accountable.
Swasps can coordinate operational work and surface intelligence.
Hospital staff retain responsibility for:
- Clinical decisions
- Patient safety
- Approvals
- Consequential actions
- Exceptions and escalation
Human oversight remains built into the workflow.
Design-partner ask
Help us build the workflow around your hospital.
We are looking for one design-partner hospital to:
- Map the current patient-access workflow
- Validate integration requirements
- Define baseline metrics
- Run a controlled pilot
- Review results with the Swasps team
The goal is to improve how the existing workflow operates.
The team
The team building it.
-
Stanley Onyango
Founder / CEO -
Beth Njeri
Co-founder / COO
Get started
Bring Hospital OS to your hospital.
Hospital OS is ready for hospital pilots. If you want to talk about what deploying it at your hospital looks like, let's have that conversation.
Swasps Hospital OS. The hospital, coordinated.