Surgical network determination of prioritization of communication, interaction, or processing based on system or device needs
A surgical hub within a surgical hub network may include a controller having a processor, in which the controller may determine a priority of a communication, an interaction, or a processing of information based on a requirement of a system or a device communicating with the hub. The controller may prioritize an order of transmission of communication packets, including packets to a device outside of the network. The packets may include data to update routines, processes, or execute a critical procedural step. The controller may prioritize a communication traffic flow within the hub network. A network of surgical hubs may include a first hub having a first controller and a second hub having a second controller. The first controller may control interactions between the first hub and the second hub based on the capabilities of the first hub and a location of modules within the network.
1. A surgical hub within a surgical hub network comprising:
a controller comprising a processor, wherein the controller is configured to determine a priority of a communication, an interaction, or a processing of information during a surgical procedure based on a requirement of a system or a surgical device used during the surgical procedure in communication with the surgical hub,
wherein the controller comprises a default configuration to:
assign a highest priority of the communication, the interaction, or the processing of information to monitoring a patient status;
assign a second highest priority of the communication, the interaction, or the processing of information to communication of the surgical device with the surgical hub; and
assign a third highest priority of the communication, the interaction, or the processing of information to communication with a second surgical hub within the surgical hub network.
2. The surgical hub of claim 1 , wherein the controller is configured to prioritize an order of transmission of one or more communication packets.
3. The surgical hub of claim 2 , wherein the one or more communication packets are directed to a device outside of the surgical hub network.
4. The surgical hub of claim 3 , wherein the one or more communication packets comprise data to update routines, processes, or data required to execute a critical procedural step executed by the processor.
5. The surgical hub of claim 1 , wherein the controller is configured to prioritize a communication traffic flow within the surgical hub network.
6. The surgical hub of claim 5 , wherein the controller is configured to adjust the communication traffic flow to enable a more critical piece of data to take priority over a less critical piece of data thereby insuring the success of a device, a hub process, or a hub operation configured to transmit or receive the more critical piece of data.
7. The surgical hub of claim 5 , wherein the controller is configured to delay or interrupt the communication traffic flow.
8. The surgical hub of claim 7 , wherein the controller is configured to interrupt the communication traffic flow and the interruption of the communication traffic flow comprises a re-ordering of communication packets.
9. The surgical hub of claim 7 , wherein the controller is configured to delay the communication traffic flow and the delay of the communication traffic flow comprises an adjustment to a data collection or to a transmission rate.
10. The surgical hub of claim 6 , wherein the adjustment continues for a period of time less than a period of time corresponding to a duration of the surgical procedure.
11. The surgical hub of claim 6 , wherein the adjustment continues for an entire duration of the surgical procedure.
12. The surgical hub of claim 6 , wherein the adjustment continues until the prioritization of the communication traffic flow changes.
13. The surgical hub of claim 1 , wherein the controller is configured to change the default configuration based at least in part on the surgical procedure.
14. A network of surgical hubs, comprising:
a first surgical hub having a first controller; and
a second surgical hub having a second controller,
wherein the first controller is configured to control one or more interactions between the first surgical hub and the second surgical hub based on one or more capabilities of the first surgical hub and a location of one or more modules within the network of surgical hubs,
wherein the one or more capabilities of the first surgical hub comprise one or more of a computing capacity of the first surgical hub, a type of the first surgical hub, a type of data associated with the first surgical hub, an interaction of the data needed to perform a specified surgical procedure by the first surgical hub, or a computing requirement of the first surgical hub, and
wherein the first controller is further configured to allow the second controller to control the one or more interactions between the first surgical hub and the second surgical hub based on an anticipated surgical procedure.
15. The network of surgical hubs of claim 14 , wherein the control of the one or more interactions comprises a control of one or more task ownerships.
16. The network of surgical hubs of claim 14 , wherein the computing capacity of the first surgical hub comprises one or more of an available processing power, an available processor memory for data storage, an available amount of idle processing cycles, and an available communication bandwidth.
17. The network of surgical hubs of claim 14 , wherein the location of the one or more modules comprises a location of the one or more modules deemed necessary for a successful outcome of an ongoing surgical procedure.