The present disclosure relates to healthcare communication systems, such as nurse call systems. In particular the present disclosure relates to healthcare communication systems having a master station and devices in patient rooms that communicate with the master station.
Most hospitals and other types of in-patient healthcare facilities have some sort of a nurse call system. Patients place nurse calls by pressing a nurse call button located on a hospital bed or on a hand-held unit, known in the art as a pillow speaker or pillow speaker unit, or by actuating a wall mounted switch. After a patient places a nurse call, a caregiver at a master station may answer the nurse call which enables voice communications between the caregiver at the master station and the patient. To facilitate such voice communications a microphone and speaker is located somewhere in the patient room. Oftentimes the microphone and speaker are included in the pillow speaker unit or in an audio station mounted to a wall of the patient or to headwall unit which is, in turn, mounted to a wall of the patient room.
One example of a known nurse call system is Hill-Rom's COMLINX® system. In addition to the voice communication function, the COMLINX system is connected to the patient's hospital bed to receive bed status information regarding various aspects of the hospital bed such as the position of the siderails of the bed (e.g., up or down), whether the bed's casters are braked or released, whether or not an upper frame of the bed is in its lowest position, and so forth. See, for example, U.S. Pat. Nos. 7,242,308; 6,897,780; 6,362,725; 6,147,592; 5,838,223; 5,699,038; and 5,561,412, which relate to the COMLINX system. Another example of a known nurse call system is G.E. Healthcare's TELLIGENCE™ system.
The present invention comprises a healthcare communication system and/or method, or a component thereof, that has any one or more of the features listed in the appended claims and/or any one or more of the following features, which alone or in any combination may comprise patentable subject matter:
A healthcare communication system may comprise a first plurality of computer devices that are operable as a nurse call system. The first plurality of computer devices may have core nurse call functionality residing on an embedded computing platform. The first plurality of computer devices may include patient stations, staff stations, or master stations of the nurse call system and any of these stations may have a graphical display screen. The healthcare communication system may have a second plurality of computer devices that are operable to provide the first plurality of computer devices with additional functionality via software plug-ins that are transmitted to one or more of the first plurality of computer devices. Some or all of the second plurality of computer devices may be part of an Ethernet of the healthcare facility.
Use of a user interface displayed on the graphical display screen may result in at least one of the software plug-ins being transmitted to at least one of the first plurality of computer devices. The first plurality of computer devices may include an input/output (I/O) circuit that is coupled to an associated patient station. Some of the software plug-ins may be operable to change the user interface of the graphical display screen to a different user interface. In response to a new computer device being added to the first plurality of computer devices, such as connecting a new patient station or staff station to the nurse call system, at least one of the second plurality of computer devices automatically transmits at least one software plug-in to the new computer device.
The additional functionality of the second plurality of computer devices may reside on a server computing platform. The second plurality of software devices may be configured such that at least one of the software plug-ins is transmitted to the first plurality of computer devices on an as needed basis as dictated by use of at least one of the first plurality of computer devices. Additionally or alternatively, the second plurality of software devices may be configured such that at least one of the software plug-ins is transmitted to some or all of the first plurality of computer devices in response to use of at least one of the second plurality of computer devices. Software upgrades or updates installed on at least one of the second plurality of computer devices may be distributed automatically to at least some of the first plurality of computer devices. The software upgrades or updates may also be distributed automatically to at least one other computer device of the second plurality of computer devices.
The core nurse call functionality may comprise functionality regulated by a regulations entity, such as a governmental body or standards setting organization such as Underwriter's Laboratories, and the additional functionality may comprise non-regulated functionality. For example, in some embodiments, the first plurality of computer devices may be compliant with the Underwriter's Laboratories UL-1069 standard.
The first plurality of computer devices and/or the second plurality of computer devices may incorporate Publish and Subscribe (PubSub) data communication technology. The PubSub data communication technology permits at least one computer device of the first plurality of computer devices to publish data to, and/or to subscribe to data from, at least one computer device of the second plurality of computer devices, and vice versa. At least one of the first plurality of computer devices may be communicatively coupled to a hospital bed and may receive bed status data from the hospital bed.
At least one computer device of the first plurality of computer devices may have auto-discovery software that is operable, in response to installation of the at least on computer in the nurse call system, to detect network connectivity and to initiate communications with a device manager. The device manager may be operable to provide software modules and/or network settings to the at least one computer device of the first plurality of computer devices
The healthcare communication system may have at least one additional computer device that may be coupled to at least one of the computer devices of the first plurality or second plurality of computer devices and that may incorporate a software-based or hard-ware based Session Initiation Protocol (SIP) voice over Internet protocol (VoIP) to separate the setting up and tearing down of voice calls between SIP enabled voice endpoint devices. The at least one additional computer device may comprise, for example, a VoIP private branch exchange (PBX). At least one of the first computer devices may comprise a VoIP room gateway that is operable to distribute communication data to multiple voice terminals or VoIP voice endpoints installed in patient rooms and hallways.
The first plurality of computer devices may be interconnected logically and/or physically in a tiered architecture arrangement to provide fault isolation among the tiers so that faults occurring in computer devices of one tier don't affect the operability of computer devices in other tiers and/or so that faults occurring in any of the second plurality of computer devices don't affect the core nurse call functionality of the first plurality of computer devices.
At least one of the tiers in such an arrangement may comprise a subset of the first plurality of computer devices that are associated with a patient room. Another of the tiers in such an arrangement may comprise a subset of the first plurality of computer devices that are associated with a nursing unit having a plurality of patient rooms.
At least one computer device of the first plurality of second plurality of computer devices may comprise a server that is equipped with Redundant Arrays of Independent Disks or Drives (RAID), redundant power supplies, and/or clustering failover capability. At least one computer device of the first plurality of second plurality of computer devices may comprise broker service software that may be operable to monitor other services on the first plurality and/or second plurality of computer devices and that may repair or restart faulty services.
Additional features, which alone or in combination with any other feature(s), such as those listed above, may comprise patentable subject matter and will become apparent to those skilled in the art upon consideration of the following detailed description of various embodiments exemplifying the best mode of carrying out the embodiments as presently perceived.
The detailed description particularly refers to the accompanying figures, in which:
A healthcare communication system 20 includes a plurality of graphical audio stations 22 and a master station or console 24 which are communicatively coupled as shown diagrammatically in
Patient stations 22 communicate bidirectionally (e.g., two-way communication) with an input/output (I/O) circuit 27 which is located within a housing 26 mounted near a dome light assembly 28. The bidirectional communication is indicated diagrammatically in
A 9-page electric circuit schematic illustrating one possible electric circuit implementation of one embodiment of the circuitry of dome light assembly 28 is shown in FIG. 12 of U.S. Provisional Patent Application No. 61/066,877, which was filed Feb. 22, 2008, which was titled “Distributed Healthcare Communication System,” and which is already incorporated by reference herein. In one embodiment, dome light assembly 28 is, for example, an International Business Machines (IBM) Part No. 43T1899 dome light fixture. A 55-page electric circuit schematic illustrating one possible electric circuit implementation of input/output (I/O) circuit 27 according to this disclosure is shown in FIG. 15 of U.S. Provisional Patent Application No. 61/066,877 which is already incorporated by reference herein. In one embodiment, I/O circuit 27 is, for example, an IBM part no. 43T2063 IO Board. In some Appendices of the written description of U.S. Provisional Patent Application No. 61/066,877, I/O circuit 27 may be referred to as an I/O board or an I/O circuit board. However, this is not to imply that all circuit components of the circuitry of I/O circuit 27 need to be on a single circuit board, but that is certainly one possibility. Thus, in some contemplated embodiments I/O circuitry 27 may be distributed among numerous circuit boards, and in other contemplated embodiments some or all of the components of circuit 27 may not be on any circuit board at all. While illustrative circuit 27 is located in housing 26, it is within the scope of this disclosure for various components of circuit 27 to be located in separate housings.
The I/O circuit 27 of assembly 28 communicates bidirectionally with a Power over Ethernet (PoE) switch 32 as indicated diagrammatically in
Typically, all of the patient stations 22 of a nursing unit communicate with the same master station 24. The master stations 24 and graphical audio stations 22 of different nursing units may be coupled together by interconnecting the respective PoE switches as indicated diagrammatically in
In some embodiments, such as the one shown in
One version of bed connector unit 40 is referred to in some of the Appendices of the written description of U.S. Provisional Patent Application No. 61/066,877 as a Bed Interface Unit (BIU) which, in one embodiment, includes a 37-pin connector to attach to a bed cable, includes another connector for attachment of a call pendant or pillow speaker unit, and an includes a button that can be manually pressed to send and/or cancel a nurse call. Another version of a bed connector 228 is referred to as a Silver Plate in some of the Appendices attached in U.S. Provisional Patent Application No. 61/066,877 and is shown in
Many other types of devices in a patient room may also couple to a respective I/O circuit 27 mounted near the corresponding dome light assembly 28 to communicate with master station 24 and, if desired, other computer devices of the a computer network of the healthcare facility. For example, in
As previously mentioned, some graphical audio stations 22 are located in staff work areas and are referred to as staff stations or consoles 22. In
Each of the communications links 30, 34, 36, 44, 46, 50, 54, 60, 62, 66 shown diagrammatically by lines or arrows in
While this disclosure contemplates that the data formatting for the data transmitted over any of links 30, 34, 36, 44, 46, 50, 54, 60, 62, 66, 68, 70 may be according to any suitable data formatting protocol, in one embodiment, the data formatting protocol is according to the protocol discussed in detail in the “Project NCM II, Interface Design Specification, NPD05514” document which is attached to U.S. Provisional Patent Application No. 61/066,877 as Appendix 1 and which is considered part of the written description of that provisional patent application and of this patent application via the incorporation by reference previously made in this application of U.S. Provisional Patent Application No. 61/066,877. In general, the protocol described in Appendix 1 of U.S. Provisional Patent Application No. 61/066,877 uses extensible markup language (XML) strings to transfer data. This protocol is sometimes referred to as the Palmetto Protocol and is sometimes referred to as the XML protocol herein and in some of the documents in the Appendices of the written description of U.S. Provisional Patent Application No. 61/066,877. It is also contemplated that the communication protocol for links 30, 34, 36, 44, 46, 50, 54, 60, 62, 66 may be according to any suitable protocol such as the TCP/IP protocol, the RS-232 protocol, the RS-422 protocol, the RS-423 protocol, or the RS-485 protocol, or similar such protocols, and such as wireless protocols including any of the IEEE 802.11x protocols (where x represents the various revision levels a, b, c, d, e, g and so forth of the 802.11 protocol), the Bluetooth protocol, the Zigbee protocol, or similar such wireless communication protocols.
In one embodiment, links 44, 46, 54, 62, which are the communications links associated with a patient room that communicate between devices in the patient room and the I/O circuit board of dome light assembly 28, are according to the RS-485 protocol, whereas links 34, 36, 68, 70, which are the links to and from PoE switch 32, are according to the TCP/IP protocol. The devices that communicate over these various links are configured and programmed appropriately for the required RS-485 or TCP/IP protocol, as the case may be.
It should be noted that, in one contemplated embodiment, link 30 comprises a coupler that couples to a PoE port of the respective I/O circuit 27 such that communications over link 30 are transmitted according to the TCP/IP protocol and I/O circuit 27 provides feed through of any data, including communication data such as voice data, communicated between station 22 and PoE switch 32. Because stations 22 communicate according to the TCP/IP protocol, staff stations 22 are coupleable to PoE switch 32 without the use of an intervening I/O circuit 27, if desired. As to the various devices coupled to I/O circuit 27 other than station 22, the circuitry of I/O circuit 27 operates to convert the data from these various devices according to their device-specific communication protocols (e.g., serial links to stations 122, 222; locating and tracking receiver 56 room bus protocol; bed connector 40 room bus protocol; and serial to dome light protocol) into the TCP/IP protocol for subsequent transmission to the PoE switch and ultimately to the master station 24 and beyond, if desired.
According to this disclosure, system 20 is scaleable such that basic, intermediate, and advanced nurse call systems can be created depending upon the particular requirements of a particular healthcare facility. The graphical audio stations 22 discussed herein are associated with an advanced nurse call system and are referred to in several of the documents of the Appendices of U.S. Provisional Patent Application No. 61/066,877, which are considered part of this written description via incorporation by reference, as an advanced graphical audio station (AGAS) and are referred to in the documents of the Appendices of U.S. Provisional Patent Application No. 61/145,306, which is also considered part of this written description via incorporation by reference, as a Graphical Room Station 10 (GRS-10). A 42-page electric circuit schematic illustrating one possible electric circuit implementation of one embodiment of an advanced graphical audio station (AGAS) 22 according to this disclosure is shown in FIG. 11 of U.S. Provisional Patent Application No. 61/066,877. In one embodiment, audio graphical station 22 is an IBM part no. 43T2058 station.
A graphical audio station 122, shown in
A standard audio station 222, shown in
Standard audio stations 222 are a low cost offering that provides call cancel, call placement, reception for signals from badges 58, and voice communication functionality. As mentioned already, stations 222 do not have a graphical display. Stations 222 connect to the I/O circuit board of assembly 28 via an RS-485 connection 30. Stations 222 can be configured as a patient station, staff station, or visitor station. As indicated in
While
Intermediate level audio stations 122 are a mid range offering that provides all of the functionality that a standard audio station 222 provides. In addition, stations 122 have small touch screen displays 124 that allow for monitoring calls, monitoring other types of alerts, view the location of staff, call located staff, change bed status (e.g., clean or dirty status), enable and disable nurse calls and alerts for a location or for a nursing unit. Unlike station 222, station 122 runs a Linux operating system (OS) that drives the graphical display and responds to user interaction. The content for display 124 of station 122 is controlled by the associated I/O circuit board 27 and by advanced services which are resident on other computer devices of system 20 as will be further discussed below. For base functionality, the I/O circuit controls the display of station 122 by sending XML strings to station 122. The circuitry of station 122 interprets those strings and displays a corresponding user interface (UI). If an advanced functionality is requested by station 122, the I/O circuit forwards the request for the advanced service(s) and the computer device of system 20 having the advanced service(s) replies back with the content in the appropriately formatted XML string.
In the illustrative example, advanced level audio stations 22, 24 provide all of the functionality of stations 122 except stations 22 couple to bed connectors 40, 224 via I/O circuits and not directly. However, in other embodiments contemplated herein, either of connectors 40, 224 may be integrated into station 22 or connected thereto in a manner similar to which they are integrated or connected in stations 122, 222 as described above. Stations 22, 24 also run a Linux OS, but it is written in C# programming code and executed under Mono, an open source implementation of the .NET framework maintained by Novell. This permits some code sharing between base and advanced systems as discussed in more detail below, and in the Appendices of U.S. Provisional Patent Application No. 61/066,877 which are already incorporated by reference herein.
In broad general terms, it is the stations 22, 24 which are configured to communicate with various other computer devices, such as servers, included in the Ethernet of a healthcare facilities' system 20 and it is this additional communication capability that distinguishes these devices as advanced graphical audio stations. According to this disclosure, the components of system 20 which cooperate to provide a healthcare facility with a nurse call system are referred to collectively as a “base nurse call system.” Thus, stations 22, 122, 222 and I/O circuit 27, dome light assemblies 28, and any of the equipment described above that is capable of providing a nurse call signal, as well as the associated master station 24 and PoE switch 32 along with any of the communication links interconnecting these components, are among the components which comprise a “base nurse call system” according to this disclosure. Staff stations 22, if present, are also considered to comprise part of the base nurse call system.
If voice communication capability among stations 22, 24, 122, 222 is to be a function of the nurse call system, then a Voice over Internet Protocol (VoIP) sever 250 is also included in the base nurse call system and is coupled to PoE switch 32 via a TCP/IP communications link 252 as shown in
According to this disclosure, stations 22, 24 also permit users to perform functions associated with an “advanced services system.” The software code, such as applets or plug-ins, that provides stations 22 with these advanced functions may be communicated from various servers, or similar such computer devices discussed below, to stations 22 via stations 24, PoE switch 32, I/O boards 27, and the associated links 30, 34, 36. Thus, stations 22, 24 are dependent upon some devices that are not part of the base nurse call system, but instead are part of the advanced services system, to provide the advanced functionality to stations 22, 24. However, if these other devices are inoperable or communications with such devices of the advanced services system cannot be established or is otherwise faulty, the base nurse call system functionality is still able to operate. Thus, functionally, the base nurse call system is isolated from the advanced services system from a hardware standpoint and from a software standpoint.
System 20 includes an enterprise server 260 which is included as part of the advanced services system as shown in
As shown in
While the term “server” is used herein, it will be understood by those skilled in the art that the functionality represented or performed by devices referred to as “severs” may comprise and be performed by any suitable computer device having software programs or services that may be resident and/or executable by any computer, device or equipment in the system or more than one computer, device or equipment in the network. Thus, there term “server” is intended to broadly encompass any computer device that is capable of performing the mentioned functions.
In the illustrated embodiment, server 284 is configured to provide communication and configuration for wireless devices using Emergin Wireless Office; server 286 is configured to provide communication and configuration for wireless Vocera devices; server 290 is configured to interface with or be included as part of a Hill-Rom® NaviCare™ system to receive and process task assignment and completion information. Plug-ins or applets or similar such software code may be resident on any of servers 260, 282, 284, 286, 288, 290, 292, 294, for example, and be retrieved by stations 22, 24 via server 260 as part of the “advanced services system” functionality. The software to display a particular user interface associated with an advanced service on a particular station 22, 24 which is operated by a user in a manner resulting in the request of the advance service may be executed on a device other than the one that requested it. For example, such advance service software may be executed by the circuitry of a master station 24 or I/O circuit 27, but yet the resulting user interface is display on one of stations 22. Additional details of the advanced services functionality are shown and described in the “Code Blue Advanced System Software, Architectural Design Specificaiton, NPD05503” document attached to U.S. Provisional Patent Application No. 61/066,877 as Appendix 2 and is considered part of the written description of this patent application via incorporation by referenced of U.S. Provisional Patent Application No. 61/066,877. Further details of system 20 and its functionality are also provided in this same U.S. Provisional Patent Application No. 61/066,877.
Referring now to
The primary console 24 is configured to communicate with a specific IP address and port which are associated with the device service. The device service accepts any incoming connections from one or more primary consoles 24 and monitors the consoles 24 to determine if any advanced service functionality is to be delivered to a particular console 24, possibly for subsequent distribution by console 24 to other devices, such as stations 22, 122 and circuit 27, for example. The various activities occurring in the base nurse call system are communicated by consoles 24 to the device service which operates to relay relevant data to any other advanced service or any other computer device which have subscribed to receive such data or to which the device service publishes such data.
In the illustrative example, the advanced services system includes a configuration service module 304, an alert/call service module 306, a communication service module 308, a location service module 310, a staff service module 312, a roll services module 314, a broker/supervisor service module 316, a logging service module 318, a patient service module 320, a licensing service module 322, an HL7 service module 324, and a legacy integration service module 326. Legacy integration service module 326 provides connectivity to existing nurse call systems, such as the COMLINX® system, which is represented in
As mentioned above, device service module 302 is resident on server 260. However, it is within the scope of this disclosure for any one or more of service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 to be resident on any one or more of servers 260, 282, 284, 286, 288, 290, 292, 294. In one embodiment, however, all of service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 are resident on server 260. The listed service modules and/or other service modules may also be resident on VoIP server 250 in other embodiments.
If one of the advanced services needs to transmit commands or information to a device of the base nurse call system, for example, if the advanced service needs to communicate to primary console 24 an alert condition occurring in some other portion of system 20 or the advanced system needs to command the I/O circuit 27 to reset, device service 302 sends to the primary console 24 the data or command through a TCP/IP socket connection of the primary console 24 using the XML over TCP/IP protocol discussed above and in the Appendices of U.S. Provisional Patent Application No. 61/066,918 which is already incorporated by reference herein.
This disclosure contemplates a second line of communication to devices of the base nurse call system, which second line of communication is through a defined interface. The base application running on stations 22, 24 is written in C# using Mono on Linux as mentioned previously. Advanced features are enabled on stations 22, 24 by pushing advanced plug-ins down to stations 22, 24 and having them dynamically loaded in separate application domains when needed. The description below of how plug-ins operate on one of stations 22 is applicable to other stations 22, 24 as well, and also to stations 122 in some embodiments.
A logical representation of this second line of communication is illustrated in
Station 22 has an interface 354 between firmware 350 and integration software. Interface 354 is a control interface and, in the illustrative embodiment, is not intended to transfer data. Data transfer through interface 354 may occur in other embodiments, however. Interface 354 provides the ability of station 22 to load and unload one or more plug-ins, start and stop the functionality of the plug-ins, and show and hide the plug-in's user interface, if the plug-in has one associated with it.
When a new device, such as one of stations 22, 24 or I/O circuit 27, is added to the system, server 260 pushes one or more software plug-ins, as appropriate, from one or more of advanced service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 in response to server 260 becoming aware of the new device. The one or more software plug-ins are installed and become operational when launched, such as when a user first uses an associated advanced service on the device. Future updates and upgrades of the plug-ins pushed to the new device are also sent to the new device automatically.
According to this disclosure, system 20 includes a hospital administrative client computer 360 as shown in
Computer 360 may also be used to distribute software upgrades and updates throughout system 20, including to devices of the base nurse call system. The software upgrades and updates are distributable all at once to the multiple devices using computer 360. This eliminates the need to load software upgrades and updates on individual computer devices of the base nurse call system. Microsoft ClickOnce application software is an example of software that computer 360 may use to implement this manner of software upgrades and updates.
It should be appreciated that, as to the base nurse call system components, the software upgrades and updates distributed by computer 360 relate only to the advanced functionality of the base nurse call system and not the core nurse call functionality of the base nurse call system. That is, the software updates and upgrades do not change any of the firmware 350 of the embedded computer platforms of stations 22, 24 or other devices of the base nurse call system, such as circuit 27. By isolating the core nurse call functionality from the advanced services functionality of stations 22, 24 in this way, recertification for compliance with the UL-1069 standard is not needed when any of the advanced services are upgraded or updated or additional advanced services added. Thus, regulated functionality of the base nurse call system is isolated on a software basis and/or a hardware basis from the advanced services that are run on some of the devices of the base nurse call system.
The architecture of system 20 allows a user to have access to both the core nurse call functionality and other optional features that are available seamlessly via the embedded computing platform of stations 22, 24, and stations 122 in some embodiments. By use of software plug-ins to accomplish this, stable software that is stored locally is combined with the optional software of the plug-ins, which is applied to the embedded platform as needed. For example, a portion of a user interface on the graphical display screens of stations 22, 24, 122, are generated with local software, whereas other user interfaces, or portions thereof, are generated by the software plug-ins but this is generally unknown and undetected by the user.
In one embodiment, server 260 is a Windows-based server platform capable of running .NET 3.0 in order to support Windows Communications Foundation (WCF), a service architecture framework provided by Microsoft. Advanced service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 are implemented in WCF and communicate using deployment-time configured protocols. In the case in which all of service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 are running on the same machine, such as server 260, each service communicates to the others using Named Pipes which is an efficient means of communication and supports state machine deployment. In other instances, service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 are configured to communicate via a binary TCP/IP protocol, using Microsoft Message Queuing (MSMQ) to provide substantially guaranteed delivery, and Hypertext Transfer Protocol (HTTP) when providing compatibility to Mono and other third party integrations. Each service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 may be configured to communicate over more than one binding in order to support simultaneous usage from legacy systems as well as base nurse call system disclosed herein. Additional details of the service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326 are provided in the document attached as Appendix 2 to U.S. Patent Application No. 61/066,918 which is already incorporated by reference herein.
System 20 is configured in a tiered architecture arrangement to incorporate several levels of fault tolerance, redundancy, and self monitoring to lessen the impact of component failures on users of the system. System 20 is tiered at several levels to achieve this fault tolerance. For example, the room gateway (e.g., I/O circuit) has sufficient computing power and functionality to allow a patient, caregiver, or monitoring device to initiate an alert even if there is a major fault in a portion of the system 20 not associated with the particular patient room. This aspect of system 20 may be referred to as room survivability. Another level of the tiered architecture arrangement is that the master nurse station console 24 has sufficient computing power and functionality to run an entire nursing unit with all the core nurse call system functionality, even if server 260 has a major failure. This aspect of system 20 may be referred to as nursing unit survivability.
At the enterprise level of system 20, which includes, but is not limited to, the devices associated with the advanced services system, there are many hardware and software mechanisms included throughout the system that allow some or all of the system 20 to remain functional despite the occurrence of a variety of faults. For example, any one or more of servers 250, 260, 282, 284, 286, 288, 290, 292, 294 may be equipped with at least one of Redundant Arrays of Independent Disks or Drives (RAID), redundant power supplies, or clustering failover capability. Broker service module 316 operates to monitor the health of the other service modules 302, 304, 306, 308, 310, 312, 314, 318, 320, 322, 324, 326 and is operable to repair or restart faulty services, in some instances.
As mentioned above, system 20 comprises a software architecture that incorporates distributed Publish and Subscribe (PubSup) data communication technology. This allows many services and applications to easily communicate and share data with each other. The PubSub data communication technology allows this data sharing between software services and applications on the same computing platform or between many computing platforms across a network. Each service or application, such as one or more of service modules 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326, has the ability to publish or make available its data to other services or applications (e.g., subscribers) that have a use for the data. As the data changes, the subscribers are automatically updated.
Stations 22, 24, and stations 122 in some embodiments, as well as I/O circuit 27 each include auto-discovery technology, such as software, that allows these computer devices to discover their network connectivity settings, software modules, and other system responsibilities when first installed in system 20. Each of these computer devices are configured with the auto-discovery technology at the time of manufacture. When a device is installed, the auto-discovery software of the device operates to automatically seek and initiate contact with a device manager. The device manager, such as server 260, will then communicate appropriate network settings, transfer the required software modules, and/or assign other responsibilities to the newly installed device. That newly installed device is then operational on system 20 once this information from the device manager is received.
According to this disclosure, in some embodiments, system 20 incorporates software-based or hardware-based Session Initiation Protocol (SIP) voice over internet protocol (VoIP) technology to separate the set up and tear down of voice calls between SIP enabled voice endpoint devices. This is accomplished having a separate VoIP private branch exchange (PBX), such as PBX 264 (e.g., hard-ware based) or servers 250284, 286 (software-based), that has connectivity to the rest of system 20 and/or to PSTN 268. System 20 also incorporates a VoIP room gateway, such as I/O circuit 27, which can distribute voice communications to multiple voice terminals or VoIP voice endpoints installed in patient rooms and hallways.
As is apparent from the discussion above, some of the improvements realized by system 20 over prior art systems include the following improvements. The distributed architecture retains and preserves the most critical functionality at the local user level should a failure occur in system 20 outside that local area, which lessens system wide impact due to single points of failure. Distributing software updates and upgrades from administration computer device 360 greatly reduces the time required to perform updates and upgrades to numerous devices and lessens the chance that devices are not updated due to human error. Computer 360 permits a user to easily and quickly install software applications on numerous devices. Also, software maintenance is simplified by having some updates and upgrades distributed automatically when a particular application is launched. Use of software plug-ins allows the core nurse call functionality software to be developed, built, and tested separate from the optional software. This lessens the chance of the core software being adversely affected by changes to the optional software. It also allows the core software to remain more stable though product life cycle and reduce the number of regulatory submissions. It should be appreciated that various system embodiments according to this disclosure may not be configured to have all of the improvements mentioned above in this paragraph or even any of them.
Additional improvements realized by system 20 over prior art systems include the following improvements. The fault tolerant, tiered architecture arrangement of system 20 increases reliability by reducing single points of failure in the system. It also allows a technician to perform maintenance on the system while impacting few or no other users. The PubSub technology allows communication and sharing to occur more efficiently and makes software development easier and faster because individual developers are able to focus on their particular software application or service. The auto-discovery technology eases installation and greatly reduces installation and repair times, as well as eliminating the need for the installation technician to connect to each device, one at a time, to configure network settings and install software. Having a separate SIP VoIP PBX allows the healthcare facility to select from a variety of compliant PBX's on the market or to use one the facility already possesses for their other voice systems. The SIP VoIP PBX also isolates less critical voice features from the core nurse call alert notification features. The flexibility to use either a software-based or hardware-based SIP VoIP PBX gives healthcare facilities the option to install this functionality on existing servers or to use a high reliability hardware appliance to support voice features of the system. Use of the VoIP room gateway gives the healthcare facility the flexibility to select lower cost voice terminals with limited functionality or higher cost VoIP voice endpoints with more functionality. It should be appreciated that various system embodiments according to this disclosure may not be configured to have all of the improvements mentioned above in this paragraph or even any of them.
Although certain illustrative embodiments have been described in detail above, variations and modifications exist within the scope and spirit of this disclosure as described and as defined in the following claims.
This application is a continuation of U.S. application Ser. No. 12/369,818, filed Feb. 12, 2009, now U.S. Pat. No. 8,046,625, which claims the benefit, under 35 U.S.C. §119(e), of U.S. Provisional Patent Application Nos. 61/066,877, 61/066,882, 61/066,883, and 61/066,918, each of which was filed Feb. 22, 2008, and U.S. Provisional Patent Application No. 61/145,306, which was filed Jan. 16, 2009, the disclosures of all of which are hereby expressly incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
2330356 | Belliveau | Sep 1943 | A |
2335524 | Lomax | Nov 1943 | A |
2736888 | McLain | Feb 1956 | A |
2896021 | Philipps | Jul 1959 | A |
3098220 | De Graaf | Jul 1963 | A |
3439320 | Ward | Apr 1969 | A |
3478344 | Schwitzgebel et al. | Nov 1969 | A |
3553383 | Rochtus | Jan 1971 | A |
3599199 | Bunting | Aug 1971 | A |
3599200 | Bunting | Aug 1971 | A |
3696384 | Lester | Oct 1972 | A |
3739329 | Lester | Jun 1973 | A |
3767859 | Doering et al. | Oct 1973 | A |
3805265 | Lester | Apr 1974 | A |
3913153 | Adams et al. | Oct 1975 | A |
3973200 | Akerberg | Aug 1976 | A |
4067005 | Levy et al. | Jan 1978 | A |
4150284 | Trenkler et al. | Apr 1979 | A |
4151407 | McBride et al. | Apr 1979 | A |
4183015 | Drew et al. | Jan 1980 | A |
4216462 | McGrath et al. | Aug 1980 | A |
4225953 | Simon et al. | Sep 1980 | A |
4228426 | Roberts | Oct 1980 | A |
4237344 | Moore | Dec 1980 | A |
4264982 | Sakarya | Apr 1981 | A |
4275385 | White | Jun 1981 | A |
4279433 | Petaja | Jul 1981 | A |
4298863 | Natitus et al. | Nov 1981 | A |
4331953 | Blevins et al. | May 1982 | A |
4356475 | Neumann et al. | Oct 1982 | A |
4418334 | Burnett | Nov 1983 | A |
4455548 | Burnett | Jun 1984 | A |
4489387 | Lamb et al. | Dec 1984 | A |
4495495 | Ormanns et al. | Jan 1985 | A |
4495496 | Miller, III | Jan 1985 | A |
4539560 | Fleck et al. | Sep 1985 | A |
4577185 | Andersen | Mar 1986 | A |
4578671 | Flowers | Mar 1986 | A |
4593273 | Narcisse | Jun 1986 | A |
4598275 | Ross et al. | Jul 1986 | A |
4601064 | Shipley | Jul 1986 | A |
4649385 | Aires et al. | Mar 1987 | A |
4680790 | Packard et al. | Jul 1987 | A |
4709330 | Yokoi et al. | Nov 1987 | A |
4740788 | Konneker | Apr 1988 | A |
4752951 | Konneker | Jun 1988 | A |
4792798 | Wilowski | Dec 1988 | A |
4795905 | Zierhut | Jan 1989 | A |
4814751 | Hawkins et al. | Mar 1989 | A |
4833452 | Currier | May 1989 | A |
4833467 | Kobayashi et al. | May 1989 | A |
4837568 | Snaper | Jun 1989 | A |
4853692 | Wolk et al. | Aug 1989 | A |
4899135 | Chahariiran | Feb 1990 | A |
4907845 | Wood | Mar 1990 | A |
4947152 | Hodges | Aug 1990 | A |
4955000 | Nastrom | Sep 1990 | A |
4967195 | Shipley | Oct 1990 | A |
4990892 | Guest et al. | Feb 1991 | A |
4998095 | Shields | Mar 1991 | A |
4998939 | Potthast et al. | Mar 1991 | A |
5006830 | Merritt | Apr 1991 | A |
5027314 | Linwood et al. | Jun 1991 | A |
5041086 | Koenig et al. | Aug 1991 | A |
5062151 | Shipley | Oct 1991 | A |
5065154 | Kaiser | Nov 1991 | A |
5075523 | Ford | Dec 1991 | A |
5086290 | Murray et al. | Feb 1992 | A |
5103108 | Crimmins | Apr 1992 | A |
5124991 | Allen | Jun 1992 | A |
5137033 | Norton | Aug 1992 | A |
5140309 | Gusakov | Aug 1992 | A |
5153584 | Engira | Oct 1992 | A |
5235258 | Schuerch | Aug 1993 | A |
5266944 | Carroll et al. | Nov 1993 | A |
5276680 | Messenger | Jan 1994 | A |
5291399 | Chaco | Mar 1994 | A |
5319355 | Russek | Jun 1994 | A |
5319363 | Welch et al. | Jun 1994 | A |
5327592 | Stump | Jul 1994 | A |
5351439 | Takeda et al. | Oct 1994 | A |
5357254 | Kah, Jr. | Oct 1994 | A |
5375604 | Kelly et al. | Dec 1994 | A |
5396224 | Dukes et al. | Mar 1995 | A |
5396227 | Carroll et al. | Mar 1995 | A |
5416695 | Stutman et al. | May 1995 | A |
5430900 | Kim | Jul 1995 | A |
5434775 | Sims et al. | Jul 1995 | A |
5446678 | Saltzstein et al. | Aug 1995 | A |
5455560 | Owen | Oct 1995 | A |
5458123 | Unger | Oct 1995 | A |
5461390 | Hoshen | Oct 1995 | A |
5475367 | Prevost | Dec 1995 | A |
5511256 | Capaldi | Apr 1996 | A |
5534851 | Russek | Jul 1996 | A |
5537459 | Price et al. | Jul 1996 | A |
5548637 | Heller et al. | Aug 1996 | A |
5549113 | Halleck et al. | Aug 1996 | A |
5561412 | Novak et al. | Oct 1996 | A |
5564108 | Hunsaker et al. | Oct 1996 | A |
5568119 | Schipper et al. | Oct 1996 | A |
5576452 | Dever et al. | Nov 1996 | A |
5576952 | Stutman et al. | Nov 1996 | A |
5579001 | Dempsey et al. | Nov 1996 | A |
5588005 | Ali et al. | Dec 1996 | A |
5594786 | Chaco et al. | Jan 1997 | A |
5600214 | Fromson | Feb 1997 | A |
5621388 | Sherburne et al. | Apr 1997 | A |
5635907 | Bernard et al. | Jun 1997 | A |
5636245 | Ernst et al. | Jun 1997 | A |
5640953 | Bishop et al. | Jun 1997 | A |
5649833 | Pfeuffer et al. | Jul 1997 | A |
5650769 | Campana, Jr. | Jul 1997 | A |
5650770 | Schlager et al. | Jul 1997 | A |
5664270 | Bell et al. | Sep 1997 | A |
5682139 | Pradeep et al. | Oct 1997 | A |
5686888 | Welles, II | Nov 1997 | A |
5686902 | Reis et al. | Nov 1997 | A |
5687734 | Dempsey et al. | Nov 1997 | A |
5689229 | Chaco et al. | Nov 1997 | A |
5691980 | Welles, II et al. | Nov 1997 | A |
5699038 | Ulrich et al. | Dec 1997 | A |
5705980 | Shapiro | Jan 1998 | A |
5708421 | Boyd | Jan 1998 | A |
5713856 | Eggers et al. | Feb 1998 | A |
5714548 | Ma et al. | Feb 1998 | A |
5719761 | Gatti et al. | Feb 1998 | A |
5731757 | Layson, Jr. | Mar 1998 | A |
5742237 | Bledsoe | Apr 1998 | A |
5751246 | Hertel | May 1998 | A |
5752917 | Fuchs | May 1998 | A |
5760704 | Barton et al. | Jun 1998 | A |
5767791 | Stoop et al. | Jun 1998 | A |
5781442 | Engleson et al. | Jul 1998 | A |
5781921 | Nichols | Jul 1998 | A |
5787528 | Antinori | Aug 1998 | A |
5793290 | Eagleson et al. | Aug 1998 | A |
5808564 | Simms et al. | Sep 1998 | A |
5812056 | Law | Sep 1998 | A |
5822418 | Yacenda et al. | Oct 1998 | A |
5822544 | Chaco et al. | Oct 1998 | A |
5838223 | Gallant et al. | Nov 1998 | A |
5844488 | Musick | Dec 1998 | A |
5867821 | Ballantyne et al. | Feb 1999 | A |
5877675 | Rebstock et al. | Mar 1999 | A |
5901391 | Kato | May 1999 | A |
5933488 | Marcus et al. | Aug 1999 | A |
5936539 | Fuchs | Aug 1999 | A |
5942986 | Shabot et al. | Aug 1999 | A |
5944659 | Flach et al. | Aug 1999 | A |
5956539 | Fitterman et al. | Sep 1999 | A |
5963137 | Waters, Sr. | Oct 1999 | A |
5974389 | Clark et al. | Oct 1999 | A |
5991728 | DeBusk et al. | Nov 1999 | A |
5995937 | DeBusk et al. | Nov 1999 | A |
6014633 | DeBusk et al. | Jan 2000 | A |
6037723 | Shafer et al. | Mar 2000 | A |
6057758 | Dempsey et al. | May 2000 | A |
6057782 | Koenig | May 2000 | A |
6067019 | Scott | May 2000 | A |
6076166 | Moshfeghi et al. | Jun 2000 | A |
6078261 | Davsko | Jun 2000 | A |
6085493 | DeBusk et al. | Jul 2000 | A |
6088362 | Turnbull et al. | Jul 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6097308 | Albert et al. | Aug 2000 | A |
6101644 | Gagneur et al. | Aug 2000 | A |
6111509 | Holmes | Aug 2000 | A |
6125350 | Dirbas | Sep 2000 | A |
6133837 | Riley | Oct 2000 | A |
6147592 | Ulrich et al. | Nov 2000 | A |
6183417 | Geheb et al. | Feb 2001 | B1 |
6208250 | Dixon et al. | Mar 2001 | B1 |
6241668 | Herzog | Jun 2001 | B1 |
6259355 | Chaco et al. | Jul 2001 | B1 |
6264614 | Albert et al. | Jul 2001 | B1 |
6272347 | Griffith et al. | Aug 2001 | B1 |
6279183 | Kummer et al. | Aug 2001 | B1 |
6287253 | Ortega et al. | Sep 2001 | B1 |
6302844 | Walker et al. | Oct 2001 | B1 |
6314556 | DeBusk et al. | Nov 2001 | B1 |
6320510 | Menkedick et al. | Nov 2001 | B2 |
6344794 | Ulrich et al. | Feb 2002 | B1 |
6348777 | Brown et al. | Feb 2002 | B1 |
6362725 | Ulrich et al. | Mar 2002 | B1 |
6364834 | Reuss et al. | Apr 2002 | B1 |
6398727 | Bui et al. | Jun 2002 | B1 |
6406426 | Reuss et al. | Jun 2002 | B1 |
6407335 | Franklin-Lees et al. | Jun 2002 | B1 |
6412980 | Lounsberry et al. | Jul 2002 | B1 |
6416471 | Kumar et al. | Jul 2002 | B1 |
6421649 | Rattner | Jul 2002 | B1 |
6439769 | Polkus et al. | Aug 2002 | B1 |
6441742 | Lovely et al. | Aug 2002 | B1 |
6442290 | Ellis et al. | Aug 2002 | B1 |
6445299 | Rojas, Jr. | Sep 2002 | B1 |
6450956 | Rappaport et al. | Sep 2002 | B1 |
6462656 | Ulrich et al. | Oct 2002 | B2 |
6483264 | Shafer et al. | Nov 2002 | B1 |
6486792 | Moster et al. | Nov 2002 | B1 |
6493568 | Bell et al. | Dec 2002 | B1 |
6494831 | Koritzinsky | Dec 2002 | B1 |
6510344 | Halpern | Jan 2003 | B1 |
6516324 | Jones et al. | Feb 2003 | B1 |
6526310 | Carter et al. | Feb 2003 | B1 |
6529164 | Carter | Mar 2003 | B1 |
6533453 | Heidsieck et al. | Mar 2003 | B1 |
6535576 | Vafi et al. | Mar 2003 | B2 |
6539393 | Kabala | Mar 2003 | B1 |
6544173 | West et al. | Apr 2003 | B2 |
6544174 | West et al. | Apr 2003 | B2 |
6551243 | Bocionek et al. | Apr 2003 | B2 |
6553105 | Chea, Jr. et al. | Apr 2003 | B2 |
6553106 | Gould et al. | Apr 2003 | B1 |
6554174 | Aceves | Apr 2003 | B1 |
6556630 | Brinsfield et al. | Apr 2003 | B1 |
6560224 | Kung et al. | May 2003 | B1 |
6560274 | Leitgeb et al. | May 2003 | B1 |
6572556 | Stoycos et al. | Jun 2003 | B2 |
6575901 | Stoycos et al. | Jun 2003 | B2 |
6581204 | DeBusk et al. | Jun 2003 | B2 |
6584182 | Brodnick | Jun 2003 | B2 |
6584454 | Hummel, Jr. et al. | Jun 2003 | B1 |
6585645 | Hutchinson | Jul 2003 | B2 |
6589170 | Flach et al. | Jul 2003 | B1 |
6593528 | Franklin-Lees et al. | Jul 2003 | B2 |
6594146 | Frangesch et al. | Jul 2003 | B2 |
6594519 | Stoycos et al. | Jul 2003 | B2 |
6600421 | Freeman | Jul 2003 | B2 |
6603494 | Banks et al. | Aug 2003 | B1 |
6609115 | Mehring et al. | Aug 2003 | B1 |
6616606 | Petersen et al. | Sep 2003 | B1 |
6622088 | Hood | Sep 2003 | B2 |
6640246 | Gary, Jr. et al. | Oct 2003 | B1 |
6643238 | Nakajima | Nov 2003 | B2 |
6650346 | Jaeger et al. | Nov 2003 | B1 |
6659947 | Carter et al. | Dec 2003 | B1 |
6665358 | Oldagiri | Dec 2003 | B1 |
6665385 | Rogers et al. | Dec 2003 | B2 |
6665820 | Frowein et al. | Dec 2003 | B1 |
6669630 | Joliat et al. | Dec 2003 | B1 |
6671547 | Lyster et al. | Dec 2003 | B2 |
6671563 | Engelson et al. | Dec 2003 | B1 |
6685633 | Albert et al. | Feb 2004 | B2 |
6689091 | Bui et al. | Feb 2004 | B2 |
6693514 | Perea, Jr. et al. | Feb 2004 | B2 |
6694367 | Miesbauer et al. | Feb 2004 | B1 |
6694509 | Stoval et al. | Feb 2004 | B1 |
6697765 | Kuth | Feb 2004 | B2 |
6707476 | Hochstedler | Mar 2004 | B1 |
6714913 | Brandt et al. | Mar 2004 | B2 |
6721818 | Nakamura | Apr 2004 | B1 |
6726634 | Freeman | Apr 2004 | B2 |
6727818 | Wildman et al. | Apr 2004 | B1 |
6731311 | Bufe et al. | May 2004 | B2 |
6731989 | Engleson et al. | May 2004 | B2 |
6740033 | Olejniczak et al. | May 2004 | B1 |
6749566 | Russ | Jun 2004 | B2 |
6751630 | Franks et al. | Jun 2004 | B1 |
6754545 | Haeuser et al. | Jun 2004 | B2 |
6754883 | DeBusk et al. | Jun 2004 | B2 |
6759607 | Engler | Jul 2004 | B2 |
6759959 | Wildman | Jul 2004 | B2 |
6763541 | Mahoney et al. | Jul 2004 | B2 |
6771172 | Robinson et al. | Aug 2004 | B1 |
6773396 | Flach et al. | Aug 2004 | B2 |
6778225 | David | Aug 2004 | B2 |
6781517 | Moster et al. | Aug 2004 | B2 |
6784797 | Smith et al. | Aug 2004 | B2 |
6788206 | Edwards | Sep 2004 | B1 |
6791460 | Dixon et al. | Sep 2004 | B2 |
6792396 | Inda et al. | Sep 2004 | B2 |
6801227 | Bocionek et al. | Oct 2004 | B2 |
6807543 | Muthya | Oct 2004 | B2 |
6825763 | Ulrich et al. | Nov 2004 | B2 |
6826578 | Brackett et al. | Nov 2004 | B2 |
6828992 | Freeman et al. | Dec 2004 | B1 |
6829796 | Salvatini et al. | Dec 2004 | B2 |
6830549 | Bui et al. | Dec 2004 | B2 |
6832199 | Kucek et al. | Dec 2004 | B1 |
6840117 | Hubbard, Jr. | Jan 2005 | B2 |
6847814 | Vogeleisen | Jan 2005 | B1 |
6864795 | Smith et al. | Mar 2005 | B2 |
6868256 | Dooley et al. | Mar 2005 | B2 |
6870484 | Brinsfield et al. | Mar 2005 | B1 |
6871211 | Labounty et al. | Mar 2005 | B2 |
6873884 | Brackett et al. | Mar 2005 | B2 |
6876303 | Reeder et al. | Apr 2005 | B2 |
6876985 | Kawanaka | Apr 2005 | B2 |
6885288 | Pincus | Apr 2005 | B2 |
6891909 | Hurley et al. | May 2005 | B2 |
6892083 | Shostak | May 2005 | B2 |
6904161 | Becker et al. | Jun 2005 | B1 |
6909995 | Shiraishi | Jun 2005 | B2 |
6912549 | Rotter et al. | Jun 2005 | B2 |
6915170 | Engleson et al. | Jul 2005 | B2 |
6925367 | Fontius | Aug 2005 | B2 |
6930878 | Brackett et al. | Aug 2005 | B2 |
6958706 | Chaco et al. | Oct 2005 | B2 |
6968375 | Brown | Nov 2005 | B1 |
6982639 | Brackett et al. | Jan 2006 | B2 |
6988989 | Weiner et al. | Jan 2006 | B2 |
6998986 | Smith | Feb 2006 | B2 |
7020921 | Wang | Apr 2006 | B2 |
7023821 | Wotherspoon et al. | Apr 2006 | B2 |
7038584 | Carter | May 2006 | B2 |
7053767 | Petite et al. | May 2006 | B2 |
7061396 | Conrad et al. | Jun 2006 | B1 |
7068143 | Doering et al. | Jun 2006 | B2 |
7071820 | Callaway | Jul 2006 | B2 |
7079036 | Cooper et al. | Jul 2006 | B2 |
7088235 | Carricut | Aug 2006 | B1 |
7092376 | Schuman | Aug 2006 | B2 |
7107642 | Wong et al. | Sep 2006 | B2 |
7138902 | Menard | Nov 2006 | B2 |
7151457 | Riley et al. | Dec 2006 | B2 |
7160133 | Karadimas et al. | Jan 2007 | B2 |
7248881 | Shostak | Jul 2007 | B2 |
7263669 | Denholm | Aug 2007 | B2 |
7275220 | Brummel et al. | Sep 2007 | B2 |
7290299 | Votel | Nov 2007 | B2 |
7292135 | Bixler et al. | Nov 2007 | B2 |
7299512 | Cavalier et al. | Nov 2007 | B2 |
7301451 | Hastings | Nov 2007 | B2 |
7307522 | Dawson | Dec 2007 | B2 |
7310541 | Shostak | Dec 2007 | B2 |
7319386 | Collins, Jr. et al. | Jan 2008 | B2 |
7333002 | Bixler et al. | Feb 2008 | B2 |
7336187 | Hubbard, Jr. et al. | Feb 2008 | B2 |
8046625 | Ferguson et al. | Oct 2011 | B2 |
20010050610 | Gelston | Dec 2001 | A1 |
20010051765 | Walker et al. | Dec 2001 | A1 |
20020014951 | Kramer et al. | Feb 2002 | A1 |
20020032583 | Joao | Mar 2002 | A1 |
20020044043 | Chaco et al. | Apr 2002 | A1 |
20020044059 | Reeder et al. | Apr 2002 | A1 |
20020067273 | Jaques et al. | Jun 2002 | A1 |
20020070867 | Conway et al. | Jun 2002 | A1 |
20020080037 | Dixon et al. | Jun 2002 | A1 |
20020101349 | Rojas, Jr. | Aug 2002 | A1 |
20020103674 | Reeder et al. | Aug 2002 | A1 |
20020151990 | Ulrich et al. | Oct 2002 | A1 |
20020173991 | Avitall | Nov 2002 | A1 |
20020186136 | Schuman | Dec 2002 | A1 |
20020196141 | Boone et al. | Dec 2002 | A1 |
20030010345 | Koblasz et al. | Jan 2003 | A1 |
20030028449 | Heinen et al. | Feb 2003 | A1 |
20030030569 | Ulrich et al. | Feb 2003 | A1 |
20030052787 | Zerhusen et al. | Mar 2003 | A1 |
20030074222 | Rosow et al. | Apr 2003 | A1 |
20030146835 | Carter | Aug 2003 | A1 |
20030149598 | Santoso et al. | Aug 2003 | A1 |
20030176798 | Simon | Sep 2003 | A1 |
20030179099 | Perea, Jr. et al. | Sep 2003 | A1 |
20030197614 | Smith et al. | Oct 2003 | A1 |
20030206116 | Weiner et al. | Nov 2003 | A1 |
20030212575 | Saalsaa et al. | Nov 2003 | A1 |
20030230469 | Engler | Dec 2003 | A1 |
20040064890 | Kim et al. | Apr 2004 | A1 |
20040158922 | Eberler et al. | Aug 2004 | A1 |
20040183681 | Smith | Sep 2004 | A1 |
20040183684 | Callaway | Sep 2004 | A1 |
20040186358 | Chernow et al. | Sep 2004 | A1 |
20040193449 | Wildman et al. | Sep 2004 | A1 |
20040222897 | Schuhmann et al. | Nov 2004 | A1 |
20040243446 | Wyatt | Dec 2004 | A1 |
20040249670 | Noguchi et al. | Dec 2004 | A1 |
20040261184 | Flick | Dec 2004 | A1 |
20050035862 | Wildman et al. | Feb 2005 | A1 |
20050055779 | Damewood | Mar 2005 | A1 |
20050076441 | Dominati et al. | Apr 2005 | A1 |
20050110617 | Kile et al. | May 2005 | A1 |
20050155149 | Pedersen | Jul 2005 | A1 |
20050170863 | Shostak | Aug 2005 | A1 |
20050206505 | Arcaria | Sep 2005 | A1 |
20050242946 | Hubbard et al. | Nov 2005 | A1 |
20060046579 | Karadimas et al. | Mar 2006 | A1 |
20060049936 | Collins et al. | Mar 2006 | A1 |
20060114854 | Wotherspoon et al. | Jun 2006 | A1 |
20060126560 | Wotherspoon et al. | Jun 2006 | A1 |
20060136265 | Summers et al. | Jun 2006 | A1 |
20060214786 | Bixler et al. | Sep 2006 | A1 |
20060220798 | Willis | Oct 2006 | A1 |
20060239195 | Camins et al. | Oct 2006 | A1 |
20060248221 | Hottel et al. | Nov 2006 | A1 |
20060267740 | Bixler et al. | Nov 2006 | A1 |
20070071114 | Sanderford, Jr. et al. | Mar 2007 | A1 |
20070135688 | Brown | Jun 2007 | A1 |
20070156456 | McGillin et al. | Jul 2007 | A1 |
20070210917 | Collins, Jr. et al. | Sep 2007 | A1 |
20070229249 | McNeal et al. | Oct 2007 | A1 |
20070237487 | Lin | Oct 2007 | A1 |
20070239484 | Around et al. | Oct 2007 | A1 |
20070257788 | Carlson et al. | Nov 2007 | A1 |
20080004904 | Tran | Jan 2008 | A1 |
20080015900 | Denholm | Jan 2008 | A1 |
20080018436 | Traughber et al. | Jan 2008 | A1 |
20080027754 | Auker et al. | Jan 2008 | A1 |
20090217080 | Ferguson et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
1 623 666 | Feb 2006 | EP |
250 769 | Apr 1926 | GB |
1-76197 | Mar 1989 | JP |
WO 9523378 | Aug 1995 | WO |
WO 9808203 | Feb 1998 | WO |
WO 02091297 | Nov 2002 | WO |
WO 2004036390 | Apr 2004 | WO |
Entry |
---|
Hill-Rom a Hillenbrand Industry, The COMposer® System Installation Manual, 2003. |
Hill-Rom a Hillenbrand Industry, The COMposer Communication System Service Manual, 1995. |
Hill-Rom a Hillenbrand Industry, COMLinx™ Enterprise Solutions Nurse Communication Module, User's Guide, 2000. |
European Search Report for EP 09 25 0419, dated Aug. 13, 2010, (7 pages). |
Partial European Search report from EP 09 25 0420 date Jun. 16, 2009. |
(Online) XP002530934 Hill-Rom Technical Brief, www.hill-rom/canada/PDF/144097.pdf :CONLinx Nurse Communication Module Technological Advances, Jul. 13, 2006, 4 pages. |
European Search Report for European Patent Application No. 12164812.5, dated Mar. 9, 2012, 8 pages. |
European Search Report for European Patent Application No. 12164815.8, dated Mar. 9, 2012, 8 pages. |
European Search Report for European Patent Application No. 12164817.4, dated Mar. 9, 2012, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20120017206 A1 | Jan 2012 | US |
Number | Date | Country | |
---|---|---|---|
61066877 | Feb 2008 | US | |
61066882 | Feb 2008 | US | |
61066883 | Feb 2008 | US | |
61066918 | Feb 2008 | US | |
61145306 | Jan 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12369818 | Feb 2009 | US |
Child | 13241461 | US |