Healthcare prompt examples

Draft a follow-up for our clinic team using these fictional huddle notes. Use a table with action, owner, due date, and status. Mark missing details as [Needs confirmation]. Keep it under 120 words. Notes: The educator will draft the kiosk tip sheet by Friday. The operations lead requested a training room; approval is pending. The team still needs to assign someone to plan float-staff training.

Try a follow-up: “Give me a two-sentence opening for a busy shift team. Preserve the table and the pending items.”

Check: the room stays pending, and the float-staff task keeps its missing owner visible.

Rewrite this fictional update for clinic staff reading on a phone. Put the action first, use plain language, and stay under 80 words. Preserve the timing and the pending detail. Update: Staff must finish the scheduling refresher by Friday. The educator will post the registration link on Tuesday. The session time still needs confirmation.

Try a follow-up: “Make the tone warmer and keep the deadline equally clear.”

Check: the deadline and registration timing survive the rewrite, and the session time remains unresolved.

Compare the attached [previous policy] and [current policy] for a supervisor briefing staff. Make a table of changed requirements, affected staff, and the supporting section in each document. Keep effective dates visible. Put conflicting or unclear requirements in a questions-for-the-policy-owner list.

Try a follow-up: “Turn the confirmed changes into a five-bullet shift briefing. Keep the open questions separate.”

Check: the versions, effective dates, exceptions, and each reported change against both documents.

Using the attached approved [orientation guide], draft a first-week checklist for a new [role]. Group it by day, include who can help, and show the guide section for each required task. Label your suggested timing as [Suggested]. Flag any missing deadline or contact for the educator to confirm.

Try a follow-up: “Create five practice questions using the same guide. Give each answer with its supporting section.”

Check: required tasks come from the guide, and suggested timing stays clearly labeled.

Rewrite the attached approved [general patient handout] in everyday language for adults. Aim for a sixth-grade reading level and short headings. Keep every warning, instruction, number, and contact detail faithful to the source. Flag wording that needs a clinician's decision. Return a draft for clinical review.

Try a follow-up: “List the medical terms you changed and show the original and revised wording side by side.”

Check: a qualified clinician verifies meaning, warnings, and completeness before patient use. This task uses a general handout and needs no patient details.

Summarize this fictional staff-training queue for our supervisor in three bullets. Show the totals for completed and pending requests. Identify the category with the largest pending count. Keep conclusions within this single snapshot. Portal access: 18 completed, 6 pending. Session registration: 21 completed, 9 pending. Attendance corrections: 10 completed, 6 pending.

Try a follow-up: “What extra data would help us understand waiting times? Keep proposals separate from the snapshot's findings.”

Check: add the figures yourself: 49 completed and 21 pending. The source gives one snapshot, with waiting times and causes still unknown.

Our fictional clinic team wants to make appointment check-in instructions easier for patients to follow. Suggest four small changes we could discuss. For each, explain the idea, what we would need to learn first, and one way to test it. Treat every idea as a proposal for team review. Ask me one question if you need more context.

Try a follow-up: “Which assumptions should we check with frontline staff before choosing a test?”

Check: proposals fit the local workflow, resources, and approval process. Keep suggested benefits as questions to test.

Help me write a prompt for [task]. Ask one question at a time about my goal, audience, permitted source material, and useful output. Then propose a short prompt using placeholders for missing details, plus a checklist I can use to review the result.

Try a follow-up: “Make that a reusable template. Keep the source, audience, and review step easy to change.”

Check: the proposed prompt matches your task and asks only for information you may share.

Using the current approved visitor policy for [location], summarize the check-in steps for front-desk staff in five bullets. Include the route for exception requests. Ask me for any detail you need to identify the right policy.

Try a follow-up: “Which parts of my question remain unresolved by the policy?”

Check: open the agent's linked policy and confirm location, current version, steps, and exceptions.

Help me find the approved steps for reporting a broken workstation at [location]. Use your staff IT support guide. Ask one question at a time if you need more detail. If this needs service-desk help, tell me the approved contact route and the information I should have ready.

Try a follow-up: “Draft a short description of the issue for me to review, using the details I have provided.”

Check: verify the support route in the guide. Keep passwords and patient details out of the request.

Help new [clinic or department] staff find answers in the configured, approved [orientation guide]. Use that guide for factual answers. Give brief, plain-language responses suited to new colleagues. Ask a clarifying question when the role or location matters. When the guide leaves a question unresolved, explain the gap and direct the person to [orientation contact]. Route patient-specific care questions to the appropriate clinical team. Keep your work within staff orientation.

Try as a user: “Where do I find the required learning for my first week as a [role]?”

Before testing: replace the role and contact, connect the guide approved for this audience, and limit the agent's tools to its purpose.

Help [team] prepare follow-ups from the permitted meeting notes the user supplies. Draft a short opening, an action table with owners and due dates, and an open-questions list. Use the notes for factual details and mark gaps as [Needs confirmation]. Keep proposed actions separate from agreed actions. Show the draft for review. If the user asks you to send or update anything, show the exact proposed action and wait for their explicit approval before using a configured tool. If that action is unavailable, explain the next step the user can take.

Try as a user: “Use these fictional huddle notes to draft our follow-up. Keep the unresolved owner visible.”

Before testing: start with drafting. Any sending or record-update tool needs separately configured permissions and an approval control checked by the builder.