What is a Strong Patient Agenda Case?

A strong patient agenda case is one where the patient arrives with a clear, fixed expectation of what they want from the consultation. They have already decided on a specific medication, test, referral, or course of action, and they expect you to deliver it. Your job is to manage that expectation while providing safe, evidence-based care and maintaining the therapeutic relationship.

These are the most common case type in the SCA. MedTutor's case bank includes 17 strong patient agenda scenarios spanning mental health, women's health, men's health, neurology, dermatology, and more. In practice data, they account for over 1,300 simulation sessions, more than double any other consultation skill type.

The reason they appear so frequently is that they test all three SCA marking domains simultaneously. Data Gathering is tested because you need to understand why the patient wants what they want. Clinical Management is tested because you need to offer evidence-based alternatives. Relating to Others is tested because you need to negotiate without damaging rapport.

For a broader overview of how the SCA is marked, see our SCA Marking Scheme Explained guide.

Why These Cases Trip Up So Many Trainees

The core problem is binary thinking. Trainees see two options: say yes (give the patient what they want) or say no (refuse the request). Both lose marks.

Saying yes to an inappropriate request costs you Clinical Management marks. If a patient asks for diazepam for a flight and you prescribe it without exploring alternatives, you have failed to demonstrate evidence-based practice, regardless of how nicely you did it.

Saying no without adequate explanation costs you Relating to Others marks. If a patient asks for an MRI and you say "we don't do that in primary care" without exploring their concerns and offering an alternative, you have failed to demonstrate person-centred communication.

The examiners are not testing whether you say yes or no. They are testing whether you can navigate the space between the two: acknowledge the patient's perspective, explain your clinical reasoning transparently, and arrive at a shared decision that the patient accepts (even if it's not what they originally asked for).

The second common trap is spending the entire consultation debating the request rather than consulting normally. You still need to take a proper history, assess the underlying issue, and formulate a management plan. The request is the entry point to the consultation, not the whole consultation.

The ARENA Framework for Strong Patient Agenda

This six-step framework gives you a repeatable structure for any strong patient agenda case. It works within the 12-minute SCA consultation and maps directly to the three marking domains.

A: Acknowledge the request

Start by acknowledging what the patient wants and why they want it. "I can see you've come in today hoping to get [specific request]. Tell me a bit more about what's led you to that." This validates the patient and opens the door for exploration.

R: Reason behind the request

Explore their ideas, concerns, and expectations. Why do they want this specific thing? What have they read or been told? What are they worried about? This is your ICE exploration, built naturally into the consultation rather than as a checklist. This is where you earn Data Gathering marks.

E: Explain your clinical perspective

Share your reasoning transparently. Not "I can't prescribe that" but "I understand why diazepam seems like the obvious solution. Let me explain why I think there are options that would actually work better for you." Use clear, jargon-free language. Reference guidelines naturally if relevant.

N: Negotiate an alternative

Offer a credible alternative that addresses the patient's underlying need. If they want an MRI for back pain, the alternative isn't "take paracetamol." The alternative is a structured assessment, a physiotherapy referral, and specific red flag safety-netting with a clear pathway to imaging if needed. The alternative must feel like a real solution, not a dismissal.

A: Agree a plan together

Reach a shared decision. Summarise what you've agreed. Check the patient is on board. If they're not fully convinced, acknowledge that: "I can see you're not entirely sure about this, and that's okay. Why don't we try this approach for the next two weeks, and if things haven't improved, we'll review and consider other options?"

This framework maps to the marking domains: A and R cover Data Gathering, E and N cover Clinical Management, and the entire approach covers Relating to Others.

Category 1: Medication Requests

The most common strong patient agenda pattern is a patient requesting a specific medication. They may have been recommended it by a friend, read about it online, or received it from a previous GP. Common examples include benzodiazepine requests, sleeping tablets, antibiotics, and hormone therapy.

The key to these cases is understanding that the patient's request is usually a proxy for an unmet need. The patient who wants diazepam for a flight doesn't actually want diazepam. They want to get on the flight without panic. The patient who wants sleeping tablets doesn't want zopiclone. They want to sleep. Addressing the underlying need opens the door to alternatives.

Medication request cases to practise:

In all these cases, the examiner is watching whether you explore the underlying issue before addressing the specific medication request.

Category 2: Referral and Investigation Demands

The second pattern is a patient demanding a specific test or referral. They want an MRI, a blood test, a specialist opinion, or a specific procedure. These cases test whether you can explain the clinical rationale for or against a test without sounding dismissive.

The trap here is hiding behind policy. "We don't do MRIs for back pain" is a policy statement, not a clinical explanation. The examiner wants to see you explain why an MRI isn't indicated for this patient at this time, what you would do instead, and what circumstances would change your decision.

Referral and investigation cases to practise:

In each case, the patient's expectation is specific and concrete. Your management needs to be equally specific. Vague reassurance ("I'm sure it'll be fine") is not a plan.

Category 3: Information and Lifestyle Requests

The third pattern involves patients seeking specific information, documentation, or validation. This includes fit note requests, driving restriction discussions, and patients who arrive with a pre-formed self-diagnosis.

These cases are deceptive because the patient's request seems straightforward, but the clinical picture underneath is more complex. A patient requesting a fit note for stress may be experiencing domestic abuse. A patient asking about driving after a seizure may be in denial about the implications.

Information request cases to practise:

How the Marking Domains Apply

Strong patient agenda cases are tested heavily across all three domains, but each domain is looking for something specific.

Data Gathering and Diagnosis: The examiner wants to see that you explored why the patient wants what they want, not just what they want. If a patient asks for sleeping tablets, did you take a sleep history? Did you screen for depression? Did you ask about caffeine, screen time, shift work? The request is not the diagnosis. The underlying issue is.

Clinical Management and Medical Complexity: This is where the negotiation happens. Examiners look for evidence-based alternatives presented with confidence. They want to see you explain the risks of the requested treatment (without being preachy) and the benefits of the alternative (without overselling). They also look for safety-netting and follow-up.

Relating to Others: This is the domain where most marks are lost in strong patient agenda cases. The patient came in with an expectation. If they leave feeling unheard, dismissed, or lectured, you lose marks regardless of how clinically sound your management was. Examiners specifically look for acknowledgment of the patient's perspective, transparent reasoning, and shared decision-making.

For the full breakdown of each domain, see our SCA Marking Scheme Explained guide.

Common Mistakes and How to Avoid Them

Mistake 1: Jumping straight to refusal.

The patient says "I'd like diazepam for my flight" and you immediately say "We don't prescribe benzodiazepines for flying." You've skipped the entire exploration phase. Instead, acknowledge the request and explore it first. You have 12 minutes. Use the first 6 to understand the problem before you address the request.

Mistake 2: Caving to pressure.

The patient pushes back on your alternative, and you prescribe the requested medication to avoid conflict. This scores poorly on Clinical Management. It's okay for the patient to leave the consultation without getting exactly what they asked for, as long as they feel heard and understand your reasoning.

Mistake 3: Spending the whole consultation on the request.

Some trainees get so focused on the medication or referral debate that they forget to take a proper history, assess the underlying condition, or safety-net. The request is the starting point, not the entire consultation.

Mistake 4: Lecturing the patient.

There's a fine line between explaining your reasoning and delivering a monologue about guidelines. Keep explanations concise and patient-centred. "The evidence suggests X works better than Y for most people in your situation" is better than a five-minute guideline summary.

Mistake 5: Not offering a credible alternative.

If you decline a request, you need to offer something in its place. A patient who leaves with "no" and nothing else will feel dismissed. A patient who leaves with "no to diazepam, but yes to a CBT referral, a fear of flying course recommendation, and a follow-up in two weeks" has a plan.

Browse all 17 strong patient agenda cases across 10 clinical specialties to build your confidence with this case type.