WO2002027611A2 - System and method for tracking appointment data - Google Patents
System and method for tracking appointment data Download PDFInfo
- Publication number
- WO2002027611A2 WO2002027611A2 PCT/US2001/030269 US0130269W WO0227611A2 WO 2002027611 A2 WO2002027611 A2 WO 2002027611A2 US 0130269 W US0130269 W US 0130269W WO 0227611 A2 WO0227611 A2 WO 0227611A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- appointment
- target
- engine
- seeker
- time
- Prior art date
Links
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
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
Definitions
- the present invention relates generally to scheduling applications and, more specifically, to a system and method for tracking appointment data.
- PnP solutions require an enterprise employee to check appointment availability by referring to one or several calendars. The employee must then relay the available appointment options to the party seeking the appointment and schedule the party's appointment. The process can be exceedingly slow and unreliable.
- PnP solutions require the presence of an individual, which means an enterprise seeking to have twenty-four hour a day coverage will need to employ at least three shifts of people - making PnP solutions costly.
- a system and method for tracking appointment data includes a clinic engine operable to allow an appointment target to identify a first block of time as available-to-meet time and an appointment engine operable to make available at least a portion of the first block of time to an appointment seeker in response to an appointment request.
- the system may also include an appointment seeker interface that allows the appointment seeker to schedule a first appointment during the first block of time and a notification engine operable to notify the appointment target of the first appointment.
- the clinic engine may be further operable to allow the appointment target to identify allowable locations for the first appointment.
- the clinic engine may be further operable to allow the appointment target to identify an allowable duration for the first appointment and an allowable class of user for given blocks of time.
- An engine may include, for example, computer operations running in separate computing platforms or the same computing platforms. The computer operations may be written to be object-oriented and may make use of different languages including, for example, third generation languages like Java, Visual Basic, C++, and PL/S.
- engines may be modular and identifiable as separate discrete blocks of code. In other embodiments, engines may be included within and integrated into one or more larger blocks of code.
- a method incorporating teachings of the present disclosure may include maintaining a data store comprising information relating to an appointment schedule of an appointment target.
- the appointment target may be, for example, an individual, a group, or an organization, with whom another individual, group, or organization would like to meet.
- the method embodiment described above for tracking appointment information may include identifying an appointment opportunity for the appointment target as open for scheduling or available-to-meet and receiving a request to schedule an appointment during the appointment opportunity.
- the request may be granted in real time and without further consultation with the appointment target though the appointment target may be subsequently notified of the granted request.
- An appointment target perhaps a doctor, an automobile mechanic, a barber, or an executive, can preemptively establish their availability and publish the availability to appointment seekers.
- an appointment seeker for example a patient or an individual in need of a hair cut, may select an appointment and, in some embodiments, receive real time confirmation of the appointment. The appointment seeker may no longer be forced to wait until the target can respond to a request for a meeting.
- some embodiments may be implemented as software engines on local or distributed computing platforms and networks.
- these systems may be available twenty-four hours a day and readily accessible via a large computer network such as the Internet or enterprise intranets.
- users may access the system using communication protocols like TCP/IP.
- Figure 1 depicts a block diagram of one embodiment of a system incorporating teachings of the present disclosure.
- Figure 2 depicts a block diagram of another embodiment of a system incorporating teachings of the present disclosure.
- Figure 3 shows a state transition diagram that illustrates operation and use of a system embodiment incorporating teachings of the present disclosure.
- Figure 4 shows one embodiment of a graphical user interface presented to a system user at log in.
- Figure 5 shows one embodiment of a graphical user interface presented to a system administrator.
- Figure 6 shows one embodiment of a graphical user interface presented to an appointment target identifying blocks of available to meet time.
- Figure 7 shows one embodiment of a graphical user interface presented to an appointment seeker viewing a calendar of a specific target's available to meet time.
- Figure 8 shows one embodiment of a graphical user interface presented to an appointment seeker searching for and scheduling an appointment.
- Figure 9 shows one embodiment of a graphical user interface presented to an appointment seeker depicting the seeker's scheduled appointments.
- system 100 may include a server 102 executing various software engines.
- system 100 may include a clinic engine 104, an appointment engine 106, an interface engine 108, and a notification engine 110.
- An engine may include, for example, computer operations running in separate computing platforms or the same computing platform.
- the computer operations may be written to be object-oriented and may make use of different languages including, for example, third generation languages like Java, Visual Basic, C++, and PL/S.
- system 100 may help an appointment seeker, such as a patient, receive real time and web based confirmation of an appointment with an appointment target, such as a doctor.
- the system may also provide the functionality an organization, enterprise, or entity needs to manage other processes that are triggered when an appointment occurs (e.g., electronic payment claims, on-line prescriptions, on-line diagnosis, etc.).
- the system may be secure, and the privacy of target and seeker information protected.
- System 100 may be Internet based.
- System 100 may also be embedded in an organization's existing intranet site or set up on an extranet to give an organization real-time scheduling functionality.
- system 100 may allow an appointment target 112, 114 to access server 102 through a communication network 116, such as the Internet, using communication protocols like TCP/IP. Once accessed, system 100 may allow an appointment target 112, 114 to establish and publish an availability summary.
- clinic engine 104 may allow a doctor to create, modify, or delete various types of information about the doctor's schedule.
- clinic engine 104 may allow a doctor to list his or her specialty, the facility or facilities where the doctor will meet patients, the appointment type
- Clinic engine 104 may also allow for additional criteria to be input.
- an appointment seeker 118, 120, 122 may access interface 108 through a communication network 124.
- Appointment seeker 118, 120, 122 may search for an individual or type of target using appointment engine 106.
- Appointment engine 106 may compare a seeker's request against the known availability of targets that have established a clinic and present a seeker with targets who are available to meet.
- a seeker may select a target and receive real time confirmation of the appointment and its time, place, etc.
- notification engine 110 may initiate the sending of a meeting notice to a target.
- a target may want to have some information about the seeker before the meeting.
- some embodiments of system 100 may include a form or chart to be filled out by the seeker.
- a seeker may be a registered user or have used system 100 before and his or her information may be stored in a data store and prepopulated into the form or chart.
- other functionality such as the functionality depicted in Figure 2, may be added to system 100.
- System 200 may include a clinic engine 204, an appointment engine 206, an interface engine 208, and a notification engine 210.
- system 200 may include targets 212, 213, 214, 215, some with access through communication network 216, and seekers 218, 219, 200, 221, 222, some with access through communication network 224.
- system 200 may allow for direct access links 226 between seekers and server 202 and a direct access link 228 between target 214 and server 202.
- a system incorporating teachings of the present disclosure may seek to notify a target or group of targets 230 of a scheduled meeting.
- the notification may involve electronic mail and may involve accessing an enterprise Email server 232 via an email interface 234.
- a system incorporating teachings of the present disclosure may also seek to prepopulate forms with data from a legacy system 236 across a legacy interface 238. Accessing existing data stores and enterprise servers may allow system 200 to operate very efficiently and without the complete duplication of information already available.
- system 200 may include a calendar engine 240 operable to generate a calendar that may make selecting an appointment time and date simpler. The calendar generated may be presented to a user when the user is either seeking to make time available or schedule a meeting.
- system 200 may include an update engine 242 that recognizes when a seeker has scheduled an appointment with a target and automatically updates the targets calendar to indicate that the scheduled time is no longer available for appointment.
- update engine 242 may also recognize when information located within legacy system 236 has changed and initiate an updating of the information located within legacy system 236 to reflect the change.
- Other engines may also be present in system 200. For example, some users may want to offer survey capabilities.
- a system administrator may want to develop and or present a survey to an appointment seeker to determine any number of things, such as, usability of system 200, availability of targets, professionalism of targets, etc.
- a survey engine may allow almost anyone to create, distribute, and/or respond to a survey in real time.
- system 200 may also involve uses more complex than scheduling a meeting or creating and responding to a survey.
- a seeker may need to meet a specific target and may not be able to do so face-to-face.
- a remotely located patient may need to meet with a specialist. If a person on an aircraft carrier or submarine needs to meet with a dermatologist and a dermatologist is not on ship, the patient may need to virtually meet with the doctor.
- system 200 may need to recognize that a seeker has scheduled a virtual meeting and initiate provisioning of a virtual meeting link 244 such as a teleconference or videoconference link.
- system 200 may allow a seeker to forward information to a target in lieu of or in addition to establishing a telecommunication link.
- a seeker scheduling a virtual dermatologist meeting might take digital photographs of an infected skin area and system 200 may allow for attachment of the image files to an appointment notice being sent to the dermatologist target.
- system 200 may involve significant complexities.
- system 200 may include an administrator console 246.
- Administrator console 246 may take several forms.
- administrator console 246 may be a separate PC directly linked to server 202, a software engine, or a specific type of user.
- Administrator console 246 may allow for the provisioning of rights or access within system 200.
- certain targets may not be permitted to schedule virtual meetings or group 230 may not be allowed to include certain facility locations in clinics or schedules it establishes.
- entities of system 200 may be managed (either directly or indirectly) using a graphical user-interface.
- a system administrator may add particular entities to the system's scheduling domain, based on the initial requirements of the enterprise applications being made available. As the scheduling domain evolves, the administrator may manage the entities by modifying ones that currently exist, adding more, or removing ones that are no longer necessary.
- Depicted method 300 of Figure 3 may include several stages.
- an enterprise or entity may acquire access to a scheduling platform incorporating teachings of the present disclosure.
- the platform may support a system like system 200 of Figure 2.
- the enterprise or entity may choose any or all of several techniques for making the platform available to users.
- stage 304 depicts an integration option whereby the platform is incorporated into an existing system, a hosting or application service provider ("ASP") model whereby the platform executes on a remote server and may support more than one enterprise, and a catch all option, which may include a stand alone extranet or intranet option.
- ASP application service provider
- some or all of these access techniques may be employed.
- operational requirements or guidelines may need to be established.
- guidelines may be established that articulate goals and metrics for tracking the appointment data of one or more entities.
- an insurance company may be interested in tracking appointment information to better understand where a new hospital or service provider should be located.
- the development of these requirements may be an initial step in the application process and may make it possible to provide preferred metric tracking.
- establishing operational guidelines may identify distinct applications (e.g., Microsoft Outlook) or legacy systems that contain important user information. Identifying these information sources may help a developer or integrator decide how and whether to interface an appointment tracking system with other information sources.
- Components or software instances necessary to interface with other systems may be built using a variety of programming languages, depending on the systems in question. These components may facilitate the transfer of data to and from enterprise systems as application requirements dictate. Each integration component may access application programming interfaces (APIs) in order to access desired information instances. As application requirements change, an entity may enhance the integration components as needed.
- APIs application programming interfaces
- Special conditional logic statements which may drive a rules engine in a server-based scheduling system may be created by the system administrator using a graphical user-interface with menu driven options. These rules may control how data that is applied to the domain is distributed to users in the domain.
- a system administrator may add users to the system. As the domain evolves, the administrator may manage the users by adding more, modifying ones that currently exist, or removing ones that are no longer necessary. Before a user interacts with the domain, the user may be linked to applications and privileges that they can use under their account, and have those applications and privileges made available to them.
- Each application may be a software instance that can be created, deployed and updated by developers that interface with the domain.
- an application may be managed using the graphical user-interface provided by the computing system. This interface may be used to link applications to new users and unlink applications from users, as required for the consistent and efficient operation of the system.
- an appointment target may be added and managed. This step may be performed by various individuals including the target, an assistant with permission to act as the target, or an administrator.
- a target may access, create, and update availability calendars or data instances managed by the domain, and may have relevant transactions based on these instances re-distributed to other interested seekers and targets in the domain (as rules in the system dictate).
- the rules may be established by the target or by an administrator.
- a set of targets may be established such that the set is treated collectively as an individual target, as indicated in Figure 2 at 230.
- a group of targets may be treated collectively as a single target, with each target in the group sharing some set of assigned privileges.
- targets may be collected into groups so that they may share domain resources based on real- world affiliations, such as geographic location or job role.
- a seeker may be added to and access the system in much the same way as a target.
- the seeker may also be linked to various applications or instances of data. For example, if the seeker is a patient, data instances may be linked to and distributed to the seeker in order to populate applications and forms with personal and medical information requested by the target doctor.
- a seeker may search for an available doctor based on several criteria including, for example, doctor name, location, time available, and specialty.
- the seeker may schedule an appointment at step 310.
- the appointment scheduling may result in a real time confirmed appointment as well as the triggering of several other operations.
- a notification may be sent to the target through any of several means including, for example, Email.
- a target's schedule may be updated to reflect the newly scheduled meeting, and at step 316, reservations necessary (e.g., reserved space or telecommunication bandwidth) may be made.
- step 304 may involve a hosting solution.
- Hosting may, itself, involve the steps of receiving a software platform that includes appointment tracking code and loading the software platform onto a server that is connected with a computer network, such as the Internet or an intranet, so that multiple users may access the software platform.
- Hosting may also include hosting services that accompany the hosting process. Payment, or other type of monetary value, for hosting the software platform may also be invoiced and collected - involving additional steps.
- Figures 4 through 9 depict graphical user interfaces (GUIs) that may be presented during operation of a system like system 200 of Figure 2.
- GUIs graphical user interfaces
- Figure 4 shows one embodiment of a graphical user interface presented to a system user at log in. During log in, a user may be identified and preferences or privileges associated with the logged in user may be called.
- Figure 5 shows one embodiment of a graphical user interface presented to a system administrator
- Figure 6 shows one embodiment of a graphical user interface presented to an appointment target identifying blocks of available to meet time.
- a target doctor, Dr. Butler is establishing a clinic or making himself available for orthopedic services on the 20 th and the 27 th of June 2001.
- Dr. Butler has made himself available for thirty minute meetings in the Professional Tower.
- Dr. Butler could put more or less restrictions on her meeting availability.
- Figure 7 shows one embodiment of a graphical user interface presented to an appointment seeker viewing a calendar of a specific target's available to meet time. As depicted, the calendar is for Dr. Butler's addiction meetings.
- Figure 8 shows one embodiment of a graphical user interface presented to an appointment seeker searching for and scheduling an appointment. The appointment scheduled is with Dr. Butler, for orthopedic services in the Professional Tower. As depicted, the meeting is an initial consultation.
- Figure 8 shows one embodiment of a graphical user interface presented to an appointment seeker viewing a calendar of a specific target's available to meet time. As depicted, the calendar is for Dr. Butler's addiction meetings.
- Figure 8 shows one embodiment of a graphical user interface presented to an appointment seeker searching for and scheduling an appointment. The appointment scheduled is with Dr. Butler, for orthopedic services in the Professional Tower. As depicted, the meeting is an initial consultation.
- Figure 8 shows one embodiment of a graphical user interface presented to an appointment seeker viewing a calendar of a specific target's available to meet time. As depict
- FIG 9 shows one embodiment of a graphical user interface presented to an appointment seeker depicting the seeker's scheduled appointments.
- Figures 4 through 9 depict GUIs as web pages in a browser window.
- the data entered in a web based scheduling system like system 200 may represent some real world object, place, thing, person, or collection and combination thereof.
- the entered data may be used to create a calendar, physical table or group of tables in a data store that will hold physical instances of those objects, places, things, or combinations, in records.
- class names in a data model may be used to instantiate physical tables in a data store, a developer may want to consider naming limitations of the particular database management system (DBMS).
- DBMS database management system
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/381,968 US20040039626A1 (en) | 2001-09-26 | 2001-09-26 | System and method for tracking appointment data |
EP01973580A EP1352350A2 (en) | 2000-09-29 | 2001-09-26 | System and method for tracking appointment data |
AU2001293142A AU2001293142A1 (en) | 2000-09-29 | 2001-09-26 | System and method for tracking appointment data |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US23708800P | 2000-09-29 | 2000-09-29 | |
US60/237,088 | 2000-09-29 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2002027611A2 true WO2002027611A2 (en) | 2002-04-04 |
WO2002027611A3 WO2002027611A3 (en) | 2003-07-31 |
Family
ID=22892290
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/030269 WO2002027611A2 (en) | 2000-09-29 | 2001-09-26 | System and method for tracking appointment data |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1352350A2 (en) |
AU (1) | AU2001293142A1 (en) |
WO (1) | WO2002027611A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007293577A (en) * | 2006-04-25 | 2007-11-08 | Nec Corp | Remote medical treatment providing system and remote medical treatment providing method |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5772585A (en) * | 1996-08-30 | 1998-06-30 | Emc, Inc | System and method for managing patient medical records |
EP0921670A2 (en) * | 1997-12-04 | 1999-06-09 | Siemens Information and Communication Networks, Inc. | Electronic scheduling devices |
US5924074A (en) * | 1996-09-27 | 1999-07-13 | Azron Incorporated | Electronic medical records system |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
-
2001
- 2001-09-26 EP EP01973580A patent/EP1352350A2/en not_active Withdrawn
- 2001-09-26 AU AU2001293142A patent/AU2001293142A1/en not_active Abandoned
- 2001-09-26 WO PCT/US2001/030269 patent/WO2002027611A2/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5772585A (en) * | 1996-08-30 | 1998-06-30 | Emc, Inc | System and method for managing patient medical records |
US5924074A (en) * | 1996-09-27 | 1999-07-13 | Azron Incorporated | Electronic medical records system |
EP0921670A2 (en) * | 1997-12-04 | 1999-06-09 | Siemens Information and Communication Networks, Inc. | Electronic scheduling devices |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
Non-Patent Citations (3)
Title |
---|
DIETERICH H ET AL: "INTELLIGENT AGENTS AS APPOINTMENTS MANAGERS LIVING IN PUBLIC NETWORKS" PROCEEDINGS OF THE INTERNATIONAL SYMPOSIUM ON HUMAN FACTORS IN TELECOMMUNICATIONS, XX, XX, 1997, pages 23-30, XP000984330 * |
MERCANDO A D: "APPOINTMENT SCHEDULING ON COMPUTER" PACE - PACING AND CLINICAL ELECTROPHYSIOLOGY, FUTURA PUBLISHING COMPANY, INC, US, vol. 20, no. 7, July 1997 (1997-07), pages 1860-1862, XP009000604 ISSN: 0147-8389 * |
NGUYEN H: "SchedNet, a 24-hour Internet patient scheduling system" COMPUTER-BASED MEDICAL SYSTEMS, 1999. PROCEEDINGS. 12TH IEEE SYMPOSIUM ON STAMFORD, CT, USA 18-20 JUNE 1999, LOS ALAMITOS, CA, USA,IEEE COMPUT. SOC, US, 18 June 1999 (1999-06-18), pages 156-161, XP010345810 ISBN: 0-7695-0234-2 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007293577A (en) * | 2006-04-25 | 2007-11-08 | Nec Corp | Remote medical treatment providing system and remote medical treatment providing method |
Also Published As
Publication number | Publication date |
---|---|
WO2002027611A3 (en) | 2003-07-31 |
EP1352350A2 (en) | 2003-10-15 |
AU2001293142A1 (en) | 2002-04-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20040039626A1 (en) | System and method for tracking appointment data | |
RU2435208C2 (en) | Accessibility data service | |
KR100763672B1 (en) | System, method and service for negotiating schedules while preserving privacy though a shared representation | |
US7051012B2 (en) | User interface system for maintaining organization related information for use in supporting organization operation | |
US7181493B2 (en) | Platform independent model-based framework for exchanging information in the justice system | |
US6073109A (en) | Computerized method and system for managing business processes using linked workflows | |
US8060500B1 (en) | Method and system for selecting a healthcare provider with minimal office wait times | |
US20160098687A1 (en) | Systems and methods for private schedule coordination and event planning | |
US8185426B1 (en) | Method and system for providing real time appointment rescheduling | |
US8140370B2 (en) | System and method for reducing the steps involved in searching for available appointment times and scheduling appointments in a health care environment | |
US20060293930A1 (en) | Sales call management | |
US20020131572A1 (en) | Method and apparatus for scheduling appointments | |
JP2006523352A (en) | Joint start pad | |
WO2005067614A2 (en) | A system and method of commitment management | |
CA2470027A1 (en) | Management systems and methods | |
CA3148798C (en) | Virtual visit objects | |
US20020099568A1 (en) | System and method for facilitating the coordination of care of an individual and dissemination of information | |
US7716671B2 (en) | Method for coordinating a set of related tasks and events by reducing duplicated effort | |
US7299465B2 (en) | Configurable application integrating service request and fulfillment process | |
US7644008B1 (en) | Web-based system and method for user role assignment in an enterprise | |
CN101258482B (en) | Availability data service | |
Bhat et al. | Intelligent scheduling in health care domain | |
WO2002027611A2 (en) | System and method for tracking appointment data | |
EP1304639A1 (en) | A system for maintaining organization related information for use in supporting organization operation | |
Moonian et al. | HCRBAC –An Access Control System for Collaborative Context-Aware HealthCare Services in Mauritius |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2001973580 Country of ref document: EP |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 10381968 Country of ref document: US |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 2001973580 Country of ref document: EP |
|
NENP | Non-entry into the national phase in: |
Ref country code: JP |