CROSS-REFERENCED TO RELATED APPLICATION This is a non-provisional application of U.S. Provisional Application Ser. No. 60/623,706 filed Oct. 29, 2004.
FIELD OF THE INVENTION The present invention relates to the field of patient monitoring and/or treatment devices which may be connected to hospital local area networks (LANs), and more specifically, to patient monitoring and/or treatment devices which may be coupled to hospital LANs via more than one communications channel.
BACKGROUND OF THE INVENTION In hospital environments, patients often require continual monitoring with relatively short repetition intervals, even when the patient is being transported from one location in the hospital to another. Portable patient monitors have been developed which are battery operated and are able to travel with the patient to provide uninterrupted patient monitoring. Portable patient monitors may include electrodes attached to a patient to receive electrical signals representing physiological parameters of the patient. These parameters may be displayed on the portable patient device, but may also be supplied to a central location in the hospital where they may be displayed on a patient monitoring system, or stored in a patient medical record or a patient data repository.
In such a hospital environment, docking stations for portable devices are provided at fixed locations throughout the hospital, such as patient rooms, therapy rooms, operating rooms, and so forth. Such docking stations permit the batteries in the portable patient monitor to be recharged and also permit the portable patient monitor to be connected to the central location through a wired link from the docking station to the central location. It is also possible for the portable patient monitor to remain in communication with the docking station when undocked in proximity of the docking station. For example, the portable patient monitor may be undocked within a therapy room to allow the patient to exercise without the restraint of being attached to the docking station. When the patient is being moved from one location to another, the portable patient monitor may remain in communication with the central location wirelessly. To do this, wireless access points with associated antennae are located throughout the hospital, e.g. in hallways, elevators, etc.; wherever a patient may be transported from one room to another.
Thus, a portable patient monitor may include multiple channels for maintaining communication with the central location of the hospital. It is desirable that transitions between communications channels be handled properly so that continual monitoring may be maintained.
BRIEF SUMMARY OF THE INVENTION In accordance with principles of the present invention, a communication system is used by a portable patient monitoring device in connecting to a plurality of other devices, including a docking station suitable for attaching to the portable patient monitoring device. The portable patient monitoring device processes signal parameters acquired from a patient. The communications system includes an adaptive communication interface for automatically operating in a first mode of operation when the portable patient monitoring device is attached to the docking station. In the first mode of operation the portable patient monitor receives an identifier identifying a particular docking station via a first wireless communication link exclusively between the docking station and the portable patient monitoring device, in response to detecting the portable patient monitoring device is attached to the docking station. Patient parameters acquired via the first wireless communication link are communicated to a destination associated with the particular docking station identified by the received identifier. In a second mode of operation when the portable patient monitoring device is unattached to the docking station, the portable patient monitor establishes a second wireless communication link between the portable processing device and a network, in response to detecting the first communication link is non-operational. Patient parameters acquired via the second wireless communication link are communicated to a destination.
BRIEF DESCRIPTION OF THE DRAWING In the drawing:
FIG. 1 is a block diagram of respective communications channels between a portable patient monitor and a hospital central location;
FIG. 2 is a block diagram of a portable patient monitor and a docking station according to principles of the present invention; and
FIG. 3 is a flowchart useful in understanding the operation of the portable patient monitor and docking station illustrated inFIG. 2 according to principles of the present invention.
DETAILED DESCRIPTION OF THE INVENTION A processor, as used herein, operates under the control of an executable application to (a) receive information from an input information device, (b) process the information by manipulating, analyzing, modifying, converting and/or transmitting the information, and/or (c) route the information to an output information device. A processor may use, or comprise the capabilities of, a controller or microprocessor, for example. The processor may operate with a display processor or generator. A display processor or generator is a known element for generating signals representing display images or portions thereof. A processor and a display processor comprises any combination of, hardware, firmware, and/or software.
An executable application, as used herein, comprises code or machine readable instructions for conditioning the processor to implement predetermined functions, such as those of an operating system, remote patient monitoring system or other information processing system, for example, in response to user command or input. An executable procedure is a segment of code or machine readable instruction, sub-routine, or other distinct section of code or portion of an executable application for performing one or more particular processes. These processes may include receiving input data and/or parameters, performing operations on received input data and/or performing functions in response to received input parameters, and providing resulting output data and/or parameters.
FIG. 1 is a block diagram of respective communications channels between aportable patient monitor20 and a hospitalcentral location15. InFIG. 1, a hospitalcentral location15 includes apatient data repository40, a patientmedical record50 and apatient monitoring system60 coupled together via a local area network (LAN)5. TheLAN5 is also coupled to a plurality of patient area networks (PAN)70, which are described in more detail below. TheLAN5 is also coupled to anaccess point80.
A patient area network (PAN)70 may include a plurality of patient monitoring and/or treatment devices which are coupled together via a network. Typically,PANs70 are located in fixed locations in the hospital where diagnosis, monitoring and treatment of a patient may be performed, such as in a patient room a therapy room, an operating room, a diagnostic test room (e.g. X-ray, CAT scan, etc.), and so forth. Therespective PANs70 are assigned a unique identifier which is used to identify messages to and from thePAN70. The unique identifier may also be used to determine a geographical location of the PAN70.
At the top left ofFIG. 1, a particular PAN70 is illustrated in more detail. In thisPAN70, apatient90 has sensors (not shown) attached to him to generate various signals which may be processed to derive physiological parameters of that patient, such as (a) electrocardiograph (ECG) data, (b) blood parameter data, (c) ventilation parameter data, (d) infusion pump related data, (e) blood pressure data, (f) pulse rate data, and (g) temperature data. These signals are coupled to a portablepatient monitor device20. The portablepatient monitor device20 includes circuitry for processing these signals to generate patient physiological parameters, and a display screen for displaying the physiological parameters for a clinician. The portablepatient monitor device20 may be physically and electrically coupled to adocking station10. Thedocking station10 is coupled to apatient monitor processor30. Thepatient monitor30 may provide processing capabilities beyond what the portablepatient monitor device20 alone has, and also includes a link, termed a bridge, between the PAN70 and theLAN5. This permits thepatient monitor processor30 to access data at thecentral location15 and to display this data on thepatient monitor30.
In operation, the destination of the patient physiological parameter data from the portablepatient monitor device20 is thecentral location15. Also, because the unique identifier identifying the network node sending the patient physiological parameter data to thecentral location15 is associated with adocking station10, and because the geographical location of thedocking station10 is known, the unique identifier enables determination of the geographical location of thedocking station10. A map may be maintained in thecentral location15 associating the identifier with a geographical location. Thecentral location15 may display the patient physiological parameter data on thepatient monitoring system60. This permits the medical status of one or more patients to be monitored at a single location. The patient physiological parameter data may also be stored in a patientmedical record50. This data may be reviewed by a physician or other clinician as part of a diagnosis or treatment process. The patient physiological parameter data may also be stored in apatient data repository40, providing for longer term storage and retrieval of patient data.
When thedocking station10 detects that the portablepatient monitor device20 has been docked, it initiates a first mode of operation. In this mode of operation, the portablepatient monitor device20 is configured to connect to theLAN5 via thedocking station10 and thepatient monitor processor30, in a manner described in more detail below. This mode of operation may continue even if the portablepatient monitor device20 is undocked from thedocking station10. This is illustrated in phantom inFIG. 1. If the portablepatient monitor device20 remains in relative proximity to thedocking station10, then a wireless link may be maintained between the portablepatient monitor device20 and thedocking station10, allowing the portablepatient monitor device20 to continue to communicate with thecentral location15 via thedocking station10 and thepatient monitor processor30.
At the bottom left ofFIG. 1, awireless access point80 is coupled to theLAN5. Typically, thewireless access points80 are located at locations in the hospital where patients may be transported, but which are not in fixed locations where adocking station10 andpatient monitor processor30 may be placed, such as a hallway, elevator, and so forth. A portablepatient monitor device20 is illustrated as being connected to apatient90. In this case, the portablepatient monitor device20 is not in close proximity to adocking station10 orpatient monitor processor30. The portablepatient monitor device20 includes a wireless link which may connect to theLAN5 via thewireless access point80. In this situation, the portablepatient monitor device20 is configured to operate in a second mode of operation. In this mode of operation, the portablepatient monitor device20 communicates patient physiological parameter data to thecentral location15 via theLAN5.
FIG. 2 is a block diagram of a portablepatient monitor device20 and adocking station10 according to principles of the present invention. InFIG. 2, those elements which are the same as those illustrated inFIG. 1 are designated by the same reference number. InFIG. 2, a source of electrical power (not shown) is coupled to a power input terminal (PWR IN) of adocking station10. The power input terminal is coupled to respective input terminals of aload sense circuit13 and a modulator/demodulator (modem)16. An output terminal of themodem16 is coupled to an input terminal of apower coupler15. A bidirectional Ethernet link is coupled to a network connection (not shown), such as theLAN5, or toLAN5 via a patient monitor processor30 (also not shown). The Ethernet link is coupled to a first communication terminal of aninterface processor25. A second communication terminal of theinterface processor25 is coupled to an optical link, e.g.optical driver17 andoptical receiver19. A third communications terminal is coupled to a PAN RF link109. A fourth communications terminal is coupled to themodem16. A first control input terminal is coupled to an output terminal of theload sense circuit13. A second control input terminal is coupled to asource14 of a unique identifier. A radio frequency identification (RFID)tag115 is also located on thedocking station10. TheRFID tag115 may be passive, requiring no power, or active, requiring power for operation.
The portablepatient monitor device20 includes apower coupler39. An output terminal of thepower coupler39 is coupled to respective input terminals of aload sense circuit25 and amodem24. An output terminal of themodem24 is coupled to abattery charger37. The battery charger is coupled to abattery43. Adata acquisition unit50 is coupled to a plurality of patient attachable electrodes (not shown) which may be attached to a patient to generate electrical signals representing patient physiological parameter data. An output terminal of thedata acquisition unit50 is coupled to an input terminal of aprocessor35. An output terminal of theprocessor35 is coupled to an input terminal of adisplay unit45. A bidirectional communications terminal of theprocessor35 is coupled to a first communications terminal of anadaptive communications interface33. A second communications terminal of theadaptive communications interface33 is coupled to aLAN RF link107. A third communications terminal is coupled to a PAN RF link111. A fourth communications terminal is coupled to an optical link, e.g.optical driver21 andoptical receiver23. A fifth communications terminal is coupled to themodem24. A sixth communications terminal is coupled to anRFID tag reader113. A control input terminal of theadaptive communications interface33 is coupled to an output terminal of theload sense circuit25 and a bidirectional control terminal of theadaptive communications interface33 is coupled tostorage34 for a unique identifier.
In operation, the portablepatient monitor device20 may be docked in thedocking station10. In this configuration, illustrated inFIG. 2, thepower couplers15 and39 are physically aligned to pass power from thedocking station10 to the portablepatient monitor device20. For example, thepower couplers15 and39 may be a split transformer in which the primary winding is in thepower coupler15 and the secondary winding is in thepower coupler39. When docked, the primary winding15 and secondary winding39 are magnetically coupled so that power is transferred from thedocking station10 to the portablepatient monitor device20. In the portablepatient monitor device20, thebattery charger37 receives power from thepower coupler39, recharges thebattery43 and maintains it at full charge.
Thedocking station10 may detect that the portablepatient monitor device20 is docked by sensing the status of the signal at the power input terminal. For example, when the portablepatient monitor device20 is docked, the current through the power input terminal will be higher than when the portablepatient monitor device20 is undocked. Theload sense circuit13 monitors the signal on the power input terminal and generates a control signal ‘Docked’ indicating that the portablepatient monitor device20 is docked to thedocking station10. In a similar manner, theload sense circuit25 in the portablepatient monitor device20 may also detect when it is docked to thedocking station10. Alternatively, theadaptive communications interface33 in the portablepatient monitor device20 may detect that it is docked to thedocking station10 by detecting that an active communication link is present between thedocking station10 and the portablepatient monitor device20.
When the portablepatient monitor device20 is docked, the optical link in thedocking station10, e.g.optical driver17 andoptical receiver19, is physically aligned with the optical link in the portablepatient monitor device20, e.g.optical receiver23 andoptical driver21 respectively. When aligned, it is possible for theinterface processor25 in thedocking station10 to communicate with theadaptive communications interface33 in the portablepatient monitor device20 via the optical link. Because it is an optical link, this communications link may not receive signals from another location. That is, it is a wireless link which exists exclusively between thedocking station10 and the portablepatient monitor device20.
When the portablepatient monitor device20 is docked to thedocking station10, themodem16 in thedocking station10 may be configured to receive data from the interface,processor25 and to modulate the amplitude and/or frequency of the power input signal with that data. Themodem24 in the portablepatient monitor device20 demodulates data received from theinterface processor25 via themodem16 in thedocking station10, and supplies that data to theadaptive communications interface33. Correspondingly, themodem24 in the portablepatient monitor device20 may be configured to receive data from theadaptive communications interface33 and modulate the amplitude and/or frequency of the power input signal with that data. Themodem16 in thedocking station10 demodulates data received from theadaptive communications interface33 in the portablepatient monitor device20 via themodem24, and supplies that data to theinterface processor25. Because this is a magnetically coupled link, this communications link, too, may not receive signals from another location. Thus, it, also, is a wireless link which exists exclusively between thedocking station10 and the portablepatient monitor device20.
Theinterface processor25 in thedocking station10 may communicate with theadaptive communications interface33 in the portablepatient monitor device20 via thePAN wireless link109,111. This link may be activated when the portablepatient monitor device20 is docked to thedocking station10 and may remain activated when it is not docked. This link is implemented as an RF link, and thus is subject to receiving signals from other locations. However, the power in the RF link may be constricted so that the range of operation of this link is limited. More specifically, in the illustrated embodiment, the typical range of operation of this link is approximately the size of a room, such as a patient room, operating room, therapy room, etc. However, the power in this link may be controlled so that when the portablepatient monitor device20 is docked, the power is constricted to be low enough that the range of operation is only several inches. In this way, while possible, it is improbable that a signal will be received from another location. Thus, in practical terms, this wireless link exists exclusively between thedocking station10 and the portablepatient monitor device20.
When the portablepatient monitor device20 is attached to thedocking station10, theadaptive communications interface33 initiates a first mode of operation using a first wireless link. In the first operational mode the portablepatient monitor device20 communicates patient physiological parameter data to a first destination. For example, the portablepatient monitor device20 may send patient physiological parameter data to the patient monitor processor30 (FIG. 1) via thedocking station10. Thepatient monitor processor30 may include a display device larger than the display device on the portablepatient monitor device20 and further processing power. This enables thepatient monitor processor30 to display more sophisticated patient physiological parameter data than possible by the portablepatient monitor device20 alone. Further, thepatient monitor processor30 may communicate with thecentral location15, enabling it to retrieve data from thecentral location15, such as X-ray images, or laboratory test results and display them for the clinician. Alternatively, the portablepatient monitor device20 may send patient physiological parameter data to thecentral location15 via thedocking station10,patient monitor processor30 andLAN5. Referring again toFIG. 1, as described above, at the central location, the patient physiological parameter data may be sent to (a) anelectronic patient record50, (b) apatient monitoring system60, and/or (c) apatient data repository40.
In order to send and receive messages over theLAN5 via the Ethernet link from thedocking station10, the portablepatient monitor device20 uses a unique identifier associated with thedocking station10. This identifier may be: (a) an Ethernet compatible MAC address, (b) an IP address, (c) a port identifier, (d) an Internet compatible address and/or (e) a LAN address. Messages sent from the portablepatient monitor device20 include this unique identifier to identify the network node which sent the message. The unique identifier associated with the portablepatient monitor device20 is derived from thedocking station10 to which it is docked.
In order to ensure that the unique identifier assigned to the portablepatient monitor device20 comes from thedocking station10 to which it is docked, the communications channel used to transmit this data is exclusive between thedocking station10 and the portablepatient monitor device20. The unique identifier may be communicated from thedocking station10 to the portablepatient monitor device20 using one of the three wireless links discussed above: (a) theoptical link17,19,21,23; (b) themagnetic link15,16,24,39; or (c) the PAN RF link109,111, with constricted power. More specifically, in the illustrated embodiment, theinterface processor25 in thedocking station10 retrieves the unique identifier from theidentifier source14. Theinterface processor25 then establishes one of the communication links described above, and sends the identifier representative data to theadaptive communications interface33 in the portablepatient monitor device20. Theadaptive communications interface33 receives the identifier representative data and stores it in theidentifier store34.
Alternatively, theRFID tag115 in thedocking station10 may be encoded to return data representing the unique identifier associated with thedocking station10 when queried. Theadaptive communications interface33 may activate theRFID tag reader113 to query theRFID tag115 in thedocking station10 to retrieve the unique identifier. When queried, theRFID tag115 in thedocking station10 returns a signal carrying the unique identifier representative data to theRFID tag reader113. Theadaptive communications interface33 receives this signal from theRFID tag reader113 and stores data representing the unique identifier in theidentifier store34.
One skilled in the art understands that other information may also be stored in theidentifier store34. For example: (a) an identifier associated with aprevious docking station10 to which the portablepatient monitor device20 was docked prior to thecurrent docking station10, (b) information representing the time a portablepatient monitor device20 is docked in adocking station10 and undocked from that docking station10 (e.g. time stamps), and/or (c) other information derived using the identifier associated with said previous docking station may also be stored in theidentifier store34.
In subsequent communications with the patient monitor processor30 (FIG. 1) or thecentral location15 via the Ethernet link, theadaptive communications interface33 uses the unique identifier. More specifically, in the illustrated embodiment, after the unique identifier has been received by the portablepatient monitor device20, the portablepatient monitor device20 communicates acquired patient parameters from thedata acquisition unit50 via the first wireless communication link to the first destination e.g.patient monitor processor30 and/or thecentral location15 associated with the particular docking station identified by the unique identifier. More specifically, in the illustrated embodiment, theadaptive communication interface33 supports communication via the Ethernet link in thedocking station10 using wireless technologies including at least one of, (a) WLAN 802.11b standard compatible communication, (b) 802.11a standard compatible communication, (c) 802.11g standard compatible communication, (d) Bluetooth802.15 standard compatible communication, (e) GSM/GPRS standard compatible communication, (f) UWB standard compatible communication 802.15.3, and (g) RFID sensing. (The 802.11 standard compatible communications links are sometimes termed WiFi communications links.) Referring again to the bottom left-hand portion ofFIG. 1, apatient90 may also be monitored by an undocked portablepatient monitor device20 outside of aPAN70. When the portablepatient monitor device20 is not attached to, or in communication with, adocking station10, the portablepatient monitor device20 operates in a second mode of operation. In this mode of operation, the portablepatient monitor device20 establishes a second wireless link to thenetwork LAN5. This mode of operation may be established when it is detected that the first more of operation, described above, becomes non-operational. In this mode of operation, the portablepatient monitor device20 communicates patient physiological parameter data to a second destination via the second wireless link. More specifically, in the illustrated embodiment, the second destination may be thecentral location15, where the data may be supplied to thepatient record50, thepatient monitoring system60 and/or thepatient data repository40. This second destination may be the same as the first destination, or may be different.
Referring again toFIG. 2, theadaptive communications interface33 includes circuitry which may monitor the status of established communications links. Specifically, theadaptive communications interface33 may detect when a communications link becomes non-operational. For example, a status signal from a link, e.g.optical link21,23, PAN RF link111 or themodem24, may indicate that the link has become non-operational. When it is detected that the first communications link is non-operational, theadaptive communications interface33 conditions the LAN RF link107 to attempt to connect to theLAN5 via anaccess point80. In this manner, patient physiological parameter data may be continually supplied from the portablepatient monitor device20 to thecentral location15 even if the portablepatient monitor device20 is undocked from thedocking station10 and removed from the vicinity of thePAN70. One skilled in the art understands that the LAN RF link107 has a relatively longer range than thePAN RF LINK111.
It is also possible for a portablepatient monitor device20 to be returned to aPAN70 from which it was removed, as when a patient returns from a diagnostic testing room to the patient room. The portablepatient monitor device20 may then be redocked in thedocking station10. In this case, communications may be reestablished using the wireless links described above. The manner of transitioning among (a) a communications link used when a portablepatient monitor device20 is docked in adocking station10, (b) a communications link used when the portablepatient monitor device20 is undocked but is within range of aPAN70, and (c) a communications link used when a portablepatient monitor device20 is undocked, is not within range of aPAN70 but is within range of theLAN5, is described in more detail below.
FIG. 3 is a flowchart useful in understanding the operation of the portable patient monitor20 anddocking station10 illustrated inFIG. 2 according to principles of the present invention, during the transitions. In the following description, reference will be made to bothFIG. 2 andFIG. 3.FIG. 3 begins instep302 when the portablepatient monitor device20 is not operating within range of aPAN70. This may, for example, occur when a portablepatient monitor device20 is initially powered on and attached to a patient, or when it is operating within range of theLAN5 but not within range of aPAN70. Instep304, the portablepatient monitor device20 determines if it has been docked in adocking station10. This may be determined via theload sense circuit25 as described above. Instep306, the unique identifier for thePAN70 is retrieved from thedocking station10 using a first communications link (e.g. optical link, magnetic link, PAN RF link or RFID link), as described above. In step308, the portablepatient monitor device20 establishes Ethernet communications with thepatient monitor processor30 via thedocking station10. Patient physiological parameter data from thedata acquisition unit50 are supplied to the first destination (patient monitor processor30 and/or central location15) via the first communications link (e.g. optical link, magnetic link, or PAN RF link).
Instep310, the portablepatient monitor device20 monitors whether it is still docked. This may be done by theload sense circuit25. If the portablepatient monitor device20 remains docked, it maintains the first communications link established in step308. If the portablepatient monitor device20 becomes undocked, then communications with thePAN70 is maintained, possibly using a different communications link. This may occur if the portablepatient monitor device20 is undocked from thedocking station10, but remains within the patient room. In this case, instep312, theadaptive communications interface33 activates the PAN RF link109,111 if it is not already active. The transmission power of the PAN RF link109,111 in this mode of operation is substantially higher than the constricted power used by the PAN RF link109,111 when the portablepatient monitor device20 is docked in thedocking station10. This enables a transmission range sufficient to cover the patient room. Patient physiological parameter data from thedata acquisition unit50 is communicated over the PAN RF link109,111, with substantially higher power, to thepatient monitor processor30 and/or thecentral location15 via thedocking station10.
In general, a portablepatient monitor device20 will attempt to remain in communication with thePAN70 containing thedocking station10 from which it received the unique identifier as long as it remains within range. Instep314 theadaptive communications interface33 in the portablepatient monitor device20 monitors communication with thedocking station10. So long as the portablepatient monitor device20 remains within range of thedocking station10, the portablepatient monitor device20 communicates with thedocking station10 using the PANRF communication link109,111 instep312.
If, however, the PAN RF link109,111 becomes inoperative, e.g. because the portablepatient monitor device20 goes out of range, then in step316 theadaptive communications interface33 activates theLAN RF link107, establishing a second communications link between the portablepatient monitor device20 and theLAN5. The patient physiological parameter data from thedata acquisition unit50 is supplied to thecentral location15 via theLAN5 in this mode of operation. As described above, this may occur when a patient is removed from the patient room and taken to e.g. an operating room, diagnostic testing room, therapy room, etc., though the hospital.
The LAN RF link107 is maintained so long as the portablepatient monitor device20 remains within range of theLAN5 and out of range of aPAN70. Because of the varying ranges of PAN RF communication links in therespective PANs70, the portablepatient monitor device20 may come within range of a PAN RF link during transportation of the patient in the hospital, and/or when the patient arrives at the final destination, if that destination contains aPAN70. Instep318 theadaptive communications interface33 determines (a) that the portablepatient monitor device20 is within range of a PAN, and (b) whether the identifier stored in theidentifier store34 matches the identifier of the PAN RF link currently within range, i.e. is the same PAN from which the portablepatient monitor device20 was undocked.
Theadaptive communications interface33 is inhibited from establishing communication with aPAN70 which fails to provide the previously received unique identifier unless the portablepatient monitor device20 is docked. If adifferent PAN70 is detected, then instep322 theadaptive communications interface33 in the portablepatient monitor device20 monitors whether the portablepatient monitor device20 is docked. If the portablepatient monitor device20 is docked in the newly enteredPAN70, communication is established between the portablepatient monitor device20 and thenew PAN70 e.g. using the optical link, magnetic link, PAN RF link at constricted power, or RFID link. Instep306 the unique identifier associated with thedocking station10 in thenew PAN70 is retrieved, and in step308 communications between the portablepatient monitor device20 and thedocking station10 established. Patient physiological parameter data from thedata acquisition unit50 is sent to thepatient monitor processor30 orcentral location15 via thedocking station10 in thenew PAN70.
If instep318 the same PAN is detected, as may happen if the patient is returned to the patient room from which he was originally taken, then in step320 theadaptive communications interface33 in the portablepatient monitor device20 activates the PAN RF link109,111, with substantially higher power. This reestablishes the first communications link with thedocking station10. In this case, patient physiological parameter data from thedata acquisition unit50 is sent to thepatient monitor processor30 orcentral location15 through thedocking station10 via the PAN RF link109,111. Instep314, theadaptive communications interface33 in the portablepatient monitor device20 monitors the PAN RF link109,111 to detect if the portablepatient monitor device20 goes out of range.
The embodiment above is described as having multiple communications links available, e.g five links: (1)optical link17,19,21,23; (2)magnetic link15,16,24,39; (3) PAN RF link109,111; (4)LAN RF link107; and (5)RFID link113,115. One skilled in the art, however, understands that different combinations of communication links may be available in the portablepatient monitor device20 anddocking station10.
For example, in another configuration, the portablepatient monitor device20 may have three links: (1) a short-range wireless PAN link e.g. theoptical link17,19,21,23, used by thedocking station10 to communicate the unique identifier to the portablepatient monitor device20 and by the portablepatient monitor device20 to communicate patient physiological parameter data to thepatient monitor processor30 and/orcentral location15 via thedocking station10 when it's docked; (2) a short-range wirelessRF PAN link109,111 used by the portablepatient monitor device20 to communicate patient physiological parameter data to thepatient monitor processor30 and/orcentral location15 via thedocking station10 when it's undocked but within thePAN70; and (3) a longer-range wireless link used by the portablepatient monitor device20 to communicate patient physiological parameter data to thecentral location15 via theLAN5 when it's undocked and not within thePAN70.
Another exemplary configuration includes two links: (1) a short-range wirelessRF PAN link109,111 used by thedocking station10 to communicate the unique identifier to the portablepatient monitor device20 in a constricted power mode, and by the portablepatient monitor device20 to communicate patient physiological parameter data to thepatient monitor processor30 and/orcentral location15 when it's within range of thedocking station10; and (2) a longer-range wireless link used by the portablepatient monitor device20 to communicate patient physiological parameter data to thecentral location15 via thedocking station10 when it's undocked and not within thePAN70.
Another exemplary configuration includes a single link: a wireless link for communicating between the portablepatient monitor device20 and thedocking station10. That is, the first and second wireless communication links are the same link used in different first and second communication modes. In this case, the single link may operate in two different operational modes. For example, a Bluetooth RF link may operate in a very low power mode when the portablepatient monitor device20 is communicating with thedocking station10 within aPAN70, and in a high power mode when communicating directly with theLAN5. Alternatively, the single link may be a WiFi (802.11 standard) communications link which operates in the “ad-hoc” mode when communicating with thedocking station10 within a PAN and in “station” mode when communicating directly to theLAN5.
In this manner, theadaptive communications interface33 in the portablepatient monitor device20 automatically, and without user intervention, remains in continual communication with either thepatient monitor processor30 in thePAN70 and/or with thecentral location15 via theLAN5. Once associated with aparticular PAN70 by receiving and using the unique identifier associated with thatPAN70, it communicates through thatPAN70 as long as it remains within range. Otherwise it communicates with theLAN5.