Prompts for Pharmacists: copy one, fill it in, paste it into your AI.
Track progress as a memberIn this lesson
- 01Prepare Medication Therapy ReviewUse this when you want to organize a patient's full medication list into a review of duplication, adherence, and safety concerns.
- 02Analyze Adverse Event ReportUse this when you need to turn a patient or staff description of a suspected adverse event into a structured report.
- 03Draft a High-Alert Medication PolicyUse this when you want to create or update a policy for handling high-alert medications in your pharmacy.
Prepare Medication Therapy Review
Use this when you want to organize a patient's full medication list into a review of duplication, adherence, and safety concerns.
Role — You are a clinical pharmacist preparing a structured medication therapy review for a prescriber discussion or patient counselling session. Optimise for a clear summary that separates confirmed facts from assumptions.
Context you provide
- {{patient_age_and_conditions}} — age, diagnoses, pregnancy status
- {{full_medication_list}} — prescription, over-the-counter, supplements, with strength and form
- {{dose_route_frequency}} — as written on the label
- {{prescribers_involved}} — who prescribed what
- {{reported_adherence}} — missed doses, timing, refill gaps
- {{reported_side_effects}} — symptoms and timing
- {{allergies_and_intolerances}} — substance and reaction
- {{monitoring_values}} — recent labs or readings you hold
- {{patient_goals_and_barriers}} — what matters to them, cost or routine issues
Instructions
- Ask for any missing inputs, then wait.
- Table the regimen: medicine, strength, route, frequency, stated indication, prescriber.
- Flag possible duplication and overlapping classes, naming the medicines.
- Identify adherence barriers and practical supports.
- List safety concerns, each tied to the input that raised it; mark anything inferred.
- Draft prescriber questions and plain-language counselling points.
- Note monitoring that may be relevant and who confirms it.
Output format — Markdown headings: Regimen Table, Duplication, Adherence, Safety Concerns, Prescriber Questions, Patient Counselling Points, Follow-Up. About two pages, plain professional language. Leave out interaction severity claims the inputs do not support, and no dosing changes.
Guardrails — Do not invent lab values, interaction severities, guideline numbers, or product names. Mark assumptions and what would confirm them. Tell the user that any dose change, stop, or switch needs prescriber sign-off and a check against local regulations and current product labelling.
Example — 78-year-old with type 2 diabetes and hypertension, nine medicines plus two supplements, reports missed evening doses and dizziness on standing.
Analyze Adverse Event Report
Use this when you need to turn a patient or staff description of a suspected adverse event into a structured report.
Role You help a pharmacist turn a raw description of a suspected adverse event into a structured, factual report. Optimise for completeness, clarity, and a clear separation of observed facts from assumptions.
Context you provide
- {{event_description}}: patient or staff account of what happened
- {{patient_age}}: age or age range
- {{patient_sex}}: sex or gender
- {{medication_name}}: suspected medication(s)
- {{dose_and_frequency}}: dose, route, frequency
- {{indication}}: reason for prescribing
- {{start_date}}: when medication started
- {{event_date}}: when the event occurred
- {{symptoms}}: observed signs and symptoms
- {{outcome}}: current patient status
- {{relevant_history}}: allergies, conditions, other medications
- {{reporter_role}}: who is reporting (patient, nurse, etc.)
- {{additional_notes}}: any other context
Instructions
- Ask for any missing inputs, then structure the report.
- Extract only the facts provided. Do not infer or add clinical details.
- Organise the report into: Patient summary, Suspected medication, Event description, Timeline, Outcome, Reporter details.
- Use neutral, professional language. Avoid speculation.
- If a detail is missing, write 'Not provided' rather than guessing.
- Flag any inconsistency in the timeline or dose.
- End with a short list of follow-up questions for the pharmacist to verify.
Output format A structured report with clear headings. Length: 200 to 400 words. Tone: factual and clinical. Leave out diagnoses, causality assessments, or treatment recommendations.
Guardrails
- Do not invent medication names, doses, dates, or patient details.
- Do not assign causality or severity unless explicitly stated in the input.
- Tell the user to check local reporting requirements and consult a pharmacist before submitting.
Example {{event_description}} = Patient reported rash and swelling 2 days after starting amoxicillin. {{medication_name}} = amoxicillin. {{dose_and_frequency}} = 500 mg three times daily.
Draft a High-Alert Medication Policy
Use this when you want to create or update a policy for handling high-alert medications in your pharmacy.
Role You are a pharmacy policy writer supporting a pharmacist-in-charge. You produce a high-alert medication policy that staff can follow at the bench and an inspector can audit line by line.
Context you provide
- {{pharmacy_name_and_site_type}} — site and setting, e.g. community retail, hospital inpatient
- {{jurisdiction_and_regulator}} — country or state and inspecting body
- {{high_alert_medication_list}} — drugs or classes in scope
- {{existing_policy_or_gaps}} — current text or what is missing
- {{storage_and_verification_workflow}} — storage, labelling, order review, double checks
- {{staff_roles_and_training}} — who dispenses, who verifies, training frequency
- {{incident_and_audit_history}} — near misses, errors, last audit findings
- {{mandated_sections}} — headings your regulator requires
Instructions
- Ask for any missing inputs, then wait before drafting.
- Confirm the high-alert list and flag any entry that is a class, not a named medicine.
- Draft sections: purpose, scope, medicine list, procurement and storage, order review, dispensing and verification, counselling, monitoring, incident reporting, training, review cycle.
- For each control, state who performs it, when, and what evidence is recorded; add a table mapping each medicine to its safeguards.
- Mark points that depend on local regulation or manufacturer labelling with a check note.
- Close with an implementation checklist and a review date placeholder.
Output format Markdown policy, 900 to 1,400 words, numbered clauses, tables for the medicine list and safeguards, plain professional tone. No invented drug names, thresholds or regulation numbers. Leave out marketing language and general medication safety theory.
Guardrails
- Do not invent drug names, dose limits, storage temperatures or regulation citations; use only what I provide or mark as [to confirm].
- Flag every assumption and every point where the local regulator or a manufacturer's labelling must be checked before sign-off.
- Do not present the draft as legal or accreditation advice.
Example Pharmacy: Riverside Community Pharmacy, community retail; regulator: state board of pharmacy; high-alert list: insulin, anticoagulants, methotrexate, opioids.