Swasps

The AI Infrastructure for Hospital Operations

Swasps is building the AI infrastructure that orchestrates hospital workflows, systems, and people as one intelligent, connected operation.

AI-native healthcare infrastructure. Explore the vision ↓
The problem

One continuous journey. Disconnected operations.

The patient journey is one continuous experience. Hospital operations aren't.

Registration Triage Clinical Care Diagnostics Pharmacy Billing Discharge

Each step often runs through a different system, department, and workflow.

The gaps between them create
  • Manual coordination
  • Repeated data entry
  • Staff phone calls
  • Delays
  • Broken handoffs
Hospitals have systems for each function. They lack a layer that coordinates the whole journey.
The wedge

Starting with patient access.

From arrival to triage, hospitals rely on multiple systems and teams to move one patient forward.

Patient arrives →Registration →Eligibility and intake →Queue assignment →Triage →Clinical handoff
When those handoffs are disconnected
  • Staff repeat data entry
  • Patients wait without visibility
  • Teams coordinate by phone, chat, and memory
  • Delays at the front desk ripple into the rest of the hospital

Swasps starts by coordinating this workflow with automated AI agents from registration, then expands across hospital operations and departments.

The solution

Coordination, not replacement.

Swasps gives hospitals one intelligent coordination layer above the systems they already use.

  1. 01 Capture and understand what needs to happen next
  2. 02 Move tasks to the right team or system
  3. 03 Keep patient workflows progressing
  4. 04 Surface delays and missing information
  5. 05 Escalate consequential decisions to humans

For patient access, Scout coordinates the journey from arrival to triage without forcing hospitals to replace their existing infrastructure.

Existing hospital systems + Swasps agents + Human oversight = One coordinated workflow
Orchestration

Many agents. One orchestration layer.

Swasps agents work together under one orchestration layer to execute the work between hospital systems, departments, and staff.

At every stage, the agents
  • Understand the patient's current state
  • Determine what needs to happen next
  • Execute routine tasks across connected systems
  • Route work to the right staff member or department
  • Carry context forward across handoffs
  • Detect missing information, delays, and exceptions
  • Request human verification before consequential actions
RegistrationTriageClinical CareDiagnosticsPharmacyBillingDischarge
Swasps orchestration layer
Agent-coordinated Human verification
Early signals

The coordination problem, already visible.

The coordination problem is already visible in the market.

  • 13of 20 hospitals approached issued a letter of intent
  • 4 Core AI agents in development

Full patient-access workflow currently being built.

Prototype
Design partnerships
Pilots

Swasps is being built from direct insight into hospital workflows — starting with the coordination layer and expanding across hospital operations.

Why now

More software. Same gaps.

Hospitals have more software than ever. The gaps between those systems still depend on people, phone calls, spreadsheets, and memory.

  1. 01

    Hospital data is becoming more accessible through APIs and standards such as FHIR, HL7, DICOM, and REST.

  2. 02

    AI agents can interpret context, make routine decisions, and execute multi-step workflows.

  3. 03

    Hospitals need to improve capacity and staff efficiency without replacing every system they already use.

Swasps sits between the systems hospitals already have and the work that still falls through the gaps.

Go-to-market

Sell the workflow, not the platform.

Swasps starts with founder-led sales to hospitals in Kenya, using workflow insight and existing hospital interest to recruit design partners.

  1. 01 Target one internal champion: COO, head of patient access, or hospital operations lead
  2. 02 Run a workflow-mapping session with patient-access and clinical teams
  3. 03 Agree on baseline metrics before the pilot
  4. 04 Deploy Scout in a tightly scoped 8-12 week design partnership
  5. 05 Convert successful pilots into paid deployments and expand into adjacent workflows
Arrival-to-triage timeManual handoffs and phone callsDuplicate data entryStaff time spent chasing statusPatient visibility and completion rates
Business model

Land and expand.

Swasps is sold to hospitals as an AI coordination layer across existing systems.

  • Workflow modules, starting with patient access
  • The orchestration layer connecting systems, teams, and agents
  • Usage that scales with hospital volume and workflows coordinated
Initial wedge → expansion
TriageClinical coordinationDiagnosticsPharmacyBillingDischarge
Competition and alternatives

Many systems. One gap.

Hospitals already use many systems. The gap is what happens between them.

Current alternatives
  • Hospital information systems that manage individual departments
  • Patient-access and scheduling tools focused on one workflow
  • Integration platforms that move data but do not coordinate work
  • Manual processes using calls, chats, spreadsheets, and staff memory
Swasps combines
  • Cross-system workflow coordination
  • Agents that understand context and execute routine tasks
  • Handoffs routed to the right person or department
  • Human verification for consequential decisions
Team and founder-market fit

Founder-market fit.

The team is building from direct observation of hospital coordination problems in Africa, where disconnected systems and manual handoffs create operational friction across the patient journey.

  • Stanley Onyango

    Founder & CEO

    Software Developer.

Vision & the ask

The future of healthcare infrastructure.

Today Hospital Operations →Tomorrow Connected Hospitals →Then Patient Ecosystem →Eventually Healthcare Intelligence Network

We're building the foundation for the next generation of healthcare infrastructure.

Swasps. The hospital, coordinated. swasps.health