Early on, before TELCOR was TELCOR, the team did contract engineering for point of care device manufacturers, building one data management application for one instrument at a time. When other manufacturers asked for the same thing, TELCOR chose a different path. The founders could see that a customer would eventually have twenty or thirty device types, and a separate data management system for every brand wasn't going to work.
IT FEELS LIKE ONE PURCHASE. IT'S REALLY THREE DECISIONS.
When a hospital buys a new point of care device, nobody experiences it as three choices. You pick the analyzer, sign the paperwork, and get it on the unit. But tucked inside the purchase are three decisions that behave very differently once the ink is dry.
Which device to buy. It's a clinical and workflow question, and the easiest one to revisit at the next refresh cycle.
Which data management layer sits on top of it. This one usually gets made by default, because the software comes with the device.
How the software contract is structured. Almost nobody negotiates it, and it's the one that can box you in the longest.
Most vendor dependency doesn't come from the device. It comes from what happens to the second and third decisions once the first one is made.
WHY THIS CAN'T WAIT.
None of these pressures are new. What's new is that they're all arriving at once, at programs often run by a handful of people for whom testing is one part of a much bigger job.
Testing keeps moving out of the lab and onto more devices, in the hands of thousands of nurses, respiratory therapists, physicians, and OR staff who all have to be trained, certified, and re-certified on every device they touch. The documentation bar for that testing keeps rising. Consolidation means every acquired practice arrives with whatever brands its old owner bought. And device manufacturers, seeing the same fragmentation you do, want to become the platform you standardize on, built around their own instruments first.
The paper walks through each of these pressures, with the numbers behind them.
ONE VENDOR, OR VENDOR NEUTRAL?
Vendor-neutral isn't the answer for everybody. If you're a small hospital running one device type from one manufacturer, you don't have a multi-vendor problem to solve. The paper lays out the narrow but real cases where staying on a manufacturer's own platform is the right call, including one category of instruments where a neutral platform simply can't do what the manufacturer's software does.
For most programs, though, one connectivity layer across every device is a much stronger case. You just won't see it if you only compare software price tags.
Here's the cost that shows up most often. Picture a nurse who runs a coag test, a glucose check, and a urine test in one shift. If those devices live in different systems, her training record, certification date, and competency file can end up in two or three places, entered by people who can't see each other's work. That's duplicated effort and the risk of serious errors. Then the surveyor arrives, and you're pulling half her file from one system and the rest from another.
Then there's the device you never buy. If a device can't be connected, results get charted by hand, and most programs won't accept that, so the best clinical fit quietly drops off the shortlist. With an independent connectivity layer, connecting a new device is routine work, and that constraint comes off the table.
NOBODY THINKS TO NEGOTIATE THE CONTRACT.
The longest-lived decision in all of this isn't the device. It's the contract underneath the data management layer.
Some device-tied contracts start a new clock every time you add a device: a five-year term here, a seven-year term there, none of them lining up. After a decade, a hospital can't say, without digging through a stack of agreements, what's up for renewal and what's locked in for years. That's not an accident. It's a structural pattern in how some vendors build these contracts.
TELCOR built its contracts the opposite way. Every device a customer adds folds into one annual renewal date, so swapping a device is a line-item change, not a renegotiation. Whatever platform you choose, ask about this in writing before you sign.
WHAT'S IN THE FULL PAPER.
This post gives you the argument. The paper gives you the tools to test it against your own program:
A cost model. The line items that belong in any comparison of “included” and separately purchased software, including where the cost of “free” software usually ends up.
Four red-flag questions. What to ask any vendor whose device comes bundled with its own software, including where your data goes when something breaks.
A seven-question self-assessment to answer internally before your next vendor call. Here's one to start with: do you know, right now, without looking it up, when each of your point of care contracts renews?
Where this is headed. Why the pressure on point of care programs will keep building, and why an industry connectivity standard hasn't solved it.
Ask TELCOR every one of these questions too. Run the same evaluation on every vendor, including TELCOR, and you'll know whether next year's device decision is still open, or whether it got settled the day you signed.
