1. A system for monitoring a patient, comprising:
a sensor configured to drape around the patient’s neck, the sensor comprising an impedance sensor for measuring impedance signals from the patient, an ECG sensor for measuring ECG signals from the patient, a motion sensor for measuring motion signals from the patient, and a first wireless transceiver for transmitting information related to the impedance, ECG, and motion signals; and
a computer comprising a second wireless transceiver, video output system, and a CPU, the second wireless transceiver configured to receive the impedance, ECG, and motion signals and process them to determine physiological and exercise information, and the CPU configured to render a graphical user interface that guides the patient through a pre-determined exercise routine and ports the physiological and exercise information, or new information calculated therefrom, through the video output system so it can be displayed on a video display.
2. The system of claim 1, wherein the pre-determined exercise routine comprises instructing the patient to take a series of steps.
3. The system of claim 1, wherein the pre-determined exercise routine comprises a sequence of exercises.
4. The system of claim 1, wherein the impedance sensor is configured to measure an impedance baseline and impedance plethysmogram from the patient.
5. The system of claim 4, wherein the impedance sensor is configured to process the impedance baseline to determine fluid levels from the patient.
6. The system of claim 4, wherein the impedance sensor is configured to process the impedance baseline to determine a respiratory rate from the patient.
7. The system of claim 4, wherein the impedance sensor is configured to process the impedance plethysmogram to determine a stroke volume from the patient.
8. The system of claim 7, wherein the impedance sensor is configured to process the stroke volume to determine the cardiac output from the patient.
9. The system of claim 4, wherein the impedance sensor is configured to process the impedance plethysmogram to determine a fiducial point.
10. The system of claim 9, wherein the impedance sensor is configured to process the fiducial point to estimate a blood pressure value from the patient.
11. The system of claim 1, wherein the impedance sensor is configured to measure an ECG waveform from the patient.
12. The system of claim 11, wherein the ECG sensor is configured to process the ECG waveform to determine a value of heart rate from the patient.
13. The system of claim 11, wherein the ECG sensor is configured to process the ECG waveform to determine a value of heart rate variability from the patient.
14. The system of claim 1, wherein the ECG sensor is configured to process the ECG waveform to determine a fiducial point.
15. The system of claim 14, wherein the ECG sensor is configured to process the fiducial point to estimate a blood pressure value for the patient.
16. The system of claim 1, wherein the motion sensor is configured to process the motion signals to estimate a number of steps taken by the patient.
17. The system of claim 1, wherein the motion sensor is configured to process the motion signals to estimate a degree of work exerted by the patient.
18. The system of claim 1, wherein the motion sensor is configured to process the motion signals to estimate a duration of exercise performed by the patient.
19. The system of claim 1, wherein the motion sensor is configured to process the motion signals to determine a respiratory rate for the patient.
20. The system of claim 1, wherein the sensor is configured to collectively process the impedance and ECG signals to estimate a blood pressure value for the patient.
21. The system of claim 1, wherein the sensor is configured to collectively process the impedance and ECG signals to estimate a cardiac output value for the patient.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A computer-implemented method for recovering from continuous-data-protection blackouts, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:
identifying a continuous data protection system that includes a splitter driver configured to copy each change made to a set of data in real time;
determining that the splitter driver has been unloaded, wherein the continuous data protection system blacks out while the splitter driver is unloaded;
identifying a set of changes made to the set of data but missed by the continuous data protection system as a result of the continuous data protection system blacking out and not copying one or more changes that were made to the set of data while the continuous data protection system was blacked out;
determining that the splitter driver has been reloaded;
identifying an alternate change-tracking system that tracks changes made to the set of data;
in response to determining that the splitter driver has been reloaded, updating the continuous data protection system with the missed set of changes as tracked by the alternate change-tracking system.
2. The computer-implemented method of claim 1, wherein identifying the set of changes made to the set of data but missed by the continuous data protection system comprises determining that the continuous data protection system has stopped copying changes made to the set of data.
3. The computer-implemented method of claim 2, wherein determining that the continuous data protection system has stopped copying changes made to the set of data comprises recording a time when the continuous data protection system stopped copying changes made to the set of data.
4. The computer-implemented method of claim 2, wherein determining that the continuous data protection system has stopped copying changes made to the set of data comprises halting at least a part of the continuous data protection system.
5. The computer-implemented method of claim 4, wherein halting at least a part of the continuous data protection system comprises unloading a change tracking driver.
6. The computer-implemented method of claim 1, wherein identifying the alternate change-tracking system that tracks changes made to the set of data comprises initiating the alternate change-tracking system.
7. The computer-implemented method of claim 1, wherein the alternate change-tracking system comprises a file change log.
8. The computer-implemented method of claim 1, wherein updating the continuous data protection system with the missed set of changes as tracked by the alternate change-tracking system comprises writing the missed set of changes to a journal of the continuous data protection system.
9. The computer-implemented method of claim 1, wherein updating the continuous data protection system with the missed set of changes as tracked by the alternate change-tracking system comprises:
identifying a set of file system objects affected by the missed set of changes;
identifying a set of storage blocks used by the set of file system objects;
copying the set of storage blocks to a journal of the continuous data protection system.
10. The computer-implemented method of claim 1, further comprising updating the continuous data protection system with storage metadata that changed while the continuous data protection system missed the set of changes.
11. The computer-implemented method of claim 10, wherein the storage metadata comprises at least one of:
a volume table of contents;
a partition table;
virtualization metadata.
12. The computer-implemented method of claim 1, further comprising inserting a blackout window into a timeline of the continuous data protection system, the blackout window spanning from when the continuous data protection system stopped copying changes made to the set of data to when the continuous data protection system was updated with the missed set of changes.
13. The computer-implemented method of claim 1, wherein identifying the set of changes made to the set of data but missed by the continuous data protection system comprises syncing a file system that includes the set of data by committing each pending file system operation.
14. A system for recovering from continuous-data-protection blackouts, the system comprising:
an identification module programmed to:
identify a continuous data protection system that includes a splitter driver configured to copy each change made to a set of data in real time;
determine that the splitter driver has been unloaded, wherein the continuous data protection system blacks out while the splitter driver is unloaded;
identify a set of changes made to the set of data but missed by the continuous data protection system as a result of the continuous data protection system blacking out and not copying one or more changes that were made to the set of data while the continuous data protection system was blacked out;
determine that the splitter driver has been reloaded;
identify an alternate change-tracking system that tracks changes made to the set of data;
an update module programmed to, in response to the determination that the splitter driver has been reloaded, update the continuous data protection system with the missed set of changes as tracked by the alternate change-tracking system;
at least one processor configured to execute the identification module and the update module.
15. The system of claim 14, wherein the identification module is programmed to identify the set of changes made to the set of data but missed by the continuous data protection system by determining that the continuous data protection system has stopped copying changes made to the set of data.
16. The system of claim 15, wherein the identification module is programmed to determine that the continuous data protection system has stopped copying changes made to the set of data by recording when the continuous data protection system stopped copying changes made to the set of data.
17. The system of claim 15, wherein the identification module is programmed to determine that the continuous data protection system has stopped copying changes made to the set of data by halting at least a part of the continuous data protection system.
18. The system of claim 17, wherein the identification module is programmed to halt at least a part of the continuous data protection system by unloading a change tracking driver.
19. The system of claim 14, wherein the identification module is programmed to identify the alternate change-tracking system that tracks changes made to the set of data by initiating the alternate change-tracking system.
20. A physical computer-readable-storage medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:
identify a continuous data protection system that includes a splitter driver configured to copy each change made to a set of data in real time;
determine that the splitter driver has been unloaded, wherein the continuous data protection system blacks out while the splitter driver is unloaded;
identify a set of changes made to the set of data but missed by the continuous data protection system as a result of the continuous data protection system blacking out and not copying one or more changes that were made to the set of data while the continuous data protection system was blacked out;
determine that the splitter driver has been reloaded;
identify an alternate change-tracking system that tracks changes made to the set of data;
in response to determining that the splitter driver has been reloaded, update the continuous data protection system with the missed set of changes as tracked by the alternate change-tracking system.