Cloud-based dose verification
US-2024123258-A1 · Apr 18, 2024 · US
US2025140379A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025140379-A1 |
| Application number | US-202318494475-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 25, 2023 |
| Priority date | Oct 25, 2023 |
| Publication date | May 1, 2025 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and techniques may be used for visualization of radiation therapy data. An example method may include determining a data set corresponding to visualization data to be displayed in an application user interface (e.g., on a client device). The data set may include one or more Digital Imaging and Communications in Medicine (DICOM) objects. A request for the data set may be received at an application programming interface (API) configured to access multiple sources of DICOM objects. The method may include processing the requested data set, verifying the request for the data set, and upon the verifying, providing the client device with access to the processed data set to enable visualization of the processed data set. The processed data set may be cached, and verified requests for the same data set may be provided access to the cached processed data to visualize at the same or different client device.
Opening claim text (preview).
What is claimed is: 1 . A method of radiation therapy data visualization, the method comprising: determining a data set corresponding to visualization data to be displayed in an application user interface, the data set including one or more Digital Imaging and Communications in Medicine (DICOM) objects; receiving a request for the data set at an application programming interface (API), wherein the API is configured to access multiple sources of DICOM objects; processing the requested data set, wherein processing the requested data set includes optimizing the requested data set; verifying the request for the data set, and providing, responsive to the verifying, a client device with access to the processed data set to enable visualization of the processed data in the application user interface. 2 . The method of claim 1 , wherein optimizing the requested data set includes optimizing the requested data set for visualization without visualizing the requested data set. 3 . The method of claim 1 , wherein an environment comprising the multiple sources of DICOM objects includes a multi-application and a multi-tenant environment, and wherein the API retrieves the requested data set from a cached data source. 4 . The method of claim 1 , wherein processing the requested data set includes: removing identifying information of a patient, wherein removing identifying information of the patient includes extracting a portion of pixel data from the one or more DICOM objects. 5 . The method of claim 1 , further comprising: creating a secure key corresponding to the one or more DICOM objects; and verifying, in response to receiving the API request, that the secure key corresponds to the requested data set. 6 . The method of claim 5 , further comprising: caching the processed data set; receiving a second request for the data set at the API, the request including a second secure key; verifying, in response to receiving the second request, that the second secure key corresponds to the requested data set; and responsive to the verifying, providing a second client device with access to the cached processed data set to enable visualization. 7 . The method of claim 5 , wherein the request for the data set at the API includes the secure key, wherein the secure key is unique to the API request and only allows access to a specific combination of the one or more DICOM objects in the data set, and wherein the secure key is provided in a JSON web token (JWT). 8 . The method of claim 7 , wherein to verify that the secure key corresponds to the requested data set, the API validates the JWT using a public key, and wherein the public key is configured to: validate that the client device is a valid source to request the data set; and validate that the request for the data set has not been modified or corrupted in transit from the client device. 9 . The method of claim 5 , wherein the secure key includes a message digest, the message digest including a hash generated from a list of each of the one or more DICOM objects, and wherein the hash is generated from one or more of: a list of images, one or more spatial registration objects, a structure set, a radiotherapy plan, or a radiotherapy dose to be visualized. 10 . The method of claim 5 , further comprising: transmitting secure key to a renderer of the client device. 11 . The method of claim 5 , wherein determining the data set and creating the secure key is performed by a first server, wherein the first server generates the secure key using a private key, and wherein receiving the request for the data set, verifying that the secure key corresponds to the requested data set, processing the requested data set, and providing the client device access to the processed data set is performed by a second server different than the first server. 12 . A system for radiation therapy data visualization, the system comprising: processing circuitry; and memory, including instructions stored thereon, which, when executed by the processing circuitry, cause the processing circuitry to: determine a data set corresponding to visualization data to be displayed in an application user interface, the data set including one or more Digital Imaging and Communications in Medicine (DICOM) objects; create a secure key corresponding to the one or more DICOM objects; receive a request for the data set at an application programming interface (API), the request including the secure key, wherein the API is configured to access multiple sources of DICOM objects; verify, in response to receiving the API request, that the secure key corresponds to the requested data set; process the requested data set to remove identifying information, wherein the processing includes: optimizing the requested data set for visualization without visualizing the requested data set; and caching the optimized data set; and responsive to the verifying, provide a client device with access to the processed data set to enable visualization of the processed data at the application user interface. 13 . The system of claim 12 , wherein an environment comprising the multiple sources of DICOM objects includes at least one of a multi-application or a multi-tenant environment, and wherein the API retrieves the requested data set from a cached data source. 14 . The system of claim 12 , wherein the secure key is provided in a JSON web token (JWT), and wherein to verify that the secure key corresponds to the requested data set the API validates the JWT using a public key. 15 . The system of claim 14 , wherein the public key is configured to: validate that the client device is a valid source to request the data set; and validate that the request for the data set has not been modified or corrupted in transit from the client device. 16 . The system of claim 12 , wherein the secure key only allows access to a specific combination of the one or more DICOM objects in the data set, wherein the secure key includes a message digest, the message digest including a hash generated from a list of each of the one or more DICOM objects, and wherein the hash is generated from one or more of: a list of images, one or more spatial registration objects, a structure set, a radiotherapy plan, or a radiotherapy dose to be visualized. 17 . The system of claim 12 , wherein processing the requested data set includes: extracting a portion of pixel data from the one or more DICOM objects. 18 . A non-transitory computer-readable medium with instructions stored thereon that, when executed by a processor of a computing device, cause the processor to: determining a data set corresponding to visualization data to be displayed in an application user interface, the data set including one or more Digital Imaging and Communications in Medicine (DICOM) objects; create a secure key corresponding to the one or more DICOM objects; receive a request for the data set at an application programming interface (API), the request including the secure key, wherein the API is configured to access multiple sources of DICOM objects; verify, in response to receiving the API request, that the secure key corresponds to the requested data set; process the requested data set to remove identifying information, wherein processing the requested data set includes optimizing the requested data set; and responsive to the verifying, provide a client device with access to the processed data set to enable visualization of the data in the application user interface. 19 . Th
X-ray therapy; Gamma-ray therapy; Particle-irradiation therapy (A61N5/01 takes precedence) · CPC title
for handling medical images, e.g. DICOM, HL7 or PACS · CPC title
relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture · CPC title
Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062) · CPC title
Protecting personal data, e.g. for financial or medical purposes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.