Link context documents to patient profile
Joseph Power
Allow uploaded context documents to be linked to a patient profile such that they load as context for every subsequent session with the same patient. This would also be fine if a local directory could be specified for each patient the same purpose. Allow this to be done separately from linking past Heidi sessions.
Joseph Power
Thank you. This may also be covered by integration with clinical management apps (e.g. Clinic to Cloud which I have raised elsewhere).
- Letters (referrals, my letters, past reports etc.), forms (patient registration, psychometrics etc.), pathology results. They do not change often but rather accumulate with subsequent visits. Pre-loading context documents each visit is a significant time sink.
- For me, it would be best if the documents autopopulated the context tab and could then be selected to include/exclude or persist/desist. E.g. initial referral would be included every time, newly completed psychometrics would be added as they arise, previously reviewed pathology does not need inclusion at subsequent visits and would desist.
- This question is probably better answered by Heidi given e.g. server costs, load times. One-time import may be better given possible constraints on users' permission/ability to store clinical documents locally.
Heidi Team
Thanks for sharing this — linking “always-on” context docs to a patient profile would be a big time-saver, especially if you’re seeing the same patient multiple times a day.
Just to make sure we capture it correctly for the team:
1) What kinds of documents are you wanting to persist (e.g., referral letters, PMH summaries, care plans, imaging reports), and do they change often?
2) Should these docs auto-load into the Context tab for every new session with that patient by default, or would you want a quick toggle to include/exclude them per visit?
3) For the “local directory per patient” idea, are you thinking Heidi watches a folder and keeps it in sync, or just a one-time import from that folder?
We’ll share this with the product team — it’s a great complement to how patient sessions can already be linked for historical context, but with persistent documents handled separately.