Robotic surgery using multi-user authentication without credentials

US12119110B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12119110-B2
Application numberUS-201916429346-A
CountryUS
Kind codeB2
Filing dateJun 3, 2019
Priority dateJun 6, 2018
Publication dateOct 15, 2024
Grant dateOct 15, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

One example method for robotic surgery using multi-user authentication without credentials includes receiving, by a robotic surgical device, a case code associated with a medical procedure; validating the case code; determining one or more users associated with the case code; and providing access to the one or more users to the robotic surgical device to enable a robotic surgical procedure.

First claim

Opening claim text (preview).

That which is claimed is: 1. A method comprising: receiving, by a controller of a robotic surgical device from a case code interface device, a case code identifying a medical procedure, wherein the robotic surgical device comprises one or more articulating arms and is configured to assist in surgical procedures, wherein the robotic surgical device is communicatively coupled to the controller, the controller comprising one or more user interface devices to effect movement of the one or more articulating arms; validating, by the controller, the case code based on a format of the case code, a configuration of the medical procedure specified by the case code, and a characteristic of the robotic surgical device, the case code identifying a surgical team and the medical procedure to be performed, wherein the case code comprises a backup code; and responsive to validating the case code: receiving an identification of a user of the robotic surgical device; determining, by the controller, the user is authorized to perform the medical procedure associated with the case code based on the surgical team; generating an alert based on the backup code; denying access to one or more patient data records based on the backup code; enabling, by the controller, the one or more user interface devices; providing limited access, by the controller, to the user to control the robotic surgical device to enable a robotic surgical procedure; and receiving, by the controller during the robotic surgical procedure, user inputs from the user interface devices and controlling the movement of the one or more articulating arms based on the user inputs. 2. The method of claim 1 , wherein the case code is a self-authenticating case code or a cryptographically signed code. 3. The method of claim 1 , further comprising: obtaining, using the case code, one or more patient data records associated with the robotic surgical procedure, at least one of the patient data records comprising personalized health information (“PHI”), and in response to validating the case code, providing access to the one or more patient data records to the one or more users. 4. The method of claim 1 , further comprising, responsive to validating the case code: obtaining, using the case code, identification information for each user of the one or more users; and logging each user of the one or more users into the robotic surgical device. 5. The method of claim 4 , receiving a user input indicating a first user of the one or more users is using the robotic surgical device, and changing an identity of an operating user to the first user. 6. The method of claim 5 , further comprising recording surgical data during performance of the robotic surgical procedure and associating the first user with the surgical data. 7. The method of claim 6 , further comprising: receiving a second user input indicating a second user of the one or more users is using the robotic surgical device, and changing the identity of the operating user to the second user; recording additional surgical data during performance of the robotic surgical procedure and associating the second user with the additional surgical data. 8. The method of claim 1 , further comprising recording surgical data during performance of the robotic surgical procedure. 9. The method of claim 8 , further comprising: responsive to completing the robotic surgical procedure, completing recording the surgical data; and transmitting the surgical data to a remote server. 10. The method of claim 9 , wherein transmitting the surgical data to a remote server comprises associating identities of each user of the one or more users and one or more data records associated with the robotic surgical procedure with the surgical data, and transmitting the identities of each user of the one or more users and one or more data records to the remote server. 11. The method of claim 8 , further comprising streaming, during the robotic surgical procedure, the surgical data to a remote server. 12. The method of claim 1 , wherein determining the one or more users associated with the case code comprises receiving one or more user inputs identifying at least one user of the one or more users. 13. The method of claim 1 , further comprising: recording surgical data during performance of the robotic surgical procedure; receiving a second case code, the second case code associated with a scheduled robotic surgical procedure; determining a second set of one or more users associated with the second case code; associating the surgical data with the scheduled robotic surgical procedure and the second set of one or more users; and transmitting the surgical data and the associated second set of one or more users to a remote server. 14. The method of claim 1 , wherein receiving the case code comprises at least one of (i) scanning a bar code, (ii) obtaining the case code from an RFID tag; (iii) obtaining the case code using a Bluetooth® communication technique, or (iv) receiving typed user input from a user input device. 15. The method of claim 1 , wherein the robotic surgical procedure is a simulated medical procedure or a training exercise. 16. A system comprising: a robotic surgical device comprising one or more articulating arms and configured to assist in surgical procedures; a case code interface device; a controller comprising one or more user interface devices to effect movement of the one or more articulating arms, the controller communicatively coupled to the robotic surgical device, the controller comprising a communications interface; a non-transitory computer-readable medium; and one or more processors configured to execute processor executable instructions stored in the non-transitory computer-readable medium to: receive, from the case code interface device, a case code identifying a medical procedure; validate the case code based on a format of the case code, a configuration of the medical procedure specified by the case code, and a characteristic of the robotic surgical device, the case code identifying a surgical team and the medical procedure to be performed, wherein the case code comprises a backup code; and responsive to validating the case code: receive an identification of a user of the robotic surgical device; determine the user is authorized to perform the medical procedure associated with the case code based on the surgical team; generate an alert based on the backup code; deny access to one or more patient data records based on the backup code; provide limited access, by the controller, to the user to control the robotic surgical device to enable a robotic surgical procedure; and receive, by the controller during the robotic surgical procedure, user inputs from the user interface devices and controlling the movement of the one or more articulating arms based on the user inputs. 17. The system of claim 16 , further comprising a case code interface configured to (i) scan a bar code to obtain the case code, (ii) obtain the case code from an RFID tag; (iii) obtain the case code using a Bluetooth® communication technique, or (iv) receive typed user input from a user input device. 18. The system of claim 16 , wherein the medical procedure is a simulated medical procedure or a training exercise. 19. The system of claim 16 , wherein the processor is configured to execute further processor-executable instructions stored in the non-transitory computer- readable medium to: obtain, using the case code, one or more patient data records as

Assignees

Inventors

Classifications

  • G16H10/60Primary

    for patient-specific data, e.g. for electronic patient records · CPC title

  • using barcodes · CPC title

  • Surgical robots · CPC title

  • Use of tools · CPC title

  • using electromagnetic means, e.g. transponders · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12119110B2 cover?
One example method for robotic surgery using multi-user authentication without credentials includes receiving, by a robotic surgical device, a case code associated with a medical procedure; validating the case code; determining one or more users associated with the case code; and providing access to the one or more users to the robotic surgical device to enable a robotic surgical procedure.
Who is the assignee on this patent?
Verily Life Sciences Llc
What technology area does this patent fall under?
Primary CPC classification G16H10/60. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Oct 15 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).