WO2006102718A1 - A healthcare administration system - Google Patents

A healthcare administration system Download PDF

Info

Publication number
WO2006102718A1
WO2006102718A1 PCT/AU2006/000433 AU2006000433W WO2006102718A1 WO 2006102718 A1 WO2006102718 A1 WO 2006102718A1 AU 2006000433 W AU2006000433 W AU 2006000433W WO 2006102718 A1 WO2006102718 A1 WO 2006102718A1
Authority
WO
WIPO (PCT)
Prior art keywords
software product
care
database
pda
intervention
Prior art date
Application number
PCT/AU2006/000433
Other languages
French (fr)
Inventor
John Leslie Slaven
Original Assignee
Ecp Board
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from AU2005901564A external-priority patent/AU2005901564A0/en
Application filed by Ecp Board filed Critical Ecp Board
Priority to AU2006228992A priority Critical patent/AU2006228992A1/en
Publication of WO2006102718A1 publication Critical patent/WO2006102718A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT 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/20ICT 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

Definitions

  • the present invention relates to a healthcare administration system.
  • the present invention also relates to a wireless communication device which is configured to permit a user to interface with a remote database. Additionally, the present invention relates to a software product which, when executed, facilitates said interface with the remote database.
  • the present invention also relates to a method of administering a healthcare system.
  • Patient information records are generally kept in close proximity to the patient and, accordingly, a carer must go to the patient to view the patient's information.
  • the Applicant has identified a need for a system whereby a carer can access and manipulate patient information from a location remote from a centrally located database in which patient information is stored. This need also extends to a situation where the carer attends to patients at their homes. In such cases, it is both difficult and inconvenient for carers to have readily available patient information, particularly when the carers have to travel from one patient to the other.
  • the Applicant has conceived the present invention to address this need and to provide a system in which patient information can be centrally stored and managed.
  • the Applicant has conceived the present invention to provide a means whereby patients can be cared for by carers with full and complete information relating to the patients at their disposal.
  • Care Intervention - data representing any process that is carried out by a carer to care, treat, control or otherwise interact with a patient.
  • Carer any person, including professionals such as nurses, doctors or specialists employed in the healthcare industry.
  • Computer - a computational device including one or more processors including personal computers (PCs), mainframes, servers or the like.
  • Patient any person who is a patient or a resident in a healthcare facility such as a hospital or aged care home, or in the community who receives care at home.
  • a healthcare facility such as a hospital or aged care home, or in the community who receives care at home.
  • the words "patient” and "resident” are to be considered interchangeable.
  • Patient Information information relating to a patient that includes information that would usually be collected at a healthcare facility, such as: mobility, food allowances/restrictions, personal hygiene issues, toileting issues, bladder management, bowel management, behavioural characteristics, emotional characteristics, social and human needs, medication needs, therapy needs, vision, hearing, and any other information that could assist in patient management.
  • Patient Profile A description of a patient that can be stored electronically and that is based at least partially on the patient information and is stored in tables to facilitate associations and retrieval of the patient information.
  • ECP Electronic Care Plan
  • Wireless communication which does not require the use of a wired link, including radio frequency (RF) links such as Bluetooth ® , for example, or any other long distance wireless protocols, such as code division multiple access (CDMA) broadband.
  • RF radio frequency
  • PDA Personal Digital Assistant
  • a healthcare administration system that includes a computer programmed to define a database for storing patient information and connected to a network at a central location; and at least one wireless communication device connected to the network at an end user location, the, or each, wireless communication device being configured to define an interface with the database, via the network.
  • the computer may include a database server for storing and managing the database and a web server for interfacing the database with the network.
  • the network may be a Wireless Fidelity (WIFI) intranet through which the, or each, wireless communication device interfaces with the web server.
  • WIFI Wireless Fidelity
  • The, or each, wireless communication device may be a personal digital assistant (PDA).
  • PDA personal digital assistant
  • the system may include at least one workstation computer at the end user location that interfaces with the web server via one of a local area network (LAN) and the Internet.
  • LAN local area network
  • Said interface defined by the wireless communication device may be in the form of a virtual private network (VPN).
  • VPN virtual private network
  • a method of administering a healthcare system including the steps of: inputting data representing patient information into a database; manipulating the patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
  • the step of maintaining the database may include the step of generating patient profiles within the database.
  • the method may include the step of generating electronic care plans (ECP's) using the patient profile.
  • ECP's electronic care plans
  • the method may include the step of providing a notes interface so that a carer can enter further patient information into the database to be accessible via the interface.
  • the method may include the step of generating care interventions based on the ECP's.
  • the method may include the step of generating reports from data stored in the database.
  • a software product for use in a healthcare administration system the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the method as described above.
  • a software product for use in a healthcare administration system, the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the following steps: providing a database in which patient information can be stored; manipulating patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
  • the software product may be configured to define an application service provider (ASP) to manage web forms to be displayed on the wireless communication device.
  • ASP application service provider
  • the ASP may be configured to generate web form architecture to permit a carer to log in to the healthcare administration system.
  • the ASP may be configured to generate the web form architecture such that the PDA carries out one or more of the following steps: prompts a carer to enter data representing a facility in which a patient resides; generates menu options to facilitate access to patient information and to facilitate the input of data, such as note data to the database.
  • the ASP may be configured to generate the web form architecture such that the PDA can carry out one or more of the following steps: provides a log on menu for an administrator; generates menu options to facilitate access to information including care interventions.
  • the ASP may be configured to generate the web form architecture to define a care intervention.
  • the ASP may be configured to generate the web form architecture such that the PDA can communicate the assignment of the care intervention to a carer.
  • the ASP may be configured to generate the web form architecture such that the PDA can prompt a carer to input data indicating whether or not the care intervention is complete.
  • the software product may be configured to provide a relational database.
  • the software product may be configured to generate a care intervention table of the relational database such that the care intervention table stores data relating to care interventions generated by the software product.
  • the software product may be configured to generate a care intervention groups table of the relational database such that the care intervention groups table stores data relating to care interventions associated with particular facilities at which the care interventions are carried out.
  • the software product may be configured to generate a care intervention group facility table such that the care intervention group facility table stores data relating to all facilities linked to particular intervention groups.
  • the software product may be configured to generate a care intervention note table, such that the care intervention note table relates notes and corresponding care interventions.
  • the software product may be configured to generate a care intervention status table, such that the care intervention status table stores status codes used for respective care interventions.
  • a software product for use in a healthcare administration system the software product being executable on a personal digital assistant (PDA) and being configured so that, when executed, establishes an interface with the software product as described above.
  • PDA personal digital assistant
  • the software product may be configured so that the PDA can generate a graphic user interface (GUI) to permit a carer to interface with the software product of the third and fourth aspects of the invention.
  • GUI graphic user interface
  • the software product may be configured so that the PDA can generate a decision tree to permit a carer to input data representing whether or not one or more of the following steps have been carried out by the carer: a particular care intervention has been completed; progress notes are to be input.
  • the software product may be configured so that the PDA can communicate details relating to said one or more of the steps to the database.
  • PDA personal digital assistant
  • the personal digital assistant may be Internet-enabled.
  • Figure 1 is a schematic diagram showing a broad layout of a system infrastructure for a first embodiment of a healthcare administration system in accordance with the invention
  • Figure 2 is a broad flowchart illustrating a method, in accordance with the invention, for generating a patient profile within the parameters of the healthcare administration system;
  • Figure 3 is a flowchart showing an example of a care intervention process carried out within the parameters of the healthcare administration system
  • Figure 4 is a page of a GUI generated on a wireless communication device of the invention by a software product of the invention, for a care intervention schedule;
  • Figure 5 is a schematic diagram showing a broad layout of a system infrastructure for a second embodiment of a healthcare administration system in accordance with the present invention
  • Figure 6 is a schematic diagram showing hotkeys generated by the software product on the wireless communication device in the form of a PDA
  • Figure 7 is a representation of a ratings and funding report generated for a patient by the software product for facilitating data entry into a database of the healthcare administration system;
  • Figure 8a is a representation of a first page of a worksheet summary generated for a patient by the software product
  • Figure 8b is a representation of a further page of the worksheet summary of Fig. 8a;
  • Figure 8c is a representation of a first page of a worksheet relating to a care status of the patient of Fig. 8a generated by the software product;
  • Figure 8d is a representation of a further page of the worksheet of Fig. 8c
  • Figure 8e is a representation of a further page of the worksheet of Fig. 8c
  • Figure 9 is a block diagram showing the overall logical architecture of the first embodiment of the healthcare administration system.
  • Figure 10 is a block diagram showing the web form architecture for a staff member logon generated on the PDA of the invention by the software product;
  • Figure 11 is block diagram showing the web form architecture for information relating to patients which is generated on the PDA by the software product;
  • Figure 12 is a block diagram showing the web form architecture of a "to do" list generated on the PDA by the software product;
  • Figure 13 is a block diagram showing the web form architecture for an administrator log on generated on a workstation by the software product
  • Figure 14 is a block diagram showing the logical design for a care intervention process carried out within the parameters of the healthcare administration system
  • Figure 15 is a block diagram of a relational database generated by the software product which includes tables generated by the software product;
  • Figure 16 is a block diagram showing the web form relationships for PDA log on
  • Figure 17 is a block diagram showing the web form relationships generated by the software product for logging on as a staff member
  • Figure 18 is a block diagram showing the web form relationships generated by the software product for logging on as an administrator;
  • Figure 19 is a block diagram showing various web forms generated by the software product for different care plans;
  • Figure 20 is a block diagram showing various web forms generated by the software product for clinical data collection sheets.
  • FIG. 1 A first embodiment of a healthcare administration system 2a, according to the present invention is shown in Figure 1.
  • the system 2a is described with reference to aged care whereby the patients are long term residents.
  • the system 2a could be equally applicable to hospital resident care where patients are short term residents, or other similar care systems.
  • the healthcare administration system 2a includes a computer 4 at a central location.
  • the computer 4 defines a database for storing resident information and is connected to a network 6.
  • the network 6 is a wireless fidelity (WI-FI) intranet.
  • the healthcare administration system 2a also includes a pair of wireless communication devices in the form of personal digital assistants (PDAs) 8. Each PDA 8 is interfaced to the WI-FI 6 via a wireless communication link 10.
  • the computer 4 includes a database server 12 for storing and managing a database of resident information. Additionally, the computer 4 also includes a web server 14 for interfacing the database with the WI-FI 6.
  • the database server 12 and web server 14 are interfaced together through a local area network (LAN) 13.
  • LAN local area network
  • the healthcare administration system 2a enables a carer to manage resident information stored on the database using a PDA 8.
  • the PDA 8 is typically located at an end user location which is remote from the central location where the computer 4 is located.
  • the healthcare administration system 2a also includes a work station computer 15 which is connected to the computer 4 via the LAN 13.
  • the work station computer 15 enables a carer to view and manipulate the resident information stored on the database server 12.
  • the PDA 8 is loaded with a software product in accordance with the invention which, when executed, facilitates an interface between the PDA 8 and the computer 4.
  • resident information is stored in a single database at the central location.
  • Carers such as doctors and nurses are able to interface with the database using the PDA 8 when they are not located in close proximity to either the database or the resident.
  • a carer can readily view and modify resident information as he or she wanders around the care facility in which the resident resides.
  • the PDA 8 is Intemet- enabled, a carer can view and modify such information at a home of the resident.
  • reference numeral 16 generally indicates a flowchart that broadly illustrates a method, in accordance with the invention, of generating a resident profile within the parameters of the healthcare administration system 2a.
  • An aged care (AC) document 18 is prepared on the resident admission date, and contains general information relating to the resident such as address details.
  • a resident care status (RCS) document 20 is prepared using details from the AC document 18 and includes information about particular care requirements for the resident.
  • assessment forms 22 and data collection forms 24 are prepared.
  • a number of electronic care plans 26 are prepared using resident information from the RCS document 20, the assessment forms 22 and the data collection forms 24.
  • the care plans 26 outline particular care requirements of residents, and resident information can be shared between care plans 26 via electronic notes entered at 34.
  • a software product of the invention is configured to generate care intervention data at 28 based upon the electronic care plans 26.
  • Care interventions outline how associated care plans 26 for a resident are to be implemented.
  • Care interventions are also based upon details relating to additional resident information including any additional treatments, or acute care requirements entered at 30, and prescribed activities entered at 32.
  • the software product includes a log file 36 in which information is stored. Any modifications made to resident information can be stored in the log file 36 which is located in the central location.
  • the software product is configured to store details regarding the status of both complete and incomplete care interventions in the log file 36.
  • the software product is also configured to store data collected from the RCS document 20, the assessment forms 22, the data collection forms 24, the care plans 26, care intervention data input by a carer actioning a care intervention, and any notes in the log file 36.
  • the software product is configured to generate sample reports from the log file 36.
  • sample reports typically include: incomplete care intervention data; all log entries made within a 24 hour period for a particular resident; all changes made since a previous resident care status (RCS) assessment in care plans 26 which may give rise to a change in an RCS category and a listing of all activities for a resident in the previous week.
  • the notes entered at 34 are sent to the log file 36 and typically include doctor's notes, case conference notes, and process/incident notes.
  • the carer can view and modify resident information using the PDA 8.
  • the PDA 8 is configured to receive care intervention data which is generated by the software product of the invention. Additionally, the PDA 8 is configured to receive data from the log file 36. The PDA 8 is configured so that the carer has access to data by using a range of hotkeys which are available on the PDA 8.
  • Figure 3 shows an example of a care intervention which has been generated from a care plan 26 by the software product.
  • the care intervention relates to the bathing of a particular resident named Mrs. Smith.
  • a carer or a group of staff are assigned to carry out the care intervention on the resident.
  • the software product generates a decision tree on the PDA 8 based on whether or not the care intervention has been completed. If the carer inputs an affirmative response, the software product records the current date, time and carer identification number in the log file 36 (step 42).
  • the software product generates a decision tree on the PDA 8 based on whether or not any progress notes are to be recorded. If the carer inputs a negative response, the care intervention is closed at step 46. If the carer inputs a positive response, the software product generates an input field so that the progress notes are entered by the carer at step 48.
  • the software product then passes control to step 50, where the software product generates a decision tree based on whether or not the inputting of progress notes is complete so that the software product can evaluate whether or not all of the progress notes have been recorded.
  • the decision tree automatically defaults to "no" at step 52, in which case the software product records an incomplete care intervention and passes control back to step 50. If the carer inputs a positive response at step 50, the software product stores details of the input progress notes in the log file 36 and appends the notes to staff details previously entered into the log file 36 (step 54).
  • step 56 the software product records the current date, time, and carer identification number in the log file 36 (step 58) together with details of the incomplete care intervention.
  • the software product then generates a decision tree at step 60, based on whether or not there are any notes to be recorded. If the carer inputs a negative response, the software product will flag the care intervention at step 62 for the attention of the carer's supervisor. If the carer inputs a positive response, the software product generates an interface for the user to enter notes at step 64 and passes control to step 66 where a decision tree is generated based on whether or not the notes to be recorded are incomplete. The decision tree at step 66 automatically defaults to "no" (step 68) in which case the software product records an incomplete care intervention and passes control back to step 66. If the carer inputs a positive response at step 66, the entered notes are stored in the log file 36 and the details of the incomplete care intervention are recorded to be followed up by the carer's supervisor at a later stage (step 70).
  • FIG. 4 shows a page of a graphical user interface (GUI) 72 for a care intervention generated by the software product on the PDA 8.
  • GUI 72 provides a schedule by which carers can assist residents in their daily routines.
  • the schedule includes information regarding the type of care to be provided to the resident 74, the daily frequency at which the care should be provided 76 (i.e. morning, afternoon and night), and the days of the week 78 (i.e. Mon, Tue, etc.).
  • the information is thus used by carers to complete care interventions that includes timing, information about the resident, and work instructions to assist in carrying out the care intervention. All of the foregoing information is available to the carer via the PDA 8 when the software product is executed.
  • a healthcare administration system 2b as shown in Figure 5.
  • the healthcare administration system 2b includes a structured query language (SQL) database server 12 which is interfaced to a server 74, for example an Atlas server 74.
  • the database server 12 is also interfaced with a web server (not shown) which, in turn, interfaces with the Internet 76 via a wide area network (WAN) 78.
  • WAN wide area network
  • VPN virtual private network
  • the work station computers 15 are interfaced to the VPN 80 via an Asymmetric Digital Subscriber Line (ADSL) modem 82.
  • ADSL Asymmetric Digital Subscriber Line
  • PDA's 8 which are interfaced with the ADSL modem 82 via a wireless link 10.
  • the healthcare administration system 2b also includes a number of the fixed work station computers 15 at a second end user location 23 which are each interfaced to a LAN 13.
  • PDA's 8 which are interfaced with the LAN 13 via a wireless link 10.
  • the PDA's 8 are able to run conventional software packages such as Microsoft Internet Explorer as well as tailored software products for managing resident information stored in the SQL database.
  • the PDA's 8 at the first user location 21 enable carers to view and modify resident information from a remote location.
  • the PDA's 8 at the second user location 23 enable the carers to view and modify resident information at a care facility in which the residents reside or at the homes of such residents.
  • resident information is maintained within the centrally located SQL database 12 which is accessible using PDA's 8 both operating in the care facility and from locations remote from the care facility.
  • the healthcare administration systems 2a, 2b have the benefit of requiring that only one database be maintained and backed-up.
  • reports and statistics can be generated using the resident information on the database with the PDA's 8, and carers are able to access resident information on the centrally located database from a number of locations simultaneously. Carers thus have the latest progress notes, care plans and other resident information available to them, whether at work or at home.
  • the healthcare administration systems 2 track a history of care plans 26 and care intervention changes which allows carers to readily view the changing care needs of a particular resident.
  • Carers are also able to view resident notes using the PDA 8.
  • the types of notes to be viewed include: notes to attach to care interventions generated from within care plans 26 to assist carers in completing those care interventions; notes to the care plans 26; and notes which are passed to care interventions which are generated by non-associated care plans 26.
  • Figure 6 shows a list of hotkeys which are generated by the software product to facilitate interfacing the PDA 8 with the web server 14. The hotkeys minimize cluttering of the relatively small PDA 8 displays and allow for quick activation of the various carer functions (F).
  • the safety hotkey F1 can be used to display precautionary information in relation to a care intervention, prior to displaying the care intervention.
  • a carer could be forewarned that a resident is violent, before showering the resident when executing the care intervention.
  • Other hotkeys include a behaviour hotkey F2, a carer alert hotkey F3, a communication hotkey F4, a medical alert hotkey F5 and a mobility hotkey F6, each of which are available to the carer at any time during a care intervention, whether at a facility or at a home of the resident.
  • the software product is configured so that the resident care status (RCS) reports 20 can be generated using the PDA 8 or computers 15 and printed on printers 84 which are interfaced with the server 74.
  • Resident care status reporting enables a carer to generate comprehensive reports with the software product in relation to residents including, for example, reports related to a resident's funding status. Examples of funding status reports (FSR) are shown in Figures 7, 8a and 8b.
  • the FSR shows a rating 86 generated by the software product in response to answers to a questionnaire input by the carer using a PDA 8 for a range of criteria for a resident.
  • a funding amount 88 is calculated by the software product based upon a total score 90.
  • Figure 8c shows a RCS worksheet generated for a resident by the software product.
  • the RCS worksheet contains: a title block 92 which includes patent information; a scoring section 94 in which a score is allocated for various resident attributes; and a summary block 96.
  • Figure 9 shows the overall logical architecture of the healthcare administration system 2a.
  • Web forms (or pages) are managed by an application service provider (ASP) 100 of the software product and displayed on the PDA 8.
  • the ASP 100 is wirelessly interfaced to the web server 14 which, in turn, is interfaced to the database 12.
  • the web server 14 includes a visual basic VB.NET server component 101 and a data access component 103 which are interfaced together.
  • the VB.NET server component 101 interfaces with the ASP 100 and the data access component 103 interfaces with the database 12.
  • Figure 10 shows the web form architecture generated by the ASP 100 for a carer (staff member) log on.
  • the ASP 100 prompts the staff member to log on at 108, by entering a personal identification number (PIN) into the PDA 8 to thereby validate that they are entitled to access resident information stored in the database 12.
  • PIN personal identification number
  • the ASP 100 prompts the carer to select the facility in which a particular resident resides, once the carer's identification has been validated.
  • the ASP 100 generates a main menu which is displayed on the PDA 8.
  • the ASP 100 is configured so that the main menu displays menu options available to a carer.
  • the menu options include a residents option 114, a "to do" list option 116, an email option 118, and an asset and maintenance option 120.
  • Figure 11 shows the web form architecture generated by the ASP 100 for the residents option 114 in the main menu 112.
  • the ASP 100 is configured to permit selection of this option to enable a carer to access a resident details sub-menu 122.
  • the resident details sub-menu 122 includes a care interventions sub-menu 124a which, in turn, includes a care intervention details sub-menu 124b which, in turn, includes a care plan details sub-menu 124c and a note details sub-menu 124d.
  • the resident details sub-menu 122 also includes a notes sub-menu 126a which, in turn, includes a note details sub-menu 126b.
  • the resident details sub-menu 122 includes a care plans sub-menu 128a which, in turn, includes a care plan details submenu 128b.
  • the resident details sub-menu 122 also includes a hotkeys submenu 130a which, in turn, includes a care plan details sub-menu 130b.
  • the resident details sub-menu 122 includes a quick reports sub-menu 132a which, in turn, includes care plan details sub-menus 132b and 132c.
  • the resident details sub-menu 122 also includes a data collection sheets submenu 134a which, in turn, includes a care plan details sub-menu 134b.
  • Figure 12 shows the web form architecture generated by the ASP 100 for the "to do” list option 116 in the main menu 112.
  • the "to do” list option 116 has a care intervention groups sub-menu 136 which lists the available care intervention groups.
  • the care intervention groups sub-menu 136 has a care interventions list sub-menu 138 which lists any available care interventions.
  • the care intervention list sub-menu 138 has a care intervention details sub- menu 140 which lists the details of each care intervention.
  • the care intervention details sub-menu 140 has two sub-menus, being a care intervention notes sub-menu 142 and a care plans sub-menu 144.
  • Figure 13 shows the web form architecture generated by the ASP 100 for an administrator.
  • An administrator log on menu 146 is provided.
  • the administrator log on menu 146 has a main administration sub-menu 148.
  • the main administration sub-menu 148 has a care intervention groups sub-menu 150, a care intervention management sub-menu 152, a staff log on sub-menu 154, and an email sub-menu 156.
  • the care intervention groups sub-menu 150 has a care intervention group details sub-menu 158.
  • the care intervention management sub-menu 152 has a care intervention details submenu 160.
  • the care intervention details sub-menu 160 has a care plan submenu 162 and a note sub-menu 164.
  • the staff log on sub-menu 154 has a further staff log on sub-menu 156.
  • Figure 14 is a block diagram showing the logical design for a care intervention process generated by the ASP 100. Initially, the care intervention process is created at step 166 and a "request" status code (RQ) is generated by the ASP 100.
  • RQ request status code
  • the ASP 100 If the process is cancelled, the ASP 100 generates a "cancelled" status code (CN) at step 168. Accordingly, the process is then finished at step 171.
  • the ASP 100 If the process is assigned to a carer, the ASP 100 generates an "assignment" status code (IS) representing an assignment to a carer at step 170 and the process proceeds to query step 172.
  • IS assignment status code
  • the ASP 100 queries whether the care intervention is complete.
  • the ASP 100 If the carer responds that the care intervention is complete at step 172, the ASP 100 generates a "completed" status code (CO) and the care intervention is recorded as complete at step 174. Subsequently, the care intervention is automatically closed and the ASP 100 generates a "fully completed” status code (CC) at step 176. The process is thereby recorded as finished at step 171.
  • CO completed status code
  • CC fully completed status code
  • the ASP 100 If the carer responds that the care invention is not complete at 172, the ASP 100 generates an "incomplete" status code (IN) at step 178.
  • the ASP 100 provides the supervisor with the discretion to reassign the care intervention to another staff member (i.e. carer).
  • the ASP 100 generates an "incomplete and closed” status code (IC) at step 180 whereby the care intervention is recorded as incomplete and is closed by the supervisor.
  • IC "incomplete and closed" status code
  • the physical design is described with reference to pseudo-code set out below which illustrates the data model for creating various tables in a relational database for the healthcare administration system 2a.
  • the following is pseudo-code of the software product for creating a care intervention table.
  • the care intervention table stores data relating to all the care interventions generated by the software product.
  • Care intervention data can be assigned to care intervention groups according to health care facilities at which the care interventions are carried out.
  • Figure 15 illustrates the relational database generated by the software product, and shows data flow between various tables including those generated by the software product as illustrated above.
  • the relational database includes a care intervention table 182, a care intervention group table 184, a care intervention group facility table 186, a care intervention note table 188, a care intervention status table 190, a log file table 192, a resident intervention table 194, a location table 196, a facility table 198, a users table 200 and a resident table 202.
  • the software product associates data in the care intervention table 182 with data in the resident intervention table 194, the care invention group table 184, and the care intervention status table 190.
  • the software product associates data in the care intervention table 182 and the care intervention group facility 186 with data in the care intervention group table 184.
  • the software product associates data in the care intervention group facility table 186 with data in the care intervention group table 184 and the facility table 198.
  • the software product associates data in the care intervention note table 188 with data in the resident table 202 and the resident intervention table 194.
  • the software product associates data in the care intervention table 182 with data in the care intervention status table 190.
  • the software product associates data in the log file table 192 with data in the user table 200.
  • the software product associates data in the care intervention table 182 and care intervention note table 188 with data in the resident information table 194.
  • the software product also associates data in the resident information table 194 with data in the resident table 202.
  • the software product associates data in the care intervention group facility table 186 and the facility table 198 with data in the location table 196.
  • the software product associates data in the care intervention group facility table 186 and the resident table 202 with data in the facility table 198.
  • the software product associates data in the log file table 192 with data in the user's table 200.
  • the software product associates data in the resident intervention table 194 and care intervention note table 188 with data in the resident table 202.
  • the software product also associates data in the resident table 202 with data in the facility table 198.
  • the software product is configured to generate a large number of different reports from the relational database shown in Figure 15.
  • the software product is configured to generate the reports shown in the second column upon entry of corresponding SQL commands in the first column.
  • a web interface generated by the software product is described below.
  • Figure 16 is a block diagram showing the web form (i.e. page) relationships generated by the software product for a PDA (mobile system) logon.
  • a home page 204 is generated which redirects to a log in page 206.
  • System administrators and supervisors are able to access the log in page 206.
  • Normal staff members i.e. carers
  • Administrators and supervisors are able to access an administrator/supervisor menu page 208.
  • Carers are able to access a main menu page 210. Administrators and supervisors are also able to access the main menu page 210.
  • Figure 17 shows the web form relationships generated by the software product for logging on as a staff member.
  • a note detail page 212 is generated.
  • a main menu page 214 is generated under the note detail page 212. Navigation is facilitated between the main menu page 214 and a residents page 216, a "to do" list page 218 and an email page 220.
  • Navigation is facilitated between the residents page 216 and a resident details page 222. Navigation is facilitated between the resident details page 222 and: a data collection sheet page 224, a resident notes page 226, a care plans page 228, a hotkeys page 230 and a quick report page 232. Navigation is facilitated between the data collection sheets page 224 and a clinical data collection sheets page 234. Navigation is facilitated between the resident notes page 226 and: a note details page 236 and a new note page 238. Navigation is facilitated between the note details page 236 and an edit note page 240. Navigation is facilitated between the care plans page 228 and a care plan page 242. Navigation is facilitated between the hotkeys page 230 and a care plan page 244. Navigation is facilitated between the quick report page 232 and: a note details page 246 and a care plan page 248. Navigation is facilitated between the note details page 246 and an edit note page 250.
  • Navigation is facilitated between the "to do" list page 218 and a care intervention details page 252.
  • Navigation is facilitated between the care intervention details page 252 and: a note details page 254, a new note page 256 and a care plan page 258.
  • Navigation is facilitated between the note details page 254 and an edit note page 260.
  • Navigation is facilitated between the email page 220 and: a new email page 222 and an email message page 224.
  • Figure 18 shows the web form relationships generated by the software product for logging on as an administrator.
  • An administrator/supervisor menu page is provided at 326. Navigation is facilitated between the administrator/supervisor menu page 326 and: a care intervention group setup page 328, a care intervention management page 330, a staff log on page 332 and an email page 334. The carer is able to navigate from the staff log on page 332 to a main menu page 336 and, in turn, return to the administrator/supervisor menu 326.
  • Navigation is facilitated between the care intervention management page 330 and a care intervention details page 338.
  • Navigation is facilitated between the care intervention details page 338 and: an "assign to staff" page 340, a note details page 342, a "new note” page 344, and a care plan page 346.
  • Navigation is facilitated between the note details page 342 and an edit note page 348.
  • a carer is able to navigate from the email page 334 to: a new email page 348 and an email message page 350.
  • Figure 19 shows a range of care plan web pages generated by the software product.
  • Figure 20 shows a range of clinical data collection web pages generated by the software product.
  • the present invention provides a method of administering a healthcare administration system 2.
  • the method includes the steps of maintaining a database in which resident information is stored, establishing a wireless communication protocol between the database and the PDA 8, and generating an interface on the PDA 8 so that the PDA 8 can interface with the database.
  • the present invention enables resident information to be stored in a single centrally located database.
  • the present invention also enables carers, such as doctors and nurses, to interface with the database when they are not located in close proximity to either the database or the resident.
  • Some embodiments of the present invention provide a means for enabling a carer to view and modify resident information as he or she wanders around a care-facility in which the resident resides.
  • a PDA was used for wirelessly communicating with the network 6.
  • other types of wireless communication device could be used such as, for example, a keyboard enhanced PDA.

Abstract

A healthcare administration system includes a computer programmed to define a database for storing patient information and connected to a network at a central location. At least one wireless communication device is connected to the network at an end user location, the, or each, wireless communications device being configured to define an interface with the database, via the network.

Description

A HEALTHCARE ADMINISTRATION SYSTEM
TECHNICAL FIELD
The present invention relates to a healthcare administration system.
The present invention also relates to a wireless communication device which is configured to permit a user to interface with a remote database. Additionally, the present invention relates to a software product which, when executed, facilitates said interface with the remote database.
The present invention also relates to a method of administering a healthcare system.
BACKGROUND
Infirm and Aged people are often reliant on palliative care in healthcare facilities such as nursing homes and hospitals. Carers are continually challenged by the varying needs of patients or residents under their care, as each patient has a unique set of issues which require constant attention. It follows that it is important for information records outlining the requirements for each patient to be readily accessible. However, the Applicant has found that keeping accurate and up to date records is extremely challenging as the physical condition of patients is continually subject to change. Manually amending these records by hand can be a laborious task, particularly when the amendments are substantial.
Patient information records are generally kept in close proximity to the patient and, accordingly, a carer must go to the patient to view the patient's information. The Applicant has identified a need for a system whereby a carer can access and manipulate patient information from a location remote from a centrally located database in which patient information is stored. This need also extends to a situation where the carer attends to patients at their homes. In such cases, it is both difficult and inconvenient for carers to have readily available patient information, particularly when the carers have to travel from one patient to the other.
The Applicant has conceived the present invention to address this need and to provide a system in which patient information can be centrally stored and managed. In particular, the Applicant has conceived the present invention to provide a means whereby patients can be cared for by carers with full and complete information relating to the patients at their disposal.
Definitions
"Care Intervention" - data representing any process that is carried out by a carer to care, treat, control or otherwise interact with a patient.
"Carer" - any person, including professionals such as nurses, doctors or specialists employed in the healthcare industry.
"Computer" - a computational device including one or more processors including personal computers (PCs), mainframes, servers or the like.
"Patient" - any person who is a patient or a resident in a healthcare facility such as a hospital or aged care home, or in the community who receives care at home. In this specification, the words "patient" and "resident" are to be considered interchangeable.
"Patient Information" - information relating to a patient that includes information that would usually be collected at a healthcare facility, such as: mobility, food allowances/restrictions, personal hygiene issues, toileting issues, bladder management, bowel management, behavioural characteristics, emotional characteristics, social and human needs, medication needs, therapy needs, vision, hearing, and any other information that could assist in patient management. "Patient Profile" - A description of a patient that can be stored electronically and that is based at least partially on the patient information and is stored in tables to facilitate associations and retrieval of the patient information.
"Electronic Care Plan (ECP)" - Data representing a series of actions to be taken when dealing with a particular patient and based at least partially on the patient profile.
"Wireless communication" - communication which does not require the use of a wired link, including radio frequency (RF) links such as Bluetooth®, for example, or any other long distance wireless protocols, such as code division multiple access (CDMA) broadband.
"Personal Digital Assistant (PDA)" - A portable computational device that is configured to communicate wirelessly with other computational devices, via a network, such as a combination of a wireless network and the Internet.
SUMMARY OF THE INVENTION
According to a first aspect of the invention, there is provided a healthcare administration system that includes a computer programmed to define a database for storing patient information and connected to a network at a central location; and at least one wireless communication device connected to the network at an end user location, the, or each, wireless communication device being configured to define an interface with the database, via the network.
The computer may include a database server for storing and managing the database and a web server for interfacing the database with the network.
The network may be a Wireless Fidelity (WIFI) intranet through which the, or each, wireless communication device interfaces with the web server.
The, or each, wireless communication device may be a personal digital assistant (PDA). The system may include at least one workstation computer at the end user location that interfaces with the web server via one of a local area network (LAN) and the Internet.
Said interface defined by the wireless communication device may be in the form of a virtual private network (VPN).
According to a second aspect of the invention, there is provided a method of administering a healthcare system, the method including the steps of: inputting data representing patient information into a database; manipulating the patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
The step of maintaining the database may include the step of generating patient profiles within the database.
The method may include the step of generating electronic care plans (ECP's) using the patient profile.
The method may include the step of providing a notes interface so that a carer can enter further patient information into the database to be accessible via the interface.
The method may include the step of generating care interventions based on the ECP's.
The method may include the step of generating reports from data stored in the database. According to a third aspect of the invention, there is provided a software product for use in a healthcare administration system, the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the method as described above.
According to a fourth aspect of the invention, there is provided a software product for use in a healthcare administration system, the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the following steps: providing a database in which patient information can be stored; manipulating patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
The software product may be configured to define an application service provider (ASP) to manage web forms to be displayed on the wireless communication device.
The ASP may be configured to generate web form architecture to permit a carer to log in to the healthcare administration system.
The ASP may be configured to generate the web form architecture such that the PDA carries out one or more of the following steps: prompts a carer to enter data representing a facility in which a patient resides; generates menu options to facilitate access to patient information and to facilitate the input of data, such as note data to the database.
The ASP may be configured to generate the web form architecture such that the PDA can carry out one or more of the following steps: provides a log on menu for an administrator; generates menu options to facilitate access to information including care interventions. The ASP may be configured to generate the web form architecture to define a care intervention.
The ASP may be configured to generate the web form architecture such that the PDA can communicate the assignment of the care intervention to a carer.
The ASP may be configured to generate the web form architecture such that the PDA can prompt a carer to input data indicating whether or not the care intervention is complete.
The software product may be configured to provide a relational database. In particular, the software product may be configured to generate a care intervention table of the relational database such that the care intervention table stores data relating to care interventions generated by the software product.
The software product may be configured to generate a care intervention groups table of the relational database such that the care intervention groups table stores data relating to care interventions associated with particular facilities at which the care interventions are carried out.
The software product may be configured to generate a care intervention group facility table such that the care intervention group facility table stores data relating to all facilities linked to particular intervention groups.
The software product may be configured to generate a care intervention note table, such that the care intervention note table relates notes and corresponding care interventions.
The software product may be configured to generate a care intervention status table, such that the care intervention status table stores status codes used for respective care interventions. According to a fifth aspect of the invention, there is provided a software product for use in a healthcare administration system, the software product being executable on a personal digital assistant (PDA) and being configured so that, when executed, establishes an interface with the software product as described above.
The software product may be configured so that the PDA can generate a graphic user interface (GUI) to permit a carer to interface with the software product of the third and fourth aspects of the invention.
The software product may be configured so that the PDA can generate a decision tree to permit a carer to input data representing whether or not one or more of the following steps have been carried out by the carer: a particular care intervention has been completed; progress notes are to be input.
The software product may be configured so that the PDA can communicate details relating to said one or more of the steps to the database.
According to sixth aspect of the invention, there is provided a personal digital assistant (PDA) programmed with a software product as described above.
The personal digital assistant may be Internet-enabled.
BRIEF DESCRIPTION OF THE DRAWINGS Preferred features, embodiments and variations of the invention may be discerned from the following Detailed Description which provides sufficient information for those skilled in the art to perform the invention. The Detailed Description is not to be regarded as limiting the scope of the preceding Summary of the Invention in any way. The Detailed Description will make reference to a number of drawings as follows:
Figure 1 is a schematic diagram showing a broad layout of a system infrastructure for a first embodiment of a healthcare administration system in accordance with the invention; Figure 2 is a broad flowchart illustrating a method, in accordance with the invention, for generating a patient profile within the parameters of the healthcare administration system;
Figure 3 is a flowchart showing an example of a care intervention process carried out within the parameters of the healthcare administration system;
Figure 4 is a page of a GUI generated on a wireless communication device of the invention by a software product of the invention, for a care intervention schedule;
Figure 5 is a schematic diagram showing a broad layout of a system infrastructure for a second embodiment of a healthcare administration system in accordance with the present invention;
Figure 6 is a schematic diagram showing hotkeys generated by the software product on the wireless communication device in the form of a PDA;
Figure 7 is a representation of a ratings and funding report generated for a patient by the software product for facilitating data entry into a database of the healthcare administration system;
Figure 8a is a representation of a first page of a worksheet summary generated for a patient by the software product;
Figure 8b is a representation of a further page of the worksheet summary of Fig. 8a;
Figure 8c is a representation of a first page of a worksheet relating to a care status of the patient of Fig. 8a generated by the software product;
Figure 8d is a representation of a further page of the worksheet of Fig. 8c; Figure 8e is a representation of a further page of the worksheet of Fig. 8c;
Figure 9 is a block diagram showing the overall logical architecture of the first embodiment of the healthcare administration system;
Figure 10 is a block diagram showing the web form architecture for a staff member logon generated on the PDA of the invention by the software product;
Figure 11 is block diagram showing the web form architecture for information relating to patients which is generated on the PDA by the software product;
Figure 12 is a block diagram showing the web form architecture of a "to do" list generated on the PDA by the software product;
Figure 13 is a block diagram showing the web form architecture for an administrator log on generated on a workstation by the software product;
Figure 14 is a block diagram showing the logical design for a care intervention process carried out within the parameters of the healthcare administration system;
Figure 15 is a block diagram of a relational database generated by the software product which includes tables generated by the software product;
Figure 16 is a block diagram showing the web form relationships for PDA log on;
Figure 17 is a block diagram showing the web form relationships generated by the software product for logging on as a staff member;
Figure 18 is a block diagram showing the web form relationships generated by the software product for logging on as an administrator; Figure 19 is a block diagram showing various web forms generated by the software product for different care plans; and
Figure 20 is a block diagram showing various web forms generated by the software product for clinical data collection sheets.
^DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
A first embodiment of a healthcare administration system 2a, according to the present invention is shown in Figure 1. In this particular embodiment, the system 2a is described with reference to aged care whereby the patients are long term residents. However, it is to be understood that the system 2a could be equally applicable to hospital resident care where patients are short term residents, or other similar care systems.
The healthcare administration system 2a includes a computer 4 at a central location. The computer 4 defines a database for storing resident information and is connected to a network 6. In the present embodiment, the network 6 is a wireless fidelity (WI-FI) intranet. The healthcare administration system 2a also includes a pair of wireless communication devices in the form of personal digital assistants (PDAs) 8. Each PDA 8 is interfaced to the WI-FI 6 via a wireless communication link 10. The computer 4 includes a database server 12 for storing and managing a database of resident information. Additionally, the computer 4 also includes a web server 14 for interfacing the database with the WI-FI 6. The database server 12 and web server 14 are interfaced together through a local area network (LAN) 13.
The healthcare administration system 2a enables a carer to manage resident information stored on the database using a PDA 8. In use, the PDA 8 is typically located at an end user location which is remote from the central location where the computer 4 is located. The healthcare administration system 2a also includes a work station computer 15 which is connected to the computer 4 via the LAN 13. The work station computer 15 enables a carer to view and manipulate the resident information stored on the database server 12. The PDA 8 is loaded with a software product in accordance with the invention which, when executed, facilitates an interface between the PDA 8 and the computer 4. Advantageously, resident information is stored in a single database at the central location. Carers such as doctors and nurses are able to interface with the database using the PDA 8 when they are not located in close proximity to either the database or the resident. A carer can readily view and modify resident information as he or she wanders around the care facility in which the resident resides. Furthermore, if the PDA 8 is Intemet- enabled, a carer can view and modify such information at a home of the resident.
In Figure 2, reference numeral 16 generally indicates a flowchart that broadly illustrates a method, in accordance with the invention, of generating a resident profile within the parameters of the healthcare administration system 2a.
An aged care (AC) document 18 is prepared on the resident admission date, and contains general information relating to the resident such as address details. A resident care status (RCS) document 20 is prepared using details from the AC document 18 and includes information about particular care requirements for the resident.
In addition, assessment forms 22 and data collection forms 24 are prepared. A number of electronic care plans 26 are prepared using resident information from the RCS document 20, the assessment forms 22 and the data collection forms 24. The care plans 26 outline particular care requirements of residents, and resident information can be shared between care plans 26 via electronic notes entered at 34.
A software product of the invention is configured to generate care intervention data at 28 based upon the electronic care plans 26. Care interventions outline how associated care plans 26 for a resident are to be implemented. Care interventions are also based upon details relating to additional resident information including any additional treatments, or acute care requirements entered at 30, and prescribed activities entered at 32.
The software product includes a log file 36 in which information is stored. Any modifications made to resident information can be stored in the log file 36 which is located in the central location. The software product is configured to store details regarding the status of both complete and incomplete care interventions in the log file 36. The software product is also configured to store data collected from the RCS document 20, the assessment forms 22, the data collection forms 24, the care plans 26, care intervention data input by a carer actioning a care intervention, and any notes in the log file 36. The software product is configured to generate sample reports from the log file 36. These sample reports typically include: incomplete care intervention data; all log entries made within a 24 hour period for a particular resident; all changes made since a previous resident care status (RCS) assessment in care plans 26 which may give rise to a change in an RCS category and a listing of all activities for a resident in the previous week. The notes entered at 34 are sent to the log file 36 and typically include doctor's notes, case conference notes, and process/incident notes.
The carer can view and modify resident information using the PDA 8. The PDA 8 is configured to receive care intervention data which is generated by the software product of the invention. Additionally, the PDA 8 is configured to receive data from the log file 36. The PDA 8 is configured so that the carer has access to data by using a range of hotkeys which are available on the PDA 8.
Figure 3 shows an example of a care intervention which has been generated from a care plan 26 by the software product. The care intervention relates to the bathing of a particular resident named Mrs. Smith.
Initially, at step 38, a carer or a group of staff are assigned to carry out the care intervention on the resident. At step 40, the software product generates a decision tree on the PDA 8 based on whether or not the care intervention has been completed. If the carer inputs an affirmative response, the software product records the current date, time and carer identification number in the log file 36 (step 42).
At step 44, the software product generates a decision tree on the PDA 8 based on whether or not any progress notes are to be recorded. If the carer inputs a negative response, the care intervention is closed at step 46. If the carer inputs a positive response, the software product generates an input field so that the progress notes are entered by the carer at step 48.
The software product then passes control to step 50, where the software product generates a decision tree based on whether or not the inputting of progress notes is complete so that the software product can evaluate whether or not all of the progress notes have been recorded. The decision tree automatically defaults to "no" at step 52, in which case the software product records an incomplete care intervention and passes control back to step 50. If the carer inputs a positive response at step 50, the software product stores details of the input progress notes in the log file 36 and appends the notes to staff details previously entered into the log file 36 (step 54).
If subsequent to step 40, the carer inputs a negative response (step 56), the software product records the current date, time, and carer identification number in the log file 36 (step 58) together with details of the incomplete care intervention.
The software product then generates a decision tree at step 60, based on whether or not there are any notes to be recorded. If the carer inputs a negative response, the software product will flag the care intervention at step 62 for the attention of the carer's supervisor. If the carer inputs a positive response, the software product generates an interface for the user to enter notes at step 64 and passes control to step 66 where a decision tree is generated based on whether or not the notes to be recorded are incomplete. The decision tree at step 66 automatically defaults to "no" (step 68) in which case the software product records an incomplete care intervention and passes control back to step 66. If the carer inputs a positive response at step 66, the entered notes are stored in the log file 36 and the details of the incomplete care intervention are recorded to be followed up by the carer's supervisor at a later stage (step 70).
Figure 4 shows a page of a graphical user interface (GUI) 72 for a care intervention generated by the software product on the PDA 8. The GUI 72 provides a schedule by which carers can assist residents in their daily routines. The schedule includes information regarding the type of care to be provided to the resident 74, the daily frequency at which the care should be provided 76 (i.e. morning, afternoon and night), and the days of the week 78 (i.e. Mon, Tue, etc.). The information is thus used by carers to complete care interventions that includes timing, information about the resident, and work instructions to assist in carrying out the care intervention. All of the foregoing information is available to the carer via the PDA 8 when the software product is executed.
According to a second embodiment of the present invention, there is provided a healthcare administration system 2b as shown in Figure 5. With reference to Figures 1 to 4, like reference numerals refer to like parts, unless otherwise specified. The healthcare administration system 2b includes a structured query language (SQL) database server 12 which is interfaced to a server 74, for example an Atlas server 74. The database server 12 is also interfaced with a web server (not shown) which, in turn, interfaces with the Internet 76 via a wide area network (WAN) 78. At a first end user location 21 , there is provided a virtual private network (VPN) 80 which provides an interface between the Internet 76 and a number of work station computers 15. The work station computers 15 are interfaced to the VPN 80 via an Asymmetric Digital Subscriber Line (ADSL) modem 82. There is also provided a number of Internet-enabled PDA's 8 which are interfaced with the ADSL modem 82 via a wireless link 10. The healthcare administration system 2b also includes a number of the fixed work station computers 15 at a second end user location 23 which are each interfaced to a LAN 13. There is also provided a number of PDA's 8 which are interfaced with the LAN 13 via a wireless link 10.
The PDA's 8 are able to run conventional software packages such as Microsoft Internet Explorer as well as tailored software products for managing resident information stored in the SQL database. The PDA's 8 at the first user location 21 enable carers to view and modify resident information from a remote location. In contrast, the PDA's 8 at the second user location 23 enable the carers to view and modify resident information at a care facility in which the residents reside or at the homes of such residents. Hence, resident information is maintained within the centrally located SQL database 12 which is accessible using PDA's 8 both operating in the care facility and from locations remote from the care facility.
The healthcare administration systems 2a, 2b have the benefit of requiring that only one database be maintained and backed-up. In addition, reports and statistics can be generated using the resident information on the database with the PDA's 8, and carers are able to access resident information on the centrally located database from a number of locations simultaneously. Carers thus have the latest progress notes, care plans and other resident information available to them, whether at work or at home. The healthcare administration systems 2 track a history of care plans 26 and care intervention changes which allows carers to readily view the changing care needs of a particular resident.
Carers are also able to view resident notes using the PDA 8. The types of notes to be viewed include: notes to attach to care interventions generated from within care plans 26 to assist carers in completing those care interventions; notes to the care plans 26; and notes which are passed to care interventions which are generated by non-associated care plans 26. Figure 6 shows a list of hotkeys which are generated by the software product to facilitate interfacing the PDA 8 with the web server 14. The hotkeys minimize cluttering of the relatively small PDA 8 displays and allow for quick activation of the various carer functions (F). The safety hotkey F1 can be used to display precautionary information in relation to a care intervention, prior to displaying the care intervention. For example, a carer could be forewarned that a resident is violent, before showering the resident when executing the care intervention. Other hotkeys include a behaviour hotkey F2, a carer alert hotkey F3, a communication hotkey F4, a medical alert hotkey F5 and a mobility hotkey F6, each of which are available to the carer at any time during a care intervention, whether at a facility or at a home of the resident.
Returning to Figure 5, the software product is configured so that the resident care status (RCS) reports 20 can be generated using the PDA 8 or computers 15 and printed on printers 84 which are interfaced with the server 74. Resident care status reporting enables a carer to generate comprehensive reports with the software product in relation to residents including, for example, reports related to a resident's funding status. Examples of funding status reports (FSR) are shown in Figures 7, 8a and 8b.
In Figure 7, the FSR shows a rating 86 generated by the software product in response to answers to a questionnaire input by the carer using a PDA 8 for a range of criteria for a resident. A funding amount 88 is calculated by the software product based upon a total score 90.
Figure 8c shows a RCS worksheet generated for a resident by the software product. The RCS worksheet contains: a title block 92 which includes patent information; a scoring section 94 in which a score is allocated for various resident attributes; and a summary block 96.
The conceptual and logical design of the first embodiment of the healthcare administration system 2a (as shown in Figure 1) is described below. Figure 9 shows the overall logical architecture of the healthcare administration system 2a. Web forms (or pages) are managed by an application service provider (ASP) 100 of the software product and displayed on the PDA 8. The ASP 100 is wirelessly interfaced to the web server 14 which, in turn, is interfaced to the database 12. The web server 14 includes a visual basic VB.NET server component 101 and a data access component 103 which are interfaced together. The VB.NET server component 101 interfaces with the ASP 100 and the data access component 103 interfaces with the database 12.
Figure 10 shows the web form architecture generated by the ASP 100 for a carer (staff member) log on. Initially, the ASP 100 prompts the staff member to log on at 108, by entering a personal identification number (PIN) into the PDA 8 to thereby validate that they are entitled to access resident information stored in the database 12.
At 110, the ASP 100 prompts the carer to select the facility in which a particular resident resides, once the carer's identification has been validated.
At 112, the ASP 100 generates a main menu which is displayed on the PDA 8. The ASP 100 is configured so that the main menu displays menu options available to a carer. The menu options include a residents option 114, a "to do" list option 116, an email option 118, and an asset and maintenance option 120.
Figure 11 shows the web form architecture generated by the ASP 100 for the residents option 114 in the main menu 112. The ASP 100 is configured to permit selection of this option to enable a carer to access a resident details sub-menu 122. The resident details sub-menu 122 includes a care interventions sub-menu 124a which, in turn, includes a care intervention details sub-menu 124b which, in turn, includes a care plan details sub-menu 124c and a note details sub-menu 124d. The resident details sub-menu 122 also includes a notes sub-menu 126a which, in turn, includes a note details sub-menu 126b. In addition, the resident details sub-menu 122 includes a care plans sub-menu 128a which, in turn, includes a care plan details submenu 128b. The resident details sub-menu 122 also includes a hotkeys submenu 130a which, in turn, includes a care plan details sub-menu 130b. In addition, the resident details sub-menu 122 includes a quick reports sub-menu 132a which, in turn, includes care plan details sub-menus 132b and 132c. The resident details sub-menu 122 also includes a data collection sheets submenu 134a which, in turn, includes a care plan details sub-menu 134b.
Figure 12 shows the web form architecture generated by the ASP 100 for the "to do" list option 116 in the main menu 112. The "to do" list option 116 has a care intervention groups sub-menu 136 which lists the available care intervention groups. The care intervention groups sub-menu 136 has a care interventions list sub-menu 138 which lists any available care interventions.
The care intervention list sub-menu 138 has a care intervention details sub- menu 140 which lists the details of each care intervention. The care intervention details sub-menu 140 has two sub-menus, being a care intervention notes sub-menu 142 and a care plans sub-menu 144.
Figure 13 shows the web form architecture generated by the ASP 100 for an administrator. An administrator log on menu 146 is provided. The administrator log on menu 146 has a main administration sub-menu 148. The main administration sub-menu 148 has a care intervention groups sub-menu 150, a care intervention management sub-menu 152, a staff log on sub-menu 154, and an email sub-menu 156. The care intervention groups sub-menu 150 has a care intervention group details sub-menu 158. The care intervention management sub-menu 152 has a care intervention details submenu 160. The care intervention details sub-menu 160 has a care plan submenu 162 and a note sub-menu 164. The staff log on sub-menu 154 has a further staff log on sub-menu 156.
Figure 14 is a block diagram showing the logical design for a care intervention process generated by the ASP 100. Initially, the care intervention process is created at step 166 and a "request" status code (RQ) is generated by the ASP 100.
If the process is cancelled, the ASP 100 generates a "cancelled" status code (CN) at step 168. Accordingly, the process is then finished at step 171.
If the process is assigned to a carer, the ASP 100 generates an "assignment" status code (IS) representing an assignment to a carer at step 170 and the process proceeds to query step 172.
At query step 172, the ASP 100 queries whether the care intervention is complete.
If the carer responds that the care intervention is complete at step 172, the ASP 100 generates a "completed" status code (CO) and the care intervention is recorded as complete at step 174. Subsequently, the care intervention is automatically closed and the ASP 100 generates a "fully completed" status code (CC) at step 176. The process is thereby recorded as finished at step 171.
If the carer responds that the care invention is not complete at 172, the ASP 100 generates an "incomplete" status code (IN) at step 178. The ASP 100 provides the supervisor with the discretion to reassign the care intervention to another staff member (i.e. carer). Alternatively, the ASP 100 generates an "incomplete and closed" status code (IC) at step 180 whereby the care intervention is recorded as incomplete and is closed by the supervisor. The process then finishes at step 171.
The physical design of the healthcare administration system 2a is described below.
The physical design is described with reference to pseudo-code set out below which illustrates the data model for creating various tables in a relational database for the healthcare administration system 2a. The following is pseudo-code of the software product for creating a care intervention table. The care intervention table stores data relating to all the care interventions generated by the software product.
CREATE TABLE [Carelntervention] (
[CIID] [int] IDENTITY (1, 1) NOT NULL ,
[CIStatusCode] [varchar] (50) COLLATE SQL_Latinl_General_CP850_CI_AS NOT NULL , [LogFilelD] [int] NULL ,
[AssignTo] [int] NULL , [Residentlntervention] [int] NOT NULL , [ScheduledDate] [smalldatetime] NULL ,
[ScheduledTime] [varchar] (5) COLLATE SQL_Latinl_General_CP850_CI_AS NULL ,
CONSTRAINT [PK_PDACI] PRIMARY KEY CLUSTERED
(
[CIID]
) ON [PRIMARY] , CONSTRAINT [FK_CareIntervention_CIGroup] FOREIGN KEY
(
[AssignTo] ) REFERENCES [CIGroup] (
[CIGroupID] ) NOT FOR REPLICATION ,
CONSTRAINT [FK_PDACI_PDACIStatus] FOREIGN KEY
(
[CIStatusCode] ) REFERENCES [CIStatus] ( [CIStatusCode]
),
CONSTRAINT [FK_PDACI_Residentlntervention] FOREIGN KEY
(
[Residentlntervention] ) REFERENCES [Residentlntervention] (
[Residentlntervention]
) ) ON [PRIMARY] GO
The following is pseudo-code of the software product for creating a care intervention group table. Care intervention data can be assigned to care intervention groups according to health care facilities at which the care interventions are carried out.
CREATE TABLE [CIGroup] (
[CIGroupID] [int] IDENTITY (1, 1) NOT NULL , [Description] [varchar] (30) COLLATE SQL_Latinl_General_CP850_CI_AS
NOT NULL ,
[DefaultGroup] [tinyint] NULL , [Disabled] [tinyint] NULL ,
CONSTRAINT [PK_CIGroup] PRIMARY KEY CLUSTERED (
[CIGroupID] ) ON [PRIMARY] ) ON [PRIMARY] GO
The following is pseudo-code of the software product for creating a care intervention group facility table. This table maintains data relating to all facilities linked to the particular intervention groups. Care interventions conducted in common facilities can be assigned to particular groups.
CREATE TABLE [CIGroupFacility] (
[CIGroupFacilitylD] [int] IDENTITY (1, 1) NOT NULL , [CIGroupID] [int] NOT NULL , [Location] [tinyint] NOT NULL , [Facility] [tinyint] NOT NULL ,
CONSTRAINT [PK_CIGroupFacility] PRIMARY KEY CLUSTERED
(
[CIGroupFacilitylD] ) ON [PRIMARY] , CONSTRAINT [FK_CIGroupFaciHty_CIGroup] FOREIGN KEY
( [CIGroupID] ) REFERENCES [CIGroup] (
[CIGroupID]
) NOT FOR REPLICATION , CONSTRAINT [FK_CIGroupFacility_Facility] FOREIGN KEY
(
[Location],
[Facility]
) REFERENCES [Facility] ( [Location],
[Facility]
) NOT FOR REPLICATION , CONSTRAINT [FK_CIGroupFacility_Location] FOREIGN KEY
( [Location]
) REFERENCES [Location] (
[Location]
) NOT FOR REPLICATION ) ON [PRIMARY] GO
The following is pseudo-code of the software product for creating a care intervention note table. This table relates notes and their respective corresponding care interventions.
CREATE TABLE [CINote] (
[CINotelD] [int] IDENTITY (1, 1) NOT NULL , [Resident] [int] NOT NULL ,
[ResidentNoteAC] [varchar] (3) COLLATE SQL_Latinl_General_CP850_CI_AS NOT NULL ,
[ResidentNotelD] [int] NOT NULL ,
[Residentlntervention] [int] NULL ,
CONSTRAINT [PK_PDACINote] PRIMARY KEY CLUSTERED
( [CINotelD]
) ON [PRIMARY] , CONSTRAINT [FK_PDACINote_Resident] FOREIGN KEY
( [Resident]
) REFERENCES [Resident] ( [Resident]
)/ CONSTRAINT [FK_PDACINote_ResidentIntervention] FOREIGN KEY
(
[Residentlntervention] ) REFERENCES [Residentlntervention] (
[Residentlntervention] )
) ON [PRIMARY] GO
The following is pseudo-code of the software product for creating a care intervention status table. The status codes used for the care intervention process shown in Figure 14 are stored in this table.
CREATE TABLE [CIStatus] (
[CIStatusCode] [varchar] (50) COLLATE SQL_Latinl_General_CP850_CI_AS NOT NULL , [CIStatusDesc] [varchar] (30) COLLATE SQL_Latinl_General_CP850_CI_AS
NULL ,
CONSTRAINT [PK_PDACIStatus] PRIMARY KEY CLUSTERED
(
[CIStatusCode] ) ON [PRIMARY]
) ON [PRIMARY] GO
The following is pseudo-code of the software product for creating a care intervention log file table. Data relating to event logs generated by the software product is stored in this table.
CREATE TABLE [LogFile] (
[LogFilelD] [int] IDENTITY (1, 1) NOT NULL , [LiTiMD] [UIt] NULL ,
[LinkTable] [varchar] (40) COLLATE SQL_Latinl_General_CP850_CI_AS NULL , [StatusCode] [varchar] (4) COLLATE SQL_Latinl_General_CP850_CI_AS NULL ,
[LogText] [varchar] (100) COLLATE SQL_Latinl_General_CP850_CI_AS
NULL 7 [LogDateTime] [datetime] NOT NULL CONSTRAINT
[DF_LogFile_LogDate_55ADD80B] DEFAULT (getdateO), [CreatedBy] [int] NULL , CONSTRAINT [PK_PDACILog] PRIMARY KEY CLUSTERED
( [LogFilelD]
) ON [PRIMARY] , CONSTRAINT [FKJPDACILogJJsers] FOREIGN KEY
(
[CreatedBy] ) REFERENCES [Users] (
[Userld]
)
) ON [PRIMARY] GO
Figure 15 illustrates the relational database generated by the software product, and shows data flow between various tables including those generated by the software product as illustrated above. The relational database includes a care intervention table 182, a care intervention group table 184, a care intervention group facility table 186, a care intervention note table 188, a care intervention status table 190, a log file table 192, a resident intervention table 194, a location table 196, a facility table 198, a users table 200 and a resident table 202.
The software product associates data in the care intervention table 182 with data in the resident intervention table 194, the care invention group table 184, and the care intervention status table 190.
The software product associates data in the care intervention table 182 and the care intervention group facility 186 with data in the care intervention group table 184. The software product associates data in the care intervention group facility table 186 with data in the care intervention group table 184 and the facility table 198.
The software product associates data in the care intervention note table 188 with data in the resident table 202 and the resident intervention table 194.
The software product associates data in the care intervention table 182 with data in the care intervention status table 190.
The software product associates data in the log file table 192 with data in the user table 200.
The software product associates data in the care intervention table 182 and care intervention note table 188 with data in the resident information table 194. The software product also associates data in the resident information table 194 with data in the resident table 202.
The software product associates data in the care intervention group facility table 186 and the facility table 198 with data in the location table 196.
The software product associates data in the care intervention group facility table 186 and the resident table 202 with data in the facility table 198.
The software product associates data in the log file table 192 with data in the user's table 200.
The software product associates data in the resident intervention table 194 and care intervention note table 188 with data in the resident table 202. The software product also associates data in the resident table 202 with data in the facility table 198. Thus, the software product is configured to generate a large number of different reports from the relational database shown in Figure 15.
A possible list of SQL storage procedure commands for the tables are shown below. The software product is configured to generate the reports shown in the second column upon entry of corresponding SQL commands in the first column.
Figure imgf000027_0001
Figure imgf000028_0001
Figure imgf000029_0001
A web interface generated by the software product is described below.
Figure 16 is a block diagram showing the web form (i.e. page) relationships generated by the software product for a PDA (mobile system) logon. A home page 204 is generated which redirects to a log in page 206. System administrators and supervisors are able to access the log in page 206. Normal staff members (i.e. carers) are also able to access the log in page 206 via a PDA 8. Administrators and supervisors are able to access an administrator/supervisor menu page 208. Carers are able to access a main menu page 210. Administrators and supervisors are also able to access the main menu page 210.
Figure 17 shows the web form relationships generated by the software product for logging on as a staff member. A note detail page 212 is generated. A main menu page 214 is generated under the note detail page 212. Navigation is facilitated between the main menu page 214 and a residents page 216, a "to do" list page 218 and an email page 220.
Navigation is facilitated between the residents page 216 and a resident details page 222. Navigation is facilitated between the resident details page 222 and: a data collection sheet page 224, a resident notes page 226, a care plans page 228, a hotkeys page 230 and a quick report page 232. Navigation is facilitated between the data collection sheets page 224 and a clinical data collection sheets page 234. Navigation is facilitated between the resident notes page 226 and: a note details page 236 and a new note page 238. Navigation is facilitated between the note details page 236 and an edit note page 240. Navigation is facilitated between the care plans page 228 and a care plan page 242. Navigation is facilitated between the hotkeys page 230 and a care plan page 244. Navigation is facilitated between the quick report page 232 and: a note details page 246 and a care plan page 248. Navigation is facilitated between the note details page 246 and an edit note page 250.
Navigation is facilitated between the "to do" list page 218 and a care intervention details page 252. Navigation is facilitated between the care intervention details page 252 and: a note details page 254, a new note page 256 and a care plan page 258. Navigation is facilitated between the note details page 254 and an edit note page 260.
Navigation is facilitated between the email page 220 and: a new email page 222 and an email message page 224.
Figure 18 shows the web form relationships generated by the software product for logging on as an administrator. An administrator/supervisor menu page is provided at 326. Navigation is facilitated between the administrator/supervisor menu page 326 and: a care intervention group setup page 328, a care intervention management page 330, a staff log on page 332 and an email page 334. The carer is able to navigate from the staff log on page 332 to a main menu page 336 and, in turn, return to the administrator/supervisor menu 326.
Navigation is facilitated between the care intervention management page 330 and a care intervention details page 338. Navigation is facilitated between the care intervention details page 338 and: an "assign to staff" page 340, a note details page 342, a "new note" page 344, and a care plan page 346. Navigation is facilitated between the note details page 342 and an edit note page 348.
A carer is able to navigate from the email page 334 to: a new email page 348 and an email message page 350.
Figure 19 shows a range of care plan web pages generated by the software product.
Figure 20 shows a range of clinical data collection web pages generated by the software product.
In view of the foregoing, a person skilled in the art will appreciate that the present invention provides a method of administering a healthcare administration system 2. The method includes the steps of maintaining a database in which resident information is stored, establishing a wireless communication protocol between the database and the PDA 8, and generating an interface on the PDA 8 so that the PDA 8 can interface with the database.
The present invention enables resident information to be stored in a single centrally located database. The present invention also enables carers, such as doctors and nurses, to interface with the database when they are not located in close proximity to either the database or the resident.
Some embodiments of the present invention provide a means for enabling a carer to view and modify resident information as he or she wanders around a care-facility in which the resident resides.
Other embodiments provide a means for enabling a carer to view and modify resident information from a remote location. That is, the carer can view and modify resident information via the Internet as he or she wanders around his or her home or the home of the resident or patient. It follows that a particular advantage of this invention is that it greatly facilitates home care. This can substantially cut medical costs, a large proportion of which are associated with lodging of aged care residents.
A person skilled in the art will also appreciate that many embodiments and variations can be made without departing from the ambit of the present invention.
In the first and second embodiments described, a PDA was used for wirelessly communicating with the network 6. Alternatively, other types of wireless communication device could be used such as, for example, a keyboard enhanced PDA.
In compliance with the statute, the invention has been described in language more or less specific to structural or methodical features. It is to be understood that the invention is not limited to specific features shown or described since the means herein described comprises preferred forms of putting the invention into effect.

Claims

1. A healthcare administration system that includes a computer programmed to define a database for storing patient information and connected to a network at a central location; and at least one wireless communication device connected to the network at an end user location, the, or each, wireless communication device being configured to define an interface with the database, via the network.
2. A healthcare administration system as claimed in claim 1 , in which the computer includes a database server for storing and managing the database and a web server for interfacing the database with the network.
3. A healthcare administration system as claimed in claim 2, in which the network is a Wireless Fidelity (WIFI) intranet through which the, or each, wireless communication device interfaces with the web server.
4. A healthcare administration system as claimed in claim 1 , in which the, or each, wireless communication device is a personal digital assistant (PDA).
5. A healthcare administration system as claimed in claim 2, in which the system includes at least one workstation computer at the end user location that interfaces with the web server via one of a local area network (LAN) and the Internet.
6. A healthcare administration system as claimed in claim 1 , in which said interface defined by the wireless communication device is in the form of a virtual private network (VPN).
7. A method of administering a healthcare system, the method including the steps of: inputting data representing patient information into a database; manipulating the patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
8. A method as claimed in claim 7, in which the step of maintaining the database includes the step of generating patient profiles within the database.
9. A method as claimed in claim 8, which includes the step of generating electronic care plans (ECP's) using the patient profile.
10. A method as claimed in claim 9, which includes the step of providing a notes interface so that a carer can enter further patient information into the database to be accessible via the interface.
11. A method as claimed in claim 9, which includes the step of generating care interventions based on the ECP's.
12. A method as claimed in claim 7, which includes the step of generating reports from data stored in the database.
13. A software product for use in a healthcare administration system, the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the method as claimed in any one of claims 7 to 12.
14. A software product for use in a healthcare administration system, the software product being executable on a computer and being configured so that, when executed, the software product is capable of carrying out the following steps: providing a database in which patient information can be stored; manipulating patient information to generate patient profiles; establishing a wireless communication protocol between the database and a wireless communication device; and generating an interface on the wireless communication device so that the wireless communication device can interface with the database.
15. A software product as claimed in claim 14, which is configured to define an application service provider (ASP) to manage web forms to be displayed on the wireless communication device.
16. A software product as claimed in claim 15, in which the ASP is configured to generate web form architecture to permit a carer to log in to the healthcare administration system.
17. A software product as claimed in claim 16, in which the ASP is configured to generate the web form architecture such that the PDA carries out one or more of the following steps: prompts a carer to enter data representing a facility in which a patient resides; generates menu options to facilitate access to patient information and to facilitate the input of data, such as note data to the database.
18. A software product as claimed in claim 16, in which the ASP is configured to generate the web form architecture such that the PDA can carry out one or more of the following steps: provides a log on menu for an administrator; generates menu options to facilitate access to information including care interventions.
19. A software product as claimed in claim 16, in which the ASP is configured to generate the web form architecture to define a care intervention.
20. A software product as claimed in claim 19, in which the ASP is configured to generate the web form architecture such that the PDA can communicate the assignment of the care intervention to a carer.
21. A software product as claimed in claim 20, in which the ASP is configured to generate the web form architecture such that the PDA can prompt a carer to input data indicating whether or not the care intervention is complete.
22. A software product as claimed in claim 14, which is configured to provide a relational database.
23. A software product as claimed in claim 22, which is configured to generate a care intervention table of the relational database such that the care intervention table stores data relating to care interventions generated by the software product.
24. A software product as claimed in claim 23, which is configured to generate a care intervention groups table of the relational database such that the care intervention groups table stores data relating to care interventions associated with particular facilities at which the care interventions are carried out.
25. A software product as claimed in claim 24, which is configured to generate a care intervention group facility table such that the care intervention group facility table stores data relating to all facilities linked to particular intervention groups.
26. A software product as claimed in claim 23, which is configured to generate a care intervention note table, such that the care intervention note table relates notes and corresponding care interventions.
27. A software product as claimed in claim 23, which is configured to generate a care intervention status table, such that the care intervention status table stores status codes used for respective care interventions.
28. A software product for use in a healthcare administration system, the software product being executable on a personal digital assistant (PDA) and being configured so that, when executed, establishes an interface with the software product of any one of claims 13 to 28.
29. A software product as claimed in claim 28, which is configured so that the PDA can generate a graphic user interface (GUI) to permit a carer to interface with the software product of any one of claims 13 to 28.
30. A software product as claimed in claim 28, which is configured so that the PDA can generate a decision tree to permit a carer to input data representing whether or not one or more of the following steps have been carried out by the carer: a particular care intervention has been completed; progress notes are to be input.
31. A software product as claimed in claim 30, which is configured so that the PDA can communicate details relating to said one or more of the steps to the database.
32. A personal digital assistant (PDA) programmed with a software product of any one of claims 28 to 31.
33. A personal digital assistant as claimed in claim 32, which is Internet- enabled.
PCT/AU2006/000433 2005-03-31 2006-03-31 A healthcare administration system WO2006102718A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2006228992A AU2006228992A1 (en) 2005-03-31 2006-03-31 A healthcare administration system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AU2005901564 2005-03-31
AU2005901564A AU2005901564A0 (en) 2005-03-31 A healthcare administration system

Publications (1)

Publication Number Publication Date
WO2006102718A1 true WO2006102718A1 (en) 2006-10-05

Family

ID=37052880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2006/000433 WO2006102718A1 (en) 2005-03-31 2006-03-31 A healthcare administration system

Country Status (1)

Country Link
WO (1) WO2006102718A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8789156B2 (en) 2011-08-19 2014-07-22 International Business Machines Corporation Data management with a networked mobile device

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4835372A (en) * 1985-07-19 1989-05-30 Clincom Incorporated Patient care system
US5845255A (en) * 1994-10-28 1998-12-01 Advanced Health Med-E-Systems Corporation Prescription management system
US5867821A (en) * 1994-05-11 1999-02-02 Paxton Developments Inc. Method and apparatus for electronically accessing and distributing personal health care information and services in hospitals and homes
WO2000014640A1 (en) * 1998-09-03 2000-03-16 Sony Electronics, Inc. Apparatus and method for retrieving information over a computer network utilizing a hand-held portable device
US6151581A (en) * 1996-12-17 2000-11-21 Pulsegroup Inc. System for and method of collecting and populating a database with physician/patient data for processing to improve practice quality and healthcare delivery
US6154726A (en) * 1994-08-24 2000-11-28 Rensimer Enterprises, Ltd System and method for recording patient history data about on-going physician care procedures
US6272470B1 (en) * 1996-09-03 2001-08-07 Kabushiki Kaisha Toshiba Electronic clinical recording system
US6381577B1 (en) * 1997-03-28 2002-04-30 Health Hero Network, Inc. Multi-user remote health monitoring system
WO2002056151A2 (en) * 2001-01-10 2002-07-18 Univ California Method and system for dispensing communication devices to provide access to patient-related information
WO2002069099A2 (en) * 2001-02-26 2002-09-06 Alaris Medical Systems, Inc. System and method for managing patient care
US6463417B1 (en) * 2000-02-22 2002-10-08 Carekey.Com, Inc. Method and system for distributing health information

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4835372A (en) * 1985-07-19 1989-05-30 Clincom Incorporated Patient care system
US5867821A (en) * 1994-05-11 1999-02-02 Paxton Developments Inc. Method and apparatus for electronically accessing and distributing personal health care information and services in hospitals and homes
US6154726A (en) * 1994-08-24 2000-11-28 Rensimer Enterprises, Ltd System and method for recording patient history data about on-going physician care procedures
US5845255A (en) * 1994-10-28 1998-12-01 Advanced Health Med-E-Systems Corporation Prescription management system
US6272470B1 (en) * 1996-09-03 2001-08-07 Kabushiki Kaisha Toshiba Electronic clinical recording system
US6151581A (en) * 1996-12-17 2000-11-21 Pulsegroup Inc. System for and method of collecting and populating a database with physician/patient data for processing to improve practice quality and healthcare delivery
US6381577B1 (en) * 1997-03-28 2002-04-30 Health Hero Network, Inc. Multi-user remote health monitoring system
WO2000014640A1 (en) * 1998-09-03 2000-03-16 Sony Electronics, Inc. Apparatus and method for retrieving information over a computer network utilizing a hand-held portable device
US6463417B1 (en) * 2000-02-22 2002-10-08 Carekey.Com, Inc. Method and system for distributing health information
WO2002056151A2 (en) * 2001-01-10 2002-07-18 Univ California Method and system for dispensing communication devices to provide access to patient-related information
WO2002069099A2 (en) * 2001-02-26 2002-09-06 Alaris Medical Systems, Inc. System and method for managing patient care

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8789156B2 (en) 2011-08-19 2014-07-22 International Business Machines Corporation Data management with a networked mobile device

Similar Documents

Publication Publication Date Title
US20220384046A1 (en) Systems and methods for determining and providing a display of a plurality of wellness scores for patients with regard to a medical condition and/or a medical treatment
Lancaster et al. Individual behavioural counselling for smoking cessation
Flodgren et al. Tools developed and disseminated by guideline producers to promote the uptake of their guidelines
US6450956B1 (en) System and method for treatment and outcome measurement analysis
Bunn et al. Telephone consultation and triage: effects on health care use and patient satisfaction
Weech-Maldonado et al. Nurse staffing patterns and quality of care in nursing homes
Doherty et al. Enhancing person-centred care through the development of a therapeutic relationship
CN102576376A (en) Medical history system
US20110046975A1 (en) Dynamically adjusted rules-based decision support using site-specific mapped values
Kortüm et al. Using electronic health records to build an ophthalmologic data warehouse and visualize patients' data
US20200097910A1 (en) A system for generating a record of community-based patient care
EP2973104A2 (en) Method and apparatus for transmitting healthcare messages to an automatically identified set of patients
Cadogan et al. A perfect storm: care transitions for vulnerable older adults discharged home from the emergency department without a hospital admission
WO2016156975A1 (en) Elder care assessment and interactive case management system
US20070136096A1 (en) Systems and methods for maintaining and accessing medical information
Russell Effects of constraints and consequences on plan complexity in conversations about end-of-life care
Pheerapanyawaranun et al. COVID-19 vaccine hesitancy among health care workers in Thailand: The comparative results of two cross-sectional online surveys before and after vaccine availability
Radbruch et al. Germany: Cancer pain and palliative care—current situation
Stephenson Medical, mental health communities mobilize to cope with terror's psychological aftermath
WO2006102718A1 (en) A healthcare administration system
Procter et al. Scoping the role and education needs of practice nurses in London
US20070260478A1 (en) Delivery of Health Insurance Plan Options
AU2006228992A1 (en) A healthcare administration system
McCormick et al. New Zealand community pharmacist attitudes toward opioid-dependent clients
CN111627545A (en) Management method, system and equipment for medical examination and inspection rules

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2006228992

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2006228992

Country of ref document: AU

Date of ref document: 20060330

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 2006228992

Country of ref document: AU

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

NENP Non-entry into the national phase

Ref country code: RU

WWW Wipo information: withdrawn in national office

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06721315

Country of ref document: EP

Kind code of ref document: A1

WWW Wipo information: withdrawn in national office

Ref document number: 6721315

Country of ref document: EP