Case formulation: Abductive reasoning applied
Before moving on any further with the ATOM (abductive theory of method) as used in case formulation, I need to define what is data and what is phenomenon. Haig defines data as individual pieces of information, often unique to the person or situation, whereas phenomenon are patterns amongst those pieces of data that form distinctive features.

For example, difficulty getting off to sleep, lack of energy and poor appetite are data; when they’re tied together with tearfulness and feelings of guilt and poor concentration, and occur over the period of at least two weeks and are causing problems in work, home and social life, we can call it part of a pattern that we recognise as depression. Data are the evidence for the underlying phenomenon, they’re visible or reportable, but in themselves are not patterns.

But giving it a name doesn’t mean it’s now a case formulation – we need to sift through other pieces of data and phenomenon to identify relationships between factors to start to create an explanation for how and why it is occurring. This is abductive reasoning and this is also case formulation. It ‘takes us from descriptions of data patterns to one or more plausible explanations of those phenomena. This explanatory move is from presumed effect(s) to underlying causal mechanisms.’

In the case of chronic pain, there are so many variables that could be affecting an individual’s presentation, that it’s vital to take some time to really listen to what the person is describing. By doing this we are clinically sifting through masses of data, looking for patterns.

Does this person repeatedly avoid certain movements?
Does the person describe certain physiologic symptoms?
Are there patterns of response to certain people or interactions?

Revising from the last post I made, the first step is to collect some data, and the second part of that step is to reduce it and look for patterns. In looking for patterns we’re also searching for reliability of that information – does it come from several sources, how do they agree or differ, is it stable over time and place? To find this out we usually use information from more than one source such as the person, any questionnaires they’ve completed, any testing we’ve done, observation, and hopefully with other team members and the person’s significant others.

The next step is inferring causal mechanisms for the phenomena or patterns that have been identified. Most times clinicians work from a basic framework or theoretical orientation such as the biopsychosocial model, but adopt specific theoretical models such as operant conditioning (pain behaviour being reinforced), cognitive (eg schema, cognitive distortions), affective (eg attachment styles, emotion regulation), biological (eg central sensitisation, cortical organisation), or a combination of these. These theories are usually from the clinician’s ‘existing knowledge base of empirically established relationships between psychological mechanisms and behavioral patterns.’ In other words, clinicians draw on their knowledge of the literature, and their clinical experience to develop potential explanations for how and why this person at this time has developed these problems.

Given that the explanations generated are still hypothetical, it’s necessary to test for these relationships to confirm or disconfirm how well they explain the person’s presentation. Vertue and Haig suggest drawing the possible relationships in a graphic form to help generate links between various factors. Being a visually driven person myself, I find it helpful too – and helpful when working with the person with pain.

The next step is to establish how well this model explains what is happening. The degree to which it satisfies a number of criteria determines how useful the model is. So, it should:

  • explain the majority of features of the person’s presentation – including how the problem started, the resources the person has, the difficulties, as well as being able to predict the response to treatment,
  • be simple (not too many special assumptions to make),
  • be analagous to a similar model used in a similar way

The final step in this process of case formulation is to write a summary of the client’s presentation.  Vertue and Haig quote Ward in saying this part ‘is a comprehensive and, hopefully, integrated conceptualization of a case encompassing phenomenology, etiology, maintaining factors, prognosis, and treatment recommendations. It is a set of descriptive and explanatory hypotheses that attempts to explain why a client developed these problems at a particular time, what is maintaining them, and what should be done about them (Ward et al., 1999).

Whew!  What does that mean?  It should describe what you see, what the person reports, how the situations arose, what’s keeping it that way, what the likely future is, and what treatments should be applied.

I hope this account of clinical reasoning does a couple of things:

  1. helps structure your approach to ensure you don’t prematurely arrive at a conclusion well before you’ve explored the person’s presentation in depth
  2. helps you look at the range of possible and competing explanations before choosing one, and then using good criteria to establish which one is the most satisfactory explanation
  3. helps you appreciate just how complex this process of clinical reasoning actually is – it’s far more challenging than simply pattern recognition, because it’s about working out relationships between the underlying phenomenon

Frances M. Vertue, Brian D. Haig (2008). An abductive perspective on clinical reasoning and case formulation Journal of Clinical Psychology, 64 (9), 1046-1068 DOI: 10.1002/jclp.20504


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s