Planning device, computer-implemented method and computer program product for radiotherapy

Abstract

Disclosed is a treatment planning apparatus for radiotherapy, the apparatus comprising: a processing circuit; a network interface; and a non-transitory computer readable medium storing instructions that, when executed by the processing circuitry, cause the processing circuitry to: in a first mode of operation, receive input data including imaging data and one or more medical targets, and perform an optimization procedure using the input data to generate a treatment plan; and in a second mode of operation, outputting data including the imaging data and the one or more medical targets to an external treatment plan server via the network interface, and receiving a treatment plan from the external treatment plan server via the network interface.

Description

Technical Field

[0001] This invention relates to a treatment planning apparatus for radiotherapy planning. The invention also relates to a computer-implemented method for radiotherapy planning, and to a computer program product configured to perform the methods described herein when run on a computer or processing circuitry. Background Technology

[0002] Radiation therapy, or radiotherapy, can be described as using ionizing radiation to damage or destroy unhealthy cells in humans and animals. Ionizing radiation can be directed to tumors on the surface of the skin or deep inside the body. Common forms of ionizing radiation include X-rays and charged particles. An example of a radiation therapy technique is gamma rays. One method involves irradiating the patient with multiple lower-intensity gamma rays that are focused with high intensity and precision onto a target area (e.g., a tumor). Another example of radiotherapy includes using a linear accelerator (linac), which irradiates the target area with high-energy particles (e.g., electrons, high-energy photons, etc.). In yet another example, radiotherapy can be delivered using a heavily charged particle accelerator (e.g., protons, carbon ions, etc.).

[0003] The placement and dosage of radiation beams can be precisely controlled to deliver a prescribed dose of radiation to a target area (such as a tumor) and minimize damage to surrounding healthy tissues (called organs at risk, OARs). The process of determining the placement and dosage of one or more radiation beams for any given treatment is called treatment planning, and the device that performs this process is called a treatment planning system.

[0004] One aspect of treatment planning involves determining the appropriate characteristics of the radiation to be delivered to produce a safe and effective dose. These characteristics include, for example, the fluence pattern or distribution. The fluence pattern can depend on the beam arrangement, energy, and field size, which in turn are related to controllable parameters (which are optimizable). By determining appropriate values ​​for these parameters, a suitable fluence pattern can be obtained.

[0005] Optimization processes can be used to develop radiotherapy plans (treatment plans, or simply plans) to determine the optimal set of parameter or variable values ​​for the expected delivery of an appropriate dose. Optimization processes can be based on clinical and dosimetric goals and constraints. Examples of clinical and dosimetric goals and constraints include maximum, minimum, and average doses to the target area and surrounding areas (e.g., tumors and critical organs). Clinical and dosimetric goals and constraints can be referred to as treatment planning objectives. Optimization is typically performed with respect to one or more treatment planning parameters to reduce beam-on time, improve dose homogeneity, etc.

[0006] The treatment planning process may involve using images of the patient (two-dimensional or three-dimensional) to identify the target region and critical organs near the target region. Segmentation can be used to identify the target region (or area to be treated, such as the planned target volume (PTV)) and surrounding areas (such as the organ of radiation exposure area). After segmentation, a dosing plan can be created for the patient, indicating the desired dose of radiation to be received by the target region and / or surrounding areas. The target region may have an irregular volume and may vary in size, shape, and location.

[0007] In practical examples, there may be multiple anatomical structures (target area and / or surrounding areas). For example, in head and neck treatment, there may be more than 20 anatomical structures. For each structure, various treatment planning goals may be desired. For example, the target area may be associated with a minimum dose target (in other words, the dose delivered to the target area should be at least X); the OAR may be associated with a maximum dose target (in other words, the dose delivered to the OAR should not exceed Y). Different priorities can be assigned to structures and their goals to achieve a clinically acceptable plan.

[0008] Creating a radiation therapy plan is typically a time-consuming process in which planners may attempt to adhere to various treatment goals or constraints—considering their respective importance—to produce a clinically acceptable radiation therapy plan. Common problems encountered when creating radiation therapy plans involving optimization processes include the lengthy optimization time and high computational burden required to achieve safe and satisfactory results. These processes often involve trial and error by users (e.g., treatment planners, dosimeters, clinicians, or healthcare workers), can be time-consuming, and are further complicated by the addition of additional goals and constraints.

[0009] Therefore, the software used for radiotherapy planning is also complex and undergoes significant ongoing research and development. As new features are added and optimization processes improve, the software can be expected to benefit from updates to new versions. Treatment planning systems with such software are typically located close to the radiotherapy unit where the treatment plan will be implemented. For example, they may be located within the same medical center or department. While the process for remotely updating software is generally well-known, patient safety aspects of radiotherapy (and therefore treatment planning) mean that updating treatment planning software is not so straightforward. For instance, once a new version of the software is installed, a safety check may need to be performed before use.

[0010] An alternative approach is to use a client-server architecture for treatment planning. In this method, the software installed locally at or near the radiotherapy unit consists only of a client that interacts with a remote server to perform optimization tasks. The client itself does not perform optimization tasks; instead, it communicates with the remote server by sending the data necessary to generate the treatment plan and then receiving the plan from the remote server. The remote server can provide treatment planning services to multiple clients, and the treatment planning software installed on the remote server can be updated as new versions become available. Some problems with this approach are that it relies on sufficient performance of the remote server and a reliable network between the client and server through which communication takes place. If the network between the client and server fails, treatment planning cannot continue, and ultimately the radiotherapy unit becomes unusable.

[0011] Therefore, an improved system for radiotherapy planning is desired. Summary of the Invention

[0012] The purpose of the embodiments of the present invention is to solve these and other problems in the art.

[0013] In one aspect, the present invention provides a treatment planning apparatus for radiotherapy. The apparatus includes: processing circuitry; a network interface; and a non-transient computer-readable medium. The medium stores instructions that, when executed by the processing circuitry, cause the processing circuitry to: in a first operating mode, receive input data including imaging data and one or more medical targets, and perform an optimization process using the input data to generate a treatment plan; and in a second operating mode, output data including imaging data and one or more medical targets to an external treatment planning server via the network interface, and receive the treatment plan from the external treatment planning server via the network interface.

[0014] In a second aspect, the present invention provides a computer-implemented method executed by a computer or processing circuitry for radiotherapy planning. The method includes: in a first operating mode, receiving input data including imaging data and one or more medical targets, and performing an optimization process using the input data to generate a treatment plan; and in a second operating mode, outputting data including imaging data and one or more medical targets to an external treatment planning server via a network interface, and receiving the treatment plan from the external treatment planning server via the network interface.

[0015] In a third aspect, the present invention provides a computer program product for performing the method of the second aspect. The computer program product may include a computer-readable medium embodied therein, the computer-readable medium having computer-readable code configured to, when executed by a computer or processing circuitry, cause the computer or processing circuitry to: in a first operating mode, receive input data including imaging data and one or more medical targets, and perform an optimization process using the input data to generate a treatment plan; and in a second operating mode, output data including imaging data and one or more medical targets to an external treatment plan server via a network interface, and receive a treatment plan from the external treatment plan server via the network interface. Attached Figure Description

[0016] To better understand the invention, and to more clearly illustrate how the invention can be implemented, reference will now be made to the accompanying drawings by way of example only, in which:

[0017] Figure 1 This is a schematic diagram of a radiotherapy planning system according to an embodiment of the present invention;

[0018] Figure 2 This is a flowchart of a computer-implemented method according to an embodiment of the present invention;

[0019] Figure 3 This is a schematic diagram of a radiotherapy planning device according to an embodiment of the present invention; and

[0020] Figure 4 This is a schematic diagram of a radiotherapy device. Detailed Implementation

[0021] Figure 1 This is a schematic diagram of a radiotherapy planning system 100 according to an embodiment of the present invention. System 100 includes one or more local treatment planning devices 110 (in the illustrated embodiment, system 100 includes a plurality of such devices 110) and a central treatment planning server 120. In some embodiments, system 100 further includes an addressing server 130.

[0022] Each treatment planning device 110 is associated with one or more radiotherapy implementation devices 116 and provides treatment plans to these radiotherapy implementation devices. Figure 4 The illustration schematically depicts one possible radiotherapy implementation device, but those skilled in the art will understand that different radiotherapy methods and architectures are possible within the scope of this invention.

[0023] Each treatment planning device 110 can be described as "local" in the sense of its close proximity to one or more radiotherapy implementation devices 116 on which the treatment plan provided by the treatment planning device 110 will be implemented. For example, the treatment planning device 110 may be located in the same medical center or department as the one or more radiotherapy implementation devices. In another example, the treatment planning device 110 may be located on the same local communication network (e.g., LAN) as the one or more radiotherapy implementation devices 116. In some embodiments, the treatment planning device 110 may be located in the same location as the radiotherapy implementation device 116. For example, the treatment planning device 110 may be implemented within the same computing system or controller that controls the radiotherapy implementation device (regarding...). Figure 4 (See below).

[0024] The treatment planning device 110 includes a treatment planning core 112 (also referred to as the "core") and a treatment planning controller 114 (also referred to as the "controller"). The core 112 includes hardware, software, or a combination of hardware and software configured to perform the treatment planning process. For example, the core may include a dedicated processor for performing the treatment planning process or a general-purpose processor running software for performing the treatment planning process.

[0025] Those skilled in the art will understand that the precise nature of the treatment planning process performed by core 112 is irrelevant to understanding embodiments of the invention. However, typically, the treatment planning process may include one or more optimization processes for determining a treatment plan. For example, such a process may determine the weights of one or more radiation sub-beams delivered as part of radiotherapy. The optimization process may utilize a cost function comprising a mathematical expression relating the dose distribution (e.g., per unit dose) to the sub-beam weights. The cost function may incorporate one or more medical objectives (also referred to as reference objectives) and / or one or more constraints. Reference objectives may list one or more of the maximum dose, minimum dose, and average dose to be achieved within a given volume (e.g., target, OAR, healthy tissue, etc.). The cost function may be configured to employ higher values ​​to reflect failure of a given dose distribution to meet one or more of these objectives, and lower values ​​to reflect satisfaction of a given dose distribution to meet one or more of these objectives. Constraints may be implemented by setting hard constraints on output parameters (e.g., sub-beam weights) to reflect the physical realities and / or constraints of the radiotherapy apparatus 116 to which treatment is to be performed. For example, a fundamental constraint may be that sub-beam weights cannot be negative. Additional constraints may be imposed, for example, by the maximum sub-beam weight defined by the maximum power output of the radiotherapy device 116, or by the permissible angular range from which radiation can be delivered, for example, defined by the physical geometry of the radiotherapy device 116.

[0026] The controller 114 is responsible for determining the operating mode of the treatment planning device 110 and controlling the treatment planning process according to this operating mode. In the first mode, the treatment plan is executed within the treatment planning device; that is, the treatment planning device 110 generates the treatment plan using its own core 112. In the second mode, the treatment planning device communicates with and receives treatment plans from the central treatment planning server 120. Importantly, the device 110 has the ability to operate in both operating modes. The device includes a core 112 that enables the device to generate treatment plans itself (i.e., in the first operating mode), and it has one or more interfaces to communicate with and obtain treatment plans from the central server 120 (i.e., in the second operating mode). Further details regarding this operation are described below. Figure 2 The method is described as shown.

[0027] The central treatment planning server 120 may be described as “central” to distinguish it from the “local” treatment planning device 110. Those skilled in the art will understand that the treatment planning server 120 does not need to be located centrally within system 100 in a geographical or any other sense. The central treatment planning server 120 is located external to and remote from the local treatment planning device 110, and communicates with the device to generate treatment plans according to a second operating mode, which will be referenced below. Figure 2 Let's have a more detailed discussion.

[0028] The central treatment planning server 120 includes its own treatment planning core 122. This core 122 can be substantially similar to the core 112 implemented in the local treatment planning device 110. That is, the core 122 also includes hardware, software, or a combination of hardware and software configured to perform treatment planning processes. The core may include a dedicated processor for performing the treatment planning process, or a general-purpose processor running software for performing the treatment planning process. The central treatment planning server 120 can be operable to perform treatment planning processes for multiple local treatment planning devices 110, therefore the core 122 can have a larger capacity than the core 112. For example, the core 122 can be implemented in multiple processors, multiple servers, processors with greater computing power, etc.

[0029] In the illustrated embodiment, the central treatment planning server 120 is not associated with any specific radiotherapy device. That is, the central treatment planning server 120 functions to provide treatment plans to the local treatment planning device 110 for implementation by its associated radiotherapy device 116; the central treatment planning server 120 does not generate treatment plans for implementation by any radiotherapy device associated with it. However, in other embodiments, the central treatment planning server 120 may have one or more associated radiotherapy devices in a manner similar to the local treatment planning device 110. In such embodiments, the central treatment planning server 120 may be substantially similar to the local treatment planning device 110, except that it provides external treatment planning services to other treatment planning devices 110.

[0030] Addressing server 130 includes a central treatment planning server 120 and a database 132 containing addressing information (e.g., Internet Protocol addresses) for one or more local treatment planning devices 110.

[0031] As mentioned above, while the process for remotely updating software is generally well-known, patient safety considerations in radiotherapy (and therefore treatment planning) mean that updating treatment planning software is not so straightforward. For example, once a new version of the software is installed, a security check may need to be performed before use. However, this approach relies on sufficient performance of the remote server and a reliable network through which the client and server communicate. If the network between the client and server fails, the treatment plan cannot continue, and ultimately the radiotherapy unit cannot be used.

[0032] Embodiments of the present invention address this problem by providing a treatment planning apparatus that can selectively operate in one of two operating modes. In a first mode, a treatment plan is executed within the treatment planning apparatus; that is, in the context of the system 100 described above, the treatment planning apparatus 110 generates a treatment plan using its own core 112. In a second mode, the treatment planning apparatus communicates with and receives a treatment plan from a remote treatment planning server (e.g., in a client-server architecture); in the context of system 100, the treatment planning apparatus 110 transmits input data to a central treatment planning server 120, which generates a treatment plan and provides it back to the treatment planning apparatus 110 for implementation by the radiotherapy system 116. Reference is made below. Figure 2 Let's elaborate on the other details.

[0033] Figure 2 This is a flowchart of a computer-implemented method according to an embodiment of the present invention. The method can be implemented by a treatment planning device, for example... Figure 1 The local treatment planning device 110 shown.

[0034] The method begins at step 200, where the apparatus receives input data and uses that input data to generate a treatment plan. For example, the input data may include imaging data (e.g., two-dimensional or three-dimensional imaging data) of the patient for whom a treatment plan will be generated. The input data may also include one or more medical objectives that the treatment plan must meet, such as one or more of the maximum dose, minimum dose, and average dose to be achieved within a given volume (e.g., target, OAR, healthy tissue, etc.). The input data may also include indications of one or more constraints for the treatment planning process, such as based on the radiotherapy apparatus for achieving the treatment plan (e.g., maximum dose rate, range of possible delivery angles of the radiation beam, etc.) and / or based on physical realities (e.g., subbeam weights cannot be negative).

[0035] Input data can be received directly from an imaging system (e.g., magnetic resonance imaging data, computational tomography data, etc.) or from an intermediate database storing such data. Similarly, medical goals and / or constraints can be received directly from the medical operator of the treatment planning system or from a database storing such data (and initially provided by a physician or other qualified medical personnel).

[0036] In step 202, the device determines whether it operates in a first operating mode (also referred to herein as the "local" operating mode) or in a second operating mode (also referred to herein as the "remote" operating mode).

[0037] The choice between a first operating mode and a second operating mode can be a subject of user input and / or automatic input. For example, a user of the treatment planning device can select or configure the device to operate in either a first or second operating mode. One or the other operating mode can be selected as the default mode, which will be utilized without any further user input; for example, the first operating mode can be the default mode.

[0038] The operating mode can be selected based on one or more performance criteria. Specifically, since the second operating mode relies on sufficient performance of the external treatment planning server, the first operating mode can be selected (e.g., automatically) in response to determining that the external treatment planning server does not meet one or more performance criteria. Such performance criteria may include one or more of the following: the external treatment planning server is reachable via a network interface; the external treatment planning server generates a treatment plan within a threshold time; the external treatment planning server has a workload less than a threshold amount. That is, the first operating mode can be selected if the external treatment planning server becomes unreachable (e.g., due to a network failure); a network failure can be detected by timeouts in attempts by the device to reach the external treatment planning server. The first operating mode can also be selected if the external treatment planning server has a high workload or fails to generate a treatment plan within a sufficient timeframe. Performance statistics (and / or current workload levels) can be shared between the external treatment planning server and the device, or measured by the device itself, and then used as part of the selection process.

[0039] The first operating mode is a standalone mode, in which a local treatment planning device (e.g., core 112) generates a treatment plan based on input data without outputting imaging data or medical goals and / or constraints to the central server 120 via a network interface. Optimization and / or computational tasks are performed locally by core 112. This first operating mode may correspond to local inter-process communication (IPC).

[0040] In the second operating mode, optimization and / or computation tasks are performed by an external treatment planning server. This second operating mode may correspond to a remote procedure call (RPC), where the local treatment planning device 110 operates as a client and the external treatment planning server 120 operates as a server.

[0041] In the first operating mode, the process moves to step 204, where the local treatment planning device itself performs optimization and / or computation tasks using the input data received in step 200 to generate a treatment plan. Therefore, controller 114 uses the input data received in step 200 to guide core 112 in performing optimization and / or computation tasks to generate a treatment plan.

[0042] In step 206, the treatment plan thus generated is output to the radiotherapy implementation device 116 for implementation. Alternatively, the treatment plan can be output to a database for storage, so that it can be implemented by the device 116 at a later time.

[0043] In the second operating mode, the process moves to step 208, where the local treatment planning device outputs imaging data, medical objectives, and / or constraints to the external treatment planning server 120 via its network interface. The local treatment planning device can also output instructions to the external treatment planning server 120 to perform one or more optimization and / or computational tasks using the output data to generate a treatment plan. That is, the local treatment planning device causes procedures (e.g., subroutines) to be executed on the external treatment planning server.

[0044] The local treatment planning device can communicate with an addressing server (e.g., addressing server 130) to discover the address of the external server 120. In cases where system 100 includes multiple external treatment planning servers, addressing server 130 can implement one or more load balancing algorithms to identify the server 120 with the best capabilities to handle requests from the local treatment planning device. Once identified, addressing server 130 provides the address information of the identified server 120 to device 110, enabling communication between the two entities.

[0045] The external treatment planning server 120 thus performs optimization and / or computational tasks (e.g., using its core 122) to generate a treatment plan, and in step 210, the device 110 receives the treatment plan from the external server 120. The process moves to step 206, and the received treatment plan is output to the radiotherapy implementation device 116 for implementation. Alternatively, the treatment plan may be output to a database for storage, to be implemented by the device 116 at a later time.

[0046] Communication between device 110 and server 120 can be direct or indirect. In the former case, the data transmitted in step 208 and / or the treatment plan received in step 210 can be directly transmitted between device 110 and server 120 (e.g., in the absence of an intermediate network node between the two entities). In the latter case, the data transmitted in step 208 and / or the treatment plan received in step 210 can be transmitted between the two entities via one or more intermediate network nodes. The intermediate network nodes used for the data transmitted in step 208 and for the treatment plan received in step 210 can be the same or different.

[0047] Figure 3 This is a schematic diagram of a radiotherapy planning apparatus 300 according to an embodiment of the present invention. The optical network element includes processing circuitry 302, a non-transient computer-readable medium 304, and one or more interfaces 306.

[0048] Processing circuitry 302 may include one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device or resource; or a combination of hardware, software, and / or coded logic operable to provide the functionality of the treatment planning system 300, either alone or in combination with other components of the treatment planning system 300, such as memory 304. For example, processing circuitry 302 may be configured to cause the treatment planning system to perform actions as described in the reference. Figure 2 The method described.

[0049] Therefore, in one embodiment, the processing circuit 302 is configured to cause the treatment planning system 300 to: in a first operating mode, receive input data including imaging data and medical targets, and perform an optimization process using the input data to generate a treatment plan; and in a second operating mode, output data including imaging data and medical targets to an external treatment planning server via a network interface, and receive a treatment plan from the external treatment planning server via a network interface.

[0050] Memory 304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)) and / or any other volatile or non-volatile, non-transient device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 302. Memory 304 may store any suitable instructions, data, or information, including computer programs, software, including logic, rules, code, tables, and / or executable by processing circuitry 302 and utilized by treatment planning system 300 (e.g., for performing...). Figure 2 The method may be applied in one or more of the other instructions. Memory 304 may be used to store any calculations performed by processing circuitry 302 and / or any data received via communication interface 306. In some embodiments, processing circuitry 302 and memory 304 are integrated.

[0051] One or more communication interfaces 306 are used for wired or wireless communication of signals and / or data between the treatment planning system 300 and the network, and / or between the treatment planning system 300 and one or more network servers (e.g., central planning server 120 and / or addressing server 130). Communication interface 306 may include one or more ports / one or more terminals for sending data to and receiving data from the network via wired connections (e.g., electrical, optical, etc.) and / or wireless connections.

[0052] The methods of this invention can be implemented in hardware or as software modules running on one or more processors. The methods can also be executed according to instructions of a computer program, and the invention also provides a computer-readable medium having a program stored thereon for performing any of the methods described herein. The computer program embodying the invention can be stored on a computer-readable medium, or it can be, for example, in the form of a signal, such as a downloadable data signal provided from an Internet website, or it can be any other form.

[0053] Figure 4 A radiotherapy implementation apparatus 400 suitable for implementing a radiotherapy plan determined according to an embodiment of the invention is described.

[0054] The radiotherapy apparatus 400 includes a radiation head 410 and a beam receiver 402, both attached to a gantry 404. The radiation head 410 includes a radiation source 412 that emits a radiation beam 406. The radiation source may include a linear accelerator designed to accelerate charged particles (e.g., protons, electrons, etc.) to therapeutic energies (e.g., in the MeV range). The radiation thus generated may include the charged particles themselves (e.g., alpha or beta radiation) and / or secondary radiation (e.g., X-rays, neutrons, etc.) generated by directing the charged particles to a target. The radiation head 410 also includes a beamforming device 418 that controls the size and shape of the radiation field associated with the beam.

[0055] The beam receiving device 402 is configured to receive radiation emitted from the radiating head 410 in order to absorb and / or measure the radiation beam. In the view shown, the radiating head 410 and the beam receiving device 402 are positioned diametrically opposite each other.

[0056] The gantry 404 may be rotatable and supports the radiator 410 and beam receiver 402 such that they can rotate about a rotation axis 408 that can coincide with the patient's longitudinal axis. The gantry provides rotation of the radiator 410 and beam receiver 402 in a plane perpendicular to the patient's longitudinal axis (e.g., the sagittal plane). Three gantry directions X can be defined. G Y G Z G , where Y G The direction is perpendicular to the axis of rotation of the platform. Z G The direction extends from the point on the gantry corresponding to the radiant head toward the axis of rotation of the gantry. Therefore, from the patient reference frame, Z... G The direction rotates as the test bench rotates.

[0057] The radiotherapy apparatus 400 also includes a support surface 420 that supports the subject (or patient) during radiotherapy. The radiation head 410 is configured to rotate about a rotation axis 408 such that the radiation head 410 directs radiation toward the subject from various angles around the subject, thereby diffusing the radiation dose received by healthy tissue to a larger area of ​​healthy tissue while accumulating a prescribed radiation dose at the target area.

[0058] The radiotherapy device 400 is configured to deliver a radiation beam toward a radiation isocenter, which is located approximately on a rotation axis 408 at the center of the gantry 404, regardless of the angle at which the radiation head 410 is positioned.

[0059] The dimensions of the rotatable stage 404 and the radiant head 410 are determined to allow for the presence of a central aperture 422. The central aperture 422 provides an opening sufficient to allow a subject to be positioned therethrough without accidental contact with the radiant head 410 or other mechanical components as the stage rotates around the subject.

[0060] A radiation head 410 emits a radiation beam 406 along a beam axis 424 (or radiation axis or beam path), wherein the beam axis 424 defines the direction of radiation emitted by the radiation head. The radiation beam 406 is incident on a beam receiving device 402, which may include at least one of a beam stop and a radiation detector. The beam receiving device 402 is attached to a stage 404 on the side opposite the diameter of the radiation head 410 to attenuate and / or detect the radiation beam after it has passed through a subject.

[0061] For example, the radiation beam axis 424 can be defined as the center or the point of maximum intensity of the radiation beam 406.

[0062] Beam shaping device 418 defines the diffusion of the radiation beam 406. Beam shaping device 418 is configured to adjust the shape and / or size of the radiation field generated by the radiation source. Beam shaping device 418 achieves this by defining a variable-shaped aperture (also called a window or opening) to calibrate the radiation beam 406 to a selected cross-sectional shape. In this example, beam shaping device 418 can be provided by a combination of an aperture and an MLC. Beam shaping device 418 can also be referred to as a beam modifier.

[0063] The radiotherapy device 400 can be configured to perform coplanar and non-coplanar (also known as tilted) modes of radiotherapy. In coplanar treatment, radiation is emitted in a plane perpendicular to the axis of rotation of the radiation head 410. In non-coplanar treatment, radiation is emitted at an angle not perpendicular to the axis of rotation. To perform coplanar and non-coplanar treatment, the radiation head 410 can be moved between at least two positions: one where radiation is emitted in a plane perpendicular to the axis of rotation (coplanar configuration), and another where radiation is emitted in a plane not perpendicular to the axis of rotation (non-coplanar configuration).

[0064] In a coplanar configuration, the radiator is positioned to rotate about the axis of rotation and within a first plane. In a non-coplanar configuration, the radiator is tilted relative to the first plane, such that the radiation field generated by the radiator is guided at an angle relative to the first plane and the axis of rotation. In a non-coplanar configuration, the radiator is positioned to rotate in a corresponding second plane parallel to and displaced from the first plane. The radiation beam is emitted at an angle relative to the second plane, thus sweeping out a cone shape as the radiator rotates.

[0065] When the radiotherapy apparatus is in coplanar and non-coplanar modes, the beam receiver 402 remains in the same position relative to the rotatable stage. Therefore, the beam receiver 402 is configured to rotate about the axis of rotation in the same plane in both coplanar and non-coplanar modes. This can be the same plane as the plane in which the radiation head rotates.

[0066] The beam forming device 410 is configured to reduce the diffusion of the radiation field in a non-coplanar configuration compared to a coplanar configuration.

[0067] The radiotherapy apparatus 400 includes a controller 430 programmed to control a radiation source 412, a beam receiver 806, and a gantry 802. The controller 430 can perform functions or operations such as treatment planning, treatment execution, image acquisition, image processing, motion tracking, motion management, and / or other tasks involved in the radiotherapy process. Specifically, in one embodiment, a local treatment planning device 110 may be implemented within the controller 430 of the radiotherapy administration apparatus 400. In other embodiments, the local treatment planning device 110 may be implemented in a separate computing device.

[0068] The controller 430 is programmed to control the features of the device 400 according to a radiotherapy plan in order to irradiate the patient's target area, also known as the target tissue. The treatment plan includes information about the specific dose to be applied to the target tissue, as well as other parameters such as beam angle, dose histogram volume information, the number of radiation beams to be used during treatment, and the dose of each beam. The controller 430 is programmed to control various components of the device 400 according to the treatment plan, such as the gantry 404, the radiation head 410, the beam receiver 402, and the support surface 420.

[0069] The hardware components of controller 430 may include one or more computers (e.g., general-purpose computers, workstations, servers, terminals, portable / mobile devices, etc.); processors (e.g., central processing units (CPUs), graphics processing units (GPUs), microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), dedicated or special-purpose processors, etc.); memory / storage devices, such as memory (e.g., read-only memory (ROM), random access memory (RAM), flash memory, hard disk drives, optical disks, solid-state drives (SSDs), etc.); input devices (e.g., keyboards, mice, touchscreens, MICS, buttons, knobs, trackballs, joysticks, handles, joysticks, etc.); output devices (e.g., displays, printers, speakers, vibration devices, etc.); circuitry; printed circuit boards (PCBs); or other suitable hardware. The software components of controller 430 may include operating device software, application software, etc.

[0070] A radiator 410 may be connected to a head actuator 414 configured to actuate the radiator 410, for example, between a coplanar configuration and one or more non-coplanar configurations. This may involve translation and rotation of the radiator 410 relative to the test bench. In some implementations, the head actuator may include a curved track along which the radiator 410 can move to adjust the position and angle of the radiator 410. A controller 430 may control the configuration of the radiator 430 via the head actuator 414.

[0071] The beamforming apparatus 418 includes a shaping actuator 416. The shaping actuator is configured to control the position of one or more elements in the beamforming apparatus 418 to shape the radiation beam 406. In some implementations, the beamforming apparatus 418 includes an MLC (Multi-Layer Cylinder), and the shaping actuator 416 includes means for actuating blades of the MLC. The beamforming apparatus 418 may also include an aperture, and the shaping actuator 416 may include means for actuating a block of the aperture. A controller 430 may control the beamforming apparatus 418 via the shaping actuator 416.

[0072] The treatment plan may include positioning information for the bundle forming device 418. The positioning information for the bundle forming device 418 may include information indicating the configuration of one or more elements of the bundle forming device 418, such as the leaf configuration of the MLC of the bundle forming device 418, the configuration of the aperture of the bundle forming device 418, the configuration of the openings (e.g., windows or orifices) of the MLC, etc.

[0073] Those skilled in the art will understand that device 400 is merely one example of a radiotherapy apparatus capable of implementing a treatment plan. Alternative radiotherapy implementation apparatus may not include [details about the apparatus]. Figure 4One or more of the described features may be configured differently (e.g., source 412 may be fixed in place, or the apparatus may include multiple radiation sources configured to deliver radiation from multiple directions). Generally, embodiments of the invention are applicable to any radiotherapy implementation apparatus that requires the generation of a treatment plan.

[0074] Unless otherwise specifically stated, as is evident from the foregoing discussion, it should be understood that throughout this specification, discussions using terms such as “receive,” “determine,” “compare,” “implement,” “maintain,” “identify,” “obtain,” and “access” refer to the actions and processes of a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the registers and memories of the computer system and transforms it into other data similarly represented as physical quantities in the computer system’s memory or registers or other such information storage, transmission, or display devices.

[0075] While certain embodiments have been described, these embodiments are presented by way of example only and are not intended to limit the scope of the invention. In fact, the novel methods and apparatus described herein can be embodied in various other forms; furthermore, various omissions, substitutions, and changes can be made to the form of the methods and apparatus described herein.

Claims

1. A treatment planning device for radiotherapy, characterized in that, The device includes: Processing circuitry; Network interface; and A non-transient computer-readable medium storing instructions that, when executed by the processing circuitry, cause the processing circuitry to: In the first operating mode, input data including imaging data and one or more medical targets is received, and an optimization process is performed using the input data to generate a treatment plan; and In the second operating mode, data including imaging data and one or more medical targets are output to an external treatment planning server via the network interface, and a treatment plan is received from the external treatment planning server via the network interface.

2. The treatment planning device according to claim 1, characterized in that, The processing circuit can be configured to operate in either the first or the second operating mode based on user input.

3. The treatment planning device according to claim 1, characterized in that, The first operating mode is the default mode.

4. The treatment planning device according to claim 1, characterized in that, The processing circuitry is configured to enter the first operating mode in response to determining that the external treatment plan server does not meet one or more performance criteria.

5. The treatment planning device according to claim 4, characterized in that, The one or more performance criteria include one or more of the following criteria: the external treatment plan server is accessible via the network interface; the external treatment plan server generates the treatment plan within a threshold time; the external treatment plan server has a workload less than a threshold amount.

6. The treatment planning device according to any one of the preceding claims, characterized in that, The first operating mode is a stand-alone mode, in which the processing circuit generates the treatment plan without outputting imaging data or medical targets through the network interface.

7. The treatment planning device according to any one of the preceding claims, characterized in that, The processing circuitry performs optimization and / or computation tasks locally in the first operating mode.

8. The treatment planning device according to any one of the preceding claims, characterized in that, The first operation mode corresponds to local inter-process communication.

9. The treatment planning device according to any one of the preceding claims, characterized in that, In the second operating mode, optimization and / or computation tasks are performed by the external treatment planning server.

10. The treatment planning device according to any one of the preceding claims, characterized in that, The second operating mode corresponds to remote procedure call.

11. The treatment planning device according to any one of the preceding claims, characterized in that, In the second operating mode, the processing circuit is operable to obtain the address information of the external treatment plan server via communication with an external addressing server.

12. The treatment planning device according to claim 11, characterized in that, The address information includes Internet Protocol (IP) addresses.

13. The treatment planning device according to any one of the preceding claims, characterized in that, In the second operating mode, the data, including imaging data and one or more medical targets, is sent to the external treatment planning server via the network interface and through one or more first intermediate network nodes.

14. The treatment planning device according to any one of the preceding claims, characterized in that, In the second operating mode, the treatment plan is received from the external treatment plan server via the network interface through one or more second intermediate network nodes.

15. A computer-implemented method executed by a computer or processing circuitry for use in radiotherapy planning, characterized in that, The method includes: In the first operating mode, input data including imaging data and one or more medical targets is received, and an optimization process is performed using the input data to generate a treatment plan; and In the second operating mode, data including imaging data and one or more medical targets are output to an external treatment planning server via a network interface, and a treatment plan is received from the external treatment planning server via the network interface.

16. The method according to claim 15, characterized in that, The first or second operating mode is based on user input selection.

17. The method according to claim 15, characterized in that, The first operating mode is the default mode.

18. The method according to claim 15, characterized in that, The first operating mode is selected in response to determining that the external treatment plan server does not meet one or more performance criteria.

19. The method according to claim 18, characterized in that, The one or more performance criteria include one or more of the following criteria: the external treatment plan server is accessible via the network interface; the external treatment plan server generates the treatment plan within a threshold time; the external treatment plan server has a workload less than a threshold amount.

20. The method according to any one of claims 15 to 19, characterized in that, The first operating mode is a stand-alone mode, in which the computer or the processing circuit generates the treatment plan without outputting imaging data or medical targets through the network interface.

21. The method according to any one of claims 15 to 20, characterized in that, The optimization and / or computation tasks are performed locally by the computer or the processing circuit in the first operating mode.

22. The method according to any one of claims 15 to 21, characterized in that, The first operation mode corresponds to local inter-process communication.

23. The method according to any one of claims 15 to 22, characterized in that, In the second operating mode, optimization and / or computation tasks are performed by the external treatment planning server.

24. The method according to any one of claims 15 to 23, characterized in that, The second operating mode corresponds to remote procedure call.

25. The method according to any one of claims 15 to 24, characterized in that, Also includes: In the second operating mode, the address information of the external treatment plan server is obtained via communication with the external addressing server.

26. The method according to claim 25, characterized in that, The address information includes Internet Protocol (IP) addresses.

27. The method according to any one of claims 15 to 26, characterized in that, In the second operating mode, the data, including imaging data and one or more medical targets, is sent to the external treatment planning server via the network interface and through one or more first intermediate network nodes.

28. The method according to any one of claims 15 to 27, characterized in that, In the second operating mode, the treatment plan is received from the external treatment plan server via the network interface through one or more second intermediate network nodes.

29. A computer program product comprising a computer-readable medium, wherein computer-readable code is specifically implemented in the computer-readable medium, characterized in that, The computer-readable code is configured to cause the computer or processing circuitry to perform the method according to any one of claims 15 to 28 when executed by the computer or processing circuitry.

Images