US 12,133,709 B2
Communication hub and storage device for storing parameters and status of a surgical device to be shared with cloud based analytics systems
Frederick E. Shelton, IV, Hillsboro, OH (US); Jason L. Harris, Lebanon, OH (US); and David C. Yates, Morrow, OH (US)
Assigned to Cilag GmbH International, Zug (CH)
Filed by Cilag GmbH International, Zug (CH)
Filed on May 4, 2023, as Appl. No. 18/143,365.
Application 18/143,365 is a continuation of application No. 17/217,175, filed on Mar. 30, 2021, granted, now 11,737,668.
Application 17/217,175 is a continuation of application No. 15/940,640, filed on Mar. 29, 2018, granted, now 11,202,570, issued on Dec. 21, 2021.
Claims priority of provisional application 62/649,294, filed on Mar. 28, 2018.
Claims priority of provisional application 62/611,339, filed on Dec. 28, 2017.
Claims priority of provisional application 62/611,341, filed on Dec. 28, 2017.
Claims priority of provisional application 62/611,340, filed on Dec. 28, 2017.
Prior Publication US 2023/0389796 A1, Dec. 7, 2023
Int. Cl. A61B 5/00 (2006.01); A61B 1/00 (2006.01); A61B 17/00 (2006.01); A61B 18/00 (2006.01); A61B 18/12 (2006.01); A61B 34/30 (2016.01); A61B 90/00 (2016.01); G06F 13/00 (2006.01); G16H 10/60 (2018.01); G16H 30/00 (2018.01); G16H 80/00 (2018.01); H04L 43/0811 (2022.01); H04L 67/00 (2022.01); H04L 67/10 (2022.01); H04L 67/12 (2022.01); H04L 67/2871 (2022.01); H04L 67/5683 (2022.01)
CPC A61B 5/0022 (2013.01) [A61B 1/00011 (2013.01); A61B 1/00016 (2013.01); A61B 18/1206 (2013.01); A61B 34/30 (2016.02); A61B 90/37 (2016.02); G06F 13/00 (2013.01); G16H 10/60 (2018.01); G16H 30/00 (2018.01); G16H 80/00 (2018.01); H04L 43/0811 (2013.01); H04L 67/12 (2013.01); H04L 67/2871 (2013.01); H04L 67/34 (2013.01); H04L 67/5683 (2022.05); A61B 2017/00221 (2013.01); A61B 2018/00994 (2013.01); A61B 2018/1253 (2013.01); A61B 2018/126 (2013.01); A61B 2218/006 (2013.01); A61B 2218/008 (2013.01); H04L 67/10 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A modular surgical system comprising:
a hospital data barrier;
an Electronic Medical Records (EMR) database within the hospital data barrier to store patient data using a key that uniquely identifies a patient EMR;
a first hub within the hospital data barrier, wherein the first hub is to:
store redacted data with a unique anonymous procedure number;
interrogate the EMR database to retrieve the patient data and the key; and
combine, by the key and the unique anonymous procedure number, the redacted data with the patient data to form an un-redacted data set; and
a second hub within the hospital data barrier in communication with the first hub, wherein the first hub is to transmit the un-redacted data set to the second hub; and
wherein the first and second hub are to communicate with a cloud-based analytics network located outside the hospital data barrier and the first hub is to transmit a redacted dataset to the cloud-based analytics network.