A hard thing about being an ER doctor is that I know a little, sometimes very little, about a lot of things. When I am faced with a particular condition, I often need to call the specialist for that organ, who knows way way more about it than I ever will, and they all think I'm an idiot because I don't know as much about their organ as they do. There's a huge asymmetry of knowledge, and it can create some tension and conflict.
I'm OK with it, because I can ignore their condescension and I am secure with what I do know, and its limits. But sometimes I get perplexing instructions from the specialists. The emergency medicine dogma can be overbroad and a little hidebound and what the specialists will do in the real world often radically diverges from what the Emergency Medicine textbooks say to do. It's often an interesting learning opportunity for me, especially when it's a condition I don't encounter that much. But I also have to work to maintain a flexible and open-minded attitude when I call a consultant and my side of the conversation consists of "Really? I didn't know you did that for this..." You need to know and trust your colleagues in other specialties, and know when to call BS on them and push to do something else, which is really hard to do when you are talking to someone who is so much more of an expert than you are.
So I saw this guy recently, a urban hipster who was perhaps a bit too old to be riding his longboard on the hilly streets of our fair town. He didn't seem to be too good at it, judging by the collection of crusted abrasions and aging ecchymoses he was sporting. He had been falling a lot recently -- we only get about a month of sun here, so I guess he was making the most of the summer weather practicing his new hobby. He had a variety of complaints from his recent falls, but it was a wound infection that had driven him to come in. A bit of road rash on his thigh was looking a bit cellulitic and I thought might benefit from some keflex.
I had to go through the motions of doing a more or less thorough exam, and he was pretty tender on his neck, I noticed. He said it had been hurting for about a week, since he had fallen backwards and hit his head on a car fender. He demonstrated how his neck was fully extended at the moment of impact, and the resolving goose egg on his scalp correlated. I wasn't terribly impressed by any of his orthopedic injuries, but I did order a few plain films, just to CYA, and I included a C-spine series as well, which is rare for me since if I really think someone might have a C-spine injury CT scanning is the imaging modality of choice.
I actually got a little short of breath when I scanned through his images and this jumped out at me:
For those not accustomed to reading these, this is a fracture through the posterior part of the second cervical vertebra, also known as a hangman's fracture. You might infer from the name that this is an unstable, bad injury, and you would be right. And our hipster friend had been walking around (hell, skating around and falling) for a full week with this injury! His neuro exam, I confirmed, was rock-solid normal. We popped a C-collar on him and I called the neurosurgeon at the local spine center to arrange transfer.
I had the opportunity to hold forth, as the nurses and techs gathered around the monitor to see the image, explaining that the "hangman's fracture" is a bit of a misnomer. Generally it is sustained from axial loading (as opposed to traction), which makes a ton of difference. The real-world mechanism is planting your forehead into a car windshield, that is, not hanging from a rope, and the spinal cord is typically uninjured in mechanisms of this sort. It's unstable and needs to be fixed, but there are many worse c-spine fractures you could have. My audience was very appreciative and I basked in their attention.
I was quite surprised, however, when I eventually spoke to the neurosurgeon. "It's a stable fracture," he told me, "he's had it for a week and his cord is fine. Put him in a hard collar and send him home. I'll see him in clinic next tuesday." It was one of those "What? Really?" moments I described above.
This surgeon, I should mention, was not some fly-by-night guy, nor was it the intern. He's a very respected professor at a university-affiliated trauma center. Not someone I am predisposed to argue with. I see hangman's fractures about, oh, once a decade, and he operates on them all the time. He clearly thought it was quite routine to send him home. And he did have a point -- it had been a week, after all. So with great discomfort, I acquiesced. For lay readers, it is important to understand that there are categories of stable spinal fractures that should go home, so it's not as crazy as it sounds. Not quite, anyway.
It seemed wrong, though, very wrong. I ran it by a couple of my partners and their eyes all got kind of big at the prospect, too. Without any clear plan, I decided to buy time and get the CT scan to better delineate the injury. After all, I reasoned, they will need it to plan the surgery when he goes to clinic next week. ("Next week? Am I really going to send a C2 fracture home for a week without even seeing the neurosurgeon? This is nuts! I just can't.") I chatted with the radiologist who read the CT, who described the hangman's fracture and blah blah blah, lots of technical details that meant nothing to me. I had radiology send the images electronically to the trauma center and sent a message to the surgeon that there was a scan available, in the hopes that might change his mind.
The surgeon called me back about ten minutes later, with a hint of anxiety in his voice. "Please tell me you didn't send that guy home, did you? This is a really bad, unstable injury. I need to operate on him today." To his credit, he had the grace to be embarrassed about his earlier advice and acknowledged that I was right to have stuck to my guns on this case.
I still don't claim to fully understand the intricacies of this injury or what about it changed the surgeon's mind. I'm not a neurosurgeon. I am very glad, though, that in this case I listened to my gut and that I didn't send him home. My malpractice carrier is, too. Knowing when to call BS, when to say "No" is one of the hardest things about my job, because it's pure instinct.