TEAM
Two designers: me and my design manager
Making legacy healthcare tools feel like one product
RLDatix makes software for hospitals and healthcare teams. Its tools help them manage safety, risk and staffing.
During COVID-19, I was one of two designers on the risk platform. I led research and design, from shared patterns to how people review risks and report incidents.
I OWNED
Research, interaction design, UI library, usability testing
WORKED WITH
Product, Engineering, support and clinical experts
DCIQ
OverviewRisksReportsActions
LS
Legacy risk registerLater public dashboard
Explore two screens: a legacy risk register and a later public dashboard. They show the kinds of work in the platform, not a direct before-and-after of one screen.
A shared foundation, used in practice
Client organisations
Tested Icon Wall template creation and management with four major clients.
Research scopeConfiguration journey
Brought three separate admin flows into one connected experience.
Design changeCustomer workflows
Redesigned risk-management screens went into day-to-day customer use.
Delivery outcomeWhat I learned
A consistent platform needed more than visual polish: shared component behaviour, practical local configuration and terminology clinicians already understood.
Bringing fragmented healthcare tools together during COVID-19
Datix Cloud IQ (DCIQ) brought incident reporting, risk and patient safety into one platform, but its legacy tools still worked differently.
COVID-19 put healthcare teams under greater pressure, so these workflows had to become clearer and more consistent.
Hard to navigate
Mixed navigation levels and inconsistent layouts made it difficult for staff to know where they were or what to do next.
Unclear feedback
Vanishing menus and unclear system responses interrupted tasks and left staff unsure whether an action had worked.
Repeated work
Without shared components, product teams solved the same interface problems separately. We needed patterns they could reuse.
The audit showed the same problems across navigation, forms and tables, so one fix could improve many screens.
Healthcare staffReport an incidentRisk teamsReview records and follow upLeadersSee priorities across the organisation
Build common patterns from what people need
Clinicians and client teams showed us where navigation, forms and feedback got in the way. Those problems set the priorities for a shared library.
I worked with Engineering on reusable navigation, forms, tables, icons and status messages.
RLDATIX / SHARED UI LIBRARYA shared language.
A shared language.
Across every workflow.
Reusable foundations for clear actions, familiar navigation and consistent feedback.
Foundations → Components → Workflows
Component examples from the shared library
INPUTS & ACTIONSOrganisation unit
Adult Directorate
STATUS & FEEDBACK
ApprovedIn progressOverdue
✓ Changes saved| Risk | Owner | Status | Next action |
|---|---|---|---|
| Clinical handover | Governance team | In review | Review controls |
| Reporting guidance | Quality team | Approved | Publish update |
| Staffing escalation | Ward lead | Overdue | Confirm owner |
Overview›
Risk registers›
Risk trackers›
Reports›
!
Review handover controlsClinical safety · Governance teamOverdue
›✓
Update reporting guidanceQuality improvement · Quality teamApproved
›Clinical safetyWorkforceQualityAdult Directorate ×In review ×
Help people see what needs attention
Teams needed a quick view of what needed attention, and the detail behind it. So we paired a risk overview with detailed lists.
Start with the overview
The matrix groups risks by likelihood and impact, so teams can scan the overall picture.
Show the next action
Owners, status and overdue actions show who needs to follow up.
Keep the detail
Detailed tables remain available for reviewing each risk and its next action.
REPORTING JOURNEY
From first signal to follow-up
Four screens show how a staff member could report an incident and see what needs attention.
DCIQLS
STEP 1 OF 3
What would you like to report?
Choose the event that best describes what happened.
DCIQLS
STEP 2 OF 3 · PATIENT SAFETY
Tell us what happened
●
Add a voice noteRecord a short description
You can review your note before submitting.
Save draft
DCIQLS
STEP 3 OF 3
Review your report
Check the details before you send it to your team.
Report typePatient safety
SummaryMedication dose checked before administration
Voice note▶ Listen · 0:24
Your report will be shared with the appropriate safety team.
Back to edit
DCIQLS
FOLLOW-UP
Actions needing attention
Keep owners, due dates and status together.
Review handover controlsClinical safety · Governance team
OVERDUEDue 12 Oct · Assigned to youOpen action ›
Update reporting guidanceQuality improvement
IN PROGRESSDue 18 Oct · Quality teamView details ›
Make it easier to report a new incident
Staff needed a clear route from an event to the right report, so I used labelled icons and categories. Client teams needed to manage local options, so I brought three configuration flows into one.
Part of the original clinical icon library.
Swipe to explore the four parts of the experience.
Test the decisions.
Listen to the people using them.
I tested the designs with healthcare professionals and used their feedback to decide what to keep, change and improve.
A DECISION CHANGED BY RESEARCH
Familiar language mattered more than a simpler label.
- 01 / HYPOTHESIS
Try a clearer name
Could “Grouped Risks” make “Risk trackers” easier to understand?
- 02 / FINDING
Familiarity was clearer
Clinicians already understood “Risk trackers”. A new label added confusion.
- 03 / DECISION
Keep the term. Improve the flow.
I kept “Risk trackers” and improved navigation hierarchy and the visibility of risk actions.
THE TAKEAWAY
Simplifying the interface doesn’t always mean changing its language.
PROTOTYPE FINDINGSWhat we refined.
What we refined.
What came next.
Refine the experience
Sessions highlighted navigation and dashboard content that needed work.
Plan the next iteration
Printing, sharing and a personal dashboard became priorities for later work.