US9993197B2 - Patient monitoring systems and messages that send alerts to patients only when the patient is awake - Google Patents

Abstract

A system for is provided for using telemetry data based on 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.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of all of the following: This application also is related to and claims the benefit of which is a Continuation-in-Part U.S. patent application Ser. No. 15/058,986, filed Mar. 2, 2016, which is a Continuation-in-Part U.S. patent application Ser. No. 15/058,869, filed Mar. 2, 2016, which is a Continuation-in-Part U.S. patent application Ser. No. 15/058,809, filed Mar. 2, 2016, which is a Continuation-in-Part U.S. patent application Ser. No. 15/058,728, filed Mar. 2, 2016, which is a Continuation-in-Part U.S. patent application Ser. No. 14/729,608, filed Jun. 6, 2015, which is a Continuation-in-Part U.S. patent application Ser. No. 14/725,973, filed May 29, 2015, which is a U.S. Provisional Patent Application No. 62/118,384, filed Feb. 19, 2015, which is a Continuation U.S. application Ser. No. 14/604,569, filed Jan. 23, 2015, which is a Continuation-in-Part U.S. application Ser. No. 14/604,566, filed Jan. 23, 2015, which is a Continuation U.S. application Ser. No. 14/588,853, filed Jan. 2, 2015, which is a Continuation-in-Part U.S. application Ser. No. 14/588,848, filed Jan. 2, 2015, which is a Continuation U.S. application Ser. No. 14/495,656, filed Sep. 24, 2014, which is a Continuation-in-Part U.S. application Ser. No. 14/495,332, filed Sep. 24, 2014, now U.S. Pat. No. 9,320,435, issued Apr. 26, 2016 which is a U.S. Provisional Patent Application No. 62/027,885, filed Jul. 23, 2014, which is a Continuation-in-Part of U.S. application Ser. No. 14/180,152, filed Feb. 13, 2014, which is a Continuation-in-Part of U.S. application Ser. No. 14/180,109, filed Feb. 13, 2014, which is a Continuation of U.S. application Ser. No. 14/052,376, filed Oct. 11, 2013, which is a Continuation of U.S. application Ser. No. 14/051,093, filed Oct. 10, 2013, which is a Continuation of U.S. application Ser. No. 14/049,822, filed Oct. 9, 2013, which is a Continuation of U.S. application Ser. No. 14/049,690, filed Oct. 9, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 14/048,731, filed Oct. 8, 2013, which is a Continuation of U.S. application Ser. No. 14/039,802, filed Sep. 27, 2013, which is a Continuation of U.S. patent application Ser. No. 14/039,145, filed Sep. 27, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 14/038,990, filed Sep. 27, 2013, which is a Continuation of U.S. application Ser. No. 14/037,974, filed Sep. 26, 2013, now abandoned, which is a Continuation of U.S. application Ser. No. 14/037,870, filed Sep. 26, 2013, which is a Continuation of U.S. application Ser. No. 14/037,825, filed Sep. 26, 2013, now Abandoned, which is a Continuation of U.S. application Ser. No. 14/037,747, filed Sep. 26, 2013, which is a Continuation of U.S. application Ser. No. 14/037,717, filed Sep. 26, 2013, now U.S. Pat. No. 9,055,791, issued Jun. 16, 2015, which is a Continuation of U.S. application Ser. No. 14/037,643, filed Sep. 26, 2013, which is a Continuation of U.S. application Ser. No. 14/037,594, filed Sep. 26, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 14/037,536, filed Sep. 26, 2013, which is a Continuation of U.S. application Ser. No. 14/036,382, filed Sep. 25, 2013, which is a Continuation of U.S. application Ser. No. 14/036,287, filed Sep. 25, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 14/036,111, filed Sep. 25, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 14/023,876, filed Sep. 11, 2013, now U.S. Pat. No. 9,159,223, issued Oct. 13, 2015, which is a Continuation of U.S. application Ser. No. 13/966,641, filed Aug. 14, 2013, which is a Continuation of U.S. application Ser. No. 13/966,623, filed Aug. 14, 2013, which is a Continuation of U.S. application Ser. No. 13/967,120, filed Aug. 14, 2013, which is Continuation of U.S. application Ser. No. 13/967,109, filed Aug. 14, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/967,094, filed Aug. 14, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/961,599, filed Aug. 7, 2013, now U.S. Pat. No. 9,149,189, issued Oct. 6, 2015, which is a Continuation-in-Part of U.S. application Ser. No. 13/961,511, filed Aug. 7, 2013, now U.S. Pat. No. 9,204,798, issued Dec. 8, 2015, which is a Continuation-in-Part of U.S. application Ser. No. 13/960,491, filed Aug. 6, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/960,451, filed Aug. 6, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/960,436, filed Aug. 6, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/960,407, filed Aug. 6, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/960,075, filed Aug. 6, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/959,085, filed Aug. 5, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/959,022, filed Aug. 5, 2013, which is a Continuation of U.S. application Ser. No. 13/956,815, filed Aug. 1, 2013, now U.S. Pat. No. 9,298,882, issued Mar. 29, 2016, which is a Continuation of U.S. application Ser. No. 13/956,674, filed Aug. 1, 2013, which is a Continuation-in-Part of U.S. application Ser. No. 13/956,564, filed Aug. 1, 2013, which is a Continuation of U.S. application Ser. No. 13/955,892, filed Jul. 31, 2013, which is a Continuation of U.S. application Ser. No. 13/955,845, filed Jul. 31, 2013, which is a Continuation of U.S. application Ser. No. 13/955,810, filed Jul. 31, 2013, now U.S. Pat. No. 9,320,434, issued Apr. 26, 2016, which is a Continuation-in-Part of U.S. application Ser. No. 13/955,777, filed Jul. 31, 2013, which is a Continuation of U.S. application Ser. No. 13/923,937, filed Jun. 21, 2013, which is a Continuation of U.S. patent application Ser. No. 13/923,909, filed Jun. 21, 2013, which is a Continuation of U.S. application Ser. No. 13/923,809, filed Jun. 21, 2013, which is a Continuation of U.S. application Ser. No. 13/923,750, filed Jun. 21, 2013, which is a Continuation of U.S. application Ser. No. 13/923,637, filed Jun. 21, 2013, now U.S. Pat. No. 8,810,430, issued on Aug. 19, 2014, which is a Continuation of U.S. patent application Ser. No. 13/923,614, filed Jun. 21, 2013, now U.S. Pat. No. 8,850,421, issued on Sep. 30, 2014, which is a Continuation of U.S. application Ser. No. 13/923,560, filed Jun. 21, 2013, now U.S. Pat. No. 8,803,366, issued Aug. 12, 2014, which is a Continuation of U.S. application Ser. No. 13/923,543, filed Jun. 21, 2013. All of the above applications are fully incorporated herein by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

The 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.

Description of the Related Art

Patient 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.

With 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.

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

It 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.

Medical 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.

There 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

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

Another 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.

A 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.

Yet 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.

These 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.

In 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

FIGS. 1(a) and 1(b) illustrate one embodiment of a wearable device of the present invention, where one size fits all.

FIG. 2 illustrates one embodiment of electronics that can be included in the wearable device.

FIG. 3 illustrates one embodiment of a telemetry system of the present invention.

FIG. 4 is a diagram of the programming input schematic of the secure sensor/transmitter array ofFIG. 7.

FIG. 5 is a block diagram of the system of programming the sensor/transmitter(s) comprising the secure sensor/transmitter array ofFIG. 7.

FIG. 6 is a block diagram of the jam command and security/randomization bits of the secure sensor/transmitter array ofFIG. 7.

FIG. 7 is a logic circuit diagram of the sensor/transmitter programming input schematic in one embodiment of the present invention.

FIG. 8 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.

FIG. 9 is a block diagram illustrating one embodiment of a SNAPSHOT GPS receiver for use according to the present invention.

FIG. 10 is a block diagram of a remote sensor shown in communication with two different external communication devices.

FIG. 11 is a diagram of the active RF and RF backscatter antennas.

FIG. 12 is a diagram of the encoding scheme for the symbols in the active RF protocol.

FIG. 13 is a diagram of the packet structure in the IRDA protocol.

FIG. 14 is a diagram of the encoding scheme in the IRDA protocol.

FIG. 15 illustrates one embodiment of a wireless network that can be used with the present invention.

FIGS. 16(a)-16(d) 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.

FIG. 17 illustrates an embodiment of a social network circle with social devices in accordance with one embodiment of the present invention.

FIG. 18 illustrates an embodiment of a social group with a variety of members in accordance with one embodiment of the present invention.

FIG. 19 is a functional block diagram illustrating a social network infrastructure and social devices in accordance with one embodiment of the invention.

FIG. 20 illustrates a simplified block diagram of a client-server system and network in one embodiment of the present invention.

FIG. 21 illustrates a more detailed diagram of an exemplary client or server computer that can be used in one embodiment of the present invention.

FIG. 22 illustrates a system for activity collection and building a social graph including sharing activity between users in one embodiment of the present invention.

FIG. 23 illustrates a social graph with nodes representing users and edges representing sharing activity between the users in one embodiment of the present invention.

FIG. 24 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

As 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.

As 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.

As 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.

As 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”).

A 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.

As 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.

As 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.

As 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:

• • LANs or WANs belonging to multiple organizations and interconnected and accessed using remote dial-up
  • LANs or WANs belonging to multiple organizations and interconnected and accessed using dedicated lines
  • 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

As 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:

• • A LAN
  • A Wide-area network (WAN) that is comprised of a LAN that extends usage to remote employees with dial-up access
  • A WAN that is comprised of interconnected LANs using dedicated communication lines
  • 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)

As 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.

Additionally 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.

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

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

In various embodiments, the present invention provides apatient monitoring device10, such as a wearable device, where one size fits all. As illustrated inFIGS. 1(a) and 1(b), in one embodiment of the present invention, thepatient monitoring device10 include a plurality ofmagnets12, with adjacent magnets having opposite polarity, with a length suitable to be worn by all people. In one embodiment, the length of thepatient monitoring device10 can be 10-12 inches. Themagnets12 are positioned along an interior of thepatient monitoring device10 to be provided for good conformation to a user's wrist.

One ormore sensors14 are coupled to thepatient monitoring device10. The sensors are measuring devices. As a non-limiting example, the measuring device orsensors14 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.

Alternatively,multifunctional sensors14 which can perform all the aforementioned functions of RTSS may be attached or embedded inpatient monitoring device10. In one embodiment, each sensor can be in communication and or connect electronically and/or RF to atelemetry module16. A variety ofdifferent sensors14 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.

As 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.

Referring toFIG. 2, in various embodiments, thepatient monitoring device10, also known as the patient monitoring device, can include apower source24, such a battery that can be rechargeable. Thebattery24 can be put into a sleep state when not actively used in order to preserve power. A wake up feature allows thebattery24 and other electronics of thepatient monitoring device10 to “sleep” during non-use or and is initiated into the “wake up” mode by certain predestinated events.

In one embodiment, as illustrated inFIG. 3, atelemetry system server16 is coupled to adatabase18. Eachpatient monitoring device10 is assigned its own unique identification, ID.

The data transmitted by thepatient monitoring device10sensors14 and its ID may be coded by appending a seed to digital data bits. As illustrated inFIG. 3 central processor unit20 (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. Aprogramming device22 may be configured to transmit data to asensor14, 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.

In one embodiment,sensors14 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 theprogramming device22 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.

Referring again toFIG. 2, in one embodiment, thepatient monitoring device10 includes acontrol unit26 that puts thepatient monitoring device10 in a low power state. Amonitoring system28 can be included that remains active. Themonitoring system28 wakes up theelectronics30 in thepatient monitoring device10 from a low power state. Thecontrol unit26 can be notified of awaking of the other components by themonitoring system28. Thecontrol unit26 can set a status bit on themonitoring system28 only when thebattery24 needs to be in a full power state. Thecontrol unit26 then forces a power cycle.

Referring toFIG. 3, one embodiment of atelemetry system32 is illustrated. Thetelemetry system32 is in the communication with thesensors14 and orpatient monitoring device14 and ID of thepatient monitoring device10 and can include one ormore receivers34, acentral server36 with theCPU20. Thetelemetry system32 can optionally include adisplay42 and analarm44. Thetelemetry system32 receives information fromsensors14 and or the monitoring device of a user's habits, activities, and the like, and then processes this information.Patient monitoring device10 with its unique ID andsensors14 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 thetelemetry system32. It should, however, be appreciated that thetelemetry system32 may be implemented to track and/or monitor a much larger number of users.

In one embodiment of the present invention, radio frequency (RF) devices that aresensors14 and/or chips may serve as the identifying devices. Each source,sensor14, 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.

Telemetry system32 of the present invention may include a Real-Time Location System (RTLS)46 and Real-Time Sensing System (RTSS)48 with RF technology. The RF technology may include active and/orpassive RFID sensors14 and an RF wireless array system as areceiver34. The RF technology in theRTLS46 andRTSS48 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.

Thesensors14 may communicate directly with each other and/or relay telemetry data directly to base receiving RF device(s) orbase receivers34. Thebase receivers34 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. Thecomprehensive telemetry system32 using RF technologies such as UWB, ZigBee, Wi-Fi, GPS data system can be utilized as described above.

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

Theactive sensors14 may employ dual-radio architecture. In one embodiment,active sensors14 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.

Thepatient monitoring device10 gathers telemetry data, communicates that data to a base station, BLUETOOTH® enabled device, or smart phone and the like. From the base station, thepatient monitoring device10 can receive firmware updates or via a BLUETOOTH® enabled device. Thepatient monitoring device10 can receive updates wirelessly. The base station can receive firmware updates from Network Systems, take telemetry data from thepatient monitoring device10 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 thepatient monitoring device10 wirelessly and deliver information to the servers for processing.

In one embodiment, thepatient monitoring device10 uses an accelerometer, gyroscope, GPS sensor, a BLUETOOTH® chip, and a heart rate monitor.

As a non-limiting example, for heart monitoring, the accelerometer,sensor14, determines when to sample thesensors14 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.

As a non-limiting example, aheart rate monitor14 detects the user's heart rate in order to accurately determine the user's activity level, behavioral patterns and the like.

An 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.

Classifiers 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.

A 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.

Fuzzy 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.

In various embodiments, thepatient monitoring device10 has additional features. In one embodiment, thepatient monitoring device10 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 thepatient monitoring device10.

In another embodiment, thepatient monitoring device10 remotely reminds and can be used to administer medications. As a non-limiting example, thepatient monitoring device10 can inject adrenalin. In one embodiment, thepatient monitoring device10 has sleep pattern recognition based on movement and heart rate.

In various embodiments, thepatient monitoring device10 uses algorithms to determine activity type, behavioral patterns and user habits based on collected data.

In one embodiment, thepatient monitoring device10 uses the accelerometer information to improve the heart rate monitor. As a non-limiting example, thepatient monitoring device10 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.

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

User activity, performance and action can be based on the acceleration and angular velocity of thepatient monitoring device10. In one embodiment, thepatient monitoring device10 has a feature where thepatient monitoring device10 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, thepatient monitoring device10 can “orders” the person another one based on the prior history.

In one embodiment, thepatient monitoring device10 features near-bypatient monitoring device10 recognition that provides for otherpatient monitoring device10 devices to be recognized within a particular vicinity and are able to share and transfer data between them. Thepatient monitoring device10's data analysis and feedback can be based on current or previous sensor output. Thepatient monitoring device10 can alert the user when to charge thepatient monitoring device10 and when it is the most convenient for the user.

In one embodiment, thepatient monitoring device10 provides feedback via color change. An outer shell of thepatient monitoring device10 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, thepatient monitoring device10 is flexible in shape. As a non-limiting example, if the user puts thepatient monitoring device10 over their hand it can expand or contract, morphing to change size and shape.

In one embodiment, thepatient monitoring device10 can have a sync feature for multiple bands at the same time.

In one embodiment, thepatient monitoring device10 has data transfer to an external device that can be included or not included insystem32.Patient monitoring device10 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.

In one embodiment, thepatient monitoring device10 can disable the recording of one ormore sensors14 based on location, acceleration (or lack thereof) and the like.

In one embodiment, thepatient monitoring device10 detects different types of transportation and activity based on sensor data. In one embodiment,patient monitoring device10 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 thepatient monitoring device10 once.

In one embodiment, thepatient monitoring device10 recognizes the wearer based on biometric information, previous data, movement pattern, and the like. In one embodiment, thepatient monitoring device10 detects a new user based on an inability to match to user/usage patterns.

As non-limiting examples, a variety ofdifferent sensors14 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. Apressure sensor14 can be placed on a circulatory vessel such as a vein to detect pulse.

With thepatient monitoring device10 of the present invention, mechanical actions of the user can be triggered, recognized and evaluated.

As a non-limiting example, with multiple users andwearable devices10, a separatepatient monitoring device10 ID is assigned to each of the users A, B AND C, and thereafter the assigned transmitter/monitor14 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 thesensors14 is transferred to thereceivers34 via thewireless connections38 represented by a dashed line.

A network ofreceivers34 transfers the user activity and/or tracking data tosystem server16 viaconnection50.System server16 includes aprocessor52 configured to process the user data in a known manner. For example, theprocessor52 may convert raw user data acquired by thesensors14 into more conveniently readable data.

As a non-limiting example, thedisplay42 can be implemented to graphically convey user information fromsystem server16 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.Alarm44 may be included in this embodiment.

In some embodiments,system32 ID circuitry delivers a unique ID to the wearable device fromdatabase18. BLUETOOTH® chips can be coupled with otherwearable devices10 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.

The ID circuitry ofsystem32 can include a number of system/components: unique ID storage, communication system, which reads and transmits the unique ID from the unique ID storage,battery24 or power system that provides power to enable communication with thepatient monitoring device10, 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 thetelemetry system32,sensors14 and sensing devices are disposed onwearable devices10 worn by users. Data, such as movement, location, speed, acceleration, and the like, can be acquired, captured and provided tosystem32.

System32 and an associated network can include an identification reference, including user activity, performance and reference information for eachindividual sensor14 and location.

The user activity, performance metrics, data and the like captured bysystem32 can be recorded into standard relational databases SQL server, and/or other formats and can be exported in real-time.

In various embodiments, thepatient monitoring device10 and/orsystem32 are fully sealed and have inductively charges. All communication is done wirelessly.

In one embodiment, there are no electrical contacts, physical contacts or connections with thepatient monitoring device10. Thepatient monitoring device10 is seamless. Thetelemetry system32 can include a microprocessor withCPU20, memory, interface electronics andconditioning electronics33 configured to receive a signal from thesensors14. In one embodiment, all or a portion of theconditioning electronics33 are at thepatient monitoring device10.

In one embodiment, theCPU20 includes aprocessor52, 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 theprocessor52 to store information and a master dock. The microprocessor is controlled by the master clock that provides a master timing signal used to sequence themicroprocessor52 through its internal states in its execution of each processed instruction. In one embodiment, themicroprocessor52, and especially theCPU20, is a low power device, such as CMOS, as is the necessary logic used to implement the processor design. Thetelemetry system32 can store information about the user's activity in memory.

This memory may be external to theCPU20 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 thesensors14 can be in communication withconditioning electronics33 that with afilter35, with scale and can determine the presence of certain conditions. This conditioning essentially cleans the signal up for processing byCPU20 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 theCPU20. Thetelemetry system32 can also provide for intelligence in the signal processing, such as achieved by theCPU20 in evaluating historical data.

In one embodiment, the actions of the user wearing thepatient monitoring device10 with the unique ID can be used for different activities and can have different classifications atsystem32.

The 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 indatabase18.

In one embodiment, the user wearing thepatient monitoring device10 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.

As a non-limiting example, thepatient monitoring device10 communicates with a base station atsystem32. Thepatient monitoring device10 can intelligently switch between data transfer and charging based on sensor readout. Thepatient monitoring device10 can represent data based on connected devices.

In one embodiment, thepatient monitoring device10 has the capability of providing recommendations, popularity of locations or activities based on acquired data from the user.

In one embodiment, thepatient monitoring device10 has the capability of introducing the user to other people or users based on their data and the user's data.

In one embodiment, thepatient monitoring device10 can determine emotion of the user.

In one embodiment, thepatient monitoring device10 uses incremental data transfer via BLUETOOTH® and the like. Thepatient monitoring device10 can transmit data through the inductive coupling for wireless charging. The user is also able to change the frequency of data transmission.

Thepatient monitoring device10 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, thepatient monitoring device10 has data storage. As a non-limiting example, storage of telemetry data onpatient monitoring device10 can be amounts up to about 16 mg.

In one embodiment, data transferred if it's in a selected proximity of a base station ofsystem32 or in proximity of an associated connected network. In one embodiment, thepatient monitoring device10 has a dynamic change of data capture frequency. Thepatient monitoring device10 can be programmed to instantly change how often it samples anysensor14 based upon the sensor data. Intelligent data sampling is based on sensor readout.

Thepatient monitoring device10 can receive firmware updates via abase station110 ofsystem32. In one embodiment, thepatient monitoring device10 presents analyzed data and feedback on a website. In one embodiment, thepatient monitoring device10's software is based on unique human movement. Thepatient monitoring device10 is able to identify its wearer based on the unique patterns of movement, location check-ins and daily habits of the user.

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

In 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.

In one embodiment, thepatient monitoring device10 has artificial intelligence. Awearable device processor54 implements logic resources that exist onpatient monitoring device10.

In one embodiment,patient monitoring device10 engages in the routing of user information to third parties based on predefined rules, based onsystem32 analysis.

In one embodiment,patient monitoring device10 includes one ormore processors54 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.

The ID can be sent from thepatient monitoring device10 in a variety of different transmit modes, which may be provided as part of the firmware or software of an ID orsensor transmitter14, and which may be utilized selectively during the operation of saidsensor transmitter14, 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, thesensors14 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/transmitter14, as needed. Referring toFIG. 4,system32 includesdata base18 which contains the desired transmitter, sensor,14 personality data, as well as, the address/device ID bits for eachpatient monitoring device10.

In one embodiment, the initial programming of thepatient monitoring device10 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.

In one embodiment, an inductive field coil is used for programming thesensors14 and ID ofpatient monitoring device10.

As illustrated inFIG. 4, thepatient monitoring device10 can include asensor14 with an output that be received by anamplifier56 and decoded by an I/O decoder58 to determine I/O logic levels, as well as, both clock anddata information60. 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 amemory62. Any of these connections provides a logical link from the system'sdatabase18 to thesensor14, ID of thepatient monitoring device10, as shown inFIG. 5.

In one embodiment, illustrated inFIG. 5, thesystem32 chooses the necessary programmable sensor functions and stores them intodatabase18. In one embodiment, in order to insure that an unauthorized user cannot connect into and programpatient monitoring device10 the following procedure may be used:

Both thesensor14 andreceiver34 contain an identical, repeatable pseudo randomization algorithm in ROM or in ASIC logic.

Referring toFIG. 6, the algorithm is applied tooutgoing programming data64 fromsystem32 and produces a number of security/randomization bits66 that can be appended to the outgoing programming message ormessage68 and sent to asensor14.

Referring toFIG. 7 thesensor14 likewise applies this pseudo randomization algorithm as the security/randomization bits66 to the outgoing programming data, now forming theincoming programming data70 tosensor14 and produces a several bit result in theshift register71. 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.

Optionally, in one embodiment, before asensor14 accepts this programming, stored in an address andpersonality register73, both the pseudo random code, stored in data in ashift register75 fromsystem32 and asensor14, in ashift register71 must match via a comparator ID,77, 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.

In 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 thepatient monitoring device10 is then done with a new, unused spread spectrum code or system code or frequency channel can be selected, or, in the alternative,CPU20.

As illustrated inFIG. 5, step “E” would include, for example, the step of thesensor14, inputting the programming message and saving a seed inmemory62; with thesensor14 utilizing the seed to code digital data bits transmitted.

As illustrated inFIG. 8, the location of apatient monitoring device10 with the ID andsensors14 can be determined. As a non-limiting example, in one embodiment thepatient monitoring device10 includes asensor14 that can provide a position signal having positioning data (e.g., raw GPD data or pseudo ranges) and the ID is transmitted from thepatient monitoring device10 tosystem server16.Server16 receives the position signal and analyzes the signal to generate information representing the location of thepatient monitoring device10.Server16 transmits this location information to a client computer where the location of thepatient monitoring device10, allowing a user to identify the location of theremote sensor14.

In one embodiment, the position signal transmitted by theremote sensor14 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 thepatient monitoring device10 or by use of a user's mobile device. Pressing the panic button may causemobile device74 to transmit an emergency signal to acell site76 where the emergency signal is relayed toserver16. In response,server16 can transmit Doppler information regarding in-view satellites, a fix command and a time trigger signal to thepatient monitoring device10.

When the location of thepatient monitoring device10 has been determined, software running onserver16 configuresserver16 such that a call or other signal is sent to a local emergency operator in the vicinity ofremote sensor14. When the call or signal is received at the emergency operator station, the location ofremote sensor14 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 ofremote sensor14 to the required emergency service (police, fire department, ambulance service, etc.). In other embodiments, instead of or in addition to a position report for theremote sensor14, the emergency operator may also be provided with information which identifies an emergency response vehicle in close proximity toremote sensor14.

As illustrated inFIG. 9, asensor14 of thepatient monitoring device10 can include aSNAPSHOT GPS receiver72. As described above,sensor14 uses information transmitted from separately locatedbase station110, mobile devices, computers, and other devices, to assist in determining the position of theremote sensor14, as more fully disclosed in U.S. Pat. No. 6,661,372, incorporated herein by reference.

As non-limiting examples, and as illustrated inFIG. 10, thesensors14 can be athermal transducer78, anacoustic transducer80, and amagnetic transducer82. It will be appreciated that the present invention is not limited Thetransducers78,80, and82 in thepatient monitoring device10 can communicate with amicroprocessor84 also located in thepatient monitoring device10. Thepatient monitoring device10 can communicate with other devices via anRF transceiver86, anIRDA transceiver88, and/or anRF backscatter transceiver90. Each of the components in thepatient monitoring device10 receives power as necessary from thebattery24, which may include the rechargeable battery.

Theacoustic transducer80 may include a microphone, a low-pass filter, a gain amplifier, and a threshold comparator. Theacoustic transducer80 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 themicroprocessor84. 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 themicroprocessor84 for processing.

Themagnetic transducer82 can include a magnetic sensor integrated circuit, a differential instrumentation amplifier, a low-pass filter, two gain amplifiers, and a threshold detector. Themagnetic transducer82 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 themicroprocessor84 for processing.

A 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 LMV393IPWR 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 themicroprocessor84 for data collection.

Thethermal transducer78 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.

Even 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 themicroprocessor84, the thermal transducer can perform a 9-bit temperature conversion in 75 milliseconds.

TheRF transceiver86 may include an RF Monolithic DR3000 transceiver, although any suitable transceiver or separate transmitter andreceiver34 would suffice. Thistransceiver86 allows for both digital transmission and reception. Thetransceiver86 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 themicroprocessor84. Thetransceiver86 can use an antenna92 (FIG. 11) 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.

TheIRDA transceiver88 may include a Sharp GP2W0110YPS infrared transceiver, although any suitable IRDA compliant infrared transceiver would suffice. Thistransceiver88 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.

The RFbackscatter transmission device90 may include circuitry available from Alien Technology (of Morgan Hill, Calif.) for receiving and transmitting signals via RF backscatter.Battery24 may be a 3.6volt 1/2 AA lithium battery with a capacity of 1.2 amp hours. Thebattery24 can be apower source24 that can include a Texas Instruments TPS76930DBVT 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.

TheRF backscatter transceiver86 in thepatient monitoring device10 communicates with an RF backscatter reader94 such as aclass 3 reader from Alien Technology. The reader94 transmits data to thebackscatter transceiver90 of thepatient monitoring device10 by broadcasting encoded RF pulses and receives data back from thetransceiver86 by continually broadcasting RF energy to thesensor10 and monitoring the modulated RF reflections from thesensor10.

TheRF backscatter transceiver90 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 themicroprocessor84 so that data reception can begin. In one embodiment, the reader94 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 reader94 can be On-Off Keying (OOK). In one embodiment, the transmission power is 1 watt. The operation of the reader94 may be controlled by an external computer (not shown) as directed by Labview software via a RS-232 serial link.

TheRF transceiver86 can communicate with an external RF transceiver96 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. Theactive RF antenna92 can be a quarter-wavelength monopole made from a guitar G-string and appropriate matching circuitry. Two control lines from themicroprocessor84 can be used to select the mode of operation, choosing from transmit, receive, and sleep. Theactive RF receiver34 consumes the most power in receive mode compared to the other two communication links.

FIG. 6 shows the relative positioning and shape of theactive RF antenna92 and theRF backscatter antenna98.

TheIRDA transceiver88 of thepatient monitoring device10 can communicate with anexternal IRDA transceiver100 that may be identical to theIRDA transceiver88. Alternatively, theIRDA transceiver100 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, theIRDA transceiver88 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.

When any one of thetransceivers86,88 and90 on thepatient monitoring device10 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.

In 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 inFIG. 2. It can include a preamble to reset and spin-up the state machine of theRF receiver34 and to properly bias the receiver's34 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.

Furthermore, the encoding scheme for the three symbols is shown inFIG. 12. The entire packet is DC balanced to maintain an optimal level on the data slicer/threshold detector and thereceiver34. Data is sent most significant bit first.

The 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 thereceiver34 to determine when the entire packet has been received and processing of information can begin. The packet structure is shown inFIG. 13 and the IRDA/UART encoding scheme is shown inFIG. 14.

The data bytes contained in a packet transmitted to thesensor10 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 thereceiver34, even if the CHECKSUM is correct.

The 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.

The 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.

Thetransceivers86,88 and90 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 aremote sensor10.

FIG. 15 illustrates one embodiment of anexemplary network101 that can be used with the present invention. As shown inFIG. 15 a wireless packetdata service network102 that can be utilized with thepatient monitoring device10. Anenterprise network104, 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 servers106-1 through106-N can be included and disposed as part of theenterprise network104 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 thewearable devices10. Thepatient monitoring device10 can be in communication with a variety of personal information devices other than thepatient monitoring device10, including but not limited to, computers, laptop computers, mobile devices, and the like.

Additionally,system server16 may be interfaced with theenterprise network104 to access or effectuate any of the services from a remote location using apatient monitoring device10. 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 asNetwork Systems108, as well as the wireless packetdata service network102 operable with apatient monitoring device10 via suitable wireless network infrastructure that includes a base station (BS)110. In one embodiment, atrusted relay network112 may be disposed betweenNetwork Systems108 and the infrastructure of wireless packetdata service network102.

In another embodiment, the infrastructure of the trustedrelay network112 may be integrated with the wireless packetdata service network102, 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 device10 may be capable of receiving and sending messages, web browsing, interfacing with corporate application servers, and the like, regardless of the relationship between thenetworks102 and112. Accordingly, a “network node” may include both relay functionality and wireless network infrastructure functionality in some exemplary implementations.

In one embodiment, the wireless packetdata service network102 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 packetdata service network102 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 packetdata service network102 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.

Referring now toFIG. 16(a) through 16(d), in one embodiment, thepatient monitoring device10 is in communication with aninteraction engine120 that can be at amobile device74 orsystem32. The interface engine can be a software application running onmobile device74 associated with another party, including but not limited to a merchant, an associate, a friend, and the like. The enables thepatient monitoring device10 user and a merchant to interact with atransaction engine114 to and enter into a financial transaction for the transfer of funds from a thirdparty payment system116 that is independent of thepatient monitoring device10 user'sfinancial account118, and complete a transaction. It should be noted that thepayment system116 can be affiliated with thefinancial account118 or can be a separate and non-affiliated with thefinancial account118. Theinteraction engine120 can take input of information related to a transfer of funds from thepatient monitoring device10 users'financial accounts118 as input to thetransaction engine114 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 theinteraction engine114 can include, an amount of a transaction, additional items related to the transaction, authorization and/or signature of thepatient monitoring device10 user.

In one embodiment, themobile device74 receives information from thepatient monitoring device10, e.g., the unique ID.

Theinteraction engine120 can also present products or services provided by a merchant to directly to or throughsystem32 to thepatient monitoring device10 user. In one embodiment, thepatient monitoring device10 users can use themobile device74, the WEB, and the like, to view, text, pictures, audio, and videos, and browse through the products and services on themobile device74, personal computers, other communication devices, the WEB, and anything that is BLUETOOTH®, anything associated with Network Systems, and the like.

In one embodiment, thetransaction engine114, which can be at themobile device74, or external to themobile device74, including but not limited topatient monitoring device10 and the like, takes decoded financial transaction card information from adecoding engine122, internal or external to themobile device74, and a transaction amount from aninteraction engine120, also internal or external to the mobile device. Thetransaction engine114 then contacts thepayment service116, and or thepatient monitoring device10 users'financial account118, such as an acquiring bank that handles such authorization request, directly or through thepayment system116, which may then communicate with a financial transaction card issuing bank to either authorize or deny the transaction. Thepayment system116 can include a user database, a transaction database, a product database, and the like. These databases can also be external topayment system116. If the third party authorizes the transaction, then thetransaction engine114 transfers funds deducted from the account of thepatient monitoring device10 user, or thepayment system116 can already have those funds readily available, to an account of a third party which can be anotherpatient monitoring device10 user, a merchant, and the like, and provides transaction or transfer of fund results to theinteraction engine120 for presentation to a third party.

In one embodiment, thetransaction engine114 does not have the financial account or financial card information of thepatient monitoring device10 user that is doing the transfer. In some embodiments, thetransaction engine114 keeps only selected information of thepatient monitoring device10 user'sfinancial accounts118 or financial transaction cards.

In one embodiment, the wearable device communicates directly, withoutmobile device74, with thepayment system116 and/or the user'sfinancial account118 or associated financial institution.

In one embodiment, thetransaction engine114 communicates and interacts with thefinancial account118 or associated financial institution directly or through thepayment system116, through a user database, product database, and transaction database, which databases can be separate from or included in thepayment system116, 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.

With social networking applications, thepatient monitoring device10, with its unique ID, is an ID device. Information from thepatient monitoring device10 relating to social networking, and the like, communicates withsystem32. In this manner, thewearable devices10, 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 apatient monitoring device10 for a variety of social networking and other communication applications. Additionally,patient monitoring device10, with itssensors14 and ID can communicate directly to social networking sites, Network Systems, cloud services, and the like.

In one embodiment, with the current permissions given by the wearable device users, marketers, companies or individuals who wish can deliver advertisementpatient monitoring device10 users. More particularly,system32 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 topatient monitoring device10 users with the appropriate permissions. In one embodiment,system32 maintains the anonymity of thepatient monitoring device10 users while allowing the marketers to have their advertisements delivered to those that fall within their defined market segment.

In 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.

System32 may serve a number of purposes without straying from the scope of the present invention. For example, the social networking service may allowpatient monitoring device10 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.

In one embodiment, the step of providing personal information to start an account withsystem10 for different applications may be performed by a purchasing or acquiring apatient monitoring device10, 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 ofsystem32.

In another embodiment the step of providing personal information to start an account withsystem32 bypatient monitoring device10 users may be performed automatically. In this embodiment,system32 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.

In a further embodiment, the step of providing personal information tosystem32 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.

The 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.

In one embodiment, a computer generated personal page may be provided to apatient monitoring device10 user. The personal page may utilize a computer to automatically import the information provided when signing up withsystem32 or a social networking service. In another embodiment, the information and formatting of the personal page can be customizable.

Whenmobile device74 is used, it communicates with one ormore sensors14 that are at thepatient monitoring device10, as more fully herein. The mobile device can74 pull fromsystem32 updates from theserver16, including but not limited to settings such as alarms, name of the wearable device wearer using the ID, asensor14 and the like.Sensors14 at thepatient monitoring device10 can send streams of information, both encrypted and non-encrypted to the mobile device and then to the server atsystem32.Server16 sends encrypted, and can also send non-encrypted information, tomobile device74. Processing of this information can be achieved at themobile device74, and/orserver16.Mobile device74 can receive raw sensor information from thepatient monitoring device10. This information can be compressed as well as non-compressed. A compression algorithm, at the wearable device and/ormobile device74 orsystem32, can be used in order to minimize the amount of information thatserver16 sends.System32 can include additional encryption and/or decryption systems.

Referring now toFIG. 17, a social network circle/group124 (hereinafter “SNET circle”) comprisingsocial devices126, includingpatient monitoring device10, is shown. Beyond traditional social networking features and services, aSNET circle124 and associatedsocial devices124 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 device10 can utilizenetwork101 for communication with the SNET circle, as well as with other social networking sites, or throughsystem32.

Briefly, membership in theSNET circle124 may comprise docked and undockedsocial devices124 and human SNET circle members [104]128, as well as proxies thereof. Further,SNET circle124 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 robots130, SNET security device(s)132, appliances, vehicles andservice providers134, common or authorized members/functionality of other SNET circles124, and the like. Further, access to specific content and resources of aSNET circle124 may be shared with members of additional SNET(s)124, 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.

In the illustrated embodiment, formation, maintenance and operation ofSNET circle124 is performed by standalone or distributed SNET processing circuitry andsoftware136. 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, theSNET processing circuitry136 may be included in a standalone server, server farm, cloud-based resources,network101,system32 and/or the various types of devices described below, and incorporate authentication andsecurity functionality138. 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 theSNET circle124 may involve one or more of a social device association/control module140, a SNET circlemember profiling module142, and an adaptive resource allocation andarbitration module144 as described more fully below.

Distribution of internal and external SNET content/media146 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/media146 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 tosocial devices124 of theSNET circle124, may occur over anNetwork Systems backbone148, cellular communication system, WAN, LAN, and the like.

FIG. 18 illustrates an embodiment of asocial group150 comprising a variety of members in accordance with the present invention that can communicate through theirwearable devices10 and other devices, including but not limited tomobile devices74. In this embodiment, membership in thesocial group150 may include a variety of novel social system members [204]152 functioning in various capacities within thesocial group150. As will be understood, certain of thesocial system members152 may support direct or indirect associations between thesocial group150 and human members/non-members andusers154.

In the illustrated embodiment, social system members (or nodes)152 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.

Social system members152 further include devices configured to operate as nodes within thesocial group150. Social functionality in such devices and othersocial system members152 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, ageneral purpose device152amay include social code that enables participation in thesocial group150. In a further embodiment, adevice152bdesigned to include social functionality may participate in thesocial group150 through a combination of non-social code and a social shim layer or driver wrapper. In yet another embodiment, a member device152chaving a social design may utilize additional social code, including code specific to asocial group150.

Participation in thesocial group150 is supported through functionality that includes automated and member-triggered membership invitations and processing (membership management)156. More particularly,membership management156 may function to invite prospective members to participate in thesocial group150 through automatic, automated and member-triggered processes. For example,membership management156 might be configured by ahuman user154 to establish asocial group150 by automatically inviting/accepting social system members having certain characteristics (such as devices owned or controlled by the user or acquaintances of the user).

Processing of accepted invitations and unsolicited requests to join thesocial group150 may be conditioned upon input or authorization from an existing social system member(s)152 or human user(s)154 (e.g., through a user interface). Similarly,membership management156 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.

Access to and visibility of resources of asocial group150, including services and data, may be managed through general and member class-specific access configurations158. For example, if membership in thesocial group150 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.

Thesocial group150 may offer a wide variety ofmember services162, including both internal and external services accessible bysocial system members152. By way of example, thesocial group150 may offer email or other communication services between full members and/or authorized guest members and visitors. As with other resources of thesocial group150, access control and constraints onmember services162 may be applied to individual members or classes of members.

FIG. 19 is a functional block diagram illustrating a social network (SNET)infrastructure164, as more fully described and disclosed in EP 2582116, fully incorporated herein by reference.

In one embodiment, illustrated inFIG. 20,wearable devices10 are in communication with a distributedcomputer network166 that can includenetworks102,104,112, coupled toNetwork Systems108 andsystem32 via a plurality of communication links168.Communication network166 provides a mechanism for communication withsystem16,patient monitoring device10, social media networks,mobile devices74, payment systems,116, theengines114,120,122, components ofsystem16, and with all third parties, as described above.

Thecommunication network166 may itself be comprised of many interconnected computer systems and communication links. Communication links168 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 inFIG. 20. These communication protocols may include TCP/IP, HTTP protocols, wireless application protocol (WAP), vendor-specific protocols, customized protocols, and others.

While in one embodiment,communication network166 is the Network Systems, in other embodiments,communication network166 may be anysuitable communication network166 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.

System32 is responsible for receiving information requests fromwearable devices10, third parties, and the like, performing processing required satisfying the requests, and for forwarding the results corresponding to the requests backing to the requestingpatient monitoring device10 and other systems. The processing required to satisfy the request may be performed byserver16 or may alternatively be delegated to other servers connected tocommunication network166.

FIG. 21 shows an exemplary computer system that can be utilized with thewearable devices10. In an embodiment, a user interfaces withsystem32 using apatient monitoring device10 and then through a computer workstation system, such as shown inFIG. 21, a mobile device, and the like.

Thecommunication network166 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.11 ac, 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.

FIG. 22 shows a system for activity collection and building a social graph for networkpatient monitoring device10 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 thewearable device users10 are logged into a membership site, such as a social networking site.

Resources170 and172 gather activity data and pass this data to anactivity storage server174, typically viaNetwork Systems108.Partner resource172 may be processed by a partner back end, and then this data is passed toactivity storage server174.

Patient monitoring device10 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. Apatient monitoring device10 user (sender) can share information (e.g., video, photo, link, article, or other) by posting to a site. Thepatient monitoring device10 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 bysystem32.

Messenger applications such as those onmobile device74 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.

Users use messenger application to send links and other information to other users, and also achieve this using theirwearable devices10. A user (sender) can copy a link (e.g., via a clipboard) and send to one or more users via the messenger application withmobile device74 and with itspatient monitoring device10. When a recipient user clicks on the link, there is connection activity between the sender and recipient for that link.

Sharing 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 atactivity storage server174, typically through Network Systems.Server174 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.

The activity data collected is stored atserver174, usually in a database or file systems on hard drives ofserver174. 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 component178 can run on the same server that stores the activity data, or may run on a separate server that accessesstorage server174.

In one embodiment, a build-update graph180 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 graph180 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.

For the incoming activity data collected, identifynodes182 scan through and find the nodes and edges of the social graph that need to be updated.

Whensystem32 is processing a user activity data it has the ID of thepatient monitoring device10 user and attributes this activity to thatpatient monitoring device10 user.

When 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 asocial graph184 with nodes modeling user profiles and edge modeling sharing activities among users.

FIG. 23 shows a samplesocial graph186 wherecircles188 represent nodes and lines areedges190 representing sharing interactions betweennodes182. There can be one ormore edges190 between twonodes182.Several edges190 betweennodes182 can indicate sharing activities along several categories: e.g., travel, computers, sports, and others.

Nodes182 connected together directly have one degree of separation.Nodes182 connected through one other node have two degrees of separation. Depending on a number of interveningnodes182 between twonodes182, this will be a number of degrees of separation between the twonodes182.

In a specific implementation, edges190 betweennodes182 indicate sharing activities along several categories such as travel, computers, sports, and the like. For each additional new sharing category, anadditional edge190 is added. In a specific implementation, for each additional new sharing interest category, anadditional edge190 is added. Further, in an implementation, the sharing interaction oredges190 between thenodes182 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.

Some 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. Formobile devices74 the sharing activities can further include: sending SMS-type messages between users. In some embodiments, messages can be sending fromwearable devices10.

Once two users connect, such as onepatient monitoring device10 sending anotherpatient monitoring device10 user a message containing a link concerning a topic. When the recipient user clicks on the link from the sender user,system32 will add anedge190 to graph186 to represent the activity. Anedge190 is added to thegraph186 to represent this sharing activity between the two users.

In a specific implementation, twopatient monitoring device10 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.

In one embodiment of the present invention, illustrated inFIG. 24, thepatient monitoring device10 includes thealarm44. In one embodiment, thealarm44 sends a message to the patient only when the patient is awake. The awake status of the patient can be determined by themonitoring device10 itself, themonitoring device10 in combination with thetelemetry system32, or by thetelemetry system32.

Thealarm44 can be visual, by motion, audio, and the like. Thepatient monitoring device10 can include avisual display42 that can communicate an alert to the patient. In another embodiment, thealarm44 can provide an audio alert to the patient.

Thedisplay42 can be a touch screen display, such that the patient or a bystander can communicate with thetelemetry system32.

In one embodiment, themonitoring device10 detects and awake or non-awake status of the patient. Thealarm44 is then activated when the patient is alert or awake, when an alert is required.

InFIG. 24, thealarm44 is positioned atpatient monitoring device10.Sensors14 are to theprocessor18 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, theprocessor84 communicates with an alarm circuit216 coupled to thedisplay42 or theaudio alarm44 and provide an alert to the patient regarding the patient's condition, a change in a patient parameter, a hazard, and the like.

The 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.

In one embodiment, the determination for the awake condition of the patient is determined at thetelemetry system32. In this embodiment, when a patient needs to receive an alert byalarm44,display42, and the like, thetelemetry system32 sends a wireless signal to themonitoring device10. The signal can be sent to theprocessor84, circuit216,transceiver86 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.

The 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.

Claims (15)

What is claimed is:

1. A system for using telemetry data relative to individual sleep information and sleep behavior information of an individual, comprising:

a monitoring device that includes a microphone, a transmitter and at least two sensors, the at least two sensors selected from at least sensors that in combination determine: air quality, sound level/quality, light quality, and ambient temperature near the individual;

an accelerometer or other movement detecting device configured to detect a movement information for the individual relative to the individual sleep information and the sleep behavior information of the individual, wherein the accelerometer, or the other movement detecting device, and the monitoring device are configured to assist in determining the individual sleep information and the sleep behavior information, and a recording by the at least sensors being disabled in response to the detection of the movement information for the individual by the accelerometer or the other movement detecting device;

an alarm at the monitoring device or the accelerometer or the other movement detecting device that in operation only provides an alert corresponding to a detected sleep parameter of the individual with respect to the movement information detected for the individual; and

a telemetry system in communication with the monitoring device, the telemetry system including a database of identifiers.

2. The system ofclaim 1, wherein an awake status of the individual is determined by the monitoring device, the accelerometer or the other movement detecting device and the telemetry system.

3. The system ofclaim 1, wherein the alarm is selected from a group consisting of visual, motion, audio, and vibratory alarms.

4. The system ofclaim 1, further comprising:

a visual display at the monitoring device.

5. The system ofclaim 4, wherein the visual display is a touch screen display.

6. The system ofclaim 1, wherein the monitoring device further includes a processor.

7. The system ofclaim 1, further comprising:

a control system at the monitoring device to orchestrate communication between different systems.

8. The system ofclaim 1, further comprising:

a noise reduction element at the monitoring device to reduce signal noise.

9. The system ofclaim 1, wherein conditioning electronics clean a signal for processing by a central processing unit (CPU) of the telemetry system.

10. The system ofclaim 9, wherein the CPU evaluates historical data.

11. The system ofclaim 1, wherein the telemetry system in operation creates different classifications for data received from the monitoring device.

12. The system ofclaim 1, wherein the telemetry system in operation provides firmware updates to the monitoring device.

13. The system ofclaim 1, wherein streams of information are sent from at least one sensor at the monitoring device to the telemetry system.

14. The system ofclaim 13, wherein the streams of information are capable of including both encrypted information and non-encrypted information.

15. The system ofclaim 13, wherein the streams of information are sent from the monitoring device to a mobile device or a computer.

Images