Mobile panic button for health monitoring system
Granted 18 Nov 2014 · 1 office action
Assignee: pomdevices, LLC
Law firm: Law firm · Log in to unlock
Attorney: Attorney · Log in to unlock
Inventors: Ajit Pendse · Examiner: Benjamin C Lee · AU 2684 · TC 2600
Life of the application
10 dated eventsAbstract
In one example, a mobile device with a panic button includes a surface structured to removably engage a surface of a docking station. The mobile device includes a first interface to communicatively couple the mobile device to the docking station at least when the surfaces are engaged, the first interface comprising a short range wireless transceiver or an electrical connector to make contact an electrical connector of the docking station. The mobile device includes a second interface comprising a long range wireless radio. A processing device of the mobile device is configured to relay messages between the docking station and a remote caregiver computing device using the first and second interfaces to enable synchronization between the mobile device and the docking station.
Description
8 parts›This application is a non-provisional of U.S. Provisional…
This application is a non-provisional of U.S. Provisional Application No. 61/378,540 filed on Aug. 31, 2010, entitled: MOBILE PANIC BUTTON FOR HEALTH MONITORING SYSTEM, and a continuation in part of U.S. Non-provisional application Ser. No. 13/151,528 filed on Jun. 2, 2011, entitled: INTERACTIVE ELECTRONIC GAME RESULTS AS HEALTH INDICATORS, and a continuation in part of U.S. Non-provisional application Ser. No. 13/151,034 filed on Jun. 1, 2011, entitled: META SMS/TEXT DATA EXTRACTION, and a continuation in part of U.S. Non-provisional application Ser. No. 13/104,371 filed on May 10, 2011, entitled: ACTIVITY TREND DETECTION AND NOTIFICATION TO A CAREGIVER, and a continuation in part of U.S. Non-provisional application Ser. No. 13/102,300 filed on May 6, 2011, entitled: AIDED CONSTRUCTION OF SMS STATUS MESSAGES TO CAREGIVERS, and a continuation in part of U.S. Non-provisional Application No. 13/151,572 filed on Jun. 2, 2011, entitled: MONITORING ELECTRONIC DEVICE USAGE IN A MANAGED HEALTHCARE ENVIRONMENT, and a continuation in part of U.S. Non-provisional application Ser. No. 13/217,649 filed on Aug. 25, 2011, entitled: MOBILE DEVICE USER INTERFACE FOR HEALTH MONITORING SYSTEM, each of which is incorporated herein by reference in its entirety.
›COPYRIGHT NOTICE
©2010-2011 pomdevices, LLC. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 CFR §1.71(d).
›BACKGROUND OF THE INVENTION
Many devices and services have been provided to consumers that aim to decrease complexity and increase safety and security for the older adult. Such devices are often single-purpose, push button devices that may be worn, carried, or otherwise situated hopefully within reach of an older adult who may need assistance. Such devices transmit basic information such as a device identifier to a central monitoring station or terminal, which then passes the information on to a caregiver or appropriate authorities such as police, fire, medical, or 911 call takers. In life-or-death situations, such a “middle man” can cost the user precious time that could make the difference between life and death.
›SUMMARY OF THE INVENTION
In one example, a mobile device including a panic button is provided. The mobile device includes a long range wireless interface (such as radios used in cellular telephones). The mobile device is configured to wirelessly transmit an alert using the long range wireless interface responsive to actuation of the panic button.
An intelligent docking station having a surface structured to engage with the mobile device is also provided. The intelligent docking station includes a wired or short range wireless interface configured to communicatively couple the docking station to the mobile device at least when the surfaces are engaged.
The intelligent docking station includes a processing device configured to connect to a remote caregiver computing device using the long range wireless interface of the mobile device, responsive to the surfaces being engaged (in the case of a wired connection), or responsive to the mobile device coming in range (in the case of a short range wireless connection). The processing device is configured to send or receive information to or from the remote caregiver computing device related to monitoring the health of the mobile device user.
The processing device may also be configured to synchronize the mobile device with some or all of the information sent to or from the remote caregiver computing device during the message exchange. In one example, the information synchronized to the mobile device can include a value for a target address setting of the mobile device. The target address setting controls which remote caregiver device(s) the mobile device notifies responsive to actuation of the panic button. For example, the target address may specify an SMS-capable wireless device telephone number, a land-line telephone number, an email address, etc.
›BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a docking station communicating with a remote caregiver computing device through a mobile device.
FIG. 2 illustrates a process of using interactive electronic game results as health indicators that may be performed by the docking station of FIG. 1 .
FIG. 3 illustrates a process of tagging text messages for health monitoring that may be performed by the docking station of FIG. 1 .
FIG. 4 illustrates a process of activity trend detection for health monitoring that may be performed by the docking station of FIG. 1 .
FIG. 5 illustrates a process of aided construction of SMS messages to caregivers that may be performed by the docking station of FIG. 1 .
FIG. 6 illustrates a process of collecting electronic device usage information for health monitoring that may be performed by the docking station of FIG. 1 .
›DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS · 1 of 3
In one aspect, the present disclosure is directed to provide users with a simple and easy way of contacting both caregivers and governmental authorities or other emergency responders with, for example, a push of a button. In a preferred embodiment, my system would include a docking station, which may be a PC or a custom hardware device. For example, a docking station for this purpose may be a compute station of the type described above, with greater or lesser interfaces and capabilities as appropriate or desired.
The docking station gathers information and provides analysis on the most recent data available for the patient, including medication monitoring, movement through the household, healthcare information, and other variables further described herein. A simple handheld device (clamshell style or otherwise) docks into the intelligent docking station and is made aware of the most recent data, including for example appropriate contacts (agencies, caregivers, emergency call takers, etc), health trends, etc. The handheld device in a presently preferred embodiment may have the following features:
Mobile communication enabled; A central processing unit; GPS functionality or other location capability; A single, preferably protected (from unintended use), “panic” button; Logic card; Software for interpreting data from the docking station and optimizing panic output data; and/or A hoop, clip, pin, button, etc. for securing the mobile device to a mobile device user or an article of clothing.
In one example, a handheld device having the above components may be significantly smaller than the typical cellular telephone. With regard to user input/output interfaces, the handheld device may have less extensive user input/output interfaces than the docking station. For example, the docking station may have a screen display, whereas the handheld device may have a more limited visual user output interface such as an indicator light, or even no light driven visual output.
The following scenario is illustrative:
Jane had been using a stationary healthcare monitoring device for several months. One morning, Jane forgets to take her medication (which is noted by the docking station) and goes out to pick up groceries. On her way out, Jane picks up her handheld device, which has all of her latest information, including that she forgot (or declined) to take her morning medication.
At the grocery store, Jane falls ill and presses the panic button on her handheld device. The device, using its mobile network connection, sends a message (e.g., pre-recorded voice, real-time voice, SMS text, etc) to both the primary caregiver (e.g. Jane's daughter), and the doctor that had been loaded into Jane's stationary device at home. The message may include most recent health updates, such as the failure to take medication that morning. Jane is rescued in time, which may not have been possible using present solutions.
FIG. 1 illustrates a docking station 8 communicating with the caregiver computing device 6 through a mobile device 30 having a panic button 31 . The processing device 11 of the docking station 8 is configured to detect a physical coupling (via a dock or other wired connection such as USB) or a short range wireless coupling (for example Bluetooth) of the mobile device 30 to the docking station 8 . The processing device 11 may be configured to establish the logical connection 301 over the Wide Area Network (WAN) 16 responsive to the detection. By the term “WAN” we mean to include any network that covers a broad area, including but not limited to, cellular networks; satellite-based networks; the Publicly Switched Telephone Network (PSTN) and other circuit switched networks; packet switched networks, etc. The logical connection 301 is established through the mobile device 30 using the connection between the mobile device 30 and the portable patient computing device 8 , as well as another connection extending from the mobile device 30 (which may be, for example, data service connection to a cell tower).
Having established the logical connection 301 , the processing device 11 synchronizes with the remote computing device 6 via the logical connection 301 . Synchronization can include sending information to the remote computing device 6 , or receiving information from the remote computing device 6 . The transmitted information can include medication monitoring information, information on movement of the mobile device user through the home, healthcare information, or any of the information handled by the portable patient computing device described in co-pending U.S. patent application Ser. Nos. 13/151,528, 13/151,034, 13/104,371, 13/102,300, 13/151,572, and 13/217,649, each of which are herein incorporated by reference in their entirety.
Before, after, or in parallel with the remote caregiver computing device synchronization, the processing device 11 synchronizes with the mobile device. This mobile device synchronization can include sending information to the mobile device 30 . Such transmitted information can include any portion of the information exchanged during the remote caregiver computing device synchronization, i.e. all or only selected portions of the information exchanged during the remote caregiver computing device synchronization.
In one example, during the mobile device synchronization, the processing device 11 updates a target address setting of the mobile device by, for example, transmitting a value indicating an address of a destination device(s). The target address setting controls which remote device(s) the mobile device notifies responsive to actuation of the panic button.
In another example, during the mobile device synchronization, the processing device 11 transmits information gleaned from patient monitoring, such as data indicating that the mobile device user skipped a dosage of medication. Such transmitted information can be stored on the mobile device 30 for later use, including but not limited to insertion in an emergency message transmitted by the mobile device 30 responsive to actuation of the panic button 31 and/or passive storage on the mobile device 30 to be extracted from the memory device 30 by emergency personnel (or any other caregiver).
›DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS · 2 of 3
FIG. 2 illustrates a process that may be performed by the docking station of FIG. 1 . Briefly, this process pertains to capturing data in response to a patient activity, such as playing an electronic game, and analyzing that data to infer changes in the patient's condition.
The processor 11 of docking station 8 may be configured to, alone or in combination with processing performed by a processor of caregiver computing device 6 , perform the process 201 shown in FIG. 2 , which is described in more detail in U.S. patent application Ser. No. 13/151,528 filed on Jun. 2, 2011 entitled “INTERACTIVE ELECTRONIC GAME RESULTS AS HEALTH INDICATORS”, which is herein incorporated by reference in its entirety. Any of the information gathered, transmitted, or stored according to process 201 may be synchronized to the mobile device 30 of FIG. 1 , in one example. Any of the information gathered, transmitted, or stored according to process 201 , or data derived therefrom thereof (such as a code representative of the information), may be inserted by the mobile device 30 into an emergency response message responsive to actuation of the panic button.
FIG. 3 illustrates another process that may be performed by the docking station of FIG. 1 . Briefly, this process pertains to extracting and analyzing data contained in multiple SMS or “text messages” received by a processor such as a remote caregiver device.
The processor 11 of docking station 8 may be configured to, alone or in combination with processing performed by a processor of caregiver computing device 6 , perform the process 301 shown in FIG. 3 , which is described in more detail in U.S. patent application Ser. No. 13/151,034 filed on Jun. 1, 2011 entitled “META SMS/TEXT DATA EXTRACTION”, which is herein incorporated by reference in its entirety. Any of the information gathered, transmitted, or stored according to process 301 may be synchronized to the mobile device 30 of FIG. 1 , in one example. Any of the information gathered, transmitted, or stored according to process 301 , or data derived therefrom (such as a code representative of the information), may be inserted by the mobile device 30 into an emergency response message responsive to actuation of the panic button.
FIG. 4 illustrates another process that may be performed by the docking station of FIG. 1 . Briefly, this process relates to trend analysis of a patient's daily activity and notifications to caregivers as may be indicated.
The processor 11 of docking station 8 may be configured to, alone or in combination with processing performed by a processor of caregiver computing device 6 , perform the process 401 shown in FIG. 4 , which is described in more detail in U.S. patent application Ser. No. 13/104,371 filed on May 10, 2011 entitled “ACTIVITY TREND DETECTION AND NOTIFICATION TO A CAREGIVER”, which is herein incorporated by reference in its entirety. Any of the information gathered, transmitted, or stored according to process 401 may be synchronized to the mobile device 30 of FIG. 4 , in one example. Any of the information gathered, transmitted, or stored according to process 401 , or data derived therefrom thereof (such as a code representative of the information), may be inserted by the mobile device 30 into an emergency response message responsive to actuation of the panic button.
FIG. 5 illustrates another process that may be performed by the docking station of FIG. 1 . Briefly, this process pertains to aided construction of SMS status messages to caregivers.
The processor 11 of docking station 8 may be configured to, alone or in combination with processing performed by a processor of caregiver computing device 6 , perform the process 501 shown in FIG. 5 , which is described in more detail in U.S. patent application Ser. No. 13/102,300 filed on May 6, 2011 entitled “AIDED CONSTRUCTION OF SMS STATUS MESSAGES TO CAREGIVERS”, which is herein incorporated by reference in its entirety. Any of the information gathered, transmitted, or stored according to process 501 may be synchronized to the mobile device 30 of FIG. 5 , in one example. Any of the information gathered, transmitted, or stored according to process 501 , or data derived therefrom thereof (such as a code representative of the information), may be inserted by the mobile device 30 into an emergency response message responsive to actuation of the panic button.
FIG. 6 illustrates another process that may be performed by the docking station of FIG. 1 . Briefly, this process pertains to collecting information from electronic devices, such as multimedia capable entertainment devices, for detecting a change in health of a patient.
The processor 11 of docking station 8 may be configured to, alone or in combination with processing performed by a processor of caregiver computing device 6 , perform the process 601 shown in FIG. 6 , which is described in more detail in U.S. patent application Ser. No. 13/151,572 filed on Jun. 2, 2011 entitled “MONITORING ELECTRONIC DEVICE USAGE IN A MANAGED HEALTHCARE ENVIRONMENT”, which is herein incorporated by reference in its entirety. Any of the information gathered, transmitted, or stored according to process 601 may be synchronized to the mobile device 30 of FIG. 1 , in one example. Any of the information gathered, transmitted, or stored according to process 601 , or data derived therefrom thereof (such as a code representative of the information), may be inserted by the mobile device 30 into an emergency response message responsive to actuation of the panic button.
Most of the equipment discussed above comprises hardware and associated software. For example, the typical portable device is likely to include one or more processors and software executable on those processors to carry out the operations described. We use the term software herein in its commonly understood sense to refer to programs or routines (subroutines, objects, plug-ins, etc.), as well as data, usable by a machine or processor. As is well known, computer programs generally comprise instructions that are stored in machine-readable or computer-readable storage media. Some embodiments of the present invention may include executable programs or instructions that are stored in machine-readable or computer-readable storage media, such as a digital memory. We do not imply that a “computer” in the conventional sense is required in any particular embodiment. For example, various processors, embedded or otherwise, may be used in equipment such as the components described herein.
›DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS · 3 of 3
Memory for storing software again is well known. In some embodiments, memory associated with a given processor may be stored in the same physical device as the processor (“on-board” memory); for example, RAM or FLASH memory disposed within an integrated circuit microprocessor or the like. In other examples, the memory comprises an independent device, such as an external disk drive, storage array, or portable FLASH key fob. In such cases, the memory becomes “associated” with the digital processor when the two are operatively coupled together, or in communication with each other, for example by an I/O port, network connection, etc. such that the processor can read a file stored on the memory. Associated memory may be “read only” by design (ROM) or by virtue of permission settings, or not. Other examples include but are not limited to WORM, EPROM, EEPROM, FLASH, etc. Those technologies often are implemented in solid state semiconductor devices. Other memories may comprise moving parts, such as a conventional rotating disk drive. All such memories are “machine readable” or “computer-readable” and may be used to store executable instructions for implementing the functions described herein.
A “software product” refers to a memory device in which a series of executable instructions are stored in a machine-readable form so that a suitable machine or processor, with appropriate access to the software product, can execute the instructions to carry out a process implemented by the instructions. Software products are sometimes used to distribute software. Any type of machine-readable memory, including without limitation those summarized above, may be used to make a software product. That said, it is also known that software can be distributed via electronic transmission (“download”), in which case there typically will be a corresponding software product at the transmitting end of the transmission, or the receiving end, or both.
Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. We claim all modifications and variations coming within the spirit and scope of the following claims.
Claims as granted
13 claimsLog in to read the claims of this application.
Log in to unlockClassifications
17 codes- G08B25/01
- G06F1/16
- G06F19/00
- G08B5/22
- H04W4/90
- H04W4/12
- H04W88/06
- H04W4/00
- H04Q1/30
- H04L29/08
- H04M1/72424
Claim changes
SoonSee which claims were amended, added or cancelled during examination, with every added and removed word marked.
The published claims of this application are not paired with the granted ones in what we hold.
File wrapper
See the full prosecution history — every USPTO and applicant action on this file, in order.
Log in to unlockDocuments
Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.
Log in to unlockChain of title
See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.
Log in to unlock