Feature Requests

It takes too much time to go to context for each patient and tick to include previous sessions as context. I'd like there to be a global setting that I could toggle on to include the last x number of sessions for all patients. I already found it wastes time to have to do this for each patient session, but since an update yesterday I now have to click the calendar icon and then tick each session, it wastes even more time.

It would be nice to be able to edit the transcript, i.e delete certain parts not relevant or confusing info captured during the consultation.

It would be very helpful if Heidi could label speakers in the transcript ("Speaker 1", "Speaker 2" etc) as it is quite time consuming going through the transcript afterwards and having to figure out when I spoke vs when the patient spoke.

User wanted to link more than 3 past sessions as he is a Psychologist with having to generate from 6 appointments or more.

I just discovered that the "tidy up" button which deletes empty sessions also deletes upcoming sessions. It seems logical that the upcoming sessions should be excluded from being cleaned away.

I copied previous visits of a patient into the context section and wanted Heidi to give me a summary, using my summary template. I did not want to generate it without transcription.

It would be nice if some sort of sound/notification could be made if there is an issue with the microphone picking up the audio? I am not often looking at the Heidi window when in a session and can't therefore tell if there are issues with the recording. I have had a few consultations that were not transcribed due to this reason. Very frustrating.

It would be helpful to be able to archive or "check off" notes for sessions that have been copied and completed so when my list can be decluttered during shifts where I see 20+ patients.

After a note is pushed to the EHR (in our case, Athena), there is no persistent indication that this has already been done. This sometimes leads to duplicate pushes and lots of deleting later on. If the status went to "Sent" after the note was (literally) sent, this would prevent this problem.