Management systems and methods
First Claim
1. A management system, comprising:
- a) a database for storing patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, and whether or not the patient indicates that the patient is unavailable, b) means for calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) means for calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
1 Assignment
0 Petitions
Accused Products
Abstract
A management system is used for management of patients on waiting lists in such fields as elective surgery, diagnostic services, clinic services and endoscopies. The system also administers administrative entities based on aggregate data provided by the system. The system has data entry, list management, audit and reporting functions. It acquires and creates its data. It calculates much data dynamically (in real time). For example, it stores data on when a patient entered onto a waiting list, and a patient'"'"'s urgency score. Based on the urgency score, it calculates a target date for the patient. It dynamically (in real time) calculates the number of days a patient is from the target date, and ranks the patients accordingly. It filters a list of patients awaiting procedures according to various resource criteria. It provides for and manages referrals between systems, and lists, in different fields, and it allows calendar booking.
78 Citations
47 Claims
-
1. A management system, comprising:
-
a) a database for storing patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, and whether or not the patient indicates that the patient is unavailable, b) means for calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) means for calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 42, 43, 44, 45)
-
-
23. A management system, comprising:
-
a) a database for storing patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, pre-procedure requirements required before the procedure can take place, and whether or not each pre-procedure requirement has taken place, b) means for calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) means for calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date. - View Dependent Claims (24, 25)
-
-
26. A database schema for use in a management system, comprising:
-
a) a first field for storing the date a patient entered onto a list for a procedure, b) a second field for storing an urgency score for the patient for the procedure, c) a third field for storing a target number of days to receive the procedure based on the urgency score, and d) a fourth field for storing whether or not the patient indicates that the patient is unavailable, wherein data stored in the fields is available prior to the procedure taking place.
-
-
27. A database schema for use in a management system, comprising:
-
a) a first field for storing the date a patient entered onto a list for a procedure, b) a second field for storing an urgency score for the patient for the procedure, c) a third field for storing a target number of days to receive the procedure based on the urgency score, d) a fourth field for storing a pre-procedure requirement required before the procedure can take place, and e) a fifth field for storing whether or not each pre-procedure requirement has taken place, wherein data stored in the fields is available prior to the procedure taking place.
-
-
28. Computer program instructions on computer readable media for use in association with a database containing a first field storing the date a patient entered onto a list for a procedure, a second field storing an urgency score for the patient for the procedure, a third field storing a target number of days to receive the procedure based on the urgency score, and a fourth field for storing whether or not the patient indicates that the patient is unavailable, the computer program instructions on computer readable media comprising:
-
a) instructions for a computer to calculate a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and b) instructions for a computer to calculate, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
29. Computer program instructions on computer readable media for use in association with a database containing a first field storing the date a patient entered onto a list for a procedure, a second field storing an urgency score for the patient for the procedure, a third field storing a target number of days to receive the procedure based on the urgency score, a fourth field for storing a pre-procedure requirement required before the procedure can take place, and a fifth field for storing whether or not each pre-procedure requirement has taken place, the computer program instructions on computer readable media comprising:
-
a) instructions for a computer to calculate a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and b) instructions for a computer to calculate, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
30. A user interface screen comprising:
-
a) a first data element for viewing the date a patient entered onto a list for a procedure, b) a second data element for viewing an urgency score for the patient for the procedure, c) a third data element for viewing a target number of days to receive the procedure based on the urgency score, and d) a fourth data element for viewing whether or not the patient indicates that the patient is unavailable.
-
-
31. A user interface screen comprising:
-
a) a first data element for viewing the date a patient entered onto a list for a procedure, b) a second data element for viewing an urgency score for the patient for the procedure, c) a third data element for viewing a target number of days to receive the procedure based on the urgency score, d) a fourth data element for viewing a pre-procedure requirement required before the procedure can take place, and e) a fifth data element for viewing whether or not each pre-procedure requirement has taken place.
-
-
32. A method of operating a management system, comprising:
-
a) storing in a database patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, and whether or not the patient indicates that the patient is unavailable, b) calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
33. A method of operating a management system, comprising:
-
a) storing in a database patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, pre-procedure requirements required before the procedure can take place, and whether or not each pre-procedure requirement has taken place, b) calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
34. A method of managing a patient, comprising:
-
a) selecting an urgency score for the patient for a procedure;
b) calculating a target date for the patient for the procedure based on the date the patient entered onto a list for that procedure and the target number of days, c) calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date, and d) storing whether or not the patient indicates that the patient is unavailable. - View Dependent Claims (35, 36, 37)
-
-
38. A method of managing a patient, comprising:
-
a) selecting an urgency score for the patient for a procedure;
b) calculating a target date for the patient for the procedure based on the date the patient entered onto a list for that procedure and the target number of days, c) calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date, d) storing a pre-procedure requirement required before the procedure can take place, and e) storing whether or not each pre-procedure requirement has taken place. - View Dependent Claims (39)
-
-
40. A management system, comprising:
-
a) a database for storing patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, and whether or not the patient indicates that the patient is unavailable, b) a calculator for calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) a calculator for calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
41. A management system, comprising:
-
a) a database for storing patient waiting data, including the date a patient entered onto a list for a procedure, an urgency score for the patient for the procedure, a target number of days to receive the procedure based on the urgency score, pre-procedure requirements required before the procedure can take place, and whether or not each pre-procedure requirement has taken place, b) a calculator for calculating a target date for the patient for the procedure based on the date the patient entered onto the list for that procedure and the target number of days, and c) a calculator for calculating, for any given date prior to the procedure taking place, the number of days the given date is from the target date.
-
-
46. A management system, comprising:
-
a) a database for storing patient data, including an urgency score for a patient for a procedure, and whether or not the patient indicates that the patient is unavailable, b) a plurality of modalities, each modality utilizing the stored patient data for a distinct waiting list of patients, and c) a referral process for online referral of a patient to a waiting list of one of the modalities. - View Dependent Claims (47)
-
Specification