Why we built Sienna
The frustrations and decisions behind Sienna's local-first design for general practices in Namibia and Southern Africa.
What we kept seeing in GP practices
General practitioners work in fast-paced environments where patient flow is constant, time per consultation is limited, and systems must not fail during care. In many practices, connectivity is not always reliable, yet most modern systems assume that the internet is always available.
This creates friction in the moments that matter most:
- Opening a patient record during a consultation
- Writing notes while the patient is present
- Scheduling follow-ups quickly between visits
- Accessing history without delays
What we designed for
Working from how general practices operate, a few requirements became non-negotiable:
- The system must be fast on a local network
- It must remain usable even when internet connectivity is unstable
- Core workflows must require as few steps as possible
- Staff should not switch between multiple systems to complete basic tasks
How that shaped Sienna
Instead of building a cloud-first system, we designed Sienna as a local-first platform. This means it runs inside the practice while still being accessible through a browser.
- Patient records remain inside the practice environment
- Clinicians access the system through a browser
- Workflows are organised around consultation speed and clarity
- Local deployment can keep the system reachable during connectivity disruptions
Our current focus
The first phase has focused on individual GP practices, which lets us refine consultation workflows, onboarding, and day-to-day usage. Practices with two or more doctors, and larger clinics, are scoped and deployed per practice.
What comes next
As Sienna grows, we plan to expand into:
- Multi-provider clinics
- Specialist workflows
- Deeper reporting and integrations
If you are a GP interested in using Sienna, we invite you to explore it yourself or talk it through with us.