Feature Requests

Heidi Issues when used without EHR Integration
This is feedback already given to the Support Team at Heidi, I have been asked to include this on here for the product development team. I feel a lot of the underlying issues are due to using Heidi without an EHR integration (my Trust uses Cerner, like many in the UK, which is not supported by Heidi). Recent Update 23/06/26 No longer have past/upcoming sessions Sessions no longer divided by date, visually very cluttered Date filter works by the date the sessions were created, not the date of the clinic (see attached ‘Date Filter’) Default is reverse chronological order (I assume as days no longer separated?) Managing Preparing Clinics without EHR Integration The recent updates to the workflow appear to be directed towards creating patients, rather than unlinked sessions. Any edit to a session name defaults to creating a new patient (see attached ‘create new patient’). I don’t think this would be as much of an issue if it was possible for Heidi to import session information to create patients. Currently, no matter what format I use, Heidi will only create unlinked sessions. Our patient lists are generated as Surname, First name - so I have to manually reverse this for every session (and now need to click ‘create unlinked session’ every time I make a change - which wasn’t required before). The alternative workflow is: Print Screen > Paste data from image into Excel > Text-to-columns > Reorder & label columns > Save as CSV > Import into Heidi When trying to prep a clinic - it is helpful to have headline information at a glance (reason for attendance, patient age, gender, do patients need an audiogram on arrival (AoA) etc). The only way to do this is by having this information in the session name (see attached ‘Prepped Patients’). Heidi now generates a similar summary, but this cannot be entered/edited by the user until after the session is transcribed - it remains ‘untitled session” until then. Date of birth/age is only available if entered manually and even then, only visible by hovering over the patient details (see attached ‘Patient Details’). I am sure all of this is dramatically easier with EHR integration but, for those of us stuck without it, Heidi is becoming more and more cumbersome to use.
0
·
Teams
Notification Preferences for Support Tickets
Support Ticket Notification Preferences Summary Allow users to choose how they receive support ticket communications and notifications, including the ability to receive support messages exclusively through their preferred platform. Problem Currently, when a Heidi support team member responds to a support ticket, notifications are delivered across every device and platform where the user is logged into Heidi. This can result in multiple duplicate notifications for a single support message. Reading or responding to a support message on one platform does not always clear the notification state on other devices, requiring users to manually dismiss the same notification multiple times. Impact For clinicians actively seeing patients, these duplicate notifications can: • Interrupt patient care workflows • Create unnecessary distraction and cognitive load • Require repeated manual dismissal across multiple devices • Contribute to notification fatigue Requested Enhancement Allow users to select their preferred method for receiving support communications, such as: • Email only • Desktop app only • Mobile app only • Browser only • Any other single platform of their choice Additionally, support message notifications should automatically sync across devices so that once a message has been read on one platform, it is marked as read everywhere. Expected Benefit Providing notification preferences for support communications would reduce workflow interruptions, improve focus during patient care, and give users greater control over how they interact with the Heidi support team. [Request submitted 06/01/2026]
0
·
Teams
Load More