Skip to content

UX/UI Design for medical software

We design medical software, from cloud platforms to device interfaces, together with the companies that build it.
The deadline planner of Medwork, the cloud application for occupational health surveillance designed by Moze.

We step in when a medtech company needs to rethink its software, or design a new one, where an interface error weighs more than anywhere else.

We work on cloud platforms for healthcare and on medical device interfaces, often parts of the same product. We have been designing software for technology companies since 2012, and in the medical field we have worked on health surveillance, clinical trial data, assistive technology and laser therapy devices.

It may be the right time if

  • You want to improve the user experience of your software, but you have no in-house designers and your developers design it today
  • Your product lives on several devices — machine, desktop software, cloud, patient app — and each one has grown on its own
  • You are preparing a new model or a new version of the device and want to rethink the interface too
  • Clinicians, technicians, researchers and patients use the same product with very different needs
  • You want to validate a flow with users before writing its code
  • You need to hold usability and compliance together, from MDR requirements to the device’s usability engineering

Where we step in

Two areas, often within the same product

Two hand-drawn people looking in the same direction.Two hand-drawn people looking in the same direction.

Cloud software and healthcare platforms

Web applications for clinical management, compliance, data and research, used every day by doctors, clinics and companies. What matters here is long flows, roles and permissions, deadlines and large amounts of data made readable. We did it for Medwork, the cloud application for workers’ health surveillance.
A hand-drawn code window with a moving cursor.A hand-drawn code window with a moving cursor.

Medical machines and devices

Touch interfaces of machines used in the clinic, laboratory software connected to the devices, apps that accompany the patient. What matters here is the context of use, safety and how quickly decisions are made. We did it for the interface of a laser therapy device.

One product, several devices

In the medical field the same product often moves from the machine to the laboratory’s desktop software, from the cloud platform to the patient’s app. When each of these pieces is designed at a different time, by different people, users find different names, hierarchies and behaviours for the same task.

We start from the clinical flow and follow it across every device, to define a shared language: the same terms, the same states, the same alerts. Each device keeps its own constraints, but the product becomes one again.

Diagram of starting a treatment on the device tablet, desktop software, cloud platform and patient app, each with its own user: the same treatment and the same “In progress” status on all four.

How we work

Five activities that take medical software from an idea to a foundation the team can build on

① Understand the clinical context

In workshops with product, clinical and regulatory teams, we map the real flow and the regulatory constraints that shape the interface.

  • Use flows and users
  • Context of use and risks
  • Technical and regulatory constraints
A Moze designer facilitates a workshop in front of a whiteboard full of sticky notes with flows and use cases.

② Prototype with AI

With AI we build prototypes in code that don’t just look real but work, to try by hand, on touch screens too. They become the foundation for the existing codebase or for a new one.

  • Interactive prototype in code
  • Tried on the device or on a tablet of the same size
  • Foundation for the existing codebase or for a new one
A designer, seen from behind, prototypes the device screen with AI at the computer: chat on the left, interactive preview on the right.

③ Test with the people who will use it

Clinicians, technicians and patients try the prototype: hesitations and errors surface that a static screen does not show. For Medwork we chose the solutions through live tests with occupational doctors.

  • Tests with real users
  • Options compared
  • Decisions backed by results
During a test, a hand lowers the power on the device prototype, while a designer takes notes beside it.

④ Build the design system

From the validated screens we derive tokens, components and patterns, with particular care for alerts and errors: one system for every device of the product.

  • Tokens, components and patterns
  • Alert and error states
  • One system for every device of the product
Components of the device design system in light and dark themes, with the interface colours: labels, buttons, select fields, protocol cards and tooltips.

⑤ Document the decisions, for AI agents too

We document flows and decisions for the team and for usability engineering, and write rules in a DESIGN.md that agents such as Claude Code, Codex or Cursor use as context.

  • Documentation for the development team
  • Material for usability engineering
  • A DESIGN.md for AI agents
«Moze helped our company’s growth journey get started, with a focus on a better user experience for our customers. Our collaboration with Moze has been the first fundamental step towards positioning our products in the cloud software market for corporate compliance.»

Andrea Garganico Product Design Director & CPO, NSI

Medical projects

Frequently asked questions