IP Library › Granted Patent US 12,452,655
Granted Patent B2
US 12,452,655 · App. 17/681,893 · Granted Oct 21, 2025

Medical image transfer system

Inventors: Daniel Maia (Madison, CT); Chris Aucone (Raritan, NJ); Jun Chen (Raritan, NJ); Yevgeniy Shkolnikov (Raritan, NJ)
Assignee: Biosense Webster (Israel) Ltd.
H04W12/033A61B90/37G16H70/20H04L9/0891H04L9/0894H04L9/3226H04L63/0471H04L63/0876H04L63/0884H04W12/06A61B34/20A61B2034/2074H04L2209/80H04L2209/88
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,452,655
App. No.
17/681,893
Granted
Oct 21, 2025
Kind
B2
Abstract

A transfer module, such as a single board computer having wireless communication capabilities, may be attached to an image guided surgery (“IGS”) navigation system. Images, video, and data stored on the IGS navigation system may be moved to and stored on the transfer module in an encrypted format. The transfer module may connect to a secure network or other secure wireless communication and transfer encrypted IGS medical procedure data to a physician device, a hospital system device, or other device. After validation, the physician device or other device may decrypt and display the data. The transfer module may be useful for IGS navigation systems having no preexisting wireless capabilities; and for those having wireless capabilities that are less secure than those provided by the modified IGS navigation system. The transfer module may also wirelessly transmit IGS medical procedure data to a cloud storage system for subsequent access by end users.

Claims (117)

1. A data transfer system comprising:

(a) a transfer module comprising a storage device, a wireless communication device, and a data interface, the data interface being configured to couple with and receive data from an image guided surgery navigation system, the wireless communication device being configured to connect to a wireless network via a Wi-Fi or cellular signal;

(b) a cloud storage system, the cloud storage system being in communication with the transfer module over the wireless network via a Wi-Fi or cellular signal; and

(c) a user device comprising a display and a user interface; the transfer module being configured to:

(i) provide a web server that the user device may communicate with over the wireless network, and

(ii) connect to the wireless network using a static address, the wireless network consisting of peers that are either transfer modules such as the transfer module or user devices such as the user device,

(iii) receive a set of medical procedure data from the image guided surgery navigation system,

(iv) encrypt the set of medical procedure data as a set of encrypted medical procedure data using a current key, store the encrypted medical procedure data on the storage device, and delete the set of medical procedure data, and

(v) provide the set of encrypted medical procedure data to the cloud storage system;

the cloud storage system being configured to:

(i) receive a medical procedure data request from the user device, and

(ii) provide the set of encrypted medical procedure data to the user device; and

the user device being configured to:

(i) receive the set of encrypted medical procedure data from the cloud storage system,

(ii) decrypt the set of encrypted medical procedure data,

(iii) display at least some of the decrypted medical procedure data to a user of the user device,

(iv) store a device key and a device key version,

(v) authenticate the user of the user device,

(vi) validate the user device based upon the device key and the current key,

(vii) when the user device is not validated, prompt the user for a new key and set it as the device key, then delete any information on the user device associated with a previous device key, and

(viii) when the user device is validated, decrypt the set of encrypted medical procedure data using the device key.

2. The data transfer system of claim 1 , the user device being further configured to:

(i) receive a set of authentication data from the user,

(ii) provide the authentication data to the cloud storage system, and

(iii) authenticate the user based upon an authentication response from the cloud storage system.

3. The data transfer system of claim 1 , the user device being further configured to:

(i) store a local validation database comprising a unique hardware identifier, a file description, an encrypted file description, and a key version, the file description and the encrypted file description both describing the same file, and the encrypted file description being created from the file description using the device key,

(ii) receive a module identifier and a module key version from the cloud storage system, and

(iii) validate the user device when the local validation database contains a record whose key version matches the module key version and whose module identifier matches the unique hardware identifier.

4. The data transfer system of claim 1 , the user device being further configured to:

(i) receive a module key version from the cloud storage system, and

(ii) validate the user device when the module key version matches the device key version.

5. The data transfer system of claim 1 , the user device being further configured to:

(i) store a local validation database comprising a file description and an encrypted file description, the file description and the encrypted file description both describing a file stored on the cloud storage system, and the encrypted file description being created from the file description using the device key,

(ii) request a file portion associated with the encrypted file description from the cloud storage system,

(iii) decrypt the file portion using the device key to create a decrypted file portion, and

(iv) validate the user device where the decrypted file portion matches the file description.

6. The data transfer system of claim 1 , the user device being further configured to:

(i) select a set of encrypted file names from the set of encrypted medical procedure data,

(ii) where the user is authenticated, and the user device is validated, decrypt the set of encrypted file names to create a set of file names and display the set of file names via the display, and

(iii) receive a selection from the user identifying one or more of the set of file names.

7. The data transfer system of claim 6 , the user device being further configured to:

(i) decrypt a set of files from the set of encrypted medical procedure data based upon the selection to create a set of decrypted files and display the set of decrypted files via the display, and

(ii) when the set of decrypted files are no longer being displayed via the display, delete the set of decrypted files.

8. The data transfer system of claim 6 , the user device being further configured to:

(i) decrypt a set of files from the set of encrypted medical procedure data based upon the selection to create a set of decrypted files and transmit the set of decrypted files to a secure destination associated with the user, and

(ii) after transmitting the set of decrypted files, delete the set of decrypted files.

9. The data transfer system of claim 1 , the wireless communication device being selected from the group consisting of a Wi-Fi transceiver, a Bluetooth transceiver, and a cellular data transceiver, the data interface being selected from the group consisting of a USB connection and an ethemet connection, and the transfer module being a single board computer.

10. The data transfer system of claim 1 , the transfer module being further configured to:

(i) receive a configuration data set, the configuration data set comprising a previous key, a new key, and a new key version,

(ii) confirm that the current key is different from the new key,

(iii) decrypt the set of encrypted medical procedure data using the previous key to create a second set of medical procedure data, and delete the set of encrypted medical procedure data,

(iv) encrypt the second set of medical procedure data using the new key to create a second set of encrypted medical procedure data, and delete the second set of medical procedure data,

(v) provide the second set of encrypted medical procedure data to the cloud storage system; and

(vi) update a local configuration to make the device key version equal to the new key version and make the current key equal to the new key.

11. The data transfer system of claim 1 , the cloud storage system being configured to:

(i) store a set of email templates, each email template being associated with a user, and each email template being configured to format the set of medical procedure data for transmission to that user,

(ii) receive a template request from the user device, the template request comprising an identifier for the user and a terms acceptance,

(iii) provide an email template of the set of email templates that is associated with the user to the user device, and

(iv) store the terms acceptance, the terms acceptance describing a legal agreement and an indicator of the user's acceptance of that legal agreement.

12. The data transfer system of claim 1 , transfer module being further configured to:

(i) restrict the function of the web server to prevent use of a set of commands, the set of commands comprising POST, PUT, and DELETE,

(ii) generate a self-signed secure sockets layer certificate, the self-signed secure sockets layer certificate having a duration of time, and

(iii) generate a new self-signed secure sockets layer certificate when the duration of time has passed.

13. A method for transferring data from an image guided surgery navigation system comprising the steps:

(a) installing a transfer module on the image guided surgery navigation system, the transfer module comprising a wireless communication device, and a data interface, the data interface being configured to couple with and receive data from an image guided surgery navigation system, the wireless communication device being configured to connect to a wireless network;

(b) receiving a set of medical procedure data from the image guided surgery navigation system at the transfer module;

(c) encrypting the set of medical procedure data as a set of encrypted medical procedure data using a current key, providing the set of encrypted medical procedure data to a cloud storage system, and deleting the set of medical procedure data;

(d) providing the set of encrypted medical procedure data from the cloud storage system to a user device, the user device comprising a display and a user interface;

(e) the user device decrypting the set of encrypted medical procedure data, and displaying at least some of the decrypted medical procedure data to a user of the user device;

(f) storing a device key and a device key version;

(g) authenticating the user of the user device;

(h) validating the user device based upon the device key and the current key;

(i) when the user device is not validated, prompting the user for a new key and setting it as the device key, then deleting any information on the user device associated with a previous device key; and

(j) when the user device is validated, receiving the set of encrypted medical procedure data and decrypting the set of encrypted medical procedure data.

14. The method of claim 13 , further comprising the steps:

(a) receiving a set of authentication data from the user;

(b) providing the authentication data to the cloud storage system;

(c) authenticating the user based upon an authentication response from the cloud storage system;

(d) storing a local validation database on the user device, the local validation database comprising a unique hardware identifier, a file description, an encrypted file description, and a key version, the file description and the encrypted file description both describing the same file, and the encrypted file description being created from the file description using the device key;

(e) receiving a module identifier and a module key version from the cloud storage system; and

(f) validating the user device when the local validation database contains a record whose key version matches the module key version and whose module identifier matches the unique hardware identifier.

15. The method of claim 13 , further comprising the steps:

(a) receiving a configuration data set at the transfer module, the configuration data set comprising a previous key, a new key, and a new key version;

(b) confirming that the current key is different from the new key;

(c) decrypting the set of encrypted medical procedure data using the previous key to create a second set of medical procedure data, and deleting the set of encrypted medical procedure data;

(d) encrypting the second set of medical procedure data using the new key to create a second set of encrypted medical procedure data, and deleting the second set of medical procedure data; and

(e) updating a local configuration of the transfer module to make the device key version equal to the new key version and make the current key equal to the new key.

16. The method of claim 13 , further comprising the steps:

(a) restricting the function of the cloud storage system to prevent use of a set of commands by the user of the user device, the set of commands comprising POST, PUT, and DELETE;

(b) generating a self-signed secure sockets layer certificate, the self-signed secure sockets layer certificate having a duration of time; and

(c) generating a new self-signed secure sockets layer certificate when the duration of time has passed.

17. A data transfer system comprising:

(a) a transfer module comprising a wireless communication device, and a data interface, the data interface being configured to couple with and receive data from an image guided surgery navigation system, the wireless communication device being configured to connect to a wireless network via a Wi-Fi or cellular signal;

(b) a cloud storage system, the cloud storage system being in communication with the transfer module over the wireless network via a Wi-Fi or cellular signal; and

(c) a user device comprising a display and a user interface; the transfer module being configured to:

(i) receive a set of medical procedure data from the image guided surgery navigation system, and

(ii) encrypt the set of medical procedure data as a set of encrypted medical procedure data using a current key, and provide the set of encrypted medical procedure data to the cloud storage system;

the cloud storage system being configured to:

(i) receive a medical procedure data request from the user device,

(ii) provide the set of encrypted medical procedure data to the user device,

(iii) store a set of email templates, each email template being associated with a user, and each email template being configured to format the set of medical procedure data for transmission to that user,

(iv) receive a template request from the user device, the template request comprising an identifier for the user and a terms acceptance,

(v) provide an email template of the set of email templates that is associated with the user to the user device, and

(vi) store the terms acceptance, the terms acceptance describing a legal agreement and an indicator of the user's acceptance of that legal agreement; and

the user device being configured to:

(i) receive the set of encrypted medical procedure data from the cloud storage system,

(ii) decrypt the set of encrypted medical procedure data, and

(iii) display at least some of the decrypted medical procedure data to a user of the user device.

18. The data transfer system of claim 17 , the transfer module being further configured to:

(i) receive a configuration data set, the configuration data set comprising a previous key, a new key, and a new key version,

(ii) in response to receiving the configuration data set:

(a) confirm that the current key is different from the new key,

(b) decrypt the set of encrypted medical procedure data using the previous key to create a second set of medical procedure data, and delete the set of encrypted medical procedure data,

(c) create a second set of encrypted medical procedure data by encrypting the second set of medical procedure data using the new key,

(d) provide the second set of encrypted medical procedure data to the cloud storage system; and

(e) update a local configuration to make the device key version equal to the new key version and make the current key equal to the new key.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2024
From: MAIA, DANIEL; AUCONE, CHRIS; CHEN, JUN; SHKOLNIKOV, YEVGENIY
To: BIOSENSE WEBSTER (ISRAEL) LTD.
Reel/Frame 068602/0059 →
Continuity (3)
Division 16368168 · Mar 28, 2019
Provisional Application 62668473 · May 8, 2018
Related Publication 20220248219A1 · Aug 4, 2022
References Cited (68)
US 7720521B2 · Chang et al. · 2010 [cited by applicant]
US 8108432B2 · Westin et al. · 2012 [cited by applicant]
US 8320711B2 · Altmann et al. · 2012 [cited by applicant]
US 8702626B1 · Kim et al. · 2014 [cited by applicant]
US 8874453B2 · Menschik et al. · 2014 [cited by applicant]
US 10146961B1 · Baruch et al. · 2018 [cited by applicant]
US 10362965B2 · Kesten et al. · 2019 [cited by applicant]
US 11297495B2 · Maia et al. · 2022 [cited by applicant]
US 20070232885A1 · Cook et al. · 2007 [cited by applicant]
US 20090262109A1 · Markowitz et al. · 2009 [cited by applicant]
US 20090282371A1 · Curl · 2009 [cited by applicant]
US 20090326985A1 · Martin et al. · 2009 [cited by applicant]
US 20100167334A1 · Williamson, IV · 2010 [cited by applicant]
US 20110060214A1 · Makower · 2011 [cited by applicant]
US 20110123027A1 · Gotthardt · 2011 [cited by applicant]
US 20110307947A1 · Kariv et al. · 2011 [cited by applicant]
US 20120059911A1 · Randhawa · 2012 [cited by examiner]
US 20120140923A1 · Lee et al. · 2012 [cited by applicant]
US 20130006867A1 · Dove et al. · 2013 [cited by applicant]
US 20130177157A1 · Li · 2013 [cited by examiner]
US 20130191647A1 · Ferrara, Jr. et al. · 2013 [cited by applicant]
US 20140156988A1 · Takahashi et al. · 2014 [cited by applicant]
US 20140188513A1 · Balignasay et al. · 2014 [cited by applicant]
US 20140276056A1 · Ohta et al. · 2014 [cited by applicant]
US 20140364725A1 · Makower · 2014 [cited by applicant]
US 20150046192A1 · Raduchel · 2015 [cited by examiner]
US 20150248526A1 · Choi · 2015 [cited by applicant]
US 20150278444A1 · Westin et al. · 2015 [cited by applicant]
US 20150310188A1 · Ford et al. · 2015 [cited by applicant]
US 20150347682A1 · Chen et al. · 2015 [cited by applicant]
US 20160063187A1 · Vettrival et al. · 2016 [cited by applicant]
US 20160105402A1 · Soon-Shiong · 2016 [cited by examiner]
US 20160234176A1 · Chu et al. · 2016 [cited by applicant]
US 20160310077A1 · Hunter et al. · 2016 [cited by applicant]
US 20170011174A1 · Higgs · 2017 [cited by applicant]
US 20170230871A1 · Rangaswamy · 2017 [cited by examiner]
US 20170257214A1 · Stufflebeam · 2017 [cited by examiner]
US 20170262585A1 · Grow et al. · 2017 [cited by applicant]
US 20170262603A1 · Grow et al. · 2017 [cited by applicant]
US 20170277831A1 · Ruff · 2017 [cited by examiner]
US 20170288857A1 · Zuhorski · 2017 [cited by examiner]
US 20170293718A1 · Perez et al. · 2017 [cited by applicant]
US 20180096179A1 · Dang · 2018 [cited by examiner]
US 20180131573A1 · Matsuda · 2018 [cited by applicant]
US 20180263495A1 · Cronin · 2018 [cited by examiner]
US 20180268164A1 · Minami · 2018 [cited by applicant]
US 20190198138A1 · Baldwin et al. · 2019 [cited by applicant]
US 20190229907A1 · Nicolson · 2019 [cited by examiner]
US 20190356479A1 · Grimme · 2019 [cited by applicant]
US 20190386814A1 · Ahmed · 2019 [cited by applicant]
US 20200286600A1 · De Brouwer · 2020 [cited by examiner]
US 20220374414A1 · Shelton, IV · 2022 [cited by examiner]
US 20240090742A1 · Maltese · 2024 [cited by examiner]
CN 1938708A · 2007 [cited by applicant]
CN 101601041A · 2009 [cited by applicant]
JP 2008126063A · 2008 [cited by applicant]
JP 2009529951A · 2009 [cited by applicant]
JP 2015191601A · 2015 [cited by applicant]
JP 2017216519A · 2017 [cited by applicant]
WO 2009137688A2 · 2009 [cited by applicant]
WO 2014130592A1 · 2014 [cited by applicant]
Chinese Office Action, The First Office Action and First Search dated Jan. 19, 2024 for Application No. CN 01980046144.1, 8 pgs. [cited by applicant]
European Communication dated Aug. 18, 2021 for Application No. EP 19730212.8, 8 pgs. [cited by applicant]
International Search Report and Written Opinion dated Aug. 16, 2019 for Application No. PCT/IB2019/053530, 12 pgs. [cited by applicant]
International Preliminary Report on Patentability dated Nov. 10, 2020 for Application No. PCT/IB2019/053530, 9 pgs. [cited by applicant]
Japanese Office Action, Notice of Reasons for Refusal, dated Jun. 13, 2023 for Application No. JP 2020-562599, 7 pgs. [cited by applicant]
Japanese Office Action, Decision of Refusal, dated Dec. 12, 2023 for Application No. JP 2020-562599, 4 pgs. [cited by applicant]
US Provisional U.S. Appl. No. 62/668,473, entitled “Medical Image Transfer System,” filed May 8, 2018. [cited by applicant]