Patent Application
20140379357
This invention generally relates to hospital staff assignment and nurse call systems, and more particularly to staff assignment and sharing of staff assignments between a nurse call system and devices that interface with the nurse call system.
A typical hospital includes many care units, such as an Intensive Care Unit (ICU), a Cardiology Unit, an Emergency Care Unit, a General Surgery Unit, an Oncology Unit, a Pediatrics Unit, and a Pharmacy Unit, among others. Further, each of these units requires associated staff members and equipment to provide care for patients of the hospital.
Hospitals generally use a nurse call system to alert staff of varying needs of support in the hospital. Typically, a nurse call system is implemented over a hospital's internal network and utilized to update staff as to needed support within the care units of the hospital. The needed support is generally handled by a staff member assigned to a specific location or level of support within a hospital/hospital care unit. A staff member assignment is typically done at the beginning of that staff member's shift and modified accordingly based on staffing needs and breaks.
In certain types of nurse call systems, the staff assignments are made at a central location that handles specific staff members starting/stopping their shifts and taking breaks. The central location can also be used for staff assignments to specific units within the hospital. Because staffing assignments are generally handled at a centralized location, a bottleneck occurs at certain points during the day when large numbers of staff come on and off duty. Further, the updated staff assignment is not shared within the hospital's internal network with all of the various care units and the specialized equipment within that care unit. Other arrangements of nurse call systems exist, such as those where staff assignments are made at nurses' stations within the various units in the hospital. Some hospitals may use a combination of central and nurse's station staffing assignments.
Accordingly, errors will be made in the staff assignments in that not every care unit will have the same information regarding staff assignments. Also, system use may decline among the staff because of the bottleneck created during shift changes within the hospital and the hassle associated with updating a staff assignment at each of the care units that a particular staff member may be assigned throughout the course of a work shift.
In view of the above, there is a need for a system that will update staff assignments efficiently and across all care units of a hospital and also between numerous disparate and diverse systems. Embodiments of the invention provide such a solution for hospital staff assignment and nurse call systems. These and other advantages of the invention, as well as additional inventive features, will be apparent from the description of the invention provided herein.
One embodiment provides an assignment system for coordinating staff members of a hospital. The assignment system includes a plurality of interface devices, a communication network, an application server, and a nurse call system. The communication network is coupled to each of the plurality of interface devices, and the plurality of interface devices capable of receiving input data and sending output data over the communication network. The application server is coupled to the communication network and configured to communicate with each of the plurality of interface devices. The nurse call system is coupled to the application server and configured to track and update one or more client devices based on data received from the application server.
Another embodiment includes a method of coordinating staff assignments in a hospital nurse call system. The hospital nurse call system interfaces with an application server that communicates with an at least one publishing device over a communication network. The method includes receiving, by an assignment interface of the application server, a staff assignment from the at least one publishing device. The method further includes parsing, by the assignment interface, the staff assignment to obtain assignment information, and storing the assignment information of the staff assignment in a call system database associated with the nurse call system. Further the method includes detecting, by the nurse call system, the stored assignment information, and notifying, by the nurse call system, a client device of the nurse call system of the staff assignment.
Yet another embodiment includes a method of coordinating staff assignments in a hospital nurse call system. The hospital nurse call system interfaces with an application server that communicates with an at least one subscribing device over a communication network. The method includes relaying, by the nurse call system, a staff assignment from a client device of the nurse call system to an assignment interface of the application server. The method further includes parsing, by the assignment interface, the staff assignment to obtain assignment information, and storing the assignment information of the staff assignment in a call system database associated with the nurse call system. Further, the method includes sending, by an assignment messenger of the assignment interface, the assignment information of the staff assignment to the at least one subscribing device.
Another embodiment includes an application server for coordinating staff members of a hospital with a nurse call system. The application server coordinates hospital staff assignments between an at least one publishing device and the nurse call system. The at least one publishing device and the application server are communicatively coupled over a hospital communication network. The application server includes an at least one processor and a computer readable memory device associated with the at least one processor. The computer readable memory device has computer executable instructions for performing the steps of receiving, by an assignment interface of the application server, a staff assignment from the at least one publishing device; parsing, by the assignment interface, the staff assignment to obtain assignment information; storing the assignment information of the staff assignment in a call system database associated with the nurse call system; and notifying the nurse call system of the stored assignment information.
The accompanying drawings incorporated in and forming a part of the specification illustrate several aspects of the present invention and, together with the description, serve to explain the principles of the invention. In the drawings:
While the invention will be described in connection with certain preferred embodiments, there is no intent to limit it to those embodiments. On the contrary, the intent is to cover all alternatives, modifications and equivalents as included within the spirit and scope of the invention as defined by the appended claims.
A typical hospital environment contains many care units supported by staff members employed by the hospital. Specific staff members are assigned to support the individual care units within the hospital. Even further, certain staff members will be assigned to certain area of the care unit and even assigned to particular equipment within the care unit or hospital at large.
In this manner, a staff member providing care or servicing some other need of the hospital is able to be informed in an expedient manner because that individual was pre-assigned that specific duty prior to the service needs arising. For instance, as an example, a specific staff member may be assigned to certain beds within a hospital's patient rooms. Accordingly, when a patient indicates a need for care or patient monitoring equipment indicates a need for care, the staff member assigned to that specific bed will be alerted of that need over a hospital's nurse call system.
Generally, a hospital's nurse call system is operated over the hospital's internal network. In certain situations, the network ties together the various hospital care units and the individual equipment within that care unit. Also, in order to maintain an accurate staff assignment system, assignment information must be maintained within each of the care units in general and within the associated equipment within that care unit. To accomplish this, certain staff members may need to enter a particular staff assignment in a multitude of locations, which can be burdensome on the hospital staff in general and lead to errors within the system.
Accordingly, there is a need for a centralized system that updates staff assignments made at a single point within the network of the hospital throughout the various care units that exist within a hospital.
In certain embodiments, the nurse call application server 102 connects to a plurality of interface devices 108 over a Local Area Network (LAN) or a Wide Area Network (WAN) 110 via Transmission Control Protocol of the Internet Protocol Suite (TCP/IP). The interface devices 108 are distributed throughout a hospital's various individual care units and among the hospital staff.
Further, in certain embodiments, the nurse call application server 102 includes a plurality of interconnected servers or a plurality of services running on an individual server. In either embodiment, the nurse call application server 102 includes an assignment application 112 and a nurse-call application 114. The assignment application 112 includes the functionality of assignment sharing between the interface devices 108 and the nurse call system 104. The nurse-call application includes functionality to interoperate the nurse call system 104 with the assignment application 112. The assignment application 112 and the nurse-call application 114 may each operate as a service running on a single server or on separate servers.
Therefore, the nurse call application server 102 bridges a communication gap between the individual interface devices 108 and the nurse call system 104. This communication is facilitated over an extensible markup language (XML) interface hosted by the nurse call application server 102 that exchanges assignment information for staff assignments and device assignments such as on/off duty or on/off break for staff assignments or wireless handset, pager, or real time location badge assignments for device assignments. Accordingly, staff and device assignments can be shared among all of the necessary interface devices 108 via the nurse call application server 102. Further, for ease of description, when the term staff assignment is used herein it is meant to include both staff assignments and device assignments.
Additionally, interface devices 108 may include cellular phones, pagers, RFID badges, or any device that is capable of being associated with an individual staff member in both name and location. In certain embodiments, an individual staff member is assigned an interface device 108, which receives calls for care for the individual staff member from the nurse call system 104. Accordingly, the interface device 108 receives updates from the nurse call system 104 that provide notice to the assigned staff member that their services are needed. For instance, the wireless staff phone system interface device 108 supports wireless phones carried by the staff. Therefore, assignment information for staff assignments related to a staff members wireless phone may be updated through the wireless staff phone system interface device 108, which updates the nurse call system 104 with the staff assignment related to the particular mobile device carried by the staff member.
Because staff assignments can be shared among the various interface devices 108, hospital staff will be able to focus on their hospital duties as opposed to constantly updating new systems as they progress through their shift. For example, by sharing information among all interface devices 108, a staff member will not have to enter their name and contact information into each interface device 108, as they access that device. Also, staff will not have to update a real time location system with their badge in order to update their location and level of care to be provided in that location. An EMR system will know what staff members are associated with a particular patient's medical charts. A patient will be able to identify the staff member assigned to provide care through an Interactive Television. Also, medical devices will have the latest staff assignments stored such that the device can quickly and efficiently inform relevant staff members of various diagnostic data and alarms.
The interface device 108 also includes a staff assignment User Interface (UI) 200. UI 200 is a network application hosted on the nurse call application server 102 (see
As illustrated, processor 202 is configured to implement functionality and/or process instructions for execution within the interface device 108. For example, processor 202 executes instructions stored in memory 204 or instructions store on a storage device 208. Memory 204, which may be a non-transient, computer-readable storage medium, is configured to store information within the interface device 108 during operation. In some embodiments, memory 204 includes a temporary memory, an area for information not to be maintained when the interface device 108 is turned off. Examples of such temporary memory include volatile memories such as random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Memory 204 also maintains program instructions for execution by the processor 202.
Storage device 208 also includes one or more non-transient computer-readable storage media. The Storage device 208 is generally configured to store larger amounts of information than memory 204. The Storage device 208 may further be configured for long-term storage of information. In some examples, the Storage device 208 includes non-volatile storage elements. Non-limiting examples of non-volatile storage elements include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
The interface device 108 uses network interface 206 to communicate with external devices via one or more networks, such as the network 110 of
The interface device 108 includes one or more input devices 212. Input devices 212 are configured to receive input from a user or a surrounding environment of the user through tactile, audio, and/or video feedback. Non-limiting examples of input device 212 include a presence-sensitive screen, a mouse, a keyboard, a voice responsive system, video camera, microphone, optical sensor or any other type of input device. In some examples, a presence-sensitive screen includes a touch-sensitive screen.
One or more output devices 214 are also included in interface device 108. Output devices 214 are configured to provide output to a user using tactile, audio, and/or video stimuli. Output device 214 may include a display screen (part of the presence-sensitive screen), a sound card, a video graphics adapter card, or any other type of device for converting a signal into an appropriate form understandable to humans or machines. Additional examples of output device 214 include a speaker, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD), or any other type of device that can generate intelligible output to a user.
The interface device 108 includes one or more power sources 210 to provide power to the device. Non-limiting examples of power source 210 include regulated power from a power network, single-use power sources, rechargeable power sources, and/or power sources developed from nickel-cadmium, lithium-ion, or other suitable material.
As illustrated, processor(s) 302 are configured to implement functionality and/or process instructions for execution within server 102. For example, processors 302 execute instructions stored in memory 304 or instructions stored on storage devices 308. Memory 304, which may be a non-transient, computer-readable storage medium, is configured to store information within server 102 during operation. In some embodiments, memory 304 includes a temporary memory, i.e. an area for information not to be maintained when the server 102 is turned off. Examples of such temporary memory include volatile memories such as random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Memory 304 also maintains program instructions for execution by the processors 302.
Storage devices 308 also include one or more non-transient computer-readable storage media. Storage devices 308 are generally configured to store larger amounts of information than memory 304. Storage devices 308 may further be configured for long-term storage of information. In some examples, storage devices 308 include non-volatile storage elements. Non-limiting examples of non-volatile storage elements include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
The server 102 uses network interface 306 to communicate with external devices via one or more networks, such as the network 110 of
As previously mentioned above regarding
The staff assignment engine 310 includes program instructions and/or data that are executable by the server 102. The program instructions and data included in the staff assignment engine 310 include instructions to receive and transmit assignment information to and from the interface devices 108 and nurse call system 104.
The assignment interface 402 includes sub-blocks such as a staff assignment client service 404, an assignment messenger 406, and an assignment synchronizer 408. The assignment interface 402 exchanges messages with the interface devices 108 and is implemented as a network service and hosts a staff assignment client service 404 inside. The assignment interface 402 further includes an assignment messenger to push staff assignments to interface devices 108 that are subscribed to the assignment server 102. The assignment interface 402 also includes an assignment synchronizer 408, which synchronizes staff assignments with interface devices 108 that are configured to publish staff assignments to the nurse call application server 102.
Accordingly, the interface devices 108 are shown with two representative devices; one device set up as a publishing device 416 and another device set up as a subscribing device 418. As stated previously, interface devices 108 can comprise a multitude of device types used in a hospital environment. Each type of these devices has a different functionality and can be set up within the hospital's internal network 100 (see
The previously mentioned assignment interface 402 acts to relay staff assignments to endpoint systems such as interface devices 108 including publishing devices 416 and subscriber devices 418. In the embodiment of the disclosure illustrated in
Further, the assignment messenger 406 of the assignment interface 402 pushes the staff assignments to subscribing device(s) 418. When a new staff assignment is recognized in the system, the assignment messenger interfaces with database 412 to determine a list of subscribing device(s) 418 that should receive the staff assignment. The updated staff assignment will be relayed via the API on the client service 404.
Another functional block of the assignment interface 402 is the assignment synchronizer 408, which synchronizes staff assignments from the nurse call system 104 with staff assignments from all publishing device(s) 416. The assignment synchronizer 408 runs whenever the staff assignment engine 310 starts and runs again periodically thereafter. The frequency of synchronization is typically every five minutes, but could be any time that system operators desired. Ideally, the frequency would be no less than one synchronization every ten minutes and no more than one synchronization every one minute.
During synchronization, the assignment synchronizer 408 obtains a list of publishing device(s) 418 from database 412 and proceeds to query each publishing device 418 for staff assignments from that specific publishing device 418. The assignment synchronizer 408 then obtains a list of staff assignments from that specific publishing device 418, as stored in database 414 associated with the nurse call system 104 and compares the former list with the later list. Based on the comparison, the assignment synchronizer 408 will update the staff assignments stored in database 414 with the latest staff assignments from publishing device(s) 418.
The synchronization process performed by the assignment synchronizer 408 is typically enabled upon system initialization or reinitialization. This is done to ensure an accurate list of staff assignments, and therefore, acts primarily as a back up to the various updates created via the staff assignments from the staff assignment engine 310.
Furthermore, UI 200, which was discussed above while referencing
Another function of the mapping engine 410 is to allow a user via the UI 200 to compare and synchronize patient bed mappings between database 412 and database 414. Accordingly, an accurate bed mapping is maintained between the nurse call system 104 and the staff assignment engine 310.
Another function of the mapping engine 408 is team mapping. This allows the user to synchronize unit teams such as an ICU unit or oncology unit, to name a few, between database 412 and database 414.
Another function of the mapping engine 408 is staff mapping and interface device mapping. This allows the user to synchronize staff lists and interface device lists between database 412 and database 414.
As an aside, while the above mapping is described as being between database 412 and database 414, database 412 actually acts more as a translator between the publishing device 416 and database 414. Specifically, synchronization is really achieved between various storage devices 208 (see
This translation is necessary because the various interface devices 108 may each have a different way of describing the staff, device, location, and level associated with that device, while the nurse call system 104 has only a single way of describing each staff, device, location, and level. Accordingly, a translation is needed for the nurse call system 104 to properly interpret the staff assignment data. This translation is stored as a user defined mapping in the staff assignment engine database 412.
Turning now to
A list of staff assignments defined in the API associated with
Regarding the Set Staff to Device Assignment Change, this staff assignment assigns or unassigns a device such as interface device 108 (see
Regarding the Set Staff to Location Assignment Change, this staff assignment assigns to a staff member a location such as a hospital department like the ICU or a bed in a particular hospital department. This staff assignment further specifies a specific care level such as primary care provider or secondary care provider for the staff member. Accordingly, required assignment information to be included in this staff assignment is a staff member and a location. Optionally, the staff assignment can specify a level of care. Also optionally, this staff assignment can specify a response team such as a nursing care team or an environmental team associated with that particular location. Further optional assignment information is a particular patient in need of care, a start time for this staff assignment, and a stop time for this assignment.
Further, because the assignment information for this staff assignment may also optionally specify a start and end time for the assignment, a pre-assignment can be made by specifying the time at which this assignment is made. Therefore, this staff assignment can be entered prior to the staff member starting their shift for the day, and the staff assignment will be implemented once the associated staff member comes on duty.
Regarding the Set Device to Location Assignment Change, this staff assignment assigns a device to a location such as a hospital department like the ICU or a bed in a particular hospital department. This staff assignment further specifies a specific care level such as primary care or secondary care for the device. Accordingly, required assignment information to be included in this staff assignment is a device, a location, and a level of care. Optionally, this staff assignment can specify a particular patient in need of care, a start time for this staff assignment, and a stop time for this assignment.
Further, the assignment information for this staff assignment may also optionally specify a start and end time for the assignment. However, as opposed to the counterpart staff assignment related to assigning a staff member location, this staff assignment does not utilize pre-assignments because devices are always online. Accordingly, this staff assignment will be shared immediately, as opposed to when a staff member comes on duty.
Regarding the Set Staff On Duty Status, this staff assignment sets a staff member either on or off duty, and can be optionally extended to setting a team of staff members on or off duty. Furthermore, as previously discussed pre-assignments may be made for certain staff members, and these assignments should only be shared once that particular staff member is on duty. Therefore, once this staff assignment is made, any stored pre-assignments will be shared.
Additionally, an off duty assignment will automatically trigger sharing of unassign events for any staff to device, staff to location, and device to location mappings that were active for the particular staff member.
The Set Staff On Duty Status staff assignment includes certain required assignment information to be provided prior to sharing the staff assignment. The required assignment information is a status such as on or off duty and an associated staff member. Optional assignment information is team information such as a whole staff team coming on or off duty.
Regarding the Set Staff On Break Status, this staff assignment sets a staff member either on or off break, and can be optionally extended to specifying a covering staff member while the primary staff member is on break. Because being on break in temporary, staff assignments related to the break are shared.
The Set Staff On Break Status staff assignment includes certain required assignment information to be provided prior to sharing. The required assignment information is a status such as on or off break, and an associated staff member. Optional assignment information is a staff member that will cover for the staff member on break.
Regarding the Set Device On Duty Status, this staff assignment sets a device on or off duty, and optionally for a team. Also, only staff assignments associated with an on duty device will be shared. Accordingly, setting a device on duty initiates sharing of any pre-assignments. Further, an off duty message from this staff assignment triggers sharing of unassign events for any device to location assignments that were active for this particular device.
The Set Device On Duty Status staff assignment includes certain required assignment information to be provided prior to sharing. The required assignment information is an event action such as on or off duty and a particular device associated coming on or off duty. Optional assignment information includes a team associated with the device coming on or off duty.
Regarding the Set Device On Break Status, this staff assignment sets a device on or off break, and optionally provides for a covering device while the primary device in on break. In the situation where a covering device is specified, once the primary device comes back on duty from a break the covering device is automatically removed. This staff assignment associated with a device on break will be shared, as break status is only temporary and the device is still on duty.
The Set Device On Break Status staff assignment includes certain required assignment information to be provided prior to sharing. The required assignment information is a status such as on or off break and a specific device associated that is going on or off break. Optionally, assignment information pertaining to a covering device may be specified.
A list of staff assignments or, by another name, system requests defined in the API associated with
The staff assignment requests defined in the API related to
The Get All Owned Staff to Device Assignments staff assignment request will provide a list of all staff members assigned to interface device 108 (see
The Get All Owned Staff to Location Assignments staff assignment request will provide a list of all staff members assigned to hospital location. The assignment synchronizer utilizes this staff assignment request to synchronize staff assignments published by a publishing device 416 with a list of staff assignments stored at the call system database 414. This ensures that an accurate list of published location to staff member assignments is maintained between publishing device 416 and the call system database 414. The subscribing device 418 utilizes this staff assignment request to ensure that its list of assignments in its storage device 208 (see
The Get All Owned Staff to Location Assignments staff assignment request will provide a list of all staff members assigned to a hospital location. The assignment synchronizer utilizes this staff assignment request to synchronize staff assignments published by a publishing device 416 with a list of staff assignments stored at the call system database 414. This ensures that an accurate list of published location to staff member assignments is maintained between publishing device 416 and the call system database 414. The subscribing device 418 utilizes this staff assignment request to ensure that its list of assignments in its storage device 208 (see
The Get All Owned Device to Location Assignments staff assignment request will provide a list of all hospital locations assigned to a device. The assignment synchronizer utilizes this staff assignment request to synchronize staff assignments published by a publishing device 416 with a list of staff assignments stored at the call system database 414. This ensures that an accurate list of published device to location assignments is maintained between publishing device 416 and the call system database 414. The subscribing device 418 utilizes this staff assignment request to ensure that its list of assignments in its storage device 208 (see
The Get All Owned Staff On Duty staff assignment request will provide a list of all on duty staff members assigned to a particular interface device 108 (see
The Get All Owned Staff On Break staff assignment request will provide a list of all on break staff members assigned to a particular interface device 108 (see
The Get All Owned Devices On Duty staff assignment request will provide a list of all interface devices 108 (see
The Get All Owned Devices On Break staff assignment request will provide a list of all interface devices 108 (see
All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.
The use of the terms “a” and “an” and “the” and “at least one” and similar referents in the context of describing the invention (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The use of the term “at least one” followed by a list of one or more items (for example, “at least one of A and B”) is to be construed to mean one item selected from the listed items (A or B) or any combination of two or more of the listed items (A and B), unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the invention.
Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for the invention to be practiced otherwise than as specifically described herein. Accordingly, this invention includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the invention unless otherwise indicated herein or otherwise clearly contradicted by context.
