# US 2026/0076718 A1 · Bone fixation device with secured remote operation

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

- Number: US 2026/0076718 A1
- Document ID: US20260076718A1
- Status: Published application
- Kind: A1
- Application number: 18/885,278
- Filed: 2024-09-13
- Published: 2026-03-19
- Earliest claimed: 2024-09-13
- Assignees: Synthes GmbH
- Applicants: Synthes GmbH
- Inventors: Oren Cohen; Shahar Harari
- Web page: https://patentgrep.com/patent/US20260076718A1

## CPC

- A61B 17/66: {Alignment}, compression or distraction mechanisms
- A61B 17/62: Ring frames, i.e. devices extending around the bones to be positioned ({A61B17/6433} , A61B17/66 take precedence)
- A61B 34/10: Computer-aided planning, simulation or modelling of surgical operations
- G16H 20/40: relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
- G16H 40/67: for remote operation
- A61B 2017/00212: {using remote controls}
- A61B 2017/681: {Alignment, compression, or distraction mechanisms}
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

Reconfiguration of a bone fixation device of a patient may include generating, on a main server, a new actuation plan for the bone fixation device, the new actuation plan including operational parameters of the bone fixation device, notifying a patient device that the new actuation plan is available on the main server, requesting from a patient on the patient device an approval of the new actuation plan. Upon receiving the patient's approval, requesting by the patient device, from the main server, the new actuation plan from the main server, and reconfiguring the bone fixation device with the new actuation plan.

## Claims

### Claim 1

A method for remote reconfiguration of a bone fixation device of a patient, the bone fixation device including a frame connectible to bone tissue, a plurality of adjustable struts connected to the frame, and a control system including: a plurality of actuators associated with the plurality of adjustable struts, each actuator configured for adjusting a length of at least one adjustable strut, the method comprising:
(a) generating, on a main server, a new actuation plan for the bone fixation device, the new actuation plan including operational parameters of the bone fixation device,
(b) notifying a patient device that the new actuation plan is available on the main server,
(c) requesting from a patient on the patient device an approval of the new actuation plan,
(d) upon receiving the patient's approval, requesting by the patient device the new actuation plan from the main server, and
(e) reconfiguring the bone fixation device with the new actuation plan.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the bone fixation device is configured with a current actuation plan, and generating the new actuation plan is based on the current actuation plan.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising, prior to generating the new actuation plan, receiving on the main server a current status of the bone fixation device from the patient device, the current status including data indicative of the operation and status of a current plan on the bone fixation device.

### Claim 4 (depends on 3)

The method according to claim 3, wherein generating the new actuation plan is based on the current status.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising, subsequent to generating the new actuation plan, initiating, by the main server, notifying the patient device.

### Claim 6 (depends on 1)

The method according to claim 1, further including a notification server, and notifying the patient device is via the notification server.

### Claim 7 (depends on 6)

The method according to claim 6, further including a first secure communication channel between the notification server and the patient device, and the notifying the patient device is via the first secure communication channel.

### Claim 8 (depends on 6)

The method according to claim 6, further including a second secure communication channel between the main server and the patient device, the requesting the new actuation plan is via the second secure communication channel, and the new actuation plan is transmitted via the second secure communication channel from the main server to the patient device.

### Claim 9 (depends on 1)

The method according to claim 1, further comprising:
(a) transmitting, by the main server, via a primary communication channel, to the patient device, the new actuation plan; and
(b) transmitting a user authenticating key to the patient device via a secondary communication channel, and wherein reconfiguring the bone fixation device includes authentication of the new actuation plan using the user authenticating key.

### Claim 10 (depends on 1)

The method according to claim 1, wherein:
(i) notifying the patient device includes sending an authenticating key to the patient device, and
(ii) requesting the new actuation plan includes sending the authenticating key from the patient device to the main server.

### Claim 11 (depends on 1)

The method according to claim 1, wherein:
(i) notifying the patient device includes sending an identifier to the patient device, and
(ii) requesting the new actuation plan includes sending the identifier from the patient device to the main server.

### Claim 12 (depends on 1)

The method according to claim 1, further including, prior to generating the new actuation plan:
(a) generating, on the main server, a halt command for the bone fixation device, the halt command including operational parameters for ceasing operations of the bone fixation device,
(b) notifying the patient device that the halt command has been generated,
(c) requesting from the patient on the patient device an approval of the halt command, and
(d) upon receiving the patient's approval, transmitting the halt command to the bone fixation device.

### Claim 13 (depends on 1)

The method according to claim 1, wherein the new actuation plan includes one or more operational parameters for implementing a function selected from the group consisting of:
(a) halting operation of one or more portions of the bone fixation device, and
(b) resuming operation of one or more portions of the bone fixation device.

### Claim 14

A system for remote reconfiguration of a bone fixation device of a patient, the bone fixation device including a frame connectible to bone tissue, a plurality of adjustable struts connected to the frame, and a control system including: a plurality of actuators associated with the plurality of adjustable struts, each actuator configured for adjusting a length of at least one adjustable strut, the system comprising:
a patient device comprising at least one processing circuitry for remote reconfiguration of the bone fixation device, the at least one processing circuitry configured for:
(a) receiving, from a communicatively coupled main server, a notification that a new actuation plan is available on the main server, the new actuation plan including operational parameters of the bone fixation device,
(b) requesting from a patient an approval of the new actuation plan,
(c) upon receiving the patient's approval, requesting, from the main server, the new actuation plan from the main server,
(d) receiving, from the main server, the new actuation plan, and
(e) reconfiguring the bone fixation device with the new actuation plan.

### Claim 15 (depends on 14)

The system according to claim 14, wherein the at least one processing circuitry is further configured for:
generating a current status of the bone fixation device, the current status including data indicative of the operation and status of a current plan on the bone fixation device.

### Claim 16 (depends on 14)

The system according to claim 14, further including a notification server communicatively coupled to the patient device, and the at least one processing circuitry is further configured to receive the notification from the notification server.

### Claim 17 (depends on 16)

The system according to claim 16, further including a first secure communication channel between the notification server and the patient device, and the notification is received by the at least one processing circuitry via the first secure communication channel.

### Claim 18 (depends on 16)

The system according to claim 16, further including a second secure communication channel between the main server and the patient device, and the at least one processing circuitry is further configured to request the new actuation plan via the second secure communication channel and receive the new actuation plan is via the second secure communication channel from the main server.

### Claim 19 (depends on 14)

The system according to claim 14, wherein the at least one processing circuitry is further configured for:
(a) receiving, from the main server, via a primary communication channel, the new actuation plan; and
(b) receiving a user authenticating key via a secondary communication channel, and
(c) reconfiguring the bone fixation device based on authentication of the new actuation plan using the user authenticating key.

### Claim 20

A method for remote reconfiguration of a bone fixation device of a patient, the bone fixation device including a frame connectible to bone tissue, a plurality of adjustable struts connected to the frame, and a control system including: a plurality of actuators associated with the plurality of adjustable struts, each actuator configured for adjusting a length of at least one adjustable strut, the method comprising:
(a) generating, on a main server, a halt command for the bone fixation device, the halt command including operational parameters for ceasing operations of the bone fixation device,
(b) notifying a patient device that the halt command has been generated,
(c) requesting from a patient on the patient device an approval of the halt command,
(d) upon receiving the patient's approval, transmitting the halt command to the bone fixation device,
(e) generating, on the main server, a new actuation plan for the bone fixation device, the new actuation plan including operational parameters of the bone fixation device,
(f) notifying the patient device that the new actuation plan is available on the main server,
(g) requesting from the patient on the patient device an approval of the new actuation plan,
(h) upon receiving the patient's approval, requesting by the patient device the new actuation plan from the main server, and
(i) reconfiguring the bone fixation device with the new actuation plan.
