# US 12,119,110 B2 · Robotic surgery using multi-user authentication without credentials

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,119,110 B2
- Document ID: US12119110B2
- Status: Granted
- Kind: B2
- Application number: 16/429,346
- Filed: 2019-06-03
- Published: 2019-12-12
- Granted: 2024-10-15
- Earliest claimed: 2018-06-06
- Assignees: Verily Life Sciences LLC
- Applicants: Verily Life Sciences LLC
- Inventors: Joëlle Barral; Martin Habbecke; James Shuma; Robin Thellend; Brian Carnes; Neil Inala; Timothy Chung; Michael Newton; Michal Levin
- Web page: https://patentgrep.com/patent/US12119110B2

## CPC

- G16H 40/63: for local operation
- A61B 34/30: Surgical robots
- A61B 34/37: Leader-follower robots (A61B34/35 takes precedence)
- A61B 90/96: using barcodes
- A61B 90/98: using electromagnetic means, e.g. transponders
- G06F 21/31: User authentication
- G06F 21/44: Program or device authentication
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G09B 19/24: Use of tools
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 10/65: stored on portable record carriers, e.g. on smartcards, RFID tags or CD
- G16H 20/40: relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- A61B 2034/256: {having a database of accessory information, e.g. including context sensitive help or scientific articles}
- A61B 2034/258: {providing specific settings for specific users}
- A61B 2090/0808: {for indicating correct assembly of components, e.g. of the surgical apparatus}
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G09B: EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS (devices for psychotechnics or for testing reaction times A61B5/16; games, sports, amusements A63; projectors, projector screens G03B)

## Abstract

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.

## Claims

### Claim 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.

### Claim 2 (depends on 1)

The method of claim 1, wherein the case code is a self-authenticating case code or a cryptographically signed code.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 4)

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.

### Claim 6 (depends on 5)

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.

### Claim 7 (depends on 6)

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.

### Claim 8 (depends on 1)

The method of claim 1, further comprising recording surgical data during performance of the robotic surgical procedure.

### Claim 9 (depends on 8)

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.

### Claim 10 (depends on 9)

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.

### Claim 11 (depends on 8)

The method of claim 8, further comprising streaming, during the robotic surgical procedure, the surgical data to a remote server.

### Claim 12 (depends on 1)

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.

### Claim 13 (depends on 1)

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.

### Claim 14 (depends on 1)

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.

### Claim 15 (depends on 1)

The method of claim 1, wherein the robotic surgical procedure is a simulated medical procedure or a training exercise.

### Claim 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.

### Claim 17 (depends on 16)

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.

### Claim 18 (depends on 16)

The system of claim 16, wherein the medical procedure is a simulated medical procedure or a training exercise.

### Claim 19 (depends on 16)

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 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, provide access to the one or more patient data records to the one or more users.

### Claim 20 (depends on 16)

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, identification information for each user of the one or more users; and
log each user of the one or more users into the robotic surgical device.

### Claim 21 (depends on 16)

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:
record surgical data during performance of the robotic surgical procedure;
responsive to completing the robotic surgical procedure, complete recording the surgical data; and
transmit the surgical data to a remote server.

### Claim 22

A non-transitory computer-readable medium comprising processor-executable instructions configured to cause one or more processors to:
receive, 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;
validate, 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:
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.