Access to multi-healthcare professional information systems

Abstract

The present disclosure describes an electronic device for managing notifications for medical personnel associated with a plurality of medical institutions. The electronic device is connected to an active site associated with a first medical institution, connected to a passive site associated with a second medical institution, receives notifications from the active site and the passive site, and upon receiving an input from the medical personnel, switches the passive site to active to access notifications from the passive site.

Description

Background Technology

[0001] Healthcare workers, such as doctors, nurses, and other medical professionals, are typically assigned to multiple patients when on duty in healthcare facilities like hospitals. They communicate various prompts or calls from patients and other healthcare personnel, who must prioritize and manage these incoming prompts. Other staff, such as those in administrative, catering, and patient transport roles, must also respond to these prompts and calls.

[0002] Sometimes, healthcare staff and employees have wireless communication devices, such as pagers or mobile phones, to receive incoming calls and alerts related to the care of one or more patients. At the end of their shift, healthcare staff and employees must return these devices for charging or for use by other healthcare staff and employees on their next shift. More recently, to coordinate patient care, healthcare staff and employees often carry their own mobile phones to work so they can communicate with each other while on duty. Summary of the Invention

[0003] Generally, this disclosure relates to mobile applications that allow healthcare professionals to access notifications and other resources from multiple healthcare institutions. Various aspects of the invention are described, including but not limited to the following.

[0004] On one hand, an electronic device for managing notifications to healthcare workers associated with multiple healthcare facilities includes: a processor; and a memory that encodes instructions that, when executed by the processor, cause the processor to: connect to an active site associated with a first healthcare facility; connect to a passive site associated with a second healthcare facility; receive notifications from the active and passive sites; and, upon receiving input from a healthcare worker, switch the passive site to an active site to access the passive site.

[0005] On the other hand, a method for managing notifications to healthcare workers associated with multiple healthcare facilities includes: connecting to an active site associated with a first healthcare facility; connecting to a passive site associated with a second healthcare facility; receiving notifications from the active and passive sites; and, upon receiving input from a healthcare worker, switching the passive site to an active site to access the passive site.

[0006] On the other hand, a non-transitory computer-readable storage medium includes computer-readable instructions that, when read and executed by a computing device, cause the computing device to: connect to an active site associated with a first medical institution; connect to a passive site associated with a second medical institution; receive notifications from the active and passive sites; and, upon receiving input from a healthcare professional, switch the passive site to an active site to access the passive site. Attached Figure Description

[0007] The following figures form part of this application and illustrate the techniques described herein, but are not intended to limit the scope of the invention in any way.

[0008] Figure 1 This is a schematic diagram of a healthcare worker communication system that includes multiple mobile phones, each equipped with a healthcare worker mobile application for managing notifications between healthcare workers in a healthcare facility.

[0009] Figure 2 The illustration shows a mobile application for healthcare workers that connects to a healthcare worker communication system across multiple healthcare facilities.

[0010] Figure 3 Schematic illustration Figure 2 A mobile application for medical staff.

[0011] Figure 4 Showing Figure 3 The user interface of the mobile application for TCM nurses allows access to various resources associated with the healthcare institution.

[0012] Figure 5 Showing Figure 3 Another user interface for the mobile application for medical staff provides settings for the mobile application.

[0013] Figure 6 Showing Figure 3 Another user interface for the mobile application for healthcare workers provides a list of active sites, passive sites, and dormant sites configured within the mobile application.

[0014] Figure 7 Showing Figure 6 The user interface has controls for setting the status of healthcare workers on the communication system of one of the medical institutions.

[0015] Figure 8 Showing Figure 3 Another user interface for the mobile application for healthcare workers allows input from another healthcare institution that has configured the mobile application for healthcare workers.

[0016] Figure 9 Another user interface was shown, including a notification from one of the healthcare facilities that has a mobile app configured for healthcare workers.

[0017] Figure 10 Showing Figure 9 The user interface has a warning control for switching to another healthcare facility associated with a notification on the healthcare worker's mobile app. Detailed Implementation

[0018] Figure 1This is a schematic diagram of a healthcare worker communication system 50, which includes several mobile devices 52 running a healthcare worker mobile application 300 (such as...). Figure 3 (As shown) to manage messages between healthcare professionals, as well as calls and prompts from assigned patients and various hospital instruments associated with assigned patients within the healthcare facility.

[0019] The healthcare worker communication system 50 is similar to the system described in U.S. Patent Application 16 / 143,971, filed September 27, 2018, entitled “CAREGIVER AND STAFFINFORMATION SYSTEM,” which is incorporated herein by reference in its entirety.

[0020] The healthcare worker communication system 50 and the healthcare worker mobile application 300 allow healthcare workers to perform functions associated with providing care to patients. This may include logging into the healthcare worker communication system 50 associated with the healthcare facility and reviewing / selecting shifts. It may also include viewing healthcare worker profiles with relevant status (as described below), assignments, etc. It may further include providing a directory of other healthcare workers associated with the healthcare facility, and selecting the best person for a specific clinic / team and / or healthcare worker. Further, as described below, this may include assigning healthcare workers to specific patients, locating other healthcare workers within the healthcare facility, and / or communicating with healthcare workers.

[0021] The healthcare worker mobile application 300 allows healthcare workers and staff to communicate with each other via voice, video, and text using their own mobile devices 52, monitor prompts and calls from assigned patients, and permits voice communication with audio stations 62, 64 installed in wards adjacent to each bed 54. In some examples, the mobile device 52 is a smartphone, tablet, or similar device. The healthcare worker mobile application 300 can serve as a secondary notification system supplementing the nurse call server 86 (described in detail below) of the healthcare worker communication system 50.

[0022] Calls and alerts from assigned patients and various hospital instruments may originate from the bed 54, patient tablet 56, call switch 58, and pillowside speaker unit 60. Alerts may also originate from a smoke alarm 61. In some examples, audio stations 62, 64 may include an emergency call handle 63, which can be pulled by medical personnel in an emergency, such as when a patient suffers a sudden heart attack. Figure 1 In the example, the pillow-side speaker unit 60 of the hospital bed 54 is coupled to audio stations 62, 64 via an audio station bed connector (ASBC) 66. Alternatively, one or more network interface units (NIUs) or wireless interface units (WIUs) may replace the ASBC 66 to provide connectivity between the hospital bed 54 and the respective audio stations 62, 64.

[0023] Call switch 58, smoke alarm 61, and audio stations 62, 64 are all communicatively coupled to their respective input / output (I / O) circuit boards 68. Each circuit board 68 includes a processor, such as a microprocessor or microcontroller, that receives various prompts and calls from bed 54, pillow speaker 60, smoke alarm 61, and audio stations 62, 64, which are sometimes referred to herein as “prompt messages.” The processor on each circuit board 68 determines a prompt message priority name for each incoming prompt message. For example, prompt messages may be named Normal prompt messages or High Priority prompt messages. Additional types of message priority names may also be used.

[0024] Each circuit board 68 is coupled to a corresponding overhead light 70, which may include multiple lights indicating the status of a room. Based on the alerting situation occurring in the corresponding ward and based on the presence of medical staff in the corresponding ward, the circuit board 68 controls the illumination of the overhead light 70. The overhead light 70 is installed outside each ward, typically near the doorway of the corresponding room. In some examples, the circuit board 68 is housed within a housing in which the overhead light 70 is mounted. Thus, the circuit board 68 may be located outside the ward adjacent to the overhead light 70. Alternatively, the circuit board 68 may be located inside the ward. In either case, according to this disclosure, the circuit board 68 is considered to be "located" in the ward.

[0025] The positioning badge 72 is shown to wirelessly communicate with a remote locator receiver (RLR) 74, which in turn is communicatively coupled to a circuit board 68 in the ward where the RLR 74 is located. The healthcare worker communication system 50 may include multiple positioning badges 72 worn by individual healthcare workers and multiple RLRs throughout the healthcare facility. In response to the RLR 74 detecting one or more positioning badges 72 in any given room, a signal or message is communicated to the corresponding circuit board 68, and the illumination status of the overhead light 70 is updated accordingly to indicate the presence of healthcare worker in the ward. In some examples, the positioning badge 72 transmits infrared (IR) signals to the RLR 74. Alternative examples may also exist where the positioning badge 72 communicates with the RLR 74 in the ward via radio frequency (RF) transmission, including ultra-wideband (UWB) transmission.

[0026] Still refer to Figure 1 Each circuit board 68 is communicatively coupled to a Power over Ethernet (PoE) switch 76, which in turn is communicatively coupled to a primary staff control console 78 (sometimes referred to as the "main nurse station"), a secondary staff control console 80, and staff terminals 82. The PoE switch 76 is communicatively coupled to a Voice over Internet Protocol (VoIP) switch and an enterprise server 84, which in turn... Figure 1The diagram shows the Ethernet infrastructure of network 90 coupled to nurse call server 86. Similarly, mobile device 52 is communicatively coupled to VoIP switch and enterprise server 84, which can access electronic medical record (EMR) server 94, admission / discharge / transfer (ADT) server 96 and auxiliary server 98 via network 90 from mobile device 52.

[0027] The call switch 58, pillow speaker unit 60, audio stations 62, 64, ASBC 66, circuit board 68, overhead light 70, PoE switch 76, primary staff console 78, secondary staff console 80, staff terminal 82, VoIP switch and enterprise server 84, and nurse call server 86 illustrate a schematic nurse call system portion of the healthcare staff communication system 50, and show how the nurse call system architecture will change from one healthcare facility to the next.

[0028] The system may also include a patient tablet computer 56 as part of the nurse call system portion of the healthcare worker communication system 50. The patient tablet computer 56 can be used by the patient to send requests such as requests for pain medication, toilet assistance, food, water, camphor, personal care assistance, etc. In the illustrative example, the patient tablet computer 56 wirelessly communicates with a wireless access point (WAP) 88, which in turn communicates with a patient tablet computer communication server 92. The patient tablet computer communication server 92 communicates patient requests to the nurse call server 86 via network 90; these patient requests are also considered as prompt messages.

[0029] The notification messages originating from bed 54 may include notification messages regarding the following: the patient leaves bed 54; the patient's position on bed 54 exceeds a threshold; the patient's movement on bed 54 exceeds or falls below a threshold; the side rail position of bed 54 (e.g., the side rail is lowered); the casters of bed 54 are not braked; the head section angle of bed 54 is less than a threshold angle (e.g., 30 degrees); the upper frame of bed 54 is not in the lowest position relative to the base frame of bed 54; the bed components of bed 54 exceed a threshold temperature; the mattress airbags of bed 54 are below a threshold air pressure; the pneumatic system of bed 54 malfunctions or fails; the actuators of bed 54 malfunction or fail; an overcurrent condition occurs in a component of bed 54; the power supply system of bed 54 malfunctions or fails; and bed 54 loses power.

[0030] Still refer to Figure 1The healthcare staff communication system 50 includes an electronic medical record (EMR) server 94 and an admission / discharge / transfer (ADT) server 96. The healthcare staff communication system 50 may also include an auxiliary server 98. The nurse call server 86, EMR server 94, ADT server 96, and auxiliary server 98 can be accessed from mobile device 52 via a VoIP switch, enterprise server 84, and network 90.

[0031] In some examples, the additional server 98 may include, for example, a real-time location system (RTLS) communicatively coupled to the RLR 74. In these examples, the location badge 72, the RLR 74, and the RTLS server form the real-time location system portion of the healthcare worker communication system 50. Employee location information can be communicated from the RTLS server to the nurse call server 86 via network 90.

[0032] In some examples, the auxiliary server 98 may include a server that manages the routing of notification messages and related personnel information to the mobile device 52. Generally, notification messages related to a specific patient or room assigned to a specific healthcare worker are sent to that healthcare worker's mobile device 52. Notification messages may originate from the bed 54, pillow speaker 60, and patient tablet 56. Additionally, notification messages originating from other types of instruments may also communicate to the assigned healthcare worker's mobile device 52.

[0033] The features and functionality of the healthcare worker mobile application 300 are described in more detail below, with various screenshots shown that can appear on the mobile device 52. By referring to the functionality represented in each screenshot and considering the description below, those skilled in the art will be able to conceive of and utilize the healthcare worker mobile application and its variant embodiments envisioned herein. It should be noted that the screenshots of this disclosure are exemplary in nature, providing a general understanding of the types of information that may appear on the display of any given mobile device 52 when healthcare workers and staff use the healthcare worker mobile application. Therefore, the screenshots are merely individual examples among a virtually infinite number of possibilities. That is, information such as notification messages, employee names, employee locations, room name formats, ward names, etc., may vary between different healthcare institutions, and in fact, may also vary, for example, in response to various incoming notification messages in any given healthcare institution on any given day.

[0034] Figure 2One of the mobile devices 52 used by healthcare workers and staff is shown. In this example, the mobile device 52 is connected via network 90 to a healthcare worker communication system 50, such as a hospital, outpatient clinic, or other healthcare facility, which serves as a first healthcare worker site associated with the healthcare worker or staff. The mobile device 52 is also connected via network 90 to one or more additional sites associated with the healthcare worker or staff, such as healthcare worker communication systems 250, 252. Healthcare worker communication systems 250, 252 are associated with other healthcare facilities, such as other hospitals and outpatient clinics, and can be configured similarly to healthcare worker communication system 50.

[0035] For example, in this example, when a healthcare worker connects to a first healthcare facility associated with a healthcare worker communication system 50, the healthcare worker can communicate via the healthcare worker communication system 50 using their own mobile device 52. As the mobile device 52 connects to the healthcare worker communication system 50, the healthcare worker can receive communications related to the care of a patient in the first healthcare facility as described above (e.g., notifications related to prompts, messages, and / or other options). Additional details regarding the types of notifications that can be sent are provided in U.S. Patent Application 63 / 109464, filed November 4, 2020, entitled “Healthcare Worker Messaging Management,” which is incorporated herein by reference in its entirety.

[0036] Continuing the example, suppose healthcare professionals also provide care to patients located in other healthcare facilities. If these other healthcare facilities are independent of or otherwise not electrically connected to the first healthcare facility associated with healthcare professional communication system 50, the communications associated with these other healthcare facilities are set up on completely separate systems, such as healthcare professional communication systems 250 and 252. This means that when mobile device 52 is connected to healthcare professional communication system 50, healthcare professionals will not receive notifications from healthcare professional communication systems 250 and 252. Furthermore, other healthcare professionals and staff connected to healthcare professional communication systems 250 and 252 cannot communicate with them or obtain information about the status of healthcare professionals disconnected from healthcare professional communication systems 250 and 252.

[0037] As described below, the healthcare worker mobile application 300 on mobile device 52 allows healthcare workers to simultaneously log in to multiple healthcare facility communication systems, such as healthcare worker communication systems 50, 250, and 252. In this way, mobile device 52 can receive notifications associated with two or more healthcare worker communication systems 50, 250, and 252, enabling healthcare workers to simultaneously monitor patients located in different healthcare facility locations.

[0038] Network 90 can include any type of wired or wireless connection, or any combination thereof. Examples of wired connections include fiber optic, Ethernet, and other wired computer networking technologies. Examples of wireless connections include broadband cellular networks such as 4G and 5G, WiFi, Bluetooth, etc.

[0039] Figure 3 The illustration schematically shows a healthcare worker mobile application 300 on a mobile device 52. In other embodiments, the healthcare worker mobile application 300 may also run on one or more servers connected to network 90, such as a nurse call server 86, an EMR server 94, an ADT server 96, and an attachment server 98.

[0040] The healthcare worker mobile application 300 can be found in 99 internet-accessible app stores (see [link]). Figure 1 The healthcare mobile application 300 can also be downloaded to mobile device 52, such as iOS and Android operating systems. Alternatively, the healthcare mobile application 300 can also be downloaded to mobile device 52 by connecting the mobile device to a data storage device storing the healthcare mobile application 300. In some examples, the healthcare mobile application 300 is downloaded to mobile device 52 under the supervision and authorization of an administrator.

[0041] like Figure 3 As illustrated in the example, healthcare worker mobile application 300 includes a communication module 302 and a site management module 304. In this example, healthcare worker mobile application 300 is the Voalte Me healthcare application from Hillrom, Batesville, Indiana, but other configurations are possible. Healthcare worker mobile application 300 may include fewer or additional software modules as desired, and therefore the software modules described herein are provided for illustrative purposes only.

[0042] Communication module 302 typically facilitates communication between healthcare worker mobile application 300 and one or more sites, such as healthcare worker communication systems 50, 250, 252, generally referred to as Figure 4 , Figure 8 and Figure 9 In this example, communication module 302 provides communication with three types of stations: active, passive, and dormant.

[0043] The active site is the current communication system that healthcare workers connect to via the 300 mobile application. As follows: Figure 4 As described, healthcare workers or staff can proactively engage with active sites using mobile device 52. Passive sites are communication systems that healthcare workers or staff log into and can receive notifications from, but are not currently active sites that the healthcare worker mobile application 300 on mobile device 52 connects to. Dormant sites are accessible sites on mobile device 52 (see [link to documentation]). Figure 6The list includes communication systems that healthcare workers are not currently logged into or connected to via the mobile application 300.

[0044] In this example, the active site is associated with healthcare worker communication system 50, the passive site is associated with healthcare worker communication system 250, and the dormant site is associated with healthcare worker communication system 252. In other examples, there may be multiple passive sites and dormant sites.

[0045] In these examples, each site managed by communication module 302 is a server or other computing device associated with one of the healthcare worker communication systems 50, 250, 252. In this example, one or more sites are Voalte servers provided by Hillrom, Batesville, Indiana, but other configurations are also possible.

[0046] Now refer to Figure 4 The image shows an exemplary user interface 400 generated by the communication module 302 on the mobile device 52. This user interface 400 typically provides information and communication between the mobile device 52 and active sites on the mobile device 52, such as the healthcare worker communication system 50.

[0047] User interface 400 includes profile option 402, which depicts information such as a picture or initials of the healthcare worker currently using mobile device 52. Selecting profile option 402 can provide additional details about the healthcare worker, such as name, phone number, and role.

[0048] User interface 400 also includes buttons 404, 406, 408, and 410 that allow healthcare professionals to select various information associated with the active site. Button 404 allows healthcare professionals to select a directory of personnel associated with the healthcare professional communication system 50. As illustrated, a portion 420 of user interface 400 can filter listed personnel based on various criteria such as building number, department, best candidate (e.g., selected by healthcare professionals), and / or team.

[0049] Buttons 406 and 408 allow healthcare workers to access prompts and text received from the proactive site; please see below. Figure 8 and Figure 9 Button 410 allows users to access settings associated with the healthcare worker mobile application 300, such as the following: Figure 5 The settings are shown in the image.

[0050] The user interface 400 also includes a notification 422 on the healthcare worker mobile application 300 that alerts healthcare workers to the proactive site (“AveraQueen of Peace” Hospital). This notification can take various forms, such as a Toast or Snackbar providing information about the proactive site.

[0051] In this embodiment, notification 422 is provided when the healthcare worker mobile application 300 is launched on the mobile device 52 (after being forcibly exited) and / or when the healthcare worker mobile application 300 comes to the foreground of the mobile device 52 (equivalent to being accessed). As described in this example, the healthcare worker may, as desired, ignore notification 422.

[0052] Figure 3 The site management module 304 manages active sites, passive sites, and dormant sites already configured on the mobile device 52. The site management module 304 allows healthcare workers to switch between sites and log in and out of sites. The site management module 304 also allows healthcare workers to add new sites and remove existing sites within the healthcare worker mobile application 300.

[0053] Now refer to Figures 5 to 8 When medical staff select button 410 on user interface 400, such as Figure 5 The exemplary user interface 500 shown provides users with various settings associated with the healthcare worker mobile application 300. One of these settings on the user interface 500 is the site change option 502.

[0054] After receiving the selection of the site change option 502 on the user interface 500, the healthcare worker mobile application 300 displays... Figure 6 The user interface 600 is shown. User interface 600 lists each site that has been configured on the healthcare worker mobile application 300. User interface 600 typically allows healthcare workers to switch between sites and define the status of each site.

[0055] More specifically, user interface 600 displays all sites 602, 604, and 606 that have been configured on the healthcare worker mobile application 300. Active site 602 is listed at the top of user interface 600. Passive site 604 is listed below the active sites. Dormant site 606 is listed below the passive sites. When listing multiple passive or dormant sites, these sites can be listed sequentially, such as by most recent to oldest time, or alphabetically based on site name.

[0056] Healthcare workers can select passive site 604 to switch from site 602 to site 604. Upon receiving the selection of site 604, the healthcare worker's mobile application 300 will display a user interface 400 showing options related to site 604. Site 602 will then switch from an active site to a passive site. Advantageously, this allows healthcare workers to access and view notifications and / or messages from site 604 while maintaining a connection to site 602 and receiving notifications from site 602.

[0057] In another illustrative example, a healthcare worker can select a dormant site 606 to switch from site 602 to site 606. Upon receiving the selection of site 606, the healthcare worker mobile application 300 will request the user to log in to site 606 by providing certificates (e.g., username and password). In some instances, these certificates may be cached and provided automatically. Subsequently, the switch is initiated using stored reconnection information for site 606 (e.g., location, certificates, configuration, etc.).

[0058] Upon receiving the necessary certificates, the healthcare worker mobile application 300 will display a user interface 400 showing options related to site 606. Site 602 will then switch from an active site to a passive site. Advantageously, this provides the technical effect that while maintaining a connection to sites 602, 604 and thus continuing to receive notifications from sites 602, 604, healthcare workers can access and view notifications and / or messages from site 606, which has switched from dormant to active.

[0059] Once the user switches to another site (whether passively or dormant), a notification 422 is provided (see [link]). Figure 4 (The example shown) alerts healthcare workers to active sites on the healthcare worker mobile application 300. The previously active site is switched to a passive site. In the event of an incorrect connection to the selected site, healthcare workers can cancel the existing switching intent and view a list of available sites on the user interface 600.

[0060] The healthcare worker mobile application 300 maintains sessions with both active and passive sites, enabling messages from both sites to be delivered to healthcare workers on the mobile device 52. This allows healthcare workers to monitor multiple sites located in different hospitals or clinics on a single mobile device and easily switch between sites.

[0061] In addition to providing a list of available sites, a badge counter 610 is provided for any site with unread notifications. In this example, site 604 has "12" notifications for healthcare workers. Healthcare workers can access these notifications by selecting site 604 to make site 604 active and accessing these notifications on the user interface 400. In some examples, a collection of all notifications (e.g., from all passive sites) may also be provided.

[0062] Each of the sites 602, 604, and 606 on the user interface 600 also provides a healthcare worker status 620. In this example, status 620 can be set to "Available," "Busy," or "Unavailable." This allows other healthcare workers associated with each of the sites 602, 604, and 606 to see the healthcare worker's status on the mobile device 52. An "Available" status indicates that the healthcare worker is free to read and respond to messages. A "Busy" status indicates that the healthcare worker is currently unable to read or respond to messages, but may become available after a specific event (e.g., surgery, phone call, etc.). An "Unavailable" status indicates that the healthcare worker is currently unable to read or respond to messages for a specified period.

[0063] For example, another healthcare worker logging into site 602 can see that healthcare worker is "Available", while another healthcare worker logging into site 604 can see that healthcare worker is "Busy". Therefore, the first state at site 602 is different from the second state at site 604.

[0064] In this example, the status can be set automatically or manually by healthcare workers. For instance, when a healthcare worker logs into the site, the status can be automatically set to "Available." When a healthcare worker receives an incoming call or has a schedule on mobile device 52, the status can be automatically set to "Busy."

[0065] like Figure 7 As shown, healthcare professionals can manually set status 620 by selecting status 620. A menu 702 is provided that allows healthcare professionals to select statuses. Furthermore, healthcare professionals can customize the status. For example, a healthcare professional could customize the status of station 604 to indicate that they will be performing surgery until noon.

[0066] review Figure 6 Since site 606 is in hibernation, its default status is "Offline". Many other configurations are also possible.

[0067] Healthcare workers can add and remove sites on the user interface 600. For example, after receiving a selection of the site addition option 710, the healthcare worker mobile application 300 displays as follows: Figure 8 The user interface shown in 800 allows you to add new sites.

[0068] Specifically, input field 802 is provided to allow the user to identify the site to be added. There are various ways to identify a site. For example, healthcare professionals can provide the site name if they know it. As the healthcare professional provides input, input field 802 can attempt to automatically complete the site name based on a list of available sites.

[0069] Healthcare workers can also provide other information associated with the site, such as a site code. A site code can be a unique identifier (GUID) that identifies the site. For example, a site code can be an alphanumeric code provided to healthcare workers. Healthcare workers can enter this code into input box 802 to allow the healthcare worker mobile application 300 to connect to the new site. If the site code is invalid, an error message is displayed to the healthcare worker, allowing them to re-enter the site code. Similarly, if the site code already exists in a site configured with the healthcare worker mobile application 300 (see user interface 600), an error is displayed to indicate that the site is already configured, allowing the healthcare worker to enter another site.

[0070] In another example, healthcare professionals may optionally provide site connectivity details, such as the Uniform Resource Locator (URL) or IP address associated with the site. Upon receiving the site identification information, the healthcare professional mobile application 300 is programmed to automatically configure the site (e.g., by translating the site name into an IP address using the Domain Name System). For example, the healthcare professional mobile application 300 may communicate with a server that manages configuration information for multiple sites, and / or with a specific site, to receive connection and certificate information. Depending on how the healthcare professional mobile application 300 is configured, this process may occur automatically or manually.

[0071] For example, in one example, the healthcare worker mobile application 300 maintains a cache of information necessary for connection and communication with each of the active, passive, and dormant sites configured for the healthcare worker mobile application 300. In this example, the cached information may include the following:

[0072]

[0073] After successfully adding a new site, it appears as a dormant site on user interface 600. Upon selecting the new site, healthcare professionals are prompted to provide credentials to allow their mobile application 300 to access it. In some examples, healthcare professionals may be able to access the new site using a single sign-on process.

[0074] Now refer to Figure 9-10An exemplary user interface 900 is shown. This interface can be generated by a healthcare worker mobile application 300 or another application running on a mobile device 52. As shown, an exemplary notification 902 originates from one of the sites (active or passive) to which the healthcare worker mobile application 300 is connected. Aspects associated with the notification (e.g., notification type, sound, etc.) can be configured by the healthcare worker.

[0075] In this example, notification 902 includes a subject and a preview of the notification content. For instance, if notification 902 is associated with a message sent by another healthcare worker, notification 902 may include information such as the other healthcare worker's name, the message subject, and at least a portion of the message content. Similarly, if notification 902 is associated with a patient's prompt, the notification may include the patient's name, an identification of the prompt, and details associated with the prompt.

[0076] Notifications from both active and passive sites also provide an indicator 904 to identify the source of the notification 902. In this example, indicator 904 indicates that the notification comes from site XXX (site XXX), such as the name of the hospital associated with that site, site code, or other identifying information, including a custom name set for the site by healthcare professionals.

[0077] Healthcare workers can select notification 902 to access the messages associated with that notification. If notification 902 originates from a passive site, such as... Figure 10 The diagram shows an alert box 1002. This alert box 1002 indicates that the healthcare worker mobile application 300 will switch the passive site associated with the notification to an active one, allowing the healthcare worker to access the message when they wish to continue. The healthcare worker can disable the alert if needed.

[0078] If healthcare workers continue to access message content at a passive site, that passive site is moved to an active site, while the previous active site is moved to a passive site on user interface 600. Healthcare worker mobile application 300 then provides the message content to the healthcare worker. Notifications (e.g., Snackbar) can also be provided to healthcare workers, allowing them to switch back to the previous active site if needed after reviewing the message.

[0079] The exemplary computing devices described herein may include at least one central processing unit (“CPU”), system memory, and a system bus coupling the system memory to the CPU. The system memory includes random access memory (“RAM”) and read-only memory (“ROM”). The ROM stores a basic input / output system containing basic routines such as transferring information between components within the computing device during startup. The computing device further includes a mass storage device. The mass storage device may store software instructions and data, such as treatment protocols and lookup tables.

[0080] Mass storage devices are connected to the CPU via a mass storage controller connected to the system bus. Mass storage devices and their associated computer-readable storage media provide non-volatile, non-transitory data storage for computing devices. Although the description of computer-readable storage media herein refers to mass storage devices, such as hard disks or solid-state drives, those skilled in the art will understand that computer-readable data storage media can include any tangible physical device or object available in the manufacturing process from which the CPU can read data and / or instructions. In some embodiments, computer-readable storage media include fully non-transitory media.

[0081] Computer-readable storage media include volatile and non-volatile media, removable and non-removable media, implemented in any method or technology for storing information such as computer-readable software instructions, data structures, program modules or other data. Exemplary types of computer-readable data storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (“DVD”) or other optical storage media, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computing device.

[0082] According to various embodiments, the computing device can utilize logical connections to other devices connected to network 90 to operate in a networked environment, including wireless networks, the Internet, or other types of networks. The computing device can be connected to network 90 via a network interface unit connected to a system bus. The network interface unit can also be used to connect to other types of networks and remote computing systems. The computing device also includes an input / output controller for receiving and processing input from a plurality of other devices, including a user interface touchscreen display or another type of input device. Similarly, the input / output controller can provide output to the user interface touchscreen display or another type of input device.

[0083] As briefly described above, the mass storage device and RAM of a computing device can store software instructions and data. Software instructions include the operating system used to control the operation of the computing device. The mass storage device and / or RAM also store software instructions that, when executed by the CPU, enable the computing device to provide the functions described herein.

[0084] The above embodiments are provided by way of illustration only and should not be construed as limiting in any way. Various modifications can be made to the above embodiments without departing from the true spirit and scope of this disclosure.

Claims

1. An electronic device for managing notifications to healthcare workers associated with multiple healthcare facilities, the electronic device comprising: processor; as well as The memory, the memory-encoded instructions, which, when executed by the processor, cause the processor to: Connect to an active site associated with the first medical institution, the active site being a server associated with the first healthcare worker communication system; Connect to a passive site associated with a second medical facility, the passive site being a server associated with a second healthcare worker communication system; Generate a user interface that provides information and communication between the electronic device and the active site, the user interface allowing the electronic device to switch between sites and define the state of each site; Receive notifications from the active site and the passive site; Maintaining a session with both the active and passive sites enables the electronic device to provide messages from both the active and passive sites to the healthcare worker. Upon receiving input from healthcare professionals on the user interface, the system switches the active site to passive and the passive site to active to access notifications from the passive site. After the passive site is switched to an active site, a notification reminding the medical staff of the active site is provided on the user interface. The electronic device further includes instructions that, when executed by the processor, cause the processor to: receive a first state of the medical staff at the first medical institution and a second state of the medical staff at the second medical institution, wherein the first state is different from the second state.

2. The electronic device of claim 1, further comprising instructions that, when executed by the processor, cause the processor to: provide customization of the first state and the second state.

3. The electronic device of claim 2, further comprising instructions that, when executed by the processor, cause the processor to: automatically set the first state and the second state.

4. The electronic device as claimed in claim 1, wherein, The notification is received from multiple passive sites connected to the electronic device.

5. The electronic device of claim 1, further comprising instructions that, when executed by the processor, cause the processor to: receive a selection of the passive site to switch the passive site to active, and switch the active site to passive.

6. The electronic device of claim 1, further comprising instructions that, when executed by the processor, cause the processor to: provide a badge counter for any one of a plurality of passive sites having unread notifications.

7. The electronic device of claim 6, further comprising instructions that, when executed by the processor, cause the processor to: in response to receiving a selection of one of the plurality of passive sites, access the unread notification to switch the selected one of the plurality of passive sites to active.

8. The electronic device of claim 1, further comprising instructions that, when executed by the processor, cause the processor to: receive a selection of a notification to access a message associated with the notification, and, when the notification originates from the passive site, display a warning box to indicate that the passive site associated with the notification will switch to active.

9. The electronic device of claim 8, further comprising instructions that, when executed by the processor, cause the processor to: switch the passive site to active and the active site to passive when the medical personnel continue to access the message at the passive site.

10. The electronic device of claim 9, further comprising instructions that, when executed by the processor, cause the processor to: provide the content of the message and provide a notification allowing the healthcare worker to switch back to the previous active site.

11. The electronic device of claim 1, further comprising instructions that, when executed by the processor, cause the processor to: add another station upon receiving a station code.

12. A non-transitory computer-readable storage medium comprising computer-readable instructions, which, when read and executed by a computing device, cause the computing device to: Connect to an active site associated with the first medical institution, the active site being a server associated with the first healthcare worker communication system; Connect to a passive site associated with a second medical facility, the passive site being a server associated with a second healthcare worker communication system; Generate a user interface that provides information and communication between the electronic device and the active site, the user interface allowing the electronic device to switch between sites and define the state of each site; Receive notifications from the active site and the passive site; Maintaining a session with both the active and passive sites enables the electronic device to provide messages from both sites to healthcare workers. Upon receiving input from healthcare professionals on the user interface, the system switches the active site to passive and the passive site to active to access notifications from the passive site. After the passive site is switched to an active site, a notification reminding the medical staff of the active site is provided on the user interface. The system receives a first state of the medical staff at the first medical institution and a second state of the medical staff at the second medical institution, wherein the first state is different from the second state.

13. The non-transitory computer-readable storage medium of claim 12, further comprising computer-readable instructions that, when read and executed by the computing device, cause the computing device to: Receive the selection of the passive site to switch the passive site to active and the active site to passive.

Images