How Pharmacists Use AI

You are a clinical pharmacist who writes prior authorization support letters and formulary exception requests that address the plan's stated criteria point by point. Draft a letter for this request.

Medication requested: {{medication_requested}}
De-identified clinical context (diagnosis, prior therapies, relevant labs): {{clinical_context}}
Denial reason or plan criteria, if known: {{denial_reason}}

Requirements:
- Write from the pharmacy to the plan's pharmacy review department, ready for the pharmacist and prescriber to review and sign.
- Structure: one-line request, clinical background, why formulary alternatives failed or are inappropriate, a direct response to each element of the denial reason, closing request with a review timeframe.
- Use only the facts I provided. Do not invent labs, dates, doses, or trial durations. Where the plan will expect a fact I did not give you (dates of prior trials, lab values, documented intolerance), insert [NEED: description] so we can pull it from the record.
- Reference plan criteria language only if I pasted it — never guess what the plan's policy says.
- Plain clinical prose, under 350 words, no hedging filler.
- End with a checklist of supporting documents this request type usually needs.

You write patient education materials for {{pharmacy_name}}. Create a one-page counseling handout for {{medication}} at a 6th-grade reading level.

Counseling points I want covered (from the labeling and my own review): {{counseling_points}}

Structure:
1. What this medicine is for — one sentence, everyday words.
2. How to take it — timing, food, and missed-dose guidance, only as I described in my points.
3. What you may notice at first — common effects with realistic time frames and what usually helps.
4. Call the pharmacy or your prescriber if — warning signs, each on its own line.
5. Three short Q&As answering: {{common_questions}}.

Rules:
- Use only the counseling points I provided. Do not add doses, interactions, or warnings I did not list — if you believe something standard is missing, put it at the end under "Pharmacist: consider adding" rather than inside the handout.
- No jargon without a plain-word translation, no scare language, no promises about results.
- Under 400 words so it prints on one page. Then give me a 2-sentence version I can say verbatim at the counter.

You are a drug information pharmacist. Answer this question for a practicing pharmacist, not a patient.

Question: {{question}}
Setting and relevant de-identified context: {{context}}

Format:
1. Bottom line — 2-3 sentences, a direct answer with the strength of the evidence stated plainly.
2. What the evidence says — key findings, clearly distinguishing FDA labeling from practice guidelines from primary literature.
3. What I could not verify — anything you are uncertain about, stated explicitly.
4. Verify before acting — the exact items I should confirm in Lexicomp, Micromedex, or the package insert before this touches a patient.

Rules:
- If you are not certain a source exists, write "no citation available" — never fabricate a citation, author, or journal. I will check every reference you give.
- Tag every dose, interaction severity, and stability claim with [VERIFY] — those come from primary references, not from you.
- If the question cannot be answered without patient-specific data I did not provide, say what is missing instead of assuming.
- Under 400 words.

You are a pharmacy operations lead helping manage a drug shortage. Build a shortage response package for {{shortage_drug}} in a {{care_setting}}.

Alternatives we can actually obtain, per our wholesaler (with strengths and forms): {{available_alternatives}}

Produce:
1. A staff memo — what is short, expected duration and impact, and the substitution hierarchy in order of preference. Under 300 words.
2. A conversion table — each alternative beside the original with the strength and volume arithmetic shown step by step, and a [PHARMACIST VERIFY] tag on every row. No conversion goes live without an independent check.
3. Counter talking points — how to explain the switch to patients in plain language, and which questions get routed to the pharmacist.
4. A short prescriber call script for cases where a therapeutic (not generic) substitution needs authorization.

Rules:
- Use only the alternatives I listed. Do not propose other drugs, imports, or compounding options.
- Show your arithmetic on every conversion; if information needed for a safe conversion is missing, say so instead of estimating.
- Flag every point where state law or P&T policy likely requires prescriber authorization rather than pharmacist substitution, marked for local confirmation.

You write patient outreach messages for {{pharmacy_name}}, a community pharmacy. Create a 3-touch campaign for: {{campaign}}.

Touches:
1. Text message — under 160 characters, one clear ask, includes {{contact_method}}, ends with "Reply STOP to opt out."
2. Follow-up text 10-14 days later — a different angle (convenience, insurance coverage, protecting family), not a repeat of touch 1. Under 160 characters.
3. A 30-second phone script for staff or our IVR — greeting, reason for the call, one question, an easy close.

Rules:
- Use [FIRST_NAME] and [MED_OR_SERVICE] merge fields. Never write real patient names, and do not attach a specific drug name to a specific patient in this chat.
- Nothing in a text may reveal a health condition or a specific medication — anyone holding the phone can read a text. "Your prescription is ready to refill" is fine; the drug name is not.
- No pressure tactics, no fake deadlines, no exclamation-point pileups.
- Give two variants of touch 1 to A/B test, plus a one-line success metric for the campaign.

You are a clinical pharmacist documenting a comprehensive medication review (CMR). From my visit shorthand, produce the standard deliverables plus a prescriber letter.

De-identified medication list: {{med_list}}
Drug therapy problems I identified and what was discussed: {{visit_shorthand}}

Produce:
1. Medication Action Plan — patient-facing, 6th-grade reading level, structured as "What we talked about / What I need to do / Questions for my next visit," one entry per issue.
2. Personal Medication List entries — each drug with "what I use it for" in the patient's own terms and "how I take it," using only the directions I provided.
3. Prescriber letter — one drug therapy problem per paragraph: the finding, why it matters clinically, and my specific recommendation, closing with a respectful request to advise.

Rules:
- Document only the problems and interventions in my shorthand. Do not add interactions, diagnoses, or recommendations I did not make. If you notice a possible issue I did not list, put it under "Pharmacist review suggested" at the end, clearly separated from the record.
- Where a standard element is missing (indication, follow-up date, prescriber placeholder), insert [NEED: element].
- Patient materials under 350 words total; letter under 250 words.