Clinical logistics · saying it so care happens
Side-effect communication scripts: how to message an async clinical team so the right thing happens fast
Asynchronous care runs on the quality of your message, and most side-effect messages fail the same way — a vibe (“feeling rough lately”) instead of a clinical picture. The structure that gets good answers in one round-trip: what changed · when it started · how severe (use comparisons and counts, not adjectives) · what you’ve already tried · your specific question — five lines, written like you’re briefing someone smart who can’t see you, because you are. Two boundaries sit above every script: certain symptoms skip messaging entirely — severe or persistent abdominal pain (especially radiating to the back), repeated vomiting with inability to keep fluids, signs of an allergic reaction, or anything your gut labels emergency goes to urgent or emergency care first and the portal second; and no script self-adjusts a dose — the templates below ask hold-or-proceed questions; the prescriber answers them. The five ready-to-adapt scripts, the escalation ladder, and the documentation habit that makes every message count twice.
The five-line structure — why it works on async medicine
Async clinicians triage dozens of threads; messages that pre-answer the triage questions get substantive replies instead of clarifying ping-pong. What changed names one thing, specifically (“nausea after my Tuesday dose” beats “stomach issues”). When gives onset and pattern (“started ~6 hours post-injection, worst on days 1–2, easing by day 4”). Severity uses counts and function, never adjectives: episodes per day, meals kept down, work missed, sleep lost — “vomited twice yesterday, holding fluids since” is data; “pretty bad” is weather. Already tried shows the basics are done (smaller meals, hydration, timing shifts) so the reply starts past them. The question is one sentence with a decision in it: “Should I hold Thursday’s dose or proceed?” Messages shaped this way also become records — the export ritual is quietly building your side-effect history one well-formed message at a time.
The five scripts — adapt, don’t improvise
The nausea-pattern script: “Since moving to [dose] on [date], nausea runs [X] hours starting [when relative to injection], severity: [meals affected / episodes]. Tried [small meals, fluids, timing]. Question: is this expected at this step, and at what threshold would you adjust?” The hold-or-proceed script (the workhorse): “Next dose due [date]. Since last dose: [one-line summary with counts]. Currently [keeping fluids / eating normally / not]. Question: hold or proceed — and if hold, resume how?” The new-symptom script: “New since [date]: [symptom, location, constant/intermittent, severity by function]. No prior history of [same]. Not present before [dose change / start]. Question: does this need evaluation before my next dose?” The plateau-adjacent script (pairs with the audit): “Four-plus weeks stable at [dose] with adherence per my log (attached). Audit done: [drift findings]. Question: dose step, or hold course?” The medication-interaction script: “New prescription from another provider: [drug, dose, start date]. Question: any timing or monitoring changes for my GLP-1?” Every script ends with a question mark — statements get sympathy; questions get decisions.
Skip-the-portal symptoms — the short list worth memorizing
Portals measure response time in hours to days; some presentations don’t have that budget. Seek in-person urgent or emergency care first — and message after — for: severe or persistent abdominal pain, especially epigastric pain radiating to the back (the pattern pancreatitis warnings describe), with or without vomiting; repeated vomiting or inability to keep fluids down beyond a day — dehydration compounds fast; right-upper-abdomen pain attacks, particularly after meals (the gallbladder pattern the labels flag); allergic-reaction signs — facial or throat swelling, hives with breathing difficulty; and severe hypoglycemia symptoms in anyone combining therapy with insulin or sulfonylureas. This isn’t a diagnosis list — it’s a routing list, and the routing rule is simple: when a symptom would scare you in a person you love, the portal is the second call.
The escalation ladder — when the portal goes quiet
Rung one: the well-formed message, with 24–48 business hours of patience for non-urgent matters. Rung two: the bump reply — same thread, one line (“following up; next dose decision needed by [date]”), which resets queues at most platforms. Rung three: the phone line or “urgent” flag if the platform offers one — corridor-quality providers publish this path, which is exactly the reachability test worth running before you need it. Rung four: care outside the platform — an urgent-care visit for the symptom plus a documented note to the portal (“seen at urgent care [date] for [issue]; records to follow”) — because continuity of record beats loyalty to channel. A platform that routinely forces rung four is telling you something the renewal review should hear.
FAQ
What should I include when messaging about side effects?
Five lines: what changed, when it started, severity in counts and function, what you’ve tried, and one specific decision-shaped question.
Which GLP-1 symptoms need urgent care instead of a portal message?
Severe or persistent abdominal pain (especially radiating to the back), repeated vomiting or inability to hold fluids, right-upper-abdomen pain attacks, allergic-reaction signs, and severe hypoglycemia symptoms when combined with insulin or sulfonylureas.
Can I ask my provider whether to skip a dose?
Yes — the hold-or-proceed script exists for exactly that; describe the interval in counts, state your fluid/food status, and ask the binary question. Never self-adjust silently.