Post-clinic letters and follow-ups

A Rhazes workflow that turns a recorded consultation into a clinic letter and the follow-up tasks it generated, in a single run.

Updated

The problem

The consultation is the easy part. What takes the evening is the letter, and the three things you meant to arrange afterwards that are now on a sticky note.

Doing them later means reconstructing the encounter from memory, which is both slower and less accurate than writing it while it is fresh.

The steps

  1. Patient details and Patient record. The letter is written in context rather than from the transcript alone, so it can refer to the history properly instead of only what was said aloud.
  2. Sources, pointed at your service conventions if they are written down: how letters are addressed, what they must include, house style on abbreviations.
  3. Ask Rhazes to draft the letter from the consultation. Say what it must always cover: the working diagnosis, what was discussed, what was agreed, what was prescribed or changed, and the safety-netting advice actually given.
  4. Document, using your clinic letter template. See Templates.
  5. Create tasks for what the consultation generated: the investigation to arrange, the result to chase, the review to book. Set due dates relative to the visit rather than leaving them undated.
  6. Output the letter for you to check.

Running it

Record the consultation, then run the workflow from that chat. See Recording a consultation in Rhazes.

Correct the transcript first if anything important came out wrong. Everything downstream is written from it. See Reading and editing a transcript.

Adjusting it

If you write to patients as well as to their GP, add a second Document step with a patient-facing template. One run, two letters, written from the same encounter and therefore consistent with each other.

What to check

The letter, properly, before it goes anywhere. Read the medication names and doses, the follow-up interval and the safety-netting paragraph hardest, because those are the parts a fluent draft makes easiest to skim past.

Check the tasks too. A workflow that files a follow-up for the wrong interval is worse than one that files none, because you will trust it.

Related articles