When I first started handling medical equipment orders, I assumed a purchase order was the end of the job. It wasn't. Three years and roughly $46,000—maybe $48,000, I'd have to check the ledger—in rework, rush shipping, and dead stock later, I started asking a much better question: which procurement scenario are we actually in?
The mistake I kept making was treating every product the same. A dental autoclave is not an ostomy bag, and neither of them behaves like a remote patient monitoring program. The advice that works for one misses the point for another. That's why I've split what I know into three scenarios. None of them has one universal answer. But each scenario has a repeatable process.
Here are the three scenarios I work through now:
- Scenario A – Regulated capital equipment, like a dental autoclave.
- Scenario B – High-volume consumables, like an ostomy bag.
- Scenario C – Connected digital health, like remote patient monitoring.
Scenario A: Regulated capital equipment
If you've ever bought a dental autoclave, you know the sticker price is the least interesting number. What I mean is that the total cost includes the machine, the room modifications, the training, the maintenance contract, the sterilization monitoring supplies, and the documentation burden that follows you every year. The quotes that look cheap often hide those costs.
In 2021, I helped a clinic order a dental autoclave. We compared chamber size, cycle speed, and warranty, then picked a reasonable model. What did we miss? The counter space, the three-hour training session for three assistants, and the sterilization log requirements that came up during an inspection. That wasn't an autoclave failure. It was a total-cost failure.
Here's the counterintuitive part: do not lead with features. A 20% faster cycle doesn't help if the clinic only runs 15 loads a day. But a machine with a responsive service provider and a known calibration process helps every day. Before you sign anything, ask what happens when the machine breaks. Who answers, how fast, and where does the replacement come from? For a dental autoclave, downtime isn't just a schedule problem; it's a patient-safety risk.
My rule for Scenario A is simple: treat it as infrastructure, not as a product. Write down the regulations, the support expectations, and the training plan before you compare models. The machine is only one line in that plan.
Scenario B: High-volume consumables
Now let's talk about an ostomy bag. This is the opposite kind of purchase. It's not one device in a room; it's a product a patient lives with. When I started, I thought the goal was the lowest unit cost. The reality is the opposite: the cheapest bag can be the most expensive if it doesn't fit the person using it.
I don't have hard data on what percentage of ostomy supplies get wasted, but from my own dead-stock counts, I'd estimate it can reach 15–20% in a poorly managed formulary. That waste usually costs more than the discount you negotiated. Put another way: a product that works for 80% of patients can still create huge waste for the 20% who can't use it.
The old belief that “a bag is a bag” comes from an era when health systems carried a tiny formulary and patients had fewer choices. That's changed. Patients live with this product every day, and one bag design doesn't match every body type, skin type, or daily routine.
So my advice here is also counterintuitive: buy less variety, not more. I'll take a short list of two or three well-tested products over a catalog of low-bid options every time. The key is to test those products with real patients first. In my current process, I ask product vendors for trial samples, I document usage over two weeks, and then I make the formulary decision. That extra month of testing saves me from a year of complaints and returns. Also, include education. If clinicians can't show a patient how to use the bag, it doesn't matter how good it looked in the sample box.
Scenario C: Connected digital health and remote patient monitoring
The third scenario is where I've watched teams get excited—and a few of them bought the same mistake I almost made. Before any technology decision, you need to answer a basic question: what is remote patient monitoring? In plain terms, remote patient monitoring (RPM) means collecting patient health data at home or in another non-clinical setting and sending it to a care team for review. It can be as simple as a Bluetooth blood pressure cuff with a smartphone app, or as complex as a home ventilator with a dashboard for nurses.
The mistake comes when you buy the platform before defining the workflow. I did this in 2019 with a monitoring pilot. We chose a system with impressive dashboards, then discovered we hadn't answered the boring but critical question: who watches the alerts on weekends? The system got used, but only partially, and the pilot taught me an expensive lesson about implementation.
I've found the Philips AI in healthcare report—I read the 2024 edition—a useful conversation starter. It frames artificial intelligence as a way to support clinical decisions, not replace them. That sounds obvious, but it changes the questions you ask in a demo. You stop asking “How many alerts can it show?” and start asking “Which alerts will a nurse actually act on?” A report won't give you your specific workflow, but it gives you the vocabulary to ask better questions.
For Canadian health systems, the procurement route is often provincial. If you're working with a vendor like Philips Healthcare Canada, the first questions should be about local support, data residency, and integration services in your province. The technology might be global, but the workflow always has a local address.
I'm generally an efficiency optimist. I've seen automation cut documentation time noticeably in one telehealth program. But the efficiency gain came from defining who reviews the data and when, not from the software alone. Here's the counterintuitive rule for RPM: start with the workflow, not the device. If you can't describe the whole protocol in one paragraph—who collects, who receives, who calls the patient—no amount of AI fixes it. The platform can amplify a good workflow; it can't create one.
How to tell which scenario you're in
So how do you know which lens to use? At least, that's been my experience with mid-sized clinics and regional health networks as of early 2025.
- If failure could harm a patient or threaten a license, use Scenario A. Treat it as infrastructure, not as a product swap.
- If you'll order the item thousands of times a year, use Scenario B. Track waste per product, get patient feedback, and build a short formulary with realistic exceptions.
- If the value depends on data leading to action, use Scenario C. Document the clinical pathway first, then select the technology.
I'm not here to say one brand is the absolute answer. Philips Healthcare has a strong portfolio across imaging, monitoring, and home care. But my advice is not “buy Philips Healthcare.” It's “buy with a clearly named scenario.” A good contract with a clear workflow beats a great device with a vague plan. That lesson cost me close to $48,000—and I'd rather you not repeat it.
