Associating an information reader and a medical device

Patent No. US9053520 (titled "Associating an information reader and a medical device") on Oct 17, 2011. The application was issued on Jun 9, 2015.

What is this patent about?

’520 is related to the field of medical device integration and data management systems. It specifically addresses the technical challenges of reliably routing data from peripheral input devices, such as barcode scanners or RFID readers, to specific clinical hardware like infusion pumps or ventilators in a dynamic hospital environment.

The underlying idea behind ’520 is the creation of a flexible, software-mediated link between a scanner and a medical device that is not dependent on a permanent physical connection. By scanning a specialized association barcode or tag, the scanner captures both the unique identity of the target medical device and the routing parameters for a device agent, effectively “pairing” the two units logically so that all subsequent data captures are directed to the correct clinical context.

The claims of ’520 focus on a device agent that manages the lifecycle of this connection by processing association information that includes a specific data element, such as a cookie. This data element is appended to all subsequent scans to ensure the system can uniquely identify which medical device is the intended recipient of the data, while also providing mechanisms to automatically terminate the link based on specific workflow events.

In practice, the invention allows a single handheld scanner to be moved between different bedside units by simply scanning a setup code displayed on or near the target machine. The device agent acts as a traffic controller, using the appended data element to route medication or patient information to the active device, and can even process scans that were stored in memory before the association was finalized to ensure no data is lost during the transition.

This approach differs from prior solutions by moving away from rigid, one-to-one hardware tethering or centralized systems that lack device-specific routing logic. By incorporating automatic disassociation triggers—such as the completion of a drug administration sequence, a timeout, or a physical distance limit—the system ensures that a scanner does not remain accidentally linked to the wrong device, thereby preventing critical medication errors.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’520 was filed, barcode integration in clinical environments was typically implemented using fixed-wire connections where a scanner was physically or logically tethered to a single host medical device. At a time when systems commonly relied on centralized backend servers to process peripheral inputs for general identification purposes, the routing of data between disparate hardware components was constrained by static associations. Hardware and software limitations made the dynamic, ad hoc redirection of scanner input to specific, non-tethered medical devices non-trivial, as communication protocols were generally designed for point-to-point hardware parity rather than flexible workflow-driven routing.

Prosecution Position

The disclosed invention addresses the technical constraint of rigid hardware-to-device associations by introducing an architectural shift that enables a mobile scanner to be dynamically paired with specific medical devices through a scanning-based intent protocol. By utilizing a specialized scan to establish a temporary communication link, the system overcomes the limitation of fixed-tethered peripherals and the lack of device-specific routing in centralized systems. This integration allows for the redirection of subsequent data scans to a targeted device, achieving a technical effect of increased hardware flexibility and improved workflow accuracy without requiring permanent physical interfaces between the scanner and the medical equipment.

Claims

This patent contains 20 total claims, with claims 1, 10, and 18 serving as the independent claims. The independent claims focus on a device agent, method, and system for establishing a functional link between a medical device and an information reader by utilizing specific association data to identify scans and managing the connection through automated disassociation triggered by workflow events. The dependent claims serve to further define the hardware components, such as barcode or RFID readers, specify data routing protocols for both new and previously obtained information, and establish proximity-based or event-driven parameters for maintaining or terminating the device association.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Association information
(Claim 1, Claim 10, Claim 18)
Association information 210 is information that is used to associate a medical device and an information reader. In one embodiment, the association information 210 is a barcode. The association information 210 includes medical device information 212 and device agent information 214.Data obtained via an information reader that includes unique identification for a medical device and specific information for a device agent to facilitate a logical link between the reader and the device.
Data element
(Claim 1, Claim 18)
The association information 210 includes a data element that is appended to scans after the association of the medical device and the information reader. This allows for the scans to be identified as being intended for the medical device.A specific piece of information within the association data that is added to subsequent scans to ensure those scans are routed or identified as belonging to the associated medical device.
Device agent
(Claim 1, Claim 10, Claim 18)
Device agent 130 is for associating a medical device and an information reader. In one embodiment, device agent 130 is a server. In another embodiment, device agent 130 is a medical device.A functional entity, distinct from the information reader, that processes association information to establish and manage the connection between a medical device and the reader.
Medical device information
(Claim 1, Claim 10, Claim 18)
Medical device information 212 is information that uniquely identifies a medical device. For example, medical device information 212 can be, but is not limited to, a serial number of a medical device, a MAC address, or a name of the medical device.A component of the association information used to uniquely identify a specific medical device for the purpose of establishing a targeted communication link.
Workflow event
(Claim 10, Claim 18)
The association between the medical device and the information reader is automatically disassociated in response to completion of a workflow event. A workflow event can be, but is not limited to, a power down of a medical device, a log off of a medical device, or a completion of a medical protocol.A triggering condition or completed task that signals the device agent to automatically terminate the logical association between the information reader and the medical device.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
1:25-cv-00591May 12, 2025Becton, Dickinson And Company V. Baxter International Inc.

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US9053520

Application Number
US13275005A
Filing Date
Oct 17, 2011
Publication Date
Jun 9, 2015
External Links
Slate, USPTO , Google Patents