All work

Onus: Electronic Health Records Platform

A patient-centred digital health platform connecting patients and healthcare providers through secure, accessible health data.

Product design · UI/UX design · Full-stack development
Windhoek, Namibia · 2025

Onus interface screens for patients, providers and administrators arranged around an illustrated doctor.

Onus is built on a simple idea: health information should empower the patient. It gives patients one place to hold their medical history and decide which healthcare providers can see and add to it. We designed and built the first working version, from product thinking to full-stack development.

The challenge

Medical history is spread across doctors, practices, and hospitals, and it rarely moves with the patient. Clinicians meeting someone for the first time often start with an incomplete picture.

As an early-stage product, Onus also had to resolve its workflows, business model, and user experience while the platform was being built.

The approach

We focused on a functional MVP rather than the full long-term vision: enough to show how Onus works in practice and to start testing it with doctors and other healthcare professionals.

Product thinking, UX, and engineering ran as one process, so decisions about the interface, permissions, data structure, and clinical workflows shaped each other throughout the build.

One platform, three users

Patients

Patients see their medical information and consultation history in one place, and decide which members of their care team can view and contribute to their record.

The patient dashboard showing health records and recent consultations.
Patient dashboard
The connections screen where a patient manages which providers can access their record.
Choosing who has access

Healthcare providers

Authorised clinicians see a patient’s existing history and add to it, so each consultation starts with more context.

The provider dashboard with recent patients and consultation requests.
Provider dashboard
The form a provider uses to record a new consultation.
Recording a new consultation

Administrators

An administrative layer oversees the platform and its users as it grows.

The administrator dashboard with platform analytics.
Administrator overview
The Onus sign-in screen beside an illustrated doctor.
Sign-in

Privacy was a product requirement, not a feature.

Consent, permissions, access control, patient ownership, and the separation of user roles shaped the architecture from the start. Onus was as much an exercise in designing trust as in designing software.

What we delivered

  • Product and UX planning
  • Complete UI/UX design
  • Patient, provider and administrator interfaces
  • Full-stack web development
  • Authentication and permissions
  • Health records and consultation workflows
  • Data and application architecture
  • Deployment of the working application

The outcome

A working application, not a prototype. The MVP establishes the relationship at the heart of Onus: patients control access to their health information, and authorised providers contribute to an evolving medical history.

Just as importantly, it gives the team something real to put in front of healthcare professionals and learn from.

Project facts

ClientOnus
ProjectElectronic Health Records Platform
IndustryHealth Technology
LocationWindhoek, Namibia
Year2025
ServicesProduct Design · UI/UX Design · Full-Stack Development · Web Application Development · Software Architecture
UsersPatients · Healthcare Providers · Administrators

Planning something similar?

Start a project