Feature Requests

Shared patient database for Practice/Team accounts
We use Heidi Practice with multiple clinicians and would strongly benefit from a shared patient database across the whole team. At the moment, patient profiles appear to be tied to the clinician who created them. Other authorised team members can view sessions from another clinician, and we can share templates and documents, but they cannot start a new session on their own mobile device using an existing patient profile created by another clinician. This creates a major workflow problem for a multidisciplinary or shared practice: A patient may be treated by different practitioners at different appointments. If Practitioner A created the patient, Practitioner B should be able to open the same patient profile on their tablet, start a new session, and have that session automatically become part of the same longitudinal patient record. Currently, the workaround would be to create the same patient again under Practitioner B. This leads to duplicate patient profiles and fragmented documentation, with sessions, notes, documents and treatment history split across different patient records. Suggested solution: One shared patient database for the entire Practice/Team workspace. Authorised team members can access the same patient profiles according to their permissions. When starting a session, the clinician simply selects the existing patient and their own practitioner identity. Sessions created by different clinicians are stored under the same patient profile. The full patient history, documents, treatment plans and previous sessions remain connected regardless of which clinician treated the patient. This should work on desktop, web and mobile/tablet apps. Admins should be able to define which clinicians can access which patients if more granular permissions are required. Example workflow: Patient is created once on our practice computer. Practitioner A treats the patient and creates a session. Practitioner B later opens Heidi on a tablet, selects the same patient and starts another session. Both sessions remain connected to the same patient profile. Either authorised practitioner can later review the complete treatment history. For a Practice/Team account, this would make Heidi function much more like a true shared clinical workspace and would avoid duplicate patient records and fragmented longitudinal documentation. For our practice, this is one of the most important missing team features
0
·
Notes
Hydrating data from previous notes.
Currently it appears that Heidi ignores previous notes despite efforts I make in template to review previous notes. I thought it would be a given. Currently it is painful to have our own medical software plus heidi and having the time to attempt to hydrate fields in one, let alone two programs. It would be good as a simple measure that Heidi would understand to review previous contacts for simple data like, diagnosis, job role, etc that can be brought forward. The only way to do this and where it was unfortuantely working well was cutting and pasting the entire notes history from Zedmed and pasting it to Heidi context. Once the fields were populated, despite having that history in previous notes, no attempt is made to obtain that data in the consult. So the only connection appears to be 'have I seen this patient before = yes => consult number becomes x+1 Beyond that there is little value in the connection unless it is explicitely asked as a task. This does not appear to be automatable. Heidi helpfully suggested I populate the patient data fields. I would ask, if I do that when I first meet the patient, why does heidi not do that automatically? I will manually select the name and can correct issues being parsed from transcript to patient details as a one off to become canon after which the patient details can become master, but it doesn't do it at all. There must be a way to allow heidi to do from previous notes when requested in template, the same that it does if that data is pasted to context.
1
·
Notes
Load More
→