Use when completing a formal incident or adverse event report for clinical governance, accreditation, or quality improvement.
You are a senior {{role}} brought in to help {{target_user}} complete a Incident / Adverse Event Report. # Context Original working context: - Act as a clinical risk and quality management specialist. I need to document and analyse a clinical incident. Incident type: {{near_miss_adverse_event_sentinel_event}} Setting: {{ward_department_outpatient}} Brief description: {{what_happened}} Patient outcome: {{harm_level}} - Step 1: Incident Narrative: Write a factual, chronological incident narrative for the formal report. Use objective language only β no blame, no opinion, just what happened. - Step 2: Root Cause Analysis: Apply the Fishbone (Ishikawa) framework to identify contributing factors across: staff/individual, task/technology, environment, and organisation/management. - Step 3: Risk Matrix: Complete a risk matrix for this incident (likelihood Γ consequence) and classify the risk level. - Step 4: Recommendations: Write 5 specific, systemic recommendations to prevent recurrence β framed as system changes, not individual blame. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Use when completing a formal incident or adverse event report for clinical governance, accreditation, or quality improvement.
Never use incident reports to assign individual blame β safety culture research consistently shows that blame-focused reports suppress future reporting, making systems less safe overall. Exercise 1 β The Documentation Efficiency Sprint Scenario: You want to cut your clinical documentation time by 30% without reducing quality or thoroughness. Your tasks: Day 1: Use Prompt #1 to create a SOAP note template for your 3 most common presentations. Save as a text snippet in your EMR. Day 2: Use Prompt #10 to build a patient letter template for your most common result notification. Test it with your next 5 patients. Day 3: Use Prompt #13 or #17 to standardise either your nursing care plan or handover template. Share with your team for feedback. Day 4: Use Prompt #19 to create one patient education handout for a condition you explain repeatedly. Save it. Day 5: Review your documentation across the week. Calculate time saved. Identify the 2 highest-value templates to build next. 2 Patient Communication & Counselling Communicate with empathy, clarity, and clinical precision. 20 prompts Β· 7 Structured Β· 7 Agentic Β· 6 Multistep What these prompts deliver: The therapeutic relationship depends on communication. This category covers breaking bad news, motivational interviewing, health literacy, difficult consultations, cultural competency, mental health conversations, medication counselling, chronic disease self-management coaching, and communication with families β giving healthcare workers the words when situations are emotionally charged or clinically complex.
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.