mcpbeat

Clinical Diagnostic Reasoning

curiositech/some_claude_skills-clinical-diagnostic-reasoning

Cognitive framework for medical diagnostic decision-making addressing systematic biases (commission bias, satisfaction of search, availability error, anchoring error, attribution error). NOT for clinical knowledge acquisition or specific disease protocols.

6k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
177
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/curiositech/some_claude_skills --skill clinical-diagnostic-reasoning

The instruction itself

19 sections, as written by the author

Clinical Diagnostic Reasoning

Apply systematic cognitive strategies to avoid predictable diagnostic errors and improve clinical decision-making accuracy.

When to Use

✅ Use for:

  • Medical diagnostic decision-making across all specialties
  • Clinical case analysis and error review
  • Teaching diagnostic reasoning to medical trainees
  • Quality improvement initiatives targeting diagnostic accuracy
  • Patient communication about treatment options

❌ NOT for:

  • Learning pathophysiology or disease-specific knowledge
  • Memorizing diagnostic algorithms or clinical guidelines
  • Emergency protocols requiring rapid standardized responses
  • Non-clinical decision-making domains

Core Process

Diagnostic Decision Tree

Patient Presentation
│
├─→ Information Gathering
│   ├─→ Use language-based communication as primary tool
│   ├─→ Actively listen for unique patient context
│   └─→ [CHECKPOINT] Am I stereotyping based on demographics? (Attribution Error check)
│
├─→ Hypothesis Generation
│   ├─→ Form initial diagnostic hypotheses
│   ├─→ [CHECKPOINT] Am I anchored to initial impression? (Anchoring Error check)
│   └─→ Generate at least 3 alternative explanations
│
├─→ Evidence Search
│   ├─→ Seek confirming evidence
│   ├─→ Actively seek disconfirming evidence
│   ├─→ [CHECKPOINT] Have I found ONE thing or EVERYTHING needed? (Satisfaction of Search check)
│   └─→ Ask: "What else could explain these symptoms?"
│
├─→ Algorithm Application
│   ├─→ Apply relevant diagnostic protocols
│   ├─→ [CHECKPOINT] Does this patient's context warrant deviation?
│   ├─→ If recent similar case: What's DIFFERENT here? (Availability Error check)
│   └─→ Contextual adjustment based on patient specifics
│
├─→ Action Decision
│   ├─→ Option A: Treat (action)
│   ├─→ Option B: Observe (inaction)
│   ├─→ [CHECKPOINT] Am I biased toward action? (Commission Bias check)
│   └─→ Explicitly weigh risks of intervention vs. observation
│
└─→ Patient Communication
    ├─→ Frame options neutrally
    ├─→ [CHECKPOINT] Would different framing change patient choice?
    └─→ Present clinically equivalent information consistently

Cognitive Error Prevention Loop

During diagnosis:
│
├─→ PAUSE: Identify which cognitive trap is most likely here
│   ├─→ Recent memorable case? → Availability Error risk
│   ├─→ Found something interesting? → Satisfaction of Search risk
│   ├─→ Strong initial impression? → Anchoring Error risk
│   ├─→ Patient fits stereotype? → Attribution Error risk
│   └─→ Uncertain situation? → Commission Bias risk
│
├─→ COUNTER: Apply specific correction strategy
│   └─→ See Anti-Patterns section below
│
└─→ REASSESS: Periodically restart from first principles
    └─→ "If I saw this patient fresh today, what would I think?"

Anti-Patterns

Commission Bias

Novice Approach: "The patient is presenting with symptoms, so I need to do something—prescribe treatment, order tests, intervene."

Expert Approach: "I explicitly consider watchful waiting. Is observation the more appropriate choice here? What are the actual risks of my intervention versus doing nothing?"

Timeline: Develops after seeing cases where intervention caused harm and observation would have allowed natural resolution. Recognition typically comes after 2-3 years of clinical practice when physicians have accumulated enough cases to see the consequences of unnecessary action.

Signal: Expert asks "What happens if we wait?" before "What should we do?"


Novice Approach: "I found a kidney stone explaining the flank pain. That's the diagnosis—we're done."

Expert Approach: "I found a kidney stone, but I continue systematic evaluation. Could there be additional pathology? What else might coexist? The stone may be incidental to the actual problem."

Timeline: Recognition occurs after experiencing a case where the first finding was incomplete or coincidental. Often crystallizes during residency when a missed diagnosis is discovered after initial "satisfactory" finding.

Signal: Expert says "What else?" even after finding something plausible.


Availability Error

Novice Approach: "I just saw three cases of pneumonia this week. This patient has similar symptoms—probably pneumonia."

Expert Approach: "I recognize I've seen recent pneumonia cases. What makes THIS patient different? I'll actively search for distinguishing features before applying the familiar pattern."

Timeline: Awareness develops after misdiagnosing a patient by inappropriately applying a recent memorable case pattern. Usually occurs within first 2 years of independent practice.

Signal: Expert asks "What's different?" when pattern matching to familiar cases.


Anchoring Error

Novice Approach: "The ER note says 'anxiety attack' and initial exam seemed consistent. I'll proceed with that framework."

Expert Approach: "The initial impression was anxiety, but I periodically reassess from zero. What if I ignore that label and start fresh with just the symptoms?"

Timeline: Develops after experiencing a case where initial impression was incorrect and prevented proper diagnosis. Recognition typically occurs after receiving feedback on a missed diagnosis that seemed obvious in retrospect.

Signal: Expert periodically says "Let me start over from first principles."


Attribution Error

Novice Approach: "Chart says 'drug-seeking behavior' from previous visits. The colleague who referred her mentioned she's 'difficult.' I'll be appropriately cautious about her pain complaints."

Expert Approach: "I see the labels, but I approach this individual with fresh assessment. What objective findings does THIS patient present TODAY? I question stereotypes from demographic factors or second-hand information."

Timeline: Recognition usually triggered by discovering serious pathology in a patient who had been stereotyped. Often occurs mid-career after enough experience to have seen exceptions to stereotypes.

Signal: Expert explicitly states "I'll assess the patient myself" when given second-hand characterizations.


Algorithmic Rigidity

Novice Approach: "The clinical guideline says do X, Y, then Z. I follow the algorithm exactly as written."

Expert Approach: "The algorithm is a tool, not a mandate. This patient's unique context suggests deviation is appropriate here. My experience with similar exceptions supports this modification."

Timeline: Develops gradually through accumulated patient experience, typically requiring 5+ years to build sufficient pattern recognition for confident contextual deviation.

Signal: Expert says "The algorithm would suggest X, but in this patient's context, Y is more appropriate because..."

Mental Models

"Cognitive Traps as Pitfalls"

Diagnostic biases are hazards in the terrain of clinical reasoning—they can be identified, mapped, and avoided with awareness, but only if you know where they are and actively watch for them. Like physical pitfalls, falling into them once teaches you to look for them permanently.

"The First Find Is Not the Finish Line"

Satisfaction of search thinking treats diagnosis like a simple treasure hunt (find something, you're done). Expert thinking treats it like archaeology (finding one artifact means carefully searching the surrounding area for related findings).

"Framing Is the Frame"

The frame around a painting changes how viewers perceive the artwork. Similarly, how you frame medical information changes the picture patients see—even when the clinical content is identical.

Shibboleths

  • Novice says: "I found the problem"
  • Expert says: "What else could be contributing?"
  • Novice says: "The algorithm says..."
  • Expert says: "The algorithm suggests, but this patient's context..."
  • Novice says: "We should do something"
  • Expert says: "What happens if we observe?"
  • Novice says: "This looks like that case I saw"
  • Expert says: "This looks similar, but what's different?"
  • Novice says: "The patient is [stereotype]"
  • Expert says: "Let me assess this individual directly"

Key Principles

  • Language remains foundational: Despite technology, verbal communication is the primary diagnostic tool
  • Algorithms need context: Protocols are tools to apply within patient-specific circumstances, not universal mandates
  • Framing effects matter: Clinically equivalent information presented differently produces different patient decisions
  • Search beyond satisfaction: The first plausible explanation is not necessarily complete or correct
  • Experience builds deviation capability: Clinical judgment for contextual algorithm modification improves with patient volume

References

  • Source: "How Doctors Think" by Jerome Groopman
  • Domain: Clinical diagnostic reasoning and cognitive bias in medicine
  • Key contribution: Systematic identification of cognitive biases affecting physician judgment with emphasis on the gap in medical education regarding error recognition

How to use it

Copy the folder

Take curiositech/some_claude_skills-clinical-diagnostic-reasoning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.