Automatic cancer registry record generation

Through the computer system automatically processing and updating the cancer registration form records, the problems of cumbersome and inaccurate data entry in the prior art are solved, and the rapid and accurate data generation and update are achieved, which improves the timeliness and value of data.

CN113728392BActive Publication Date: 2024-11-12ELEKTA AB
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202080031298.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-03-14
Filing Date
2020-03-11
Publication Date
2024-11-12
Estimated Expiration
2040-03-11

AI Technical Summary

Technical Problem

The data entry process of the existing electronic cancer registration form is cumbersome, time-consuming and easy to introduce inaccuracies, resulting in data delays and inefficiencies, affecting the timeliness and accuracy of the data.

Method used

Through computer-implemented methods and systems, automatic processing of patient medical information is used, natural language processing and rule evaluation generate and update cancer registration records, fill in missing information, and share data between multiple hospitals to ensure the timeliness and accuracy of the data .

Benefits of technology

It realizes the rapid and accurate generation and update of cancer registration records, reduces clinicians' examination and correction time, improves the timeliness and value of data, and ensures that the latest group medical information is reflected.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113728392B_ABST
    Figure CN113728392B_ABST
Patent Text Reader

Abstract

Techniques for generating cancer registry records are provided. The techniques include: obtaining a plurality of rules that define cancer registry record generation based on a patient health record; obtaining one or more electronic health records associated with the patient that include cancer-related treatment information; processing the cancer-related treatment information in the one or more electronic health records to generate a cancer registry record for the patient that represents partial cancer-related treatment information; determining that the cancer registry record includes insufficient cancer-related treatment information; and updating the cancer registry record to resolve the insufficient cancer-related treatment information by evaluating the cancer-related treatment information against the plurality of rules.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Priority claim

[0002] This application is a continuation of and claims the benefit of priority to U.S. application Serial No. 16 / 354,090, filed on March 14, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of the present disclosure generally relate to methods and systems for managing patient treatment using an electronic patient data repository, such as a cancer registry. Background Art

[0004] Electronic data repositories, such as registries established for trauma, transplantation, and cancer patients, can be used to collect and store useful information about specific and potentially large groups over potentially long periods of time. For example, the Surveillance, Epidemiology, and End Results (SEER) program, supported by the National Cancer Institute (NCI), collects data on specific geographic areas and specific types of cancer covering more than 25% of the U.S. population, with data in some places dating back to 1973. Such repositories can provide valuable data in quantities sufficient for meaningful analysis. Data is entered into such registries through a manual process that is subject to various regulatory rules, which takes a lot of time and effort, which introduces long delays and inefficiencies in the collected data. In addition, it is difficult and tedious to ensure that all rules are followed, which produces inaccuracies in the data that are ultimately entered.

[0005] Overview

[0006] The present disclosure includes a process for generating a cancer registry record.

[0007] In some embodiments, the technology includes a computer-implemented method and system comprising at least one processor and a storage medium, the storage medium comprising instructions that cause the processor to perform the following operations: obtain multiple rules that define cancer registry record generation based on a patient health record; obtain one or more electronic health records associated with the patient that include cancer-related treatment information; process the cancer-related treatment information in the one or more electronic health records to generate a cancer registry record for the patient that represents a portion of the cancer-related treatment information; determine that the cancer registry record includes insufficient cancer-related treatment information; and update the cancer registry record by evaluating the cancer-related treatment information against multiple rules to resolve the insufficient cancer-related treatment information.

[0008] In some implementations, determining that the cancer registry record includes insufficient cancer-related treatment information includes automatically determining that the cancer registry record includes missing or incomplete information. In some implementations, the cancer registry record is stored in a government-mandated registry.

[0009] In some implementations, cancer-related treatment information is processed by performing natural language processing to generate data representing the cancer-related treatment information; identifying one or more cancer registry codes associated with the generated data based on a plurality of rules; and populating one or more fields in a cancer registry record based on the identified one or more cancer registry codes.

[0010] In some implementations, the one or more electronic health records are in a first format and the cancer registry record is in a second format.

[0011] In some implementations, in response to processing the cancer-related treatment information, determining that the portion of the cancer-related treatment information corresponds to a cancer-related treatment or diagnosis; comparing the cancer-related treatment or diagnosis to a threshold value representing the frequency of the cancer-related treatment or diagnosis; and in response to determining that the cancer-related treatment or diagnosis exceeds the threshold value, generating a notification for a user to review the cancer registry record.

[0012] In some implementations, determining based on at least one of the rules that data in a first field in a cancer registry record is inconsistent with data in a second field in the cancer registry record; accessing additional cancer-related treatment information from one or more electronic health records to verify that the data in at least one of the first field or the second field is correct; and updating the data in at least one of the first field or the second field based on the additional cancer-related treatment information. In some implementations, the data in the first field indicates that the patient is female, and the data in the second field indicates a diagnosis of prostate cancer, and accessing the additional cancer-related treatment information is performed by retrieving at least one of medical imaging information or blood sample information from one or more electronic health records; determining that the medical imaging information or the blood sample information corresponds to a male patient; and adjusting the data in the first field to indicate that the patient is male, or marking the data for review.

[0013] In some implementations, determining that a first type of data from the cancer-related treatment information corresponds to a first code for a field in a cancer registry record; determining that a second type of data from the cancer-related treatment information corresponds to a second code for a field in the cancer registry record; prioritizing the second type of data over the first type of data based on a rule; and populating the field in the cancer registry record with the second code instead of the first code based on the prioritization. In some implementations, the first type of data represents results of a biopsy and the second type of data represents results from medical imaging.

[0014] In some implementations, a set of cancer registry records associated with multiple cancer patients that are similar to the generated cancer registry record are identified; treatment regimens indicated in the set of cancer registry records are identified; and a recommended treatment regimen for treating the patient is generated based on the identified treatment regimens.

[0015] In some implementations, one or more electronic health records are retrieved from a first database that manages cancer patients of a first hospital; one or more additional electronic health records are obtained from a second database that manages cancer patients of a second hospital; and the cancer registry records from a plurality of cancer registry records are stored in an inter-hospital registry containing data about a group of cancer patients.

[0016] The above summary is intended to provide an overview of the subject matter of this patent application. It is not intended to provide an exclusive or exhaustive description of the present disclosure. The detailed description is included to provide additional information about this patent application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In the drawings, which are not necessarily drawn to scale, similar reference numerals describe substantially similar components throughout the several views. Similar reference numerals with different letter suffixes represent different instances of substantially similar components. The accompanying drawings generally illustrate various embodiments discussed in this document by way of example and not by way of limitation.

[0018] Figure 1 An example radiation therapy system suitable for performing a treatment plan generation process according to some examples is shown.

[0019] Figure 2 An example image-guided radiation therapy apparatus according to some examples of the present disclosure is shown.

[0020] Figure 3 to Figure 4 An example of a cancer registry record-generating workflow according to some examples of the present disclosure is shown.

[0021] Figure 5 An example cancer registry record-generating workflow across multiple hospitals is shown according to some examples of the present disclosure.

[0022] Figure 6 A flow diagram illustrating example operations for automatically generating cancer registry records according to some examples of the present disclosure.

[0023] Figure 7 An example user interface of a cancer registry record-generating workflow according to some examples of the present disclosure is shown. DETAILED DESCRIPTION

[0024] The present disclosure includes various techniques for generating a cancer registry record. Specifically, the disclosed techniques obtain a plurality of rules that define cancer registry record generation based on a patient health record, and obtain one or more electronic health records associated with the patient that include cancer-related treatment information. The cancer-related treatment information in the one or more electronic health records is processed to generate a cancer registry record for the patient that represents a portion of the cancer-related treatment information. The disclosed techniques determine that the cancer registry record includes insufficient cancer-related treatment information, and automatically update the cancer registry record to address the insufficient cancer-related treatment information by evaluating the cancer-related treatment information against a plurality of rules.

[0025] Typically, medical information can be contributed to the data repository by trained and / or certified and collected, viewed and entered according to the established standards by the people they believe to be accurate information. For example, cancer registrants enter data into cancer registry forms, as required by the North American Association of Central Cancer Registries (NAACCR) data standards. Such data repository is used to describe the incidence or prevalence of certain events (for example, birth, violent crime, obesity, accidental death and disease) of a particular group within a specific time period. In the case of appropriate certain privacy controls, electronic data repository can be shared between programs and institutions, and can even be public. For example, SEER data is available to researchers and the public, and they use this information to search for cancer trends, report cancer statistics in geographic areas and identify cancer risk factors. Such research can be used to focus on remedial efforts, such as education or outreach, particularly in areas or personnel that are considered to be at risk.

[0026] In many cases, trained data entry personnel utilize the reporting guidelines provided by NCI to complete the cancer registry, as well as various resources that help clinicians fill out the cancer registry. When the record has data that is correctly entered, verified as correct and / or otherwise verified, the information contained therein is structured and uploaded to the cancer registry. Although such a record creation process works well over time, the process of creating such a record is very time-consuming and undergoes some changes between clinicians. Specifically, the time required to create a verified registry record is usually longer, and for many cancer registries, the patient's data is entered for the first time several months or even years after the patient is diagnosed with cancer. Based on the registrant's assessment of multiple possible contradictory information sources, one field at a time is entered, and the process is slow, tedious, repeated and time-consuming. The registrant may have multiple cases waiting in the queue, and these cases are in various states of completion due to difficulty in verifying or obtaining necessary data. Not surprisingly, the patient's additional data may be provided occasionally, for example, after cure, five years later, and after death. The utility of the registry record is usually limited to the difficulty of providing a verified registry record. Furthermore, due to the long delays in creating and validating such records in repositories, studies utilizing records often generate results based on stale data and fail to reflect the most up-to-date status of the population.

[0027] To address such inefficiencies and poor data analysis, the disclosed technology automatically processes patient medical information (without receiving user input) and automatically utilizes rules (without receiving user input) to create accurate medical records. The disclosed technology creates reliable and accurate electronic records for cancer patients, and / or the disclosed technology augments registry records with additional medical information sources that can be easily accessed to provide instant insight into cancer treatment methods, trends, etc. This ensures that the data reflected in the state and / or hospital repositories is up to date with the latest available medical information about a given population.

[0028] Specifically, in some embodiments, existing human and knowledge resources for creating and updating registry records are substantially eliminated and augmented, respectively. The time spent by clinicians reviewing and correcting rejected registry records is reduced, if not eliminated. In addition, the disclosed embodiments address the need to provide validated records in a more timely manner so that the structured information contained therein can have greater value and utility to stakeholders such as medical professionals, researchers, and biopharmaceutical and medical device companies.

[0029] In some embodiments, the content of the verified registry record is enhanced. Specifically, the available resources from the hospital's data repository are used to supplement the information found in the verified registry record. For example, in one embodiment, the registry record is supplemented by adding the following content: information describing the specific mode for treating the patient, and optionally parameters of indications specific to the treatment of the mode recorded or observed during the course of treatment, such as dosage, treatment duration, and. In some embodiments, a hospital-to-hospital registry is created using a verified registry record and / or an enhanced registry record. The hospital-to-hospital registry can be used to expand the physician's available resources when the physician selects or modifies a treatment plan for her patient. For example, the hospital-to-hospital registry can provide benchmark data for the treatment of a specific type of mode used for a given condition and patient demographics. Considering the diversity and number of enhanced registry records that can be accumulated in the hospital-to-hospital registry, its beneficiaries, for example, can include physicians, researchers, and pharmaceutical and medical device companies looking for clinical trial candidates. The registry record or enhanced registry record (provided by the hospital's registry or via the hospital-to-hospital registry) is used with other patient data to expand the physician's decision-making when she plans a treatment plan for the patient.

[0030] In some embodiments, natural language processing is performed to process cancer-related treatment information for a given patient received from one or more hospitals. The data resulting from natural language processing is analyzed according to specified rules to identify one or more cancer registry codes associated with the data. A cancer registry template is retrieved, and the fields of the cancer registry template are automatically (without receiving user input) filled with the identified cancer registry code. After automatically (without receiving user input) generating a record (which may be in a format different from the received cancer-related treatment information), the record is processed to determine whether sufficient cancer-related information is included. This can be performed by determining whether the record includes missing or incomplete information.

[0031] In some implementations, a specified rule is used to determine whether the data in a first field in a cancer registry record is inconsistent with the data in a second field in the cancer registry record. For example, the data in the first field may indicate that the patient is female, and the data in the second field may indicate a diagnosis of prostate cancer, which is inconsistent with a female patient. In such a case, additional cancer-related treatment information is accessed from one or more electronic health records of the patient to verify that the data in at least one of the first field or the second field is correct. For example, at least one of medical imaging information or blood sample information can be retrieved from one or more electronic health records, and it can be determined that the medical imaging information or the blood sample information corresponds to a male patient. The data in at least one of the first field or the second field is then updated based on the additional cancer-related treatment information, or a notification can be provided in a graphical user interface to notify a clinician about the inconsistency for the clinician to review.

[0032] In some embodiments, the disclosed technology determines whether a portion of the cancer-related treatment information corresponds to a cancer-related treatment or diagnosis. The cancer-related treatment or diagnosis is compared to a threshold representing the frequency of the cancer-related treatment or diagnosis across a larger population. If the treatment or diagnosis exceeds the threshold, a notification is generated and displayed to a clinician or user in a graphical user interface, indicating the cancer-related treatment or diagnosis. The clinician can then view the automatically generated record to verify the accuracy of the cancer-related treatment or diagnosis.

[0033] In some embodiments, a collection of cancer registry records similar to the generated cancer registry record associated with a plurality of cancer patients is obtained. Treatment regimens indicated in the collection of cancer registry records are identified and used to generate a recommended treatment regimen for treating the patient. Such recommendations can be provided to a clinician in a graphical user interface for the clinician to review and accept.

[0034] Figure 1 An exemplary radiation therapy system 100 is shown that is suitable for performing treatment plan generation processing using one or more of the methods discussed herein. These radiation therapy planning processing operations are performed to enable the radiation therapy system 100 to provide radiation therapy to a patient based on captured medical imaging data and specific aspects of treatment dose calculations. The radiation therapy system 100 can automatically generate and verify cancer registry records. For example, the radiation therapy system 100 can obtain cancer-related treatment information for a given patient and perform natural language processing to obtain cancer-related data, which is analyzed together with specified rules to identify one or more cancer registry codes associated with the data. A cancer registry template can be retrieved, and the fields of the record can be automatically populated using the identified cancer registry codes.

[0035] The radiation therapy system 100 includes a radiation therapy processing computing system 110 that hosts treatment processing logic 120. The radiation therapy processing computing system 110 can be connected to a network (not shown), and such a network can be connected to the Internet. For example, the network can connect the radiation therapy processing computing system 110 with one or more medical information sources (e.g., a radiation information system (RIS), a medical record system (e.g., an electronic medical record (EMR) / electronic health record (EHR) system), an oncology information system (OIS)), one or more image data sources 150, an image acquisition device 170 (e.g., an imaging modality), a treatment device 180 (e.g., a radiation therapy device), and one or more treatment data sources 160. As an example, the radiation therapy treatment computing system 110 can be configured to receive cancer-related treatment information 162 of a subject, such as dose information or a magnetic resonance (MR) image, and as part of an operation to generate a registration record to be used by a treatment device 180 and / or for output on an output device 146, automatically generate a cancer registration record by applying rules to obtain a code representing the cancer-related treatment information, such as by executing instructions or data from the treatment processing logic 120.

[0036] The radiation therapy treatment computing system 110 may include a processing circuit system 112, a memory 114, a storage device 116, and other hardware-operable and software-operable features such as a user interface 142, a communication interface (not shown), etc. The storage device 116 may store transient or non-transitory computer-executable instructions such as an operating system, radiation therapy treatment plans (e.g., training cone beam computed tomography (CBCT) images, real computed tomography (CT) images, pairing information associating training images and real CT images, modified or altered CBCT images, etc.), software programs (e.g., image processing software; image or anatomical visualization software; AI implementations and algorithms such as provided by DL models, machine learning (ML) models, and neural networks, etc.), and any other computer-executable instructions to be executed by the processing circuit system 112.

[0037] In an example, processing circuit system 112 may include a processing device, for example, one or more general-purpose processing devices such as a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc. More specifically, processing circuit system 112 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor that implements other instruction sets, or a processor that implements a combination of instruction sets. Processing circuit system 112 may also be implemented by one or more special-purpose processing devices such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), a system on a chip (SoC), etc. As will be appreciated by those skilled in the art, in some examples, processing circuit system 112 may be a special-purpose processor rather than a general-purpose processor. Processing circuit system 112 may include one or more known processing devices, such as those from Intel. TM Pentium manufactured TM 、Core TM , Xeon TM or series of microprocessors from AMD TM Made by Turion TM , Athlon TM 、Sempron TM 、Opteron TM FX TM or Phenom TM series of microprocessors, or any of a variety of processors manufactured by Sun Microsystems. Processing circuit system 112 may also include a graphics processing unit, such as a graphics processing unit from Nvidia TM Manufactured or series of GPUs from Intel TM GMA or Iris manufactured TM series of GPUs, or from AMD TM Made by Radeon TM The processing circuit system 112 may also include an accelerated processing unit, such as an accelerated processing unit from Intel TM Xeon Phi manufactured TMseries of units. The disclosed embodiments are not limited to any type of processor, but may be embodied on any processor configured to meet the computational requirements of identifying, analyzing, maintaining, generating and / or providing large amounts of data or manipulating such data to perform the methods disclosed herein. In addition, the term "processor" may include more than one physical (circuitry-based) or software-based processor, such as a processor with a multi-core design or multiple processors each having a multi-core design. The processing circuit system 112 can execute a sequence of transient or non-transient computer program instructions stored in the memory 114 and accessed from the storage device 116 to perform various operations, processes, and methods that will be described in more detail below. It should be understood that any component in the radiation therapy system 100 can be implemented separately and operated as a stand-alone device, and can be coupled to any other component in the radiation therapy system 100 to perform the techniques described in the present disclosure.

[0038] Memory 114 may include read-only memory (ROM), phase-change random access memory (PRAM), static random access memory (SRAM), flash memory, random access memory (RAM), dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM), electrically erasable programmable read-only memory (EEPROM), static memory (e.g., flash memory, flash disk, static random access memory), other types of random access memory, cache memory, registers, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage device, cassette tape, other magnetic storage device, or any other non-transitory medium that can be used to store information including images, data, or transient or non-transitory computer executable instructions (e.g., stored in any format) that can be accessed by processing circuit system 112 or any other type of computer device. For example, computer program instructions can be accessed by processing circuit system 112, can be read from ROM or any other suitable memory location, and can be loaded into RAM for execution by processing circuit system 112.

[0039] The storage device 116 may constitute a drive unit including a transitory or non-transitory machine-readable medium on which is stored one or more transitory or non-transitory instruction sets and data structures (e.g., software) implemented or utilized by any one or more of the methods or functions described herein (including, in various examples, the treatment processing logic 120 and the user interface 142). During execution of the instructions by the radiation therapy treatment computing system 110, the instructions may also reside, in whole or in part, within the memory 114 and / or the processing circuit system 112, wherein the memory 114 and the processing circuit system 112 also constitute transitory or non-transitory machine-readable media.

[0040] The memory 114 and the storage device 116 may constitute a non-transitory computer-readable medium. For example, the memory 114 and the storage device 116 may store or load transient or non-transitory instructions for one or more software applications on a computer-readable medium. Software applications stored or loaded using the memory 114 and the storage device 116 may include, for example, operating systems for general-purpose computer systems and software-controlled devices. The radiotherapy treatment computing system 110 may also operate various software programs including software codes for implementing the treatment processing logic 120 and the user interface 142. In addition, the memory 114 and the storage device 116 may store or load the entire software application, a portion of the software application, or code or data associated with the software application that can be executed by the processing circuit system 112. In another example, the memory 114 and the storage device 116 may store, load, and manipulate one or more radiotherapy treatment plans, imaging data, segmentation data, treatment visualization, dose histograms, dose measurement results, AI model data (e.g., weights and parameters), marking and mapping data, etc. It is contemplated that the software program may be stored not only on storage device 116 and memory 114, but also on removable computer media such as a hard drive, a computer disk, a CD-ROM, a DVD, a Blu-ray DVD, a USB flash drive, an SD card, a memory stick, or any other suitable media; such software programs may also be transmitted or received over a network.

[0041] The memory 114 may be distributed across multiple hospitals or state registries. The memory 114 may be used to store information about Figures 2 to 7 Cancer-related treatment information and cancer registry records discussed. Cancer-related treatment information includes analog, digital, audio, visual, structured or unstructured data associated with a diagnosed or undiagnosed patient - it is maintained at one or more healthcare facilities such as a hospital. Cancer-related treatment information may include one or more of the following: existing or planned treatment regimens, enhanced registry records, recommended regimens, registry records provided to state registries, insurance providers, payment records, diagnostic conditions, pathology records, immunization registry records, trauma registry records, and epidemiological or radiological data. Registry records include structured data about patients including fields, which include one or more information or codes representing cancer-related information. Patients' registry records can be defined by a state or other authority, for example, through a menu-driven software application that provides users with templates for entering data into different fields of a record.

[0042] Although not depicted, the radiation therapy treatment computing system 110 may include a communication interface, a network interface card, and a communication circuit system. Example communication interfaces may include, for example, a network adapter, a cable connector, a serial connector, a USB connector, a parallel connector, a high-speed data transmission adapter (e.g., optical fiber, USB 3.0, thunderbolt, etc.), a wireless network adapter (e.g., an IEEE 802.11 / Wi-Fi adapter), a telecommunications adapter (e.g., communicating with 3G, 4G / LTE, and 5G networks, etc.), etc. Such a communication interface may include one or more digital and / or analog communication devices that allow the machine to communicate with other machines and devices, such as remotely located components, via a network. The network may provide the functionality of a local area network (LAN), a wireless network, a cloud computing environment (e.g., software as a service, platform as a service, infrastructure as a service, etc.), a client-server environment, a wide area network (WAN), etc. For example, the network may be a LAN or WAN that may include other systems, including additional image processing computing systems or image-based components associated with medical imaging or radiation therapy operations.

[0043] Processing circuitry 112 may be communicatively coupled to memory 114 and storage device 116, and processing circuitry 112 may be configured to execute computer-executable instructions stored thereon from memory 114 or storage device 116. Processing circuitry 112 may execute the instructions to cause medical images and / or cancer-related treatment information from image data 152 to be received or obtained in memory 114 and processed using treatment processing logic 120. In further examples, processing circuitry 112 may utilize a software program (e.g., image processing software) along with image data 152 and other patient data to automatically generate a cancer registry record.

[0044] In an example, the image data 152 may include one or more MRI images (e.g., 2D MRI, 3D MRI, 2D flow MRI, 4D MRI, 4D volume MRI, 4D imaging MRI, etc.), functional MRI images (e.g., fMRI, DCE-MRI, diffusion MRI), computed tomography (CT) images (e.g., 2D CT, 2D cone beam CT, 3D CT, 3D CBCT, 4D CT, 4D CBCT), ultrasound images (e.g., 2D ultrasound, 3D ultrasound, 4D ultrasound), positron emission tomography (PET) images, X-ray images, fluoroscopic images, radiotherapy portal images, single photon emission computed tomography (SPECT) images, computer-generated synthetic images (e.g., pseudo CT images), etc. In addition, the image data 152 may also include or be associated with medical image processing data, such as training images, ground truth images, contour images, and dose images. In other examples, equivalent representations of anatomical regions may be represented in non-image formats (eg, coordinates, maps, etc.).

[0045] In an example, the image data 152 may be received from the image acquisition device 170 and stored in one or more of the image data sources 150 (e.g., a picture archiving and communication system (PACS), a vendor neutral archive (VNA), a medical record or information system, a data warehouse, etc.). Thus, the image acquisition device 170 may include an MRI imaging device, a CT imaging device, a PET imaging device, an ultrasound imaging device, a fluoroscope device, a SPECT imaging device, an integrated linear accelerator and MRI imaging device, a CBCT imaging device, or other medical imaging device for obtaining medical images of a patient. The image data 152 may be received and stored in any data type or any format type (e.g., in a digital imaging and communications in medicine (DICOM) format) that the image acquisition device 170 and the radiation therapy treatment computing system 110 may use to perform operations consistent with the disclosed embodiments.

[0046] In an example, the image acquisition device 170 can be integrated with the treatment device 180 into a single device (e.g., an MRI device combined with a linear accelerator, also referred to as an "MRI-Linac"). Such an MRI-Linac can be used, for example, to determine the location of a target organ or target tumor in a patient to accurately guide the radiation therapy to a predetermined target according to a radiation therapy treatment plan. For example, a radiation therapy treatment plan can provide information about a specific radiation dose to be applied to each patient. The radiation therapy treatment plan can also include other radiation therapy information, such as beam angles, dose-histogram-volume information, the number of radiation beams to be used during treatment, the dose of each beam, etc.

[0047] The radiotherapy treatment computing system 110 can communicate with an external database via a network to send and receive a plurality of various types of data related to image processing and radiotherapy operations. For example, the external database may include machine data (including equipment constraints) that provides information associated with the treatment device 180, the image acquisition device 170, or other machines related to radiotherapy or medical procedures. The machine data information may include radiation beam size, arc placement, beam switch duration, machine parameters, segments, multi-leaf collimator (MLC) configuration, gantry speed, MRI pulse sequence, etc. The external database may be a storage device and may be equipped with an appropriate database management software program. In addition, such a database or data source may include multiple devices or systems located in a central manner or in a distributed manner.

[0048] The radiation therapy treatment computing system 110 can collect and obtain data via a network and communicate with other systems using one or more communication interfaces that are communicatively coupled to the processing circuit system 112 and the memory 114. For example, the communication interface can provide a communication connection between the radiation therapy treatment computing system 110 and radiation therapy system components (e.g., allowing data to be exchanged with external devices). For example, in some examples, the communication interface can have appropriate interface circuit systems with respect to the output device 146 or the input device 148 to connect to the user interface 142, which can be a hardware keyboard, keypad, or touch screen through which a user can enter information into the radiation therapy system 100.

[0049] As an example, output device 146 may include a display device that outputs: a representation of user interface 142; and one or more aspects, visualizations, or representations of medical images, treatment plans, and the status of training, generation, validation, or implementation of such plans. Output device 146 may output, for example, Figure 7The graphical user interface depicted. The output device 146 may include one or more display screens that display medical images, interface information, treatment plan parameters (e.g., contours, doses, beam angles, markers, maps, etc.), treatment plans, targets, information related to positioning and / or tracking of targets, or any information relevant to the user. The input device 148 connected to the user interface 142 may be a keyboard, keypad, touch screen, or device that a user can use to input information to the radiation therapy system 100. Alternatively, the output device 146, input device 148, and the features of the user interface 142 may be integrated into a device such as a smart phone or tablet computer (e.g., Apple Lenovo Samsung etc.) in a single device.

[0050] In addition, any and all components of the radiation therapy system 100 may be implemented as virtual machines (e.g., via a virtualization platform such as VMWare, Hyper-V, etc.) or standalone devices. For example, a virtual machine may be software that functions as hardware. Thus, a virtual machine may include at least one or more virtual processors, one or more virtual memories, and one or more virtual communication interfaces that function collectively as hardware. For example, the radiation therapy processing computing system 110, the image data source 150, or similar components may be implemented as virtual machines or within a cloud-based virtualization environment.

[0051] The treatment processing logic 120 or other software program may cause the radiation therapy treatment computing system 110 to communicate with the image data source 150 to read images from the image data source 150 into the memory 114 and storage device 116, or to store images or associated data from the memory 114 or storage device 116 to the image data source 150. For example, in a model training or generation use case, the image data source 150 may be configured to: store and provide a plurality of images (e.g., 3D MRI, 4D MRI, 2D MRI slice images, CT images, 2D fluoroscopic images, X-ray images, raw data from MR scans or CT scans, Digital Imaging and Communications in Medicine (DICOM) metadata, etc.) hosted by the image data source 150 from a set of images in the image data 152 obtained from one or more patients via the image acquisition device 170. Thus, the radiotherapy processing computing system 110 may obtain and / or receive image data 152 (e.g., 2D MRI slice images, CT images, 2D fluoroscopic images, X-ray images, 3D MRI images, 4D MRI images, etc.) from an image data source 150, an image acquisition device 170, a treatment device 180 (e.g., MRI-Linac), or other information system related to performing radiotherapy or diagnostic operations.

[0052] The image acquisition device 170 can be configured to acquire one or more images of the patient's anatomical structure for an area of ​​interest (e.g., a target organ, a target tumor, or both). Each image, typically a 2D image or slice, can include one or more parameters (e.g., 2D slice thickness, orientation, position, etc.). In an example, the image acquisition device 170 can acquire 2D slices of any orientation. For example, the orientation of a 2D slice can include a sagittal orientation, a coronal orientation, or an axial orientation. The processing circuit system 112 can adjust one or more parameters, such as the thickness and / or orientation of a 2D slice, to include a target organ and / or a target tumor. In an example, a 2D slice can be determined based on information such as a 3DCBCT or CT or MRI volume. When a patient is undergoing radiotherapy treatment, such as when using a treatment device 180, such a 2D slice can be acquired "near real time" by the image acquisition device 170 (wherein "near real time" means acquiring data at least in milliseconds or less).

[0053] The treatment processing logic 120 in the radiation therapy treatment computing system 110 is depicted as implementing a cancer registry record-generating workflow 130. The cancer registry record-generating workflow 130 may include a cancer registry rule processing 132, a health record processing 134, a record review / enhancement module 140, and a notification / recommendation module 141. In some embodiments, the cancer registry record-generating workflow 130 receives instructions, such as via a graphical user interface of an input device 148, to generate a cancer registry record for a given patient. The cancer registry record-generating workflow 130 may receive a patient identifier via the graphical user interface. In response, the cancer registry record-generating workflow 130 may obtain cancer-related treatment information for the patient from one or more hospitals, which may be stored in the storage device 116. The cancer registry record-generating workflow 130 processes the cancer-related treatment information using one or more disclosed techniques to automatically generate a cancer registry record and / or enhance an already available record for the patient. Once a cancer registry record has been generated or enhanced, the cancer registry record-generation workflow 130 stores the automatically generated or enhanced record in a state registry (eg, in the storage device 116 ) and / or makes the record available to one or more hospitals.

[0054] In some embodiments, the cancer registry record-generating workflow 130 instructs the health record processing 134 to obtain cancer-related treatment information for the identified patient. The health record processing 134 uses the unique patient identifier provided by the input device 148 to search one or more databases available from one or more hospitals and / or cancer registries to obtain cancer-related treatment information. In some implementations, the cancer-related treatment information includes previously generated cancer registry records, tumor geometry information, images of the patient's cancer area, oncology reports, dose information, radiation therapy plans, diagnostic information, survival rates, and / or any other suitable electronically available health information. In some implementations, the health record processing 134 performs natural language processing to convert any handwritten notes into computer-readable information in the cancer-related treatment information. The health record processing 134 identifies key terms in the processed handwritten notes indicating patient gender, dose information, treatment plan, diagnosis, etc.

[0055] The health record process 134 communicates with the cancer registry rule process 132 to cross-reference any combination of information and / or key terms generated or retrieved from the patient's cancer-related treatment information with a set of rules obtained by the cancer registry rule process 132. Specifically, the cancer registry rule process 132 can detect conditions associated with the patient automatically or based on information provided by a physician via a graphical user interface. The cancer registry rule process 132 accesses one or more publicly available regulatory cancer registry databases that contain rules that associate various key terms, conditions, combinations of conditions, cancer-related treatment information, and geometric information of a tumor with one or more corresponding cancer registry codes. The health record process 134 matches any combination of key terms and cancer-related treatment information with the codes in the rules. The health record process 134 retrieves the codes and fields of the cancer registry record associated with the codes. The health record process 134 transmits the retrieved codes and fields to the record review / enhancement module 140.

[0056] The record review / enhancement module 140 determines whether a cancer registry record has been previously created for the patient associated with the unique identifier. In response to determining that a record has not been previously created, the record review / enhancement module 140 retrieves various biometric information (e.g., gender, address, name, age, etc.) of the patient from the health record process 134 and / or retrieves various biometric information of the patient provided by the physician via the input device 148. The record review / enhancement module 140 obtains a template for the cancer registry record and automatically fills in the biometric information in corresponding biometric fields of the template using the retrieved biometric information of the patient. The record review / enhancement module 140 also identifies one or more fields in the template that correspond to fields associated with the code identified by the health record process 134. The record review / enhancement module 140 fills in these fields with the code received from the health record process 134.

[0057] In some implementations, a record may have been previously created for the patient. In such a case, the record review / enhancement module 140 determines the last modification date of the previously created record. The record review / enhancement module 140 determines whether the cancer-related treatment information used by the health record processing 134 to identify the code from the cancer registry rule processing 132 is associated with a date later than the last modification date of the previously created record. For example, the record may have been previously generated based on a first set of MRI images and a radiation therapy dose delivered on a specific date (e.g., March 1, 2018). The record review / enhancement module 140 may determine that a second set of MRI images was obtained on December 1, 2018 and a radiation therapy dose was delivered. In response, the record review / enhancement module 140 determines that the record contains insufficient cancer-related treatment information, and may instruct the health record processing 134 to generate a set of codes based on cancer-related treatment information obtained on a date after the last modification date of the previously created record. The record review / enhancement module 140 may then obtain the code from the health record process 134 and store the code in a corresponding field of the record and / or update a previously stored code with a new code for a field in the record.

[0058] In some embodiments, the record review / enhancement module 140 reviews the information in a given cancer registry record to detect inconsistencies. This can be done continuously by cycling through the various records stored in the cancer registry periodically, such as once a month for each record and / or in response to a specific user request identifying a given record or patient. The record review / enhancement module 140 can access a set of rules stored by the cancer registry rule processing 132 that indicate different types of errors or inconsistencies.

[0059] For example, a rule may indicate that a female patient cannot be diagnosed with prostate cancer. A rule may indicate that a male patient cannot be diagnosed with breast cancer. A rule may indicate that a specific amount of radiation or dose distribution for a given diagnosis in a specific area cannot exceed a specified amount. A rule may indicate that the geometry of a tumor cannot exceed the geometry of an organ and / or cannot be located in a specific area of ​​a patient. A rule may be manually updated over time based on input from a physician received via a graphical user interface.

[0060] The record review / enhancement module 140 can compare the fields associated with the rules in the record with the parameters of the rule to detect inconsistencies. For example, the record review / enhancement module 140 can retrieve the gender specified in the record and the diagnosis specified in the record. The record review / enhancement module 140 can access a particularly impossible rule that specifies a given gender (e.g., a female patient cannot be diagnosed as having prostate cancer). The record review / enhancement module 140 can determine that the information in the record violates the condition of the rule (or corresponds to the impossibility indicated by the rule) by determining that the record has a field indicating a female gender and the diagnosis code in the diagnosis field indicates prostate cancer. As another example, the record review / enhancement module 140 can determine that the information in the record violates the condition of the rule (or corresponds to the impossibility indicated by the rule) by determining that the record has a field indicating a given geometric size of a tumor in a patient, and another field identifying the type of tumor and a corresponding size that exceeds the maximum geometric size of a specific type of tumor specified in the rule.

[0061] In response to determining that the record violates the rule condition, the record review / enhancement module 140 instructs the health record processing 134 to obtain additional information about the patient. For example, the record review / enhancement module 140 may instruct the health record processing 134 to obtain blood information associated with the patient. The record review / enhancement module 140 may process the blood information to determine that the patient is male. The record review / enhancement module 140 may determine that the gender indicated in a field of the record indicates female, and may automatically update the gender to indicate that the patient is male.

[0062] In some implementations, additional information to resolve the inconsistency may not be available to the health record processing 134. For example, blood information may not yet be available for the patient. In such a case, the record review / enhancement module 140 can communicate with the notification / recommendation module 141 to alert the physician or clinician about the inconsistency in the cancer registry record. The notification / recommendation module 141 can present a graphical user interface that visually distinguishes the fields that are detected as violating the rule condition or inconsistency. The notification / recommendation module 141 can receive input from the physician to correct the inconsistency via the graphical user interface and input device 148, and the record can be updated and stored in the storage device 116.

[0063] In some embodiments, the record review / enhancement module 140 can automatically access the population information for a given set or combination of fields in the cancer registry. For example, the record review / enhancement module 140 can select tumor type, tumor geometry, gender, age, diagnosis, and dose information fields as a combination of fields to search in the population information. The record review / enhancement module 140 can retrieve the patient information specified in the registry record for a specific patient in the selected field and find patients with similar conditions in the population. For example, the record review / enhancement module 140 can access multiple records from the entire population or a subset of the population stored in the cancer registry and obtain the information stored in the selected field. The record review / enhancement module 140 can filter all records into those records of patients with the same gender as the specific patient and with the same tumor type, the same tumor geometry, and the same diagnosis. The record review / enhancement module 140 can generate an average or other statistical measure of the dose information contained in the filtered retrieved records to determine specific dose information.

[0064] The record review / enhancement module 140 may compare specific dose information representing a population having the same gender, the same tumor type, the same tumor geometry, and the same diagnosis as a specific patient with dose information stored in a field of a record of a specific patient. The record review / enhancement module 140 may determine whether the dose information stored in the field of the specific patient is within a threshold or range (e.g., within 1% to 2%) of the specific dose information representing the population. In response to determining that the dose information exceeds the threshold, the record review / enhancement module 140 instructs the notification / recommendation module 141 to generate a notification for display to the physician in a graphical user interface, indicating that the dose exceeds the population dose. Alternatively or additionally, if the dose is not stored in a field of the patient's record, the record review / enhancement module 140 may enhance the record by entering specific dose information representing the population in the patient's record. The record review / enhancement module 140 may instruct the notification / recommendation module 141 to generate a notification for display to the physician in a graphical user interface, indicating an automatically generated dose recommendation.

[0065] exist Figures 3 to 7 Additional details and examples of the treatment processing logic 120 for automatically generating cancer registry records are provided in .

[0066] Figure 2 An exemplary image-guided radiation therapy device 202 is shown, which includes a radiation source such as an x-ray source or a linear accelerator, a bed 216, an imaging detector 214, and a radiation therapy output 204. The image-guided radiation therapy device 202 can be configured to emit a radiation therapy beam 208 to provide treatment to a patient. The radiation therapy output 204 can include one or more attenuators or collimators, such as a multi-leaf collimator (MLC).

[0067] As an example, a patient can be positioned in an area 212 supported by a bed 216 to receive a radiation therapy dose according to a radiation therapy treatment plan. The radiation therapy output 204 can be mounted or attached to a gantry 206 or other mechanical support. When the bed 216 is inserted into the treatment area, one or more chassis motors (not shown) can rotate the gantry 206 and the radiation therapy output 204 around the bed 216. In an example, the gantry 206 can be continuously rotatable around the bed 216 when the bed 216 is inserted into the treatment area. In another example, the gantry 206 can be rotated to a predetermined position when the bed 216 is inserted into the treatment area. For example, the gantry 206 can be configured to rotate the radiation therapy output 204 around an axis ("A"). Both the couch 216 and the radiation therapy output 204 can be independently moved to other positions around the patient, for example, in a transverse direction ("T"), in a lateral direction ("L"), or by rotation about one or more other axes, such as a transverse axis (denoted as "R"). A controller communicatively connected to one or more actuators (not shown) can control the couch 216 to move or rotate to appropriately position the patient in or out of the radiation therapy beam 208 according to the radiation therapy treatment plan. Both the couch 216 and the gantry 204 can be moved independently of each other in multiple degrees of freedom, which enables the patient to be positioned so that the radiation therapy beam 208 can be precisely targeted to the tumor.

[0068] Figure 2 208 (including axis A, axis T, and axis L) can have an origin located at an isocenter 210. The isocenter 210 can be defined as the location where the central axis of the radiotherapy beam 208 intersects the origin of the coordinate axes, such as a location to deliver a prescribed radiation dose to a patient or a location within the patient. Alternatively, the isocenter 210 can be defined as the location where the central axis of the radiotherapy beam 208 intersects the patient for various rotational positions of the radiotherapy output 204 about axis A as positioned by the gantry 206.

[0069] The gantry 206 may also have an attached imaging detector 214. The imaging detector 214 is preferably positioned opposite the radiation source (e.g., the radiotherapy output 204), and in an example, the imaging detector 214 may be located within the field of the radiotherapy beam 208. The imaging detector 214 may be mounted on the gantry 206, preferably opposite the radiotherapy output 204, for example to maintain alignment with the radiotherapy beam 208. As the gantry 206 rotates, the imaging detector 214 rotates about the rotation axis. In an example, the imaging detector 214 may be a flat panel detector (e.g., a direct detector or a scintillator detector). In this manner, the imaging detector 214 may be used to monitor the radiotherapy beam 208, or the imaging detector 214 may be used to image the patient's anatomical structure, for example, by portal imaging. The control circuitry of the image-guided radiotherapy device 202 may be integrated within the radiotherapy system 100 or remote from the radiotherapy system 100.

[0070] In the illustrative example, one or more of the couch 216, the radiotherapy output 204, or the gantry 206 may be automatically positioned, and the radiotherapy output 204 may create a radiotherapy beam 208 according to a specified dose for a particular treatment delivery instance. A sequence of treatment deliveries may be specified according to a radiotherapy treatment plan, for example, using one or more different orientations or positions of the gantry 206, the couch 216, or the radiotherapy output 204. The treatment deliveries may occur sequentially, but may intersect at desired treatment sites on or within the patient, for example, at the isocenter 210. Thus, a prescribed cumulative dose of radiotherapy may be delivered to the treatment site while reducing or avoiding damage to tissue near the treatment site.

[0071] Figure 3 An example of a cancer registry record-generating workflow according to some examples of the present disclosure is shown. Figure 3 A network is shown including a hospital registry 310, a hospital data repository 311 for storing and managing hospital data, an inter-hospital registry 314, and one or more input and user interface devices 312. Users and / or applications running on the network can be communicatively connected to the state registry 313 and the inter-hospital registry 314 via the Internet. The network includes one or more computers including general purpose processors for executing code, reading and writing functions, and network connectivity.

[0072] The hospital data repository 311 is a data repository that stores various information related to hospital functions such as accounting, employees, human resources, physicians, logistics personnel, nurses, etc., and medical information about patients admitted or treated in the hospital or under the supervision of hospital staff. Figure 3The categories of information 311a shown in are merely examples of information stored in the hospital data repository 311. The data in the hospital data repository 311 may be organized in a database format or a data lake format, and / or it may have a collection of flat or structured files organized under a file directory system according to general topics such as oncology or accounting. The data stored in the hospital data repository 311 is stored in a variety of data formats, including structured and unstructured data formats, in different and sometimes incompatible file formats. The hospital data repository 311 stores cancer-related treatment information for various patients of the hospital. In some embodiments, the memory 114 may store all or part of the hospital data repository 311.

[0073] Hospital registry 310 is a data repository that stores validated registry records for patients. Such records may include records automatically generated by cancer registry record-generating workflow 130 based on cancer-related patient information stored in hospital data repository 311. Hospital registry 310 stores data from registry records in a database format so that information contained in fields of a record can be easily retrieved from a user or machine initiated search query of information contained in one or more registry records.

[0074] The state registry 313 is accessed via the Internet and represents a designated location for uploading verified registry records for patients of hospitals operating within the jurisdiction of the state. Registry records can be created from patient data contained in the hospital data repository 311. Registry verification application software (e.g., record viewing / enhancement module 140) is used to create, fill and verify registry records. Registry records can be verified by record viewing / enhancement module 140 before being uploaded to the state registry 313. Record viewing / enhancement module 140 includes a menu-driven system and templates for automatic or semi-automatic entry of patient data. Data about newly diagnosed patients or existing patients, such as demographics, disease type, duration of treatment, and progression of disease since first diagnosis, are entered using a user interface and menu system by a registrant or other qualified person (using input and user interface device 312). When the record is completed and verified by record viewing / enhancement module 140, the record is uploaded to the state registry 313, and a copy is stored in the hospital registry 310.

[0075] Figure 4An example of a cancer registry record-generating workflow according to some examples of the present disclosure is shown. When a patient is recently diagnosed, for example, as having cancer (as indicated by the International Classification of Diseases (ICD) code 10) or when a previously diagnosed patient requires an updated registry record, the record review / enhancement module 140 of the cancer registry record-generating workflow 130 is invoked. In either case, the record review / enhancement module 140 is invoked to automatically prepare or update the patient's registry record by accessing available cancer-related treatment information about the patient (e.g., in a spreadsheet or SQL database).

[0076] In some embodiments, the cancer-related treatment information module 410 (which can implement the health record processing 134) obtains cancer-related treatment information about the patient. This can be performed by retrieving cancer-related treatment information based on a unique patient identifier from a database of one or more hospitals. The information obtained is provided to the cancer registry record-generating module 412. The cancer-related treatment information module 410 and the cancer registry record-generating module 412 can be implemented as separate modules of the treatment processing logic 120 and / or as part of the record viewing / enhancing module 140. The cancer registry record-generating module 412 communicates with one or more state registries to obtain cancer registry rules associated with a given state. The cancer registry record-generating module 412 applies the retrieved rules to the cancer-related treatment information received from the cancer-related treatment information module 410 to identify one or more codes associated with each specific condition or set of conditions specified in the cancer-related treatment information. The cancer registry record-generating module 412 fills the cancer registry template based on the code by automatically entering the identified code into the corresponding field of the template. The cancer registry record-generating module 412 outputs a new cancer registry record 420. In an embodiment, the cancer registry record-generating module 412 obtains an old cancer registry record, identifies a set of cancer-related treatment information that has been updated since the old cancer registry record was generated, and identifies fields and codes of a template that correspond only to the newly updated cancer-related treatment information.

[0077] The record review / enhancement module 140 determines whether the record 420 is incomplete, contains invalid data, or contains data that is incompatible with other data entered in the record 420. In such cases, the record 420 is invalid and is rejected. When the record 420 is rejected, the record review / enhancement module 140 automatically resolves the problem and, if possible, provides an updated record 422. The record review / enhancement module 140 can be run as a stand-alone program. The record review / enhancement module 140 analyzes the source of the error that caused the record 420 to be rejected, finds a solution if possible, and generates an updated record 422. The updated record 422 is then input to the record review / enhancement module 140, which is then evaluated. If all errors have been corrected, the record review / enhancement module 140 can then verify the updated record 422 and upload it to the state register 313.

[0078] In some embodiments, the record review / enhancement module 140 is configured to determine that a value in one field (e.g., an EMR code) is valid but inconsistent or conflicting with data in another portion of the record, for example (e.g., a patient received treatment one month after the patient's death). In such a case, the record review / enhancement module 140 automatically retrieves additional information about the patient to resolve the inconsistency. If the additional information is not available or does not resolve the inconsistency, the record review / enhancement module 140 flags the error and generates a notification for an operator to review the inconsistency using a graphical user interface.

[0079] In some embodiments, the record review / enhancement module 140 is configured to determine that the data location accessed by the record review / enhancement module 140 contains conflicting information from fields of records from two sources. In such a case, the record review / enhancement module 140 obtains the priority assigned to each source and automatically replaces or resolves the conflict by filling the field with data from the source with a higher priority. Alternatively or additionally, the record review / enhancement module 140 marks the error and generates a notification for the operator to view the conflict using a graphical user interface. For example, the record review / enhancement module 140 may determine that the registry record includes a diagnosis date of January 1 for a chest X-ray from a pathology record, which conflicts with the date (e.g., February 2) of the same diagnosis entry in oncology. In such a case, the record review / enhancement module 140 automatically resolves the conflict by determining that the diagnosis in oncology is associated with a higher priority value than the pathology record. Therefore, the record review / enhancement module 140 updates the registry record to indicate that the chest X-ray is dated February 2 instead of January 1.

[0080] In some implementations, using the registry field code for the diagnosis date, the record review / enhancement module 140 accesses a subject knowledge source to identify a source of information that may resolve the conflicting date. The identified source may include things such as a specific person, job function, or department (e.g., oncology, pathology, radiology, etc.). Using the identified source as a search guide, the record review / enhancement module 140 accesses a location knowledge source to identify an area in the hospital data repository 311 to search for information that may resolve the missing date, and collects data from the identified area. The record review / enhancement module 140 can analyze the collected data, including determining whether a first portion of the data or a second portion of the data is more reliable than the other portion, and based on the determination, automatically updating the diagnosis date in the registry field of the updated record 422.

[0081] The identified source may be automatically selected, for example, by an algorithm or by possible sources presented in a GUI, or selected by a user using input and user interface devices 312. In either case, the user may specify an area or department to search to refine the information. In some implementations, the record review / enhancement module 140 may invoke a scoring system that gives more or less weight to the accuracy of the data depending on the source of the data. The scoring system may include a weight attached to data retrieved from one source versus another, wherein the weight is proportional to the reliability of the data source.

[0082] In some embodiments, the record review / enhancement module 140 enhances the data included in the record with additional information. For example, the record review / enhancement module 140 evaluates the fields in the generated record and compares the record with the records of other patients. By identifying similarities between records, the record review / enhancement module 140 can supplement the information included in a given record. For example, if a specific MR image of a given patient identifies a target region of a tumor with a specific geometry and size, the record review / enhancement module 140 can identify a threshold number of other patient records that indicate similar target regions with similar geometry and size that were previously successfully treated. The record review / enhancement module 140 can obtain dose information for successfully treating such a target region and automatically recommend or fill in a field in the record that specifies the target dose for a given patient before the MR image is analyzed by a clinician to determine the dose information. The notification / recommendation module 141 can be used to provide a recommended dose. Specifically, the record review / enhancement module 140 is used to create an enhanced record based on information found in a verified registry record (available from the hospital registry 310) at one or more hospitals and patient data and protocol-related data from the hospital data repository 311.

[0083] Enhanced records provide physicians with more information about how patients or patient groups or demographics react to specific treatment patterns. Using this available information, physicians can better understand various aspects of treatment, such as the type of treatment, the drugs or equipment used, the specific duration of treatment and / or dosing regimen, and adjuvant therapy (e.g., for side effects) that may be factors affecting any adverse or favorable results. Enhanced records can additionally provide adverse or favorable instructions during treatment, which are specific or unique for the mode selected for treating the patient, and may have greater or lesser importance in the case of the behavior, lifestyle, or demographics of a given patient-patient relationship known by the physician. Using enhanced records, physicians can better infer and draw conclusions about whether the same scheme is desirable for his or her patient, whether any modifications are needed, and whether the treatment arrangement is appropriate in the case of the age, behavior, lifestyle, demographics, insurance resources, etc. of a given patient. Based on this information, physicians can better confirm, reject, or consider modifications to a planned or recommended scheme.

[0084] In some implementations, after the hospital registry 310 has collected a sufficient number of verified registry records 430 of current cancer patients or recently treated patients, the physician can then evaluate treatment options. For example, the physician can compare differences in treatment outcomes between patients with similar diagnoses and demographics based on different treatment modalities. In addition, for example, the physician can compare differences in treatment outcomes for patients receiving a particular treatment based on differences in patient diagnoses or demographics. With one, several, or preferably many such records, the physician has information to augment the treatment plan. Because all information is maintained in a structured format, the physician can quickly and efficiently select and view information that is only relevant to the specific conditions and characteristics of his or her patients and / or the planned treatment modality.

[0085] After the record viewing / enhancement module 140 confirms that the record is valid or contains valid information and / or enhances the information contained in the record, the record is marked as verified and stored in the registration form 310 and / or 313. The verified registration form record 430 stored in the registration form 310 and 313 provides useful information to the treating physician who selects the treatment plan for the patient when it is prepared in a timely manner. The verified registration form record 430 contains structured data so that several records can be easily searched according to various standards. Therefore, as long as the verified registration form record 430 can be updated and created in a timely manner, they can become a valuable resource for the physician. For example, the information from the verified registration form record 430 can be utilized to produce a more detailed or customized record, which can also include information on the treatment mode for the patient in addition to the required information of the state registration form.

[0086] The verified records 430 may be provided to the notification / recommendation module 141. The notification / recommendation module 141 processes the verified records to identify treatment information across populations and trends associated with the identified treatment information. The notification / recommendation module 141 uses the identified treatment information and trends across populations to generate recommendations for the patient based on the verified records 430 associated with the patient. In an embodiment, the notification / recommendation module 141 accesses the inter-hospital registry 314 to obtain verified records across multiple hospitals to identify such treatment information and trends across populations.

[0087] Figure 5 An example cancer registry record-generating workflow across multiple hospitals according to some examples of the present disclosure is shown. The inter-hospital registry 314 is configured to provide a resource that enables one or more hospitals to obtain registry record information from other hospitals to greatly increase the number of registry records that a physician may be able to access when selecting a regimen for a patient, as well as for generating automatic recommendations for treatment or notifying the physician of the number of registry records that are abnormal for a patient relative to a larger population. For example, by accessing the inter-hospital registry 314, a physician can obtain statistical information from these records in multiple hospitals and present it through a graphical user interface. The physician can inform his or her decision making by, for example, benchmarking a planned regimen against the regimen found in the registry records based on criteria such as morbidity, quality of life, etc.

[0088] Each of the N hospitals may locally execute the record viewing / enhancement module 140 to automatically generate records, create enhanced records, store the records in its respective hospital registry 310, and upload a copy to the inter-hospital registry 314. Each of the N hospitals may then access the information stored in the inter-hospital registry 314 to interrogate the information in the inter-hospital registry 314. The inter-hospital registry 314 may be accessible to the hospital through a program running locally on a WINDOWS or LINUX computing platform, for example, or remotely through a web browser.

[0089] Each of the N hospitals can execute one or more versions of the record viewing / enhancement module 140, each version having a different customization level available for recording. For example, basic functionality can include registration form record information provided by the record viewing / enhancement module 140, and additionally, functionality that allows recording and record-keeping of information for one or more types of treatment modes for patients. Additional customization levels can include dietary and health information to be included in enhanced records. Each of the N hospitals can create one or more different records that are the same as the records created by the record viewing / enhancement module 140 executed by one or more of the other hospitals, or differ by including more or less information about the patient, treatment mode, etc. Therefore, the inter-hospital registration form 314 can include two or more registration form record types that differ from each other in record content, but involve similar underlying conditions - for example, a particular type of diagnosed cancer.

[0090] A hospital may access an inter-hospital registry 314 or a record type for which the hospital does not execute a corresponding record review / enhancement module 140 and / or contribute data. Such a hospital may still use the inter-hospital registry 314 or such a record type to provide treatment decision support. Based on such access and / or use, or for other reasons, a hospital may decide to use the record review / enhancement module 140 to generate a particular registry record type of interest. The hospital may then contribute records of these corresponding registry types to the inter-hospital registry 314, thereby increasing the number and possible utility of such records.

[0091] Figure 6 A flowchart 600 is shown of a process of example operations for automatically generating a cancer registry record according to some examples of the present disclosure. The process may be performed by the treatment processing logic 120 and / or in conjunction with Figures 1 to 5 The operations of the process may be performed in parallel, sequentially or out of order, or may be skipped and omitted entirely.

[0092] At operation 610 , the treatment processing logic 120 obtains a plurality of rules defining cancer registry record generation from a patient health record.

[0093] At operation 620 , the treatment processing logic 120 obtains one or more electronic health records associated with the patient that include cancer-related treatment information.

[0094] At operation 630 , the treatment processing logic 120 processes the cancer-related treatment information in the one or more electronic health records to generate a cancer registry record for the patient representing a portion of the cancer-related treatment information.

[0095] At operation 640 , the treatment processing logic 120 automatically determines that the cancer registry record includes insufficient cancer-related treatment information.

[0096] At operation 650 , the treatment processing logic 120 automatically updates the cancer registry record to address insufficient cancer-related treatment information by evaluating the cancer-related treatment information against a plurality of rules.

[0097] Figure 7 An example graphical user interface 730 of a cancer registry record-generating workflow according to some examples of the present disclosure is shown. Figure 7 , shows a screenshot of a graphical user interface 730 generated by the treatment processing logic 120 for performing a comparison between a patient's data and a population's data. A user can select different data sources, categories, subcategories, and analysis types presented in the graphical user interface 730 for running a comparison and viewing the results using the user interface and input device 148.

[0098] Depicted is a first screen 731 that presents the user with a list of different types or categories of patient population data to select from. After selecting the population data of interest (e.g., ID="331"), the user is next presented with a second screen 732 to view a list of patients at the hospital and select from that list (e.g., patient "Smith Jane"). After selecting a patient and a population, the user may then be presented with a third screen 733 that presents a summary of the patient data found in the selected record 734 (e.g., categories A, B, C, and D) and a summary of the categories of population data 735 for the selected population (e.g., categories 1, 2, 3, and 4). The screen may also present: a Statistics section 739 having interactive options for selecting different statistics to run on the population data (e.g., first and second order statistics, and positive / negative correlations for different combinations of categories 1, 2, 3, and 4); an interactive first comparison type option 737 for finding patients from the population data that are most similar to the selected patient, and / or more specifically, for finding similarities to one or more of the A, B, C, and D categories in record 734; and an interactive second comparison type option 738. The graphical user interface 730 enables a given physician to view and / or generate statistics based on cancer registry records stored in one or more hospital registries and / or state registries.

[0099] The interactive first comparison type option 737 can instruct the device to determine which patients in the population data best match the patient across all relevant categories (e.g., using a default criterion, selecting one or more of A to D, or listing A to D in terms of priority—e.g., ranking the patients from the population that best match category A, then category B, etc.). The interactive second comparison type option 738 can instruct the device to perform a different statistical analysis comparing, for example, the patient's regimen and / or condition to the population data to determine if there is any anomalous data to consider. For example, the analysis might present to the user certain aspects of the patient's condition or treatment plan that are common or uncommon compared to the population data.

[0100] The graphical user interface 730 may present automatically generated treatment recommendations and / or notifications regarding conflicts or inconsistencies generated by the notification / recommendation module 141 of the treatment processing logic 120. The physician may interact with and respond to the recommendations and / or notifications to accept a given recommended treatment or to correct the fields of the corresponding record in which the conflict or inconsistency was found.

[0101] As previously discussed, various electronic computing systems or devices can implement one or more of the methods or functional operations discussed herein. In one or more embodiments, the radiation therapy processing computing system 110 can be configured, adapted, or used to control or operate an image-guided radiation therapy device 202, perform or implement a cancer registry record-generating workflow 130, perform or implement the operations of the flowchart 600, or perform any one or more of the other methods discussed herein (e.g., as part of the treatment processing logic 120 and the cancer registry record-generating workflow 130). In various embodiments, such an electronic computing system or device operates as a standalone device or can be connected (e.g., networked) to other machines. For example, such a computing system or device can operate in the capacity of a server or client machine in a server-client network environment, or operate as a peer machine in a peer-to-peer (or distributed) network environment. The features of the computing system or device can be implemented by a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a cellular phone, a web device, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be performed by the machine.

[0102] As also indicated above, the functionality discussed above may be implemented via instructions, logic, or other information storage on a machine-readable medium. Although a machine-readable medium may have been described in various examples as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database and / or associated cache memory and servers) storing one or more transient or non-transient instructions or data structures. The term "machine-readable medium" should also be considered to include any tangible medium that is capable of storing, encoding, or carrying any one or more transient or non-transient instructions for execution by a machine and causing the machine to perform the methods of the present disclosure, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such instructions.

[0103] The above detailed description includes reference to the accompanying drawings, which form a part of the detailed description. The accompanying drawings show specific embodiments in which the present disclosure can be practiced by way of illustration rather than by way of limitation. These embodiments are also referred to as "examples" in this article. Such examples may include elements other than those shown or described. However, the present disclosure is also intended to provide only examples of those elements shown or described. In addition, the present disclosure is also intended to use examples of any combination or arrangement of those elements (or one or more aspects of those elements) shown or described with respect to a specific example (or one or more aspects of a specific example) or with respect to other examples (or one or more aspects of other examples) shown or described in this article.

[0104] All publications, patents, and patent documents mentioned in this document are incorporated herein by reference in their entirety, as if individually incorporated by reference. If there are inconsistent usages between this document and those documents incorporated by reference, the usage in the incorporated references should be considered supplementary to that of this document; for conflicting inconsistencies, the usage in this document controls.

[0105] In this document, when introducing elements or aspects of the present disclosure or embodiments thereof, the terms "a", "an", "the", and "said" are used, as is common in patent documents, to include one or more than one of the elements, independent of any other instances or uses of "at least one" or "one or more". In this document, unless otherwise indicated, the term "or" is used to refer to a non-exclusive or, such that "A or B" includes "A but not B", "B but not A", and "A and B".

[0106] In the following claims, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Moreover, in the following claims, the terms "comprising," "including," and "having" are intended to be open-ended, e.g., meaning that there may be additional elements other than the listed elements. Moreover, in the following claims, the terms "first," "second," "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[0107] The present disclosure also relates to a computing system adapted, configured or operated to perform the operations herein. The system may be specially constructed for the desired purpose, or the system may include a general-purpose computer selectively started or reconfigured by a computer program (e.g., instruction, code, etc.) stored in a computer. Unless otherwise specified, the operation or execution order of the operations in the embodiments of the present disclosure shown and described herein is not necessary. That is, unless otherwise specified, operations may be performed in any order, and compared with the operations disclosed herein, the embodiments of the present disclosure may include more or less operations. For example, it is expected that the following falls within the scope of various aspects of the present disclosure: before another operation, simultaneously with another operation, or after another operation, a specific operation is run or performed.

[0108] In view of the above, it will be seen that the several objects of the present disclosure are achieved and other advantageous results are obtained. Having described aspects of the present disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the present disclosure as defined in the appended claims. Since various changes may be made to the above-described constructions, products and methods without departing from the scope of various aspects of the present disclosure, it is intended that all that is contained in the above description and shown in the accompanying drawings should be interpreted in an illustrative and not restrictive sense.

[0109] The examples described herein can be implemented in a variety of embodiments. For example, one embodiment includes a computing device that includes processing hardware (e.g., a processor or other processing circuit system) and memory hardware (e.g., a storage device or volatile memory), the memory hardware including transient or non-transient instructions implemented thereon, so that the instructions, when executed by the processing hardware, cause the computing device to implement, execute, or coordinate electronic operations for these technologies and system configurations and implement the modules or components described herein. Another embodiment discussed herein includes, for example, a computer program product that can be implemented by a machine-readable medium or other storage device, which provides transient or non-transient instructions for implementing, executing, or coordinating electronic operations for these technologies and system configurations. Another embodiment discussed herein includes a method that can operate on the processing hardware of a computing device to implement, execute, or coordinate electronic operations for these technologies and system configurations.

[0110] In other embodiments, the logic, commands, or transient or non-transient instructions implementing various aspects of the above-described electronic operations may be provided in a distributed or centralized computing system including any number of form factors for computing systems such as desktop computers or notebook personal computers, mobile devices such as tablet computers, netbooks, and smart phones, client terminals, and server-hosted machine instances. Another embodiment discussed herein includes incorporating the techniques discussed herein into other forms, including other forms of programming logic, hardware configurations, or dedicated components or modules, including devices having various devices that perform the functions of such techniques. Various algorithms for implementing the functions of such techniques may include sequences of some or all of the above-described electronic operations or other aspects depicted in the accompanying drawings and in the above specific embodiments.

[0111] As used herein, "module" should be considered to include units with different functions that can provide information to other modules and receive information from other modules. Therefore, the modules described can be considered to be coupled communicatively. The module can also initiate communication with an input device or an output device, and can operate resources (e.g., a collection of information, such as a database). The module can include hardware circuit systems, optical components, single or multi-processor circuits, memory circuits, software program modules and objects, firmware, and combinations thereof, depending on the specific implementation of various embodiments. The term "module" may include a recognizable portion of a code, data or computing object for implementing a specific function, operation, processing or process. As used herein, "module" or "component" includes software or source code files, or a software instruction set that is included or not included in a source code file and is present on a non-transient or transient storage medium. A module can exist as an independent program, or represent a program called by another program. In the sense that a module calls a component to perform one or more tasks, a "component" is a part of a "module".

[0112] As referred to herein, "structured data" includes information characterized by a high degree of organization, such that inclusion in a relational database (or spreadsheet) is seamless and can be easily searched by simple search techniques (e.g., Boolean word search). A verified registry record has fields occupied only by structured data. "Unstructured data" as used and interpreted includes data that cannot be seamlessly imported or stored in a relational database or spreadsheet. "Data repositories" include databases, data warehouses, data lakes, or a combination of these things. As used herein, "databases" should be considered to include centralized or distributed databases and include SQL databases. A database refers to a structured data set that can be accessed in a variety of different ways.

[0113] A "data lake" consists of a centralized repository where all structured and unstructured data is stored in one centralized location. Each type of data can be stored in its original format, with no fixed limit on account size, and without the need to structure, cleanse, or transform the data first. Data elements in a data lake can be given unique identifiers and tagged with an extended set of metadata tags. This provides a wide range of analytical capabilities. Unlike data found in a data warehouse or database, the data contained in a data lake is stored in its original format and transformed when the data or part of the data needs to be used. This way of storing and later using data can be called an extract-load-transform (ELT) strategy, similar to the "schema on read" technique. In contrast, a database or data warehouse may follow an extract-transform-load (ETL) strategy, where data is transformed before being stored in a database or data warehouse - this is called "schema on write", indicating that the schema - the structure of the data, must be defined before the data is loaded into the database or data warehouse. A data lake can coexist with a database and is accessed through access identifiers and metadata tags.

[0114] The above description is intended to be illustrative, rather than restrictive. For example, the above examples (or one or more aspects of the examples) can be used in groups with each other. In addition, without departing from the scope of the present disclosure, many modifications can be made to adapt specific situations or materials to the teachings of the present disclosure. Although the size, type and example parameters, functions and implementations of the materials described herein are intended to limit the parameters of the present disclosure, they are by no means restrictive, but exemplary embodiments. After reviewing the above description, many other embodiments will be apparent to those skilled in the art. Therefore, the scope of the present disclosure should be determined with reference to the attached claims together with the full scope of equivalents given by these claims.

[0115] In addition, in the above detailed description, various features may be grouped together to simplify the disclosure. This should not be interpreted as intending that unclaimed disclosed features are essential to any claim. Rather, the subject matter of the invention may lie in less than all features of a particular disclosed embodiment. Therefore, the appended claims are hereby incorporated into the detailed description, with each claim independently serving as a separate embodiment by itself.

Claims

1. A computer-implemented method for automatically generating a cancer registry record, the method comprising: obtaining, by the processor circuitry, a plurality of rules for defining cancer registry record generation based on a patient health record; obtaining, by the processor circuitry, one or more electronic health records associated with a patient including cancer-related treatment information; processing, by the processor circuitry, the cancer-related treatment information in the one or more electronic health records to generate a cancer registry record for the patient representing a portion of the cancer-related treatment information; determining, by the processor circuitry, that the cancer registry record includes insufficient cancer-related treatment information; as well as updating, by the processor circuitry, the cancer registry record by evaluating the cancer-related treatment information against the plurality of rules to address the insufficient cancer-related treatment information, Wherein, the method further comprises: determining, based on at least one of the rules, that data in a first field in the cancer registry record is inconsistent with data in a second field in the cancer registry record; accessing additional cancer-related treatment information from the one or more electronic health records to verify that the data in at least one of the first field and the second field is correct; and updating data in at least one of the first field and the second field based on the additional cancer-related treatment information, Wherein, accessing the additional cancer-related treatment information includes: retrieving at least one of the first information and the second information from the one or more electronic health records; determining that the first information or the second information corresponds to a first patient parameter; and Where the data in the first field indicates a second patient parameter, the data in the first field is adjusted to indicate the first patient parameter or the data in the first field is marked for review.

2. The method according to claim 1, wherein: Determining that the cancer registry record includes insufficient cancer-related treatment information includes automatically determining that the cancer registry record includes missing or incomplete information.

3. The method of claim 1 further comprising storing the cancer registry record in a government-mandated registry.

4. The method according to claim 1, wherein: Processing the cancer-related treatment information includes: performing natural language processing to generate data representing the cancer-related treatment information; identifying one or more cancer registry codes associated with the generated data based on the plurality of rules; and One or more fields in the cancer registry record are populated based on the identified one or more cancer registry codes.

5. The method according to claim 1, wherein: The one or more electronic health records are in a first format and the cancer registry record is in a second format.

6. The method according to claim 1, further comprising: responsive to processing the cancer-related treatment information, determining that the portion of the cancer-related treatment information corresponds to a cancer-related treatment or diagnosis; comparing the cancer-related treatment or diagnosis to a threshold value indicative of the frequency of the cancer-related treatment or diagnosis; as well as In response to determining that the cancer-related treatment or diagnosis exceeds the threshold, a notification is generated for a user to review the cancer registry record.

7. The method according to claim 1, wherein: The data in the first field indicates that the patient is female, and the data in the second field indicates a diagnosis of prostate cancer, wherein accessing the additional cancer-related treatment information comprises: retrieving at least one of medical imaging information and blood sample information from the one or more electronic health records; determining that the medical imaging information or the blood sample information corresponds to a male patient; and The data in the first field is adjusted to indicate that the patient is male, or the data in the first field is marked for review.

8. The method according to claim 1, further comprising: determining that a first type of data from the cancer-related treatment information corresponds to a first code for a field in the cancer registry record; determining that a second type of data from the cancer-related treatment information corresponds to a second code for a field in the cancer registry record; giving priority to the second type of data over the first type of data based on the rule; as well as Based on the priority, a field in the cancer registry record is populated with the second code instead of the first code.

9. The method according to claim 8, wherein: The first type of data represents results of a biopsy and the second type of data represents results from medical imaging.

10. The method according to claim 1, further comprising: identifying a set of cancer registry records associated with a plurality of cancer patients that are similar to the generated cancer registry record; identifying treatment regimens indicated in the collection of cancer registry records; as well as A recommended treatment regimen is generated for treating the patient based on the identified treatment regimen.

11. The method according to claim 1, wherein: Retrieving the one or more electronic health records from a first database managing cancer patients of a first hospital, the method further comprising: obtaining one or more additional electronic health records from a second database managing cancer patients of a second hospital; and The cancer registry record of a plurality of cancer registry records is stored in an inter-hospital registry containing data regarding a population of cancer patients.

12. A system for automatically generating cancer registry records, comprising: processing circuitry, the processing circuitry comprising at least one processor; as well as A storage medium comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising: Obtaining a plurality of rules generated based on a patient health record that qualifies a cancer registry record; obtaining one or more electronic health records associated with the patient that include cancer-related treatment information; processing the cancer-related treatment information in the one or more electronic health records to generate a cancer registry record for the patient representing a portion of the cancer-related treatment information; determining that the cancer registry record includes insufficient cancer-related treatment information; and updating the cancer registry record to address the insufficient cancer-related treatment information by evaluating the cancer-related treatment information against the plurality of rules, The operation further includes: determining, based on at least one of the rules, that data in a first field in the cancer registry record is inconsistent with data in a second field in the cancer registry record; accessing additional cancer-related treatment information from the one or more electronic health records to verify that the data in at least one of the first field and the second field is correct; and updating data in at least one of the first field and the second field based on the additional cancer-related treatment information, The operation of accessing the additional cancer-related treatment information includes the following operations: retrieving at least one of the first information and the second information from the one or more electronic health records; determining that the first information or the second information corresponds to a first patient parameter; and Where the data in the first field indicates a second patient parameter, the data in the first field is adjusted to indicate the first patient parameter or the data in the first field is marked for review.

13. The system according to claim 12, wherein: The operation of determining that the cancer registry record includes insufficient cancer-related treatment information includes an operation of automatically determining that the cancer registry record includes missing or incomplete information.

14. The system according to claim 12, wherein: The operations also include storing the cancer registry record in a government-mandated registry.

15. The system of claim 12, wherein: The operation of processing the cancer-related treatment information includes the following operations: performing natural language processing to generate data representing the cancer-related treatment information; identifying one or more cancer registry codes associated with the generated data based on the plurality of rules; as well as One or more fields in the cancer registry record are populated based on the identified one or more cancer registry codes.

16. The system of claim 12, wherein: The one or more electronic health records are in a first format and the cancer registry record is in a second format.

17. The system of claim 12, wherein: The operations also include: responsive to processing the cancer-related treatment information, determining that the portion of the cancer-related treatment information corresponds to a cancer-related treatment or diagnosis; comparing the cancer-related treatment or diagnosis to a threshold value indicative of the frequency of the cancer-related treatment or diagnosis; and In response to determining that the cancer-related treatment or diagnosis exceeds the threshold, a notification is generated for a user to review the cancer registry record.

18. The system of claim 12, wherein: The data in the first field indicates that the patient is female, and the data in the second field indicates a diagnosis of prostate cancer, wherein the operation of accessing the additional cancer-related treatment information comprises the following operations: retrieving at least one of medical imaging information and blood sample information from the one or more electronic health records; determining that the medical imaging information or the blood sample information corresponds to a male patient; and The data in the first field is adjusted to indicate that the patient is male, or the data in the first field is marked for review.

Citation Information

Patent Citations

  • Automated cancer registry record generation

    US20200294678A1

  • Computational medical treatment plan method and system with mass medical analysis

    CN105793852A

  • Precise medical platform for molecular diagnosis and treatment

    CN106650256A

  • Actionability framework for genomic biomarker

    US20150347699A1

  • Medical registry

    US20150363553A1