IP Library Granted Patent US 12,260,953
Granted Patent B2
US 12,260,953 · App. 17/384,457 · Granted Mar 25, 2025

Detection of surgical devices within surgical systems

Inventors: Frederick E. Shelton, IV (Hillsboro, OH); Kevin M. Fiebig (Cincinnati, OH); Shane R. Adams (Lebanon, OH)
Assignee: Cilag GmbH International
G16H40/20A61B17/00A61B18/1206A61B34/10A61B34/20A61B34/25A61B34/30A61B34/32A61B90/08A61B90/37G05B13/0265G06F3/14G06F3/1423G06F3/167G06F9/4881G06F9/542G06F13/4068G06F16/211G06F16/284G06F16/285G06N20/00G06Q10/30G06T11/60G08B5/22G10L15/22G16H10/60G16H15/00G16H20/40G16H30/40G16H40/40G16H40/63G16H40/67G16H50/20G16H50/70H04L1/22H04L41/12H04L65/80H04L67/12H04L67/125H04N5/272H04N7/15A61B8/06A61B2017/00221A61B2018/00702A61B2018/00994A61B2034/2072A61B2034/254A61B2090/364A61B2090/365A61B2090/373G06F21/6245G06F40/169G10L2015/223G16H30/20H02J7/0063
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,260,953
App. No.
17/384,457
Granted
Mar 25, 2025
Kind
B2
Abstract

Examples described herein may include a surgical computing device that directs data communications to surgical networks. The surgical computing device may include a processor that is configured to determine a present network locus, wherein the present network locus is any of a first surgical network or a second surgical network; identify a data communications session; determine a surgical data type of the data communication session, wherein the surgical data type is any of a first type of surgical data or a second type of surgical data, and direct the data communications session to the first surgical network if the surgical data type is the first type of surgical data or to the second surgical network if the surgical data type is the second type of surgical data.

Claims (46)

1. A surgical computing device for performing a surgical procedure, comprising:

a processor configured to:

determine a present network locus, wherein the present network locus is at least one of a first surgical network or a second surgical network;

identify a data communication session;

derive contextual information of the data communication session related to the surgical procedure using a situational awareness system;

determine a surgical data type of the data communication session, wherein the surgical data type is at least one of a first type of surgical data or a second type of surgical data, and wherein the determination of the surgical data type is based on at least the derived contextual information related to the surgical procedure; and

direct the data communication session to the first surgical network if the surgical data type is determined to be the first type of surgical data or to the second surgical network if the surgical data type is determined to be the second type of surgical data.

2. The surgical computing device of claim 1 , wherein the first surgical network is a primary surgical network and the second surgical network is a secondary surgical network.

3. The surgical computing device of claim 1 , wherein the determination of the surgical data type is further based on connectivity adjustments of the first surgical network and the second surgical network.

4. The surgical computing device of claim 3 , wherein the connectivity adjustments are based on at least one of: latency, data transfer parameters, bandwidth, message handling, service available, or service reliability.

5. The surgical computing device of claim 1 , wherein the processor is further configured to:

determine that the surgical computing device has moved from a first operating room to a second operating room; and

determine that the present network locus is different than a previous network locus.

6. The surgical computing device of claim 5 , wherein the first surgical network is associated with the first operating room, and the second surgical network is associated with the second operating room.

7. The surgical computing device of claim 1 , wherein the situational awareness system includes a pattern recognition system that correlates surgical inputs with the surgical procedure, and wherein the contextual information is derived using the pattern recognition system.

8. A surgical computing device for performing a surgical procedure, comprising:

a processor configured to:

determine a present network locus of the processor, wherein the present network locus is at least one of a first surgical network or a second surgical network;

identify a data communication session;

derive contextual information of the data communication session related to the surgical procedure using a situational awareness system;

determine a surgical data type of the data communication session, wherein the determination of the surgical data type is based on at least the derived contextual information related to the surgical procedure; and

direct the data communication session to the first surgical network or the second surgical network based on the present network locus and the surgical data type of the data communication session.

9. The surgical computing device of claim 8 , wherein the first surgical network is a primary surgical network and the second surgical network is a secondary surgical network.

10. The surgical computing device of claim 8 , wherein the situational awareness system includes a pattern recognition system that correlates surgical inputs with the surgical procedure, and wherein the contextual information is derived using the pattern recognition system.

11. The surgical computing device of claim 8 , wherein determining if the surgical data type is based on connectivity adjustments of the first surgical network and the second surgical network.

12. The surgical computing device of claim 11 , wherein the connectivity adjustments are based on at least one of: latency, data transfer parameters, bandwidth, message handling, service available, or service reliability.

13. The surgical computing device of claim 8 , wherein when the processor has been moved from a first operating room to a second operating room, the processor is configured to determine that the present network locus is different than a previous network locus.

14. The surgical computing device of claim 13 , wherein first surgical network is present at the first operating room, and the second surgical network is present at the second operating room.

15. A surgical system for performing a surgical procedure, comprising:

a surgical hub;

a plurality of surgical modules;

a first plurality of functions within a first surgical network, wherein the first surgical network is associated with a first type of surgical data;

a second plurality of functions within a second surgical network, wherein the second surgical network is associated with a second type of surgical data; and

a processor of the surgical hub configured to:

combine at least one of the first plurality of functions with at least one of the second plurality of functions to create a third surgical network, wherein the third surgical network is connected to the surgical hub and associated with a third type of surgical data; and

a processor of at least one of the plurality of surgical modules configured to:

determine a present network locus of the processor, wherein the present network locus is at least one of the first surgical network, the second surgical network, or the third surgical network;

identify a data communication session;

derive contextual information of the data communication session related to the surgical procedure using a situational awareness system;

determine a surgical data type of the data communication session, wherein the surgical data type is at least one of a first type of surgical data, a second type of surgical data, or a third type of surgical data, and the determination of the surgical data type is based on at least the derived contextual information related to the surgical procedure; and

direct the data communication session to the third surgical network if the surgical data type is the third type of surgical data.

16. The surgical system of claim 15 , wherein the first surgical network is a primary surgical network and the second surgical network is a secondary surgical network.

17. The surgical system of claim 15 , wherein determining if the surgical data type is the third type of surgical data is based on connectivity adjustments of the third surgical network.

18. The surgical system of claim 17 , wherein the connectivity adjustments are based on at least one of: latency, data transfer parameters, bandwidth, message handling, service available, or service reliability.

19. The surgical system of claim 15 , wherein the first surgical network, the second surgical network, and the third surgical network are connected to edge servers.

20. The surgical system of claim 19 , wherein the situational awareness system includes a pattern recognition system that correlates surgical inputs with the surgical procedure, and wherein the contextual information is derived using the pattern recognition system.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2021
From: SHELTON, FREDERICK E., IV; FIEBIG, KEVIN; ADAMS, SHANE R.
To: CILAG GMBH INTERNATIONAL
Reel/Frame 057750/0331 →
Continuity (2)
Provisional Application 63224813 · Jul 22, 2021
Related Publication 20230021832A1 · Jan 26, 2023
References Cited (84)
US 5652866A · Aldred et al. · 1997 [cited by applicant]
US 6766373B1 · Beadle et al. · 2004 [cited by applicant]
US 8565073B2 · Rahman · 2013 [cited by examiner]
US 8908678B1 · McGonigal · 2014 [cited by examiner]
US 9011427B2 · Price et al. · 2015 [cited by applicant]
US 9283054B2 · Morgan et al. · 2016 [cited by applicant]
US 9345481B2 · Hall et al. · 2016 [cited by applicant]
US 11146690B2 · Minert · 2021 [cited by examiner]
US 20020000464A1 · Ramberg et al. · 2002 [cited by applicant]
US 20050210070A1 · Macneil · 2005 [cited by examiner]
US 20070140235A1 · Aysan et al. · 2007 [cited by applicant]
US 20140160259A1 · Blanquart et al. · 2014 [cited by applicant]
US 20140160260A1 · Blanquart et al. · 2014 [cited by applicant]
US 20140263552A1 · Hall et al. · 2014 [cited by applicant]
US 20140267655A1 · Richardson et al. · 2014 [cited by applicant]
US 20150119035A1 · Ganu · 2015 [cited by examiner]
US 20150128274A1 · Giokas · 2015 [cited by applicant]
US 20170296213A1 · Swensgard et al. · 2017 [cited by applicant]
US 20180344308A1 · Nawana et al. · 2018 [cited by applicant]
US 20180360452A1 · Shelton, IV et al. · 2018 [cited by applicant]
US 20190104919A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190191963A1 · Kuhn et al. · 2019 [cited by applicant]
US 20190200844A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190200906A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190200980A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190200988A1 · Shelton, IV · 2019 [cited by applicant]
US 20190201033A1 · Yates et al. · 2019 [cited by applicant]
US 20190201102A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201104A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201115A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201123A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201124A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201125A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201126A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201127A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201129A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201137A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190201140A1 · Yates et al. · 2019 [cited by applicant]
US 20190204201A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190205441A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190205566A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190205567A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206216A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206542A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206551A1 · Yates et al. · 2019 [cited by applicant]
US 20190206556A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206562A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206569A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190206576A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190207773A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190207857A1 · Shelton, IV et al. · 2019 [cited by applicant]
US 20190207911A1 · Wiener et al. · 2019 [cited by applicant]
US 20190333626A1 · Mansi et al. · 2019 [cited by applicant]
US 20200008044A1 · Poornachandran · 2020 [cited by examiner]
US 20210205031A1 · Shelton, IV · 2021 [cited by applicant]
US 20210212717A1 · Yates et al. · 2021 [cited by applicant]
US 20220020476A1 · Souissi · 2022 [cited by applicant]
US 20220046292A1 · Nair · 2022 [cited by examiner]
US 20220104713A1 · Shelton, IV · 2022 [cited by applicant]
US 20220104896A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220104910A1 · Shelton, IV · 2022 [cited by examiner]
US 20220108789A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233119A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233135A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233136A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233151A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233191A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233252A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220233254A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220238216A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220240869A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220241028A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220241474A1 · Shelton, IV et al. · 2022 [cited by applicant]
US 20220303945A1 · Tsuda · 2022 [cited by examiner]
US 20230021920A1 · Shelton, IV et al. · 2023 [cited by applicant]
US 20230023083A1 · Shelton, IV et al. · 2023 [cited by applicant]
US 20230023635A1 · Shelton, IV et al. · 2023 [cited by applicant]
US 20230026893A1 · Shelton, IV et al. · 2023 [cited by applicant]
US 20230027543A1 · Shelton, IV et al. · 2023 [cited by applicant]
US 20230035775A1 · Kohada · 2023 [cited by examiner]
EP 1010230B1 · 2003 [cited by applicant]
EP 3506287A1 · 2019 [cited by applicant]
WO 2019119130A1 · 2019 [cited by applicant]
Jagannath, et al., “An Analysis of Speech as a Modality for Activity Recognition during Complex Medical Teamwork”, Pervasive Computing Technologies for Healthcare, May 2018, pp. 1-10. [cited by applicant]