Skip to content

Lab Results Patient Communication Drafter

Example prompt: "When a lab results email arrives, match it to the patient in our Google Sheet, draft a one-page clinician summary in Google Docs, and draft a templated 'your results are back' message to the patient — leave everything as drafts until the clinician has reviewed."

The Problem

Lab results land in a clinic inbox and the meter starts running. A normal result still needs the patient to be told it is normal; an abnormal result needs the clinician's eyes today, not Thursday; an urgent flag needs the clinician's phone to ring. Most small practices run this by hand: reception spots the email, prints the PDF, walks it to the clinician, the clinician reads, the clinician dictates a reply, reception types it up and sends. Every step has somewhere a result can get stuck for a day, the wrong patient can be named in the reply, or a clinical interpretation can leak into the patient message before the clinician has actually read the file.

How GloriaMundo Solves It

We build a workflow on the practice's results-only inbox. An integration step accepts emails only from the trusted senders listed in the 'Lab Senders' tab — anything from an unknown sender does not enter the workflow at all. For trusted emails, the workflow parses the patient code from the subject (deterministic by design; we never infer identity from body free text), looks the code up in the 'Patients' tab, and only saves the PDF under the patient's name once the lookup returns exactly one matching row. If the parse fails or the lookup misses, the attachment goes to a neutral quarantine folder and the workflow hard-fails to Slack so a human resolves identity before anything else happens. For matched results, the workflow logs the result, builds a short clinician review pack with the patient's prior tests and a decision block, and drafts both the clinician's brief and a content-free 'results are back' message for the patient. Nothing auto-sends. The Slack one-liner and the 8am daily summary use the patient code only — the named clinician opens the pack to see who and what. Glass Box preview shows every drafted message, the Drive paths, and the routing logic before anything is queued.

Example Workflow Steps

  1. Trigger (integration): A Gmail message arrives at results@ourdomain.com from a sender listed in the 'Lab Senders' tab.
  2. Step 1 (integration): Parse the patient code from the email subject; pick up test name, sample date, and urgency flag from the subject or first line.
  3. Step 2 (integration): Look the patient code up in the 'Patients' tab. If the lookup returns exactly one row, continue on the matched path; otherwise jump to Step 7.
  4. Step 3 (integration): Save attached PDFs to the 'Lab Results' folder in Drive under the patient's code.
  5. Step 4 (integration): Append a row to the 'Lab Results Log' with the patient code, test, sample date, lab sender, PDF link, clinician, and urgency flag.
  6. Step 5 (llm): Build a 'Results review pack' Google Doc with the patient details, a plain-language description of the test, prior same-type results, and a clinician decision block.
  7. Step 6 (integration): Draft a Gmail to the clinician with the pack linked, and a templated content-free 'results are back' Gmail to the patient. Post a Slack one-liner in #clinical-review with the patient code, urgency, and links — drafts only, nothing sent.
  8. Step 7 (conditional): For unmatched results, save the attachments to a neutral 'Lab Results/Quarantine' folder and post an 'UNMATCHED RESULT' Slack message with a neutral identifier and the Gmail link — no clinical detail in the Slack body.
  9. Step 8 (integration): At 8am, post a daily review queue in #clinical-review grouped by clinician with the patient-code-only convention.

Integrations Used

  • Gmail — read inbound results from trusted senders; draft the clinician brief and the patient message
  • Google Sheets — the 'Lab Senders' allow-list, the 'Patients' tab for the lookup, and the 'Lab Results Log' for the audit trail
  • Google Drive — store lab PDFs under the patient code, or in a neutral quarantine folder when identity is not yet confirmed
  • Google Docs — the 'Results review pack' the clinician reads before deciding
  • Slack — the #clinical-review one-liner per result (patient code only), the 8am daily summary, and the unmatched-result alert

Who This Is For

Private GP practices, mental-health practices using rating-scale-based monitoring, vets receiving lab panels for in-clinic and external samples, and any small clinic where lab or test results arrive by email and the chain from inbox to patient touches three or more people. Works best where the practice can ask its lab providers to include the patient code in the subject line so the parse is deterministic.

Time & Cost Saved

A practice receiving 20-40 results a week typically loses an hour a day to manual triage — reception spotting, printing, routing; clinician searching for prior results; reception typing the eventual patient message. This workflow does the matching, the pack-building, and the drafting in seconds per result. The clinician opens the pack, ticks the decision, and the patient draft is there to adjust and send. The larger gain is risk reduction: an urgent flag at the top of the clinician's inbox subject and an 'UNMATCHED RESULT' alert in Slack are much harder to miss than a printed PDF in an in-tray, and the templated patient comms cannot accidentally contain clinical content because the workflow does not generate any.

Notes on Auto-Send vs Drafts

Nothing auto-sends. The patient-facing message is templated and content-free on purpose — it says results are back and a clinician will be in touch, and that is the message the clinician approves with one click. Any clinical wording lives in the clinician's reply after they have read the pack, which is its own draft for their voice and their judgement. The workflow never interprets a result.