Patent Application
20070276702
For a more complete understanding of the present invention, reference is now made to the following descriptions taken in conjunction with the accompanying drawing, in which:
Locations 110-1, 110-N include a number of servers that manage various aspects of both the medical information and medical records. Locations 110-1, 110-N can include, for example, medical image server 111, consultation server 112, email server 113, application server 114, and web server 115. In the illustrated embodiment, each of these servers are connected to one another via connection 116. Further, in some embodiments these servers are located remote from one another.
Image server 111 is a computer or other system that manages medical images. These medical images can include a variety images related to healthcare. For example images on medical image server can include, X-rays, MRI images, CT images, images of organs, images of organs having a particular condition, images of a particular condition, etc. Through the use of image server 111 users of system 100 are able to obtain visual information related to either a patient or a condition. In some embodiments image server 111 also includes forms that are commonly used by healthcare providers or patients. These forms can include intake, insurance reimbursement requests, pre-appointment checklists and the like.
Consultation server 112 is a computer or other system that manages consultations for example, between healthcare providers and patients or between two healthcare providers. As used herein, the term “provider” can include for example, physicians, care givers, family, friends or another patient-authorized person. Consultations allow a patient to communicate with and transmit information to a healthcare provider who is not in the same location as the patient. Additionally, consultation server 112 can allow a physician at one location communicate with an expert in another location and share information related to a patient. In one embodiment consultations occur in a format similar to instant messaging. In another embodiment consultations are performed using video teleconference or other methods. Additionally, consultations can include the monitoring of the user. In these instances, the provider may log into the users data and review the data. Based on the review, the provider can, for example, leave a “note” for the user to perform a specific action.
Email server 113 provides a communications link between various patients and healthcare providers. Through email server 113 patients and healthcare providers can share various documents or transmit other information in a secure environment. Email server 113 can function in a manner similar to consultation server 112. However, email server 113 provides a time delayed (non-real time) communications system. Email server 113 provides the users of system 100 the ability to ask and answer questions over time or transmit documents prior to a scheduled visit with a healthcare provider.
Application server 114 provides a platform upon which users can use or interact with the various components of system 100. Details of exemplary application 125 and functions are discussed in greater detail below. Briefly, however, application server provides a dynamic interface that users of system 100 can use to transmit, enter, or retrieve information desired. Application server 114 provides an application interface (e.g., graphically user interface (GUI)) on a user's computer or other device so that the user can obtain the desired information. This information is provided from other servers in the location.
Web server 115 is a network based server that provides access to the application server 114 and thus system 100 over network 105. This allows users of system 100 to access information and features of service 100 when they are away from their primary computer, or on a computer that does not have the associated application installed on it. Web server 119 can be isolated from the other servers at location 110 through the use of firewalls 115. These firewalls help to prevent hackers or malicious users from accessing information that is stored on system 100.
Connected to location 110 are databases 117-1, 117-2, 117-N. These databases can be local to the specific location or can be remote from location 110 and connected to location 110 via connection 118. If database 117 is remote from location 110 then in some embodiments database 117 may be shared with multiple locations. This helps to ensure that in the event that a specific location goes down users of system 100 are able to access information stored on database 117. Database 117 for example stores information related to a patient, such as, name, date of birth, address, medical history, wellbeing, developmental milestones and the like. This information is then accessible by an authorized healthcare provider who accesses system 100. If the user desires, portions of the information in database 117 may be shielded from a particular provider. The user can limit the amount of information available to any one provider. For example, a user may allow a physician provider unlimited access to the data, and restrict a family member from some data (e.g. psychological reports).
Users interact with system 100 through a variety of client devices such as devices 120-1, 120-2, 120-3, 120-N. For example device 120-1 is a desktop computer, device 120-2 is a personal digital assistant (PDA), device 120-3 is laptop computer and device 120-N is a cellular telephone. Each of the client devices communicates with system 100 through network 105. The connection with network 105 can be either wired or wireless, and can also be accomplished though the use of other connection protocols. The user can load application 125 onto their client device 120-1, 120-2, 120-3, 120-N to provide faster and more secure access to system 100. Application 125 has in one embodiment the ability to change the form factor of a display associated with application 125 in response to the device that it is installed. By modifying the form factor information can be presented to the user in a manner appropriate to the device.
Users access system 100 through application 125. Application 125 provides the portal through which the user can use the features of system 100. Depending on the type of user (e.g. patient, physician, insurance company, etc) application 125 provides a different display or dashboard to the user. The dashboard allows users to access the information in a method and approach that is appropriate for that user. For example, when a patient accesses system 100, dashboard will display information, links and buttons appropriate for a patient. In some embodiments terms will be modified to better match the terms the general public expects to see. However, for a healthcare provider terms may remain in the common medical term. (e.g. Heart Attack vs. Myocardial Infarction).
Information that is stored on database 117 can be downloaded to user device 120. In this approach the user is able to access the information in their record without having to go out to the service 100 every time they desire to update or view information. In some embodiments this information can be downloaded and stored on a portable storage device 122-1, 122-2, 122-3, 122-N (e.g. a flash memory card, CD-ROM, etc.). This allows the user to take their medical information along with them in cases where access to the networked version of system 100 is unavailable (e.g. on a cruise ship, in remote areas, etc.). In additional embodiments, users can also store on device 122 application 125. The storage of application 125 can be useful in situations where access to application 125 is not available.
Application 125 also allows users the ability to obtain a large amount of information on various conditions.
Center section 220 of dashboard 200 provides a list of specific tasks, reminders, milestones, tips and diary or journal entries. Each of these boxes or areas allow for the user to either view or enter information into the application. For example, the user can click on diary box 226 and enter in information related to the daily activity of a child or patient. This information can then be accessed later by a healthcare provider to view the activity of the patient. This may provide a more accurate and detailed look at a patient's activity than would be associated with the patient remembering activity or symptoms at a later time.
Box 224, for example, shows a listing of reminders for the user. In the example illustrated the reminders include a reminder of the next vaccination that is required and to update a growth chart. In the example where the patient is an adult male, a reminder to have a procedure (e.g., colonoscopy) could appear following a milestone date (e.g., his 40th birthday). The reminder can remain visible until the appropriate action is taken. From the reminders, the user can view various information related to the reminders. For example, if the user desires to find out what a colonoscopy procedure is, the user can be presented with a link to find out more information. If the user accesses the link, application 125 communicates with medical image server 111 of system 100 and requests information related to a colonoscopy. The server 111 can return to the user a description of the procedure and also provide a video image of the procedure, or an image of what the physician is looking for during the procedure.
Box 225, for example, shows a list of emails that have been received by application 125. Emails that are received by application 125 are sent to an email address associated with system 100. These emails are processed by email server 113 and then delivered to the user when they log onto system 100. The user can access the email by, for example, clicking on the email. In some embodiments box 225 can also allow the user to send a context sensitive email, e.g. to request an online consultation, using a single option and sending the email. If an online consultation is requested, system 100 will identify a provider who can consult with the patient. Contextual information is transmitted to the provider via consultation server 112. Through this approach the user and provider have access to the same information. If during the consultation the provider needs to ask a question, the provider can have the user view an item from the medical image server to determine if the condition is similar to the image. This helps the provider diagnose the patient from a remote distance.
On the left hand side 230 of dashboard 200 is a listing of actions/tasks 231-240 that are commonly performed by the user. Each of these actions/tasks is represented by an icon or other indicator that is clickable by a user. Application 125 customizes the actions/tasks based on factors such as person's age, sex, race, medical needs, and usage patterns, however, other factors of a user profile can be used. The more frequently an action or task is performed the higher it will be in the list to enable faster access and recognition. In some embodiments if a specific action or task has been designated a high priority action or task it can be moved to the top of the list. (e.g. a vaccination needs to be administered, or a test needs to be scheduled). Application 125 can update the task list order every time the user logs into the system, or can update the order on a regular basis.
When the user clicks on one of the tasks 231-240 in section 230, the center section 220 of the dashboard 200 changes to display information related to the highlighted task. An example of a change in center section 220 is illustrated in
All of the information that is entered by users into system 100 through application 125 are stored on database 117. As mentioned before, this information can also be stored on portable storage device 122 and carried with the person. When a patient visits a physician or other healthcare provider, the physician can access the information in database 117 to become familiar with the status of the patient, or to review the patient's progress remotely. However, the user can limit the amount of information shared with any provider. This is achieved through the use of security or other protocols.
Through the use of dashboard 200, the user is able to review their entire medical history. Various tabs allow the user to obtain information related to upcoming visits with a healthcare provider. For example, users can pre-fill forms out prior to arriving at a physician's office, or can print out a listing of steps associated with a procedure (e.g., office visit, diagnostic test, etc.) This allows the user to know what to expect, and also allows the user to verify that proper medical care is being given.
Once into system 100, dashboard 200 is displayed on the user's device 120 at process 403. Typically, upon start-up the user is presented with a summary page for the default user that provides quick viewing of reminders, appointments, or other tasks that require attention. If the user desires to pull up another family member they can do so at process 404. At process 405 system 100 accesses the information in database 117 for this user and displays information for this user on dashboard 200.
At process 406, the user navigates through the dashboard to obtain or enter information into system 100. This can include such activities as entering data into the system or reviewing symptoms to identify a problem (e.g., requesting images of a condition from server 111). Of course a variety of other activities can be performed at process 406. If the user has decided that they need to take an action, for example, make an appointment at process 407, system 100 can help the user make an appointment with a physician, at process 408. In other examples, users can send email to a physician at process 408. For example, system 100 can access a physician's appointment schedule and allow the user to schedule the appointment directly from the system. Once the appointment has been scheduled system 100 can update the reminders section (or any other portion of the dashboard) at process 409, and can also provide a display that allows the user to know what to expect at the appointment.
When the user is finished with using the system, the user can save the information at process 410. This information can be saved either to database 117, to portable storage device 122 or both. Preferably, if information is stored to device 122 it is also stored to database 117 as well.
At process 503 the provider reviews the data for a patient. This can include reviewing such information as diary entries and other medical records. Based on this review the provider is able to prepare for the office visit or determine if additional information is needed from the patient at process 504. If additional information is required from the patient then the provider can send a message or form to the patient to request this additional information at process 505. In some embodiments, the physician stores this request on database 117 and awaits a response from the patient at optional process 505-1. The additional information is received at process 506. The physician then reviews this additional information by returning to process 503.
If no additional information is required the physician can provide medical services at process 507. If the medical services are provided in an office visit the provider and the user can review together the information at process 507. Otherwise the medical services are provided through system 100. Based on the actions taken during the visit, the patient's records can be updated in system 100 at process 508. The updated data is stored in database 117 at process 509. Also included in the stored records is data related to the provider who accessed the patient's records. This auditing and journaling feature helps to detect fraud or other unethical behaviors.
It should be noted that while the above description has been directed towards medical information sharing and storing the principles discussed above may be applied to other areas where the need to share information between users and providers of services exists. For example, the above principles can be applied to consulting services, legal services, and the like.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
The present application is a utility of U.S. Provisional Application No. 60/809,140, Attorney Docket No. 50,125-01PROV, entitled “SYSTEM AND METHOD FOR HEALTH INFORMATION,” filed on May 25, 2006, the disclosure of which is hereby incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60809140 | May 2006 | US |
