A product that provides quick access to comprehensive clinical, coding, financial, and regulatory reference data.
Trisus Reference
OVERVIEW
Trisus Reference is Craneware’s all in one data solution for chargemaster reference data. It provides Craneware’s users with dedicated resources and tools to provide clinical, code, financial and regulatory data. The product is a SaaS product that users access as part of the Craneware Trisus product suite.
Trisus Reference consists of two solutions:
-
The Trisus Reference Toolkit
-
The Trisus Reference Assistant
TRISUS REFERENCE TOOLKIT
The Trisus Reference Toolkit is a comprehensive regulatory data solution that provides Craneware’s Trisus users with a variety of Chargemaster compliance data. The product is a standalone module that users utilise to query data for day-to-day Charge Description Master maintenance and auditing to ensure compliance is met against government defined regulation.
TRISUS REFERENCE ASSISTANT
Trisus Reference Assistant is a streamlined version of the Trisus Reference Toolkits core regulatory search functionality. The product provides one click access to the data search function provided by Trisus Reference Toolkit accessible from all Craneware products across the Trisus platform.
THE PROBLEM
As part of Craneware’s transition from its legacy product suite to the Trisus platform, the existing Online Reference Toolkit required a redesign to bring into alignment with the existing Trisus products.
UX RESEARCH
Online Reference Toolkit (ORT) Customer Survey
A customer survey was sent out to over 15,000 existing ORT users and consisted of 20 questions surrounding usability, functionality and satisfaction. The returned results were analysed, once complete I identified key areas of change of the existing product to be incorporated into Trisus Reference. This allowed me to narrow the scope of the existing modules that I would recommend be a focus in the transition to the Trisus platform.
Internal stakeholder interviews
Designated stakeholders from across the business were selected to participate in interviews, with 10 individuals from 6 different departments of various technical, domain and industry knowledge. This gave me further insight into the Craneware perspective of the product and how it compared to the use cases specified by customers. These findings allowed me to further refine the product requirements.
PERSONAS
By creating the personas for our existing ORT users this allowed me to align my design choices for the product with the needs of our customers. As almost half of our user base viewed themselves as ‘All-Rounders’, as they have many responsibilities across their organisation and priorities shift on a day-to-day basis. These users must trust the information presented to them as a single source of truth. This allowed me to focus on meeting the needs for a significant portion of our legacy users with my design, while ensuring the product met the requirements of the entire user base.
USER JOURNEY
My next step was to visualise the journey for the identified personas. This provided the key interactions that the users would make with the product and provided me the basis for my low fidelity wireframes.
Trisus Reference Toolkit
Code search in Trisus Reference Assistant
Keyword search in Trisus Reference Assistant
USABILITY TESTING
PREFERENCE TESTING
Wireframes we created for usability testing with 7 participants from 6 hospitals being selected for our focus group. For this I had created two wireframes for comparison which has previously been through internal vetting which led to an A/B test taking place due to internal debate on the direction of the UI. Feedback was gathered from the participants on preference, from the results I identified a split how users interacted with this first set of designs. As a result of this initial feedback, I changed my approach to incorporate aspects of both designs to better reflect the needs of the users.
UI DESIGN
Trisus Reference Toolkit
Final UI
REFERENCE ASSISTANT TRIGGER BUTTON
TRISUS REFERENCE ASSISTANT
Final UI
