Today, a robot's identity lives inside its own vendor's fleet manager. There is no institution-level registry that says, in one place, "here is every autonomous system currently operating in this building, regardless of manufacturer." Cross-vendor robot identity is what that registry provides — a shared identity layer that sits above individual vendor systems.
How it differs from a vendor fleet manager
A vendor fleet manager tracks and manages robots from one manufacturer only. It knows everything about its own robots and nothing about anyone else's. Cross-vendor robot identity doesn't replace these vendor systems — it sits above them, pulling each robot's identity into one shared institutional record so a hospital doesn't need five separate systems to answer "what robots do we have, and what can each of them do."
Why it matters in healthcare
As hospitals adopt robots from multiple manufacturers, fragmentation compounds fast. Without a shared identity layer, there's no single place to answer basic questions: how many autonomous systems are active in the building right now, which ones are authorized for which tasks, and who is accountable for each. This is the same fragmentation problem hospitals already solved for human staff through unified credentialing systems — robots don't yet have the equivalent.
A useful analogy
This is analogous to a hospital's single employee directory, which lists every staff member regardless of which department or contracting agency employs them. No one has to check five separate HR systems to find out who's currently on shift. Cross-vendor robot identity does the same job for autonomous machines.