Medical device communication method

Patent metadata

Field	Value
Publication number	US-10812380-B2
Application number	US-201916446381-A
Country	US
Kind code	B2
Filing date	Jun 19, 2019
Priority date	Mar 6, 2013
Publication date	Oct 20, 2020
Grant date	Oct 20, 2020

Abstract

A medical device communication method that may be implemented within a variety of medical devices including but not limited to infusion pumps. The method may be implemented with a protocol stack for at least intra-device communication. Embodiments provide connection-oriented, connectionless-oriented, broadcast and multicast data exchange with priority handling of data, fragmentation, and reassembly of data, unique static and dynamic address assignment and hot swap capability for connected peripherals or subsystems.

First claim

What is claimed is:

1. A communication system for connecting a pump motor controller with a root controller, the communication system comprising:
a pump motor controller configured to transmit a first message to a root controller, the first message comprising a request for an address;
a root controller configured to:
receive the first message;
determine in a stored table that there is no entry corresponding to the pump motor controller;
generate a connection identifier for the pump motor controller based on the determination;
associate the connection identifier in the stored table with the pump motor controller; and
transmit the connection identifier to the pump motor controller, wherein the pump motor controller is further configured to update its identity with the connection identifier.

2. The communication system of claim 1 , wherein the root controller is further configured to facilitate transmission of a second message from the pump motor controller to an additional hardware, wherein the pump motor controller and the additional hardware are not directly connected.

3. The communication system of claim 2 , wherein the second message is transferred between a plurality of message layers by copying a pointer and without copying said second message itself.

4. The communication system of claim 2 , wherein a session layer communication is made independent of bus topology.

5. The communication system of claim 1 , wherein the root controller is further configured to transmit the connection identifier to a second pump motor controller that replaces the pump motor controller.

6. The communication system of claim 1 , wherein a fragmented message is reassembled into a complete message in an application buffer.

7. The communication system of claim 1 , wherein the root controller is further configured to:
determine that a size of data to transfer is larger than a predetermined fragmentation value; and
pack said data in a plurality of messages independent of an underlying data bus width.

8. The communication system of claim 1 , wherein the root controller is further configured to request memory from a buffer comprising non-uniform sizes.

9. The communication system of claim 1 , wherein the pump motor controller is connected with the root controller without altering an application of the pump motor controller.

10. The communication system of claim 1 , wherein a root controller manages connection requests from the plurality of pump motor controllers.

11. A method for connecting hardware components of an infusion pump system, the method comprising:
receiving a first message corresponding to a first request for an address from a first pump motor controller;
determining in a stored table that there is no entry corresponding to the first pump motor controller;
associating a first connection identifier for the first pump motor controller based on the determination;
transmitting the first connection identifier to the first motor controller wherein the first pump motor controller is further configured to update its identity with the first connection identifier;
receiving a second message corresponding to a second request for an address from a second pump motor controller;
determining that the second pump motor controller has replaced the first pump motor controller;
changing the association of the first connection identifier from the first pump moto controller to the second motor controller;
transmitting the first connection identifier to the second motor controller, wherein the second motor controller is further configured to update its identity with the first connection identifier.

12. The method of claim 11 , further comprising facilitating transmission of a second message from the pump motor controller to an additional hardware, wherein the pump motor controller and the additional hardware are not directly connected.

13. The method of claim 11 , further comprising transmitting messages between hardware components by copying a pointer and without copying the messages.

14. The method of claim 11 , wherein a session layer communication is made independent of bus topology.

15. The method of claim 11 , wherein a fragmented message is reassembled into a complete message in an application buffer.

16. The method of claim 11 , further comprising determining that a size of data to transfer is larger than a predetermined fragmentation value and packing said data in a plurality of messages independent of an underlying data bus width.

17. The method of claim 11 , further comprising requesting memory from a buffer comprising non-uniform sizes.

Assignees

• Icu Medical Inc

Inventors

• Jha Prakash Kumar Arvind
• Cudney James
• Herr Benjamin
• Lee Mark I
• Picinich Matteo D

Classifications

• H04L69/32

  Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level · CPC title

• G16H20/17

  delivered via infusion or injection · CPC title

• H04L69/165

  Combined use of TCP and UDP protocols; selection criteria therefor · CPC title

• G16H40/63

  for local operation · CPC title

• H04L45/302

  Route determination based on requested QoS · CPC title