ELECTRONIC MEDICAL CHART

A handheld electronic device includes a network communication device for wirelessly receiving information regarding a plurality of tasks involved in a treatment process for a patient from a database, a processor for processing the information regarding the plurality of tasks, a housing containing the processor, wherein the housing is configured for handheld, and a screen configured to display a graphic using the information regarding the plurality of tasks, the graphic indicating the plurality of tasks on respective dates in a time line.

FIELD

This application relates generally to systems and methods for providing medical information.

BACKGROUND

Radiation therapy has been employed to treat tumorous tissue. In radiation therapy, a high energy beam is applied from an external source towards the patient. The external source, which may be rotating (as in the case for arc therapy), produces a collimated beam of radiation that is directed into the patient to the target site. The dose and placement of the dose must be accurately controlled to ensure that the tumor receives sufficient radiation, and that damage to the surrounding healthy tissue is minimized.

Implementation of a radiation therapy involves many different tasks performed by different professionals, including doctors, nurses, technicians, treatment planner, etc. By means of non-limiting examples, such tasks may include consultation by a doctor, verification of insurance by a nurse, obtaining imaging (e.g., CT imaging, x-ray, MRI, PET, SPECT, etc.) by a technician, processing of images by another technician, contouring of organ structures by a doctor/technician, treatment planning by a doctor/technician, treatment preparation by nurse(s) and/or technician(s), treatment execution by a doctor/technician, follow-up by a doctor, and pain management by a nurse/doctor, etc.

The different tasks associated with a radiation therapy may be performed at different locations in different facilities, and may be required to be performed by certain due dates before another task may begin. Sometimes, if a person fails to perform a task, others may be unable to perform their tasks because the performance of their tasks may depend from a result of an earlier task. Also, different facilities that are involved in implementing a radiation therapy may not have access to the same information.

Applicant of the subject application determines that it would be desirable to provide a new system and method for allowing individual(s) to access medical information regarding a medical process that involves radiation.

SUMMARY

In accordance with some embodiments, a handheld electronic device includes a network communication device for wirelessly receiving information regarding a plurality of tasks involved in a treatment process for a patient from a database, a processor for processing the information regarding the plurality of tasks, a housing containing the processor, wherein the housing is configured for handheld, and a screen configured to display a graphic using the information regarding the plurality of tasks, the graphic indicating the plurality of tasks on respective dates in a time line.

In accordance with other embodiments, a method performed by a handheld electronic device includes wirelessly receiving information regarding a plurality of tasks involved in a treatment process for a patient from a database, processing the information regarding the plurality of tasks using a processor, and displaying on a screen a graphic using the information regarding the plurality of tasks, the graphic indicating the plurality of tasks on respective dates in a time line.

In accordance with other embodiments, a computer product includes a non-transitory medium storing a set of instructions, an execution of which causes a process to be performed by a handheld electronic device, the process comprising wirelessly receiving information regarding a plurality of tasks involved in a treatment process for a patient from a database, processing the information regarding the plurality of tasks, and displaying on a screen a graphic using the information regarding the plurality of tasks, the graphic indicating the plurality of tasks on respective dates in a time line.

In accordance with other embodiments, a system includes a processor configured to receive information regarding a plurality of tasks involved in a treatment process for a patient, the tasks associated with respective dates, and a non-transitory medium configured to store the information regarding the plurality of tasks, and the dates, wherein the processor is also configured to receive a request from a handheld device, retrieve the stored information regarding the plurality of tasks and the dates from the non-transitory medium in response to the request, and pass the information regarding the plurality of tasks and the dates downstream for transmission to the handheld device.

In accordance with other embodiments, a method for providing medical information includes receiving information regarding a plurality of tasks involved in a treatment process, the tasks associated with respective dates, storing the information regarding the plurality of tasks and the dates in a non-transitory medium, receiving a request from a handheld device, retrieving the stored information regarding the plurality of tasks and the dates from the non-transitory medium in response to the request, wherein the act of retrieving is performed using a processor, and passing the information regarding the plurality of tasks and the dates downstream for transmission to the handheld device.

In accordance with other embodiments, a computer product includes a non-transitory medium storing a set of instructions, an execution of which causes a process to be performed, the process comprising receive information regarding a plurality of tasks involved in a treatment process, the tasks associated with respective dates, storing the information regarding the plurality of tasks and the dates, receiving a request from a handheld device, retrieving the stored information regarding the plurality of tasks and the dates in response to the request, and passing the information regarding the plurality of tasks and the dates downstream for transmission to the handheld device.

Other and further aspects and features will be evident from reading the following detailed description of the embodiments.

DESCRIPTION OF THE EMBODIMENTS

FIG. 1illustrates a system2for communicating medical information in accordance with some embodiments. The system2includes a handheld electronic device10and a database14in communication with the handheld electronic device10. The device10includes a network communication device12configured to wirelessly receive medical information (e.g., information regarding a radiation process) from a database14, a processor16configured to process the medical information, a housing18containing the processor16, and a screen20configured to display the medical information. In other embodiments, the device10may receive the medical information by receiving input from a user of the device10. In such cases, the processor16may process the information, and the network communication device12may then transmit the medical information to the database14for storage. The housing16is configured for handheld, so that a user of the device10may carry the device10from place to place.

In some embodiments, the device10may be a hand-held communication device, such as an iPad, an emailing device (e.g., a Blackberry), or a phone (e.g., iPhone). In other embodiments, the device10may be a computer, such as a laptop or a desktop.

In the illustrated embodiments, the database14includes a processor56, and a non-transitory medium58for storing medical information (e.g., information regarding a radiation process). In some embodiments, the database14may be implemented using one or more computers, which may include respective processors56. Thus, as used in this specification, the term “processor” or similar terms may refer to one or more processors. Also, in some embodiments, the non-transitory medium58may include one or more storage devices, which may be located together (e.g., in a server room), or located in different places (e.g., in different buildings, different cities, etc.). In one implementation, the database14may include a plurality of computers that are communicatively linked together in a network.

As shown in the figure, the database14may be in communication with a plurality of nodes60a-60c. Although three nodes60a-60care shown, in other embodiments, there may be more than three nodes, or less than three nodes (e.g., one node). Each node60may be a source of information. By means of non-limiting examples, each node60may be a communication device (e.g., a computer, an iPad, a Blackberry, etc.) at a hospital, at a nurse station, at a doctor's office, at an imaging center, etc. The database14is configured to receive various medical information from different nodes60, process the medical information, and store the medical information in the non-transitory medium58. During use, the database14receives a request from the device10, retrieves the medical information from the non-transitory medium58in response to the request, and transmits the retrieved medical information to the device10.

Although one device10is shown in the figure, in other embodiments, there may be more than one device10in communication with the database14. For example, there may be one device10being used by a nurse, another device10being used by a doctor, and another device10being used by an imaging technician. Also, in other embodiments, one or more of the nodes60may be respective device(s)10. In some embodiments, there may be one or more devices10at a nurse station for use by different nurses, one or more devices10at a doctor's office for use by different doctors, one or more devices10at a lab center for use by different lab technicians, and/or one or more devices10at an imaging center for use by different operators. Also, in some embodiments, these professionals may participate in a treatment process (e.g., a radiotherapy process) to treat a patient. In such cases, these professionals may use the devices10to enter medical information regarding the patient for storage at the database14, so that different professionals who participate in the treatment process may retrieve the medical information from the database14using their devices10. All of the input may be stored in a database. In some embodiments, the database may be configured to check for conflicting inputs, and may transmit a warning signal if there is any conflict between inputs. In other embodiments, each person is allowed to enter only certain input so that no two persons will be allowed to enter different inputs for a same field.

In the illustrated embodiments, the device10is configured (e.g., programmed, built, etc.) to implement a user interface for presenting medical information to a user of the device10, and/or receiving medical information from the user of the device10. As used in this specification, the term “user interface” may refer to one or more graphics configured to provide information to a user, and/or any component (e.g., a screen) for providing such graphics, wherein such graphics may be displayed in a screen (e.g., as one or more pages) or may be stored in a non-transitory medium as data.

In some embodiments, the device10may be an iPad that is configured to display a user interface for presenting and/or receiving medical information.FIG. 2Aillustrates an example of a user interface200displayed in a screen202of an iPad device10for presenting medical information in accordance with some embodiments. The user interface200includes a display area204for displaying a name206of a patient, a patient identification208, and a picture209of the patient. The user interface200is configured for allowing a user (e.g., a nurse, a doctor, etc.) to input information regarding a patient. In the illustrated embodiments, the user interface200includes a keyboard234for allowing a user to input information, a field236for allowing a user to enter a weight of a patient (e.g., using the keyboard234), and a field238for allowing a user to enter a pain level being experienced by a patient (e.g., using the keyboard234). For example, the pain level may be due to a result of a radiation treatment. In other embodiments, the user interface200may include other fields (e.g., different fields for patient's age, patient's address, patient's symptoms, patient's medical history, physical examination notes, etc.). In some embodiments, after the information has been entered by a user of the device10, the device10then transmits the information to the database14for storage at the database14.

In the illustrated embodiments, the user interface200also includes a plurality of tabs220. Tab1corresponds with the display shown inFIG. 2A, such that when a user selects “Tab1” (e.g., by touching the portion of the screen202at which “Tab1” is displayed), the display shown inFIG. 2Awill be displayed to the user. The user may select any of other tabs, in which case, the device10will display different screen displays for presenting different information to the user. In some embodiments, the name206, patient identification208, and the picture209of the patient are displayed to the user of the device10regardless of which of the tabs220has been selected by the user. In other embodiments, the name206, patient identification208, and the picture209of the patient are displayed when the user selects only certain one(s) of the tabs220.

FIG. 2Billustrates another user interface200configured for allowing a user (e.g., a nurse, a doctor, etc.) to input information regarding a patient in accordance with other embodiments. In some embodiments, the user interface200ofFIG. 2Bmay be displayed for use during an initial screening process. The user interface200includes a field236for allowing a user of the device10to input the weight of the patient, a field238(in the form of a selectable scale) for allowing the user to enter a pain level experienced by the patient, and a field240for allowing the user to enter the pain location. The user interface200also includes multiple fields to input vital info of the patient that includes but not limited to a field250for allowing the user to input a temperature of the patient, a field252for allowing the user to input a pulse of the patient, a field254for allowing the user to input a respiratory rate of the patient, a field256for allowing the user to input a blood pressure of the patient, and a field258for allowing the user to input a height of the patient. In some embodiments, one or more of the information for the various fields may be input using a keyboard270, which may be implemented using a touch screen in the embodiments in which the device is an iPad (FIG. 2C). The user interface200also includes a list260of questions with checkable answers “Yes” and “No” for allowing the user of the device10to complete the questions based on responses from the patient. This allows healthcare professional to intake medical history of the patient or update the history. The user interface200further includes a field262for allowing the user of the device10who is doing the screening to enter his/her name, and a field264for allowing the date of the screening to be entered. The user interface200also includes a field266for allowing another user to verify the screening, and a field268for allowing the date of the verification to be entered.

In some embodiments, after the various inputs have been entered using the user interface200, the processor16of the device10then processes the information, and causes the information to be transmitted from the device10to the database14for storage at the database14. The stored information may then be retrieved later (e.g., by the user of the device10, and/or by another user of another device10, etc.). In some embodiments, the database14may be at a secure location, and the patient information may be imported/downloaded from the secure location.

In some embodiments, the device10may also provide a messaging functionality for the user of the device10. For example, in some embodiments, the user interface200may allow a pop up frame (message field)280to be displayed, so that the user of the device10may type a message (e.g., using the keyboard270), and may send the message to another person (FIG. 2D). In some embodiments, the message field280may be brought up by the user of the device10(e.g., by selecting an icon displayed on the screen202) any time, regardless of which of the tabs220that the user has been selected.

In some embodiments, the device10may be used to retrieve and display information regarding a patient.FIG. 3Aillustrates a user interface300displayed in the screen202for presenting medical information regarding a patient in accordance with some embodiments. The user interface300includes the plurality of tabs220. In the illustrated embodiments, the tab220for “Summary” is selected, thereby causing patient summary to be displayed in the screen202of the device10. In the example shown, the patient summary includes diagnosis information302, dose summary304, chemotherapy summary306, clinical alerts308, patient alerts310, and information regarding current medications312. The diagnosis information302includes a diagnosis of the patient. The dose summary304includes information regarding reference points, planned dose, and delivered dose. The chemotherapy summary306includes information regarding a chemotherapy plan, a current phase of the chemotherapy, and a diagnosis of the medical condition to which the chemotherapy is designed to treat. The clinical alerts308alert the medical professionals certain medical condition of the patient. For example, if the patient is allergic to certain medication, such information would be provided under the clinical alerts308. The patient alerts310alert certain medical condition of the patient. For example, if the patient has lost a significant amount of weight, then such information would be provided under patient alerts310. The current medications312provides a list of medicine which has been prescribed for the patient.

One or more of the information provided in the user interface300may be retrieved by the database14in response to a request transmitted from the device10. The database14then transmits the retrieved information and sends the information to the device10for display on the screen202.

In some embodiments, one or more of the information shown in the user interface300may be selectable. For example, in some embodiments, a user of the device10may select the information under diagnosis302. In such cases, the user interface300may display further information regarding the diagnosis302.

It should be noted that the patient summary should not be limited to the example described, and that the patient summary may provide other information. For example, in other embodiments, the user interface300may provide information regarding current fraction330of a radiotherapy for a patient and projected completion date332of the radiotherapy (FIG. 3B). Also, as shown inFIG. 3B, in some embodiments, the user interface300may provide blood test result340, biopsy result342, and scan result344. One or more of the information provided in the user interface300may be retrieved by the database14in response to a request transmitted from the device10. The database14then transmits the retrieved information and sends the information to the device10for display on the screen202. In some embodiments, one or more of the information shown in the user interface300may be selectable. For example, in some embodiments, a user of the device10may select a “Test Result” displayed on the screen202. In such cases, the user interface300may display a test results page (FIG. 3C), showing information regarding different test results (such as test results from a lab, test results from surgical department, test results from pathology, test results from radiology, etc.). The user interface300may also display the dates that correspond with the respective test results. In the illustrated embodiments, the “test result” page is associated with one of the tabs220that is labeled “Test Results”. That means the user may optionally access this page by selecting the tab220for the “Test Results” or by selecting the “Test Result” test in the display page shown inFIG. 3B. In other embodiments, the “Test Results” page is accessed as a sub-page. In such cases, there will be no tab220for the “Test Results”, and the user can access such page as a sub-page under one of the tabs220(e.g., the “Patient Summary” tab220inFIG. 3A).

In some embodiments, detail information regarding one of the tests may be retrieved by selecting one of the test results (e.g., the test results shown inFIG. 3B, orFIG. 3C). When the user selects one of the test results, the device10sends a request to the database14in response to the selection. The database14receives the request, and retrieves the requested test result from its medium. The database14then transmits the test result information to the device10for display on the screen202.FIG. 3Dillustrates an example of a pathology test result350that may be displayed on the screen202of the device10. In some embodiments, if the device10is being used by a doctor, the doctor may adjust a treatment plan based on the information he/she sees in the pathology test result350. For example, in some embodiments, the device10may provide a user interface for allowing a doctor to make changes to a treatment plan. Such feature will be described in further detail below.

In other embodiments, the user interface may provide “Radiotherapy” as one of the tabs220.FIG. 4illustrates a user interface400that provides a “Radiotherapy” tab220. When the user of the device10selects such tab220, the device displays the information shown in the figure. In the illustrated embodiments, the user interface400provides a graph402that indicates different tasks404a-404kof a treatment process for a patient at different respective dates406a-406k. As shown in the figure, the tasks404a-404kof the treatment process are arranged in a time line. This allows a user of the device10to see which task(s) has been completed and which task(s) is pending, as well as their temporal relationship with respect to each other. In the illustrated embodiments, tasks404a-404gare represented as solid dots, indicating that the tasks404a-404ghave been completed. Tasks404h-404kare pending, and are therefore represented by different graphics (e.g., open dots). When a task404has been completed, and has been signed off, then the database14will store the completed task404and its associated status “completed” in its medium. During use, when the device10requests for a radiotherapy summary from the database14, the database14then retrieves the tasks of the radiotherapy, their respective dates, and their respective status (e.g., pending, completed, etc.), and transmits these information to the device10for display in the graph402.

In some embodiments, any of the tasks404a-404kmay be selected by the user of the device10. For example, in some embodiments, when the task404cis selected, the user interface400then displays additional information (e.g., more detailed information) regarding the selected task404c. In some embodiments, such additional information may be retrieved from a medium by the database14, which transmits such information to the device10for display on the screen202.

In the illustrated embodiments, the different tasks404a-404kare organized in different categories, “Prescription”, “Treatment”, “Imaging”, “Trends”. The tasks under the “Prescription” category are prescription-related tasks, such as dose prescription, etc. The tasks under the “Treatment” category are treatment-related tasks, such as treatment planning, patient setup, treatment execution to deliver radiation dose, etc. The tasks under the “Imaging” category are imaging-related tasks, such as x-ray procedure(s), CT procedure(s), PET-CT procedure(s), imaging processing procedure(s), target segmentations, etc. These tasks may be considered to be part of the overall treatment process because imaging may be needed for the treatment process (e.g., for identifying target(s), treatment planning, patient setup, target position verification, dose verification, etc.). The tasks under “Trends” are tasks for capturing trends, such as changes in the source-to-skin distances, patient weight, etc., over time. For example, a patient, while on treatment, may lose weight. The weight loss is gradual but by trending it, the user can determine if any intervention is required before the patient loses too much weight. The same goes for source-to-skin distances. If the source-to-skin distances change too much from what was planned, intervention may be required. Trending data that are involved in a treatment process allows the user to be proactive in the intervention. In other embodiments, the graph402may not provide the tasks404a-404kunder different categories. Instead, each task404may have a description that describes the nature of the task. Also, in other embodiments, each task404may be represented by a text box that includes different information, such as task description, person assigned to perform the task, location of the task, etc.

The chart402displaying various tasks404for a treatment process for a patient is beneficial because it allows different professionals (e.g., doctors, imaging technicians, nurses, etc.) who participate in the treatment process to conveniently see how the different tasks are related to each other. For example, the person responsible for task404hwill see from the chart402that the previous task404ghas been completed, and therefore the task404his a pending task that needs to be completed before the next task404ican begin.

In some embodiments, the user interface may provide a “scheduling” tab, which allows a user of the device10to look up scheduling information, and/or to perform scheduling tasks.FIG. 5Aillustrates a user interface500for presenting scheduling information in accordance with some embodiments. The user interface500includes a calendar502with dates that are individually selectable. The user interface500also includes a list504of activities that have been scheduled for a particular user506(e.g., a nurse, a doctor, etc.) in a particular day (which is October 25 in the example shown) selected from the calendar502. The user interface500allows the user to see different activities that have been scheduled in different dates. Each activity in the list504may be selectable (e.g., using the “Info” button507) for allowing the user to see additional information regarding the activity. Also, the user of the device10may select the “Notes” button508for entering notes for different activities in the list504. For examples, in some embodiments, when the button508is selected, the user interface500provides a text field and a keyboard for allowing a user of the device10to enter notes for a certain task504(FIG. 5B).

In some embodiments, the activities in the list504(as well as their associated information, such as dates, detail information regarding the activities, notes, etc.) may be stored in the database14. In such cases, when the user of the device accesses the scheduling tab220at the device10, the device10then transmits a request to the database14. The database14retrieves the scheduling information from its medium, and transmits the retrieved scheduling information to the device10for display on the screen202.

Also, in some embodiments, the user of the device10may change an activity displayed in the list504using the device10. For example, in some embodiments, the user may delete an activity in the list504, enter a new activity in the list504, or move an activity in the list504from one time slot to another. After the user has used the device10to make change to the list504, the device10then transmits the information regarding the change to the database14. The database14then updates the list of activities stored in its medium based on the change made by the user. In some embodiments, the updates may be automatically propagated to one or more devices10. In other embodiments, the updates may be propagated to a device10in response to a user of the device10executing certain application, or in response to a user logging into the database14using the device10. In further embodiments, the updates may be sent from the database14in response to a user of the device10requesting for the scheduling information. For example, when the user of the device10requests for the scheduling information, the database14will retrieve the updated list of activities, and transmits the information to the device10for display on the screen202.

In some embodiments, the user interface may be configured to allow certain tasks be performed based on a level of authorization for a user of the device10. For example, in some embodiments, a nurse and a doctor may have different levels of authorization. In such cases, the user interface may be configured to allow certain tasks/changes be made by a doctor (and not by a nurse). Also, the user interface may be configured to allow certain tasks/changes be made by both a doctor and a nurse, and other tasks/changes be made only by a nurse (and not by a doctor). This feature may also be applied for other input fields in the user interface. For example, in some embodiments, the user interface may be configured to allow certain input field(s) be used by a doctor (and not by a nurse). Also, the user interface may be configured to allow certain input field(s) be used by both a doctor and a nurse, and other input field(s) be used only by a nurse (and not by a doctor).

It should be noted that the configuration of the scheduling tab is not limited to the example described, and that the scheduling tab may have different configurations in different embodiments.FIG. 5Cillustrates a variation of the scheduling tab for the user interface500in accordance with other embodiments. The user interface500includes a list504of activities that have been scheduled for a particular user506(e.g., a nurse, a doctor, etc.) in a particular day (which is Nov. 16, 2010 in the example shown). The user of the device10may optionally view activities in a week, or in a month, by selecting the “This Week” tab or the “This Month” tab above. In some embodiments, each item in the list504may be selectable, in which case, when the user selects the item, the user interface500will display further information regarding the selected item.FIG. 5Dillustrates an example in which the item for “Montgomery, Susan” is selected. When this happens, the device10sends a request to the database14, which then retrieves additional information regarding the selected item. The database14then transmits the retrieved information to the device10for display on the screen202. In the illustrated example, the additional information is displayed in a frame520, which includes a patient name, date of birth, diagnosis for the patient, patient alerts, clinical alerts, prescribed dose information, delivered dose information, current fraction information, and projected completion date of the radiotherapy.

In other embodiments, instead of accessing the scheduling page using a tab220, the scheduling information may be accessed as a sub-page. For example, as shown inFIG. 5E, in other embodiments, the user interface500may provide a page for allowing a user of the device10to select a “Schedule” button542. When such button542is selected, the user interface500may then display a scheduling page (such as the example shown inFIG. 5A or 5C). As shownFIG. 5E, the user interface500may also include other buttons, such as the “Tasks” button520, the “Patients” button544, and the “Contacts” button546. When the “Tasks” button520is selected, the user interface500displays a list550of tasks that have been scheduled for the particular user506. When the “Patients” button544is selected, the user interface500then displays a list560of patients who are being treated by the particular user506(FIG. 5F). When the “Contacts” button546is selected, the user interface500then displays a list of contacts on the screen202. In some embodiments, the user of the device10may select one of the contacts on the screen202, and send a message (e.g., an email) to the selected contact.

Returning toFIG. 5AandFIG. 5E, the user interface500includes a contact button546, which allows a user of the device10to send correspondence to another person. For example, in some embodiments, the user may be a doctor, who is performing certain task(s)504/550. The doctor, while or after performing the task(s), may want to send a correspondence to a colleague. The doctor may then select the button546, in which cases, the user interface500may provide a text field and a keyboard for allowing the user to type and send a message (FIG. 5G).

In other embodiments, the device10may provide a user interface for allowing a user of the device10to view medical images for a patient. For example, as shown inFIG. 6A, the device10may display a user interface500for presenting scheduling information on the screen202. The scheduling information includes various activities assigned for a given user on a certain day. The user interface500is similar to that discussed with reference toFIG. 5. As shown in the example, the list of activities assigned may include an image review task580. During use, the user may select the image review task580in the schedule page. Alternatively, the user may select one of the tabs220for retrieving medical images. In response to the user's selection, the device10sends a request to the database14to request for image information. The database14retrieves the image information from its medium, and sends the image information to the device10. The processor in the device10processes the image information, and displays images using the image information on the screen202. As shown inFIG. 6B, the device10may display a user interface600for presenting the images. The user interface600includes a display area604for displaying the name206of a patient, a patient identification208, the picture209of the patient, and medical information610for the patient. In the illustrated example, the medical information610includes a dose summary612for the patient, and anatomical images614(e.g., x-rays, CT images, PET images, SPECT images, PET-CT images, MRI images, etc.) of the patient. In other examples, the medical information610may include other types of information.FIG. 6Cillustrates another example of the user interface600, which presents different medical images614of the patient. The user interface600may optionally include one or more controls for allowing a user of the device10to adjust a brightness of an image, to adjust a contrast of an image, to select one of a plurality of images from a set of available images, to zoom in or out of an image, and/or to move one or more images within the screen202.

In other embodiments, the device10may provide a user interface for allowing different users to view and/or complete a treatment worksheet.FIG. 7Aillustrates an examine of a user interface700displaying a treatment worksheet in accordance with some embodiments. The user interface700includes a button702for allowing a user to retrieve a screening summary. When the button702is selected by the user of the device10, the device10sends a request to the database14. In response to the request, the database14retrieves the screening summary stored in its medium, and transmits the retrieved screening summary704to the device10for display on the screen202(FIG. 7B).

Returning toFIG. 7A, the user interface700also includes a checklist710for allowing a user to see various items related to a treatment process. A checklist is a “to do” list for the user much like any checklist (e.g. airplane pilot pre-flight checklist). In some embodiments, the checklist710includes items that the user should check or do before delivering the treatment. In some cases, the checklist710may be considered a safety feature that provides a safety function. In the illustrated embodiments, the various items in the checklist710include weekly port films720, treatment parameters722, dose delivery724, patient setup726, dosimetry728, and blood counts730. Weekly port films720are films or images (e.g., x-ray images) taken through the actual treatment fields of the patient in treatment position. This is used to verify patient position as well as a record of where in the body the patient was treated. In some embodiments, if the port films have been received and/or processed, then the item for the weekly port films720may be checked off. Treatment parameters722include one or more machine settings that are required to deliver the patient's treatment. Examples of parameters include field size, gantry angle, collimator angle, couch angle, and accessories to modify the treatment beam. In some embodiments, if the treatment parameters have been determined, then the item for the treatment parameters722may be checked off. Dose delivery724includes dose delivery information. For examples, it may be an amount of dose to set the machine in order to deliver the treatment, dose energy, or combination of both, etc. In some embodiments, when dose delivery information have been obtained, then the item for the dose delivery724may be checked off. Patient setup726is for checking items involved in a setup. For examples, it may include confirming the position the patient is in for treatment delivery (e.g. lying on the back with the head towards the machine, etc.), checking items in set up instructions, etc. In some embodiments, a patient setup may involve using an immobilization device to keep the patient from moving. Dosimetry728may include any pre-treatment dose measurements that were taken to ensure that the correct dose is going to be delivered to the patient. It may also include treatment plan information, such as dose distributions and information about the doses the target and critical structures would receive. In some embodiments, when the dosimetry information has been obtained and/or confirmed, then the item for the dosimetry728may be checked off. Blood counts730may include hemoglobin, white cell, and platelet counts. If a patient is undergoing chemotherapy as well as radiation, his/her blood counts need to be closely monitored as these numbers may drop to dangerous levels. In addition, treating certain areas of the body with radiation alone can cause blood counts to drop. In some embodiments, when the blood count information has been obtained and/or confirmed that it is at acceptable level(s), then the item for blood counts730may be checked off.

The user interface700also includes a checkbox for “Continue RT”740. When the user checks the box740, that means the radiotherapy is to be continued. The user interface700also includes a check box and a field742for allowing a user (e.g., a doctor) to prescribe how many days to break before the treatment is to be continued. As shown in the figure, the user interface700further includes a field744for allowing a user to input and/or review notes regarding a treatment for a patient.

In some embodiments, the user interface700may also allow a user (e.g., a doctor) to make other orders. For example, as shown inFIG. 7C, in some embodiments, the user interface700may display a checkbox750for allowing a user to order a holding of treatment for a prescribed time (e.g., 2 weeks), a checkbox752for allowing a user to order a blood test to determine blood count, a checkbox754for allowing a user to order a chemotherapy, a checkbox756for allowing a user to order a diagnostic CT imaging, a checkbox758for allowing a user to order a MRI imaging, and a checkbox760for allowing a user to order a PET scan. In some embodiments, after an order has been completed (e.g., by checking one or more of the boxes750-760), the device10may transmit the information regarding the order to the database14for storage. The database14stores the order information in its medium so that the information may be retrieved later (e.g., by the user of the device10or another device10). Also, in some embodiments, the database14may be configured to automatically change one or more scheduling for one or more users based on the received order information. For example, if the user has prescribed that a CT imaging be performed (e.g., by checking box756), the database14may then automatically insert an imaging task into a schedule of a CT technician. In some embodiments, certain field(s) in the user interface is allowed to be accessed only by user(s) with certain privilege(s). For example, in some embodiments, the box756is not allowed to be checked by a nurse, and is allowed to be checked only by a doctor. In some embodiments, the database14may automatically suggest a date for the imaging task, subjecting to the technician accepting the date. In other embodiments, instead of automatically inserting an imaging task into the CT technician's schedule, the database14may automatically sends a message to the CT technician, requesting the CT technician to enter a CT imaging task into his/her schedule. In the illustrated embodiments, the user interface700further includes a field762for allowing a user (e.g., a radiation oncologist) to enter his/her name, and a field764for allowing another user to sign off on the order.

In some embodiments, when a user of the device10orders for an imaging to be performed (e.g., by checking one of the boxes756,758,760), the device10may present a user interface for allowing the user to select which part of the patient is to be imaged.FIG. 7Dillustrates a user interface780for allowing a user of the device10to select a body part for imaging. The user interface780includes a diagram782of a patient, and a box784. The box784is selectively moveable relative to the patient diagram782so that a user can select a certain body part of the patient using the box784for imaging. In some embodiments, the box784may also be made bigger or smaller. Furthermore, in some embodiments, the patient diagram782may be moved, turned, and/or scaled up/down (e.g., using the touch screen of the device10in the embodiments in which the device10is an iPad). In other embodiments, the user interface780may be used by a user of the device10to select which body part of the patient for treatment. For example, the box784may be dragged to the part of the patient diagram782where the liver is located, thereby prescribing a radiotherapy be performed on the liver.

In some embodiments, after a certain body part has been selected for imaging and/or treatment using the user interface780, the device10then sends the prescription to the database14for storage. The database14may later retrieve the prescription information in response to a request by a user of the device10or another device10, and may send the prescription information to the device10for display on the screen202. Also, in some embodiments, the database14may automatically create or update a task (e.g., an imaging task and/or a treatment task) based on the prescription information. For example, in some embodiments, a previous imaging task for a CT technician may prescribe a certain region of a patient to be imaged. A doctor may decide to make the scanning region bigger using the user interface780. In such cases, when the database14receives the prescription from the doctor, the database14may automatically update the previously assigned imaging task for the CT technician, so that when the CT technician performs the imaging task, the CT technician will have the updated requested information. Similar updates may be automatically performed by the database14to update one or more treatment tasks.

Also, in some embodiments, the user interface700may provide a treatment overview for allowing a user to sign off on certain completed tasks.FIG. 7Eillustrates a worksheet790presented by the user interface700that includes different tasks792. Each task792has a corresponding checkbox794which allows a user to check-off on a completed task. Once a task792has been selected by the user as “completed” (e.g., by checking the box794), and the user signing off the task792has e-signed the signature block796, the device10then sends the signed-off information to the database14. The database14, upon receiving the signed-off information, will automatically update certain task(s) in its medium to have a “completed” status.

In some embodiments, the device10may present different worksheets790for different users. For example, a user who is a nurse may receive a worksheet790with task items that are different from that for a user who is a doctor. In one implementation, before the user of the device10is allowed to access information from the database14, the user may be required to input a login name and password using the device10. The device10then transmits the entered login name and password to the database14. The database14will verify the login name and password by looking up the stored name and corresponding password stored in its medium. Once the user has been verified, the database14then presents certain information to the user based on the user's profession. For example, with respect to the worksheet790inFIG. 7E, the database14may provide different task items in the worksheet790for display by the device10, depending on whether the user is a nurse, a doctor, an imaging technician, etc.

It should be noted that the feature regarding the database14providing different information based on the user's profession is not limited to the display shown inFIG. 7E, and that such feature may be used to provide different information in different displays (such as any of the ones described previously with reference toFIGS. 2-6, or any of the ones described herein after). Such feature allows different users in different professions to have different level of access for information stored in the database14. For example, a nurse may be allowed to view treatment information, but not to make prescription. As another example, an imaging technician may be allowed to perform image review, and input notes regarding the images being reviewed, but he/she is not allowed to enter notes regarding a treatment procedure.

In other embodiments, the device10may provide a user interface for presenting other types of medical information. For example, in other embodiments, the device10may provide information related to a chemotherapy for a patient, such as lab results showing blood count.

FIG. 8Aillustrates another user interface800in accordance with some embodiments. The user interface800may be displayed on the screen202of the device10in response to a user selecting one of the tabs220. The user interface800is configured for presenting lab results844to a user (e.g., a nurse, a doctor, etc.). In the illustrated example, the lab results844may include blood count information. In some cases, the lab results844may indicate that a white blood cell count is too low. In such cases, the user of the device10may use the device10to send an alert to a doctor (or the device10/database14may be configured to automatically send an alert to a doctor). The doctor, upon receiving the alert, may then send an instruction to stop a treatment (e.g., chemotherapy treatment) for the patient. In some embodiments, the doctor may be using another device10, which allows the doctor to send the instruction to stop the treatment by using an input at the device10. As shown in the figure, the user interface800may also present a graph846showing a trend of lab results. For example, the graph846may show the white blood cell counts measured at different dates. In some embodiments, one or more of the information being presented at the user interface800may be transmitted from the database14to the device10in response to a request transmitted from the device10to the database14(wherein such request may be created by a user of the device10using an input device of the device10).

FIG. 8Billustrates a variation of the user interface800for presenting lab results to a user. The user interface800includes a graph844showing the white blood cell count at different times. The user interface800also includes other blood count information848. By means of non-limiting examples, the blood count information848may include red blood cell level, white blood cell level, hematocrit level, hemoglobin level, MCV, MCH, and MCHC. As shown in the figure, the blood count information848may be presented for different dates.

FIG. 8Cillustrates a variation of the user interface800for presenting lab results to a user. The user interface800includes the blood count information848. By means of non-limiting examples, the blood count information248may include red blood cell level, white blood cell level, hematocrit level, hemoglobin level, MCV, MCH, and MCHC. The user interface800also includes a chart849showing the level of neutrophils and total white cell count on different dates for the patient.

Although embodiments of user interfaces200,300,400,500,600,700,800have been described, it should be noted that two or more of these user interfaces may be parts of an overall user interface that is provided at the device10. For examples, in some embodiments, all of the interfaces200,300,400,500,600,700,800may be provided at the device10. Thus, as used in this specification, the term “user interface” may refer to one or more user interfaces.

In any of the embodiments describe herein, the user interface may be implemented using software, hardware (e.g., processor(s), such as the processor16within the device10, the processor56at the database14, or both), or combination of both. For example, in some embodiments, a computer product may be provided that includes instructions stored in a non-transitory medium, wherein an execution of the instructions by one or more processors (e.g., the processor16of the device10, the processor56of the database14, or both) causes a process to be performed. The process may involve providing any of the features of the user interface described herein, or any of the features described herein. In one implementation, one or more software may be stored in a non-transitory medium in the device10. The device10may execute the software using the processor16to thereby process information received from the database14, and to display the processed information in various page(s).

Also, in the above embodiments, various information presented at the device10has been described as being retrieved from the database14. However, in other embodiments, some of the information may be stored in a non-transitory medium in the device10. For example, in other embodiments, one or more pieces of data displayed in any of the user interfaces200,300,400,500,600,700,800may be stored in a non-transitory medium in the device10.

As illustrated in the above embodiments, the system2is advantageous because it allows different professionals (e.g., nurses, doctors, imaging technicians, chemotherapists, etc.) participating in a treatment process to conveniently work on different tasks (e.g., by providing input using the device10), view medical images, make changes to the treatment process (if needed), and correspond with each other. Because the same device10can allow a user to perform these tasks, it obvious the need for the user to use a dedicated station to perform one task, and then use another device to perform another task. Also, because the device10is mobile, the user can perform the tasks at any location. For example, when a doctor is visiting a patient in a hospital, the doctor may immediately enter notes using the device10based on his/her observation of the patient. The doctor may transmit the notes to the database14immediately, and another professionals involved in the process (such as a pharmacist) may then immediately take the appropriate action based on the doctor's observation. Thus, the device10allows professionals involved in the treatment process to make immediate input for the process, and the input will immediately allow others involved in the process to take actions accordingly. Thus, the system2allows the treatment process to be carried out effectively without delay, and conveniently.

Computer System Architecture

FIG. 9is a block diagram that illustrates an embodiment of a computer system1200upon which embodiments of the features of the user interface10may be implemented. In some embodiments, the computer system1200may be used to implement the database14or the device10ofFIG. 1. Computer system1200includes a bus1202or other communication mechanism for communicating information, and a processor1204coupled with the bus1202for processing information. The processor1204may be configured to perform various functions described herein. The computer system1200also includes a main memory1206, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus1202for storing information and instructions to be executed by the processor1204. The main memory1206also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor1204. The computer system1200further includes a read only memory (ROM)1208or other static storage device coupled to the bus1202for storing static information and instructions for the processor1204. A data storage device1210, such as a magnetic disk or optical disk, is provided and coupled to the bus1202for storing information and instructions.

The computer system1200may be coupled via the bus1202to a display1212, such as a cathode ray tube (CRT) or a flat panel, for displaying information to a user. An input device1214, including alphanumeric and other keys, is coupled to the bus1202for communicating information and command selections to processor1204. Another type of user input device is cursor control1216, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor1204and for controlling cursor movement on display1212. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

The computer system1200may be used for performing various functions (e.g., calculation) in accordance with the embodiments described herein. According to one embodiment, such use is provided by computer system1200in response to processor1204executing one or more sequences of one or more instructions contained in the main memory1206. Such instructions may be read into the main memory1206from another computer-readable medium, such as storage device1210. Execution of the sequences of instructions contained in the main memory1206causes the processor1204to perform various processes described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in the main memory1206. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to the processor1204for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media (an example of non-transitory media) includes, for example, optical or magnetic disks, such as the storage device1210. Volatile media (another example of non-transitory media) includes dynamic memory, such as the main memory1206. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise the bus1202. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor1204for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to the computer system1200can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector coupled to the bus1202can receive the data carried in the infrared signal and place the data on the bus1202. The bus1202carries the data to the main memory1206, from which the processor1204retrieves and executes the instructions. The instructions received by the main memory1206may optionally be stored on the storage device1210either before or after execution by the processor1204.

The computer system1200also includes a communication interface1218coupled to the bus1202. The communication interface1218provides a two-way data communication coupling to a network link1220that is connected to a local network1222. For example, the communication interface1218may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface1218may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface1218sends and receives electrical, electromagnetic or optical signals that carry data streams representing various types of information.

The network link1220typically provides data communication through one or more networks to other devices. For example, the network link1220may provide a connection through local network1222to a host computer1224or to equipment1226such as a radiation beam source or a switch operatively coupled to a radiation beam source. The data streams transported over the network link1220can comprise electrical, electromagnetic or optical signals. The signals through the various networks and the signals on the network link1220and through the communication interface1218, which carry data to and from the computer system1200, are exemplary forms of carrier waves transporting the information. The computer system1200can send messages and receive data, including program code, through the network(s), the network link1220, and the communication interface1218.