Patient monitoring systems and messages that send alerts to patients

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation of U.S. patent application Ser. No. 13/955,810, filed Jul. 31, 2013, which is a continuation in part of U.S. Ser. No. 13/923,909, U.S. Ser. No. 13/923,637, U.S. Ser. No. 13/923,614, U.S. Ser. No. 13/923,809, U.S. Ser. No. 13/923,750, U.S. Ser. No. 13/923,583, U.S. Ser. No. 13/923,560, U.S. Ser. No. 13/923,543, and U.S. Ser. No. 13/923,937, all filed Jun. 21, 2013 and all of which claim the benefit of U.S. 61/772,265, U.S. 61/812,083 and 61/823,502. All of the above-identified applications are fully incorporated herein by reference.

BACKGROUND OF THE INVENTION

00021. Field of the Invention

0003The present invention is directed to patient monitoring devices and telemetry systems, and more particularly to intelligent, patient monitoring devices with unique ID's for each patient that sends alerts to patients only when the patient is awake.

00042. Description of the Related Art

0005Patient monitoring was accomplished by electronic equipment maintained at the patient's bedside. Vital signs derived from physiological waveforms were monitored with the bedside equipment and alarms were generated if predetermined limits were exceeded by the vital signs. This bedside monitoring equipment became larger, more complex and expensive as each bedside unit undertook to monitor more physiological data and provide more sophisticated displays, e.g. color, more and better communications and more in-depth analysis of the data, such as calculation of vital signs and trends which required memory and processing capability. The provision of such units at each appropriate patient bedside introduces considerable additional expense to the hospital patient care costs.

0006With the introduction of bedside monitoring units, attempts were made to provide a measure of remote monitoring by transmitting analog waveforms of physiological data from the bedside unit to equipment at a central station such as a nurse's station. Subsequently remote monitoring efforts included analog waveforms plus digital representations for display. Both the bedside and remote monitoring activity acted to give alarms upon sensing an abnormal condition and to store data and analyze data to obtain vital signs and trends. But these systems are basically one-way systems reporting physiological data from the patient. There is no communication with the patient as a part of an interactive integrated system.

0007Telemetry systems can be implemented to acquire and transmit data from a remote source. Some telemetry systems provide information about a patient's activities.

0008It is becoming commonplace to use wireless packet data service networks for effectuating data sessions with. In some implementations, unique identifications (ID) need to be assigned to the devices in order to facilitate certain aspects of service provisioning, e.g., security, validation and authentication, et cetera. In such scenarios, it becomes imperative that no two devices have the same indicium (i.e., collision). Further, provisioning of such indicia should be flexible so as to maintain the entire pool of indicia to a manageable level while allowing for their widespread use in multiple service environments.

0009Medical telemetry systems may comprise an alarm adapted to identify high risk patients and/or patients requiring special assistance. Some medical procedures and diagnostic examinations require the removal of any telemetry system components attached directly to a patient. One problem with conventional medical telemetry systems is that the process of removing telemetry system components for purposes of performing a medical procedure or diagnostic examination can generate a false alarm. False alarms unnecessarily tax hospital resources and interfere with the working environment.

0010There is a need for telemetry devices configured to be used in patient monitoring. There is a further need for monitoring devices that send alerts to patients only when the patient is awake.

SUMMARY OF THE INVENTION

0011An object of the present invention is to provide improved patient monitoring systems, and their methods of use.

0012Another object of the present invention is to provide a system, and its associated methods of use, that includes a patient monitoring device that gathers telemetry data based on a patient's habits, patient condition or patient parameter in communication with a telemetry system, that sends alerts to the patient only when the patient is awake.

0013A further object of the present invention is to provide systems, and their associated methods of use, that use a patient monitoring device or system that measures and tracks everything from a patient's movements and activities, to habits, lifestyle choices, health and social interactions, and only sends to alerts to the patient when the patient is alert.

0014Yet another object of the present invention is to provide telemetry systems, and their associated methods of use, in communication with a patient monitoring device that creates a unique portrait of a patient, and provides personalized information and mapping of a patient's daily experience, with alerts only being sent to the patient when the patient is alert.

0015These and other objects of the present invention are achieved in a system for using telemetry data based on a patient habit information or patient monitoring. One or more patient monitoring devices has a unique patient ID. The one or more monitoring devices acquire patient information selected from of at least one of, a patient's activities, behaviors and habit information, and patient monitoring. ID circuitry is at the patient monitoring device. The ID circuitry includes ID storage, a communication system that reads and transmits the unique ID from an ID storage, a power source and a pathway system to route signals through the circuitry. An alarm is at the patient monitoring device that provides an alert only when the patient is in a wake-state. A telemetry system is in communication with the patient monitoring device. The telemetry system includes a database of patient ID's.

0016In another embodiment of the present invention, a method is provided for using telemetry data is acquired based on a patient habit information or patient monitoring. The patient information is selected from of at least one of, a patient's activities, behaviors and habit information, and patient monitoring. A unique ID of the patient is sent from the monitoring device to a telemetry system. An alert is sent when the patient is in a wake-state.

BRIEF DESCRIPTION OF THE DRAWINGS

0017<figref idref="DRAWINGS">FIGS. 1(<i>a</i>) and 1(<i>b</i>)</figref> illustrate one embodiment of a wearable device of the present invention, where one size fits all.

0018<figref idref="DRAWINGS">FIG. 2</figref> illustrates one embodiment of electronics that can be included in the wearable device.

0019<figref idref="DRAWINGS">FIG. 3</figref> illustrates one embodiment of a telemetry system of the present invention.

0020<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of the programming input schematic of the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0021<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of the system of programming the sensor/transmitter(s) comprising the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0022<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of the jam command and security/randomization bits of the secure sensor/transmitter array of <figref idref="DRAWINGS">FIG. 7</figref>.

0023<figref idref="DRAWINGS">FIG. 7</figref> is a logic circuit diagram of the sensor/transmitter programming input schematic in one embodiment of the present invention.

0024<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram of an embodiment of a computer implemented system for determining the location of a remote sensor utilizing the methods of the present invention.

0025<figref idref="DRAWINGS">FIG. 9</figref> is a block diagram illustrating one embodiment of a SNAPSHOT GPS receiver for use according to the present invention.

0026<figref idref="DRAWINGS">FIG. 10</figref> is a block diagram of a remote sensor shown in communication with two different external communication devices.

0027<figref idref="DRAWINGS">FIG. 11</figref> is a diagram of the active RF and RF backscatter antennas.

0028<figref idref="DRAWINGS">FIG. 12</figref> is a diagram of the encoding scheme for the symbols in the active RF protocol.

0029<figref idref="DRAWINGS">FIG. 13</figref> is a diagram of the packet structure in the IRDA protocol.

0030<figref idref="DRAWINGS">FIG. 14</figref> is a diagram of the encoding scheme in the IRDA protocol.

0031<figref idref="DRAWINGS">FIG. 15</figref> illustrates one embodiment of a wireless network that can be used with the present invention.

0032<figref idref="DRAWINGS">FIGS. 16(<i>a</i>)-16(<i>d</i>)</figref> illustrate various embodiments of the interaction of a wearable device of the present invention with an interaction engine, a transaction engine, a decoding engine, and a payment system and a third party.

0033<figref idref="DRAWINGS">FIG. 17</figref> illustrates an embodiment of a social network circle with social devices in accordance with one embodiment of the present invention.

0034<figref idref="DRAWINGS">FIG. 18</figref> illustrates an embodiment of a social group with a variety of members in accordance with one embodiment of the present invention.

0035<figref idref="DRAWINGS">FIG. 19</figref> is a functional block diagram illustrating a social network infrastructure and social devices in accordance with one embodiment of the invention.

0036<figref idref="DRAWINGS">FIG. 20</figref> illustrates a simplified block diagram of a client-server system and network in one embodiment of the present invention.

0037<figref idref="DRAWINGS">FIG. 21</figref> illustrates a more detailed diagram of an exemplary client or server computer that can be used in one embodiment of the present invention.

0038<figref idref="DRAWINGS">FIG. 22</figref> illustrates a system for activity collection and building a social graph including sharing activity between users in one embodiment of the present invention.

0039<figref idref="DRAWINGS">FIG. 23</figref> illustrates a social graph with nodes representing users and edges representing sharing activity between the users in one embodiment of the present invention.

0040<figref idref="DRAWINGS">FIG. 24</figref> illustrates a flow illustrating operation of an alarm in one embodiment of the present invention that sends alerts to the patient only when the patient is awake.

DETAILED DESCRIPTION

0041As used herein, the term engine refers to software, firmware, hardware, or other component that can be used to effectuate a purpose. The engine will typically include software instructions that are stored in non-volatile memory (also referred to as secondary memory). When the software instructions are executed, at least a subset of the software instructions can be loaded into memory (also referred to as primary memory) by a processor. The processor then executes the software instructions in memory. The processor may be a shared processor, a dedicated processor, or a combination of shared or dedicated processors. A typical program will include calls to hardware components (such as I/O devices), which typically requires the execution of drivers. The drivers may or may not be considered part of the engine, but the distinction is not critical.

0042As used herein, the term database is used broadly to include any known or convenient means for storing data, whether centralized or distributed, relational or otherwise.

0043As used herein a mobile device includes, but is not limited to, a cell phone, such as Apple's iPhone®, other portable electronic devices, such as Apple's iPod Touches®, Apple's iPads®, and mobile devices based on Google's Android® operating system, and any other portable electronic device that includes software, firmware, hardware, or a combination thereof that is capable of at least receiving the signal, decoding if needed, exchanging information with a transaction server to verify the buyer and/or seller's account information, conducting the transaction, and generating a receipt. Typical components of mobile device may include but are not limited to persistent memories like flash ROM, random access memory like SRAM, a camera, a battery, LCD driver, a display, a cellular antenna, a speaker, a BLUETOOTH® circuit, and WIFI circuitry, where the persistent memory may contain programs, applications, and/or an operating system for the mobile device.

0044As used herein, the terms “social network” and “SNET” comprise a grouping or social structure of devices and/or individuals, as well as connections, links and interdependencies between such devices and/or individuals. Members or actors (including devices) within or affiliated with a SNET may be referred to herein as “nodes”, “social devices”, “SNET members”, “SNET devices”, “user devices” and/or “modules”. In addition, the terms “SNET circle”, “SNET group” and “SNET sub-circle” generally denote a social network that comprises social devices and, as contextually appropriate, human SNET members and personal area networks (“PANs”).

0045A used herein, the term “wearable device” is anything that can be worn by an individual and that has a back side that in some embodiments contacts a user's skin and a face side. Examples of wearable device include but are not limited to a cap, arm band, wristband, garment, and the like.

0046As used herein, the term “computer” is a general purpose device that can be programmed to carry out a finite set of arithmetic or logical operations. Since a sequence of operations can be readily changed, the computer can solve more than one kind of problem. A computer can include of at least one processing element, typically a central processing unit (CPU) and some form of memory. The processing element carries out arithmetic and logic operations, and a sequencing and control unit that can change the order of operations based on stored information. Peripheral devices allow information to be retrieved from an external source, and the result of operations saved and retrieved.

0047As used herein, the term “Internet” is a global system of interconnected computer networks that use the standard Internet protocol suite (TCP/IP) to serve billions of users worldwide. It is a network of networks that consists of millions of private, public, academic, business, and government networks, of local to global scope, that are linked by a broad array of electronic, wireless and optical networking technologies. The Internet carries an extensive range of information resources and services, such as the inter-linked hypertext documents of the World Wide Web (WWW) and the infrastructure to support email. The communications infrastructure of the Internet consists of its hardware components and a system of software layers that control various aspects of the architecture.

0048As used herein, the term “extranet” is a computer network that allows controlled access from the outside. An extranet can be an extension of an organization's intranet that is extended to users outside the organization that can be partners, vendors, and suppliers, in isolation from all other Internet users. An extranet can be an intranet mapped onto the public Internet or some other transmission system not accessible to the general public, but managed by more than one company's administrator(s). Examples of extranet-style networks include but are not limited to: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0049">LANs or WANs belonging to multiple organizations and interconnected and accessed using remote dial-up</li><li id="ul0002-0002" num="0050">LANs or WANs belonging to multiple organizations and interconnected and accessed using dedicated lines</li><li id="ul0002-0003" num="0051">Virtual private network (VPN) that is comprised of LANs or WANs belonging to multiple organizations, and that extends usage to remote users using special “tunneling” software that creates a secure, usually encrypted network connection over public lines, sometimes via an ISP</li></ul></li></ul>

0052As used herein, the term “Intranet” is a network that is owned by a single organization that controls its security policies and network management. Examples of intranets include but are not limited to: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0053">A LAN</li><li id="ul0004-0002" num="0054">A Wide-area network (WAN) that is comprised of a LAN that extends usage to remote employees with dial-up access</li><li id="ul0004-0003" num="0055">A WAN that is comprised of interconnected LANs using dedicated communication lines</li><li id="ul0004-0004" num="0056">A Virtual private network (VPN) that is comprised of a LAN or WAN that extends usage to remote employees or networks using special “tunneling” software that creates a secure, usually encrypted connection over public lines, sometimes via an Internet Service Provider (ISP)</li></ul></li></ul>

0057As used herein, the term (patient monitoring) includes: (i) Cardiac monitoring, which generally refers to continuous electrocardiography with assessment of the patient's condition relative to their cardiac rhythm. A small monitor worn by an ambulatory patient for this purpose is known as a Holter monitor. Cardiac monitoring can also involve cardiac output monitoring via an invasive Swan-Ganz catheter (ii) Hemodynamic monitoring, which monitors the blood pressure and blood flow within the circulatory system. Blood pressure can be measured either invasively through an inserted blood pressure transducer assembly, or noninvasively with an inflatable blood pressure cuff. (iii) Respiratory monitoring, such as: pulse oximetry which involves measurement of the saturated percentage of oxygen in the blood, referred to as SpO2, and measured by an infrared finger cuff, capnography, which involves CO2 measurements, referred to as EtCO2 or end-tidal carbon dioxide concentration. The respiratory rate monitored as such is called AWRR or airway respiratory rate). (iv) Respiratory rate monitoring through a thoracic transducer belt, an ECG channel or via capnography, (v) Neurological monitoring, such as of intracranial pressure. Special patient monitors can incorporate the monitoring of brain waves electroencephalography, gas anesthetic concentrations, bispectral index (BIS), and the like, (vi) Blood glucose monitoring using glucose sensors. (vii) Childbirth monitoring with sensors that monitor various aspects of childbirth. (viii) Body temperature monitoring which in one embodiment is through an adhesive pad containing a thermoelectric transducer. (ix) Stress monitoring that can utilize sensors to provide warnings when stress levels signs are rising before a human can notice it and provide alerts and suggestions. (x) Epilepsy monitoring. (xi) Toxicity monitoring, and the like.

0058Additionally the present invention can be used to detect differences for a variety of blood tests, including but not limited to tests for the following: sodium, potassium, chloride, urea, creatinine, calcium, albumin, fasting glucose, amylase, carcinoembryonic antigen, glycosylated hemoglobin, hemoglobin, erthrocytes hemoglobin and the like.

0059For purposes of the present invention, the Internet, extranets and intranets collectively are referred to as (“Network Systems”).

0060For purposes of the present invention, the Internet, extranets and intranets collectively are referred to as (“Network Systems”).

0061In various embodiments, the present invention provides a patient monitoring device <b>10</b>, such as a wearable device, where one size fits all. As illustrated in <figref idref="DRAWINGS">FIGS. 1(<i>a</i>) and 1(<i>b</i>)</figref>, in one embodiment of the present invention, the patient monitoring device <b>10</b> include a plurality of magnets <b>12</b>, with adjacent magnets having opposite polarity, with a length suitable to be worn by all people. In one embodiment, the length of the patient monitoring device <b>10</b> can be 10-12 inches. The magnets <b>12</b> are positioned along an interior of the patient monitoring device <b>10</b> to be provided for good conformation to a user's wrist.

0062One or more sensors <b>14</b> are coupled to the patient monitoring device <b>10</b>. The sensors are measuring devices. As a non-limiting example, the measuring device or sensors <b>14</b> can include RTSS devices to detect a user's activities, motions, physical parameters, and the like, including but not limited to, a heart rate monitor, a body temperature probe, a conventional pedometer, an accelerometer and the like.

0063Alternatively, multifunctional sensors <b>14</b> which can perform all the aforementioned functions of RTSS may be attached or embedded in patient monitoring device <b>10</b>. In one embodiment, each sensor can be in communication and or connect electronically and/or RF to a telemetry module <b>16</b>. A variety of different sensors <b>14</b> can be utilized, including but not limited to, an accelerometer based sensor, and pressure based sensors, voltage resistance sensor, a radio frequency sensor, and the like, as recited above.

0064As a non-limiting example, an accelerometer, well known to those skilled in the art, detects acceleration and thus user activity. The accelerometer provides a voltage output that is proportional to the detected acceleration. Accordingly, the accelerometer senses vibration. This voltage output provides an acceleration spectrum over time; and information about loft time can be ascertained by performing calculations on that spectrum. A microprocessor subsystem, such as disclosed in U.S. Pat. No. 8,352,211, incorporated herein by reference, stores the spectrum into memory and processes the spectrum information to determine activity. Other examples of suitable accelerometer sensors are disclosed in EP 2428774 A1, incorporated herein by reference. Suitable pressure sensors are disclosed in EP 1883798 B1, incorporated herein by reference. A suitable voltage resistance sensor is disclosed in EP 1883798 B1, incorporated herein by reference. A suitable radio frequency sensor is disclosed in EP 2052352 B1, incorporated herein by reference.

0065Referring to <figref idref="DRAWINGS">FIG. 2</figref>, in various embodiments, the patient monitoring device <b>10</b>, also known as the patient monitoring device, can include a power source <b>24</b>, such a battery that can be rechargeable. The battery <b>24</b> can be put into a sleep state when not actively used in order to preserve power. A wake up feature allows the battery <b>24</b> and other electronics of the patient monitoring device <b>10</b> to “sleep” during non-use or and is initiated into the “wake up” mode by certain predestinated events.

0066In one embodiment, as illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, a telemetry system server <b>16</b> is coupled to a database <b>18</b>. Each patient monitoring device <b>10</b> is assigned its own unique identification, ID.

0067The data transmitted by the patient monitoring device <b>10</b> sensors <b>14</b> and its ID may be coded by appending a seed to digital data bits. As illustrated in <figref idref="DRAWINGS">FIG. 3</figref> central processor unit <b>20</b> (CPU) validates or rejects received upon detection of the seed string appended to the digital data bits. In the alternative, the digital data bits may be coded and decoded by applying a scrambling algorithm utilizing the seed. A programming device <b>22</b> may be configured to transmit data to a sensor <b>14</b>, also known as a patient monitoring device, utilizing a variety of alternative transmission means, including, for example, RF, IR, optical, and the like, or a magnetic loop/induction system.

0068In one embodiment, sensors <b>14</b> are configured to be shipped to users in a non-programmable mode with all programming already performed at the factory. A random seed may be communicated to the programming device <b>22</b> can a variety of different mechanisms, including but not limited to, via scanning a bar code, manual input, magnetic strip, random number generation, and the like.

0069Referring again to <figref idref="DRAWINGS">FIG. 2</figref>, in one embodiment, the patient monitoring device <b>10</b> includes a control unit <b>26</b> that puts the patient monitoring device <b>10</b> in a low power state. A monitoring system <b>28</b> can be included that remains active. The monitoring system <b>28</b> wakes up the electronics <b>30</b> in the patient monitoring device <b>10</b> from a low power state. The control unit <b>26</b> can be notified of awaking of the other components by the monitoring system <b>28</b>. The control unit <b>26</b> can set a status bit on the monitoring system <b>28</b> only when the battery <b>24</b> needs to be in a full power state. The control unit <b>26</b> then forces a power cycle.

0070Referring to <figref idref="DRAWINGS">FIG. 3</figref>, one embodiment of a telemetry system <b>32</b> is illustrated. The telemetry system <b>32</b> is in the communication with the sensors <b>14</b> and or patient monitoring device <b>14</b> and ID of the patient monitoring device <b>10</b> and can include one or more receivers <b>34</b>, a central server <b>36</b> with the CPU <b>20</b>. The telemetry system <b>32</b> can optionally include a display <b>42</b> and an alarm <b>44</b>. The telemetry system <b>32</b> receives information from sensors <b>14</b> and or the monitoring device of a user's habits, activities, and the like, and then processes this information. Patient monitoring device <b>10</b> with its unique ID and sensors <b>14</b> is assigned to a specific user in order to track and/or monitor that user. For illustrative purposes assume that three users A, B AND C are being tracked and monitored by the telemetry system <b>32</b>. It should, however, be appreciated that the telemetry system <b>32</b> may be implemented to track and/or monitor a much larger number of users.

0071In one embodiment of the present invention, radio frequency (RF) devices that are sensors <b>14</b> and/or chips may serve as the identifying devices. Each source, sensor <b>14</b>, ID and the like can carry a fixed radio frequency chip encoded with identifying data which may be correlated to the individual participants, parts or objects.

0072Telemetry system <b>32</b> of the present invention may include a Real-Time Location System (RTLS) <b>46</b> and Real-Time Sensing System (RTSS) <b>48</b> with RF technology. The RF technology may include active and/or passive RFID sensors <b>14</b> and an RF wireless array system as a receiver <b>34</b>. The RF technology in the RTLS <b>46</b> and RTSS <b>48</b> may include UWB technology (e.g., IEEE 802.15), WLAN technology (e.g., IEEE 802.11), SAW RFID positioning system technology, GPS technology, and the like.

0073The sensors <b>14</b> may communicate directly with each other and/or relay telemetry data directly to base receiving RF device(s) or base receivers <b>34</b>. The base receivers <b>34</b> may forward the telemetry data to a base computer either through a direct link or through a network. Alternatively the telemetry data may be forwarded to end user devices, including but not limited to, laptops, mobile devices and the like, either directly or through a network. The comprehensive telemetry system <b>32</b> using RF technologies such as UWB, ZigBee, Wi-Fi, GPS data system can be utilized as described above.

0074The readers/antennae may be interconnected using a LAN, such as Ethernet to provide a network communication infrastructure for the computers and servers. Active and passive RFID sensors <b>14</b> may be employed. The active sensors <b>14</b> (RFID) may have a two-way communication function, which allows the base computer system to dynamically manage the sensors <b>14</b>; vary update rates; send self-identification and telemetry data.

0075The active sensors <b>14</b> may employ dual-radio architecture. In one embodiment, active sensors <b>14</b> transmit radio pulses, which are used to determine precise two-dimensional or three-dimensional location and a conventional bi-directional radio, which is used as a control and telemetry channel with a sensor update rate.

0076The patient monitoring device <b>10</b> gathers telemetry data, communicates that data to a base station, BLUETOOTH® enabled device, or smart phone and the like. From the base station, the patient monitoring device <b>10</b> can receive firmware updates or via a BLUETOOTH® enabled device. The patient monitoring device <b>10</b> can receive updates wirelessly. The base station can receive firmware updates from Network Systems, take telemetry data from the patient monitoring device <b>10</b> and transfer it to Network Systems. Telemetry data received from the base station is analyzed by servers and presented to an end user. Any third party device can receive data from the patient monitoring device <b>10</b> wirelessly and deliver information to the servers for processing.

0077In one embodiment, the patient monitoring device <b>10</b> uses an accelerometer, gyroscope, GPS sensor, a BLUETOOTH® chip, and a heart rate monitor.

0078As a non-limiting example, for heart monitoring, the accelerometer, sensor <b>14</b>, determines when to sample the sensors <b>14</b> and to improve the accuracy of the heart rate monitor. The gyroscope detects movement and orientation and the GPS sensor is used to determine location of the user. A BLUETOOTH® chip allows the device to connect wirelessly to other third party devices.

0079As a non-limiting example, a heart rate monitor <b>14</b> detects the user's heart rate in order to accurately determine the user's activity level, behavioral patterns and the like.

0080An Artificial Intelligence (AI) or Machine Learning-grade algorithms is used to identify the user's activities, behaviors, behaviors and perform analysis. Examples of AI algorithms include Classifiers, Expert systems, case based reasoning, Bayesian networks, and Behavior based AI, Neural networks, Fuzzy systems, Evolutionary computation, and hybrid intelligent systems. A brief description of these algorithms is provided in Wikipedia and stated below.

0081Classifiers are functions that can be tuned according to examples. A wide range of classifiers are available, each with its strengths and weaknesses. The most widely used classifiers are neural networks, support vector machines, k-nearest neighbor algorithms, Gaussian mixture models, naive Bayes classifiers, and decision trees. Expert systems apply reasoning capabilities to reach a conclusion. An expert system can process large amounts of known information and provide conclusions based on them.

0082A case-based reasoning system stores a set of problems and answers in an organized data structure called cases. A case based reasoning system upon being presented with a problem finds a case in its knowledge base that is most closely related to the new problem and presents its solutions as an output with suitable modifications. A behavior based AI is a modular method of building AI systems by hand. Neural networks are trainable systems with very strong pattern recognition capabilities.

0083Fuzzy systems provide techniques for reasoning under uncertainty and have been widely used in modern industrial and consumer product control systems. An Evolutionary Computation applies biologically inspired concepts such as populations, mutation and survival of the fittest to generate increasingly better solutions to the problem. These methods most notably divide into evolutionary algorithms (e.g., genetic algorithms) and swarm intelligence (e.g., ant algorithms). Hybrid intelligent systems are any combinations of the above. It is understood that any other algorithm, AI or otherwise, may also be used. Examples of suitable algorithms that can be used with the embodiments of the present invention are disclosed in, EP 1371004 A4, EP 1367534 A2, US 20120226639 and US 20120225719, all incorporated fully herein by reference.

0084In various embodiments, the patient monitoring device <b>10</b> has additional features. In one embodiment, the patient monitoring device <b>10</b> changes color, via infrared LEDs, to accurately match the wearer's skin tone. This creates a seamless and more personal integration of technology into the user's daily life. In this embodiment, there is skin contact with the patient monitoring device <b>10</b>.

0085In another embodiment, the patient monitoring device <b>10</b> remotely reminds and can be used to administer medications. As a non-limiting example, the patient monitoring device <b>10</b> can inject adrenalin. In one embodiment, the patient monitoring device <b>10</b> has sleep pattern recognition based on movement and heart rate.

0086In various embodiments, the patient monitoring device <b>10</b> uses algorithms to determine activity type, behavioral patterns and user habits based on collected data.

0087In one embodiment, the patient monitoring device <b>10</b> uses the accelerometer information to improve the heart rate monitor. As a non-limiting example, the patient monitoring device <b>10</b> detects movement and speed. Addition of this data improves the accuracy of the heart rate monitor and corrects for any miscalculations in vibration, noise and skin color.

0088In one embodiment, velocity readouts and accelerometer data are used to measure when to sample heart rate. For example, if the patient monitoring device <b>10</b> registers zero velocity readout, the user is probably at rest or engaged in a passive activity. Thus, the patient monitoring device <b>10</b> knows not to sample heart rate. This results in conversation of time, energy and data storage.

0089User activity, performance and action can be based on the acceleration and angular velocity of the patient monitoring device <b>10</b>. In one embodiment, the patient monitoring device <b>10</b> has a feature where the patient monitoring device <b>10</b> authorizes third party interaction based on hand gesture, on previous interactions or patterns of behavior. As a non-limiting example, if one purchases a coke every day for the last two weeks, the patient monitoring device <b>10</b> can “orders” the person another one based on the prior history.

0090In one embodiment, the patient monitoring device <b>10</b> features near-by patient monitoring device <b>10</b> recognition that provides for other patient monitoring device <b>10</b> devices to be recognized within a particular vicinity and are able to share and transfer data between them. The patient monitoring device <b>10</b>'s data analysis and feedback can be based on current or previous sensor output. The patient monitoring device <b>10</b> can alert the user when to charge the patient monitoring device <b>10</b> and when it is the most convenient for the user.

0091In one embodiment, the patient monitoring device <b>10</b> provides feedback via color change. An outer shell of the patient monitoring device <b>10</b> can use visual feedback, including but not limited to pigment or color changes to indicate changes in user behavior or to prompt changes in user behavior. In one embodiment, the patient monitoring device <b>10</b> is flexible in shape. As a non-limiting example, if the user puts the patient monitoring device <b>10</b> over their hand it can expand or contract, morphing to change size and shape.

0092In one embodiment, the patient monitoring device <b>10</b> can have a sync feature for multiple bands at the same time.

0093In one embodiment, the patient monitoring device <b>10</b> has data transfer to an external device that can be included or not included in system <b>32</b>. Patient monitoring device <b>10</b> could be a data leaching device. For example, the user can relay information to someone else's device (intermediary device) to access Network Systems connected device.

0094In one embodiment, the patient monitoring device <b>10</b> can disable the recording of one or more sensors <b>14</b> based on location, acceleration (or lack thereof) and the like.

0095In one embodiment, the patient monitoring device <b>10</b> detects different types of transportation and activity based on sensor data. In one embodiment, patient monitoring device <b>10</b> can unlock doors or cars. The user can turn it on and off. As a non-limiting example, it can be turned off by having a capacitor switch on top and bottom and is placed in a way that one couldn't accidentally turn it off. As a non-limiting example, turning it off can be done by rotating the patient monitoring device <b>10</b> once.

0096In one embodiment, the patient monitoring device <b>10</b> recognizes the wearer based on biometric information, previous data, movement pattern, and the like. In one embodiment, the patient monitoring device <b>10</b> detects a new user based on an inability to match to user/usage patterns.

0097As non-limiting examples, a variety of different sensors <b>14</b> can be used such as, an altimeter, blood oxygen recognition, heart rate from wrist via sonar, Doppler, based on sound wave and movement, based on pressure, and the like. A pressure sensor <b>14</b> can be placed on a circulatory vessel such as a vein to detect pulse.

0098With the patient monitoring device <b>10</b> of the present invention, mechanical actions of the user can be triggered, recognized and evaluated.

0099As a non-limiting example, with multiple users and wearable devices <b>10</b>, a separate patient monitoring device <b>10</b> ID is assigned to each of the users A, B AND C, and thereafter the assigned transmitter/monitor <b>14</b> generates user activity data and/or user tracking data. For purposes of this disclosure, monitoring data is defined to include data acquired during the process of monitoring or evaluating a predefined characteristic. The user activity data tracks data from the sensors <b>14</b> is transferred to the receivers <b>34</b> via the wireless connections <b>38</b> represented by a dashed line.

0100A network of receivers <b>34</b> transfers the user activity and/or tracking data to system server <b>16</b> via connection <b>50</b>. System server <b>16</b> includes a processor <b>52</b> configured to process the user data in a known manner. For example, the processor <b>52</b> may convert raw user data acquired by the sensors <b>14</b> into more conveniently readable data.

0101As a non-limiting example, the display <b>42</b> can be implemented to graphically convey user information from system server <b>16</b> in a conveniently readable manner. As a non-limiting example, the user may be a cardiac patient with user monitoring data graphically conveyed as a conventional ECG plot comprising a sequence of P-waves, a QRS complexes and a T-waves. As another example, user tracking data may be graphically conveyed as an icon superimposed onto a map to indicate the user's relative location. Alarm <b>44</b> may be included in this embodiment.

0102In some embodiments, system <b>32</b> ID circuitry delivers a unique ID to the wearable device from database <b>18</b>. BLUETOOTH® chips can be coupled with other wearable devices <b>10</b> in the area. This data is then stored, as more fully explained in the following paragraph. The unique ID can be utilized for a variety of different applications including but not limited to payments, social networking and the like.

0103The ID circuitry of system <b>32</b> can include a number of system/components: unique ID storage, communication system, which reads and transmits the unique ID from the unique ID storage, battery <b>24</b> or power system that provides power to enable communication with the patient monitoring device <b>10</b>, a pathway system to route signals to through the circuitry, a cluster that crunches information, and a control system, to orchestrate the communication between different systems. All of these systems can be implemented in hardware, software or a combination thereof. Continuing with the telemetry system <b>32</b>, sensors <b>14</b> and sensing devices are disposed on wearable devices <b>10</b> worn by users. Data, such as movement, location, speed, acceleration, and the like, can be acquired, captured and provided to system <b>32</b>.

0104System <b>32</b> and an associated network can include an identification reference, including user activity, performance and reference information for each individual sensor <b>14</b> and location.

0105The user activity, performance metrics, data and the like captured by system <b>32</b> can be recorded into standard relational databases SQL server, and/or other formats and can be exported in real-time.

0106In various embodiments, the patient monitoring device <b>10</b> and/or system <b>32</b> are fully sealed and have inductively charges. All communication is done wirelessly.

0107In one embodiment, there are no electrical contacts, physical contacts or connections with the patient monitoring device <b>10</b>. The patient monitoring device <b>10</b> is seamless. The telemetry system <b>32</b> can include a microprocessor with CPU <b>20</b>, memory, interface electronics and conditioning electronics <b>33</b> configured to receive a signal from the sensors <b>14</b>. In one embodiment, all or a portion of the conditioning electronics <b>33</b> are at the patient monitoring device <b>10</b>.

0108In one embodiment, the CPU <b>20</b> includes a processor <b>52</b>, which can be a microprocessor, read only memory used to store instructions that the processor may fetch in executing its program, a random access memory (RAM) used by the processor <b>52</b> to store information and a master dock. The microprocessor is controlled by the master clock that provides a master timing signal used to sequence the microprocessor <b>52</b> through its internal states in its execution of each processed instruction. In one embodiment, the microprocessor <b>52</b>, and especially the CPU <b>20</b>, is a low power device, such as CMOS, as is the necessary logic used to implement the processor design. The telemetry system <b>32</b> can store information about the user's activity in memory.

0109This memory may be external to the CPU <b>20</b> but can reside in the RAM. The memory may be nonvolatile such as battery backed RAM or electrically erasable programmable read only memory (EEPROM). Signals from the sensors <b>14</b> can be in communication with conditioning electronics <b>33</b> that with a filter <b>35</b>, with scale and can determine the presence of certain conditions. This conditioning essentially cleans the signal up for processing by CPU <b>20</b> and in some cases preprocesses the information. These signals are then passed to interface electronics, which converts the analog voltage or currents to binary ones and zeroes understood by the CPU <b>20</b>. The telemetry system <b>32</b> can also provide for intelligence in the signal processing, such as achieved by the CPU <b>20</b> in evaluating historical data.

0110In one embodiment, the actions of the user wearing the patient monitoring device <b>10</b> with the unique ID can be used for different activities and can have different classifications at system <b>32</b>.

0111The classification can be in response to the user's location, where the user spends it time, with which the user spends its time, determination of working relationships, family relationships, social relationships, and the like. These last few determinations can be based on the time of day, the types of interactions, comparisons of the amount of time with others, the time of day, a frequency of contact with others, the type of contact with others, the location and type of place where the user is at, and the like. These results are stored in database <b>18</b>.

0112In one embodiment, the user wearing the patient monitoring device <b>10</b> can access this information from any place where data is presented to the user, including but not limited to mobile devices, the WEB, applications program identifiers, and the like.

0113As a non-limiting example, the patient monitoring device <b>10</b> communicates with a base station at system <b>32</b>. The patient monitoring device <b>10</b> can intelligently switch between data transfer and charging based on sensor readout. The patient monitoring device <b>10</b> can represent data based on connected devices.

0114In one embodiment, the patient monitoring device <b>10</b> has the capability of providing recommendations, popularity of locations or activities based on acquired data from the user.

0115In one embodiment, the patient monitoring device <b>10</b> has the capability of introducing the user to other people or users based on their data and the user's data.

0116In one embodiment, the patient monitoring device <b>10</b> can determine emotion of the user.

0117In one embodiment, the patient monitoring device <b>10</b> uses incremental data transfer via BLUETOOTH® and the like. The patient monitoring device <b>10</b> can transmit data through the inductive coupling for wireless charging. The user is also able to change the frequency of data transmission.

0118The patient monitoring device <b>10</b> can engage in intelligent switching between incremental and full syncing of data based on available communication routes. As a non-limiting example, this can be via cellular networks, WiFi, BLUETOOTH® and the like. In one embodiment, the patient monitoring device <b>10</b> has data storage. As a non-limiting example, storage of telemetry data on patient monitoring device <b>10</b> can be amounts up to about 16 mg.

0119In one embodiment, data transferred if it's in a selected proximity of a base station of system <b>32</b> or in proximity of an associated connected network. In one embodiment, the patient monitoring device <b>10</b> has a dynamic change of data capture frequency. The patient monitoring device <b>10</b> can be programmed to instantly change how often it samples any sensor <b>14</b> based upon the sensor data. Intelligent data sampling is based on sensor readout.

0120The patient monitoring device <b>10</b> can receive firmware updates via a base station <b>110</b> of system <b>32</b>. In one embodiment, the patient monitoring device <b>10</b> presents analyzed data and feedback on a website. In one embodiment, the patient monitoring device <b>10</b>'s software is based on unique human movement. The patient monitoring device <b>10</b> is able to identify its wearer based on the unique patterns of movement, location check-ins and daily habits of the user.

0121In one embodiment, the app can be used on a mobile device, including but not limited to a smart phone and the like.

0122In one embodiment, a breakdown of recounting data that has been collecting is presented for analysis of that data. Observation or recommendations can be presented based on historical information and live information. The importance of the data can be based on past user behavior.

0123In one embodiment, the patient monitoring device <b>10</b> has artificial intelligence. A wearable device processor <b>54</b> implements logic resources that exist on patient monitoring device <b>10</b>.

0124In one embodiment, patient monitoring device <b>10</b> engages in the routing of user information to third parties based on predefined rules, based on system <b>32</b> analysis.

0125In one embodiment, patient monitoring device <b>10</b> includes one or more processors <b>54</b> that implement intelligent algorithmic processing and transfer of information to third parties. Feedback can be provided to the end user that is based on visual, tactile, gesture information and the like.

0126The ID can be sent from the patient monitoring device <b>10</b> in a variety of different transmit modes, which may be provided as part of the firmware or software of an ID or sensor transmitter <b>14</b>, and which may be utilized selectively during the operation of said sensor transmitter <b>14</b>, may include ‘burst” transmit modes, wherein a burst of data information is transmitted, or “parcel” transmit modes, wherein timed data packets of data, which may, as desired, comprise partial data strings, are transmitted, and, if desired, repeated during time intervals. Further, the sensors <b>14</b> may have programmed therein diagnostic routines or other test modes which assist during manufacture and use, providing the operator with operational status and verification information on said sensor/transmitter <b>14</b>, as needed. Referring to <figref idref="DRAWINGS">FIG. 4</figref>, system <b>32</b> includes data base <b>18</b> which contains the desired transmitter, sensor, <b>14</b> personality data, as well as, the address/device ID bits for each patient monitoring device <b>10</b>.

0127In one embodiment, the initial programming of the patient monitoring device <b>10</b> for the ID, as well as optionally other personal information of the user, is done securely, as unauthorized future alteration of same thereafter can be utilized as a means of violating system integrity.

0128In one embodiment, an inductive field coil is used for programming the sensors <b>14</b> and ID of patient monitoring device <b>10</b>.

0129As illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the patient monitoring device <b>10</b> can include a sensor <b>14</b> with an output that be received by an amplifier <b>56</b> and decoded by an I/O decoder <b>58</b> to determine I/O logic levels, as well as, both clock and data information <b>60</b>. Many such methods are commonly available including ratio encoding, Manchester encoding, Non-Return to Zero (NRZ) encoding, or the like; alternatively, a UART type approach can be used. Once so converted, clock and data signals containing the information bits are passed to a memory <b>62</b>. Any of these connections provides a logical link from the system's database <b>18</b> to the sensor <b>14</b>, ID of the patient monitoring device <b>10</b>, as shown in <figref idref="DRAWINGS">FIG. 5</figref>.

0130In one embodiment, illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, the system <b>32</b> chooses the necessary programmable sensor functions and stores them into database <b>18</b>. In one embodiment, in order to insure that an unauthorized user cannot connect into and program patient monitoring device <b>10</b> the following procedure may be used:

0131Both the sensor <b>14</b> and receiver <b>34</b> contain an identical, repeatable pseudo randomization algorithm in ROM or in ASIC logic.

0132Referring to <figref idref="DRAWINGS">FIG. 6</figref>, the algorithm is applied to outgoing programming data <b>64</b> from system <b>32</b> and produces a number of security/randomization bits <b>66</b> that can be appended to the outgoing programming message or message <b>68</b> and sent to a sensor <b>14</b>.

0133Referring to <figref idref="DRAWINGS">FIG. 7</figref> the sensor <b>14</b> likewise applies this pseudo randomization algorithm as the security/randomization bits <b>66</b> to the outgoing programming data, now forming the incoming programming data <b>70</b> to sensor <b>14</b> and produces a several bit result in the shift register <b>71</b>. The scrambling algorithm is devised such that a small difference in the programming bit stream causes a great difference in the pseudo randomization result. As a non-limiting example, the present invention can use a 16 bit polynomial to produce this pseudo randomization.

0134Optionally, in one embodiment, before a sensor <b>14</b> accepts this programming, stored in an address and personality register <b>73</b>, both the pseudo random code, stored in data in a shift register <b>75</b> from system <b>32</b> and a sensor <b>14</b>, in a shift register <b>71</b> must match via a comparator ID, <b>77</b>, indicating unauthorized acceptance use. In addition to insuring authorized access, this process also insures that the data itself is correct. The longer the polynomial sequence used, the greater the security.

0135In one embodiment, spread spectrum or other RF transmission is used and can include programming to determine that the frequency or spread spectrum code is unique to the area. If a spread spectrum code, system code, or frequency channel is found to be occupied at a future time of use. Re-programming of the patient monitoring device <b>10</b> is then done with a new, unused spread spectrum code or system code or frequency channel can be selected, or, in the alternative, CPU <b>20</b>.

0136As illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, step “E” would include, for example, the step of the sensor <b>14</b>, inputting the programming message and saving a seed in memory <b>62</b>; with the sensor <b>14</b> utilizing the seed to code digital data bits transmitted.

0137As illustrated in <figref idref="DRAWINGS">FIG. 8</figref>, the location of a patient monitoring device <b>10</b> with the ID and sensors <b>14</b> can be determined. As a non-limiting example, in one embodiment the patient monitoring device <b>10</b> includes a sensor <b>14</b> that can provide a position signal having positioning data (e.g., raw GPD data or pseudo ranges) and the ID is transmitted from the patient monitoring device <b>10</b> to system server <b>16</b>. Server <b>16</b> receives the position signal and analyzes the signal to generate information representing the location of the patient monitoring device <b>10</b>. Server <b>16</b> transmits this location information to a client computer where the location of the patient monitoring device <b>10</b>, allowing a user to identify the location of the remote sensor <b>14</b>.

0138In one embodiment, the position signal transmitted by the remote sensor <b>14</b> can also include an emergency code. For example, in the event of an emergency, such as a medical emergency or otherwise, a user may press a “panic button” that can be on the patient monitoring device <b>10</b> or by use of a user's mobile device. Pressing the panic button may cause mobile device <b>74</b> to transmit an emergency signal to a cell site <b>76</b> where the emergency signal is relayed to server <b>16</b>. In response, server <b>16</b> can transmit Doppler information regarding in-view satellites, a fix command and a time trigger signal to the patient monitoring device <b>10</b>.

0139When the location of the patient monitoring device <b>10</b> has been determined, software running on server <b>16</b> configures server <b>16</b> such that a call or other signal is sent to a local emergency operator in the vicinity of remote sensor <b>14</b>. When the call or signal is received at the emergency operator station, the location of remote sensor <b>14</b> is transmitted and displayed. In some cases, where separate panic buttons are available for identifying medical, police, fire or other types of emergencies, the nature of the emergency is also displayed for the emergency operator. Based on this information, the emergency operator can initiate an emergency response by providing the location of remote sensor <b>14</b> to the required emergency service (police, fire department, ambulance service, etc.). In other embodiments, instead of or in addition to a position report for the remote sensor <b>14</b>, the emergency operator may also be provided with information which identifies an emergency response vehicle in close proximity to remote sensor <b>14</b>.

0140As illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, a sensor <b>14</b> of the patient monitoring device <b>10</b> can include a SNAPSHOT GPS receiver <b>72</b>. As described above, sensor <b>14</b> uses information transmitted from separately located base station <b>110</b>, mobile devices, computers, and other devices, to assist in determining the position of the remote sensor <b>14</b>, as more fully disclosed in U.S. Pat. No. 6,661,372, incorporated herein by reference.

0141As non-limiting examples, and as illustrated in <figref idref="DRAWINGS">FIG. 10</figref>, the sensors <b>14</b> can be a thermal transducer <b>78</b>, an acoustic transducer <b>80</b>, and a magnetic transducer <b>82</b>. It will be appreciated that the present invention is not limited The transducers <b>78</b>, <b>80</b>, and <b>82</b> in the patient monitoring device <b>10</b> can communicate with a microprocessor <b>84</b> also located in the patient monitoring device <b>10</b>. The patient monitoring device <b>10</b> can communicate with other devices via an RF transceiver <b>86</b>, an IRDA transceiver <b>88</b>, and/or an RF backscatter transceiver <b>90</b>. Each of the components in the patient monitoring device <b>10</b> receives power as necessary from the battery <b>24</b>, which may include the rechargeable battery.

0142The acoustic transducer <b>80</b> may include a microphone, a low-pass filter, a gain amplifier, and a threshold comparator. The acoustic transducer <b>80</b> may include an omnidirectional microphone, although any other suitable acoustic transducer device would suffice. The microphone may be a surface mount MEMS device that has a frequency range of 100 Hz to 10 kHz. A single MCP602 operational amplifier is used on the acoustic sensor to amplify and low-pass filter the acoustic signal from the microphone. Another operational amplifier is used to generate a voltage reference used for single biasing and detection. The microphone output is biased to the midway point between the circuit supply voltage and ground to allow for both positive and negative signal swings. The biased signal is filtered with a second order low-pass Butterworth filter to remove upper frequency noise. It is then amplified with an adjustable gain that is controlled by a digital resistor potentiometer. This digital resistor operates on an I2C bus and is controlled by the microprocessor <b>84</b>. Lastly, the amplified acoustic signal is threshold detected against a static voltage to detect sufficiently large acoustic signals. The digital output of the threshold detector is connected to the microprocessor <b>84</b> for processing.

0143The magnetic transducer <b>82</b> can include a magnetic sensor integrated circuit, a differential instrumentation amplifier, a low-pass filter, two gain amplifiers, and a threshold detector. The magnetic transducer <b>82</b> may include an NVE AA002-02 GMR (giant magneto resistive) field sensor, although any suitable magnetic sensor would suffice. This sensor has a saturation field of 15 Oe, a linear range of 0 to 10.5 Oe, and a sensitivity of 3 mV/V/Oe. Two MCP602 CMOS operational amplifiers are used on the magnetic sensor to amplify and low-pass filter the analog output signal. An INA122UA instrumentation amplifier is used as a difference amplifier for the differential output from the magnetic sensor. The magnetic sensor IC can be based on Spintronics technology. Its output includes a differential voltage pair proportional to the detected magnetic field. The differential voltage pair is amplified and converted to a single voltage by the instrumentation amplifier. The AC-coupled signal is then amplified and filtered with a low-pass filter to remove upper frequency noise and boost the low-voltage signal output. The signal is amplified a second time by an adjustable gain controlled by a digital resistor similar to the acoustic sensor. Lastly, the amplified magnetic signal is threshold detected against a static voltage, to detect sufficiently large changes in magnetic fields. The digital output of the threshold detector can be connected to the microprocessor <b>84</b> for processing.

0144A DS1803E-010 digitally controlled 10 kOhm variable resistor can be used in both the acoustic and magnetic sensor circuits. It is used to adjust the gain of one gain stage in each circuit. The digital resistor is controlled through an I2C interface. A LMV3931PWR comparator is also used in both the magnetic and acoustic sensor circuits for determining when a sufficiently strong sensor signal has been detected. It compares the analog sensor signal against the voltage reference and its output is tied to the microprocessor <b>84</b> for data collection.

0145The thermal transducer <b>78</b> may include a Burr Brown TMP 100NA/250 12-bit digital temperature sensor, although any suitable thermal sensor would suffice. The digital temperature sensor has an operating range of −55 to +120.degree. C., an accuracy of 0.5.degree. C. and a maximum resolution of 0.0625.degree. C.

0146Even though it is a 12-bit sensor, suitable results are achieved with only 9-bit conversions with only the 8 most significant bits used. The sensor has an I2C interface and is normally kept in sleep mode for low power operation. When directed by the microprocessor <b>84</b>, the thermal transducer can perform a 9-bit temperature conversion in 75 milliseconds.

0147The RF transceiver <b>86</b> may include an RF Monolithic DR3000 transceiver, although any suitable transceiver or separate transmitter and receiver <b>34</b> would suffice. This transceiver <b>86</b> allows for both digital transmission and reception. The transceiver <b>86</b> can have an operating frequency of 916.5 MHz and is capable of baud rates between 2.4 kbps and 19.2 kbps. It can use OOK modulation and has an output power of 0.75 mW. It also can use digital inputs and outputs for direct connection with the microprocessor <b>84</b>. The transceiver <b>86</b> can use an antenna <b>92</b> (<figref idref="DRAWINGS">FIG. 11</figref>) that may include a 17 mil thick plain steel electric guitar G-string cut to a length of 8.18 cm. It is used in a monopole over ground configuration and can require a matching circuit of one inductor and one capacitor. Alternatively, Frequency Shift Keying (FSK), Quadrature Phase Shift Keying (QPSK), or any other suitable modulation scheme may be utilized.

0148The IRDA transceiver <b>88</b> may include a Sharp GP2W0110YPS infrared transceiver, although any suitable IRDA compliant infrared transceiver would suffice. This transceiver <b>88</b> can be IRDA v1.2 compliant and in one embodiment has an operating range of 0.7 meters. In one embodiment, it is capable of 115.2 kbps data speeds.

0149The RF backscatter transmission device <b>90</b> may include circuitry available from Alien Technology (of Morgan Hill, Calif.) for receiving and transmitting signals via RF backscatter. Battery <b>24</b> may be a 3.6 volt ½ AA lithium battery with a capacity of 1.2 amp hours. The battery <b>24</b> can be a power source <b>24</b> that can include a Texas Instruments TPS76930 DBVT voltage regulator to regulate the output signal to 3 volts and with a maximum current of 100 mA. The voltage regulator can include a LDO.

0150The RF backscatter transceiver <b>86</b> in the patient monitoring device <b>10</b> communicates with an RF backscatter reader <b>94</b> such as a class 3 reader from Alien Technology. The reader <b>94</b> transmits data to the backscatter transceiver <b>90</b> of the patient monitoring device <b>10</b> by broadcasting encoded RF pulses and receives data back from the transceiver <b>86</b> by continually broadcasting RF energy to the sensor <b>10</b> and monitoring the modulated RF reflections from the sensor <b>10</b>.

0151The RF backscatter transceiver <b>90</b> can include a printed circuit board (PCB) patch antenna for RF reception, and RF modulation, a Schotky diode detector circuit, a comparator circuit for signal decoding, and a logic circuit for wake-up. The logic circuit monitors the incoming data, and when an appropriate wake-up pattern is detected, it triggers the microprocessor <b>84</b> so that data reception can begin. In one embodiment, the reader <b>94</b> has an operating frequency between 2402 MHz and 2480 MHz, and uses frequency hopping in this band to reduce noise interference. A modulation method used by the reader <b>94</b> can be On-Off Keying (OOK). In one embodiment, the transmission power is 1 watt. The operation of the reader <b>94</b> may be controlled by an external computer (not shown) as directed by Labview software via a RS-232 serial link.

0152The RF transceiver <b>86</b> can communicate with an external RF transceiver <b>96</b> such as a DR3000 transceiver from Radio Monolithics, Inc. In one embodiment, it operates at 916.5 MHz, uses OOK modulation, has a communication range of 100 meters line of sight, and a baud rate of 19.2 kbps. The active RF antenna <b>92</b> can be a quarter-wavelength monopole made from a guitar G-string and appropriate matching circuitry. Two control lines from the microprocessor <b>84</b> can be used to select the mode of operation, choosing from transmit, receive, and sleep. The active RF receiver <b>34</b> consumes the most power in receive mode compared to the other two communication links.

0153<figref idref="DRAWINGS">FIG. 6</figref> shows the relative positioning and shape of the active RF antenna <b>92</b> and the RF backscatter antenna <b>98</b>.

0154The IRDA transceiver <b>88</b> of the patient monitoring device <b>10</b> can communicate with an external IRDA transceiver <b>100</b> that may be identical to the IRDA transceiver <b>88</b>. Alternatively, the IRDA transceiver <b>100</b> can be one such as is provided in most personal digital assistants (PDA) as well as many other consumer devices. The IRDA communication link follows the standard IRDA signal and coding protocol and is modeled after a standard UART interface. In one embodiment, the IRDA transceiver <b>88</b> is capable of data speeds less than 115.2 kbps, and may only have a range of 0.7 meters for transmission. One advantage of the IRDA communication link is that it does not require any of the RF spectrums for operation, but it typically does require line-of-sight communication.

0155When any one of the transceivers <b>86</b>, <b>88</b> and <b>90</b> on the patient monitoring device <b>10</b> detect the beginning of valid data on their respective communication link, all other transceivers are disabled, thereby preventing the corruption of incoming data with the noise or partial data packets on the other communication links. However, if the data on the active transceiver proves to be erroneous, the other transceivers will be re-enabled if appropriate to allow normal operation to continue. If the data received by the active transceiver is valid, however, the other transceivers will remain disabled for several hundred milliseconds longer in the high probability that the next data packet will be transmitted on the same communication link. If, after this extended delay, no additional packets are received, then the other transceivers will be re-enabled as appropriate.

0156In one embodiment, the active RF protocol has no wake-up or synchronization packets, and the packets sent to and from the sensor are identical. In one embodiment, the format of an active RF packet is shown in <figref idref="DRAWINGS">FIG. 2</figref>. It can include a preamble to reset and spin-up the state machine of the RF receiver <b>34</b> and to properly bias the receiver's <b>34</b> data slicer/threshold detector for optimum noise rejection and signal regeneration, two framing bits to indicate the beginning and end of the data bytes, and the data bytes themselves.

0157Furthermore, the encoding scheme for the three symbols is shown in <figref idref="DRAWINGS">FIG. 12</figref>. The entire packet is DC balanced to maintain an optimal level on the data slicer/threshold detector and the receiver <b>34</b>. Data is sent most significant bit first.

0158The IRDA communication link can follow the standard IRDA protocol for bit encoding and UART protocol for byte transmission. Packets transmitted on the IRDA link can contain no preamble or framing bits, but they do have a header that contains two bytes. The first byte is an ASCII “I” which denotes the beginning of a valid IRDA packet. The second byte equals the number of preceding bytes in the packet. This value is used by the receiver <b>34</b> to determine when the entire packet has been received and processing of information can begin. The packet structure is shown in <figref idref="DRAWINGS">FIG. 13</figref> and the IRDA/UART encoding scheme is shown in <figref idref="DRAWINGS">FIG. 14</figref>.

0159The data bytes contained in a packet transmitted to the sensor <b>10</b> through any of the communication links conform to a packet format. The CMD section of a packet is a single byte that identifies the type of packet being sent. The CMD byte appears above the beginning and end of the packet and the two must be identical. The reason for including the redundant byte is to further eliminate the chance of a packet's CMD identifier being corrupted at the receiver <b>34</b>, even if the CHECKSUM is correct.

0160The PAYLOAD contains all of the data that must be sent to, or returned from, the sensor. The PAYLOAD is broken down into individual bytes with the overall number of bytes and their content dependent on the type of packet being sent.

0161The CHECKSUM is a 16-bit CRC that is performed on all bytes in the data packet excluding the end CMD byte in packets generated by the external device. The CHECKSUM is sent most significant byte first.

0162The transceivers <b>86</b>, <b>88</b> and <b>90</b> may be required to communicate over a greater distance than do the components described herein. Upgrading these components to be suitable for longer distance transmission is considered to be within the spirit of this invention. The type of transducer is not limited to the specific transducer types described herein. In addition, the logic described herein for arbitrating between which communication device to use to communicate with the outside world and which sensor data to provide at what time is but one possible approach to arbitration logic within such a remote sensor <b>10</b>.

0163<figref idref="DRAWINGS">FIG. 15</figref> illustrates one embodiment of an exemplary network <b>101</b> that can be used with the present invention. As shown in <figref idref="DRAWINGS">FIG. 15</figref> a wireless packet data service network <b>102</b> that can be utilized with the patient monitoring device <b>10</b>. An enterprise network <b>104</b>, which may be a packet-switched network, can include one or more geographic sites and be organized as a local area network (LAN), wide area network (WAN) or metropolitan area network (MAN), and the like. One or more application servers <b>106</b>-<b>1</b> through <b>106</b>-N can be included and disposed as part of the enterprise network <b>104</b> are operable to provide or effectuate a host of internal and external services such as email, video mail, Network Systems access, corporate data access, messaging, calendaring and scheduling, information management, and the like using the unique IDs of the wearable devices <b>10</b>. The patient monitoring device <b>10</b> can be in communication with a variety of personal information devices other than the patient monitoring device <b>10</b>, including but not limited to, computers, laptop computers, mobile devices, and the like.

0164Additionally, system server <b>16</b> may be interfaced with the enterprise network <b>104</b> to access or effectuate any of the services from a remote location using a patient monitoring device <b>10</b>. A secure communication link with end-to-end encryption may be established that is mediated through an external IP network, i.e., a public packet-switched network such as Network Systems <b>108</b>, as well as the wireless packet data service network <b>102</b> operable with a patient monitoring device <b>10</b> via suitable wireless network infrastructure that includes a base station (BS) <b>110</b>. In one embodiment, a trusted relay network <b>112</b> may be disposed between Network Systems <b>108</b> and the infrastructure of wireless packet data service network <b>102</b>.

0165In another embodiment, the infrastructure of the trusted relay network <b>112</b> may be integrated with the wireless packet data service network <b>102</b>, and the functionality of the relay infrastructure can be consolidated as a separate layer within a “one-network” environment. Additionally, as non-limiting examples, patient monitoring device <b>10</b> may be capable of receiving and sending messages, web browsing, interfacing with corporate application servers, and the like, regardless of the relationship between the networks <b>102</b> and <b>112</b>. Accordingly, a “network node” may include both relay functionality and wireless network infrastructure functionality in some exemplary implementations.

0166In one embodiment, the wireless packet data service network <b>102</b> is implemented in any known or heretofore unknown communications technologies and network protocols, as long as a packet-switched data service is available therein for transmitting packetized information. For instance, the wireless packet data service network <b>102</b> may be comprised of a General Packet Radio Service (GPRS) network that provides a packet radio access for mobile devices using the cellular infrastructure of a Global System for Mobile Communications (GSM)-based carrier network. In other implementations, the wireless packet data service network <b>102</b> may comprise an Enhanced Data Rates for GSM Evolution (EDGE) network, an Integrated Digital Enhanced Network (IDEN), a Code Division Multiple Access (CDMA) network, a Universal Mobile Telecommunications System (UMTS) network, or any 3rd Generation (3G) network.

0167Referring now to <figref idref="DRAWINGS">FIGS. 16(<i>a</i>) through 16(<i>d</i>)</figref>, in one embodiment, the patient monitoring device <b>10</b> is in communication with an interaction engine <b>120</b> that can be at a mobile device <b>74</b> or system <b>32</b>. The interface engine can be a software application running on mobile device <b>74</b> associated with another party, including but not limited to a merchant, an associate, a friend, and the like. The enables the patient monitoring device <b>10</b> user and a merchant to interact with a transaction engine <b>114</b> to and enter into a financial transaction for the transfer of funds from a third party payment system <b>116</b> that is independent of the patient monitoring device <b>10</b> user's financial account <b>118</b>, and complete a transaction. It should be noted that the payment system <b>116</b> can be affiliated with the financial account <b>118</b> or can be a separate and non-affiliated with the financial account <b>118</b>. The interaction engine <b>120</b> can take input of information related to a transfer of funds from the patient monitoring device <b>10</b> users' financial accounts <b>118</b> as input to the transaction engine <b>114</b> to initiate and complete a financial transaction, including but not limited the purchase and payment of goods and services. In one embodiment, this input to the interaction engine <b>114</b> can include, an amount of a transaction, additional items related to the transaction, authorization and/or signature of the patient monitoring device <b>10</b> user.

0168In one embodiment, the mobile device <b>74</b> receives information from the patient monitoring device <b>10</b>, e.g., the unique ID.

0169The interaction engine <b>120</b> can also present products or services provided by a merchant to directly to or through system <b>32</b> to the patient monitoring device <b>10</b> user. In one embodiment, the patient monitoring device <b>10</b> users can use the mobile device <b>74</b>, the WEB, and the like, to view, text, pictures, audio, and videos, and browse through the products and services on the mobile device <b>74</b>, personal computers, other communication devices, the WEB, and anything that is BLUETOOTH®, anything associated with Network Systems, and the like.

0170In one embodiment, the transaction engine <b>114</b>, which can be at the mobile device <b>74</b>, or external to the mobile device <b>74</b>, including but not limited to patient monitoring device <b>10</b> and the like, takes decoded financial transaction card information from a decoding engine <b>122</b>, internal or external to the mobile device <b>74</b>, and a transaction amount from an interaction engine <b>120</b>, also internal or external to the mobile device. The transaction engine <b>114</b> then contacts the payment service <b>116</b>, and or the patient monitoring device <b>10</b> users' financial account <b>118</b>, such as an acquiring bank that handles such authorization request, directly or through the payment system <b>116</b>, which may then communicate with a financial transaction card issuing bank to either authorize or deny the transaction. The payment system <b>116</b> can include a user database, a transaction database, a product database, and the like. These databases can also be external to payment system <b>116</b>. If the third party authorizes the transaction, then the transaction engine <b>114</b> transfers funds deducted from the account of the patient monitoring device <b>10</b> user, or the payment system <b>116</b> can already have those funds readily available, to an account of a third party which can be another patient monitoring device <b>10</b> user, a merchant, and the like, and provides transaction or transfer of fund results to the interaction engine <b>120</b> for presentation to a third party.

0171In one embodiment, the transaction engine <b>114</b> does not have the financial account or financial card information of the patient monitoring device <b>10</b> user that is doing the transfer. In some embodiments, the transaction engine <b>114</b> keeps only selected information of the patient monitoring device <b>10</b> user's financial accounts <b>118</b> or financial transaction cards.

0172In one embodiment, the wearable device communicates directly, without mobile device <b>74</b>, with the payment system <b>116</b> and/or the user's financial account <b>118</b> or associated financial institution.

0173In one embodiment, the transaction engine <b>114</b> communicates and interacts with the financial account <b>118</b> or associated financial institution directly or through the payment system <b>116</b>, through a user database, product database, and transaction database, which databases can be separate from or included in the payment system <b>116</b>, over a network. The network can be a communication network, as recited above, and can be based on well-known communication protocols, including but not limited to, a TCP/IP protocol.

0174With social networking applications, the patient monitoring device <b>10</b>, with its unique ID, is an ID device. Information from the patient monitoring device <b>10</b> relating to social networking, and the like, communicates with system <b>32</b>. In this manner, the wearable devices <b>10</b>, with their own unique ID's, can be recognized. This can occur at different locations, close by, distanced, and notifications can be sent to the different users wearing a patient monitoring device <b>10</b> for a variety of social networking and other communication applications. Additionally, patient monitoring device <b>10</b>, with its sensors <b>14</b> and ID can communicate directly to social networking sites, Network Systems, cloud services, and the like.

0175In one embodiment, with the current permissions given by the wearable device users, marketers, companies or individuals who wish can deliver advertisement patient monitoring device <b>10</b> users. More particularly, system <b>32</b> can be configured to allow marketers, and the like, to deliver advertisements to consumers to buy products or services offered by the marketer. Advertisements can also be sent to patient monitoring device <b>10</b> users with the appropriate permissions. In one embodiment, system <b>32</b> maintains the anonymity of the patient monitoring device <b>10</b> users while allowing the marketers to have their advertisements delivered to those that fall within their defined market segment.

0176In one embodiment, the wearable device ID of a user provides a method of identifying and contacting users of a social networking service. The method may include the steps of signing up for a social networking service, displaying the wearable device ID, viewing another person's unique wearable device ID displayed by another user, and finding that user on a social networking service website by searching for the user using the wearable device ID viewed.

0177System <b>32</b> may serve a number of purposes without straying from the scope of the present invention. For example, the social networking service may allow patient monitoring device <b>10</b> users to engage in non-romantic relationships, keep in touch with acquaintances, friends and family, professional business relationships, and romantic relationships, may allow communication between wearable device users on a message board or Network Systems forum, and may allow users to follow up on missed-connections that otherwise would not have been realized.

0178In one embodiment, the step of providing personal information to start an account with system <b>10</b> for different applications may be performed by a purchasing or acquiring a patient monitoring device <b>10</b>, with a unique assigned ID, and the user can fill in an online form. This form may require users to fill in fields on the form. These fields may include: first and last name, email address, a desired password, phone number, gender, birth date, address, geographic region, education information, employment information, interests, relationship information and interests, family information, religious views, ethnicity, physical features including hair color, eye color, measurements, and the like, type of relationship being sought, living situation, answers to quiz questions, and a personal description about interesting personality traits, among other things. In addition, users may upload one or a plurality of photographs for other users to view, or for users to store the photo or photos on the server of system <b>32</b>.

0179In another embodiment the step of providing personal information to start an account with system <b>32</b> by patient monitoring device <b>10</b> users may be performed automatically. In this embodiment, system <b>32</b> can access a social networking service, access, via computer, contact lists or other sources of information that may include the type of information listed above.

0180In a further embodiment, the step of providing personal information to system <b>32</b> can be automated by importing data containing the personal information required from other social networking services including but not limited to Facebook®, LinkedIn®, MySpace®, Match.com®, EHarmony.com®, a user's email or contact list, v-card, and the like.

0181The unique wearable device ID may allow the user to be searched and identified by other users and potential users. Also, a computer generated email address may be provided to a user. In one embodiment, this email address may be the user's user ID followed by “@iseenya.com.” In another embodiment, the email address may be the user's user ID directed to another domain name.

0182In one embodiment, a computer generated personal page may be provided to a patient monitoring device <b>10</b> user. The personal page may utilize a computer to automatically import the information provided when signing up with system <b>32</b> or a social networking service. In another embodiment, the information and formatting of the personal page can be customizable.

0183When mobile device <b>74</b> is used, it communicates with one or more sensors <b>14</b> that are at the patient monitoring device <b>10</b>, as more fully herein. The mobile device can <b>74</b> pull from system <b>32</b> updates from the server <b>16</b>, including but not limited to settings such as alarms, name of the wearable device wearer using the ID, a sensor <b>14</b> and the like. Sensors <b>14</b> at the patient monitoring device <b>10</b> can send streams of information, both encrypted and non-encrypted to the mobile device and then to the server at system <b>32</b>. Server <b>16</b> sends encrypted, and can also send non-encrypted information, to mobile device <b>74</b>. Processing of this information can be achieved at the mobile device <b>74</b>, and/or server <b>16</b>. Mobile device <b>74</b> can receive raw sensor information from the patient monitoring device <b>10</b>. This information can be compressed as well as non-compressed. A compression algorithm, at the wearable device and/or mobile device <b>74</b> or system <b>32</b>, can be used in order to minimize the amount of information that server <b>16</b> sends. System <b>32</b> can include additional encryption and/or decryption systems.

0184Referring now to <figref idref="DRAWINGS">FIG. 17</figref>, a social network circle/group <b>124</b> (hereinafter “SNET circle”) comprising social devices <b>126</b>, including patient monitoring device <b>10</b>, is shown. Beyond traditional social networking features and services, a SNET circle <b>124</b> and associated social devices <b>124</b> according to various embodiments of the invention include numerous novel features and attributes as described more fully below with general reference to the illustration. Patient monitoring device <b>10</b> can utilize network <b>101</b> for communication with the SNET circle, as well as with other social networking sites, or through system <b>32</b>.

0185Briefly, membership in the SNET circle <b>124</b> may comprise docked and undocked social devices <b>124</b> and human SNET circle members [<b>104</b>] <b>128</b>, as well as proxies thereof. Further, SNET circle <b>124</b> nodes may include device services and software (e.g., applications) of various types participating as members. By way of example, SNET circle members might include artificial intelligence agents/social robots <b>130</b>, SNET security device(s) <b>132</b>, appliances, vehicles and service providers <b>134</b>, common or authorized members/functionality of other SNET circles <b>124</b>, and the like. Further, access to specific content and resources of a SNET circle <b>124</b> may be shared with members of additional SNET(s) <b>124</b>, including remote or web-based applications. Such access can be conditioned on acceptable profiling and association data. Similarly, social devices or individuals may be granted temporary or ad hoc memberships, with or without restricted access.

0186In the illustrated embodiment, formation, maintenance and operation of SNET circle <b>124</b> is performed by standalone or distributed SNET processing circuitry and software <b>136</b>. It is noted that the “SNET processing circuitry” may comprise hardware, software, applications, or various combinations thereof, and be configurable to support various functionalities disclosed herein. Further, the SNET processing circuitry <b>136</b> may be included in a standalone server, server farm, cloud-based resources, network <b>101</b>, system <b>32</b> and/or the various types of devices described below, and incorporate authentication and security functionality <b>138</b>. In addition, specialized middleware may also be utilized by SNETs according to the invention, including standardized middleware with an associated certification process. Interactions and interdependencies within the SNET circle <b>124</b> may involve one or more of a social device association/control module <b>140</b>, a SNET circle member profiling module <b>142</b>, and an adaptive resource allocation and arbitration module <b>144</b> as described more fully below.

0187Distribution of internal and external SNET content/media <b>146</b> can be accomplished in a variety of ways in accordance with various embodiments of the invention. For example, media distribution may involve an adaptive or parallel network routing infrastructure involving a wide variety of communication protocols and wired and/or wireless communications channels. SNET content/media <b>146</b> may comprise, for example, various user-driven (advertising) channels, pictures, videos, links, online text, etc. Access to such content, as well as communications with and remote access to social devices <b>124</b> of the SNET circle <b>124</b>, may occur over an Network Systems backbone <b>148</b>, cellular communication system, WAN, LAN, and the like.

0188<figref idref="DRAWINGS">FIG. 18</figref> illustrates an embodiment of a social group <b>150</b> comprising a variety of members in accordance with the present invention that can communicate through their wearable devices <b>10</b> and other devices, including but not limited to mobile devices <b>74</b>. In this embodiment, membership in the social group <b>150</b> may include a variety of novel social system members [<b>204</b>] <b>152</b> functioning in various capacities within the social group <b>150</b>. As will be understood, certain of the social system members <b>152</b> may support direct or indirect associations between the social group <b>150</b> and human members/non-members and users <b>154</b>.

0189In the illustrated embodiment, social system members (or nodes) <b>152</b> include one or more local or remote servers and server clusters that provide a support infrastructure for social group functionality and member operations (routing, data storage, services, etc.). Communications within the social group and with non-members may occur via dedicated or multi-function communication path devices.

0190Social system members <b>152</b> further include devices configured to operate as nodes within the social group <b>150</b>. Social functionality in such devices and other social system members <b>152</b> can be implemented through various means. For example, a device may have integral hardware/firmware/software to support social group access and member operations. Alternatively, a general purpose device <b>152</b><i>a </i>may include social code that enables participation in the social group <b>150</b>. In a further embodiment, a device <b>152</b><i>b </i>designed to include social functionality may participate in the social group <b>150</b> through a combination of non-social code and a social shim layer or driver wrapper. In yet another embodiment, a member device <b>152</b><i>c </i>having a social design may utilize additional social code, including code specific to a social group <b>150</b>.

0191Participation in the social group <b>150</b> is supported through functionality that includes automated and member-triggered membership invitations and processing (membership management) <b>156</b>. More particularly, membership management <b>156</b> may function to invite prospective members to participate in the social group <b>150</b> through automatic, automated and member-triggered processes. For example, membership management <b>156</b> might be configured by a human user <b>154</b> to establish a social group <b>150</b> by automatically inviting/accepting social system members having certain characteristics (such as devices owned or controlled by the user or acquaintances of the user).

0192Processing of accepted invitations and unsolicited requests to join the social group <b>150</b> may be conditioned upon input or authorization from an existing social system member(s) <b>152</b> or human user(s) <b>154</b> (e.g., through a user interface). Similarly, membership management <b>156</b> may be configured to generate automated suggestions regarding which prospective members receive an invitation. Various other approaches, such as those described herein, can be used to establish membership in accordance with the invention.

0193Access to and visibility of resources of a social group <b>150</b>, including services and data, may be managed through general and member class-specific access configurations <b>158</b>. For example, if membership in the social group <b>150</b> includes family members and associated devices, a uniform access configuration (or separate device and human configurations) could be applied across the class in an automatic or automated manner. In other embodiments, access control and constraints are imposed on a per-member basis.

0194The social group <b>150</b> may offer a wide variety of member services <b>162</b>, including both internal and external services accessible by social system members <b>152</b>. By way of example, the social group <b>150</b> may offer email or other communication services between full members and/or authorized guest members and visitors. As with other resources of the social group <b>150</b>, access control and constraints on member services <b>162</b> may be applied to individual members or classes of members.

0195<figref idref="DRAWINGS">FIG. 19</figref> is a functional block diagram illustrating a social network (SNET) infrastructure <b>164</b>, as more fully described and disclosed in EP 2582116, fully incorporated herein by reference.

0196In one embodiment, illustrated in <figref idref="DRAWINGS">FIG. 20</figref>, wearable devices <b>10</b> are in communication with a distributed computer network <b>166</b> that can include networks <b>102</b>, <b>104</b>, <b>112</b>, coupled to Network Systems <b>108</b> and system <b>32</b> via a plurality of communication links <b>168</b>. Communication network <b>166</b> provides a mechanism for communication with system <b>16</b>, patient monitoring device <b>10</b>, social media networks, mobile devices <b>74</b>, payment systems, <b>116</b>, the engines <b>114</b>, <b>120</b>, <b>122</b>, components of system <b>16</b>, and with all third parties, as described above.

0197The communication network <b>166</b> may itself be comprised of many interconnected computer systems and communication links. Communication links <b>168</b> may be hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information. Various communication protocols may be used to facilitate communication between the various systems shown in <figref idref="DRAWINGS">FIG. 20</figref>. These communication protocols may include TCP/IP, HTTP protocols, wireless application protocol (WAP), vendor-specific protocols, customized protocols, and others.

0198While in one embodiment, communication network <b>166</b> is the Network Systems, in other embodiments, communication network <b>166</b> may be any suitable communication network <b>166</b> including a local area network (LAN), a wide area network (WAN), a wireless network, an intranet, a private network, a public network, a switched network, and combinations of these, and the like.

0199System <b>32</b> is responsible for receiving information requests from wearable devices <b>10</b>, third parties, and the like, performing processing required satisfying the requests, and for forwarding the results corresponding to the requests backing to the requesting patient monitoring device <b>10</b> and other systems. The processing required to satisfy the request may be performed by server <b>16</b> or may alternatively be delegated to other servers connected to communication network <b>166</b>.

0200<figref idref="DRAWINGS">FIG. 21</figref> shows an exemplary computer system that can be utilized with the wearable devices <b>10</b>. In an embodiment, a user interfaces with system <b>32</b> using a patient monitoring device <b>10</b> and then through a computer workstation system, such as shown in <figref idref="DRAWINGS">FIG. 21</figref>, a mobile device, and the like.

0201The communication network <b>166</b> may be the Network systems, among other things. The network may be a wireless, a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system of the invention using a wireless network using a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11n, and 802.11ac, just to name a few examples), near field communication (NFC), radio-frequency identification (RFID), mobile or cellular wireless (e.g., 2G, 3G, 4G, 3GPP LTE, WiMAX, LTE, Flash-OFDM, HIPERMAN, iBurst, EDGE Evolution, UMTS, UMTS-TDD, IxRDD, and EV-DO). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.

0202<figref idref="DRAWINGS">FIG. 22</figref> shows a system for activity collection and building a social graph for network patient monitoring device <b>10</b> users. The system monitors users as they surf the Web, their activities, locations, status, interests, and other things, This can be achieved without regard to whether the wearable device users <b>10</b> are logged into a membership site, such as a social networking site.

0203Resources <b>170</b> and <b>172</b> gather activity data and pass this data to an activity storage server <b>174</b>, typically via Network Systems <b>108</b>. Partner resource <b>172</b> may be processed by a partner back end, and then this data is passed to activity storage server <b>174</b>.

0204Patient monitoring device <b>10</b> users can use social media sharing application or sites. Applications (e.g., a mobile device app or sites allow sharing of information with others. These can be used to collect activity data. A patient monitoring device <b>10</b> user (sender) can share information (e.g., video, photo, link, article, or other) by posting to a site. The patient monitoring device <b>10</b> user can post directly on the site or use an application program, such as a mobile application on a smartphone or tablet computer. When another user (recipient) clicks or vies the link, there is connection activity between the sender and recipient. This activity data is captured by system <b>32</b>.

0205Messenger applications such as those on mobile device <b>74</b> or sites can allow Network Systems or Web messaging with others. Network Systems messaging is different from short messaging server (SMS) or text messaging. Messenger applications can be used to collect sharing activity data.

0206Users use messenger application to send links and other information to other users, and also achieve this using their wearable devices <b>10</b>. A user (sender) can copy a link (e.g., via a clipboard) and send to one or more users via the messenger application with mobile device <b>74</b> and with its patient monitoring device <b>10</b>. When a recipient user clicks on the link, there is connection activity between the sender and recipient for that link.

0207Sharing activity data can be captured as described above. There can be different data collectors for different devices and platforms. The activity data is transmitted to and stored at activity storage server <b>174</b>, typically through Network Systems. Server <b>174</b> stores the data for further processing. There can be a significant amount of real-time data that is collected for processing. Distributed computing and processing can be used to process the data.

0208The activity data collected is stored at server <b>174</b>, usually in a database or file systems on hard drives of server <b>174</b>. There may be many terabytes of data that need are to be processed. Taking the stored activity data as input is a build-update graph component (e.g., executable code running on one or more servers or other computers). Build-update graph component <b>178</b> can run on the same server that stores the activity data, or may run on a separate server that accesses storage server <b>174</b>.

0209In one embodiment, a build-update graph <b>180</b> builds or updates a social graph using the collected activity data. The social graph can be stored in one or more databases or file systems. In one embodiment, build-update graph <b>180</b> can include three components: (1) identify nodes and edges for social graph that need to be updated, (2) create new nodes/edges if nodes/edges are not found, and (3) update values associated with nodes and edges.

0210For the incoming activity data collected, identify nodes <b>182</b> scan through and find the nodes and edges of the social graph that need to be updated.

0211When system <b>32</b> is processing a user activity data it has the ID of the patient monitoring device <b>10</b> user and attributes this activity to that patient monitoring device <b>10</b> user.

0212When a node or edge is found, update values update the node or an edge (e.g., associated with the node). When a node or edge is not found, a new node or edge is created in the graph. The result of build/update graph is a social graph <b>184</b> with nodes modeling user profiles and edge modeling sharing activities among users.

0213<figref idref="DRAWINGS">FIG. 23</figref> shows a sample social graph <b>186</b> where circles <b>188</b> represent nodes and lines are edges <b>190</b> representing sharing interactions between nodes <b>182</b>. There can be one or more edges <b>190</b> between two nodes <b>182</b>. Several edges <b>190</b> between nodes <b>182</b> can indicate sharing activities along several categories: e.g., travel, computers, sports, and others.

0214Nodes <b>182</b> connected together directly have one degree of separation. Nodes <b>182</b> connected through one other node have two degrees of separation. Depending on a number of intervening nodes <b>182</b> between two nodes <b>182</b>, this will be a number of degrees of separation between the two nodes <b>182</b>.

0215In a specific implementation, edges <b>190</b> between nodes <b>182</b> indicate sharing activities along several categories such as travel, computers, sports, and the like. For each additional new sharing category, an additional edge <b>190</b> is added. In a specific implementation, for each additional new sharing interest category, an additional edge <b>190</b> is added. Further, in an implementation, the sharing interaction or edges <b>190</b> between the nodes <b>182</b> can be weighted (e.g., weighting in a range from 0 to 1), so that certain types of sharing interactions are given different significance. Weight can be used to represent a relative strength of interaction related to a particular interest category.

0216Some types of sharing activities that are tracked for the social graph (or share graph) include: sending messages between users; sending files between users; sending videos between users; sending an e-mail (e.g., Web e-mail) with a link from one user to another such as sharing a link to various social media sites; and sending instant messages between users. For mobile devices <b>74</b> the sharing activities can further include: sending SMS-type messages between users. In some embodiments, messages can be sending from wearable devices <b>10</b>.

0217Once two users connect, such as one patient monitoring device <b>10</b> sending another patient monitoring device <b>10</b> user a message containing a link concerning a topic. When the recipient user clicks on the link from the sender user, system <b>32</b> will add an edge <b>190</b> to graph <b>186</b> to represent the activity. An edge <b>190</b> is added to the graph <b>186</b> to represent this sharing activity between the two users.

0218In a specific implementation, two patient monitoring device <b>10</b> users are connected when one user (sender) shares information with another user or group and the other user (recipient) consumes the information that was sent (e.g., clicked-back on the shared link, opened an attachment, opened a message). For example, simply placing a link on Facebook® wall so that all Facebook® “friends” can see this link or tweeting a link to Twitter® followers will not create a connection between the sender, or sharer, and people in the graph. This would create significant noise in the system. The connections are created between the sender and only those users who clicked back on (or otherwise consumed) the message.

0219In one embodiment of the present invention, illustrated in <figref idref="DRAWINGS">FIG. 24</figref>, the patient monitoring device <b>10</b> includes the alarm <b>44</b>. In one embodiment, the alarm <b>44</b> sends a message to the patient only when the patient is awake. The awake status of the patient can be determined by the monitoring device <b>10</b> itself, the monitoring device <b>10</b> in combination with the telemetry system <b>32</b>, or by the telemetry system <b>32</b>.

0220The alarm <b>44</b> can be visual, by motion, audio, and the like. The patient monitoring device <b>10</b> can include a visual display <b>42</b> that can communicate an alert to the patient. In another embodiment, the alarm <b>44</b> can provide an audio alert to the patient.

0221The display <b>42</b> can be a touch screen display, such that the patient or a bystander can communicate with the telemetry system <b>32</b>.

0222In one embodiment, the monitoring device <b>10</b> detects and awake or non-awake status of the patient. The alarm <b>44</b> is then activated when the patient is alert or awake, when an alert is required.

0223In <figref idref="DRAWINGS">FIG. 24</figref>, the alarm <b>44</b> is positioned at patient monitoring device <b>10</b>. Sensors <b>14</b> are to the processor <b>18</b> in order to determine if the patient is awake. When the patient is awake, and a condition exists that merits the patient receiving an alert, the processor <b>84</b> communicates with an alarm circuit <b>216</b> coupled to the display <b>42</b> or the audio alarm <b>44</b> and provide an alert to the patient regarding the patient's condition, a change in a patient parameter, a hazard, and the like.

0224The determination that the patient is awake can be made by a variety of methods. As non-limiting examples, sleep detection, e.g., awakeness of the patient, can be by, motion detection, breathing rate, respiratory function, brain activity, visual detection, eyelid activity, image detection and the like.

0225In one embodiment, the determination for the awake condition of the patient is determined at the telemetry system <b>32</b>. In this embodiment, when a patient needs to receive an alert by alarm <b>44</b>, display <b>42</b>, and the like, the telemetry system <b>32</b> sends a wireless signal to the monitoring device <b>10</b>. The signal can be sent to the processor <b>84</b>, circuit <b>216</b>, transceiver <b>86</b> and the like. If the patient is awake, then an alert is created and transmitted to the patient via, audio, visual, touch and the like.

0226The foregoing description of various embodiments of the claimed subject matter has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the claimed subject matter to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. Particularly, while the concept “component” is used in the embodiments of the systems and methods described above, it will be evident that such concept can be interchangeably used with equivalent concepts such as, class, method, type, interface, module, object model, and other suitable concepts. Embodiments were chosen and described in order to best describe the principles of the invention and its practical application, thereby enabling others skilled in the relevant art to understand the claimed subject matter, the various embodiments and with various modifications that are suited to the particular use contemplated.