Nordhealth | Oslo | 2025
Impactful Design Improvements
Objectives
With the long-term migration of our product from the legacy to the new front end, we are making small but impactful design updates to the product section by section, and page by page.
Below are 4 different different yet connected problems I tackled for our product; an example of how we are managing the migration and the improvement process.
1. Financial information restrictions
Prevent users from viewing or editing financial information for clinic locations they are not authorized to access.
Legacy solution approach (phase 1)
Replace financial data and consultation links from unauthorized clinics with a ‘[No Access]’ placeholder. A tooltip will provide context, explaining why access is restricted.
New front end approach (phase 2)
Rebuild the tables in the new front-end, ensuring that actions are properly restricted. This will allow us to lock specific functionalities and viewpoints while still preventing unauthorized visibility of financial information.
Product pattern
Difference between no access due to user permission in their own clinic location due to their role, vs not having access to other clinic locations.
2. Page layout & global CTA placement
As part of our efforts to improve and streamline the Clients & Patients page, we relocated the following buttons, that were floating on the side, to the top for better accessibility and a cleaner layout:
Tools (rename to Actions)
New (rename to Create new)
Integrations
Move Counter sale inside Create new
Move Show images of patient under Actions
Move Communication preferences icon (green phone icon) to client info bar
Legacy solution approach
Implementing simple and minor changes to help a quick development turnaround, while minimizing users friction with the new updates.
New front end approach
Updating the Client & Patient Info Bar to align with the new design direction, which reduces visual noise, and better organizes essential information for our users.
Out of all the information on this, the communication preferences is the least critical and important information. The goal was to use an icon so the user can quickly identify what the status of the communication preferences are, so if they need to update that, they take action when the time is right.
3. Transactions tables
The Finances team requires the Billing tab to be split into two separate tabs: Account management and Transactions.
Account management will retain all existing features of the current Billing tab, except for the following tables, which will be moved to the new Transactions tab:
Prepayments
Payments
Invoices → Will be split into two separate tables: Invoices and Credit notes.
I. Action buttons on tables
Below are the actions on the tables in the legacy. I redesigned and updated the CTAs on tables for better communication, a cohesive design, and easier to understand.
II. Bulk action
Improving the bulck actions in legacy: Updating the Client & Patient Info Bar to align with the new design direction, which reduces visual noise, and better organizes essential information for our users.
New bulk action design
A new design direction to make it easier for users to select multiple rows and take actions.
New filters design direction
One of the first places we are introducing our newly designed filters is on the Invoices and Credit notes tables: Filter by Clinic location.
4. Active consultation overview
To display number of active consultations, helping clinic staff identify any that remain open and take necessary actions to close them if needed.
Displaying active consultations on the same bar as the page-global action buttons ensures visibility and accessibility across all tabs within the Patients & clients section.
Although some of the design changes were minor, they do add up to improve the user experience of Provet Cloud. Most of these changes are also directly or indirectly influencing other pages and features of the product.
Working on these projects sparked conversation around setting well defined but flexible rules for complex product such as Provet Cloud. If you are interested more on this topic feel free to read more about it in my post:
