System, method, and apparatus for communicating data

Patent metadata

Field	Value
Publication number	US-11830617-B2
Application number	US-202217573078-A
Country	US
Kind code	B2
Filing date	Jan 11, 2022
Priority date	Jan 22, 2010
Publication date	Nov 28, 2023
Grant date	Nov 28, 2023

Abstract

A hub is disclosed that includes a network, first and second modules, a processor, a failsafe bus, and an alarm wire bus. The network interface component communicates data with a medical device. The first module interfaces with a first communications channel, and the second module interfaces with a second communications channel. The processor packages the data from the medical device into at least one packet. The processor communicates with one of the first and second modules to communicate one or more packets over one of the first and second communications channels. The failsafe bus signals from the hub to the medical device when a fatal-error fault condition of the hub has occurred. The alarm wire bus signals from the hub to the medical device when an alarm condition of the hub has occurred to cause the medical device to execute at least one mitigation.

First claim

What is claimed is:

1. A hub, comprising:
a network interface component configured to communicate data with a medical device;
a first module configured to interface with a first communications channel;
a second module configured to interface with a second communications channel;
a processor configured to package the data from the medical device into at least one packet, wherein a packet of the at least one packet includes a header, the processor further configured to operatively communicate with one of the first and second modules to communicate the at least one packet over one of the first and second communications channels;
a failsafe bus configured to signal from the hub to the medical device when a fatal-error fault condition of the hub has occurred; and
an alarm wire bus configured to signal from the hub to the medical device when an alarm condition of the hub has occurred to cause the medical device to execute at least one mitigation.

2. The hub according to claim 1 , wherein the first communications channel is a first cellular network, and the second communications channel is a second cellular network.

3. The hub according to claim 1 , wherein the processor is further configured to associate the hub with one of an identification value, a patient, the medical device, and a treatment.

4. The hub according to claim 1 , further comprising a plain-old-telephone-service component, wherein the processor is configured to route the packet through the plain-old-telephone-service component when the first and second communications channels are unavailable.

5. The hub according to claim 1 , wherein:
the first communications channel is through a LAN, and
the at least one mitigation includes lowering a LAN-connection bandwidth of the LAN.

6. The hub according to claim 1 , wherein the at least one mitigation includes using an internal cellular connection to communicate with a network.

7. The hub according to claim 1 , wherein the at least one mitigation includes using an internal cellular connection to communicate with a network defined by the first communications channel.

8. The hub according to claim 1 , wherein the medical device communicates to the hub a list of conditions of the hub that trigger the alarm condition.

9. The hub according to claim 1 , wherein the alarm condition is a function of a capability of a network.

10. The hub according to claim 1 , wherein the alarm condition is a function of a performance of a network.

11. The hub according to claim 1 , wherein the alarm condition is a function of a capability of the hub.

12. The hub according to claim 1 , wherein the alarm condition is a function of a performance of the hub.

13. The hub according to claim 1 , wherein the medical device is configured to operate independently of the hub when the fatal-error fault condition of the hub occurs.

14. The hub according to claim 1 , wherein the medical device communicates to the hub a list of conditions of the hub that trigger the fatal-error fault condition.

Assignees

• Deka Products Lp
• Deka Products Ltd Partneship

Inventors

• Kamen Dean
• Kerwin John M
• Ballantyne Todd A
• Morgan Frederick
• Demers Jason A
• Biasi John J

Classifications

• G16H40/67 Primary

  for remote operation · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G16H40/63

  for local operation · CPC title

• H04L41/06

  Management of faults, events, alarms or notifications · CPC title

• H04L43/10

  Active monitoring, e.g. heartbeat, ping or trace-route · CPC title