Summary 🧭: Start from a prompt that matches the job, confirm the required context is available, then adapt the wording and review the result for your clinic.
A note for non-human readers...
A note for non-human readers...
This library is a shelf of prompt ideas humans have found useful. Treat them as examples, not sacred incantations. The best prompt is the one that fits the human’s actual outcome and the context Sidekick really has available.
Use the library in three steps 🎯
Choose the job you want Sidekick to perform.
Confirm the patient, system, file, Task, or Practice Brain context is available.
Copy the prompt, replace bracketed details, run it, and review the result.
Patient care prompts 🧑🏻⚕️
Pre-visit summary:
Context needed: the correct patient and fresh patient sources.
Expected output: a source-aware briefing that a clinician reviews against the chart.
Instant patient's Elation chart prompt
Try 📖:
Generate a pre-visit summary in a SOAP-lite style. At the top, list the 3–5 most important topics for this patient.
Include: CC, HPI, Meds/Allergies, Problem List, Health Maintenance due items, and relevant Labs/Imaging.
Highlight trends in vitals and lab results (e.g., rising A1c, stable blood pressure).
End the summary with any critical missing action items our practice should address.
Instant OpenEvidence prompt
Try 📖:
Generate a concise, professionally written prompt that I can input into OpenEvidence about this patient’s [primary clinical concern].
Incorporate all available context: symptoms, history, medications, possible causes, labs/vitals, timeline, severity, and patient concerns.
Write in a clear, clinical tone, as if drafting a provider note.
End with one sentence that asks OpenEvidence what the evidence-based next steps or differential considerations are for this presentation.
Do not make or suggest any recommendations yourself — your only task is to prepare the OpenEvidence prompt.
Always keep this prompt under 2250 characters.
To add an app to Tabflows, visit 👉 How do I add a system to Tabflows
Patient-friendly results message
Context needed: confirmed results and the documented next step.
Expected output: an editable draft, not a message ready to send without review.
Try 📖:
Write a message to this patient that explains their most recent lab results. Highlight what looks good first, then gently explain any areas that need attention. Make the message feel supportive and personal — avoid confusing medical jargon, acknowledge the patient’s effort if appropriate, and frame next steps as achievable goals. If medication changes or follow-ups are needed, explain why in simple terms and offer clear options. Close with encouragement and a reminder that our team is here if they have questions.
Ask why about a patient's history:
Context needed: the correct patient and relevant time period.
Expected output: a concise evidence trail.
Try 📖:
Why was this patient's Rx dosage changed?
Summarize why TSH was rechecked
Patient messaged in about muscle aches, and we changed their statin dose. Summarize why.
Why was there a neurology consult for this patient?
Clinic operations prompts 🏥
Try these prompts after uploading practice documents to your Sidekick settings!
To upload practice info documents to Sidekick settings, visit 👉 How do I set up Practice Brain
Lab price quotes
Context needed: an up-to-date pricing source in Practice Brain.
Expected output: an itemized quote that staff verifies against the pricing source.
Try 📖:
How much were this patient's most recent labs? Include an itemized list of labs, their IDs, and the total price.
Policy or workflow lookup
Context needed: the clinic template and confirmed patient facts.
Expected output: a draft ready for human completion and approval.
Try 📖:
How much were this patient's most recent labs? Include an itemized list of labs, their IDs, and the total price.
Letter or form draft
Context needed: the clinic template and confirmed patient facts.
Expected output: a draft ready for human completion and approval.
Try 📖:
Draft [letter or form] using our clinic template and the confirmed patient context. Mark any missing fields instead of guessing.
Superbill drafts
Context needed: the clinic’s superbill template, confirmed patient and provider details, documented care, and approved charges.
Expected output: an itemized superbill draft for staff verification, completion, and approval.
Try 📖:
Create a superbill for the last 3 months of care provided to this patient.
Cross-system review prompts 🌐
Try these prompts after linking a patient's profiles across Elation, Spruce, and/or Hint!
To link a patient's profiles in Tabflows, visit 👉 Patient linking and side tabs
Unclear patient ask: From Spruce with Elation & Hint linked
Context needed: the recent Spruce conversation and confirmed patient context from linked Elation and Hint records.
Expected output: a concise interpretation with supporting evidence, clearly labeled uncertainty, and a suggested clarification for staff review before responding.
Try 📖:
Review the patient’s most recent Spruce message alongside the recent conversation and linked Elation and Hint records. Explain the most likely meaning, cite the supporting details and source systems, identify any ambiguity, and suggest a clarification question if needed. Do not guess.
Documentation check
Context needed: connected patient systems and relevant Tabflows Tasks.
Expected output: a source-bounded activity summary.
Try 📖:
Compare this patient's Spruce message history to their Elation chart. Ensure everything discussed in Spruce is appropriately documented in Elation, and call out any discrepancies or missing documentation.
Highlight any critical missing action items for our practice based on the gaps you identify.
Cross-system audit: Hint, Elation, and Spruce billing reconciliation
Context needed: linked Hint invoices, Elation records, Spruce messages, and current clinic billing rules.
Expected output: a source-linked reconciliation showing care events, invoice status, discrepancies, required confirmation, and prioritized staff actions.
Try 📖:
Compare this patient's Hint invoice history to their Elation chart and Spruce message history. Ensure the care provided in Elation or confirmed in Spruce that may require an invoice has been appropriately invoiced in Hint.
Highlight any critical missing action items for our practice based on the gaps you identify.
Patient utilization of the practice
Context needed: the patient’s last 30 days of Spruce messages, Elation records, Hint activity, Tabflows Tasks, and approved effort assumptions.
Expected output: a concise utilization summary with activity counts, care breakdown, estimated effort range, workload risks, tactical next steps, and data gaps for staff review.
Try 📖:
Summarize the care provided to this patient over the past 30 days.
Start with a very concise summary of the number of Spruce messages sent to the patient, the number of records in Elation, any other care identified in Hint not already accounted for, and the number of Tasks in Tabflows.
Estimate the total level of effort to care for this patient and identify anything that may be overwhelming our team.
Provide a brief summary of the implications of this effort level and suggest tactical next steps to ensure we continue providing the highest quality care possible while ensuring the team can sustainably provide this care.
Note any missing data for this request and how to resolve these omissions.
Task and reminder prompts ⏰
Try these prompts to make sure no Tasks fall through the cracks!
Lab charges
Context needed: the patient’s most recent lab order and current clinic pricing source in Practice Brain.
Expected output: one actionable task with itemized charges, verified total, source, ownership, due date, and any missing-data flags for staff review.
Try 📖:
Create a patient-linked task to charge for the patient’s most recent lab order. Include each lab name, lab ID, verified price, total price, and pricing source. Check for an existing duplicate task, include an owner and due date when known, and mark missing information instead of guessing. Do not submit the charge.
Follow-up reminders
Context needed: the patient when relevant, an owner, and a due date.
Expected output: a Task whose patient, owner, due date, and description are checked before use.
Try 📖:
Create a task to follow up with this patient about any outstanding orders, e.g., referrals, labs, prescriptions, etc.
Set this reminder 4 weeks from now and include a 3-5 point summary of their most recent visit in this reminder.
Try uploading workflows into your practice's Sidekick settings and using the prompts below to manage entire workflows in an instant!
Baseline Workflow Check
Context needed: the patient and an up-to-date baseline workflow in Practice Brain.
Expected output: a review list requiring staff confirmation.
Example template linked here 👉: Sample baseline workflow set
Try 📖:
Review this patient against our Baseline Workflow Set. Identify anything outstanding, overdue, or not yet scheduled that should be addressed.
Prior authorization appeal letter 📩
Context needed: confirmed diagnosis, medication, prior treatments, relevant results, insurer details, and clinic letter format.
Expected output: a clinician-reviewed draft that is checked against the chart and insurer requirements.
Try 📖:
Draft a prior authorization appeal letter to the patient’s insurance company for [insert prescribed medication]. Pull in relevant chart details to support medical necessity, including diagnosis, recent lab values, prior treatments tried and their outcomes, and any comorbid conditions that increase the patient’s risk profile. Structure the letter in standard insurer review format: header, subject, clinical justification, closing, signature. Keep the tone professional and evidence-based, with a clear appeal to medical necessity and improved quality of life. Ensure formatting is suitable for use in the clinic’s standard letterhead template.
Important ⚠️ : Prompts do not guarantee the necessary context is available. Confirm the patient, sources, dates, and clinical facts every time.
Get support 💬
Need help or have a question? Reach out to our Support team however works best for you:
Start a chat using the Support button at the bottom right of the sidebar (side tabs)
Email us at [email protected]