US 7,321,862 B2 | ||
System and method for patient-worn monitoring of patients in geographically dispersed health care locations | ||
Brian A. Rosenfeld, Baltimore, Md. (US); and Michael Breslow, Lutherville, Md. (US) | ||
Assigned to Visicu, Inc., Baltimore, Md. (US) | ||
Filed on Nov. 07, 2005, as Appl. No. 11/268,706. | ||
Application 11/268706 is a continuation in part of application No. 10/946548, filed on Sep. 21, 2004, granted, now 7,256,708. | ||
Application 10/946548 is a continuation in part of application No. 10/654668, filed on Sep. 04, 2003. | ||
Application 10/654668 is a continuation in part of application No. 09/443072, filed on Nov. 18, 1999, granted, now 6,804,656, filed on Oct. 12, 2004. | ||
Claims priority of provisional application 60/141520, filed on Jun. 23, 1999. | ||
Prior Publication US 2006/0085227 A1, Apr. 20, 2006 | ||
This patent is subject to a terminal disclaimer. | ||
Int. Cl. G06F 19/00 (2006.01) |
U.S. Cl. 705—3 [705/2; 600/300] | 46 Claims |
1. A patient monitoring system for geographically dispersed health care locations comprising a network, a body-worn monitoring
station, a monitoring station server, a remote command center, and a rules engine, wherein,
the network comprises a first sub-network and a second sub-network;
the body-worn monitoring station comprises monitoring equipment, and wherein the body worn monitoring station comprises instructions
for:
monitoring data elements from a patient assigned to a health care location; and sending monitored data elements to a monitoring
station server via the first sub-network;
the monitoring station server comprises instructions for:
receiving the monitored data elements from the body worn monitoring station; and
relaying the monitored data elements to the remote command center via the second sub-network;
the remote command center comprises instructions for:
receiving the monitored data elements from the monitoring station server;
associating the monitored data elements with the patient assigned to the health care location;
accessing patient data elements indicative of a medical condition associated with the patient;
establishing a patient-specific rule associated with the patient; and
the rules engine comprises instructions for:
selecting data elements from the monitored data elements and the patient data elements associated with the patient;
applying the patient-specific rule to the selected data elements continuously and simultaneously;
determining in an automated fashion 24 hours per day 7 days per week from the remote command center whether the patient-specific
rule for the patient has been contravened; and
issuing an alert from the remote command center in the event the patient-specific rule for the patient has been contravened.
|