IP Library Granted Patent US 12,283,372
Granted Patent B2
US 12,283,372 · App. 18/371,210 · Granted Apr 22, 2025

System for communication of data

Inventor: David Becker (Grand Rapids, MI)
Assignee: Stryker Corporation
G16H40/40G16H40/60H04L65/1036H04L67/303H04L69/08
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,283,372
App. No.
18/371,210
Granted
Apr 22, 2025
Kind
B2
Abstract

A system for communication of data is provided. The system includes a medical device. A data consuming device is positioned at a first network layer. An edge communication device is positioned at a second network layer. The edge communication device is in communication with the medical device to receive data from the medical device. The edge communication device has a profile. The profile defines a data format for the data and a communication path for transmitting the data between the network layers. A gateway device is configured to route the data from the edge communication device to the data consuming device via the communication path. The edge communication device is also configured to modify the data format to correspond to the data consuming device and to format the data according to the data format.

Claims (43)

1. A system for managing data communication in a surgical environment, the system comprising:

an edge communication device communicatively coupled to a surgical device, the edge communication device configured to receive data from the surgical device during a surgical procedure, and the edge communication device comprising a memory device, a controller, and a transceiver; and

a profile distribution server configured to communicate with the transceiver of the edge communication device over one or more networks, wherein responsive to the edge communication device being connected to the one or more networks, the profile distribution server is configured to transmit profile data to the edge communication device that configures operation of the edge communication device, the profile data identifying data types to be logged by the edge communication device, a first condition related to the surgical device data and associated with a first server, and a second condition related to the surgical device data and associated with a second server,

wherein the edge communication device is configured to store the profile data in the memory device, and based on the stored profile data, format the received surgical device data into log files of the identified data types, transmit at least a portion of the log files to the first server over the one or more networks using the transceiver only when the first condition is satisfied, and transmit at least a portion of the log files to the second server over the one or more networks using the transceiver only when the second condition is satisfied.

2. The system of claim 1 , wherein the profile distribution server is configured to:

discover the edge communication device on the one or more networks;

determine a geographic region associated with the edge communication device; and

identify the profile data for transmission to the edge communication device based on the geographic region.

3. The system of claim 2 , wherein the first and second servers are each disposed in the geographic region, and the profile data is configured to prohibit the edge communication device from transmitting any of the log files to devices outside the geographic region.

4. The system of claim 1 , wherein the identified data types include a first data type and a second data type, the profile data includes a first data collection parameter for the first server that identifies the first data type and a second data collection parameter for the second server that identifies the second data type, and based on the stored profile data, the edge communication device is configured to transmit a first of the log files to the first server using the transceiver only when the first condition is satisfied, the first log file being of the first data type, and transmit a second of the log files to the second server using the transceiver only when the second condition is satisfied, the second log file being of the second data type.

5. The system of claim 4 , wherein the first server is a cloud server, the second server is a hospital server, the first data type is sensed patient anatomy data, and the second data type is device usage data.

6. The system of claim 4 , wherein the first data type is device usage data, and the second data type is patient image data.

7. The system of claim 1 , wherein the identified data types include a first data type and a second data type, the profile data identifies a first security policy for the first data type and a second security policy for the second data type, the first security policy indicating a first access level associated with the first server and the second security policy indicating a second access level associated with the second server and higher than the first access level, and based on the first and second security policies of the stored profile data, the edge communication device is configured to permit communication of any of the log files of the first data type to the first server and prevent communication of any of the log files of the second data type to the first server.

8. The system of claim 7 , wherein the first data type is patient anatomy data and the second data type is patient information.

9. The system of claim 1 , wherein the edge communication device is defined as a first edge communication device, the system comprising:

a second edge communication device communicatively coupled to a second surgical device and configured to receive second data from the second surgical device during a surgical procedure, the second edge communication device comprising a second memory device storing the profile data, a second transceiver, and a second controller configured, based on the profile data stored in the second memory device, to format the received second surgical device data into second log files of the identified data types, transmit at least a portion of the second log files to the first server over the one or more networks using the transceiver only when the first condition is satisfied relative to the second surgical device data, and transmit at least a portion of the second log files to the second server over the one or more networks using the transceiver only when the second condition is satisfied relative to the second surgical device data,

wherein the profile distribution server is configured to, responsive to the first edge communication device being connected to the one or more networks, communicate with the second transceiver of the second edge communication device over the one or more networks to retrieve the profile data and transmit the retrieved profile data to the transceiver of the first edge communication device over the one or more networks.

10. The system of claim 9 , wherein the identified data types include a first data type and a second data type, and the profile distribution server is configured to implement a network-wide security update by communicating updated security policy data over the one or more networks to each of the first and second edge communication devices, the updated security policy data indicating an updated encryption algorithm specific to the first data type, and responsive to receiving the updated security policy data, the first and second edge communication devices are each configured to modify the profile data stored on the edge communication device with the updated security policy data.

11. The system of claim 9 , wherein the one or more networks comprise a plurality of networks, and the profile data retrieved from second edge communication edge device and transmitted to the first edge communication device includes communication path data identifying a first communication path through the plurality of networks for transmitting log files to the first server and a second communication path, different from the first communication path, through the plurality of networks for transmitting log files to the second server, the first and second communication paths including respective gateway devices each disposed between a different two of the networks.

12. The system of claim 11 , comprising a third edge communication device integral with the gateway device of the first communication path, the third edge communication device including a third transceiver, a third controller, and a third memory device storing profile data configuring operation of the third edge communication device, the profile data stored in the third memory device being remotely configurable by the profile distribution server over the one or more networks,

wherein responsive to the first edge communication device being connected to the one or more networks, the profile distribution server is configured to transmit a profile data update to the third edge communication device that configures the third controller to concatenate the at least a portion of the log files transmitted from the first edge communication device to the first server with the at least a portion of the second log files transmitted from the second edge communication device to the first server to produce concatenated log file data, and transmit the concatenated log file data to the first server over the one or more networks using the third transceiver.

13. An edge communication device for managing data communication in a surgical environment, the edge communication device being coupled to a surgical device configured to generate data during a surgical procedure, the edge communication device comprising:

a transceiver;

a memory device; and

a controller coupled to the transceiver and memory device and configured to:

responsive to the edge communication device being connected to one or more networks, receive over the one or more networks profile data that configures operation of the edge communication device from a profile distribution server, the profile data identifying data types to be logged by the edge communication device, a first condition related to the surgical device data and associated with a first server, and a second condition related to the surgical device data and associated with a second server;

store the received profile data in the memory device;

receive the data from the surgical device during the surgical procedure; and

based on the stored profile data, format the received surgical device data into log files of the identified data types, transmit at least a portion of the log files to the first server over the one or more networks using the transceiver only when the first condition is satisfied, and transmit at least a portion of the log files to the second server over the one or more networks using the transceiver only when the second condition is satisfied.

14. The edge communication device of claim 13 , wherein the profile data indicates a geographic region in which the edge communication device, the first server, and the second server are located, and prohibits the edge communication device from transmitting any of the log files to devices outside the geographic region.

15. The edge communication device of claim 13 , wherein the identified data types include a first data type and a second data type, the profile data includes a first data collection parameter for the first server that identifies the first data type and a second data collection parameter for the second server that identifies the second data type, and based on the stored profile data, the edge communication device is configured to transmit a first of the log files to the first server using the transceiver only when the first condition is satisfied, the first log file being of the first data type, and transmit a second of the log files to the second server using the transceiver only when the second condition is satisfied, the second log file being of the second data type.

16. The edge communication device of claim 15 , wherein the first server is a cloud server, the second server is a hospital server, the first data type is sensed patient anatomy data, and the second data type is device usage data.

17. The edge communication device of claim 15 , wherein the first data type is device usage data, and the second data type is patient image data.

18. The edge communication device of claim 15 , wherein the identified data types include a first data type and a second data type, the profile data identifies a first security policy for the first data type and a second security policy for the second data type, the first security policy indicating a first access level associated with the first server and the second security policy indicating a second access level associated with the second server and higher than the first access level, and based on the first and second security policies of the stored profile data, the edge communication device is configured to permit communication of any of the log files of the first data type to the first server and prevent communication of any of the log files of the second data type to the first server.

19. The edge communication device of claim 18 , wherein the first data type is patient anatomy data and the second data type is patient information.

20. A system for managing edge communication devices in a surgical environment, the system comprising:

at least one computer processor; and

a memory storing computer instructions that upon execution by the at least one computer processor cause the at least one computer processor to:

discover an edge communication device added to one or more networks, the edge communication device being communicatively coupled to a surgical device and configured to receive data from the surgical device during a surgical procedure; and

responsive to discovering the edge communication device:

determine a geographic region associated with the edge communication device;

identify profile data for configuring operation of the edge communication device based on the geographic region, the profile data identifying data types to be logged by the edge communication device, a first server and a second server to which to send log files of the identified data types generated by the edge communication device from the surgical device data, a first required condition related to the surgical device data for communicating any of the log files to the first server, and a second required condition related to the surgical device data for communicating any of the log files to the second server; and

transmit the profile data to the edge communication device over the one or more networks to configure operation of the edge communication device in accordance with the profile data.

Assignments (2)
CHANGE OF ADDRESS Recorded Dec 18, 2024
From: STRYKER CORPORATION
To: STRYKER CORPORATION
Reel/Frame 069737/0184 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2023
From: BECKER, DAVID
To: STRYKER CORPORATION
Reel/Frame 065224/0473 →
Continuity (4)
Continuation 16729609 · Dec 30, 2019
Continuation PCTUS2018040595 · Jul 2, 2018
Provisional Application 62528192 · Jul 3, 2017
Related Publication 20240013903A1 · Jan 11, 2024
References Cited (43)
US 7690059B2 · Lemire et al. · 2010 [cited by applicant]
US 7774211B1 · Mullen et al. · 2010 [cited by applicant]
US 8102254B2 · Becker et al. · 2012 [cited by applicant]
US 8126729B2 · Dicks · 2012 [cited by examiner]
US 9833194B2 · Hayes et al. · 2017 [cited by applicant]
US 9902762B2 · Camphausen et al. · 2018 [cited by applicant]
US 10200241B2 · Shen et al. · 2019 [cited by applicant]
US 10319056B1 · Perez et al. · 2019 [cited by applicant]
US 10409245B2 · Cella · 2019 [cited by examiner]
US 10693966B2 · Becker et al. · 2020 [cited by applicant]
US 20020193969A1 · Frantz et al. · 2002 [cited by applicant]
US 20050187529A1 · Reasoner et al. · 2005 [cited by applicant]
US 20070163045A1 · Becker et al. · 2007 [cited by applicant]
US 20080151932A1 · Wormer et al. · 2008 [cited by applicant]
US 20090063187A1 · Johnson et al. · 2009 [cited by applicant]
US 20100250697A1 · Hansen et al. · 2010 [cited by applicant]
US 20110093285A1 · Dicks et al. · 2011 [cited by applicant]
US 20130032479A1 · Hanko et al. · 2013 [cited by applicant]
US 20130190674A1 · Case et al. · 2013 [cited by applicant]
US 20140077956A1 · Sampath et al. · 2014 [cited by applicant]
US 20140152466A1 · Wiesner et al. · 2014 [cited by applicant]
US 20140343639A1 · Hopper et al. · 2014 [cited by applicant]
US 20150206408A1 · LaLonde · 2015 [cited by examiner]
US 20160127514A1 · Maksumov et al. · 2016 [cited by applicant]
US 20170147761A1 · Moskal et al. · 2017 [cited by applicant]
US 20190244707A1 · Becker et al. · 2019 [cited by applicant]
US 20200135333A1 · Becker · 2020 [cited by applicant]
WO 2012033947A2 · 2012 [cited by applicant]
WO WO2012033947 · 2012 [cited by applicant]
WO 2013109517A1 · 2013 [cited by applicant]
WO WO2013109517 · 2013 [cited by applicant]
WO 2018013666A1 · 2018 [cited by applicant]
WO WO2018013666 · 2018 [cited by applicant]
WO 2019010127A1 · 2019 [cited by applicant]
WO WO2019010127 · 2019 [cited by applicant]
Jennifer Bresnick, How Fog Computing May Power the Healthcare Internet of Things, Health IT Analytics (Aug. 23, 2016) (Year: 2016). [cited by examiner]
Kraemer et al., Fog Computing in Healthcare—A Review and Discussion, 5 IEEE Access 9206-9222 (May 15, 2017) (Year: 2017). [cited by examiner]
Tomovic et al., Software-Defined Fog Network Architecture for IoT, Wireless Pers Commun (Oct. 24, 2016) (Year: 2016). [cited by examiner]
Gia et la., Fog Computing in Healthcare Internet of Things: A Case Study on ECG Feature Extraction, 2015 IEEE International Conference on Computer and Information Technology; Ubiquitous Computing and Communications; Dep… [cited by examiner]
Bresnick, Jennifer, “How Fog Computing May Power the Healthcare Internate of Things”, Health IT Analytics, Aug. 23, 2016, 4 pages. [cited by applicant]
Gia, Tuan Nyguyen et al., “Fog Computing in Healthcare Internet of Things: A Case Study on ECG Feature Extraction”, IEEE International Conference on Computer and Information Technology, 2015, pp. 356-336. [cited by applicant]
International Search Report for Application No. PCT/US2017/041681 dated Oct. 18, 2017, 4 pages. [cited by applicant]
International Search Report for Application No. PCT/US2018/040595 dated Oct. 11, 2018, 4 pages. [cited by applicant]