Feature Requests

Hi Heidi team, I’d like to suggest a feature that I think could significantly broaden how clinicians use Heidi on iPhone: a system-wide Heidi keyboard with “Dictate Anywhere” functionality. The concept would be a custom iOS keyboard that can be selected anywhere the standard keyboard appears — Mail, Messages, an EHR, referral portals, browser-based systems, Notes, Microsoft apps, etc. Within the keyboard, there would be a dedicated Heidi button using the existing yellow Heidi icon. Tapping the Heidi button would start Heidi dictation and insert the resulting text directly into the active text field. In other words, rather than having to open Heidi, dictate, process the text and then copy/paste it into another application, Heidi would effectively become available wherever the clinician is already typing. I’ve attached/mock-uped the idea. The workflow I envisage is: Clinician opens any text field in any iOS app. Standard keyboard appears with a yellow Heidi button beside the emoji/globe control. Tap Heidi → Heidi begins listening. Speech is transcribed and cleaned up using Heidi’s existing AI. The finished text is inserted directly at the cursor position in the current app. Ideally, users could choose modes such as verbatim dictation, polished clinical dictation, or perhaps configurable shortcuts/templates. For clinicians, this could make Heidi much more than an ambient scribe. It would turn it into a genuinely system-wide clinical dictation layer for iOS. I could dictate an EHR note, an email to a colleague, a referral, a radiology request, a message to my secretary or a clinical letter without changing applications. A simple positioning for the feature could effectively be: Heidi — Dictate anywhere. I appreciate there may be restrictions around what an iOS keyboard extension can do with microphone/audio access, security and third-party applications. If direct audio capture from the keyboard is restricted, it would still be worth investigating the cleanest Apple-supported architecture that produces the same user experience — for example, using a keyboard extension in conjunction with the main Heidi app or whichever extension/API Apple makes available. There are similar apps wisper flow and superwispr. Future iPhone Duo / foldable iPhone support I would also strongly suggest that Heidi plans early for Apple’s expected next-generation/foldable iPhone form factors. If Apple releases an iOS 27 SDK with APIs for a dual-screen/foldable “iPhone Duo”-type device, it would be fantastic to see Heidi ready at or close to launch rather than simply scaling the existing iPhone UI. The larger internal display could be particularly useful clinically. For example, Heidi could take advantage of the expanded workspace for: * EHR or browser-based clinical systems with the Heidi keyboard across the bottom. * Simultaneous transcript/clinical note views. * Larger ambient-recording controls. * Review and editing of generated notes alongside source information. * Better multitasking between Heidi and clinical applications. * Seamless continuity between the smaller external display and the unfolded internal screen. The attached concept illustrates both ideas: Heidi Dictate Anywhere integrated into the system keyboard on the outer screen, and the same functionality being used to dictate directly into an EHR on the larger inner display. I think these two developments could make Heidi feel much more deeply integrated into the clinician’s device rather than being another standalone application. Best wishes, Andrew

Hello, in the Team setup, we are unable to search patients’ records across all team members simultaneously. Meaning I have to search each member’s record separately. This takes a long time. Can this be fixed? Such search isn't available on the mobile app at all. This prevents us reading the records in the hospital wards, ICUs, dialysis centres etc. It seems like Heidi is not supporting specialists needs like it does for GPs.

Can you please allow access to heidi web from web browsers on iPadOS? Previously, I (and our ipad-based team) could access the website (and all of its features) from my iPad. It looks like now the website forces the app to open. As the app does not allow many of the website functions, this is having a significant impact on our team - specifically related to template creation and customization. The only way to do this now (it seems) is to select "open website for full settings" from within app settings. As this is a window-in-a-window it it less than ideal.

Enabling residents to connect securely to a specific session and use their phones as a microphone; scan a QR code on a session to load a patient then it securely saves so I can expand my team out beyond my personal phone + laptio.

Please add passkey support for Heidi accounts using FIDO2/WebAuthn. This should support platform passkeys such as Windows Hello, Touch ID, Face ID, Android passkeys, and roaming hardware security keys such as YubiKeys. Ideally, passkeys should work both as a passwordless login option and as phishing-resistant MFA, with support for registering multiple passkeys per account. For Teams/Organisations, admins should be able to require passkeys or security keys for higher-risk accounts. This is especially important for healthcare because Heidi accounts contain or access sensitive clinical information. Current MFA options such as SMS and email are less secure and can be frustrating in a busy clinic workflow, while authenticator-app codes still add friction. Passkeys would improve both security and day-to-day usability for clinicians moving between devices, rooms, and browsers.

Please add a signed MSIX/MSIXBundle build of Heidi Desktop, alongside the existing EXE/MSI installers, and use it for Microsoft Store distribution. This would be particularly valuable for Heidi because many clinicians use managed organisational PCs where they cannot install arbitrary downloaded applications or do not have administrator rights. MSIX would provide: Microsoft Store installation and seamless automatic updates A signed package that organisations can deploy directly through Intune, Configuration Manager or similar management systems Silent IT-managed installation without requiring clinicians to have local administrator rights Easier application allowlisting using Heidi's publisher/package identity rather than changing executable hashes Cleaner installation, updating and removal A standard package that IT teams can deploy without having to build/repackage their own Heidi installer Direct organisational deployment even where the Microsoft Store is disabled Ideally Heidi would provide the signed MSIX/MSIXBundle as a direct download as well as through the Store, optionally with an .appinstaller feed so directly installed copies can also update automatically without an organisation having to create and maintain its own update package. The existing EXE/MSI installers should remain available for compatibility. The goal is essentially to provide a first-class, Windows-native deployment and an easy seamless update path for both individual users and managed healthcare environments.

Can we share snippets across the enterprise account or off to share across teams? Multiple guidelines and education components that need to be standardised, but not necessarily part of the template.

Hi, A general point before any further feature work: the existing bugs need to be fixed first. Building new functionality on top of unresolved problems doesn't make the product better — it makes it heavier to use. Two in particular. PDF forms cannot be printed directly from Heidi. The current workflow is: download the document, find it in the file system, open it, then print it. Four steps for something that should be a single click. In an emergency department this isn't a minor inconvenience — it's friction repeated many times per shift, at moments when there are no spare seconds. A print button that sends the form straight to the print dialog would solve it entirely. That's the expected behaviour in essentially every clinical application I use. Patient details are not populated from a photograph. When I photograph a page containing last name, first name, date of birth, address and phone numbers, all of that should fill the patient information fields automatically. Instead I retype it by hand for every patient. I'd class the second one as a bug rather than a missing feature, because the capability is already there. Heidi reads and interprets that exact same photo elsewhere — my templates rely on it to identify which hospital site the patient is at, and it works reliably. So the extraction isn't the problem. The identity fields simply aren't being populated from data Heidi has already parsed. Both of these are daily friction on every shift. I'd really like to see the teams prioritize them over new development. Best regards, Pierre-Yves Caffin, MD Emergency Physician

Jacqui suggests that aside from the team owner, certain members can change the retention period of the team

Arnaud suggests a 'What's New' popup notification system when opening Heidi Labs presenting the changes succinctly with two buttons: 'Dismiss and Remind' to reopen later and 'Dismiss' to not reopen. It also offers a Heidi Labs button with features activated, allowing you to selectively deactivate features without leaving Heidi Labs. When disabling a feature, a popup would ask why ('do you want to tell us why you don't like the feature? ') with an answer option or not. This would allow for committed and motivated beta testers with targeted feedback on changes.