US20080109262A1 - Rules Based Ticketing For Self-Scheduling of Appointments - Google Patents
Rules Based Ticketing For Self-Scheduling of Appointments Download PDFInfo
- Publication number
- US20080109262A1 US20080109262A1 US11/971,420 US97142008A US2008109262A1 US 20080109262 A1 US20080109262 A1 US 20080109262A1 US 97142008 A US97142008 A US 97142008A US 2008109262 A1 US2008109262 A1 US 2008109262A1
- Authority
- US
- United States
- Prior art keywords
- rules
- entity
- patient
- scheduling
- healthcare
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1095—Meeting or appointment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
- G16Z99/00—Subject matter not provided for in other main groups of this subclass
Definitions
- the present invention relates generally to health record management, and more particularly, the present invention relates to a rules-based scheduling system to allow a healthcare facility to control appointments scheduled through the Internet with “scheduling tickets” that incorporate a variety of rules.
- the existing scheduling solutions are based on messaging or very restricted access. These solutions allow patients to enter some limited information concerning an appointment. Some examples are: (1) which provider the patient wants to see, (2) the day and time the patient wants to be seen, (3) some of the patient's insurance information, and (4) a few other types of information relevant to scheduling.
- One embodiment of the invention relates to a method of allowing patients to schedule their own appointments on a computerized scheduling system.
- the method includes operating the computerized scheduling system to provide a first set of rules associated with a first entity, the first entity being a collection of healthcare providers.
- the first set of rules regulates self-scheduling by patients applicable to all appointments.
- the computerized scheduling system further provides at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients, and defines a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional sets of rules.
- the computerized scheduling system further communicates directly with the patient over the Internet to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers and approves or denies the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
- the system includes a rule set database.
- the database includes a first set of rules associated with a first entity, the first entity being a collection of healthcare providers, the first set of rules regulating self-scheduling by patients applicable to all appointments, and at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients.
- the system further includes a relationship processing engine configured to receive and implement a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional set of rules.
- the system yet further includes a patient scheduling interface configured to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers, and an appointment scheduling engine configured to approve or deny the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
- Yet another embodiment of the invention relates to a computer-implemented method for allowing patients to schedule their own appointments.
- the method includes receiving a request to schedule a medical appointment of a requested type with a particular healthcare provider within a collection of healthcare providers and accessing a patient accessible medical record database, the medical record database including a plurality of longitudinal patient records.
- Each longitudinal patient record is associated with a single patient and includes a medical history data structure including a patient record generated by a healthcare entity including clinical information sufficient for the delivery of medical services to those patients.
- the method further includes generating an approval or denial of the request to schedule the medical appointment received from the patient based on the longitudinal patient record associated with the patient submitting the request to schedule the medical appointment.
- FIG. 1 is a flow chart representation of the path that the system would take when a patient attempted to schedule an appointment directly from the system.
- FIG. 2 is a flowchart that illustrates the process by which a user logged in to his Patient Health Portal (PHP) Web Page can schedule an appointment that has been pre-qualified.
- PGP Patient Health Portal
- FIG. 3 is a flowchart illustrating the components and connections from the enterprise healthcare information management system through the Internet and on to the patient via a web page portal.
- the invention includes, but is not limited to, a novel structural combination of conventional data/signal processing components and communications circuits, and not in particular detailed configurations thereof. Accordingly, the structure, methods, functions, control, and arrangement of conventional components and circuits have, for the most part, been illustrated in the drawings by readily understandable block representations and schematic diagrams, in order not to obscure the disclosure with structural details which will be readily apparent to those skilled in the art, having the benefit of the description herein. Further, the invention is not limited to the particular embodiments depicted in the exemplary diagrams, but should be construed in accordance with the language in the claims.
- a system that enables a patient to use a pre-authorized or a user initiated scheduling process that utilizes hierarchically-layered rules.
- the system further provides dynamic feedback to self-schedule appointments with a user's preferred clinics and providers in a confidential and secure manner.
- the rules based ticketing system for self-scheduling provides healthcare clinics and providers the ability to manage and control patient appointment utilization. For several reasons, it is very desirable from a healthcare provider's perspective to allow patients to schedule their own appointments. It is also desirable from a patient's perspective to be able to independently schedule their own appointments at their convenience through the Internet. A system according to the preferred embodiments of the invention satisfies the desires of both parties.
- a rules-based scheduling system allows a facility to control appointments scheduled through the Internet with “scheduling tickets” that incorporate a variety of rules and triggers. These rules can be defined as many things. Some examples that may be included are:
- Rules set at more specific levels could override rules set at less-specific levels. For example, if an entire clinic's system is configured to allow diabetic patients to self-schedule using pre-authorized scheduling tickets, but a diabetic patient attempts to use a scheduling ticket to schedule an appointment in a department that does not allow diabetic patients to self-schedule, the patient would not be able to self-schedule in that department because the department level is more specific than the system level, so it takes precedence. However, diabetic patients in departments that allow diabetic patients to use self-scheduling or in departments with no specific rules for diabetic patients could still schedule an appointment with a ticket.
- Different rules could also be set up to override other rules.
- provider preference rules could be set up to override patient preference rules when a patient is using a scheduling ticket to make an appointment.
- the past patient history rules could be defined to override all other rules, because if a patient abuses self-scheduling, a facility would most likely not want that patient to be scheduling appointments, regardless of what the other rules dictate.
- these rules can be dynamic in their ability to change over time. For example, the system could revoke a patient's ability to self-schedule if the patient abuses the system. Therefore, if a patient self-scheduled three appointments and did not show up for them, the system could automatically change the patient's status from ‘able to self schedule’ to ‘unable to self schedule.’
- FIG. 1 of the drawings a flow chart representation is shown of the path that the system would take when a patient attempted to schedule an appointment directly from the system.
- a patient with access to self-scheduling can, either with a pre-authorized scheduling ticket or through a user initiated scheduling process, request an appointment with his or her clinic or provider.
- the self schedule request would then have to pass a series of checks, or rules, before it could be fulfilled.
- the system would run 104 a rules check to see 106 if the patient is authorized to self-schedule appointments. If the patient has the appropriate authorization, the system would then check 110 to see if a preauthorized scheduling ticket existed for the patient. If one existed, the system would offer 114 the patient time slots that met the ticket requirements.
- the system would verify that the patient was allowed to see the search results, whether the search results were obtained using the pre-authorized ticket or using search criteria initiated by the patient. The patient would then select 118 an appointment to schedule. The system would perform 120 one last check to make sure the patient was allowed to schedule the appointment and that the appointment was still available, and then the appointment would be made 124 . If the specific appointment that the patient was trying to book was unavailable, the patient would be prompted 112 to enter scheduling information manually, and the process would start over.
- the system can present the patient with a list of solutions that match his or her request. After the patient selects an appointment 118 , the system can perform 120 a final check to ensure that the patient is authorized to use the ticket to schedule the appointment and that the time slot is still available. If the request passes this security check, then the system can notify 124 the patient that he or she has successfully scheduled the appointment with his or her clinic or provider. If for any reason, a patient is not allowed to self-schedule, the system could be configured 108 to immediately give the patient the option to request an appointment, as opposed to actually scheduling one with a scheduling ticket.
- a patient can self-schedule an appointment with his or her clinic or provider using either a pre-authorized scheduling ticket 114 or through a user initiated scheduling process 112 .
- a pre-authorized scheduling ticket is an electronic ticket that is given to the patient via their electronic health record managed by their physician. This record is stored on a computer server and is referenced by the Internet based scheduling system to limit the patient's ability to schedule appointments to what is described 204 by the ticket.
- An electronic database of scheduling tickets (also referred to as access tickets) would be created. Attributes 204 of records in this database would include the healthcare provider who authorized the ticket, the services the ticket entitles the patient to schedule (e.g. one follow up visit within the next two months), and the patient identifier for the patient the ticket is for. The ticket also has an attribute that describes its current status (unused, appointment made, appointment completed).
- pre-authorized scheduling tickets would be automatically created during the physician's documentation of a clinical encounter with the patient.
- a doctor will document when a patient should return, in follow up of a problem (e.g. to check on how well a medication is working to control the patient's blood pressure) or for a follow up procedure (e.g. suture removal).
- the ticket's status is set to “unused.”
- the flowchart illustrates the process by which a user logged in to his Patient Health Portal (PHP) Web Page can schedule an appointment that has been pre-qualified.
- PGP Patient Health Portal
- the structure and functionality of a PHP Web Page is described in the commonly assigned United States patent application (attorney docket no. 29794/36547A) entitled “Integrated Patient and Enterprise Health Record System,” the disclosure of which is hereby expressly incorporated herein by reference.
- the Web Server queries 202 the Scheduling Server to see if there are any pre-qualified appointments available for the current user. If there are, the Web Server updates 208 the PHP Web Page with the available appointment information.
- the user can then select 210 an appointment to schedule, and indicates date, time, and locations (selections may be limited by information in the Scheduling Ticket database).
- the Web Server then obtains 214 appointment times available within the selected range and displays 218 them, whereupon the user can either select a time, change the search, or cancel.
- the Web Server notifies 224 the Scheduling Ticket database that the appointment has been scheduled and the ticket for the current user is updated 226 accordingly.
- the Scheduling Ticket database will then track whether the appointment has been cancelled or completed, and will update the corresponding pre-qualified appointment record accordingly.
- patients may schedule an appointment through a user initiated scheduling process 112 .
- An example of when this may be utilized is when a provider places a patient on a disease management protocol. These protocols might call for a patient to be seen with a certain frequency for specified types of visits. These protocols would automatically grant authority for the patients that conform to the limitations of the protocols. This process could be used independently or in combination with other insurance information available for the patient and represents the limitations that would be imposed on a patient self-scheduling through the web.
- the system may be designed to apply a more restricted set of rules to patients scheduling appointments through the user initiated scheduling process.
- a healthcare provider may reserve only a few time slots per week for patients to schedule appointments through this process. They may additionally limit those appointments to very short durations for limited purposes, such as consultations or the administration of simple tests.
- Another example is that the system could restrict a patient from selecting a provider or a department. Instead, the system would pick an appropriate provider or department from a pre-determined list that is driven by the patient as a parameter.
- the patient would be provided access to a self scheduling application (e.g. a web site or a computer application for personal use, possibly running on a home computer, personal digital assistant (PDA) or cellular telephone) which would allow them to schedule the appointment.
- a self scheduling application e.g. a web site or a computer application for personal use, possibly running on a home computer, personal digital assistant (PDA) or cellular telephone
- PDA personal digital assistant
- This self-scheduling computer application would identify and authenticate the patient and read the database of electronic tickets to determine what self-scheduling limits exist for the patient. The self-scheduling application then allows the patient to select appointments that are within the limitation of the ticket.
- an appointment Once an appointment is made, it is associated with the ticket. The ticket is then marked as “appointment made.” When the appointment is kept, the ticket is marked as “appointment completed” and then subsequently destroyed or retained for historical analysis. If the patient or provider cancels the appointment, the ticket's status would revert to the “unused status.”
- FIG. 3 The integration of the self-scheduling component into an overall healthcare management system is shown in FIG. 3 .
- a completely integrated system provides patients with secure, real-time access to their Personal Health Record and an Enterprise Health Information System (PHR and EHIS, respectively). Access may be provided by way of the Internet 316 and via a Personal Health Portal (PHP) web page 318 . From the secure PHP web page 318 , patients can view information created and maintained by their health care providers and their affiliated staff. The patients can also request services and information from their health care providers and affiliated staff, directly access EHIS-related services, such as scheduling an appointment, paying a bill, enrolling in a class, completing insurance and other forms, and viewing information and Internet services that are relevant to their particular health status.
- PHR Personal Health Information System
- EHIS Enterprise Health Information System
- a patient health record data server 302 including a machine readable media having a data structure containing patient-created data, is coupled by an electronic network with a patient interface.
- the electronic network may be the Internet 316 and the patient interface may be a suitable Internet access device including a browser for supporting a personalized web page 318 .
- a secure interface securely couples, in real-time, the patient health record server 302 to an enterprise health record system 304 for providing access by the patient to patient-related data retained within the enterprise health record system 304 .
- the patient via the patient interface, may access the patient health record server 302 for manipulating the patient-created data and for accessing the patient-related data from the enterprise health record system 304 .
- the system includes a Patient Health Record (PHR) data server 302 , an EHIS data server 306 , and a self-scheduling server 308 .
- the PHR data server 302 may be any suitable platform including processing, memory and data storage capability to perform the functions herein described.
- the PHR data server 302 stores data entered by the patient within a data structure configured within the storage portion of the PHR data server 302 .
- a secure interface or EHIS queue securely couples the PHR server 302 and the EHIS data server 306 for communication of data and information from the PHR data server 302 to the EHIS data server 306 .
- the EHIS queue provides a real-time secure communication link for information moving from the PHR data server 302 to the EHIS data server 306 .
- This queue is used to transfer information for secure messaging and self-service options.
- the PHR data server 302 forwards information to the EHIS queue.
- Information in the EHIS queue is then processed appropriately by the EHIS data server 306 .
- the EHIS data server 306 is a single data repository structured to support both the separation and the sharing of data.
- the EHIS data server 306 may receive information from existing outpatient and inpatient data management systems via interfaces or from various integrated applications.
- the EHIS data server 306 may be configured to organize information into a consistent whole to provide a longitudinal patient record.
- the EHIS data server 306 may be linked to manage all aspects of a patient's hospital health status and care and to support effective management of patient lists, results inquiry management, complete clinical documentation, physician order entry with decision support, nursing workflow and documentation, and discharge planning.
- the EHIS data server 306 may further be configured to support the inclusion of problem lists, order communications, results reporting, pharmacy management, quick documentation, clinical messaging and communication. Additionally, the EHIS data server 306 may be configured to manage referral information, up-to-date progress notes, lab results, discharge instructions, portions of a patient's record, and emergency summary cards.
- a suitable data management product that may be adapted as the EHIS data server 306 is the Epicenter® Enterprise Data Repository and related suite of products available from Epic Systems Corporation of Madison, Wis.
- the specific configuration of the scheduling server 308 is also not particular to the structure and function of the present invention.
- the scheduling server may be any suitable platform that includes a processor, memory and data storage capability to perform the functions herein described. These functions may alternatively be performed by the EHIS server 306 .
- the scheduling server 308 may be a separate component from the EHIS server 306 , or it may be one in the same.
- An electronic network couples the PHR data server 302 , the EHIS server 306 , and the scheduling server 308 to a patient interface. While FIG. 3 depicts the scheduling server 308 as a separate component, as mentioned above, an alternative embodiment may include the scheduling server as part of the EHIS server 306 , as represented by the phantom line 304 in FIG. 3 .
- the electronic network may include the Internet 316 or another suitable data network.
- the system servers are electronically linked to the Internet by a web server 312 in a highly secure dual firewall configuration. In this arrangement, a primary fire wall 314 protects the web server 312 and a secondary fire wall 310 protects the PHR data server 302 , EHIS server 306 , and scheduling server 308 . Additionally, the PHR data server 302 , EHIS server 306 , and scheduling server 308 are also electrically interconnected.
- the patient interface is preferably configured as a web page displayed within a web browser running on a suitable platform, and is further preferably configured as a personalized Personal Health Portal (PHP) web page 318 providing the patient with patient-specific information and links to the features and services offered by the invention.
- PHP Personal Health Portal
- the web server 312 may be any suitable web server platform containing routines for displaying the PHP web page 318 and for managing online communication between a user logged in via an associated PHP web page 318 , the PHR data server 302 , and the EHIS data server 306 .
- the scheduling ticket could be sent to the facility via a secure web-access application ensuring that the request will remain confidential.
- the self-scheduling functionality is equipped with a dynamic feedback system, which prevents patients from abusing their self-scheduling capabilities. For instance, if a patient schedules multiple appointments and does not show up for the appointments, the patient could be banned from scheduling any more appointments over the Internet.
- the facilities, departments, and providers are able to determine which patients can use scheduling tickets and which time slots they can schedule in at different levels, so that they do not lose control of their daily schedules.
Abstract
A method of allowing patients to schedule their own appointments on a computerized scheduling system. The method includes operating the computerized scheduling system to provide a first set of rules associated with a first entity, the first entity being a collection of healthcare providers. The first set of rules regulates self-scheduling by patients applicable to all appointments. The computerized scheduling system further provides at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients, and defines a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional sets of rules. The computerized scheduling system further communicates directly with the patient over the Internet to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers and approves or denies the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
Description
- This application is a continuation of U.S. patent application Ser. No. 09/829,292, entitled “Rules Based Ticketing For Self-Scheduling Of Appointments,” filed Apr. 9, 2001, which claims priority to U.S. Provisional Application Ser. No. 60/263,651, entitled “Rules Based Ticketing For Self-Scheduling Of Appointments,” filed Jan. 23, 2001 (attorney docket no. 29794/37078) and U.S. Provisional Application Ser. No. 60/214,219, entitled “Integrated Patient and Enterprise Health Record System,” filed Jun. 26, 2000 (attorney docket no. 29794/36547), the disclosures of which are hereby expressly incorporated herein by reference.
- The present invention relates generally to health record management, and more particularly, the present invention relates to a rules-based scheduling system to allow a healthcare facility to control appointments scheduled through the Internet with “scheduling tickets” that incorporate a variety of rules.
- Many attempts have previously been made to streamline the process of scheduling appointments for patients in the healthcare industry. From a healthcare organization's point of view the most efficient method is to let patients schedule appointments themselves. However, until the advent of the Internet, this solution was not feasible. Now, the Internet has provided patients with direct access to an organization through the web, thereby opening up the possibility of self-scheduling. Nevertheless, self-scheduling over the Internet presents unique and interesting problems. For example, there are always security issues when dealing with medical information on the Internet. Also, if the system is not implemented properly, patients could abuse the system. Furthermore, Healthcare providers, such as doctors, nurses, and surgeons often have concerns that they are losing control of their daily schedules if they allow patients to schedule their own appointments.
- The existing scheduling solutions are based on messaging or very restricted access. These solutions allow patients to enter some limited information concerning an appointment. Some examples are: (1) which provider the patient wants to see, (2) the day and time the patient wants to be seen, (3) some of the patient's insurance information, and (4) a few other types of information relevant to scheduling.
- After requests were submitted in the previous systems, workers at the clinics were then required to review each of the requests and contact every patient individually to inform him or her whether or not the request was granted. While this process is somewhat convenient for the patients, it does not automatically schedule appointments or immediately enter the data into the organization's system. Rather, it relies on human intervention to evaluate the requests and contact the patients when the decision to schedule the appointment has been made.
- There is a demonstrated need for healthcare organizations to allow the full scheduling of appointments over the Internet in an automated process that gives patients immediate results and eliminates the need for employees of the facility to review each request for an appointment. None of the previous systems satisfied this need.
- One embodiment of the invention relates to a method of allowing patients to schedule their own appointments on a computerized scheduling system. The method includes operating the computerized scheduling system to provide a first set of rules associated with a first entity, the first entity being a collection of healthcare providers. The first set of rules regulates self-scheduling by patients applicable to all appointments. The computerized scheduling system further provides at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients, and defines a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional sets of rules. The computerized scheduling system further communicates directly with the patient over the Internet to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers and approves or denies the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
- Another embodiment of the invention relates to computer-implemented system for allowing patients to schedule their own appointments. The system includes a rule set database. The database includes a first set of rules associated with a first entity, the first entity being a collection of healthcare providers, the first set of rules regulating self-scheduling by patients applicable to all appointments, and at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients. The system further includes a relationship processing engine configured to receive and implement a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional set of rules. The system yet further includes a patient scheduling interface configured to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers, and an appointment scheduling engine configured to approve or deny the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
- Yet another embodiment of the invention relates to a computer-implemented method for allowing patients to schedule their own appointments. The method includes receiving a request to schedule a medical appointment of a requested type with a particular healthcare provider within a collection of healthcare providers and accessing a patient accessible medical record database, the medical record database including a plurality of longitudinal patient records. Each longitudinal patient record is associated with a single patient and includes a medical history data structure including a patient record generated by a healthcare entity including clinical information sufficient for the delivery of medical services to those patients. The method further includes generating an approval or denial of the request to schedule the medical appointment received from the patient based on the longitudinal patient record associated with the patient submitting the request to schedule the medical appointment.
- Alternative examples and other exemplary embodiments relate to other features and combinations of features as may be generally recited in the claims.
- The invention will become more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like elements, in which:
-
FIG. 1 is a flow chart representation of the path that the system would take when a patient attempted to schedule an appointment directly from the system. -
FIG. 2 is a flowchart that illustrates the process by which a user logged in to his Patient Health Portal (PHP) Web Page can schedule an appointment that has been pre-qualified. -
FIG. 3 is a flowchart illustrating the components and connections from the enterprise healthcare information management system through the Internet and on to the patient via a web page portal. - Before describing in detail the particular improved system and method, it should be observed that the invention includes, but is not limited to, a novel structural combination of conventional data/signal processing components and communications circuits, and not in particular detailed configurations thereof. Accordingly, the structure, methods, functions, control, and arrangement of conventional components and circuits have, for the most part, been illustrated in the drawings by readily understandable block representations and schematic diagrams, in order not to obscure the disclosure with structural details which will be readily apparent to those skilled in the art, having the benefit of the description herein. Further, the invention is not limited to the particular embodiments depicted in the exemplary diagrams, but should be construed in accordance with the language in the claims.
- According to a preferred embodiment of the invention a system that enables a patient to use a pre-authorized or a user initiated scheduling process that utilizes hierarchically-layered rules. The system further provides dynamic feedback to self-schedule appointments with a user's preferred clinics and providers in a confidential and secure manner.
- The rules based ticketing system for self-scheduling provides healthcare clinics and providers the ability to manage and control patient appointment utilization. For several reasons, it is very desirable from a healthcare provider's perspective to allow patients to schedule their own appointments. It is also desirable from a patient's perspective to be able to independently schedule their own appointments at their convenience through the Internet. A system according to the preferred embodiments of the invention satisfies the desires of both parties.
- A rules-based scheduling system according to a preferred embodiment of the invention allows a facility to control appointments scheduled through the Internet with “scheduling tickets” that incorporate a variety of rules and triggers. These rules can be defined as many things. Some examples that may be included are:
-
- (1) The type of patient. The system checks if the patient has any special conditions, such as being diabetic or undergoing cancer therapy, that would allow or disallow a patient to self-schedule. A clinic may not want certain patient types scheduling their own appointments because some patients need special consideration.
- (2) A patient's Insurance. The system checks to ensure that patients have insurance or other methods to cover their medical expenses.
- (3) Referral information. The system checks to ensure that patients do not have any outstanding referrals for that type of visit so that appointments are not duplicated.
- (4) Previous visits of a certain type. The system checks if patients are due for or require a follow up appointment. For example, a minor operation may warrant a return visit to remove the sutures.
- (5) Provider preferences. The system takes into account when providers can or want to see certain types of patients. For example, if a provider does not want to schedule physicals in the morning, the system could reject any ticket submission from patients to have physicals scheduled in the morning for this particular provider.
- (6) Patient preferences. The system takes into account when patients want to be seen by their providers.
- (7) Past patient history. The system checks if factors exist that may change whether or not a patient can self-schedule. For instance, a system could deny a patient the right to self-schedule because he has a history of more than 20% no-shows or cancellations.
- (8) Copay requirements. The system checks if a copay by the patient is required for the appointment. Accordingly, the system requires that a patient must pay the copay when he or she schedules the appointment.
- These rules could further be set up as a layered hierarchy. They could be specified at various levels which include, but are not limited to:
-
- (1) System level or facility level. This is the least specific level. The settings at this level pertain to an entire healthcare facility.
- (2) Department level. This level is more specific than the system level. The settings at this level pertain to all providers who work in a specific department of a facility.
- (3) Provider level. This level is very specific. The settings at this level pertain to only a specific provider.
- (4) Rule level. The specificity of this level could vary, depending on how a facility has set up the system. For example, one facility could set up the rules level settings as overriding settings at the provider level, while another facility could set up settings at the provider level as overriding the settings at the rules level. The settings at this level pertain to only a specific rule.
- Rules set at more specific levels could override rules set at less-specific levels. For example, if an entire clinic's system is configured to allow diabetic patients to self-schedule using pre-authorized scheduling tickets, but a diabetic patient attempts to use a scheduling ticket to schedule an appointment in a department that does not allow diabetic patients to self-schedule, the patient would not be able to self-schedule in that department because the department level is more specific than the system level, so it takes precedence. However, diabetic patients in departments that allow diabetic patients to use self-scheduling or in departments with no specific rules for diabetic patients could still schedule an appointment with a ticket.
- Different rules could also be set up to override other rules. For example, provider preference rules could be set up to override patient preference rules when a patient is using a scheduling ticket to make an appointment. Also, the past patient history rules could be defined to override all other rules, because if a patient abuses self-scheduling, a facility would most likely not want that patient to be scheduling appointments, regardless of what the other rules dictate.
- Furthermore, these rules can be dynamic in their ability to change over time. For example, the system could revoke a patient's ability to self-schedule if the patient abuses the system. Therefore, if a patient self-scheduled three appointments and did not show up for them, the system could automatically change the patient's status from ‘able to self schedule’ to ‘unable to self schedule.’
- While the invention is further described in terms of several preferred embodiments, it will be appreciated that the invention is not limited in scope to the embodiments herein described. Many modifications, alterations and additions may be made without departing from the fair scope of the invention.
- Referring to
FIG. 1 of the drawings, a flow chart representation is shown of the path that the system would take when a patient attempted to schedule an appointment directly from the system. Through the system, a patient with access to self-scheduling can, either with a pre-authorized scheduling ticket or through a user initiated scheduling process, request an appointment with his or her clinic or provider. The self schedule request would then have to pass a series of checks, or rules, before it could be fulfilled. First, the system would run 104 a rules check to see 106 if the patient is authorized to self-schedule appointments. If the patient has the appropriate authorization, the system would then check 110 to see if a preauthorized scheduling ticket existed for the patient. If one existed, the system would offer 114 the patient time slots that met the ticket requirements. - If there were no pre-authorized ticket for the patient, he or she would enter an appointment search criteria manually 112. Then the system would verify that the patient was allowed to see the search results, whether the search results were obtained using the pre-authorized ticket or using search criteria initiated by the patient. The patient would then select 118 an appointment to schedule. The system would perform 120 one last check to make sure the patient was allowed to schedule the appointment and that the appointment was still available, and then the appointment would be made 124. If the specific appointment that the patient was trying to book was unavailable, the patient would be prompted 112 to enter scheduling information manually, and the process would start over.
- Again, if the scheduling ticket or the responses from the user initiated scheduling process pass all of the appropriate security checks, the system then can present the patient with a list of solutions that match his or her request. After the patient selects an
appointment 118, the system can perform 120 a final check to ensure that the patient is authorized to use the ticket to schedule the appointment and that the time slot is still available. If the request passes this security check, then the system can notify 124 the patient that he or she has successfully scheduled the appointment with his or her clinic or provider. If for any reason, a patient is not allowed to self-schedule, the system could be configured 108 to immediately give the patient the option to request an appointment, as opposed to actually scheduling one with a scheduling ticket. - As explained above, a patient can self-schedule an appointment with his or her clinic or provider using either a
pre-authorized scheduling ticket 114 or through a user initiatedscheduling process 112. As shown inFIG. 2 , a pre-authorized scheduling ticket is an electronic ticket that is given to the patient via their electronic health record managed by their physician. This record is stored on a computer server and is referenced by the Internet based scheduling system to limit the patient's ability to schedule appointments to what is described 204 by the ticket. - An electronic database of scheduling tickets (also referred to as access tickets) would be created.
Attributes 204 of records in this database would include the healthcare provider who authorized the ticket, the services the ticket entitles the patient to schedule (e.g. one follow up visit within the next two months), and the patient identifier for the patient the ticket is for. The ticket also has an attribute that describes its current status (unused, appointment made, appointment completed). - These pre-authorized scheduling tickets would be automatically created during the physician's documentation of a clinical encounter with the patient. Typically a doctor will document when a patient should return, in follow up of a problem (e.g. to check on how well a medication is working to control the patient's blood pressure) or for a follow up procedure (e.g. suture removal). When initially created, the ticket's status is set to “unused.”
- Referring again to
FIG. 2 , the flowchart illustrates the process by which a user logged in to his Patient Health Portal (PHP) Web Page can schedule an appointment that has been pre-qualified. The structure and functionality of a PHP Web Page is described in the commonly assigned United States patent application (attorney docket no. 29794/36547A) entitled “Integrated Patient and Enterprise Health Record System,” the disclosure of which is hereby expressly incorporated herein by reference. When the user clicks the Schedule Appointment option, the Web Server queries 202 the Scheduling Server to see if there are any pre-qualified appointments available for the current user. If there are, the Web Server updates 208 the PHP Web Page with the available appointment information. The user can then select 210 an appointment to schedule, and indicates date, time, and locations (selections may be limited by information in the Scheduling Ticket database). The Web Server then obtains 214 appointment times available within the selected range and displays 218 them, whereupon the user can either select a time, change the search, or cancel. When a user completes the appointment scheduling process, the Web Server notifies 224 the Scheduling Ticket database that the appointment has been scheduled and the ticket for the current user is updated 226 accordingly. The Scheduling Ticket database will then track whether the appointment has been cancelled or completed, and will update the corresponding pre-qualified appointment record accordingly. - As previously mentioned, in addition to direct provider created tickets, patients may schedule an appointment through a user initiated
scheduling process 112. An example of when this may be utilized is when a provider places a patient on a disease management protocol. These protocols might call for a patient to be seen with a certain frequency for specified types of visits. These protocols would automatically grant authority for the patients that conform to the limitations of the protocols. This process could be used independently or in combination with other insurance information available for the patient and represents the limitations that would be imposed on a patient self-scheduling through the web. - To provide additional control for healthcare providers, the system may be designed to apply a more restricted set of rules to patients scheduling appointments through the user initiated scheduling process. For example, a healthcare provider may reserve only a few time slots per week for patients to schedule appointments through this process. They may additionally limit those appointments to very short durations for limited purposes, such as consultations or the administration of simple tests. Another example is that the system could restrict a patient from selecting a provider or a department. Instead, the system would pick an appropriate provider or department from a pre-determined list that is driven by the patient as a parameter.
- The patient would be provided access to a self scheduling application (e.g. a web site or a computer application for personal use, possibly running on a home computer, personal digital assistant (PDA) or cellular telephone) which would allow them to schedule the appointment.
- This self-scheduling computer application would identify and authenticate the patient and read the database of electronic tickets to determine what self-scheduling limits exist for the patient. The self-scheduling application then allows the patient to select appointments that are within the limitation of the ticket.
- Once an appointment is made, it is associated with the ticket. The ticket is then marked as “appointment made.” When the appointment is kept, the ticket is marked as “appointment completed” and then subsequently destroyed or retained for historical analysis. If the patient or provider cancels the appointment, the ticket's status would revert to the “unused status.”
- The integration of the self-scheduling component into an overall healthcare management system is shown in
FIG. 3 . A completely integrated system provides patients with secure, real-time access to their Personal Health Record and an Enterprise Health Information System (PHR and EHIS, respectively). Access may be provided by way of theInternet 316 and via a Personal Health Portal (PHP)web page 318. From the securePHP web page 318, patients can view information created and maintained by their health care providers and their affiliated staff. The patients can also request services and information from their health care providers and affiliated staff, directly access EHIS-related services, such as scheduling an appointment, paying a bill, enrolling in a class, completing insurance and other forms, and viewing information and Internet services that are relevant to their particular health status. - In a preferred embodiment of the invention a patient health
record data server 302, including a machine readable media having a data structure containing patient-created data, is coupled by an electronic network with a patient interface. The electronic network may be theInternet 316 and the patient interface may be a suitable Internet access device including a browser for supporting apersonalized web page 318. A secure interface securely couples, in real-time, the patienthealth record server 302 to an enterprisehealth record system 304 for providing access by the patient to patient-related data retained within the enterprisehealth record system 304. Thus, the patient, via the patient interface, may access the patienthealth record server 302 for manipulating the patient-created data and for accessing the patient-related data from the enterprisehealth record system 304. - Referring again to
FIG. 3 of the drawings, the system includes a Patient Health Record (PHR)data server 302, anEHIS data server 306, and a self-scheduling server 308. ThePHR data server 302 may be any suitable platform including processing, memory and data storage capability to perform the functions herein described. ThePHR data server 302 stores data entered by the patient within a data structure configured within the storage portion of thePHR data server 302. A secure interface or EHIS queue securely couples thePHR server 302 and theEHIS data server 306 for communication of data and information from thePHR data server 302 to theEHIS data server 306. The EHIS queue provides a real-time secure communication link for information moving from thePHR data server 302 to theEHIS data server 306. This queue is used to transfer information for secure messaging and self-service options. In response to information received from thePHP web page 318, thePHR data server 302 forwards information to the EHIS queue. Information in the EHIS queue is then processed appropriately by theEHIS data server 306. - While the specific configuration of the
EHIS data server 306 is not particular to the structure and function of the present invention, preferably, theEHIS data server 306 is a single data repository structured to support both the separation and the sharing of data. As such, theEHIS data server 306 may receive information from existing outpatient and inpatient data management systems via interfaces or from various integrated applications. TheEHIS data server 306 may be configured to organize information into a consistent whole to provide a longitudinal patient record. For example, theEHIS data server 306 may be linked to manage all aspects of a patient's hospital health status and care and to support effective management of patient lists, results inquiry management, complete clinical documentation, physician order entry with decision support, nursing workflow and documentation, and discharge planning. - The
EHIS data server 306 may further be configured to support the inclusion of problem lists, order communications, results reporting, pharmacy management, quick documentation, clinical messaging and communication. Additionally, theEHIS data server 306 may be configured to manage referral information, up-to-date progress notes, lab results, discharge instructions, portions of a patient's record, and emergency summary cards. A suitable data management product that may be adapted as theEHIS data server 306 is the Epicenter® Enterprise Data Repository and related suite of products available from Epic Systems Corporation of Madison, Wis. - The specific configuration of the
scheduling server 308 is also not particular to the structure and function of the present invention. However, the scheduling server may be any suitable platform that includes a processor, memory and data storage capability to perform the functions herein described. These functions may alternatively be performed by theEHIS server 306. Thus, thescheduling server 308 may be a separate component from theEHIS server 306, or it may be one in the same. - An electronic network couples the
PHR data server 302, theEHIS server 306, and thescheduling server 308 to a patient interface. WhileFIG. 3 depicts thescheduling server 308 as a separate component, as mentioned above, an alternative embodiment may include the scheduling server as part of theEHIS server 306, as represented by thephantom line 304 inFIG. 3 . The electronic network may include theInternet 316 or another suitable data network. The system servers are electronically linked to the Internet by aweb server 312 in a highly secure dual firewall configuration. In this arrangement, aprimary fire wall 314 protects theweb server 312 and asecondary fire wall 310 protects thePHR data server 302,EHIS server 306, andscheduling server 308. Additionally, thePHR data server 302,EHIS server 306, andscheduling server 308 are also electrically interconnected. - Patients access the system by logging into the
web server 312 via the patient interface. The patient interface is preferably configured as a web page displayed within a web browser running on a suitable platform, and is further preferably configured as a personalized Personal Health Portal (PHP)web page 318 providing the patient with patient-specific information and links to the features and services offered by the invention. Theweb server 312 may be any suitable web server platform containing routines for displaying thePHP web page 318 and for managing online communication between a user logged in via an associatedPHP web page 318, thePHR data server 302, and theEHIS data server 306. - Rules-based scheduling tickets solve the many problems that the healthcare industry has encountered. First, the scheduling ticket could be sent to the facility via a secure web-access application ensuring that the request will remain confidential. Furthermore, the self-scheduling functionality is equipped with a dynamic feedback system, which prevents patients from abusing their self-scheduling capabilities. For instance, if a patient schedules multiple appointments and does not show up for the appointments, the patient could be banned from scheduling any more appointments over the Internet. Finally, because of the hierarchical rules that a facility could enact, the facilities, departments, and providers are able to determine which patients can use scheduling tickets and which time slots they can schedule in at different levels, so that they do not lose control of their daily schedules.
- The invention has been described in terms of several preferred embodiments. It will be appreciated that the invention may otherwise be embodied without departing from the fair scope of the invention defined by the following claims.
Claims (34)
1. A method of allowing patients to schedule their own appointments on a computerized scheduling system comprising the steps of operating the computerized scheduling system to:
(a) provide a first set of rules associated with a first entity, the first entity being a collection of healthcare providers, the first set of rules regulating self-scheduling by patients applicable to all appointments;
(b) provide at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients;
(c) define a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional sets of rules;
(d) communicate directly with the patient over the Internet to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers; and
(e) approve or deny the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
2. The method of claim 1 , wherein the at least one additional set of rules includes a set of rules associated with a specific healthcare provider entity, the specific healthcare provider entity being a subset of the collection of healthcare providers entity and
wherein the relationship dictates that the set of rules associated with the specific healthcare provider entity supersedes the first set of rules where there is a detected conflict.
3. The method of claim 2 , wherein the at least one additional set of rules include a set of rules associated with a healthcare facility entity, the healthcare facility entity being associated the collection of healthcare providers entity and
wherein the relationship dictates that the set of rules associated with the collection of healthcare providers entity supersedes the set of rules associated with the healthcare facility entity.
4. The method of claim 1 , wherein providing at least one additional set of rules includes associating each additional set of rules with an entity and requiring that each entity is either a subset or a superset of at least one other entity.
5. The method of claim 4 , wherein defining a relationship includes requiring that sets of rules associated with a first entity that is a subset of a second entity supersede the set of rules associated with the second entity where there is a conflict between sets of rules.
6. The method of claim 4 , wherein at least one additional set of rules is associated with a master entity, the master entity being required to be a superset of all other entities.
7. The method of claim 4 , wherein at least one additional set of rules is associated with a patient in a healthcare system entity, the patient entity being required to be a subset at least a healthcare provider entity.
8. The method of claim 1 , wherein each rule within each set of rules is associated with a rule type and
wherein the relationship further dictates applicability of one or more of the rules having a first rule type based on a detected conflict between at least one rule having a first rule type and at least a second rule having a second rule type.
9. A computer-implemented system for allowing patients to schedule their own appointments, comprising:
a rule set database, including
a first set of rules associated with a first entity, the first entity being a collection of healthcare providers, the first set of rules regulating self-scheduling by patients applicable to all appointments, and
at least one additional set of rules, each additional set of rules associated with an entity, the additional sets of rules regulating self-scheduling by patients;
a relationship processing engine configured to receive and implement a relationship between the first set of rules and the at least one additional set of rules wherein the relationship dictates applicability of one or more of the rules in the rule sets based on a detected conflict between at least one rule in the first set of rules and at least one rule in one or more of the additional set of rules;
a patient scheduling interface configured to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within the collection of healthcare providers; and
an appointment scheduling engine configured to approve or deny the request to schedule the medical appointment received from the patient based on application of the first set of rules and the at least one additional set of rules in view of the relationship.
10. The system of claim 9 , wherein the at least one additional set of rules includes a set of rules associated with a specific healthcare provider entity, the specific healthcare provider entity being included in the collection of healthcare providers entity and
wherein the relationship dictates that the set of rules associated with the specific healthcare provider entity supersedes the first set of rules where there is a detected conflict.
11. The system of claim 10 , wherein the at least one additional set of rules include a set of rules associated with a healthcare facility entity, the healthcare facility entity being associated the collection of healthcare providers entity, wherein the relationship dictates that the set of rules associated with the collection of healthcare providers entity supersedes the set of rules associated with the healthcare facility entity.
12. The system of claim 9 , wherein providing at least one additional set of rules includes associating each additional set of rules with an entity and requiring that each entity is either a subset or a superset of at least one other entity.
13. The system of claim 12 , wherein defining a relationship includes requiring that sets of rules associated with a first entity that is a subset of a second entity supersede the set of rules associated with the second entity where there is a conflict between sets of rules.
14. The system of claim 12 , wherein at least one additional set of rules is associated with a master entity, the master entity being required to be a superset of all other entities.
15. The system of claim 12 , wherein at least one additional set of rules is associated with a patient in a healthcare system entity, the patient entity being required to be a subset to at least a healthcare provider entity.
16. The system of claim 9 , wherein each rule within each set of rules is associated with a rule type and wherein the relationship further dictates applicability of one or more of the rules based on a detected conflict between at least one rule having a first rule type and at least a second rule having a second rule type.
17. A computer-implemented system for allowing patients to schedule their own appointments, comprising:
a patient accessible medical record database, the medical record database including a plurality of longitudinal patient records, each longitudinal patient record being associated with a single patient and including
a medical history data structure including a patient record generated by a healthcare entity including clinical information sufficient for the delivery of medical services to those patients;
a patient scheduling interface configured to receive a request to schedule a medical appointment of a requested type with a particular healthcare provider within a collection of healthcare providers; and
an appointment scheduling engine configured to approve or deny the request to schedule the medical appointment received from the patient based on the longitudinal patient record associated with the patient submitting the request to schedule the medical appointment.
18. The system of claim 17 , wherein the medical history data structure further includes at least one of lab results, physician order entry with decision support, and nursing workflow and documentation.
19. The system of claim 17 , wherein the longitudinal patient record further includes a patient information data structure containing patient-created data.
20. The system of claim 17 , wherein the medical history data structure includes a preauthorized scheduling ticket configured to facilitate approval of the request to schedule the medical appointment received from the patient.
21. The system of claim 17 , wherein the appointment scheduling engine is configured to approve or deny the request to schedule the medical appointment based on a medical protocol indicated in the medical history data structure.
22. The system of claim 21 , wherein the appointment scheduling engine is configured to approve a plurality of requests to schedule a medical appointment based on the medical protocol indicated in the medical history data structure.
23. The system of claim 17 , wherein the appointment scheduling engine is configured to grant or deny requests to schedule medical appointments based on one or more sets of rules associated with the healthcare entity, the set of rules regulating self-scheduling by patients applicable to all appointments, the set of rules regulating self-scheduling based on data contained in the medical history data structure.
24. The system of claim 23 , wherein the data contained in the medical history data structure upon which the set of rules regulate self-scheduling includes at least a clinical diagnosis made by a healthcare provider.
25. The system of claim 23 , wherein the healthcare entity is at least one of a healthcare provider, an association of healthcare providers, and a healthcare facility.
26. A computer-implemented method for allowing patients to schedule their own appointments, comprising:
receiving a request to schedule a medical appointment of a requested type with a particular healthcare provider within a collection of healthcare providers; and
accessing a patient accessible medical record database, the medical record database including a plurality of longitudinal patient records, each longitudinal patient record being associated with a single patient and including
a medical history data structure including a patient record generated by a healthcare entity including clinical information sufficient for the delivery of medical services to those patients; and
generating an approval or denial of the request to schedule the medical appointment received from the patient based on the longitudinal patient record associated with the patient submitting the request to schedule the medical appointment.
27. The system of claim 26 , wherein the medical history data structure further includes at least one of lab results, physician order entry with decision support, and nursing workflow and documentation.
28. The system of claim 26 , wherein the longitudinal patient record further includes a patient information data structure containing patient-created data.
29. The method of claim 26 , wherein the medical history data includes a preauthorized scheduling ticket configured to facilitate approval of the request to schedule the medical appointment received from the patient.
30. The method of claim 26 , wherein the approval or denial is generated based on a medical protocol indicated in the medical history data structure.
31. The method of claim 30 , generating an approval or denial includes generating the approval or denial for a plurality of requests to schedule a medical appointment based on the medical protocol indicated in the medical history data structure.
32. The method of claim 26 , wherein the approval or denial is generated based on one or more sets of rules associated with the healthcare entity, the set of rules regulating self-scheduling by patients applicable to all appointments, the set of rules regulating self-scheduling based on data contained in the medical history data structure.
33. The method of claim 32 , wherein the data contained in the medical history data structure upon which the set of rules regulate self-scheduling includes at least a clinical diagnosis made by a healthcare provider.
34. The method of claim 32 , wherein the healthcare entity is at least one of a healthcare provider, an association of healthcare providers, and a healthcare facility.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/971,420 US20080109262A1 (en) | 2000-06-26 | 2008-01-09 | Rules Based Ticketing For Self-Scheduling of Appointments |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US21429000P | 2000-06-26 | 2000-06-26 | |
US26365101P | 2001-01-23 | 2001-01-23 | |
US09/829,292 US7337123B2 (en) | 2000-06-26 | 2001-04-09 | Rules based ticketing for self-scheduling of appointments |
US11/971,420 US20080109262A1 (en) | 2000-06-26 | 2008-01-09 | Rules Based Ticketing For Self-Scheduling of Appointments |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/829,292 Continuation US7337123B2 (en) | 2000-06-26 | 2001-04-09 | Rules based ticketing for self-scheduling of appointments |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080109262A1 true US20080109262A1 (en) | 2008-05-08 |
Family
ID=39712727
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/829,292 Expired - Lifetime US7337123B2 (en) | 2000-06-26 | 2001-04-09 | Rules based ticketing for self-scheduling of appointments |
US11/971,420 Abandoned US20080109262A1 (en) | 2000-06-26 | 2008-01-09 | Rules Based Ticketing For Self-Scheduling of Appointments |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/829,292 Expired - Lifetime US7337123B2 (en) | 2000-06-26 | 2001-04-09 | Rules based ticketing for self-scheduling of appointments |
Country Status (1)
Country | Link |
---|---|
US (2) | US7337123B2 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080300918A1 (en) * | 2007-05-29 | 2008-12-04 | Commercenet Consortium, Inc. | System and method for facilitating hospital scheduling and support |
US20090076832A1 (en) * | 2007-09-14 | 2009-03-19 | Collins Christopher M | Inmate privilege kiosk methods, systems and user interface |
US20100057513A1 (en) * | 2008-08-26 | 2010-03-04 | Mckesson Financial Holdings Limited | Automatic appointment scheduler with hybrid timeline |
US20100070303A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Consumer portal for healthcare appointments across practice groups |
US20100070295A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Centralized marketplace for healthcare appointments across practice groups |
US20100070297A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Data synchronization for booking of healthcare appointments across practice groups |
US20100070294A1 (en) * | 2008-09-15 | 2010-03-18 | Mckesson Financial Holdings Limited | Creating and communicating staffing assignments |
US20110161128A1 (en) * | 2009-12-31 | 2011-06-30 | Mckesson Financial Holdings Limited | Scheduling and Assigning Units of Work |
US20120232946A1 (en) * | 2011-03-08 | 2012-09-13 | Charles Daniel Cocanougher | Methods and Systems for a Multi-Party Customizable Calendar |
WO2015005963A1 (en) * | 2013-07-09 | 2015-01-15 | Yi Song | Integrated health measurement and food service system |
US10535431B2 (en) * | 2014-09-17 | 2020-01-14 | Change Healthcare Holdings, Llc | System and method for dynamic schedule aggregation |
US20220059198A1 (en) * | 2013-03-14 | 2022-02-24 | Alterg, Inc. | Systems and methods for management and scheduling of differential air pressure and other unweighted or assisted treatment systems |
US20220189625A1 (en) * | 2020-12-15 | 2022-06-16 | Orchid Exchange Inc. | Systems and methods for providing virtual health services |
Families Citing this family (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090313049A1 (en) * | 1999-12-18 | 2009-12-17 | Raymond Anthony Joao | Apparatus and Method for Processing and/or Providing Healthcare Information and/or Healthcare-Related Information |
US7174303B2 (en) * | 2000-07-31 | 2007-02-06 | Uappoint, Inc | Customer driven, sponsor controlled network-based graphical scheduling system and method |
WO2002015080A2 (en) * | 2000-08-10 | 2002-02-21 | Lumenos | Managing health care resources |
US7617114B1 (en) | 2000-08-10 | 2009-11-10 | Wellpoint Inc. | Health care reimbursement |
US20020123879A1 (en) * | 2001-03-01 | 2002-09-05 | Donald Spector | Translation system & method |
US20020165734A1 (en) * | 2001-05-01 | 2002-11-07 | Caregroup Healthcare System | System and method for automating the completion of complex tasks |
US7689441B1 (en) * | 2001-08-20 | 2010-03-30 | Siemens Medical Solutions Health Services Corporation | Integrated order and scheduling in a healthcare administration system |
US20030088479A1 (en) * | 2001-10-01 | 2003-05-08 | Wooten Carl E. | Online scheduling system |
US20040006496A1 (en) * | 2002-02-07 | 2004-01-08 | Christian Nickerson | Electronic waiting room |
US20030229516A1 (en) * | 2002-02-07 | 2003-12-11 | Christian Nickerson | System and method for rapid claims submission and adjudication |
US7702523B2 (en) * | 2002-04-03 | 2010-04-20 | Joseph Sameh | Website messaging system |
US7979294B2 (en) * | 2002-07-31 | 2011-07-12 | Epic Systems Corporation | System and method for providing decision support to appointment schedulers in a healthcare setting |
US11335446B2 (en) | 2002-12-06 | 2022-05-17 | Quality Healthcare Intermediary, Llc | Method of optimizing healthcare services consumption |
US7711577B2 (en) * | 2002-12-06 | 2010-05-04 | Dust Larry R | Method of optimizing healthcare services consumption |
US20140200907A1 (en) * | 2013-01-16 | 2014-07-17 | American Health Data Institute, Inc. | Method of optimizing healthcare services consumption |
US20040268210A1 (en) * | 2003-06-12 | 2004-12-30 | Tariq Gul | Online doctors appointment |
DE102004047958A1 (en) * | 2003-10-01 | 2006-03-16 | Siemens Ag | Optimized medical examination schedule creating or updating method for patient, involves creating attributes database, and outputting either error free optimal examination schedule or error indication to user |
US20050102245A1 (en) * | 2003-11-07 | 2005-05-12 | International Business Machines Corporation | System, method, and service for negotiating schedules while preserving privacy through a shared representation |
US8620711B2 (en) * | 2003-11-26 | 2013-12-31 | Verizon Business Global Llc | Inmate visitation scheduling and management |
US20050149357A1 (en) * | 2003-12-31 | 2005-07-07 | Doyel Jeffrey S. | Computerized system and method for generating and satisfying health maintenance item expectations in a healthcare environment |
US7904315B2 (en) * | 2004-01-16 | 2011-03-08 | Sullivan Robert J | Rules-based health care referral method and system |
US20050251421A1 (en) * | 2004-03-29 | 2005-11-10 | Calvin Chang | Providing video interpreting services |
US20060026051A1 (en) * | 2004-07-30 | 2006-02-02 | Idx Investment Corporation | System and method for directly scheduling health care patient appointments |
US20060047552A1 (en) * | 2004-08-24 | 2006-03-02 | Epic Systems Corporation | Smart appointment recall method and apparatus |
US7321860B2 (en) * | 2004-12-27 | 2008-01-22 | International Business Machines Corporation | Service offering for the delivery of information to the right receivers at the right time |
US8140370B2 (en) * | 2005-01-20 | 2012-03-20 | Epic Systems Corporation | System and method for reducing the steps involved in searching for available appointment times and scheduling appointments in a health care environment |
US8775207B2 (en) * | 2005-02-02 | 2014-07-08 | Siemens Medical Solutions Usa, Inc. | Integrated treatment planning and scheduling system |
US20060224719A1 (en) * | 2005-03-30 | 2006-10-05 | Integrated Informatics, Inc. | Operator simulator and non-invasive interface engine |
US20090164243A1 (en) * | 2005-09-30 | 2009-06-25 | J&H Enterprises, Llc | Electronic healthcare identification generation and reconciliation |
US20070078682A1 (en) * | 2005-09-30 | 2007-04-05 | John Zubak | Electronic healthcare identification and reconciliation |
US8825507B1 (en) * | 2006-02-03 | 2014-09-02 | Liveops, Inc. | System and method for self-scheduling of service representatives |
US7865386B2 (en) * | 2006-06-03 | 2011-01-04 | Sarkar Shyamal K | Appointment scheduling system |
US20080052110A1 (en) * | 2006-08-23 | 2008-02-28 | Cambridge Software Solutions Corp. | Referral system |
WO2008051961A2 (en) * | 2006-10-24 | 2008-05-02 | Mid-America Consulting Group | Invitee-participant matching for meeting scheduling |
US20090003583A1 (en) * | 2007-01-12 | 2009-01-01 | Wellpoint, Inc. | Method for enhancing call center performance |
US20080306797A1 (en) * | 2007-06-11 | 2008-12-11 | International Business Machines Corporation | Method and system for automated resource management and optimization |
US20090076854A1 (en) * | 2007-09-13 | 2009-03-19 | Globalcare, Inc. | Methods and systems for saving on healthcare costs |
CA2648513A1 (en) * | 2008-01-07 | 2009-07-07 | The Quantum Group, Inc. | Systems and methods for patient scheduling and record handling |
US8249895B2 (en) * | 2008-02-22 | 2012-08-21 | Epic Systems Corporation | Electronic health record system utilizing disparate record sources |
US20090216562A1 (en) * | 2008-02-22 | 2009-08-27 | Faulkner Judith R | Method and apparatus for accommodating diverse healthcare record centers |
US8271295B1 (en) * | 2008-07-23 | 2012-09-18 | Sprint Communications Company L.P. | Health clinic broker |
US8875055B1 (en) | 2008-11-28 | 2014-10-28 | Google Inc. | Interface for creating and viewing medical decision support rules |
US8224667B1 (en) | 2009-02-06 | 2012-07-17 | Sprint Communications Company L.P. | Therapy adherence methods and architecture |
US8682704B2 (en) * | 2011-01-03 | 2014-03-25 | Express Scripts, Inc. | Methods and systems for scheduling activity level based meetings |
US8670998B2 (en) | 2011-12-02 | 2014-03-11 | Mckesson Specialty Arizona Inc. | Notification services for patients |
US20130253972A1 (en) * | 2012-03-21 | 2013-09-26 | Opendoctors 247, Inc. | System and method for scheduling and ordering services |
WO2014078672A2 (en) * | 2012-11-15 | 2014-05-22 | Kinsey Edward Phillip Ii | Methods and systems for the sale of consumer services |
US20140172445A1 (en) * | 2012-12-13 | 2014-06-19 | Homan Hajbandeh | Bill Payment Risk Level Determination |
US20140222482A1 (en) * | 2013-02-05 | 2014-08-07 | Wal-Mart Stores, Inc. | Online appointment schedulers |
US11587688B2 (en) | 2014-03-27 | 2023-02-21 | Raymond Anthony Joao | Apparatus and method for providing healthcare services remotely or virtually with or using an electronic healthcare record and/or a communication network |
US10380181B1 (en) * | 2014-12-19 | 2019-08-13 | HCA Holdings, Inc. | Randomized compliant searching |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5642731A (en) * | 1990-01-17 | 1997-07-01 | Informedix, Inc. | Method of and apparatus for monitoring the management of disease |
US5732709A (en) * | 1994-05-23 | 1998-03-31 | Enact Health Management Systems | System for monitoring and reporting medical measurements |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
US6088429A (en) * | 1998-04-07 | 2000-07-11 | Mumps Audiofax, Inc. | Interactive telephony system |
US6208974B1 (en) * | 1997-12-30 | 2001-03-27 | Medical Management International, Inc. | Method and system for managing wellness plans for a medical care practice |
US20010051881A1 (en) * | 1999-12-22 | 2001-12-13 | Aaron G. Filler | System, method and article of manufacture for managing a medical services network |
US6345260B1 (en) * | 1997-03-17 | 2002-02-05 | Allcare Health Management System, Inc. | Scheduling interface system and method for medical professionals |
US20020059082A1 (en) * | 2000-11-15 | 2002-05-16 | Roger Moczygemba | Appointment setting and payment system and method |
US20020116220A1 (en) * | 2001-02-20 | 2002-08-22 | Glazier Alan Neil | Method and system for interactively researching and scheduling a medical procedure over a computer network |
US6757898B1 (en) * | 2000-01-18 | 2004-06-29 | Mckesson Information Solutions, Inc. | Electronic provider—patient interface system |
US6988128B1 (en) * | 2000-09-27 | 2006-01-17 | International Business Machines Corporation | Calendar events and calendar-driven application technique |
US7174303B2 (en) * | 2000-07-31 | 2007-02-06 | Uappoint, Inc | Customer driven, sponsor controlled network-based graphical scheduling system and method |
US20070167688A1 (en) * | 2005-12-19 | 2007-07-19 | Ross S M | Healthcare management systems and associated methods |
US20070168224A1 (en) * | 2005-11-22 | 2007-07-19 | Letzt Alan M | Advanced diabetes management system (adms) |
Family Cites Families (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US110059A (en) * | 1870-12-13 | Improvement in life-rafts | ||
US6283761B1 (en) * | 1992-09-08 | 2001-09-04 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US5997476A (en) * | 1997-03-28 | 1999-12-07 | Health Hero Network, Inc. | Networked system for interactive communication and remote monitoring of individuals |
US6249809B1 (en) * | 1993-08-30 | 2001-06-19 | William L. Bro | Automated and interactive telecommunications system |
US5748907A (en) * | 1993-10-25 | 1998-05-05 | Crane; Harold E. | Medical facility and business: automatic interactive dynamic real-time management |
US5833599A (en) * | 1993-12-13 | 1998-11-10 | Multum Information Services | Providing patient-specific drug information |
US5471382A (en) * | 1994-01-10 | 1995-11-28 | Informed Access Systems, Inc. | Medical network management system and process |
US5845253A (en) * | 1994-08-24 | 1998-12-01 | Rensimer Enterprises, Ltd. | System and method for recording patient-history data about on-going physician care procedures |
US5666492A (en) * | 1995-01-17 | 1997-09-09 | Glaxo Wellcome Inc. | Flexible computer based pharmaceutical care cognitive services management system and method |
US5758095A (en) * | 1995-02-24 | 1998-05-26 | Albaum; David | Interactive medication ordering system |
US5692125A (en) * | 1995-05-09 | 1997-11-25 | International Business Machines Corporation | System and method for scheduling linked events with fixed and dynamic conditions |
US5974389A (en) * | 1996-03-01 | 1999-10-26 | Clark; Melanie Ann | Medical record management system and process with improved workflow features |
US5740800A (en) * | 1996-03-01 | 1998-04-21 | Hewlett-Packard Company | Method and apparatus for clinical pathway order selection in a medical information system |
US5842976A (en) * | 1996-05-16 | 1998-12-01 | Pyxis Corporation | Dispensing, storage, control and inventory system with medication and treatment chart record |
GB2315577A (en) * | 1996-07-20 | 1998-02-04 | Ibm | Grouping of operations in a computer system |
US5924074A (en) | 1996-09-27 | 1999-07-13 | Azron Incorporated | Electronic medical records system |
US6029138A (en) * | 1997-08-15 | 2000-02-22 | Brigham And Women's Hospital | Computer system for decision support in the selection of diagnostic and therapeutic tests and interventions for patients |
AU2762899A (en) | 1998-02-17 | 1999-08-30 | Southern Research Institute | Patient data acquisition unit and data support system |
WO1999052025A2 (en) * | 1998-04-03 | 1999-10-14 | Triangle Pharmaceuticals, Inc. | Systems, methods and computer program products for guiding the selection of therapeutic treatment regimens |
US6275150B1 (en) * | 1998-07-14 | 2001-08-14 | Bayer Corporation | User interface for a biomedical analyzer system |
CA2350145C (en) | 1998-11-09 | 2005-02-08 | Lifestream Technologies, Inc. | Health monitoring and diagnostic device and network-based health assessment and medical records maintenance system |
WO2000029983A1 (en) | 1998-11-13 | 2000-05-25 | Kriese George Edward Jr | System and method of storing medical records and providing information based upon a user's medical records |
US6389454B1 (en) * | 1999-05-13 | 2002-05-14 | Medical Specialty Software | Multi-facility appointment scheduling system |
CA2373419A1 (en) * | 1999-06-01 | 2000-12-07 | Central Coast Patent Agency | An internet subscription system for providing appointment management for small businesses |
US7188073B1 (en) * | 1999-08-18 | 2007-03-06 | Tam Tommy H | On-line appointment system with electronic notifications |
US20030195774A1 (en) * | 1999-08-30 | 2003-10-16 | Abbo Fred E. | Medical practice management system |
US7171371B2 (en) * | 1999-09-03 | 2007-01-30 | Smg Trust | Method and system for providing pre and post operative support and care |
US20050055252A1 (en) * | 1999-12-10 | 2005-03-10 | Todd Robert P. | Method and system for online interactive appointments and reservations |
US7676384B2 (en) * | 2000-01-18 | 2010-03-09 | Medigenesis, Inc. | System and method for the automated presentation of system data to, and interaction with, a computer maintained database |
WO2001067731A2 (en) * | 2000-03-06 | 2001-09-13 | Metro One Telecommunications, Inc. | Directory assistance system capable of providing telephonic concierge services |
US20010039504A1 (en) * | 2000-03-15 | 2001-11-08 | Linberg Kurt R. | Individualized, integrated and informative internet portal for holistic management of patients with implantable devices |
US20020188478A1 (en) * | 2000-03-24 | 2002-12-12 | Joe Breeland | Health-care systems and methods |
EP1303823A4 (en) | 2000-04-25 | 2003-08-20 | Yong-Nam Park | A method of internet-based medical record database configuration and system thereof by mutual certification between patient and doctor |
JP2001338062A (en) * | 2000-05-26 | 2001-12-07 | Nec Corp | System for controlling electronic medical record and method for the same |
US7028178B2 (en) * | 2000-06-08 | 2006-04-11 | The Herff Jones Company Of Indiana, Inc. | Scheduling system and method including creating and/or changing a scheduling system by an administrator and making appointments employing the schedule conducted through a global computer network |
US7251610B2 (en) * | 2000-09-20 | 2007-07-31 | Epic Systems Corporation | Clinical documentation system for use by multiple caregivers |
US7056289B2 (en) * | 2000-11-06 | 2006-06-06 | The Johns Hopkins University | Method and system for outpatient monitoring |
US6678613B2 (en) * | 2001-09-21 | 2004-01-13 | International Business Machines Corporation | Method and apparatus for notifying a user of an appointment |
US7577573B2 (en) | 2001-12-12 | 2009-08-18 | General Electric Company | Medical support system |
-
2001
- 2001-04-09 US US09/829,292 patent/US7337123B2/en not_active Expired - Lifetime
-
2008
- 2008-01-09 US US11/971,420 patent/US20080109262A1/en not_active Abandoned
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5642731A (en) * | 1990-01-17 | 1997-07-01 | Informedix, Inc. | Method of and apparatus for monitoring the management of disease |
US5732709A (en) * | 1994-05-23 | 1998-03-31 | Enact Health Management Systems | System for monitoring and reporting medical measurements |
US6345260B1 (en) * | 1997-03-17 | 2002-02-05 | Allcare Health Management System, Inc. | Scheduling interface system and method for medical professionals |
US6208974B1 (en) * | 1997-12-30 | 2001-03-27 | Medical Management International, Inc. | Method and system for managing wellness plans for a medical care practice |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
US6088429A (en) * | 1998-04-07 | 2000-07-11 | Mumps Audiofax, Inc. | Interactive telephony system |
US20010051881A1 (en) * | 1999-12-22 | 2001-12-13 | Aaron G. Filler | System, method and article of manufacture for managing a medical services network |
US6757898B1 (en) * | 2000-01-18 | 2004-06-29 | Mckesson Information Solutions, Inc. | Electronic provider—patient interface system |
US7174303B2 (en) * | 2000-07-31 | 2007-02-06 | Uappoint, Inc | Customer driven, sponsor controlled network-based graphical scheduling system and method |
US6988128B1 (en) * | 2000-09-27 | 2006-01-17 | International Business Machines Corporation | Calendar events and calendar-driven application technique |
US20020059082A1 (en) * | 2000-11-15 | 2002-05-16 | Roger Moczygemba | Appointment setting and payment system and method |
US20020116220A1 (en) * | 2001-02-20 | 2002-08-22 | Glazier Alan Neil | Method and system for interactively researching and scheduling a medical procedure over a computer network |
US20070168224A1 (en) * | 2005-11-22 | 2007-07-19 | Letzt Alan M | Advanced diabetes management system (adms) |
US20070167688A1 (en) * | 2005-12-19 | 2007-07-19 | Ross S M | Healthcare management systems and associated methods |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080300918A1 (en) * | 2007-05-29 | 2008-12-04 | Commercenet Consortium, Inc. | System and method for facilitating hospital scheduling and support |
US20090076832A1 (en) * | 2007-09-14 | 2009-03-19 | Collins Christopher M | Inmate privilege kiosk methods, systems and user interface |
US10636067B2 (en) | 2007-09-14 | 2020-04-28 | Keefe Commissary Network, L.L.C. | System and method for an inmate privilege kiosk |
US8370206B2 (en) * | 2007-09-14 | 2013-02-05 | Keefe Commissary Network, L.L.C. | Method, medium, and system for an inmate privilege kiosk |
US20100057513A1 (en) * | 2008-08-26 | 2010-03-04 | Mckesson Financial Holdings Limited | Automatic appointment scheduler with hybrid timeline |
US20120109679A1 (en) * | 2008-09-15 | 2012-05-03 | ZocDoc, Inc. | Consumer portal for healthcare appointments across practice groups |
US20100070303A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Consumer portal for healthcare appointments across practice groups |
US20100070297A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Data synchronization for booking of healthcare appointments across practice groups |
US20100070295A1 (en) * | 2008-09-15 | 2010-03-18 | ZocDoc, Inc. | Centralized marketplace for healthcare appointments across practice groups |
US8688466B2 (en) * | 2008-09-15 | 2014-04-01 | ZocDoc, Inc. | Data synchronization for booking of healthcare appointments across practice groups |
US20100070294A1 (en) * | 2008-09-15 | 2010-03-18 | Mckesson Financial Holdings Limited | Creating and communicating staffing assignments |
US20110161128A1 (en) * | 2009-12-31 | 2011-06-30 | Mckesson Financial Holdings Limited | Scheduling and Assigning Units of Work |
US20120232946A1 (en) * | 2011-03-08 | 2012-09-13 | Charles Daniel Cocanougher | Methods and Systems for a Multi-Party Customizable Calendar |
US20220059198A1 (en) * | 2013-03-14 | 2022-02-24 | Alterg, Inc. | Systems and methods for management and scheduling of differential air pressure and other unweighted or assisted treatment systems |
WO2015005963A1 (en) * | 2013-07-09 | 2015-01-15 | Yi Song | Integrated health measurement and food service system |
US10535431B2 (en) * | 2014-09-17 | 2020-01-14 | Change Healthcare Holdings, Llc | System and method for dynamic schedule aggregation |
US20220189625A1 (en) * | 2020-12-15 | 2022-06-16 | Orchid Exchange Inc. | Systems and methods for providing virtual health services |
WO2022132903A1 (en) * | 2020-12-15 | 2022-06-23 | Orchid Exchange Inc. | Systems and methods for providing virtual health services |
US11404164B2 (en) * | 2020-12-15 | 2022-08-02 | Orchid Exchange Inc. | Systems and methods for providing virtual health services |
Also Published As
Publication number | Publication date |
---|---|
US7337123B2 (en) | 2008-02-26 |
US20030208391A1 (en) | 2003-11-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7337123B2 (en) | Rules based ticketing for self-scheduling of appointments | |
US8688474B2 (en) | Patient health record access system | |
US8364501B2 (en) | Electronic appointment scheduling for medical resources | |
US7747453B2 (en) | System and method for managing patient encounters | |
US8090590B2 (en) | Electronic personal health record system | |
US6988075B1 (en) | Patient-controlled medical information system and method | |
US7051012B2 (en) | User interface system for maintaining organization related information for use in supporting organization operation | |
US20020120472A1 (en) | System and method for integration of health care records | |
US20040249676A1 (en) | Management systems and methods | |
US20040111293A1 (en) | System and a method for tracking patients undergoing treatment and/or therapy for renal disease | |
US20060184524A1 (en) | Method and system for automated data analysis, performance estimation and data model creation | |
US20040111294A1 (en) | System and a method for providing integrated access management for peritoneal dialysis and hemodialysis | |
US20030050802A1 (en) | Medical service and prescription management system | |
US20080249804A1 (en) | Method for Managing Medical Information Online | |
US20080287746A1 (en) | System and method for communicating health care alerts via an interactive personal health record | |
US20030236682A1 (en) | Method and system for managing a healthcare network | |
US20040220829A1 (en) | Distributed system and method for managing communication among healthcare providers, patients and third parties | |
US20070150315A1 (en) | Policy driven access to electronic healthcare records | |
US8346575B2 (en) | System and methods of automated patient check-in, scheduling and prepayment | |
US8185407B2 (en) | Referral request system | |
US20060136268A1 (en) | System and method for maintaining the association of healthcare orders in a healthcare plan in a computerized pharmacy application | |
US20140278579A1 (en) | Medical Form Generation, Customization and Management | |
KR100538582B1 (en) | Method For Supporting A Decision In System For Offering A Medical Information | |
AU2001273006A1 (en) | Patient health record access system | |
WO2000003343A1 (en) | Method and system for electronically managing and reimbursing medical care |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |