IDENTIFICATION OF DEVICES IN A MEDICAL DEVICE NETWORK AND WIRELESS DATA COMMUNICATION TECHNIQUES UTILIZING DEVICE IDENTIFIERS

• US 20070253021A1
• Filed: 02/05/2007
• Published: 11/01/2007
• Est. Priority Date: 04/28/2006
• Status: Abandoned Application

• Current Assignee: Medtronic Minimed Incorporated (Medtronic Plc)
• Original Assignee: Medtronic Minimed Incorporated (Medtronic Plc)
• Inventors: MEHTA, Kaezad J., PATEL, Himanshu, JOLLOTA, James
• Application Number:
  US11/671,170
• Publication Number:
  US 20070253021A1
• Time in Patent Office: Days
• US Class Current: 358/1.150
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61M 2205/18 with alarm
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/3584 using modem, internet or bluetooth
• CPC Class Codes: A61M 2205/3592 using telemetric means, e.g. radio or optical transmission
• CPC Class Codes: A61M 2205/50 with microprocessors or computers
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 84/10 Small scale networks; Flat hierarchical networks
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y10S 370/913 : Wireless or radio

Abstract

A fluid infusion system as described herein includes a number of local “body network” devices, such as an infusion pump, a handheld monitor or controller, a physiological sensor, and a bedside or hospital monitor. The body network devices can be configured to support communication of status data, physiological information, alerts, control signals, and other information between one another. In addition, the body network devices can be configured to support networked communication of status data, physiological information, alerts, control signals, and other information between the body network devices and “external” devices, systems, or communication networks. The networked medical devices are configured to support a variety of wireless data communication protocols for efficient communication of data within the medical device network. In addition, the wireless medical devices may be configured to support a number of dynamically adjustable wireless data communication modes to react to current operating conditions, application-specific data content, or other criteria.

Claims

1. A method for configuring a device in a medical device network, the method comprising:

obtaining at least one base identifier associated with characteristics of deployment of the device within the medical device network;

generating a key for the device from the at least one base identifier, wherein the key uniquely identifies the device within the medical device network; and

initiating storage of the key at the device.

2. A method according to claim 1, wherein the at least one base identifier comprises a serial number for the device.

3. A method according to claim 1, wherein the at least one base identifier comprises a device type identifier for the device.

4. A method according to claim 1, wherein the at least one base identifier comprises a user identifier for a user of the device.

5. A method according to claim 4, wherein the user identifier distinguishes a patient-user of the device from a caregiver-user of the device.

6. A method according to claim 1, wherein:

the at least one base identifier comprises a subnetwork identifier for the device; and

the subnetwork identifier is common to a subset of devices in the medical device network.

7. A method according to claim 1, wherein the generating step derives the key from two or more of:

a serial number for the device;

a device type identifier for the device;

a user identifier for a user of the device, wherein the user identifier distinguishes a patient-user of the device from a non-patient-user of the device; and

a subnetwork identifier for the device, wherein the subnetwork identifier is common to a subset of devices in the medical device network.

8. A method according to claim 7, further comprising obtaining the two or more of the serial number, the device type identifier, the user identifier, and the subnetwork identifier via a user interface of the device.

9. A method according to claim 1, wherein the device performs the obtaining, generating, and initiating steps.

10. A method according to claim 9, wherein the obtaining step comprises receiving, by the device, the at least one base identifier from another device in the medical device network.

11. A method according to claim 1, wherein:

a programming device performs the obtaining, generating, and initiating steps; and

the method further comprises transmitting the key from the programming device to the device.

12. A method according to claim 1, further comprising transmitting the key to another device in the medical device network.

13. A communication method for a medical device network having a first device and a second device configured to communicate data between each other using a synchronized data communication protocol, the method comprising:

maintaining, at the first device, a first key that uniquely identifies the first device within the medical device network, and a second key that uniquely identifies the second device within the medical device network;

maintaining, at the second device, the first key and the second key;

the first device transmitting a data packet intended for the second device, the data packet conveying a quantity of data along with the first key; and

the second device transmitting a response packet intended for the first device, the response packet conveying the second key.

14. A method according to claim 13, wherein the response packet conveys an acknowledgement of the data packet.

15. A method according to claim 13, wherein the response packet conveys a negative acknowledgement of the data packet.

16. A method according to claim 13, further comprising:

the second device receiving the data packet;

the second device extracting the first key from the data packet; and

the second device analyzing the first key to determine whether the data packet was intended for the second device.

17. A method according to claim 13, further comprising:

maintaining, at the second device, a third key that uniquely identifies a third device within the medical device network;

the second device designating the third key as an invalid key; and

the second device ignoring received data packets that convey the third key.

18. A method according to claim 13, further comprising:

the second device receiving the data packet;

the second device extracting the quantity of data; and

the second device analyzing the quantity of data to determine whether the data packet was intended for the second device.

19. A method according to claim 13, further comprising:

the second device receiving the data packet; and

the second device determining whether the data packet was intended for the second device based upon timing characteristics of the data packet.

20. A medical device network comprising:

a first device having memory configured to store a first key that uniquely identifies the first device within the medical device network, and a second key that uniquely identifies the second device within the medical device network; and

a second device configured to communicate data with the first device using a synchronized data communication protocol, the second device having memory configured to store the first key and the second key;

wherein

the first device is configured to transmit a data packet intended for the second device, the data packet conveying a quantity of data along with the first key; and

the second device is configured to transmit a response packet intended for the first device, the response packet conveying the second key.

21. A medical device network according to claim 20, further comprising a third device having memory configured to store the first key, the second key, and a third key that uniquely identifies the third device within the medical device network, wherein:

the memory of the second device is configured to store the third key;

the second device designates the third key as an invalid key; and

the second device ignores received data packets that convey the third key.

22. A communication method for a medical device network having a first device and a second device configured to communicate data between each other using an asynchronous data communication protocol, the method comprising:

maintaining, at the first device, a first key that uniquely identifies the first device within the medical device network, and a second key that uniquely identifies the second device within the medical device network;

maintaining, at the second device, the first key and the second key;

the first device transmitting a data packet intended for the second device, the data packet conveying a quantity of data along with the first key and the second key; and

the second device transmitting a response packet intended for the first device, the response packet conveying the first key and the second key.

23. A method according to claim 22, wherein the response packet conveys an acknowledgement of the data packet.

24. A method according to claim 22, wherein the response packet conveys a negative acknowledgement of the data packet.

25. A method according to claim 22, further comprising:

the second device receiving the data packet;

the second device extracting the first key from the data packet; and

the second device analyzing the first key to identify the first device.

26. A method according to claim 22, further comprising:

the second device receiving the data packet;

the second device extracting the quantity of data; and

the second device analyzing the quantity of data to determine whether the data packet was intended for the second device.

27. A communication method for a medical device network having a master device and a slave device configured to communicate data between each other using a synchronized data communication protocol, the method comprising:

maintaining, at the master device, a first key that uniquely identifies the master device within the medical device network, a second key that uniquely identifies the slave device within the medical device network, and additional keys that respectively identify all other slave devices within the medical device network;

maintaining, at the slave device, the first key and the second key;

the slave device transmitting a data packet intended for the master device, the data packet conveying a quantity of data along with the first key; and

the master device transmitting a response packet intended for the slave device.

28. A method according to claim 27, wherein the response packet conveys the second key.

29. A method according to claim 27, wherein the response packet conveys an acknowledgement of the data packet.

30. A method according to claim 27, wherein the response packet conveys a negative acknowledgement of the data packet.

31. A method according to claim 27, further comprising:

the master device receiving the data packet;

the master device extracting the first key from the data packet; and

the master device analyzing the first key to determine whether the data packet was intended for the master device.

32. A method according to claim 27, further comprising:

the master device receiving the data packet;

the master device extracting the quantity of data; and

the master device analyzing the quantity of data to determine whether the data packet was intended for the master device.

33. A medical device network comprising:

a master device having memory configured to store a first key that uniquely identifies the master device, and additional keys that respectively identify all slave devices within the medical device network;

a slave device configured to communicate data with the master device using a synchronized data communication protocol, the slave device having memory configured to store the first key and a second key that uniquely identifies the slave device within the medical device network;

wherein

the slave device is configured to transmit a data packet intended for the master device, the data packet conveying a quantity of data along with the first key; and

the master device is configured to transmit a response packet intended for the slave device.

34. A medical device network according to claim 33, wherein the response packet conveys the second key.

35. A medical device network according to claim 33, wherein the response packet conveys an acknowledgement of the data packet.

36. A medical device network according to claim 33, wherein the response packet conveys a negative acknowledgement of the data packet.

37. A medical device network according to claim 33, wherein the master device is configured to:

receive the data packet;

extract the quantity of data; and

analyze the quantity of data to determine whether the data packet was intended for the master device.