When a nurse calls me about a Permobil joystick that won't respond, the first words out of her mouth are, "I need the manual." I get it. The joystick is dead, the patient is waiting, and the manual is supposed to have the answer. But after six years and more than 200 emergency support calls, I've learned that the manual is rarely the answer. It's often the first layer of the problem.
Based on our internal data from 200+ rush jobs, the most expensive phrase in medical equipment isn't "we need a new part." It's "let me check the manual."
It Starts With a Manual Request
In my role coordinating emergency equipment support for hospitals and clinics, I've handled everything from a missing battery for a Permobil M300 to a CT scanner that stopped mid-scan at 2 a.m. The pattern is consistent: a clinician calls, describes the symptom, and then asks for the Permobil joystick manual, the battery replacement guide, or the troubleshooting section for whatever device is down.
I used to send it right away. Then I'd wait on the phone while they scrolled through pages and PDFs, looking for a code or a diagram that would explain why the equipment wasn't working. Sometimes it worked. More often, it didn't. Why does this matter? Because the request for a manual is often a request for something else: permission to trust their own judgment.
What the Manual Doesn't Tell You
The first thing I had to unlearn—and it took me three years, or rather closer to four, and about 150 calls to do it—is that a manual is a reference, not a conversation. It will tell you what a component is and how to replace it. It won't tell you why the component failed in this specific chair, with this specific patient, in this specific building.
Take the Permobil joystick manual. It lists error codes. It tells you what each code means. But it doesn't tell you that a joystick can show the same error when the connector has corrosion, when the battery cable is damaged, or when the controller simply needs a reset. The manual gives you a map. It doesn't tell you which road to take.
The Permobil M300 battery replacement is another example. The manual covers the steps: remove the seat, disconnect the batteries, install the new ones, reconnect. What it doesn't cover is the stuff I see in real facilities: corroded terminals, mismatched fasteners, or a battery that was ordered without checking the voltage on the old one. The third time we saw that mistake, I finally created a pre-replacement checklist. Should have done it after the first time.
The CT scanner question
A few months ago, a radiology tech asked me, "How does a CT scanner work?" It wasn't a physics question. She had a scanner that kept aborting scans, and she needed to explain it to her supervisor. The manual had a 30-page section on image acquisition. It didn't mention that the room's air filter was so clogged that the scanner was overheating and shutting down to protect itself. She didn't need a lesson in X-ray physics. She needed someone to say, "Check the environment before you check the boards."
The infection control product surprise
Manuals fail in procurement decisions, too. I once watched a facility choose an infection control product based entirely on the spec sheet: EPA-registered, quick kill claims, all the right active ingredients. What the spec sheet didn't show was that the dispenser cartridges didn't fit their existing wall brackets. The product worked. The workflow didn't. They spent three weeks retraining staff and ordering new brackets before the product was actually usable.
That's the deep problem: we treat documentation as if it's the whole truth, when it's really just the manufacturer's version of the truth. The missing context lives in the hallways, the storage closets, and the maintenance logs. And no manual can give you that. At least, that's been my experience with hospitals and clinics.
The Real Price of a 'Quick Look'
The cost of the manual-first approach is not just a few wasted minutes. It's compounded downtime. Every minute a clinician spends translating a PDF into real-world action is a minute not spent with a patient. But the bigger cost is the second call—the one after the manual doesn't work.
In March 2024, 36 hours before a state survey, a facility found that three of their wheelchairs had intermittent joystick failures. The maintenance lead asked for the Permobil M300 battery replacement manual, convinced it was a battery problem. We sent it. The team ordered batteries, waited half a day, installed them, and then discovered the joysticks still didn't work. The real issue was corroded connectors on the battery harnesses. Missing that survey deadline would have meant a $50,000 penalty clause, so we rushed the correct connectors overnight. Cost us $800 in freight. (Should mention: we'd built in a 3-day buffer, which is the only reason we made it.)
That night, we didn't have a formal escalation process for "the manual didn't work." Cost us when the maintenance lead spent two hours searching for an answer that wasn't in the manual. He later told me he'd known it wasn't the battery before he ordered it—he just didn't know what else to check. He wasn't incompetent. He was stuck between the manual and reality.
The same gap shows up with a continuous glucose monitor. The device manual lists every alert, but it doesn't tell a nurse which alerts require immediate action and which can wait until after shift change. When a CGM says "sensor failure," the manual says replace the sensor. In practice, checking the insertion site first saves money, time, and patient frustration. Context, not code, made that difference.
From Manuals to Decision Support
So what actually works? I've stopped leading with manuals. I now start with what I call the failure context: what was the device doing, when did it start, and what changed right before it failed? For a Permobil joystick, that means checking the battery connector before you order a controller. For a Permobil M300 battery replacement, it means confirming the correct battery voltage and inspecting the harness before you open the seat. For a continuous glucose monitor, it means asking about the insertion site before you blame the sensor. For a CT scanner, it means checking the room temperature and airflow before you call a service engineer.
The fundamentals haven't changed. You still need good documentation, and Permobil's technical guides are genuinely useful. But the execution has transformed. In 2020, the default answer was "check the manual." In 2025, it's check the context first, then use the manual as a cross-reference. That's a small shift in words and a big shift in outcome.
We now build one-page quick references for the equipment we support. Power, connections, environment. In that order. For an infection control product, we evaluate fit with the existing workflow before we run the kill-claims comparisons. Per FTC guidelines (ftc.gov), claims like "hospital-grade" and "clinically proven" have to be substantiated, so we look at the evidence too. But the evidence only matters if the product can actually live in the facility.
We also changed how we train biomedical technicians. Instead of quizzing them on error codes, we ask them to describe the last three failures they saw and what they checked first. The answers tell me more than any manual comprehension test. Will this work in every situation? No. But it works more often than "check the manual."
The real lesson? What was best practice in 2020 may not apply in 2025. But some things are permanent: a nurse at 2 a.m. doesn't need a 40-page manual. She needs a clear next step. The manual can wait.
