Skip to main content

What is "Context”?

How to get the most out of Heidi's 'Context' feature.

Updated today

Context is where you capture everything that doesn't need to be said out loud.

Clinicians don't say everything they're thinking during a visit. That makes it hard for Heidi — or any scribe — to build a complete picture of what actually happened. Context is the solution: a space to add your own notes, observations, and clinical details before, during, or after a session, without them entering the transcript.

You can write in shorthand, add examination findings, clarifications, symptoms, test results, reminders, or action items — anything that belongs in the note but not in the spoken record.

Access Context in the tab next to your session notes.

Example uses:

  • "Patient appears distressed and dishevelled"

  • "Possibly seeking stronger pain medication — answers inconsistent"

  • Vital signs recorded manually during exam

  • Screening questions you want reflected in the output


Uploading files to Context

You can upload files directly into Context — Heidi reads them alongside your transcript and notes to produce more complete, accurate documentation. No extra steps needed.

Supported file types

Heidi accepts PDFs, Word documents (.doc, .docx), and images (.jpg, .png). This includes scanned files, handwritten notes, and documents with tables, lists, or mixed content — Heidi handles them all automatically.

How to upload a file

In the Context tab, click the paperclip icon and select your file. Once processing is complete, the file is ready for Heidi to use. You can upload files at any point — before, during, or after a session. If you add files later, ensure you press “sync changes” to have them incorporated in your note.

What you can upload

Anything that contains clinical information useful for documentation. Some common examples:

  • Pathology and lab results

  • Discharge summaries and specialist letters

  • Imaging reports

  • Patient intake forms

  • Handwritten notes or photographs of clinical documents

Generating a note from files only

You don't need a live session to generate from uploaded files. Add your files to Context, then click Create at the top right and choose a template. Heidi will generate your note or document from the uploaded content.

💡 You can also use Ask Heidi to query or summarise the contents of an uploaded file — useful for quickly pulling specific details before or during a consult.


Separating merged patient sessions

If you start a second patient session before ending the first, the transcripts can merge into a single session. Here's how to separate them:

  1. Locate the merge point — identify where the first patient's session ends and the second begins in the transcript.

  2. Copy the relevant block — copy the section of transcript relating to the first session.

  3. Open a new session for each patient and paste the relevant transcript into the Context tab.

  4. Label clearly — add a header like "Visit with [Patient] on [Date]" to avoid future confusion.

  5. Generate your note — click Create at the top right, then choose your template.

  6. Review and finalise — check each note for clarity and completeness.

💡 Read more about this quick fix in the following article: How to Separate Merged Patient Sessions in Heidi


Adding a previous visit to the current session

Referencing details from a patient's past visit can strengthen continuity and clarity in care. Here's how to bring prior context into a new session:

  1. Start a new session and locate the patient's past session notes.

  2. Copy key details — observations, treatment plans, or anything relevant — and paste them into the Context tab of the current session. Label clearly, e.g. "Context from Initial Visit on [Date]."

  3. Generate your note — click Create at the top right and choose your template.

  4. Customise if needed — adjust the template to differentiate past context from new observations.

💡 For more details around linking previous sessions, see the following article: Linked Previous Sessions

Did this answer your question?