What's new

Medical Device Connectivity

What's new for readers who have already read the book, newest first.

The fill-in tools can be downloaded as spreadsheets

Fourteen of the buyer and builder tools in the online companion at intellectualfrontiers.com now offer a spreadsheet download of their tables, including the Device Classification Worksheet, the Four Truths Data Inventory, the Device Identity Matrix and the Synchronization Test Plan. The printed columns for writing in are narrow; a spreadsheet gives you room to fill in one copy per device, fleet or product and keep it with the decision it informed. Each page still shows the tool on screen, and your printed copy does not change.

All twenty field tools are now in the online companion

The two printed appendices of field tools, one for hospital buyers and one for device builders, are now twenty tools in the online companion at intellectualfrontiers.com, with every table and checklist carried over row for row. Buyers get nine tools that take a device from classification to retirement: place a device on four axes before naming its category, ask the vendor seventeen questions in writing before shortlisting, put each connectivity requirement into contract language, get every cloud exit protection into the contract, and test a vendor's AI-ready claim against twelve capabilities. Builders get eleven that take a device from evidence inventory to release: list every kind of evidence a device produces, review the architecture for any dependence on the network, test disconnection as a normal operating condition, check update and rollback before every field release, and start the threat model with every system element. An appendix in the book lists the twenty tools and the chapter that uses each, and prints short one-page versions of the two most-used, the No Connectivity, No Purchase Checklist and the Connectivity Maturity Model, for readers without the web.

New book: Medical Device Connectivity

Most hospital devices do real clinical and operational work, and most of them can't report what they did. When a device can't report, staff write it down by hand, rebuild it later, or never learn it at all. Medical Device Connectivity shows hospitals what to require when they buy institutional devices, and shows manufacturers how to build devices that keep working safely when the network is down, report what they did when it is up, and give people and AI the evidence they need. Buyers learn to sort devices by who operates them and who pays when they fail, list the evidence each device can produce, and write purchase requirements for data, interfaces, updates and offline behavior. Builders learn to design devices whose essential function never depends on the network or a vendor's cloud, to manage and secure them as a fleet across their life, and to build in testability so AI can help with verification and regulatory work. It has 22 chapters in five parts.