Collage of Ucentrix screens: a white blood cell trend chart over a list of blood work reports, the 10-section medical profile menu, and Personal Information, Medications and Family Medical History cards.
Hi, I’m Dokie, Vinu’s supervisor. Short on time? Let me walk you through Ucentrix in 2 minutes.
Ucentrix in 2 minutes
Audio overview · problem, process & solution
2:08

Ucentrix: A SaaS Product Developed for a Medical Clinic

Track & Share Individual Medical Records

Overview

I was the only product designer on Ucentrix, a multi-role health records platform. I took it from first wireframes to a live product in 20 months. Clinics use it to connect with patients, patients keep their full medical record in it, and AI reads their lab reports so they don’t have to type every value

Role

Role

Product Designer

Product Designer

Product

Product

Multi-role health records SaaS Web Application for clinics, doctors and patients

Duration

Duration

20 months

Stakeholders

Stakeholders

Product Designer, 2 Frontend Developers, Backend Developer, Client

Figma

Figma

Design Tool

Design Tool

Figma logo

Platform

Platform

Responsive web and mobile, built in Flutter

Scope

Scope

14 workflows and 114+ screens across a patient portal and a doctor portal

Complexity

Complexity

10-section medical profile, 4+ data-heavy lab report types, AI data extraction, role-based access

The Problem

A wrong number in a health record is worse than a missing one

Health records on their own can be confusing. When all your records are dispersed, it’s difficult to keep track of your health.

The clinic needed one place where patients and doctors share a complete health record. That record is large, varied and mostly locked inside PDFs.

Three things made it hard:

  1. Lots of data, in many shapes 

The medical profile alone has 10 sections. Every lab report type (bloodwork, DEXA, VO2 max, imaging) has its own fields, units and layout.

  1. Typing is slow, AI is fast, and AI can be wrong

Reading a report with AI saves time, but a misread value saved silently is the worst outcome.

  1. Two roles, one record.

Patients own the data. Doctors need to scan it between appointments. Each needs a different view, and the patient decides who sees what.

The design question: how do we make a large, sensitive dataset fast to enter, easy to scan and safe to trust, for two very different users❓

Who it's for

Two groups use the same platform for different jobs, and both need to trust that the data is right and find it fast.

User

Individuals/ Patients

What they need

Want their medical history, medications, allergies and results in one place, and a simple way to share them.

What gets in the way

Today they get scattered PDFs and units they can’t read.

Healthcare
Professionals/ Doctors

Want to review a patient quickly, often between appointments.

Legacy systems give them cluttered screens and make them hunt for the one value that matters.

Because the two portals share one product, I set a rule early: the same components and patterns serve both, so moving between roles never feels like switching apps.

Ucentrix sign-up screen asking “Who are you”, with two role cards, An Individual and A Healthcare Professional, and a Continue to Sign up button, beside a photo of an older couple smiling outdoors.

The system at a glance

System diagram titled “Two portals, one shared record”. A patient uploads a report, AI extracts the values, and the patient approves them before they enter the shared health record. The patient portal (8 workflows) writes to the record; the doctor portal (6 workflows) reads from it and sees only what is shared.

My Process

I worked directly with the clinic and the Flutter developers, in this order:

  1. Requirements Gathering

Interview the business owner for their requirements, competitor product analysis, end user requirements specification

  1. Map Workflows

Split the product into 14 workflows (8 patient, 6 doctor).

  1. Wireframe

Agree on structure in low fidelity before any visual design.

  1. Build the system

One Figma library of buttons, fields and cards for both portals.

  1. Design

114+ final screens for web and mobile.

  1. Validate

Present to the client, receive feedback.

  1. Hand Off

Development-ready designs, plus advice on what screens can’t show, like screen reader labels.

Workflow map for sign-up, log-in and password reset, showing each step as a box with thumbnail screens and red arrows for error flows such as an already-registered email or an expired verification link.

Key Challenges

Challenge 1:

Making AI-extracted data trustworthy

I designed a human-in-the-loop review:

AI reads the uploaded report and suggests values, and a person approves every one before anything is saved. Five decisions shaped it:

AI review screen for a blood work report. The uploaded PDF sits on the left; extracted fields on the right are grouped like the report. A warning banner asks the user to verify the AI-extracted data. An open suggestion shows a reference interval change from 8.4–10.88 to 3.4–10.8, labelled AI-generated, with an Accept button. Discard changes and Confirm and Save sit at the bottom. Annotations: source beside data, mirror the report, one decision per value, say what the AI did, saving is deliberate.

The same pattern covers bloodwork, DEXA and VO2 max, so users learn it once. Uploaded and manually entered reports end on the same review screen, which means one pattern to learn and one place where data is approved.

Challenge 2:

Making dense medical data scannable

Health records are dense by nature, so I made the layout do the sorting. Six patterns carry the whole product:

  • My Medical History screen with a side menu of 10 profile sections, from Personal Information to Health Metrics and Testing Results, next to the Personal Information details. Annotation 1: group by meaning.
  • Blood work report screen with breadcrumbs (My Health Reports, Blood work, file name) and a table of results with aligned Result, Units and Reference Interval columns. Annotation 2: breadcrumbs show where you are. Annotation 3: value and unit together.
  • Diagnostic Imaging reports in a grid, with search, filter and sort controls, a list or grid toggle, and an open menu offering View, Edit, Download Report and Delete. Annotation 4: search, filter, sort.
  • Blood Work page with a line chart of white blood cell count across reports, with 1m, 3m, 6m and 1y range buttons, above a list of blood work reports. Annotation 5: trends over time.
  • Medications section with a Current Supplements table and a collapsed Past Medications and Supplements panel, above a Medication Allergies table where severity shows a coloured dot plus the word Severe, Moderate or Mild. Annotation 6: paged history.
  • My Medical History screen with a side menu of 10 profile sections, from Personal Information to Health Metrics and Testing Results, next to the Personal Information details. Annotation 1: group by meaning.
  • Blood work report screen with breadcrumbs (My Health Reports, Blood work, file name) and a table of results with aligned Result, Units and Reference Interval columns. Annotation 2: breadcrumbs show where you are. Annotation 3: value and unit together.
  • Diagnostic Imaging reports in a grid, with search, filter and sort controls, a list or grid toggle, and an open menu offering View, Edit, Download Report and Delete. Annotation 4: search, filter, sort.
  • Blood Work page with a line chart of white blood cell count across reports, with 1m, 3m, 6m and 1y range buttons, above a list of blood work reports. Annotation 5: trends over time.
  • Medications section with a Current Supplements table and a collapsed Past Medications and Supplements panel, above a Medication Allergies table where severity shows a coloured dot plus the word Severe, Moderate or Mild. Annotation 6: paged history.
  • My Medical History screen with a side menu of 10 profile sections, from Personal Information to Health Metrics and Testing Results, next to the Personal Information details. Annotation 1: group by meaning.
  • Blood work report screen with breadcrumbs (My Health Reports, Blood work, file name) and a table of results with aligned Result, Units and Reference Interval columns. Annotation 2: breadcrumbs show where you are. Annotation 3: value and unit together.
  • Diagnostic Imaging reports in a grid, with search, filter and sort controls, a list or grid toggle, and an open menu offering View, Edit, Download Report and Delete. Annotation 4: search, filter, sort.
  • Blood Work page with a line chart of white blood cell count across reports, with 1m, 3m, 6m and 1y range buttons, above a list of blood work reports. Annotation 5: trends over time.
  • Medications section with a Current Supplements table and a collapsed Past Medications and Supplements panel, above a Medication Allergies table where severity shows a coloured dot plus the word Severe, Moderate or Mild. Annotation 6: paged history.

Challenge 3:

Two roles, one record, patient-controlled access

All 14 workflows read and write the same record, and both portals use the same components, so a doctor reviewing a report sees the layout the patient used to add it. Sharing raises one question on every screen: who can see this? Patients own the record, so they control access:

  • Invite a doctor, step 2 of 3: Review Details and Permissions. A card shows Dr. Michael Chen, Endocrinologist, and the profile sections he will be able to view, with Back to Search and Send Invitation buttons. Annotations: invite doctors; informed access level.
  • Healthcare Professionals page listing doctors with their specialty and a text label for connection and access, such as Connected, Full Access or Disconnected, No Access, beside a Recent Activity panel. Annotation 3: status shown as text, never colour alone.
  • Invite a doctor, step 2 of 3: Review Details and Permissions. A card shows Dr. Michael Chen, Endocrinologist, and the profile sections he will be able to view, with Back to Search and Send Invitation buttons. Annotations: invite doctors; informed access level.
  • Healthcare Professionals page listing doctors with their specialty and a text label for connection and access, such as Connected, Full Access or Disconnected, No Access, beside a Recent Activity panel. Annotation 3: status shown as text, never colour alone.
  • Invite a doctor, step 2 of 3: Review Details and Permissions. A card shows Dr. Michael Chen, Endocrinologist, and the profile sections he will be able to view, with Back to Search and Send Invitation buttons. Annotations: invite doctors; informed access level.
  • Healthcare Professionals page listing doctors with their specialty and a text label for connection and access, such as Connected, Full Access or Disconnected, No Access, beside a Recent Activity panel. Annotation 3: status shown as text, never colour alone.

On the doctor’s side the same rules decide which patients and reports appear, so a doctor only ever sees what a patient has shared.

Built to Scale

A component system for one designer and 114+ screens

Ucentrix component library: patient list rows, a colour palette of tints and shades, checkbox states, action menus, report category list, sidebar navigation states for both portals, file upload dialogs, and lab result field groups.

With no second designer, consistency had to come from the system, not from memory.

  1. Design once, reuse everywhere: Buttons, fields and cards are shared by every workflow.


2. Repeatable page patterns: Every report follows the same structure (source, grouped fields, confirm bar), so a new report type reuses a pattern instead of starting from scratch.

  1. Clear signals: Orange is reserved for primary actions and things that need attention.

  2. Faster handoff: Developers build each component once and reuse it.

Accessibility

I designed to WCAG 2.1 AA, because a health record has to work for everyone. These are the decisions that carry it, and where to see them above.

  1. Colour is never the only signal (1.4.1): Allergy severity, condition status, connection and access level all pair colour with a text label: “Severe”, “Connected”, “Full Access”. See Challenge 2, screen 6, and Challenge 3, screen 3.

  2. Nothing is saved until a person confirms it (3.3.4): AI suggestions are accepted one value at a time. Confirm and Save is the only way data enters the record, and Discard is always one click away. Doctor access is reviewed before an invite is sent and can be changed at any time. See Challenge 1.

  3. Structure a screen reader can follow (1.3.1, 2.4.6): Every value sits in a labelled column with its unit and reference range. Fields have visible labels, and sections have clear headings. Buttons say what they do: “Add Allergy”, not “Add”.

  4. More than one way to find a record (2.4.5): Side navigation, breadcrumbs, and search, filter and sort on every report list.

  5. Consistent everywhere (3.2.3, 3.2.4): Both portals share one sidebar and one component library. Every action menu lists View, Edit, Download and Delete in the same order.

  6. Screen reader labels in the handoff (4.1.2): I specified what assistive tech should announce, such as “Change suggestion for Hemoglobin” instead of “button,” and “Current 12.8, suggested 13” instead of an arrow.

  7. What I’d fix next: Measuring the final screens showed the orange primary buttons reach about 4.1:1, short of the 4.5:1 AA needs, and two small status labels fall short too. Darkening the orange is the first change. I’d also add visible focus states to the component library and a table view for the trend charts.

RELATED PROJECT

RELATED PROJECT

so… want to chat?


Let’s make something
people trust.

End-user needs

Utilitarian Design

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.

so… want to chat?


Let’s make something
people trust.

End-user needs

Utilitarian Design

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.

so… want to chat?


Let’s make something
people trust.

End-user needs

Business goals

That’s the bridge I love to build. I’m open to UX, product design and product roles: on-site in Ontario, hybrid or remote. Or just say hi and show me your pet.

© 2026 Vinuri Hopman. All rights reserved.