Communication hub and storage device for storing parameters and status of a surgical device to be shared with cloud based analytics systems
Various surgical hubs are disclosed. A surgical hub comprises a storage device; a processor coupled to the storage device; and a memory coupled to the processor. The memory stores instructions executable by the processor to: receive data from a surgical instrument coupled to the surgical hub; and determine a rate at which to transfer the data from the surgical hub to a remote cloud-based medical analytics network based on available storage capacity of the storage device.
1. A surgical hub comprising:
a storage device;
a processor coupled to the storage device; and
a memory coupled to the processor, the memory storing instructions executable by the processor to:
receive data from a surgical instrument coupled to the surgical hub;
determine a data transmission rate at which to transfer the data from the surgical hub to a remote cloud-based medical analytics network based on available storage capacity of the storage device;
determine a type of data to transfer from the surgical hub to the remote cloud-based medical analytics network, wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network comprises data associated with a failure event of the surgical instrument;
detect surgical hub network down time; and
determine a frequency at which to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the detected surgical hub network down time.
2. The surgical hub of claim 1 , wherein the memory stores instructions executable by the processor to determine when and how often to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the available storage capacity of the storage device.
3. The surgical hub of claim 1 , wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network is based on a user, patient, or surgical procedure.
4. The surgical hub of claim 1 , wherein the memory stores instructions executable by the processor to determine when to transfer data from the surgical hub to the remote cloud-based medical analytics network.
5. The surgical hub of claim 1 , wherein the memory stores instructions executable by the processor to receive new operational parameters for the surgical hub from the remote cloud-based medical analytics network.
6. The surgical hub of claim 1 , wherein the memory stores instructions executable by the processor to receive new operational parameters for the surgical instrument from the remote cloud-based medical analytics network.
7. The surgical hub of claim 1 , wherein the memory stores instructions executable by the processor to prioritize the data to transfer from the surgical hub to a remote cloud-based medical analytics network.
8. The surgical hub of claim 7 , wherein the data is prioritized based on criticality thereof.
9. A method of transmitting data from a surgical hub to a remote cloud-based medical analytics network, the surgical hub comprising a storage device, a processor coupled to the storage device, and a memory coupled to the processor, the memory storing instructions executable by the processor, the method comprising:
receiving, by the processor, data from a surgical instrument coupled to the surgical hub;
determining, by the processor, a data transmission rate at which to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on available storage capacity of the storage device coupled to the surgical hub;
determining, by the processor, a type of data to transfer from the surgical hub to the remote cloud-based medical analytics network, wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network comprises data associated with a failure event of the surgical instrument;
detecting, by the processor, surgical hub network down time; and
determining, by the processor, a frequency at which to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the detected surgical hub network down time.
10. The method of claim 9 , comprising determining, by the processor, when and how often to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the available storage capacity of the storage device.
11. The method of claim 9 , wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network is based on a user, patient, or surgical procedure.
12. The method of claim 9 , comprising determining, by the processor, when to transfer the data from the surgical hub to the remote cloud-based medical analytics network.
13. The method of claim 9 , comprising receiving, by the processor, new operational parameters for the surgical hub from the remote cloud-based medical analytics network.
14. The method of claim 9 , comprising receiving, by the processor, new operational parameters for the surgical instrument from the remote cloud-based medical analytics network.
15. A non-transitory computer readable medium storing computer readable instructions which, when executed, causes a machine to:
receive data from a surgical instrument coupled to a surgical hub;
determine a data transmission rate at which to transfer the data from the surgical hub to a remote cloud-based medical analytics network based on available storage capacity of a storage device;
determine a type of data to transfer from the surgical hub to the remote cloud-based medical analytics network, wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network comprises data associated with a failure event of the surgical instrument;
detect surgical hub network down time; and
determine a frequency at which to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the detected surgical hub network down time.
16. The non-transitory computer readable medium of claim 15 , storing computer readable instructions which, when executed, causes the machine to determine when and how often to transfer the data from the surgical hub to the remote cloud-based medical analytics network based on the available storage capacity of the storage device.
17. The non-transitory computer readable medium of claim 15 , wherein the type of data to transfer from the surgical hub to the remote cloud-based medical analytics network is based a user, patient, or surgical procedure.
18. The non-transitory computer readable medium of claim 15 , storing computer readable instructions which, when executed, causes the machine to determine when to transfer data from the surgical hub to the remote cloud-based medical analytics network.
19. The non-transitory computer readable medium of claim 15 , storing computer readable instructions which, when executed, causes the machine to receive new operational parameters for the surgical hub from the remote cloud-based medical analytics network.
20. The non-transitory computer readable medium of claim 15 , storing computer readable instructions which, when executed, causes the machine to receive new operational parameters for the surgical instrument from the remote cloud-based medical analytics network.