System and Method for Providing Healthcare Services to Patients

Embodiments of the innovation relate to, in a healthcare facility server device, a method for providing a personalized healthcare service to a scheduled patient. The method comprises receiving real-time schedule data from a healthcare service provider device, the real-time schedule data identifying a schedule of a healthcare service provider; applying the real-time schedule data to a schedule-monitoring model, the schedule monitoring model configured to predict a future schedule associated with the healthcare service provider; identifying a difference between the real-time schedule data and the future schedule to detect a schedule delay associated with the healthcare service provider; and outputting a delay notification to the scheduled patient of the healthcare service provider, the delay notification associated with the schedule delay.

FIELD

Embodiments of the present innovation relate generally to a system and method for providing healthcare services to patients, and particularly, to such methods and systems that allow for personalized delivery of healthcare services to patients.

BACKGROUND

Each year, millions of patients across the world visit physicians to seek medical advice regarding a variety of different issues. Typically, such patients schedule an appointment with the physician in advance. On the day of appointment, the patients typically face significant delay in seeing the physician at the scheduled time. Such delays may be caused by unexpected events, or can be due to slight delays associated with each patient, which may cumulatively result in a significant delay for subsequent patients.

SUMMARY

Conventional healthcare systems can suffer from a variety of deficiencies. For example, conventional healthcare systems do not provide the patients with advanced notice regarding physician schedule delays. Further, conventional healthcare systems do not provide other personalized features, which could facilitate a patient's visit, such as helping the patient to navigate from his/her place of residence to the medical facility at which the medical appointment is scheduled.

By contrast to conventional healthcare systems, embodiments of the present innovation relate to enhanced methods and systems for delivering healthcare services to patients.

In one arrangement, embodiments of the present innovation relate generally to methods and systems for providing personalized healthcare services to patients. By way of example, in some embodiments, the methods and systems according to the present teachings facilitate a patient's visit to a medical facility by providing the patient advanced notification regarding the date/time of the appointment, directions to the facility, and/or real-time information regarding a physician's schedule. Further, the systems and methods of the innovation provide a physician with personal and medical data associated with a patient so as to allow the physician, or other medical professionals, to interact with the patient in a more personalized manner and further to have access to up-to-date patient's medical data.

Embodiments of the innovation relate to, in a healthcare facility server device, a method for providing a personalized healthcare service to a scheduled patient. The method comprises receiving real-time schedule data from a healthcare service provider device, the real-time schedule data identifying a schedule of a healthcare service provider; applying the real-time schedule data to a schedule-monitoring model, the schedule monitoring model configured to predict a future schedule associated with the healthcare service provider; identifying a difference between the real-time schedule data and the future schedule to detect a schedule delay associated with the healthcare service provider; and outputting a delay notification to a scheduled patient of the healthcare service provider, the delay notification associated with the schedule delay.

DETAILED DESCRIPTION

Embodiments of the present innovation relate generally to methods and systems for providing personalized healthcare services to patients. By way of example, in some embodiments, the methods and systems according to the present teachings facilitate a patient's visit to a medical facility by providing the patient advanced notification regarding the date/time of the appointment, directions to the facility, and/or real-time information regarding a physician's schedule. Further, the systems and methods of the innovation provide a physician with personal and medical data associated with a patient so as to allow the physician, or other medical professionals, to interact with the patient in a more personalized manner and further to have access to up-to-date patient's medical data.

FIG.1illustrates a schematic depiction of a system100for providing personalized healthcare services to patients, according to an embodiment. The system100includes a plurality of patient devices102a,102b,102c, and102d(herein collectively referred to as devices102), each of which is associated with an individual, e.g., a patient, seeking medical services. The patient devices102can be any suitable device (e.g., a mobile device, such as, a computer, a portable computer, a mobile phone or any other device) capable of communicating with a server device associated with a medical facility and/or an individual medical provider.

The system100further includes a healthcare facility server device104associated with a medical provider, e.g., a hospital. The healthcare facility server device104includes a controller107, such as a memory and a processor, which is configured to exchange information with the patient devices102. For example, the healthcare facility server device104is disposed in electrical communication with the patient devices102via a messaging network106, e.g., the Internet. In this embodiment, each of the client devices102can include a controller103, such as a processor and memory, which is configured to execute a client program108according to the present teachings. As provided in more detail below, when executing the client program108, the patient devices102can obtain information from a patient and communicate that information to the healthcare facility server device104.

A variety of types of information can be exchanged between a patient device102and the healthcare facility server device104.

In one arrangement, the patient device102can provide patient information105to the healthcare facility server device104, such as for use for a medical appointment. For example, when executing the client program108, the client device102can present a questionnaire110to a patient to obtain information about the patient. For example, the questionnaire110can request information about the patient's marital status, number of children, name, and medical history. The patient can opt not to answer to any of the questions. However, in response to receiving input from the patient, the client device102is configured to send the information provided by the patient as patient information105, such as via a communication module, to the healthcare facility server device104. The server device104, in turn, receives the patient information105, such as via a communication module, and can store this patient information105in a database114such that the information105is associated with that particular patient, such as via a name or medical identification number. As provided in more detail below, the healthcare facility server device104can then provide the patient information105to a medical provider, such as a physician, upon request.

In one arrangement, the healthcare facility server device104can provide notification122to a patient device102, such as for use by a patient for a medical appointment. For example, the controller107of the healthcare facility server device104can be configured to execute a server program116to communicate with a client program108of a patient device102to provide one or more notifications122to the patient regarding an upcoming medical appointment. For example, when executing the server program116, the healthcare facility server device104can provide notification122to a patient device102regarding an upcoming medical appointment at a plurality of times prior to the appointment (e.g., a month, two weeks, or a week prior to the appointment).

With reference toFIG.2, and by way of example, the healthcare facility server device104can provide such a notification122to the patient via a pop-up window130appearing on the patient's device102. Further, in some embodiments, the notification122can provide information regarding the medical professional, e.g., a physician, with whom the patient has an appointment.

The notification122can include a variety of types of information. By way of example, as shown schematically inFIG.2, the notification122can provide the name of the physician, the medical facility at which the appointment is scheduled, and a web link to the physician's profile. Further, in some embodiments, the notification122can remind the patient of any test, or preparation that the patient needs to perform prior to the appointment. By way of illustration, as shown inFIG.2, when the patient has an appointment for a colonoscopy procedure, the notification122can remind the patient of the required preparation for the colonoscopy procedure.

In some embodiments, the notification122can further provide directions to the medical facility, including the best route available to the medical facility on the day of the appointment. By way of example, as shown schematically inFIG.2, on the day of appointment, the patient can launch the notification122, e.g., via selection of an icon126. The notification122can then provide the time of the appointment and the name of the medical facility to the patient. In addition, the notification122can provide the patient with the option of obtaining directions, e.g., in real time, to the medical facility. For example, the patient can choose a MAP icon included with the notification122to obtain direction instructions for traveling to the medical facility.

Returning toFIG.1, the healthcare facility server device104can communicate with additional components within the system100. For example, the healthcare facility server device104is disposed in electrical communication with a plurality of computerized devices200a,200b,200c, and200d(herein referred to as “healthcare workers” or “physician devices”200) via a messaging network114, e.g., the Internet, that can be used by medical professionals, e.g., physicians. The physician devices200can be any suitable computerized device having a controller (e.g., a memory and processor), such as a portable computer, a mobile phone, or any other suitable device.

The healthcare facility server device104can also be disposed in electrical communication with an Electronic Health Record (EHR) system112of a medical facility. In one arrangement, the server device104is configured to retrieve a patient's medical records115(e.g., laboratory tests, X-rays, etc.), from the EHR system112and provide that information to one or more of the physician devices200. In some embodiments, the healthcare facility server device104is configured to collate the patient information105obtained from a patient device102and the patient's medical records115received from the EHR system112and provide the collated records120to a physician device200for use by a medical provider, as provided in more detail below.

In certain cases, healthcare workers of a healthcare facility can experience delays in their schedules, which can, in turn, delay the times at which patients are scheduled to see the healthcare workers. To identify the presence of a delay in a healthcare worker's schedule and to provide patients with advanced notice regarding such delays, the controller107of the healthcare facility server device104can generate a schedule-monitoring model140.

For example, with reference toFIG.3, with execution of the schedule-monitoring module154, the healthcare facility server device104is configured to generate a schedule-monitoring model140based upon historical schedule data142such as generated by one or more physician practices associated with a healthcare service provider. For example, the controller107can include, and be configured to execute, a training engine144on historical schedule data142to train a schedule-monitoring framework150, such as an algorithm, using supervised and unsupervised predictive models to generate the schedule-monitoring model140.

During a training operation, the training engine144can receive the historical schedule data142from a historical database146. While the historical schedule data142can be configured in a variety of ways, in one arrangement, the historical schedule data142can identify historical schedules for healthcare workers of a particular facility during a given time period, such as over the course of one year. For example, the historical schedule data142can identify healthcare workers' schedules by time-of-the-day, by day, by week, or by month. The historical schedule data142can identify external schedule factors as well, such as holiday and weather information.

Following receipt of the historical schedule data142, the training engine144can cause the schedule-monitoring framework150to perform its operations relative to the historical data142to generate the schedule-monitoring model140. The training engine144can generate a variety of schedule-monitoring models140. In one arrangement, the training engine144is configured to generate a schedule-monitoring model140for each individual healthcare worker of a given healthcare facility.

For example, the schedule-monitoring framework150can be trained to generate a schedule-monitoring model140that is configured to estimate the delay time associated with the scheduled times for patients who seek to be examined by a particular medical professional, e.g., a particular physician. In certain cases, the historical schedule data142can identify a pattern of delays associated with scheduled appointment times for that medical professional based on data obtained over a given time period, e.g., a month, a few months, a year or multiple years. As such, the schedule-monitoring framework150can be trained on that data142to generate a schedule-monitoring model140which is configured to predict or estimate the delay time, if any, associated with scheduled appointment times for patients. As such, each schedule monitoring module140can be configured to predict a particular worker's schedule.

In one arrangement, the training engine144is configured to generate a schedule-monitoring model140for healthcare workers of a particular department in the facility. As such, the resulting schedule monitoring module140is configured to predict the schedule of any or all healthcare workers of a particular department.

Following generation of the schedule-monitoring model140, the training engine124provides the schedule-monitoring model140to the healthcare facility server device104, which can then execute the schedule-monitoring model140on real-time healthcare worker schedule data to predict a healthcare worker's schedule.

In one arrangement, during operation and with continued reference toFIG.3, the healthcare facility server device104is configured to receive real-time schedule data152from a healthcare service provider device200where the real-time schedule data152identifies a schedule of a healthcare service provider.

For example, the healthcare facility server device104can include a schedule-monitoring module154that can track the progress of a physician as the physician attends to patients and can provide notification to one or more patients having scheduled appointments to see that physician regarding whether or not the patient's visit with the physician is likely to be delayed, if so, provide the patient with an approximate delay time.

The schedule-monitoring module154can obtain real-time schedule data152regarding a physician's daily schedule in a variety of ways. In one arrangement, at the beginning of each working day, the schedule-monitoring module154can communicate, via a communication module of the healthcare facility server device104, with the EHR system112to request and obtain a physician's patients schedule for that day. For example, assume the case where Dr. Jones is scheduled to examine eight patients on a given day at the given times. In some cases, the EHR system112can receive this information, e.g., in a tabular format, from the physician via the physician device200. As each patient is examined by the physician and checks out, the EHR system112can receive notification and can provide a time stamp to the schedule-monitoring module154as the real-time schedule data152which corresponds to the patient's check-out time.

Next, the healthcare facility server device104is configured to apply the real-time schedule data152to the schedule-monitoring model140where the schedule monitoring model140is configured to predict a future schedule associated with the healthcare service provider.

In one arrangement, with receipt of the real-time schedule data152, the schedule-monitoring model140is configured to calculate the approximate time at which the physician can see the subsequent patients and to determine approximate delays for patients scheduled to visit the physician. For example, as discussed in more detail below, the schedule-monitoring model140can operate on the data152obtained from the EHR system112for that day and/or previous days regarding the check-in/check-out times of the patients to predict the upcoming or future schedule156, for the physician. In some embodiments, the schedule-monitoring model140can further take into account other factors, such as historical data for a particular physician, the day of the week, the month of the year, etc., when predicting the upcoming or future schedule156of the healthcare service provider.

If the schedule-monitoring model140identifies a difference between the real-time schedule data152and the predicted future schedule156, the schedule-monitoring model140can detect a schedule delay158associated with the healthcare service provider. For example, in the case where the schedule-monitoring model140predicts a future schedule156which is delayed relative to a particular patient's actual scheduled appointment, the healthcare facility server device104can communicate via a communication module to an associated patient device102to provide a schedule discrepancy or delay notification160to the patient device102regarding the delay in the physician's schedule.

In some embodiments, the schedule-monitoring model140can detect the approximate delay times in a physician's schedule at pre-defined times, for example, about two hours prior to each scheduled appointment time for that physician. In some such embodiments, the time at which the detection is made relative to the scheduled appointment time can be informed by the profile of the patient having the scheduled appointment. For example, the schedule-monitoring model140can perform the calculation at a time informed by the distance the patient must travel to arrive at the medical facility. In some such embodiments, the schedule-monitoring model140can receive data corresponding to the patient's profile, e.g., from the EHR system112or by analyzing data provided by the patient in a questionnaire that was previously provided to the patient.

For example, assuming that a patient has an appointment with a physician at 10 am, and the physician is about 1 hour behind schedule, the schedule-monitoring model140can communicate the delay notification160to the client device102to indicate the delay time, and the client device102can, in turn, present this information to the patient. For example, the client device102can provide a pop-up window to indicate that the physician, e.g., Dr. Jones in this case, is one hour behind schedule. This allows the patient to adjust his or her time of departure, e.g., from home, for traveling to the medical facility. Thus, the patient can avoid unnecessary delay in seeing the physician at the medical facility, and hence can enhance the patient's experience.

In one arrangement, following the detection or prediction of a schedule delay158, the healthcare facility server device104is configured to generate an appointment estimate time170which identifies when the healthcare service provider can see the scheduled patient. A variety of methods can be used to generate the appointment estimate time170relative to the patient's scheduled appointment time. For example, the estimate170can be obtained by analysis of the time a patient is seen by a doctor (herein referred to as “stamp-in time”) relative to the scheduled appointment time for that patient and/or the time at which the patient checks out of the medical facility (herein referred to as “stamp-out time”). For example, healthcare facility server device104can perform a regression analysis of the difference between the stamp-in times and the scheduled times of a plurality of patients who have been seen by a physician, or other medical professional, and have checked out of the medical facility can be used to estimate stamp-in times for one or more subsequent patients.

In some embodiments, if the stamp-out time associated with a patient for whom a stamp-in time has been recorded exceeds a predefined threshold, the healthcare facility server device104may not consider that patient in the estimation of the stamp-in times for one or more subsequent patients. For example, in some cases, a physician may order certain diagnostic tests for a patient, e.g., an MRI or x-rays, to be performed while the patient is at the medical facility. Meanwhile, the physician can continue examining other patients. The performance of the tests may significantly delay the stamp-out time associated with that patient without affecting the stamp-in times associated with subsequent patients. As such, in such embodiments, the stamp-out time is associated with that patient.

Further, in some cases, the physician may have to attend to an emergency. In such a case, the healthcare facility server device104can be provided with this information, e.g., via the EHR system112, as an emergency notification. Alternatively, the information regarding the emergency can be manually inputted into the healthcare facility server device104. In some cases, the healthcare facility server device104can be provided with an approximate time interval during which the physician may be occupied with attending to the emergency. Alternatively, the healthcare facility server device104can be configured to execute an algorithm to predict the amount of time needed by the physician to attend to the emergency.

In one arrangement, following generation of the estimation of the time170when the healthcare worker can see the patient, the healthcare facility server device104can forward the appointment estimate time170to the patient device102and can output a travel notification172to a patient device102to inform the patient scheduled to be examined by the physician regarding the delay in the physician's schedule as well as an estimate as to the travel time from the patient's location to the healthcare facility. By way of example, in some embodiments, the patient's information or profile105can include information regarding the patient's residential address. In some such embodiments, the schedule-monitoring model140can calculate the approximate time required for the patient to travel from her residential address to the medical facility. The approximate travel time can be obtained, for example, by considering the residential address of the patient, the address of the medical facility and the traffic pattern at the time of the calculation. By way of example, the schedule-monitoring model140can obtain the traffic pattern from a source, e.g., a commercially available program such as Waze. Alternatively, an average traffic pattern based on the previously-obtained traffic pattern data for that particular day of the week and the appointment time can be utilized. Such a travel time estimation can be made, for example, at the beginning of each working day, or at a fixed time (e.g., 2-3 hours) prior to each patient's scheduled appointment time.

In one arrangement, the system200can be further utilized to improve a patient's experience with a healthcare facility. For example, a physician's device200can communicate with the healthcare facility server device104to obtain information about the patient. The physician can use this information during the patient's visit to provide more personalized service to the patient. For example, the physician's device200can communicate with the healthcare facility server device104to receive information regarding a patient collected by the healthcare facility server device104.

The physician or healthcare worker can obtain a variety of types of information regarding the patient. For example, the physician, or other medical professional, can obtain information about the marital status of a patient, whether or not the patient has children, and if so, the names and birthdates of those children. Further, the physician can obtain other information about the patient's children and/or the patient's spouse, such as their occupation and/or any chronic diseases from which they may suffer. Such information can allow the physician, or other medical professional, to provide a more personalized treatment to the patient. In other words, such information can allow the physician, or other medical professional, to interact with a patient in a manner that will lead to enhanced satisfaction of the patient and a better treatment outcome.

As provided above the healthcare facility server device104can provide a travel notification172to a patient device102to inform a patient of a delay in the physician's schedule. In one arrangement, the healthcare facility server device104can review additional variables prior to sending the travel notification172. For example, the healthcare facility server device104can determine how far the patient is living (e.g., in state vs. out of state) or prior visits of patient (e.g., history of the patient's visits) prior to transmitting the travel notification160.

In one arrangement, each patient can utilize the patient device102to track where the patient is in the schedule and how the patient is advancing in the schedule.

In one arrangement, a patient's chart can include barcodes which identify scheduling information pertaining to a patient's visit at a healthcare facility. For example, the barcodes can identify the following times associated with a patient's visit: patient arriving; time chart is pulled by technician; time patient is seen by physician; time when the leave the physician; and time of patient checking out.

As provided above, the patient device102can provide patient information105to the healthcare facility server device104. In one arrangement, the patient information105is configured as a brief synopsis of the patient's data or as a personalization of the patient's information to be presented to the physician. The healthcare facility server device104can update exiting patient information with the received patient information105(e.g., nothing has changed, somebody has to update it, if needed, etc.).

As provided above, the client devices102can execute a client program108in order to obtain information from a patient and communicate that information to the healthcare facility server device104. In one arrangement, the client program108is further configured to notify the patient if the healthcare appointment is one-time only or if additional appointments have been scheduled.

While various embodiments of the innovation have been particularly shown and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the innovation as defined by the appended claims.