Ep 4 - Understanding diagnostics In Emergency Medicine Part 2 - Beyond Yes or No

The St.Emlyn’s Podcast - A podcast by St Emlyn’s Blog and Podcast - Wednesdays

Categories:

What is a Diagnosis? A diagnosis is essentially a label that we put on a patient to indicate what they have, which then guides our treatment decisions. In the ED, our primary focus is on identifying life-threatening conditions. This approach often involves working backwards by first ruling out serious conditions before considering what a patient might actually have. Initial Diagnostic Approach As emergency physicians, our initial approach is to use tests with high sensitivity. These tests are designed to pick up anyone who might have the disease. Once we rule out the serious conditions, we look at tests with high specificity to confirm the diagnosis, as treatments often carry risks. For example, therapies such as thrombolysis come with significant risks, so we need to be fairly certain before proceeding, unlike less consequential treatments like wrist splints. Understanding Probabilities in Diagnoses When we say a patient has a diagnosis, we’re essentially saying it’s likely enough to treat. Conversely, when we say a patient doesn’t have a diagnosis, we mean it’s unlikely enough to withhold treatment. This probabilistic approach is vital in the ED and can be surprising to many people. Case Study: Cardiac Chest Pain Let’s apply this to a patient with cardiac-sounding chest pain. Our goal is to either rule out or confirm the disease and start appropriate treatment. We start with specific tests to rule in a diagnosis, such as an ECG. A positive ECG with significant ST segment changes indicates a high likelihood of disease, warranting immediate treatment. This approach quickly sorts out high-risk patients. For patients with normal or near-normal ECGs but still concerning symptoms, we need sensitive tests to ensure we don't miss anyone with myocardial disease. About 10% of these patients might have underlying issues, so we need to ensure our tests are sensitive enough to catch these cases. Using Prevalence and Pre-test Probability To decide if a patient has the disease, we must consider the prevalence or pre-test probability in our population. For example, in patients with normal ECGs and no alarming history, the pre-test probability might be around 10%. This isn’t low enough to rule out the disease but also not high enough to justify treatment without further testing. Diagnostic Processes in the ED We use a step-by-step diagnostic process. Starting with the most specific tests to rule in a diagnosis, we then use sensitive tests like high-sensitivity troponin to rule out diseases. High-sensitivity troponin tests are great for ruling out diseases due to their sensitivity. If the test is negative, we can be confident the patient doesn’t have myocardial damage. If the test is positive but not dramatically high, we may need additional tests to confirm the diagnosis. Each diagnostic step adjusts our patient’s probability of having the disease. Our goal is to reach a probability low enough to safely rule out the disease or high enough to justify treatment. This process is continuous, and we apply it to every patient, whether they have chest pain or another symptom like a headache. Understanding Likelihood Ratios We often use likelihood ratios to interpret diagnostic tests. A positive likelihood ratio increases the probability of the disease, while a negative likelihood ratio decreases it. For example, a high-sensitivity troponin test is excellent at ruling out myocardial infarction because of its high sensitivity, though it’s not as good at ruling in due to lower specificity. Optimising Diagnostic Tests Diagnostic tests like troponin can be optimized by adjusting the threshold levels. For instance, a higher threshold might improve specificity and thus be better at ruling in the disease, while a lower threshold improves sensitivity, making it better at ruling out the disease. This principle applies to various tests, including white cell counts and amylase levels. Continuous Assessment and R

Visit the podcast's native language site