Codehesion
Let’s talk
Mukon
HealthcareInnovation Pods

Lab results, built for the bedside.

Have the platform and the expertise, and need the app your people will actually use? Mukon provides medical laboratory services and had already built the platform behind its results. We joined their team to design and build the app on top of it, and it's now live in both app stores.

Let's talk →Tell us about a project like this.
02

At a glance

  1. 01

    Client. Mukon, a South African medical laboratory services business.

  2. 02

    Industry. Healthcare.

  3. 03

    Delivered. The app's design, build, testing and release, on their own platform.

  4. 04

    Team. Developers, QA, a project manager and a designer, with architecture oversight.

  5. 05

    Platform. iOS and Android.

03

A platform ready for its app

Their work connects clinicians, nurses and pathologists with laboratory testing and results. They had a clear view of how an app should support that work, and they had already built the platform it would run on. They wanted a team to design and build the app itself, working alongside theirs.

The next step was putting it in clinicians' hands.

04

Results are read on the ward, not at a desk

Clinical staff check results between patients, often in parts of a hospital where the signal comes and goes. The results themselves are dense, and every detail carries clinical meaning. An app that needs a perfect connection, or simplifies the results until they lose that meaning, doesn't get used where it matters most.

05The impact we made

We designed for the ward

We took on the design as well as the build, and started from the hardest place the app would be used: a busy ward and a clinician who needs the answer now.

That decision shaped everything after it. Every design choice was tested against the ward first.

Built for the bedside, screen by screen.

06

How we built it

These are the principles behind the work, done alongside their team.

Their platform, our app

They kept their platform and the rules behind it, and we owned the app's design, build, testing and release. A split like that only works with close communication, so questions and issues were raised early and worked through with their team, whichever side of the line they sat on.

Agreed before it was built

The whole app was designed and agreed with their team before development started, so the build team knew exactly what each screen was for.

Privacy from the first sprint

Patient information deserves the highest level of care, so privacy and security were part of the design from the first sprint and part of every piece of work after it.

Tested on real phones

Clinicians use whatever phone they have, so we tested throughout on a range of real devices.

Evidence before promises

When something needed fixing, we found the cause before committing to a fix. It takes a little longer up front, and it means every fix solves the real problem.

Oversight on every sprint

Work ran in two-week sprints with daily check-ins and regular demos to their team. An experienced solution architect and stream lead oversaw the technical direction throughout.

07

The full picture, wherever they are

Their clinicians now have the lab in their pocket, wherever they work. The app and the designs behind it are theirs, ready to build on.

08

Keep going

08Let’s talk

Your people work far from a desk? Let's build for where they are.

Tell us about a project like this.