Method for establishing a telecommunications network for patient monitoring
Claim Score by NHIP
Abstract
A wireless network having an architecture that resembles a peer-to-peer network has two types of nodes, a first sender type node and a second receiver/relay type node. The network may be used in a medical instrumentation environment whereby the first type node may be wireless devices that could monitor physical parameters of a patient such as for example wireless oximeters. The second type node are mobile wireless communicators that are adapted to receive the data from the wireless devices if they are within the transmission range of the wireless devices. After an aggregation process involving the received data, each of the node communicators broadcasts or disseminates its most up to date data onto the network. Any other relay communicator node in the network that is within the broadcast range of a broadcasting communicator node would receive the up to date data. This makes it possible for communicators that are out of the transmitting range of a wireless device to be apprized of the condition of the patient being monitored by the wireless device. Each communicator in the network is capable of receiving and displaying data from a plurality of wireless devices.

Term
Projected expiry 18 November 2028.
- Priority and filed
- Published
- Today
- Projected expiry
21 claims: 3 independent, 18 dependent
- 1Broadest claimClaim Score 55, average(NHIP)In a wireless communications network having a plurality of transmitting and receiving devices, a method of conveying information relating to physical attributes of a patient remotely, comprising the steps of:a) associating at least one wireless sensor device with a patient for detecting at least one physical attribute of the patient, said sensor device including at least a transmitter;b) transmitting patient data corresponding to the detected physical attribute out onto the network;c) locating a first communicator within transmission range of said sensor device, said first communicator having a transceiver adapted to receive the patient data transmitted from said sensor device;d) broadcasting from said first communicator the received patient data out onto the network;and e) establishing communication between at least a second communicator and said first communicator, said second communicator not in direct communication with said wireless sensor device, said second communicator having a second transceiver adapted to receive the patient data broadcast by said first communicator.
- 11In a wireless network having a plurality of nodes, a method for disseminating information of a patient, comprising the steps of:a) associating at least one first type node with the patient for monitoring physical attributes of the patient, said first type node including a detector that detects at least one physical attribute of the patient and a transmitter that transmits the detected physical attribute as patient data out to the network;b) locating a plurality of second type nodes not directly associated with the patient in the network, each of said second type nodes adapted to receive signals and/or data from said first type node when moved to within broadcast range of said first type node, each of said second type nodes further adapted to receive signals and/or data from other second type nodes and to broadcast signals and/or data out to the network;c) moving one of said second type nodes to within the broadcast range of said first type node to receive the patient data output from said first type node;and d) broadcasting from said one second type node the received patient data out to the network so that any other second type node located within broadcast range of said one second type node could receive the patient data output by said first type node.
- 16In a wireless network having a plurality of nodes, a method for disseminating information of a patient, comprising the steps of:a) associating each of multiple first type nodes with a particular patient for monitoring physical attributes of the particular patient, said each first type node including a detector that detects at least one physical attribute of the particular patient and a transmitter that transmits the detected physical attribute as patient data out to the network;b) positioning in the network a plurality of second type nodes not directly associated with any patient;c) configuring each of said second type nodes to receive signals and/or data from said first type nodes when moved to within broadcast range of any of said first type nodes, and to receive signals and/or data from other second type nodes and broadcast signals and/or data out to the network;d) locating one of said second type nodes to within the broadcast range of any said first type node to receive the patient data output from said any first type node;and e) broadcasting thereafter from said one second type node the received patient data out to the network so that any other second type node located within the broadcast range of said one second type node could receive the patient data output by said any first type node.
Independent claims3
112 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
p-0002The present invention relates to a wireless telecommunications network that may be used in the medical industry, and more particularly relates to a nodal network that has a plurality of node communicators for conveying patient parameters remotely from the site where the patient is being monitored. Also disclosed are inventions that relate to the method of remotely conveying or propagating patient information along the network and the devices used in such wireless telecommunications network.
BACKGROUND OF THE INVENTION
p-0003To remotely monitor physical parameters, for example blood pressure, arterial oxygen blood saturation (SP02), heart rate, electrocardiogram, etc., of a patient, a sensor is usually attached to the patient, with the sensor being connected to a transmitter that transmits the patient signals to a central nursing station. Such transmission is usually by hardwire, and more recently wirelessly. At the nursing station, which may either be located in the general ward or in an intensive care unit (ICU) of a hospital, a number of monitors are provided to monitor the patients in the various rooms. There is always a nurse at the nursing station who monitors the physical parameters of the different patients that are being transmitted from the various patient rooms, in order to observe the physical well-being of the patients. Such central nursing station works well in an environment whereby the patients are confined to their respective rooms, with each of the rooms containing the appropriate transmitter for transmitting the physical parameters sensed by the sensor(s) connected to the respective patients.
p-0004There is however a trend in the medical field to incorporate wireless communications to provide mobility for the patient. In the medical field, for example in the area of pulse oximetry, one such portable device is a finger oximeter with remote telecommunications capabilities that is disclosed in U.S. Pat. No. 6,731,962, assigned to the assignee of the instant application. The disclosure of the '962 patent is incorporated by reference herein. The '962 device is adaptable to transmit patient data to a remote receiver or monitor. Another pulse oximeter that is capable of communicating with an external oximeter via a wireless communications link is disclosed in patent publication 2005/0234317. The remote device for this oximeter is a display. Another wireless pulse oximeter is disclosed in patent publication 2005/0113655. There a wireless patient sensor would transmit raw patient data to a pulse oximeter that processes the data and further configures the data to generate a web page, which is then transmitted wirelessly to a wireless access point, so that the web page may be downloaded by remote monitoring stations that are connected by means of a network to the access point. Another system that remotely monitors the conditions of a patient is disclosed in patent publication 2004/0102683. The '683 publication discloses a patient monitoring device worn by the patient. The patient data collected from the patient is transmitted wirelessly to a local hub. The hub then transfers the data to a remote server by way of a public or private communications network. The server is configured as a web portal so that the patient data may be selectively accessed by physicians or other designated party that are allowed to view the patient's data.
p-0005The current systems therefore are focused to the transmitting of patient data to a remote hub or access point and are therefore confined to a specific site from which the patient data may be reviewed remotely. The network or communications link that are currently used are thus either predefined links that transmit information in a particular communications path, or by means of public communications network with a particular server from which selective access may be granted. Yet all of these prior art system are not particularly suited to the above mentioned hospital environment in which there is a need to provide mobility for the patients, as well as the need to monitor the multiple patients. Moreover, there is a need to un-tether the patient from the monitor that is fixed to the room of the patient to provide the patient more mobility, and yet at the same time, allows the care-giver(s) to continue to monitor the physical well being of the patient.
p-0006There is therefore a need for a portable device that may be worn by a patient which can wirelessly transmit data collected from a patient.
p-0007Further, given the shortage of care-givers, there is a need to reduce the requirement for a particular nurse or care-giver to be stationed at for example a central nursing station, in order to monitor the physical parameters of the various patients. It may also be advantageous to have more than one care-giver who could monitor the different physical parameters of the various patients. It follows then that there is also a need to enable a nurse or care-giver, or a number of nurses or care-givers or other healthcare personnel, to be able to monitor remotely in substantially real time the physical well being of a patient, and/or the various patients in this communications network. To that end, There is a need for a communications network that could receive the data collected from the various patients, and at the same time correlate the different data collected with the various patients. To fully enable the remote monitoring capabilities of the network, a need therefore also arises for a portable device to be carried by each care-giver to thereby un-tether the care-giver(s) from any particular central monitoring location.
BRIEF SUMMARY OF THE PRESENT INVENTION
p-0008The present invention, among its multiple aspects which may themselves constitute self standing inventions, attempts to overcome the need for a central server or hub to which the data collected from the patient is routed, per taught by the prior art. The present invention therefore aims to, in the one aspect, provide remote monitoring across a network, for example a peer-to-peer network or a mesh network with a deterministic configuration, so that there is no reliance on a single hub or access point.
p-0009The present invention, in one aspect, more particularly relates to a wireless communications network that is adapted for use by medical devices and that has an architecture that may be in the form of a peer-to-peer network of medical devices without a network controller. Each of the medical devices may be considered a node of the network, with the medical devices or nodes being time synchronized and the communications among the devices scheduled, to thereby eliminate in network interference and allow good quality both in terms of the communications among the nodes and the types of messages disseminated among the devices.
p-0010In an embodiment of the instant invention set in an exemplar medical environment, for example oximetry, a patient whose physiological parameters or attributes are to be measured has attached to him or her a sensor module that has a sensor to measure the physical parameters of the patient. The obtained patient data may be routed by the sensor to a transmitter for transmission. Alternatively, the sensor module may in itself contain a transmitter for transmitting the measured physical parameters of the patient. A transceiver may also be provided in the sensor module in the event that bidirectional communications between the sensor module and a remote receiver is desired. The sensor module may be referred to, in the being discussed medical environment, as a wireless oximeter sensor. Each of the wireless oximeter sensor may include an oximeter and its associated sensor, as well as a transceiver or radio for outputting or transmitting the patient data obtained by the sensor.
p-0011The receiver that receives the signal output from the sensor attached to the patient may be a bi-directional communication device referred henceforth as a communicator that has a transceiver for receiving and transmitting information or data. At least one memory is provided in the communicator for storing the most up to date information that it has received. In addition to the transceiver and the memory, the communicator may also have a processor, an user interface, a power circuit and in the case of it communicating with an oximeter sensor, an oximeter circuit. The communicator is adapted to aggregate information received or collected, so that data from the communicator may be disseminated or broadcast out toward the network.
p-0012There may be a plurality of communicators in the communications network of the instant invention, with each communicator being considered a node of the network. As the network is comprised of a plurality of nodes each being a communicator, the communication of data through the network therefore is consistent and controllerless. Moreover, as each of the communicators is mobile, the topology of the network changes and therefore the network is topology independent and resembles a peer-to-peer architecture. The size the network depends on the number of communicators or nodes that are in the network. One exemplar network may comprise from a minimum of two communicators to a maximum of N communicators, or nodes. Each transceiver, or radio, in each of the communicators has a broadcast or transmission range of a predetermined distance, so that the information broadcast from one communicator would cover a given transceiving area. Other communicators or nodes within the network that are within the transmission range of another communicator would receive the data that is being broadcast from that other communicator. Conversely, that other communicator will receive data that is broadcast from the communicators that are within its own reception range. Thus, data may be communicated among the different communicators, or nodes, of the network. There is therefore no dedicated access point, coordinator or controller in the network of the instant invention.
p-0013Not all nodes in the network are communicators, as wireless oximeters, or other medical devices, that are meant to be attached to the patient for monitoring or measuring physical parameters of the patient may also be considered as nodes of the network. For the instant invention, such wireless oximeter, and other types of medical devices that are adapted to measure or sense physical attributes from a patient, may be considered as a sensor node of the network. Alternatively, sensor nodes that collect information from the patient and transmit the collected information to the network may also be referred to as first type nodes of the network. It follows then that the second type nodes for the network of the instant invention are the communicators that receive, aggregate and broadcast the data received from the patient via the first type nodes, i.e., the wireless oximeter sensors. The communications protocol for the different types of nodes, or among the wireless sensors and the communicators, may be based on the IEEE Standard 802.15.4.
p-0014So that the various nodes of the network can communicate with each other, the devices of the network are time synchronized and follow a given communications schedule. For synchronization, the nodes of the network each are assigned time slots, with each time slot divided into subslots. Each of the nodes, or devices, is synchronized by means of communications from its neighbor(s), so that each node transmits data only in the time slot allotted to it. The communication schedule is cyclic so that all nodes on the network are scheduled to transmit or broadcast their stored data, in accordance with the respective assigned slots for the different communicator devices that form the network.
p-0015As data is disseminated or propagated from one node to the other nodes, the data is aggregated in each of the nodes that received the data. The aggregated data is disseminated across the network, so that the messages being propagated across the network are continuously updated. Aggregation takes place in a node when the message received by that node is newer than the message previously stored in that node.
p-0016In a first aspect, the present invention is directed to a system for communicating information relating to physical attributes of a patient. The system includes at least one patient monitoring device associated with a patient that has a sensor for detecting at least one physical attribute of the patient, and at least one transmitter for transmitting patient data corresponding to the detected physical attribute out to a device transmission area. There is also included in the system a plurality of communicators each having a transceiver adapted to at least receive the data transmitted from the patient monitoring device when it is located within the device transmission area. Each of the communicators communicates with other communicators that are within its transceiving area. For the inventive system, any one of the communicators, when located within the device transmission area, is adapted to receive the patient data from the patient monitoring device, and after receipt of the patient data, broadcast the patient data to other communicators that are located within its communicator transceiving area.
p-0017Another aspect of the invention is directed to a system for communicating information relating to physical attributes of patients that includes multiple patient monitoring devices each associated with a particular patient. These patient monitoring devices each have sensor means for detecting at least one physical attribute of the patient associated with the device and a transmitter for transmitting the patient data that corresponds to the physical attribute to a transmission area of the device. There is also included in the inventive system a plurality of communicators each having a transceiver adapted to receive patient data transmitted from the patient monitoring devices when located within the respective transmission areas of the patient monitoring devices. Each of the communicators is adapted to communicate with the other communicators within its transceiving area. Each of the communicators, when located within the transmission area of any one of the patient monitoring devices, is therefore adapted to receive the patient data from the any one patient monitoring device and thereafter broadcast the received patient data out to its own communicator transceiving area.
p-0018A third aspect of the instant invention is directed to a system for disseminating information relating to physical attributes of a patient remotely that includes at least one oximeter associated with a patient having sensor means for detecting at least the SP02 of the patient. The oximeter includes at least a transmitter or transceiver to at least transmit patient data corresponding to the detected SP02 away from the device. The system further includes a plurality of communicators each having a transceiver adapted to receive the data transmitted from the patient oximeter when located within the transmission range of the patient oximeter. Each of the communicators is adapted to communicate with the other communicators, so that when one of the communicators is located within the transmission range of the oximeter, it would receive the patient data from the patient oximeter and thereafter broadcast the received patient data to the other communicators that are located within its broadcast range.
p-0019A fourth aspect of the instant invention is directed to a communications network where information relating to physical attributes of a patient may be conveyed remotely. The inventive communications network includes at least one wireless sensor associated with a patient for detecting at least one physical attribute of a patient. The sensor includes at least a transmitter for transmitting patient data corresponding to the detected physical attribute away from the sensor. The network further includes a first communicator located within transmission range of the sensor having a transceiver adapted to receive the patient data transmitted from the sensor and to broadcast the received patient data. The inventive communications network further includes a second communicator in communication with the first communicator but not in communication with the wireless sensor. The second communicator has a second transceiver adapted to receive the patient data broadcast by the first communicator.
p-0020A fifth aspect of the instant invention is directed to a wireless network having a plurality of nodes for disseminating information of patients. The inventive wireless network includes at least a first type node adapted to be associated with a patient for monitoring the physical attributes of the patient. The first type node includes a detector that detects at least one physical attribute of the patient and a transmitter that transmits the detected physical attribute of the patient as data out to the network. There may also be included in the network a plurality of mobile second type nodes not directly associated with the patient that are adapted to receive signals and/or data from the first type node when moved to within the broadcast range of the first type node. Each of the second type nodes further is adapted to receive the signals and/or data from other second type nodes and to broadcast signals and/or data onto the network. The wireless network of this aspect of the invention allows any one of the second type nodes, when moved to within the broadcast range of the first type node, to receive the patient data output from the first type node, and thereafter to broadcast the received patient data out to the network so that any other second type node located within the broadcast range of the one second type node would receive the patient data output from the first type node.
p-0021A sixth aspect of the invention is directed to a wireless network that has a plurality of nodes for disseminating information of patients. This inventive wireless network includes multiple first type nodes each adapted to be associated with a particular patient for monitoring the physical attributes of the particular patient. Each of the first type nodes includes a detector that detects at least one physical attribute of the particular patient and a transmitter that transmits the detected physical attribute as patient data out to the network. The wireless network further includes a plurality of mobile second type nodes not directly associated with any patient that are adapted to receive signals and/or data from the first type nodes when moved to within the broadcast range of any of the first type nodes. Each of the second type nodes further is adapted to receive signals and/or data from other second type nodes and to broadcast signals and/or data out onto the network. When one of the second type nodes is moved to within the broadcast range of any of the first type nodes, the one second type node would receive the patient data output from that first type node. The one second type node then would broadcast the receive patient data out to the network so that any other second type node located within the broadcast range of the one second type node would receive the patient data output by the first type node.
p-0022A seventh aspect of the instant invention is directed to a method of disseminating information relating to physical attributes of patients. The method includes the steps of: a) associating at least one patient monitoring device having sensor means and at least a transmitter with a patient; b) detecting at least one physical attribute from the patient using the sensor means; c) transmitting patient data corresponding to the one detected physical attribute out to a device transmission area; d) providing a plurality of communicators each having a transceiver adapted to receive data transmitted from the patient monitoring device and to broadcast data out to a communicator transceiver area; e) locating one of the plurality of communicators within the device transmission area of the one patient monitoring device to receive the patient data; and f) broadcasting from the one communicator the received patient data to its communicator transceiver area so that other communicators that are not located within the device transmission area but are located within the transceiver area of the one communicator are able to receive the patient data transmitted from the one patient monitoring device.
p-0023An eighth aspect of the instant invention is directed to a method of communicating information relating to physical attributes of patients that comprises the steps of: a) providing multiple patient monitoring devices each having sensor means for detecting at least one physical attribute from a patient and a transmitter for transmitting the detected physical attribute; b) associating the multiple patient monitoring devices with corresponding patients; c) providing a plurality of communicators each having a transceiver adapted to receive patient data transmitted from any one of the patient monitoring devices and to communicate with other communicators; d) locating any one of the communicators to the transmission area of one of the patient monitoring devices being used to detect the physical attributes of its associated patients; e) effecting the one communicator to receive the transmitted patient data from the one patient monitoring device; and f) effecting the one communicator to broadcast the received patient data out to its communicator transceiving area.
p-0024A ninth aspect of the invention is directed to a method of disseminating information relating to physical attributes of the patients remotely that comprises the steps of: a) associating with a patient at least one oximeter having sensor means for detecting at least SP02 of the patient, the oximeter including a transceiver or at least a transmitter to transmit patient data corresponding to the detected SP02 away from the device; b) providing a plurality of communicators, each of the communicators having a transceiver adapted to receive data transmitted from the patient oximeter when located within the transmission range of the patient oximeter, the each communicator further is adapted to communicate with other communicators; c) locating one of the communicators within the transmission range of the patient oximeter so that the one communicator receives the patient data from the patient oximeter; and d) broadcasting from the one communicator the received patient data to the other communicators that are located within the transmission range of the one communicator.
p-0025A tenth aspect of the instant invention is directed to a method of conveying information relating to physical attributes of a patient remotely in a wireless communications network environment that has a plurality of transmitting and receiving devices. The method comprises the steps of: a) associating at least one wireless sensor with a patient for detecting at least one physical attribute of the patient, the sensor including at least a transmitter; (b) transmitting patient data corresponding to the detected physical attribute out onto the network; c) locating a first communicator within the transmission range of the sensor, the first communicator having a transceiver adapted to receive the patient data transmitted from the sensor; d) broadcasting from the first communicator the received patient data out onto the network; and e) establishing communication between a second communicator and the first communicator, the second communicator not in direct communication with the wireless sensor, the second communicator having a second transceiver adapted to receive the patient data broadcast by the first communicator.
p-0026An eleventh aspect of the invention is directed to a method for disseminating information of a patient in a wireless network having a plurality of nodes. The method comprises the steps of: a) associating at least one first type node with the patient for monitoring the physical attributes of the patient, the first type node including a detector that detects at lease one physical attribute of the patient and a transmitter that transmits the detected physical attribute as patient data out to the network; b) locating a plurality of second type nodes not directly associated with the patient in the network, each of the second type nodes adapted to receive signals and/or data from the first type node when moved to within the broadcast range of the first type node, each of the second type nodes further is adapted to receive signals and/or data from other second type nodes and to broadcast signals and/or data out to the network; c) moving one of the second type nodes to within the broadcast range to the first type node to receive the patient data output from the first type node; and d) broadcasting from the one second type node the received patient data out to the network so that any other second type node located within the broadcast range of the one second type node would receive the patient data output by the first type node.
p-0027A twelfth aspect of the invention is directed to a method of disseminating information of a patient in a wireless network environment that has a plurality of nodes. The method comprises the steps of: a) associating each of multiple first type nodes with a particular patient for monitoring the physical attributes of the particular patient, each of the first type nodes includes a detector that detects at least one physical attribute of the particular patient and a transmitter that transmits the detected physical attribute as patient data out onto the network; b) positioning in the network a plurality of second type nodes not directly associated with any patient; c) configuring each of the second type nodes to receive signals and/or data from the first type nodes when moved to within the broadcast range of any of the first type nodes and to receive signals and/or data from other second type nodes when within broadcast range of the other second type nodes, and to broadcast signals and/or data out to the network; d) locating one of the second type nodes to within the broadcast range of any of the first type nodes to receive the patient data output from any of the first type nodes; and e) broadcasting thereafter from the second type node the received patient data out to the network so that any other second type node located within the broadcast range of the one second type node would receive the patient data output by the first type node.
BRIEF DESCRIPTION OF THE FIGURES
p-0028The different aspects of the invention will become apparent and will be best understood by reference to the following description of the invention(s) taken in conjunction with the accompanying drawings, wherein:
p-0029<figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>is an exemplar architecture of the system of the present invention that shows an interconnected network such as for example a peer-to-peer network;
p-0030<figref idrefs="DRAWINGS">FIG. 1</figref><i>b </i>is a simplified view of a node of the network, showing the node being a medical device including a radio in a medical instrumentation environment;
p-0031<figref idrefs="DRAWINGS">FIG. 2</figref> is an exemplar network that combines the peer-to-peer network of <figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>with wireless medical devices such as wireless oximeters that are connected to the network;
p-0032<figref idrefs="DRAWINGS">FIG. 3</figref> is an exemplar simple block diagram of a communicator, in this instance a medical communicator, that forms a node of the network of the instant invention;
p-0033<figref idrefs="DRAWINGS">FIG. 4</figref> is yet another block diagram in more detail of the communicator, or a relay node, of the network of the instant invention;
p-0034<figref idrefs="DRAWINGS">FIG. 5</figref> is a block diagram of the wireless oximeter sensor, or the sensor node, that forms part of the communication network of the instant invention;
p-0035<figref idrefs="DRAWINGS">FIG. 6</figref> shows a communicator of the instant invention, acting as a relay node, being communicatively linked to a wireless oximeter, or a sensor node, of the instant invention network;
p-0036<figref idrefs="DRAWINGS">FIG. 7</figref> is a block diagram showing a sensor, in this instance an oximeter sensor, being hardwire connected by a cable to a communicator of the instant invention, so that the communicator may act as a transmitter for the sensor;
p-0037<figref idrefs="DRAWINGS">FIG. 8</figref> is an illustration of an exemplar system of the instant invention whereby a patient sensor is communicatively linked to a communicator, which in turn is communicatively linked to other communicators of the network;
p-0038<figref idrefs="DRAWINGS">FIG. 9</figref> is an exemplar illustration of the time slots for scheduling communications among the various communicative devices of the network;
p-0039<figref idrefs="DRAWINGS">FIG. 10</figref> shows exemplar types of messages that communicate among the various communicative devices, or nodes, of the network;
p-0040<figref idrefs="DRAWINGS">FIG. 11</figref> is an exemplar illustration of how the messages are aggregated and broadcast from one node communicator to another node communicator in the network;
p-0041<figref idrefs="DRAWINGS">FIG. 12</figref> is an exemplar illustration of the interactive communications between an exemplar communicator, or relay node, and a wireless oximeter, or sensor node, of the network;
p-0042<figref idrefs="DRAWINGS">FIG. 13</figref> is a block diagram showing in more detail the various components of a communicator of the instant invention;
p-0043<figref idrefs="DRAWINGS">FIG. 14</figref> is an exemplar circuit schematic of the inventive communicator of <figref idrefs="DRAWINGS">FIG. 13</figref>;
p-0044<figref idrefs="DRAWINGS">FIG. 15</figref> is a diagram showing in more detail the various components of an exemplar wireless oximeter or sensor node of the instant invention;
p-0045<figref idrefs="DRAWINGS">FIG. 16</figref> is an illustration of the major states of the radio transmitter that may be used in the wireless oximeter sensor of the instant invention;
p-0046<figref idrefs="DRAWINGS">FIG. 17</figref> is a flow diagram illustrating the operational steps the inventive communicator processes to receive information;
p-0047<figref idrefs="DRAWINGS">FIG. 18</figref> is a flow chart that illustrates the process undertaken by the radio transmitter in the communicator, and also in the wireless sensor, to transmit data;
p-0048<figref idrefs="DRAWINGS">FIG. 19</figref> is a flow diagram that illustrates the process of data being aggregated in a communicator;
p-0049<figref idrefs="DRAWINGS">FIG. 20</figref> is a flow diagram illustrating the process for updating data in the memory of a communicator;
p-0050<figref idrefs="DRAWINGS">FIG. 21</figref> is a flow chart illustrating the process of a communicator broadcasting the message that has been updated in its memory; and
p-0051<figref idrefs="DRAWINGS">FIG. 22</figref> is a flow diagram illustrating the operational processing steps of a wireless oximeter, or a sensor node, of the instant invention.
DETAILED DESCRIPTION OF THE INVENTION
p-0052With reference to <figref idrefs="DRAWINGS">FIGS. 1</figref><i>a </i>and <b>1</b><i>b</i>, a communications network, in the configuration for example of a peer-to-peer network, is shown. For the exemplar wireless network <b>2</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref><i>a</i>, there are four nodes <b>1</b>-<b>4</b>, as well as a node N that signifies that the network can have N number of nodes. For the embodiment of the invention shown in <figref idrefs="DRAWINGS">FIG. 1</figref><i>a</i>, it is presumed that each of the nodes shown may be represented by node <b>4</b> of <figref idrefs="DRAWINGS">FIG. 1</figref><i>b </i>in that each of the nodes of the network may be a medical device that includes a radio, which may be a transmitter or transceiver. The medical device may be any one of a number of devices that monitor or measure physical attributes or parameters of a patient or subject. Such medical devices include, but are not limited to, oximeters, heart rate monitors, capnographs or CO2 monitors, pumps that connect to the patient and other devices that monitor particular physical attributes of a patient. For example, in the case of a pulse oximeter, the oxygen level of arterial blood (SPO2) of the patient is monitored and/or measured. In the case of a capnograph, the CO2, ETCO2 (End Tidal CO2) and respiration rate are monitored and/or measured. Some of these medical devices may be combined. For example, the assignee of the instant application currently markets a non-radio product that is a combination of an oximeter and a capnograph under the trade name CAPNOCHECK®. For the instant invention, such combination device may be fitted with a radio so as it could act as a node of the inventive network.
p-0053The radio portion of device <b>4</b> may be a transceiver, or at least a transmitter, that operates under a conventional standard telecommunications protocol such as for example the IEEE Standard 802.15.4, so that data may be transmitted from the device out to a given broadcast or transmission area of the device. As will be discussed later, there are additional components in device <b>4</b>. For the time being, suffice it to say that the communications network of <figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>is a network that may comprise a peer-to-peer network of devices, medical or otherwise, that can communicate among each other without a hub or a central network controller.
p-0054As will be discussed in greater detail later, the nodes of the network are time synchronized and the communications among the nodes are scheduled, so that network interference that may affect the communications among the nodes is substantially eliminated. Also, particular message types are provided to enhance the quality of communication among the nodes. The particular architecture of the network as shown in <figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>further enables the dissemination of data to all of the nodes by the data being broadcast. By a process of aggregation performed in each of the nodes, the most recently obtained data is broadcast by the nodes so that the integrity of the data being communicated is enhanced. This results in the data being communicated or propagated throughout the network to be predictable, consistent, and without any need for a central controller or hub.
p-0055The topology of the network can vary and not be constrained by a particular configuration, as the size of the network may range by a minimum of 2 to a maximum of N nodes. As each of the nodes, which may be in the form of a medical device, is mobile, the topology of the network varies in accordance with the respective locations of the nodes at any one particular time. Given that each of the nodes has its own radio transmitter, each of the nodes is capable of broadcasting to a predetermined transmission range. Thus, all nodes within the broadcast or reception range of a given node can be in communication therewith. Further, as communication is not controlled by a specific node or central hub, the communications among the nodes are not restricted to a particular access point.
p-0056As shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, the network of <figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>is communicatively connected to a number of wireless oximeters, or the other medical devices discussed above. The nodes per discussed above in the <figref idrefs="DRAWINGS">FIG. 1</figref><i>a </i>network are referenced as N<b>1</b>-NN and may also be referred to as communicators CO<b>1</b>-CON. For the <figref idrefs="DRAWINGS">FIG. 2</figref> illustration, wireless oximeters O<b>1</b>, O<b>3</b> and ON are communicatively connected to communicators CO<b>1</b>, CO<b>3</b> and CON, respectively. For the instant invention, the wireless oximeters, or other medical devices per discussion above, that monitor physical parameters of the patient, may be referred to as a first type of nodes, while the communicator CO<b>1</b>-CON may be referred to as a second type of nodes N<b>1</b>-NN, of the network. The wireless oximeters may further be referred to as sensor or sensing nodes while the communicators may further be referred to as relay or propagating nodes.
p-0057The wireless oximeters are devices or modules that may be worn by a patient, for example on the finger, with a sensor built therein to detect the SP02 of the patient. An example of such wireless oximeter module is disclosed in U.S. Pat. No. 6,731,962, assigned to the assignee of the instant invention. The disclosure of the '962 patent is incorporated by reference herein. Other types of oximeter sensors that may be worn by or associated with a patient include the reflective type that may be attached to the forehead or other substantially flat surfaces of the patient, or an ear type that is adapted to clip onto the ear of the patient. The inventors have found that the inventive network operates efficiently even when 16 wireless oximeters are connected to the network. This is not to say that the <figref idrefs="DRAWINGS">FIG. 2</figref> network. may not have a smaller number of oximeters, for example 1, or more than 16 oximeters. Similarly, it was found that the preferable number of communicators or nodes in the system or network should be between 2 to 32, with the number of communicators or nodes greater than 32 being possible by adjustment of the time slots and time synchronization of the system, as will be discussed later.
p-0058With reference to <figref idrefs="DRAWINGS">FIG. 3</figref>, a communicator <b>6</b> of the instant invention is shown to include a host processor <b>8</b> that executes a program <b>10</b> stored in a memory, not shown. The program enables processor <b>8</b> to operationally control the oximeter circuit <b>12</b>, which interfaces with an external oximeter that is either coupled to the communicator by hardwire such as for example a cable, or by radio, so as to produce digital oximetry data for processing by processor <b>8</b>. An user interface <b>14</b>, also connected to processor <b>8</b>, enables the communicator to interface with the user. The user interface may comprise a display, for example a LCD display, an input source for example a keypad, and an audio circuit and speakers that may be used for alarms. Providing the power to the communicator <b>6</b> is a power circuit <b>16</b> that may include a battery, or DC input and other well known power analog circuits, so that regulated power may be routed to all of the active circuits of the communicator. An electrical interface <b>18</b> is also provided in communicator <b>6</b>. Such electrical interface may comprise an electrically conductive communications port such as for example a RS-232 port, a USB port, or other similar input/output (IO) port that allows interfacing to and from the communicator. To transceive data to and from the communicator, there is provided a radio transceiver that wirelessly transceives or communicates data between the communicator and other communicators, as well as between the communicator and a sensor device such as the wireless oximeter sensor shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, or other sensor devices, medical or otherwise, that are adaptable to transmit data wirelessly.
p-0059<figref idrefs="DRAWINGS">FIG. 4</figref> elaborates on the various components of the communicator <b>6</b> shown in <figref idrefs="DRAWINGS">FIG. 3</figref>. For example, the user interface <b>14</b> is shown to include a display, a keypad, a speaker and an analog to digital (A/D) circuit designated by “analog”. As is well known, the AND circuit converts the analog input into a digital signal, which is sent to the host processor <b>8</b>. The power component <b>16</b> of the communicator as shown in <figref idrefs="DRAWINGS">FIG. 4</figref> includes a battery, the DC input for charging the battery, a conventional analog power circuit and a digital circuit that allows the power component <b>16</b> to communicate with host processor <b>8</b>. The power provided by the power component is routed to all of the active circuits of the communicator. The electrical interface component <b>18</b>, as was mentioned previously, has one or both of the RS-232 and USB ports, or other interfacing ports that are conventionally used. The oximeter component <b>12</b> has the analog circuit for analyzing the analog signals received from the patient sensor, a memory program that stores the operational functions for the oximeter component, and a microprocessor that processes the data received from the patient to produce digital oximetry data, which is then communicated to the host processor <b>8</b>. As was noted earlier, a memory program <b>10</b> in the host that encompasses processor <b>8</b> provides the operational instructions to processor <b>8</b> for the overall operation of the communicator. The last major component in communicator <b>6</b> is the radio <b>20</b>, which includes a radio IC module, a memory stored program that controls the functioning of the radio transmitter, the analog circuits for controlling the operations of the radio and the antenna that allows the radio transceiver to transmit and receive signals to and from the communicator.
p-0060A wireless oximeter device that forms the sensor node of the network is shown in <figref idrefs="DRAWINGS">FIG. 5</figref>. The wireless oximeter <b>22</b> is shown to include a sensor component <b>24</b>. Such component is conventional and includes two LEDs that output lights of different frequencies to a digit or some other area such as the forehead of a patient, and a detector that detects the light that passes through or reflected from the patient. Also included in wireless oximeter <b>22</b> is an oximeter circuit <b>26</b> that includes a processor, an analog circuit that analyzes the waveform signals detected from the patient and a memory that stores the program to instruct the analog circuit to analyze the incoming signals from the patient and converts it into oximetry data. The operation of the sensor <b>24</b> is also controlled by oximeter circuit <b>26</b>. Interfaced to and working cooperatively with the oximeter component <b>26</b> and/or the sensor component <b>24</b> is a radio component <b>28</b> that includes an antenna, a program stored in a memory, an analog circuitry that operates the radio IC module and an antenna that transmits the oximetry data of the patient to the communicator. Power component <b>30</b> includes the battery power source and the conventional analog power circuitry that supplies power to the other components of the wireless oximeter. In the network of the instant invention, per shown for example in <figref idrefs="DRAWINGS">FIG. 2</figref>, the wireless oximeter device of <figref idrefs="DRAWINGS">FIG. 5</figref> transmits collected patient data to the communicator(s) that is/are within its broadcast range, or transmission area.
p-0061<figref idrefs="DRAWINGS">FIG. 6</figref> shows in more detail the interaction of a wireless finger oximeter device with a communicator of the instant invention. Here a wireless communications link <b>32</b> is established between communicator <b>6</b> and the wireless oximeter <b>22</b>. As shown, the radio transceiver of communicator <b>6</b> communicates with the radio transmitter of oximeter <b>22</b>, so that the oximeter data obtained from the patient by sensor <b>24</b> is sent to communicator <b>6</b>, which may then relay the information by broadcasting it out to its transceiver area. It should be noted that communicator <b>6</b> would receive the data from oximeter <b>22</b> only if it is within the transmission area or broadcast range of the oximeter device. For the <figref idrefs="DRAWINGS">FIG. 6</figref> embodiment, when the oximeter circuit in the wireless oximeter <b>22</b> is actively analyzing and converting the patient data, the oximeter circuit in communicator <b>6</b> may not be since the patient data is being transmitted from oximeter device <b>22</b> to communicator <b>6</b>. The signal being transmitted from oximeter device <b>22</b> to communicator <b>6</b> is in most instances a digital signal. However, there may be instances where raw data may be sent directly from the oximeter device to the communicator, if it is desirable to eliminate the analog to digital circuitry in the oximeter and also reduce the processing power from the oximeter. In other words, raw data may be sent from an oximeter device to a communicator, if necessary, so that the communicator may perform the processing that converts the raw data into the required oximetry data.
p-0062In place of the wireless finger oximeter device <b>22</b> shown in <figref idrefs="DRAWINGS">FIG. 6</figref>, the instant invention is also adapted to be used with a conventional oximeter sensor, such as <b>34</b> shown in <figref idrefs="DRAWINGS">FIG. 7</figref>. There, a conventional oximeter sensor that has the light source and the detector necessary for measuring the SP02 of the patient is connected by means of a cable <b>36</b> to a communicator of the instant invention. This may be effected by mating the electrical connector of the sensor to the port that is a part of the electrical interface <b>18</b> of communicator <b>6</b>. The signals received from the patient are then processed and stored, and then broadcast out by the communicator to its transceiving area. In this embodiment, communicator <b>6</b> acts as the transmitter of the patient monitoring device by working cooperatively with the oximeter sensor. Moreover, as it has to be within cable distance from oximeter sensor <b>34</b>, communicator <b>6</b> is located fixedly relative to the oximeter sensor and proximate to the patient.
p-0063<figref idrefs="DRAWINGS">FIG. 8</figref> shows an ad hoc mesh communications network of the instant invention where a wireless oximeter sensor device <b>22</b>, with the sensor possibly attached to a digit of a patient, not shown, being in communication with a communicator <b>6</b><i>a</i>. Communicator <b>6</b><i>a </i>in turn is in communication link with communicator <b>6</b><i>b </i>and communicator <b>6</b><i>c</i>. Both communicators <b>6</b><i>b </i>and <b>6</b><i>c </i>are in communication link with communicator <b>6</b><i>d</i>. Communicator <b>6</b><i>d </i>is also communicatively linked to communicator <b>6</b><i>e. </i>
p-0064As further shown in <figref idrefs="DRAWINGS">FIG. 8</figref>, each of the communicators has a display <b>24</b> that is capable of showing the data of multiple patients. For the exemplar communicators of <figref idrefs="DRAWINGS">FIG. 8</figref>, both the SP02 and the heart rate of the patient(s) are shown on displays <b>26</b><i>a </i>and <b>26</b><i>b</i>, respectively. Further, there are shown on each of the displays of exemplar communicators <b>6</b><i>b </i>to <b>6</b><i>e </i>five sets of data, with each set of data representing a particular patient. Although data representing five patients is shown in the exemplar communicators of <figref idrefs="DRAWINGS">FIG. 8</figref>, it should be appreciated that a smaller or a greater number sets of patient parameter data may also be displayed by each of the communicators. Furthermore, it should be appreciated that if the communicators of <figref idrefs="DRAWINGS">FIG. 8</figref> were devices other than oximeters as mentioned supra, then the display of each of those communicators may display patient data that represents other patient attributes, such as for example CO2 and respiration rate in the case where the devices are CO2 monitors or combined CO2 monitor and oximeter devices.
p-0065For the wireless oximeter sensor <b>22</b> that is communicatively connected to communicator <b>6</b><i>a</i>, the physical parameter measured or sensed from the patient <b>1</b> may be sent as an oximeter data message data file, 96 byte for example, to communicator <b>6</b><i>a</i>. Upon receipt of the data file from oximeter device <b>22</b>, communicator <b>6</b><i>a </i>stores the data file for patient <b>1</b> as P<b>1</b> in its remote data display RDD table <b>28</b><i>a</i>. The patient <b>1</b> previously stored data in the memory of communicator <b>6</b><i>a </i>is replaced or updated by the latest data from patient <b>1</b>. The RDD table <b>28</b><i>a </i>for the exemplar communicator <b>6</b><i>a </i>is shown to have a capacity that can store data of a plurality of patients, for example from patient P<b>1</b> to patient PN. An exemplar approximately 18 byte memory may be reserved for each of the patients in the memory store of the communicator. Multiple tables may be stored in each of the communicators, so that patient data that were received at different times may actually be kept and compared with the latest information for an aggregation process that will be later described in greater detail. The additional exemplar tables <b>28</b><i>b </i>and <b>28</b><i>c </i>for the communicator <b>6</b><i>a </i>are shown in <figref idrefs="DRAWINGS">FIG. 8</figref>.
p-0066The interactions between wireless oximeter <b>22</b> and communicators <b>6</b> begins when wireless oximeter <b>22</b> transmits a signal representing at least one physical attribute of the patient, for example the patient's SP02, away from the oximeter to a predetermined transmission range, i.e., the sensor's transmission area. For the <figref idrefs="DRAWINGS">FIG. 8</figref> exemplar network, the wireless oximeter <b>22</b> may be considered the sensor node. As illustrated by communications link <b>30</b><i>a </i>of the <figref idrefs="DRAWINGS">FIG. 8</figref> network, communicator <b>6</b><i>a </i>is located within the transmission area or zone of wireless oximeter <b>22</b>. Thus, when wireless oximeter <b>22</b> outputs the patient data sensed from patient <b>1</b>, communicator <b>6</b><i>a </i>would receive the patient data being transmitted. Upon receipt, the patient data may be stored in a RDD table, for example <b>28</b><i>a</i>, as patient data P<b>1</b>. If there was prior P1 data for patient <b>1</b>, this prior data is replaced by the just received data in the RDD table. The stored data may be displayed on display <b>24</b> of communicator <b>6</b><i>a </i>as the SP02 and/or pulse rate of the patient. Note that the patient data may also be displayed, analyzed, conductively communicated, and/or stored for trending, RDD or high speed application.
p-0067As further shown in the exemplar <figref idrefs="DRAWINGS">FIG. 8</figref> network, communicator <b>6</b><i>a </i>has established communication paths with communicator <b>6</b><i>b </i>and communicator <b>6</b><i>c </i>via communication links <b>30</b><i>b </i>and <b>30</b><i>c</i>, respectively. As was discussed previously, each of the communicators of the instant invention has its own radio transceiver, so that each communicator is adapted to receive signals from both wireless oximeters or other medical sensors and other communicators, so long as it is within the transmission range of those sensors and/or communicators. Conversely, each of the communicators is adaptable to broadcast a signal out to a predetermined broadcast range, or its transceiving area. Thus, for the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref>, as each of communicator <b>6</b><i>b </i>and <b>6</b><i>c </i>is within the transceiving area of communicator <b>6</b><i>a</i>, those communicators each are in communication with communicator <b>6</b><i>a. </i>
p-0068For the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref>, upon receipt of the patient P<b>1</b> data from wireless oximeter <b>22</b>, after storing the received data in its RDD table <b>28</b><i>a</i>, communicator <b>6</b><i>a </i>broadcasts this latest P<b>1</b> data out to its transceiving area. Communicators <b>6</b><i>b </i>and <b>6</b><i>c</i>, each being within the transmitting range of communicator <b>6</b><i>a</i>, receive the same data of patient P<b>1</b>. Each of those communicators <b>6</b><i>b </i>and <b>6</b><i>c </i>then updates its own RDD table, and may display the latest patient P<b>1</b> data on its display, so that the holder of those communicators could see the physical parameters, in this instance, the SP02 and pulse rate, of patient P<b>1</b>. Each of communicators <b>6</b><i>b </i>and <b>6</b><i>c </i>then transmits the latest patient P<b>1</b> data out to their respective transceiving areas. Note that each of communicator <b>6</b><i>b </i>and <b>6</b><i>c </i>is shown not to be in direct communications link with wireless oximeter sensor <b>22</b>.
p-0069As communicator <b>6</b><i>d </i>happens to be in the transmission range of both communicators <b>6</b><i>b </i>and <b>6</b><i>c</i>, it receives the data of patient P<b>1</b> from each of those communicator via communication links <b>30</b><i>d </i>and <b>30</b><i>e</i>, respectively. In this scenario, as the patient P<b>1</b> data is the same from both communicators <b>6</b><i>b </i>and <b>6</b><i>c</i>, any updating of the data relating to patient P<b>1</b> results in the same data being updated in the RDD table of communicator <b>6</b><i>d</i>. However, in another scenario where the communications schedule between communicators <b>6</b><i>b </i>and <b>6</b><i>d </i>is substantially different from that between communicators <b>6</b><i>c </i>and <b>6</b><i>d</i>, it may be that the data from the same patient received by communicator <b>6</b><i>d </i>from communicators <b>6</b><i>b </i>and <b>6</b><i>d </i>may differ due to the propagation delay of the patient data along the respective communications links. In that case, the later patient data is stored as the patient data in communicator <b>6</b><i>d</i>. To prevent conflict in the event that the transmission of data from multiple nodes takes substantially the same amount of time, a time slotted schedule communication protocol, which will be discussed later, is provided for the network of the instant invention. The last node in the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref> is communicator <b>6</b><i>e</i>, which is in communications range with communicator <b>6</b><i>d </i>via communication link <b>30</b><i>f</i>. Communicator <b>6</b><i>e </i>is not in communication range with any of the other communicators or the wireless oximeter sensor <b>22</b>. With the instant invention, even though communicator <b>6</b><i>e </i>is located remotely from sensor <b>22</b>, the holder of communicator <b>6</b><i>e </i>nonetheless is able to monitor the physical parameter of patient <b>1</b> due to the propagation of data, or data hop, of the RDD messages across the communicator nodes of the network.
p-0070Although only one wireless oximeter sensor <b>22</b> is shown in the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref>, it should be appreciated that there might be multiple wireless oximeter sensor devices linked communicatively along the network, so that different communicators of the network may transmit patient information to other communicators communicatively connected thereto. As a result, data of multiple patients may be displayed on each of the communicators. This is illustrated by the respective displays <b>24</b> of communicators <b>6</b><i>b</i>, <b>6</b><i>c</i>, <b>6</b><i>d </i>and <b>6</b><i>e </i>of the <figref idrefs="DRAWINGS">FIG. 8</figref> network where five sets of data, each corresponding to a particular patient, are displayed on each of those communicators. The users or operators of those communicators may each therefore be able to monitor the physical parameters of a number of patients, even though they may not be in the vicinity of any one of those patients. Thus, for the network of the instant invention, so long as a remote communicator node is within the broadcast range of another communicator node that in turn had received, via possibly other communicator nodes, the data from a patient, that remote communicator node would also be in receipt of the same patient data and can therefore monitor remotely the well being of that patient.
p-0071To prevent conflict among the various nodes of the network of the instant invention, a time slotted scheduled communication protocol is mandated. To that end, each of the devices, or nodes, of the network has one slot of a given time period to transmit its data. This time slotted schedule communications protocol is illustrated in <figref idrefs="DRAWINGS">FIG. 9</figref>. As shown, a number of slots, for example slots S<b>1</b> to S<b>10</b>, are provided in the exemplar time period of <figref idrefs="DRAWINGS">FIG. 9</figref>. The number of slots may correspond to the number of communicator devices in a particular network. Thus, if the network were to include 16 devices, then there would be 16 slots provided in the time period. The time periods are repeated so that communications among the various devices in the network are scheduled. Predictable and reliable network communications result.
p-0072For each device, the time slot assigned thereto enables the device to transmit multiple messages exclusively at that given time slot. For example, for the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref>, slot S<b>1</b> may be assigned to communicator device <b>6</b><i>a</i>, slot S<b>2</b> to communicator <b>6</b><i>b</i>, slot S<b>3</b> to communicator <b>6</b><i>c</i>, slot S<b>4</b> to communicator <b>6</b><i>d </i>and slot S<b>5</b> to communication <b>6</b><i>e</i>. Thus, communicator <b>6</b><i>a </i>would transmit at time slot S<b>1</b>, communicator <b>6</b><i>b </i>at time slot S<b>2</b>, communicator <b>6</b><i>c </i>at time slot S<b>3</b>, etc. For the exemplar network of <figref idrefs="DRAWINGS">FIG. 8</figref>, it may not be necessary to have 10 slots for each time period. One possible way of assigning each device a particular slot is for the operator of the facility that the network is located, for example an ICU ward in a hospital, to have programmed into the devices their respective slots. Another possible way is for the operator of the network to assign the devices the different slots. The various devices in the network are synchronized to the radio frequency (rf) transmissions.
p-0073There is a fair amount of data that needs to be transmitted in pulse oximetry, including wireless oximetry. In addition to the number of devices in the network, the number of messages may be selectively optimized for each of the slots. In the communications protocol of <figref idrefs="DRAWINGS">FIG. 9</figref>, it is assumed that there might be six types of messages that are transmitted at their assigned slots by each of the relay node devices. These messages are in the form of message packets and are illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>. In <figref idrefs="DRAWINGS">FIG. 9</figref>, the messages (M) are labeled, with M<b>1</b> corresponding to the first message NWK and M<b>6</b> corresponding to the last message WS. Message M<b>1</b>, the NWK message, refers to a node overhead information message, or the “network overhead information”. Message M<b>2</b> is the RDD (remote data display) message that carries the data stored in the RDD table in the memory of the communicator and, once updated, may be displayed by the communicator. Messages M<b>3</b> and M<b>4</b> are the HS1 (high speed 1) and HS2 (high speed 2) messages that flood or broadcast data, when needed, to the other node devices in the network.
p-0074To illustrate with reference to the <figref idrefs="DRAWINGS">FIG. 8</figref> exemplar network, if the patient data received from the patient (P<b>1</b>) indicates to communicator <b>6</b><i>a </i>that the data from the patient is outside of a predetermined specified or acceptable range, then communicator <b>6</b><i>a </i>would go into an alarm mode in which an alarm is set off, so that the user of communicator <b>6</b><i>a </i>knows that there is something amiss with patient P<b>1</b>. At the same time, to overcome the bandwidth limitations of the network, by means of HS1 and/or HS2 messages, communicator <b>6</b><i>a </i>floods the network with alarm messages in order to reach the other communicators in the network, since this may be an emergency situation where the people who are carrying the other communicators should be notified. Thus, by sending HS1 and HS2 messages, the operators or medical personnel of communicators <b>6</b><i>d </i>and <b>6</b><i>e</i>, who are not in direct communications link with the wireless oximeter sensor <b>22</b>, are nonetheless notified of the alarm condition for patient (P<b>1</b>) so that appropriate action, if any, may be taken by those healthcare personnel. Also, the HS1 and/or HS2 messages may be selectively used to broadcast, upon request by a user, measured physical attribute(s) at a high rate to a remote communicator. The user may either be the person associated with the communicator that is to transmit the data, or the person associated with the remote communicator to which the data is to be transmitted. In the event that the request to use the HS1 and/or HS2 messages were to come from the remote communicator, a remote request first has to be received and recognized as such by the transmitting communicator.
p-0075The next message M<b>5</b> (CTR) is a control message from the communicator to its dedicated wireless sensor, which is identified by message M<b>6</b> WS (wireless sensor). This is required because a wireless sensor may not have the user control mechanisms required to configure the integral radio and oximeter. Furthermore, a communicator node in the network may not necessarily be in direct communications link with its dedicated sensor. For example, it may be that the carrier of communicator <b>6</b><i>e </i>is in fact the responsible nurse for the patient who is connected to wireless oximeter sensor <b>22</b> in the <figref idrefs="DRAWINGS">FIG. 8</figref> exemplar network. And the reason that communicator <b>6</b><i>e </i>is not in the vicinity of wireless oximeter sensor <b>22</b> may be that the nurse had to take care of another patient and accordingly had moved out of the transmission range of wireless oximeter sensor <b>22</b>. Yet the nurse nonetheless is able to continuously monitor the physical parameters, for example the SP02 of patient P<b>1</b> due to the relaying of the patient P<b>1</b> data from the other communicators of the network. Message M<b>6</b> therefore identifies to the other communicators that wireless oximeter sensor <b>22</b> is the dedicated sensor for communicator <b>6</b><i>e</i>. Each communicator may also control the operation of its dedicated wireless oximeter, if the wireless oximeter is adapted to wirelessly communicate bidirectionally, by sending a M5 control message CTR, which is relayed by the other nodes in the network to the wireless oximeter identified by the WS message.
p-0076With the time slotted scheduled communications protocol shown in <figref idrefs="DRAWINGS">FIG. 9</figref>, the communications among the various devices of the network become predictable and reliable. Accordingly, the protocol provides a deterministic approach for the instant invention system or network, as the processes for the various nodes are synchronized. Moreover, the system is deterministic in that each time slot is assigned to a particular device, so that each device may be able to listen to the other devices when it is not its time to “talk”; and when it is the device's turn to “talk”, the other devices of the network would listen. In other words, each of the devices of the network has been assigned or allotted a given time period to communicate or disseminate information to the other devices of the network, without any central controller mandating the various devices what to transmit and when to transmit.
p-0077The message packets of the message types of <figref idrefs="DRAWINGS">FIG. 9</figref> are assigned a sufficient size, for example 96 bytes, so that all necessary data may be carried in those message packets for propagation across the network. The message types and the respective flows of those messages across the network are shown in more detail in <figref idrefs="DRAWINGS">FIG. 10</figref>. There, communicator is designated “CO”.
p-0078<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates how the remote data display messages are aggregated and broadcast or flooded to the various relay nodes or communicators in the system and network of the instant invention. Here it is assumed that there are multiple communicators (CO<b>1</b>, CO<b>2</b> to CON) in the network, with each of the communicators transmitting its RDD message out to a given transceiving range, or broadcast range. As shown, communicator CO<b>2</b> is within the broadcast range of communicator CO<b>1</b> and communicator CON is in communication range with at least communicator CO<b>2</b>. To prevent confusion and to enhance understanding, for the discussion of <figref idrefs="DRAWINGS">FIG. 11</figref>, “RDD” may refer to a memory table in each of the communicators and also a message when it is transmitted from one node communicator to another node communicator.
p-0079Communicator C<b>01</b> has in its memory a local data store that stores the RDD message as RDD table <b>32</b>, which communicator C<b>01</b> had incorporated therein the information it received, either directly or indirectly, from a wireless oximeter. For RDD table <b>32</b>, “Node” <b>32</b><i>a </i>refers to the nodes, both sensor and communicator, of the network, the “Time” <b>32</b><i>b </i>refers to the time stamp of when the message was recorded in the node, and the “Data” <b>32</b><i>c </i>refers to the kind of data that was transmitted from the node and received by the communicator. Thus, the RDD table in communicator C<b>01</b> has stored therein data from a number of nodes (<b>1</b>, <b>2</b> to N) each having corresponding data (x<b>1</b>, x<b>2</b>, xN) with a given time stamp (t<b>11</b>, t<b>21</b> to tN<b>1</b>), respectively. The RDD table <b>32</b> from communicator C<b>01</b> is broadcast by the radio transceiver of the communicator to its transceiving range and is received as RDD message <b>32</b>′ by communicator CO<b>2</b>.
p-0080Communicator CO<b>2</b> also has a previously stored RDD table that has a number of sets of data from the various nodes, per shown by RDD table <b>34</b>. An aggregation process next takes place in communicator CO<b>2</b> in that the data received from communicator CO<b>1</b>, i.e., from RDD message <b>32</b>′, is compared with the prior stored data in RDD table <b>34</b>. As an illustration, the previously stored information from node <b>1</b> is “t<b>10</b>” in RDD table <b>34</b>, whereas the information for node <b>1</b> in RDD message <b>32</b>′ has a time stamp “t<b>1</b>”. This means that the information relating to node <b>1</b> is more recent in RDD message <b>32</b>′. As a consequence, the data for node <b>1</b> is updated to “x<b>1</b>” and is stored in the new RDD table <b>36</b>. The same aggregation process takes place with the information relating to node <b>2</b>. For that node, insofar as the time therefor in RDD table <b>34</b> is “t<b>22</b>” whereas the time for node <b>2</b> in RDD message <b>32</b>′ is “t<b>21</b>”, the data that is stored in RDD table <b>34</b> is judged to be the more recent data. Accordingly, the data “y<b>2</b>” in RDD table <b>34</b> is copied to RDD table <b>36</b>. The same aggregation process repeats for the remainder nodes in RDD table <b>34</b> by comparing its previously stored data with those in RDD message <b>32</b>′. Once the data in the RDD table <b>34</b> has all been compared and if needed updated, the updated RDD table <b>36</b> is broadcast as RDD message <b>36</b>′ by communicator CO<b>2</b> out to its transceiving area.
p-0081RDD message <b>36</b>′ is received by communicator CON as RDD table message <b>36</b>′. The same aggregation process then takes place in communicator CON whereby the information in RDD message <b>36</b>′ is compared with the previously stored information in RDD table <b>38</b> for generating an updated RDD table <b>40</b>. For the example illustration in <figref idrefs="DRAWINGS">FIG. 11</figref>, the data for node <b>1</b>, as received by communicator CO<b>1</b>, is relayed to communicator CON and updated in its RDD table <b>40</b>. Further, the data for node <b>2</b>, as reflected in RDD table <b>40</b> of communicator CON, is updated from the data previously stored in RDD table <b>34</b> of communicator CO<b>2</b>.
p-0082In a system where all of the communicators are within range of all of the other communicators, there would be minimal latency in terms of the messages transmitted and received. However, in practice, such often is not the case as shown in exemplar <figref idrefs="DRAWINGS">FIG. 8</figref>, so that there is always a propagation delay in terms of the messages that are being broadcast from one communicator to the next one, as the RDD messages would “hop” from one communicator node to the next communicator node, in order to propagate across the network. Even though only RDD messages are disclosed so far as being propagated across the network, it should be appreciated that messages aside from or in addition to RDD messages may also be disseminated or propagated across the network from node to node. For example, the communicators have built-in alarm functions, so that if the physical parameter(s) measured from a patient exceeds or falls below respective upper and higher limits, i.e., outside predetermined safety limits, the alarm is triggered to warn the user of the communicator that something may be amiss with the patient. Another aspect of the instant invention is that instead of RDD messages, only an alarm signal is propagated or flooded across the network to warn the various people, medical personnel or otherwise, equipped with communicators that a particular patient may be in distress.
p-0083So that additional information may be propagated across the network, the communicators each may be fitted with a text messenger chip so that its display may be actuated to a text mode to receive text messages that may accompany the alarm, which may be a sound of a given frequency or loudness or a flashing screen for example. The text message may be specifically directed to a given communicator, or may be broadcast or flooded to all communicators along the network. The communicator of the instant invention is therefore adapted to be used as a pager that can either simply receive an alarm from a particular patient or multiple patients, or as a more sophisticated pager where text messages may accompany an alarm when the being monitored physical parameter(s) of a particular patient or a given number of patients is/are deemed to be irregular and warrants closer scrutiny.
p-0084Power consumption is an important consideration in oximetry, since the wireless oximeters are relatively small and yet may require substantial power to operate their radio transmitters. There is therefore a need for the wireless oximeters to conserve their energy. For the network of the instant invention, since each oximeter sensor is programmed to communicate only in a given time slot assigned to it in a given time period, the wireless oximeter does not need to be cognizant of what happens to the other time slots. The wireless oximeter can therefore go into a sleep or suspension mode to conserve its power when it is not in its communication mode. But during the time that the wireless oximeter is in operation, it is important that it be synchronized with the communicators, or at least the communicator that is in range of its signals, and be able to broadcast the information that it senses from the patient to whom its sensor is attached. The time slotted schedule communications protocol of the instant invention allows such conservation of energy due to its deterministic characteristics.
p-0085With reference to <figref idrefs="DRAWINGS">FIG. 12</figref>, the interactions between a wireless oximeter sensor and a communicator are shown. The sensor and the communicator shown in <figref idrefs="DRAWINGS">FIG. 12</figref> may be wireless oximeter <b>22</b> (Sensor <b>1</b>) and communicator <b>6</b><i>a </i>(CO<b>1</b>), respectively, as shown in <figref idrefs="DRAWINGS">FIG. 8</figref>. For the communicator CO<b>1</b>, <figref idrefs="DRAWINGS">FIG. 12</figref> shows the time slot (0 to T) that the communicator has been allotted for transmitting its messages. For Sensor <b>1</b>, <figref idrefs="DRAWINGS">FIG. 12</figref> shows a sequence of functions that the oximeter goes through during approximately the same time period to conserve power.
p-0086As shown in <figref idrefs="DRAWINGS">FIG. 12</figref>, at time <b>42</b><i>a</i>, communicator CO<b>1</b> is transmitting, for example the RDD message and other transmissions disclosed with reference to <figref idrefs="DRAWINGS">FIGS. 9 and 10</figref>. At the same time <b>44</b><i>a</i>, Sensor <b>1</b>, which is connected to a patient, is in its sleep mode. At time <b>42</b><i>b</i>, communicator CO<b>1</b> continues to transmit its data. At time <b>44</b><i>b</i>, Sensor <b>1</b> wakes up either in response to an internal timer or from the initialization of the sensor to begin collecting the physical parameter(s) from the patient. This wake-up time is referenced as T<sub>WU </sub>in <figref idrefs="DRAWINGS">FIG. 12</figref>. At time <b>42</b><i>c</i>, communicator CO<b>1</b> continues to transmit its data. In the corresponding time <b>44</b><i>c</i>, Sensor <b>1</b> receives the patient data serially from its sensor. At time <b>42</b><i>d</i>, communicator CO<b>1</b> transmits a signal to a particular wireless oximeter, for example Sensor <b>1</b>. At corresponding time <b>44</b><i>d</i>, Sensor <b>1</b> receives the radio frequency signal from communicator CO<b>1</b> and, noting that it is a signal specifically identifying it, synchronizes its timing with that of communicator CO<b>1</b>. Thereafter, at time <b>44</b><i>e</i>, Sensor <b>1</b> transmits the data that it has obtained from the patient. This data is received by communicator CO<b>1</b> at time <b>42</b><i>e</i>, as designated by the RX WS (receive wireless sensor) signal. Thereafter (after time T), communicator CO<b>1</b> enters into a receiving mode where it listens to the various oximeters and communicators that may be present in the network, for example the RX<sub>1</sub>, RX<sub>2 </sub>to RX<sub>M </sub>devices. At approximately the same time, Sensor <b>1</b> goes to its sleep mode (T<sub>GS</sub>) and stays asleep until it is either waken up by an internal timer or activated to begin monitoring the physical parameter, for example SP02, of the patient.
p-0087By thus putting the wireless oximeter sensor to sleep when it is not measuring the physical parameters from the patient, the power required for the oximeter is reduced and therefore the size of the oximeter may be reduced. On the other hand, the radios of the communicators, which are mobile units, would remain awake in order to listen in on the other communicators, and other devices, that form the nodes in the network.
p-0088For the alarm pager aspect of the invention discussed earlier, it should be noted that such pager would only need to listen in on the information that is propagating along the network. In other words, a communicator operating in the guise of a pager does not need to transmit any information. Thus, a pager communicator does not do the function of a communicator described thus far. But a communicator does do, as one of its functions, the paging function by receiving the data being propagated along the network and looking for any alarm conditions. Putting it another way, a communicator is bidirectional in terms of its communicative functions, whereas the pager does not need to be.
p-0089With reference to <figref idrefs="DRAWINGS">FIG. 13</figref>, a more detailed block diagram of the communicator of the instant invention is shown. The same numbers that were used for the <figref idrefs="DRAWINGS">FIG. 4</figref> block diagram are used herein for the same components. As shown, communicator <b>6</b> has a main host board or module that has an oximeter module <b>12</b> and a radio module <b>20</b>. In the oximeter module <b>12</b>, there is a memory <b>12</b><i>a</i>, a processor controller <b>12</b><i>b </i>that is dedicated for the oximeter module and a sensor circuit <b>12</b><i>c</i>. Sensor circuit <b>12</b><i>c </i>is connected to a sensor connector <b>46</b> to which a sensor attached to a patient may be connected by means of a cable. The radio module <b>20</b> of the communicator also has its dedicated memory <b>20</b><i>a</i>, a dedicated processor controller <b>20</b><i>b</i>, a transceiver <b>20</b><i>c</i>, and an analog circuit <b>20</b><i>d </i>that drives the signal to an antenna <b>20</b><i>e </i>for transceiving data to and from the communicator.
p-0090On the main host board, there is a memory <b>10</b> and a microprocessor <b>8</b> which controls all of the modules as well as the drivers on the host board or module of the communicator. Processor <b>8</b> obtains the oximetry data from the oximeter module or circuit. This data may be communicated by visual display, audio alarms, wired communications, and RF communications. As shown, there are four different drivers <b>48</b><i>a</i>, <b>48</b><i>b</i>, <b>48</b><i>c </i>and <b>48</b><i>d</i>. Driver <b>48</b><i>a </i>drives a display <b>50</b> that displays for example the SPO2 and the pulse rate of a patient, and possibly text messages in addition, when information more than the SPO2 and pulse rate are desired or when the communicator is being used as a pager. Driver <b>48</b><i>b </i>drives an alarm <b>52</b> which triggers when the measured patient parameter is deemed not to be within an acceptable range. Driver <b>48</b><i>c </i>drives an user input <b>54</b> such as for example a keypad or a pointing device to allow the user to interact with the communicator. Driver <b>48</b><i>d </i>works with a wire communications module <b>56</b>, which in turn has connected thereto a communication connector <b>58</b> that may for example be an RS-232 port or a USB port as was discussed previously.
p-0091The power of the communicator is provided by a power circuit <b>58</b> that regulates the power level of a battery <b>60</b>. An external power interface <b>62</b> connects to the power circuit <b>58</b> to a power connector <b>64</b>, so that external power may be provided to either recharge battery <b>60</b> or to power the communicator from a power outlet, as for example when the communicator is connected by cable to a sensor that is attached to the patient. The software program for the functioning of the communicator is stored in memory <b>10</b>.
p-0092<figref idrefs="DRAWINGS">FIG. 14</figref> is an exemplar schematic diagram of the communicator of the instant invention. As shown, the main communicator printed circuit board or module <b>66</b> is divided into a number of major modules or circuits. These circuits include oximeter module <b>68</b>, power module <b>70</b>, display module <b>72</b>, the main processor <b>74</b> and its associated circuits on the PC board it is mounted to, memory module <b>76</b>, audio module <b>78</b> and radio module <b>80</b>. There are also miscellaneous circuits that include for example the realtime clock, A/D converter, and external communications circuitries. A docking station and a printer (not shown) may also be included in the system.
p-0093Oximeter module <b>68</b> comprises an oximeter PCB (print circuit board) of the assignee, designated <b>68</b><i>a</i>, that has a manufacturer reference PN 31392B1, or variants of PN 31402Bx or PN 31392Bx. This oximeter board communicates by way of a logic level, full duplex, Universal Asynchronous Receiver Transmitter (UART) from the P<b>12</b> connector to the host processor <b>74</b>. Power to the oximeter circuit board <b>68</b><i>a </i>is provided by power circuit <b>70</b> in the form of regulated 3.3 volt via connector P<b>12</b> through switched capacitor regulator U<b>9</b>. Connector P<b>11</b> at board <b>68</b> provides the connection to a connector P<b>14</b> at main board <b>66</b>, which is used to connect to a wired oximeter sensor. The signals received from the oximeter sensor are routed through board <b>68</b><i>a</i>, and by way of connector P<b>12</b> to processor <b>74</b>.
p-0094Power module <b>70</b> is adapted to be powered from multiple sources which include a universal mains AC/DC 9V wall mount power supply, a Universal Serial Bus (USB) powered at 5V at 500 mA, a user changeable AA (4 alkaline disposable batteries at 6V), and custom lithium ion rechargeable batteries at 7.4V. Whichever power is supplied is automatically arbitrated. The AC/DC 9V power and the USB 5V power enter through the general purpose docking/serial communications connector P<b>3</b>. The alkaline and lithium ion rechargeable batteries occupy the same internal battery compartment so that one or other can be present at any given time and each have their separate connections. The alkaline batteries are connected four in series by way of connectors P<b>9</b> and P<b>8</b>, while the lithium rechargeable pack connects through the five-position connecter P<b>10</b>. The lithium ion rechargeable pack contains integral charging control, fuel gauge, and redundant safety circuits. Additional signals on P<b>10</b> are the AC/DC 9V power, USB 5V power plus 7.4V out, ground and 1-1 wire logical interface to the main processor <b>74</b> (U<b>21</b>) to communicate the charging and fuel gauge information. As shown, all of the possible power supplies are diode OR'ed to create a source that can range between 4.5V and 8.5V before being routed to the main on/off power MOSFET transistor Q<b>2</b>. The power source is then efficiently converted to 2.7V by way of a step down converter/switchable regulator U<b>3</b>. Other supply voltages of 1.8V and 1.5V are also created by regulators U<b>2</b> and U<b>1</b>, respectively. The main processor U<b>21</b> operates from the 2.7V, 1.8V and 1.5V supplies. The flash and SDRAM memories operate from the 1.5V supply. The radio and much of the general purpose I/O operate from the 2.7V supply.
p-0095The display circuit may comprise a color TFT 3.0 inch LCD display manufactured by the Sharp Electronics Company having a manufacturing number PN LQ030B7DD01. The display resolution is 320Hx320V. Processor U<b>21</b> provides an integral LCD controller peripheral that is capable of generating a majority of the required timing and LCD control signals. Four additional LCD related circuits (external to processor U<b>21</b>) are shown. Contrast control is provided through digital potentiometer (POT) U<b>12</b> and commanded by the main processor U<b>21</b> by way of an I<sup>2</sup>C two-wire bus. AC and DC gray scale voltages are generated by the gray scale ASIC U<b>8</b>. Additional LCD supply voltages of +3V, +5V, +15V and −10V are generated by voltage regulators U<b>7</b> and U<b>10</b>. The light emitting diode (LED) backlighting brightness is controlled by switching regulator U<b>6</b>. The brightness is controlled by the duty cycle of the pulse width modulator (PWM) control signal from main processor U<b>21</b>. The LCD display control signals are brought out from the display module by means of a 39-conductive flex flat cable which connects to the connector P<b>6</b>. The display back light LEDs are brought out from the module with a four conductive flex flat cable which connects to connector P<b>7</b>.
p-0096The main processor <b>71</b> (U<b>21</b>) may be an ARM-9 architecture processor from the Freescale Company with manufacturing number PN MC9328MX21VM. This processor has the many onboard peripherals that are needed including for example the LCD controller, multiple UART ports, I<sup>2</sup>C ports, external memory bus, memory management unit, multiple PWM outputs, low power shutdown modes, key scan and key debounce, to name a few of the components of the processor that are utilized in the communicator of the instant invention.
p-0097In the memory module <b>76</b>, there are three different types of memories, two 8 Mb×16 SDRAM (Synchronous Dynamic RAM) at 1.8V as designated by U<b>19</b> and U<b>20</b>, one 2 Mb×16 FLASH (non-volatile memory) at 1.8V designated by U<b>22</b>, and one 1 Mb serial EEPROM (Electrically Erasable PROM) at 2.7V. The program code and non-volatile trend data are stored in the Flash memory. At power-up the program code is transferred from the slower Flash memory to the higher speed SDRAM to support faster processor operation. The non-volatile serial EEPROM is used to store system event logs, system serial number, and other systems information. The non-volatile Serial Flash Memory is used for trend data storage. The display memory is executed out of the SDRAM memory space.
p-0098The audio module <b>78</b> supports audio alarms per the 60601-1-8 Alarm standard for medical devices. Due to the volume and tonal qualities dictated by the Alarm standard, a conventional voice coil speaker is used to generate the needed sounds, as opposed to using a piezoelectric type transducer. Main processor U<b>21</b> generates a pulse width modulated (PWM) control signal with 11-bits of resolution to control both pitch and volume of the alarm signal. The signal conditioning circuitry U<b>18</b> filters this PWM stream into an analog audio signal which in turn is amplified by a class D audio amplifier U<b>15</b>. U<b>15</b> differentially drives an 8-ohm speaker in the conventional bridge tide load (BTL) configuration for maximum efficiency.
p-0099The radio circuit <b>80</b> has a radio module RF<b>1</b> that may be a single board transceiver radio and PCB antenna designed to operate in accordance with the IEEE 802.15.4 Low Data Rate Wireless Personal Area Network (WPAN) standard. The radio module hardware is supplied by the L.S. Research company, located in Cedarburg, Wis., under the product name Matrix having a manufacturing number PN MTX12-101-MTN26. The matrix module is a 2.4 GHz 802.15.4 based module that is designed for proprietary and ZigBee (a low power, wireless networking standard) data transceiver applications. The processor and transmitter of the matrix module may be based on an integrated module such as for example the Texas Instrument CC2430 chip.
p-0100With reference to <figref idrefs="DRAWINGS">FIG. 15</figref>, a more detailed exemplar wireless finger oximeter sensor corresponding to that in <figref idrefs="DRAWINGS">FIG. 5</figref> is shown. Components that are the same as those in FIG. <b>5</b> are labeled the same here. The oximeter sensor <b>22</b> in <figref idrefs="DRAWINGS">FIG. 15</figref> is shown to include an oximeter module <b>26</b> and a radio module <b>28</b>. In the oximeter module <b>26</b> there is a memory <b>26</b><i>a</i>, a controller <b>26</b><i>b </i>and a sensor circuit <b>26</b><i>c</i>. The sensor circuit is connected to and provides the power to a light source emitter <b>26</b><i>d </i>as well as a detector <b>26</b><i>e</i>. The light emitter and the detector work in combination to detect or monitor the oxygen saturation in the blood of a patient connected to the emitter and detector. The data collected from the patient is stored in memory <b>26</b><i>a</i>. The overall operation of the oximeter module is controlled by controller <b>26</b><i>b. </i>
p-0101Radio module <b>28</b> has a memory <b>28</b><i>a</i>, a controller <b>28</b><i>b</i>, a transceiver <b>28</b><i>c</i>, an analog circuit <b>28</b><i>d </i>and an antenna <b>28</b><i>e</i>. The operation of the radio module <b>28</b> for the oximeter sensor device is similar to that discussed with respect to the communicator. However, in most instances, only data that is collected and stored in the oximeter module <b>26</b> is transmitted out by the radio transmitter. However, given that transceiver <b>28</b><i>c </i>is adapted to receive signals as well as to send out signals, radio module <b>28</b> of the oximeter sensor device <b>22</b> may be able to receive a signal from a remote source, for example a communicator, so as to receive instructions therefrom. One such instruction may be a sleep instruction sent by a communicator to instruct the oximeter to go into the sleep mode. Another possible instruction may be an awake instruction to wake the oximeter sensor from its sleep mode and to begin monitor the SP02 of the patient. As was discussed with respect to the timed functions illustrated in <figref idrefs="DRAWINGS">FIG. 12</figref>, the oximeter sensor device is adapted to receive a transmission from a communicator to which it is designated, so that it may be synchronized with the communicator, before data collected from the patient by the oximeter sensor is transmitted to the communicator.
p-0102Power is provided to the oximeter and radio modules of the oximeter sensor device <b>22</b> by power circuit <b>30</b>, which regulates the power from a battery <b>30</b><i>a</i>. In most instances, the oximeter sensor device <b>22</b> is worn by the patient, with the sensor being specifically placed about a digit, such as for example the finger, of the patient. Other types of sensors such as for example reflective sensors that are attached to the forehead of a patient may also be used.
p-0103In operation, the processor controller <b>26</b><i>b </i>in oximeter module <b>26</b> controls an analog sensor circuit that samples the serially incoming analog waveform signal that corresponds to the being measured physical parameter of the patient. A program is processed by controller <b>26</b><i>b </i>to compute the digital oximetry data from the sampled analog waveform obtained from sensor circuit <b>26</b><i>c</i>. This digital data is then communicated to radio module <b>28</b>, which transmits the data to the communicator that is within its transmission area, so that the data may be displayed by the communicator. Although the protocol utilized by radio module <b>28</b> is the same as that used by the radio module of the communicator, there may be hardware differences between the radio module in the oximeter sensor device and the radio module in the communicator. This is due to for example the omission of the power amplifier and the strengthening of the antenna because of the size versus performance tradeoffs that are necessary for the oximeter sensor device.
p-0104The major transition states of the radio module, based on RF interrupts—such as for example start, receive and micro controller control—is shown in <figref idrefs="DRAWINGS">FIG. 16</figref>. As shown, there are four primary states or modes. These are: idle state <b>82</b>, receive state <b>84</b>, transmit state <b>86</b>, and sleep state <b>88</b>. There is also an initialization state <b>90</b> required for the proper operation of the radio after a hard reset. In the idle state <b>82</b>, the radio listens and upon detection of a proper RF signal, it begins to receive the incoming data. Upon command, the radio enters into the transmit state <b>86</b> where a buffered data packet is communicated over the RF interface out to the broadcast range of the radio. The sleep mode <b>88</b> allows the radio to operate at low power without losing its settings. The radio can be turned off in any state.
p-0105<figref idrefs="DRAWINGS">FIGS. 17-21</figref> are flow charts illustrating the operation of the communicator of the instant invention.
p-0106In <figref idrefs="DRAWINGS">FIG. 17</figref>, the radio module enters into the receive mode in step <b>92</b>. This receive step follows the radio protocol and any additional software control. Upon detecting a fiducial signal, the controller of the radio records its current time, per step <b>94</b>. Note that the fiducial signal is defined in the IEEE 802.15.4 standard as the start frame delimiter detection signal, and should have a relatively consistent time behavior. In step <b>96</b>, a determination is made to verify whether the received packet is intended for the particular device, i.e., whether there is proper designation address and format. If the message is not intended for this particular radio, then the process returns to an idle state, per step <b>98</b>. At that time, the message deemed not to be intended for the radio causes the radio to stop receiving data and to discard the data it has already received, before returning to the idle state. If the determination made in step <b>96</b> verifies that the message indeed is intended for the radio, then the process proceeds to step <b>100</b> where the message is received and buffered into the local memory of the radio. In step <b>102</b>, a determination is made on whether the received message is to be used for synchronization. If it is not, the process proceeds to step <b>104</b> where the message is sorted. But if the message indeed is meant for synchronization, then the process proceeds to step <b>106</b> where the slot timer is updated based on the time of the fiducial signal, before the message gets sorted in step <b>104</b>. Thereafter, the message is buffered appropriately in step <b>108</b> so that it may be serially transmitted to the host of the radio. Thereafter, the radio returns to its idle state per step <b>98</b>.
p-0107<figref idrefs="DRAWINGS">FIG. 18</figref> is a flowchart illustrating the transmit process of the radio of the communicator. The radio starts transmitting upon command from the radio micro-controller. This is step <b>110</b>. In this step, the micro-controller will signal the start of its time slot based upon the scheduling and the synchronized timing. Upon the start of a slot, the radio may update its slot timer, per step <b>112</b>. This may be important if there is a single node in the network, (i.e., the communicator is not in the transceiving range of other communicators but is within the broadcast range of the wireless oximeter sensor), and the initialization protocol requires for regular broadcasting of messages. In step <b>114</b>, a determination is made on whether there is data to be transmitted for a given time slot. If there is not, the process returns to the radio idle state, per step <b>116</b>. If there is, the data is transmitted per step <b>118</b>. In step <b>120</b>, a determination is made on whether the time slot is long enough for another transmission. If it is, the process returns to step <b>114</b> to retrieve additional data for transmission. The process continues so long as there is enough time for transmitting more messages. If it is determined that there is no longer enough time for a next transmission in step <b>120</b>, the process returns the radio to its idle state, per step <b>116</b>, where the radio awaits the next transmit, receive or sleep instruction.
p-0108The aggregate and broadcast processes for the communicators are illustrated in the flow charts of <figref idrefs="DRAWINGS">FIGS. 19 and 20</figref>, respectively. In <figref idrefs="DRAWINGS">FIG. 19</figref>, the host processor of the communicator receives the RDD message, or other aggregate and forward type messages, from the radio, per step <b>122</b>. The received data is then compared with the previously stored, or local copy of the message stored in the memory of the radio, per step <b>124</b>. In step <b>126</b>, a determination is made on whether the receive data is newer than the previously stored data. If it is, the local memory is updated with the received RDD message per step <b>128</b>. The display on the communicator may be updated per step <b>130</b>. The process then stops per step <b>132</b> until there is a next start. If in step <b>126</b> it is determined that the data received is not newer than the previously stated data, the aggregate process exits to step <b>132</b> to await the next incoming RDD message.
p-0109<figref idrefs="DRAWINGS">FIG. 20</figref> is a flow chart illustrating the forward process for the communicator of the instant invention. Per step <b>134</b>, the RDD table (which also includes the HS data and similar aggregate and forward messages) is updated with the local pulse oximetry data. In step <b>136</b>, any new local pulse oximetry data is retrieved and readied. In step <b>138</b>, the RDD message is updated. The process then exits per step <b>140</b>.
p-0110In <figref idrefs="DRAWINGS">FIG. 21</figref>, the processing steps for aggregating and forwarding the data to the radio module from the main processor of the communicator is illustrated. Starting at step <b>142</b>, the data for the radio module is updated. Thereafter, in step <b>144</b>, the messages are queued for the radio module. A decision is made on whether there is additional data in step <b>146</b>. If there is, the additional data is serially transmitted to the radio module per step <b>148</b>. The process continues until a determination is made, per step <b>146</b>, that there is no more data to be routed to the radio. At which time, the process is routed to step <b>150</b> and the aggregating and forwarding process ends.
p-0111<figref idrefs="DRAWINGS">FIG. 22</figref> is a flow chart that illustrates the operations of the wireless oximeter. So that power is conserved, as was noted above, the wireless oximeter sensor begins in a radio sleep mode. The process therefore begins at step <b>152</b> where the oximeter is awaken by either an external signal or an internal timer interrupt, as was discussed previously. The radio of the oximeter then goes into an idle state per step <b>154</b>. From the idle state, the radio may receive data, be synchronized and returns to the idle state. These processes start with step <b>156</b> where the start frame delimiter (SFD) is reviewed to capture the time, per discussion with reference to <figref idrefs="DRAWINGS">FIGS. 11 and 12</figref>. If it is determined that the SFD is not for the oximeter in step <b>158</b>, then the process returns to the idle state in step <b>154</b> to await the SFD that designates or identifies the oximeter sensor as the one. If the oximeter determines that it is the correct sensor to be communicating with the communicator, the process proceeds to step <b>160</b> where it receives the message. If the message is determined to be the synchronization message, per step <b>162</b>, then the slot timer is updated per step <b>164</b> to synchronize the oximeter with the communicator. The process then proceeds to step <b>166</b> where the messages oncoming are buffered. The same buffering process also takes place if the message is determined not to be a synchronization message. Thereafter, the process returns to the radio idle state, per step <b>168</b>.
p-0112The oximeter remains in the idle state until a start RF transmission interrupt or command is received per step <b>170</b>. At that time, the slot timer is updated per step <b>172</b>. In step <b>174</b>, the process determines whether there is data for transmission. If there is, the data is transmitted per step <b>176</b>. A determination is next made, per step <b>178</b>, on whether there is enough time for transmitting the next message. If there is, the process returns to the step <b>174</b> to retrieve the next message, and transmits the retrieved message per step <b>176</b>. The process repeats until it is determined, per step <b>178</b>, that there is no longer enough time for the next message. At which time the process returns to the idle state per step <b>180</b>. The process also goes into the idle state if it was determined in step <b>174</b> that there was no data for transmission. After the idle state, the process may receive further commands per step <b>182</b>. Thereafter, as the radio and oximeter are independently powdered, to conserve power, the radio is put to sleep per step <b>184</b> until it is awakened.
p-0113It should be appreciated that the present invention is subject to many variations, modifications and changes in detail. For example, even though the disclosed network, system and devices have been discussed with reference to a medical instrumentation environment, it should be appreciated that such network, system and devices are equally adaptable to operate in a non-medical setting. Thus, it is the intension of the inventors that all matter described throughout this specification and shown in the accompanying drawings be interpreted as illustrative only and not in a limiting sense. Accordingly, it is intended that the invention be limited only by the spirit and scope of the hereto appended claims.
Contents5
21 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2017172478A1 | Cited by | United States of America | Search report |
| US10028220B2 | Cited by | United States of America | Applicant |
| US10492684B2 | Cited by | United States of America | Applicant |
| US10536901B2 | Cited by | United States of America | Applicant |
| US10455368B2 | Cited by | United States of America | Applicant |
| WO2016123249A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US10602987B2 | Cited by | United States of America | Applicant |
| US9706489B2 | Cited by | United States of America | Applicant |
| US10545132B2 | Cited by | United States of America | Applicant |
| CN110196563A | Cited by | China | Search report |
| US10667688B2 | Cited by | United States of America | Applicant |
| US10506926B2 | Cited by | United States of America | Applicant |
| US11504014B2 | Cited by | United States of America | Applicant |
| US2002069885A1 | Cites | United States of America | Pre-grant |
| US2002082665A1 | Cites | United States of America | Pre-grant |
| US2003110291A1 | Cites | United States of America | Pre-grant |
| US2003181798A1 | Cites | United States of America | Pre-grant |
| US2004023651A1 | Cites | United States of America | Pre-grant |
| US2004107A | Cites | United States of America | Pre-grant |
| US2005011738A1 | Cites | United States of America | Pre-grant |
| US2005122469A1 | Cites | United States of America | Pre-grant |
| US2005197550A1 | Cites | United States of America | Pre-grant |
| US2006007882A1 | Cites | United States of America | Pre-grant |
| US2006056363A1 | Cites | United States of America | Pre-grant |
| US2006202816A1 | Cites | United States of America | Pre-grant |
| US2006253301A1 | Cites | United States of America | Pre-grant |
| US2006276714A1 | Cites | United States of America | Pre-grant |
| US2007030116A1 | Cites | United States of America | Pre-grant |
| US2007060802A1 | Cites | United States of America | Pre-grant |
| US2007090946A1 | Cites | United States of America | Pre-grant |
| US2007135866A1 | Cites | United States of America | Pre-grant |
| US2007180140A1 | Cites | United States of America | Pre-grant |
| US2007255250A1 | Cites | United States of America | Pre-grant |
| US2007258395A1 | Cites | United States of America | Pre-grant |
| US2007262863A1 | Cites | United States of America | Pre-grant |
| US2008004538A1 | Cites | United States of America | Pre-grant |
| US2008221420A1 | Cites | United States of America | Pre-grant |
| US2008272918A1 | Cites | United States of America | Pre-grant |
| US5839439A | Cites | United States of America | Pre-grant |
| US5944659A | Cites | United States of America | Pre-grant |
| US6539947B2 | Cites | United States of America | Pre-grant |
| US7156807B2 | Cites | United States of America | Pre-grant |
85 members in 12 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 90798007 | United States of America | A | |
| US20070907980 | – | – | – |
Members85
| Document | Office | Kind | |
|---|---|---|---|
| AU2008314638A1 | Australia | A1 | |
| AU2008314639A1 | Australia | A1 | |
| AU2008314640A1 | Australia | A1 | |
| AU2008314641A1 | Australia | A1 | |
| AU2008314642A1 | Australia | A1 | |
| CA2702387A1 | Canada | A1 | |
| CA2702388A1 | Canada | A1 | |
| CA2702389A1 | Canada | A1 | |
| CA2702390A1 | Canada | A1 | |
| CA2702391A1 | Canada | A1 | |
| US2009103469A1 | United States of America | A1 | |
| US2009105549A1 | United States of America | A1 | |
| US2009105566A1 | United States of America | A1 | |
| US2009105567A1 | United States of America | A1 | |
| WO2009051828A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009051829A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009051830A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009051831A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009051832A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200919386A | Taiwan Province of China | A | |
| TW200919990A | Taiwan Province of China | A | |
| TW200920309A | Taiwan Province of China | A | |
| TW200924709A | Taiwan Province of China | A | |
| TW200924710A | Taiwan Province of China | A | |
| US2010094098A1 | United States of America | A1 | |
| EP2200500A1 | European Patent Office (EPO) | A1 | |
| EP2200501A1 | European Patent Office (EPO) | A1 | |
| EP2200502A1 | European Patent Office (EPO) | A1 | |
| EP2200503A1 | European Patent Office (EPO) | A1 | |
| EP2200504A1 | European Patent Office (EPO) | A1 | |
| KR20100080806A | Republic of Korea | A | |
| KR20100080807A | Republic of Korea | A | |
| KR20100091947A | Republic of Korea | A | |
| KR20100096062A | Republic of Korea | A | |
| KR20100096063A | Republic of Korea | A | |
| IL205065A0 | Israel | A0 | |
| IL205067A0 | Israel | A0 | |
| IL205068A0 | Israel | A0 | |
| IL205069A0 | Israel | A0 | |
| IL205070A0 | Israel | A0 | |
| CN101902953A | China | A | |
| CN101902954A | China | A | |
| CN101902955A | China | A | |
| CN101902956A | China | A | |
| CN101902957A | China | A | |
| JP2011500205A | Japan | A | |
| JP2011500206A | Japan | A | |
| JP2011500207A | Japan | A | |
| JP2011501683A | Japan | A | |
| JP2011504114A | Japan | A | |
| RU2010119938A | Russian Federation | A | |
| RU2010119939A | Russian Federation | A | |
| RU2010119940A | Russian Federation | A | |
| RU2010119941A | Russian Federation | A | |
| RU2010119942A | Russian Federation | A | |
| US8134459B2 | United States of America | B2 | |
| CN101902953B | China | B | |
| CN101902956B | China | B | |
| CN101902957B | China | B | |
| CN101902954B | China | B | |
| AU2008314640B2 | Australia | B2 | |
| US8373557B2 | United States of America | B2 | |
| JP5432160B2 | Japan | B2 | |
| JP5432161B2 | Japan | B2 | |
| JP5432162B2 | Japan | B2 | |
| JP5450429B2 | Japan | B2 | |
| JP5450430B2 | Japan | B2 | |
| AU2008314638B2 | Australia | B2 | |
| CN101902955B | China | B | |
| BRPI0817829A2 | Brazil | A2 | |
| BRPI0817996A2 | Brazil | A2 | |
| BRPI0818607A2 | Brazil | A2 | |
| EP2200501A4 | European Patent Office (EPO) | A4 | |
| EP2200504A4 | European Patent Office (EPO) | A4 | |
| KR101572278B1 | Republic of Korea | B1 | |
| KR101572279B1 | Republic of Korea | B1 | |
| KR101574812B1 | Republic of Korea | B1 | |
| EP2200500A4 | European Patent Office (EPO) | A4 | |
| EP2200502A4 | European Patent Office (EPO) | A4 | |
| EP2200503A4 | European Patent Office (EPO) | A4 | |
| KR101637044B1 | Republic of Korea | B1 | |
| BRPI0819098A2 | Brazil | A2 | |
| BRPI0819099A2 | Brazil | A2 | |
| US9949641B2 | United States of America | B2 | |
| US9986911B2 | United States of America | B2 |
76 transactions on the USPTO file
Allowed after 3 non-final rejections, 2 final rejections, 1 RCE and 1 appeal.
- Non-final rejections
- 3
- Final rejections
- 2
- RCEs
- 1
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Correspondence Address ChangeC.ADB | C.ADB | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief FiledAP.B | AP.B | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Notice of Appeal FiledN/AP | N/AP | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Terminal Disclaimer FiledDIST | DIST | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Is Now CompleteCOMP | COMP | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW | CORRDRW | |
| Corrected PaperCPAP | CPAP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2009103469
- Publication, EPODOC
- US2009103469
- Application
- 11907980
- Application, DOCDB
- 90798007
- Application, EPODOC
- US20070907980
Titles
- English
- Method for establishing a telecommunications network for patient monitoring
Classification
- CPC, 5
- A61B5/14551
- H04W88/04
- A61B5/002
- G16H40/20
- G16H40/67
- IPC, 2
- G16H40 67
- H04B7 14
- USPC, 1
- 370315000