Reusable Medical Device Tracking: Who Owns the Instrument

Here is the fact that complicates every Hospital instrument deployment: a significant share of the instruments used in surgery are not owned by the hospital.

They arrive in vendor cases, sometimes the day before, sometimes the morning of. They belong to a manufacturer or a distributor. They are unpacked, processed, used, repacked and returned — often to a different hospital. The vendor's inventory system and the hospital's have no relationship to each other, and neither of them knows what the other believes.

This is where instrument tracking gets hard. Not because the technology is different, but because the ownership model is. Most systems are built to answer "where is our thing?" and the harder commercial question is "whose thing is this, and who is accountable for it right now?"

Four ownership models, four problems

Each needs a different tracking treatment, and mixing them into one undifferentiated Asset list is the most common design error.

Loaner trays: the sharpest version of the problem

A loaner tray for a spinal or orthopaedic procedure can contain hundreds of items, arrives in a vendor case, and must be sterilized before use — frequently on a tight schedule that pushes it to the front of the queue.

The failure modes are well known to anyone who has worked in a theatre suite:

Late arrival. The tray arrives the morning of the case. There is no time for a normal cycle, so the department is pressured into an abbreviated process. Any system that depends on advance notice fails here.

Unknown contents. The vendor's packing list is the only definition of what is in the case. If it is wrong, nobody discovers it until the surgeon asks for an instrument that is not there.

Unverified sterilization. The tray arrives having been processed elsewhere — or not at all. The receiving hospital must establish that it was cleaned and sterilized, and bear responsibility for it, without having performed the process.

Incomplete return. Trays go back with items missing. The vendor's count and the hospital's disagree weeks later, and there is no record to settle it.

Duplicate handling. Because the tray is unfamiliar, it takes disproportionately longer to inspect and assemble than an equivalent owned set.

RFID does not solve the scheduling problem, which is contractual and logistical. What it does is make contents verifiable at receipt, make the sterilization event attributable to the tray rather than to a load, and make the return a recorded transaction with a count on both sides.

Consignment: inventory that does not appear on any balance sheet

Consignment sets sit in the hospital but belong to the vendor. They are used, reprocessed and restocked, and the hospital is billed per use.

Two problems dominate. The hospital does not know what it holds, because consignment stock is not in its inventory system — so usage tracking is manual and billing depends on honesty and memory. The vendor does not know where its assets are, because they are in a hospital's sterile storage and processing loop.

Both parties want the same data and neither has it. A shared identifier — the tag ID resolving to an asset both systems recognize — is the only thing that closes this without a data-sharing project nobody has time for.

Single-use devices and the reprocessing question

Some devices are labelled single-use. Some are reprocessed by third parties under a regulatory pathway, and some are reprocessed where they should not be.

For the tracking system this creates a specific requirement: the device record must carry its intended use status, and the reprocessing event must be attributable. A tag on a single-use device that records a sterilization cycle is either evidence of legitimate third-party reprocessing or evidence of a problem — and the system should be able to tell which.

This is one of the few places where tag-side data earns its keep, because a device that travels between facilities carries its own history with it. See Sterilization Cycle Counting for why that history needs careful definition.

The accountability question

The question that actually matters in an incident is not "where is it?" but "who was accountable for it at the time?"

For a hospital-owned set, that is straightforward. For a loaner tray, accountability transfers: vendor → transport → receiving hospital → SPD → theatre → SPD → return → vendor. Each handover is a moment where responsibility for cleanliness, completeness and sterilization status changes hands.

A tracking system built only for location cannot express that. One built around handover events can. That is the design difference that matters, and it is the same principle that governs asset custody in other industries — the read at the boundary is what creates the record.

Design guidance

1. Model ownership explicitly. Vendor-owned, hospital-owned and single-use are different object types with different rules, not one asset class.

2. Tag the container and the high-value contents. Full instrument-level tagging of a loaner tray is rarely economic; tag the case, and tag the items that matter clinically or financially.

3. Verify contents at receipt against the vendor list, not against your own. You do not have a trusted list until you have checked theirs.

4. Make the sterilization event attributable to the tray, not just to the load.

5. Record the return with a count on both sides. This is what settles disputes.

6. Carry intended-use status on the device record so single-use and reprocessable items cannot be confused.

7. Agree the identifier with the vendor. If the vendor's asset ID and your tag ID are unrelated, the shared data never materializes.

Why this is the hardest part

Hospital-owned sets are a logistics problem. Loaner and consignment are a multi-party data problem, and they are worse because no single party has both the incentive and the authority to fix it.

The pragmatic entry point is receipt verification. It is the moment where the hospital's interests are most exposed — it is about to sterilize and use instruments it does not own and has not counted — and it is also the moment where a single read creates a record that is useful to both sides.

Start there. The rest of the ownership model can be built on top of it.

*Related: SPD Instrument Management · RFID Surgical Instrument Tracking · UDI RFID Compliance