US20010051765A1 - Patient care delivery system - Google Patents
Patient care delivery system Download PDFInfo
- Publication number
- US20010051765A1 US20010051765A1 US09/893,495 US89349501A US2001051765A1 US 20010051765 A1 US20010051765 A1 US 20010051765A1 US 89349501 A US89349501 A US 89349501A US 2001051765 A1 US2001051765 A1 US 2001051765A1
- Authority
- US
- United States
- Prior art keywords
- patient
- expert
- experts
- diagnosis
- compensation amount
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
- A61B5/0015—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system
- A61B5/0022—Monitoring a patient using a global network, e.g. telephone networks, internet
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/103—Detecting, measuring or recording devices for testing the shape, pattern, colour, size or movement of the body or parts thereof, for diagnostic purposes
- A61B5/11—Measuring movement of the entire body or parts thereof, e.g. head or hand tremor, mobility of a limb
- A61B5/1112—Global tracking of patients, e.g. by using GPS
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/48—Other medical applications
- A61B5/4836—Diagnosis combined with treatment in closed-loop systems or methods
- A61B5/4839—Diagnosis combined with treatment in closed-loop systems or methods combined with drug delivery
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/30—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
- A61B5/0004—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by the type of physiological signal transmitted
- A61B5/0006—ECG or EEG signals
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
- A61B5/021—Measuring pressure in heart or blood vessels
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
- A61B5/024—Detecting, measuring or recording pulse rate or heart rate
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
- A61B5/024—Detecting, measuring or recording pulse rate or heart rate
- A61B5/02411—Detecting, measuring or recording pulse rate or heart rate of foetuses
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/145—Measuring characteristics of blood in vivo, e.g. gas concentration, pH value; Measuring characteristics of body fluids or tissues, e.g. interstitial fluid, cerebral tissue
- A61B5/14532—Measuring characteristics of blood in vivo, e.g. gas concentration, pH value; Measuring characteristics of body fluids or tissues, e.g. interstitial fluid, cerebral tissue for measuring glucose, e.g. by tissue impedance measurement
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/72—Signal processing specially adapted for physiological signals or for diagnostic purposes
- A61B5/7232—Signal processing specially adapted for physiological signals or for diagnostic purposes involving compression of the physiological signal, e.g. to extend the signal recording period
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S128/00—Surgery
- Y10S128/904—Telephone telemetry
Definitions
- This invention generally relates to patient care diagnosis delivery and, more particularly, to facilitating, in exchange for compensation, the provision of an expert diagnosis opinion of a condition based upon data gathered from a remote monitor.
- Hewlett-Packard's ECGStat software for its PalmVue handheld computer system allows emergency room clinicians to capture and transmit full 12-lead ECG data, including waveforms, computerized analysis and patient notes to cardiac specialists outside the hospital. It is a wireless system that uses paging technology to transmit data to a physician's handheld computer.
- ECG monitors it is well known to use ECG monitors in conjunction with software to analyze patterns in patients' heartbeats. Typically, monitoring technicians (or monitors) are alerted to the possibility that something is amiss by an alarm. Upon examining a readout of the vital sign in question, the monitor makes a decision about (i) whether the patient requires attention (ii) whether the patient requires a cardiologist's services and if so, (iii) which cardiologist to call. Typically, the technician selects the cardiologist from a list of available specialists. This list is substantially determined by availability, i.e., who is on call at the time. If a cardiologist is required, the technician must communicate to a cardiologist the patient's condition over voice or data lines. The technician may use the Hewlett-Packard ECGStat system described above to communicate with the cardiologist.
- the invention is a method and apparatus for analyzing data from remote monitoring equipment, such as a patient telemetry device, and determining (i) if an anomaly exists, (ii) if an anomaly does exist, what kind of action should be taken, and (iii) if a physician should be contacted, which one. Further, the system operates in parallel, in that a plurality of experts (e.g., physicians) may be contacted in response to multiple anomalous events, thus ensuring the quickest possible response time.
- a plurality of experts e.g., physicians
- the present invention further contemplates methods for obtaining opinions from a plurality of experts and aggregating such diagnoses into an aggregate diagnosis.
- the opinions may be rendered by experts working independently or in consultation with one another.
- the aggregate diagnosis is obtained in response to detection of an anomaly in data from remote monitoring equipment of a patient.
- the invention further contemplates various compensation schemes for providing payment to experts who provide a diagnosis.
- a method for procuring a diagnosis comprises the steps of: receiving representative data that represents at least one physiological parameter of a patient; determining whether the received data is indicative of a physiological anomaly; selecting at least one expert to provide an expert opinion regarding the indicated anomaly; communicating, to the at least one selected expert, the physiological representative data, including the determined anomaly; and receiving, from at least one selected expert, a diagnosis of the anomaly.
- a diagnostic procurement system comprises: a monitor, for monitoring at least one parameter associated with an entity and communicating data representing the at least one entity parameter; and a controller, responsive to the data representing the at least one entity parameter, for determining whether anomalous entity operational parameters are present and, in the case of anomalous entity operational parameters being present, procuring a diagnosis from at least one of a predetermined number of experts.
- FIG. 1 depicts a high level block diagram of a patient care diagnosis delivery system
- FIG. 2 depicts a high level block diagram of a central server 200 suitable for use in the patient care diagnosis delivery system of FIG. 1;
- FIG. 3 depicts an exemplary reaction database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 4 depicts an exemplary physician database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 5A depicts an exemplary physician criteria database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 5B depicts an exemplary patient criteria database in tabular form suitable for use in the central server 200 of FIGS. 1 and 2;
- FIG. 6 depicts an exemplary patient database in tabular form suitable for use in the central server 200 of FIGS. 1 and 2;
- FIG. 7 depicts an exemplary event database 700 in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIGS. 8A and 8B depict a flow diagram of a patient care diagnosis delivery method suitable for use in the patient care diagnosis delivery system of FIG. 1;
- FIGS. 9A and 9B depict a flow diagram of an expert selection method suitable for use in the patient delivery method of FIGS. 8A and 8B;
- FIG. 10 depicts a flow diagram of an offer processing method suitable for use in the expert selection method of FIGS. 9A and 9B;
- FIG. 11 depicts a flow diagram of a patient care diagnosis delivery method 1100 suitable for use in the patient care diagnosis delivery system 100 of FIG. 1.
- FIG. 12 depicts a flow diagram of a patient care diagnosis delivery method 1200 suitable for use in the patient care diagnosis delivery system 100 of FIG. 1.
- FIG. 13 depicts an exemplary compensation agreement database in tabular form suitable for use in the central server 200 of FIGS. 1 and 2
- the present invention comprises a system which carries out continuous and passive monitoring of a patient, wherein the patient's physiological parameters are monitored by a system remote from the patient and which system detects and automatically processes any recognized anomalies in such parameters, such that a potential problem may be caught and analyzed before the patient even realizes that there is anything wrong.
- the system of the present invention may detect lack of movement from a fetus or a slow-down in the heartbeat of a fetus and contact an obstetrician to determine a course of action.
- the obstetrician may in turn study the data and determine that such a slow-down in heartbeat is normal under the circumstances and advise the system that nothing further needs to be done.
- the patient being monitored can rest easier and go on about her daily activities, secure in the knowledge that her health is being continuously monitored and qualified experts are being contacted as needed.
- the patient does not need to worry about contacting her own physician or finding an available physician.
- the system has access to a multitude of qualified experts, with enormous resources to find the right expert regardless of time of day or night.
- the system may handle the monitoring of many patients and parameters simultaneously and be capable of responding to various anomalies in different patients simultaneously such that the patient's diagnosis is not delayed unnecessarily. This is because, in at least one embodiment, the system is capable of analyzing and processing the initial physiological data automatically in order to determine what type of expert to contact, rather than being dependent on a human being to monitor physiological data and attempt to contact local physicians manually
- the system and method provide (a) an initial screening and decision capability based upon the received operating data sufficient to determine which type of expert is needed; (b) an identification and communication of at least a portion of the operating data to one or more appropriate experts; (c) a transactional capability defining a level of compensation to be provided to the expert in exchange for the rendering of an expert diagnosis regarding the anomaly; and (d) an adaptation of an existing communications infrastructure to the procurement of the expert opinion(s).
- the invention comprises, in general terms, a centralized system procuring expert diagnosis or diagnostic opinion(s) in response to remotely monitored data indicative of an event requiring such an opinion.
- An anomaly comprises a dysfunction or precursor to a dysfunction within a monitored entity, such as a patient in a medical monitoring environment.
- An “expert” is an entity that provides a diagnosis relating to an anomaly.
- An expert is one deemed by the patient and, optionally, the system, as having expertise in treating the patient's condition. In the case of standard medical specialties, the patient and system will be in agreement as to the definition of an expert. If the patient believes in practitioners of non-standard or alternative therapies, then the system and patient may disagree.
- a “diagnosis” or diagnostic opinion comprises an identification of an anomaly, a recommended treatment for a patient or any expert opinion tending to remediate or ameliorate an anomalous condition.
- Communication comprises any means of transferring data to or from a communicating party, such as a patient telemetry device, a central server, a physician terminal device, a computing device or telephonic device and the like.
- a communication may utilize encryption/decryption protocols.
- lert information comprises information, including local diagnostic information, real time physiological data and other information intended to be used in the rendering of a diagnosis or a determination of the type of expert needed to render such a diagnosis.
- a data profile is a data template against which raw or processed information is compared to produce a level of affinity between the information and the data profile.
- a high level of affinity indicates that the information may conform to an anomalous condition associated with the data profile.
- Profiles may be individualized and adapted to patients. For example, a baseline profile may be adapted over time in response to a patient's improving or degrading condition (e.g., diminished heart valve integrity will lead to changes in ECG data as the heart adapts by pumping harder and/or differently).
- FIG. 1 depicts a high level block diagram of a patient care diagnosis delivery system. Specifically, FIG. 1 depicts a high level block diagram of a patient care diagnosis delivery system 100 comprising a plurality of physician terminal devices 110 - 1 through 110 -N, a central server 200 and a plurality of patient telemetry devices 120 - 1 through 120 -N.
- Each of the plurality of patient telemetry devices 120 - 1 through 120 -N is capable of monitoring at least one physiological parameter of a patient and communicating data representative of the monitored parameter to the central server 200 via respective data paths P 1 through PN.
- the patient telemetry device may comprise a known device capable of monitoring patient data, transmitting that data to the central server and, optionally, receiving data from the central server 200 .
- the central server 200 examines the communicated data to determine if the at least one physiological parameter is within appropriate or “normal” parameter boundaries. If the data is not within the appropriate boundary, the central server 200 determines if an event or medical anomaly (e.g., cardiac arrest or other condition) may be occurring. If such a determination is made, then the central server 200 communicates an offer to one or more of the physician terminal devices via respective data paths E 1 through EN.
- an event or medical anomaly e.g., cardiac arrest or other condition
- Each physician terminal device 110 i.e., physician terminals 110 - 1 through 110 -N
- physician terminals 110 - 1 through 110 -N is associated with at least one respective expert, such as physician(s), nurse(s), and other experts.
- a physician receiving an offer accepts that offer by communicating an acceptance message to the central server 200 via the physician terminal device 110 or another means (e.g., telephone, computer network and the like).
- the central server decides which one (or more than one) of the accepted offers will be confirmed by sending a confirmation signal to the physician via, e.g., the respective physician terminal device(s).
- the physician terminal device may comprise a known device capable of receiving information from the central server and, optionally, transmitting information to the central server 200 . For example, a pager, a personal digital assistant (PDA) or a cellular telephone may be utilized for this purpose.
- PDA personal digital assistant
- An exemplary embodiment of a patient telemetry device 120 - 1 comprises an input/output (I/O) circuit 125 , support circuitry 123 , a processor 124 , a memory 126 and a data link 127 .
- the processor 124 cooperates with conventional support circuitry 123 such as power supplies, clock circuits, cache memory and the like as well as circuits that assist in executing the various software routines within the patient telemetry device 120 - 1 .
- Input/output circuit 125 forms an interface between the patient telemetry device 120 - 1 and sources of patient physiological data.
- the input/output circuit 125 may comprise sensors, transducers and other analog to digital conversion circuitry adapted to measure physiological parameters associated with a patient, such as heart rate, blood pressure, temperature, perspiration level, respiratory activity, body electrical activity, brain activity and the like.
- the physiological information is received and/or processed by the input/output circuitry to produce physiological parameter representative data in a form usable by processor 124 .
- the processor 124 communicates the physiological parameter representative data to the central server 200 via a data link 127 .
- Data link 127 comprises a wireless or a non-wireless data link (e.g., a telephone dialer, a cellular telephone link, or a computer link) or other communications link driver suitable for providing patient data to the central server 200 via a respective data path (e.g., data path P 1 ).
- the patient telemetry device is optionally responsive to a patient control signal.
- the patient control signal comprises a signal that a patient may use to communicate specific information or a request to the central server 200 .
- the patient may manually communicate this condition to the central server 200 such that appropriate action (e.g., summon an ambulance) is taken.
- the patient control signal is produced by an optional input device 145 , illustratively, a key pad.
- the patient control signal is used to communicate a message to the central server 200 comprising, e.g., a standby mode message, an impending exertion message, an equipment failure message, a medical emergency message, a non-medical emergency message, a specific physiological dysfunction message and a test message.
- the system may choose to ignore any apparent anomalies.
- An exemplary embodiment of a physician terminal device 110 - 1 comprises an input/output (I/O) circuit 115 , support circuitry 113 , a processor 114 , memory 116 , a display device 111 and a data entry device 112 .
- the processor 114 cooperates with conventional support circuitry 113 such as power supplies, clock circuits, cache memory and the like as well as circuits that assist in executing various software routines.
- the physician terminal device 110 - 1 also contains input/output circuitry 115 that forms an interface between the physician terminal device 110 and the central server 200 .
- the display device 111 comprises a liquid crystal display (LCD) or other display means, while the data entry device 112 comprises a keyboard or other data entry means.
- the memory 116 includes a standard control program such as a PDA or cellular telephone control program that enables a physician or expert interacting with the physician terminal device to receive information from the central server 200 and, optionally, transmit information back to the central server 200 .
- the physiological information received from the patient is merely converted into a digital information stream, either compressed or uncompressed, and transmitted directly to the central server 200 . That is, the patient telemetry device 120 does not perform any analysis of the physiological data.
- the data is merely passed to the central server 200 in either a compressed or uncompressed data format as appropriate to, e.g., the format of data link P 1 .
- Compressed data transfer may be effected using various compression methods, such as the frequency domain transform functions utilized in known communications systems.
- the processor 124 performs an analysis of the received physiological information to determine if, for example, monitored parameters of the patient are within appropriate boundaries.
- the processor 124 may be programmed (via a control program within the memory 126 ) to issue an alert to the central server 200 in the event of a patient heart rate exceeding an upper threshold level or dropping below a lower threshold level.
- Multiple parameter alarms may be programmed such that particular combinations of physiological parameter levels trigger specific alerts indicative of specific conditions.
- the patient telemetry device 120 - 1 and central server 200 communicate bi-directionally.
- parameter threshold levels are optionally updated via the data link (P 1 -PN) or other means (e.g., via an internet or telephone connection) such that patient monitoring may be calibrated to the changing needs of a patient. For example, if a patient is about to exercise, it is quite likely that the measured heart rate will increase. Therefore, the patient may communicate this fact to the central server 200 via a patient control signal produced using the keypad 145 .
- Bi-directional communication may be effected via the internet 170 or other communications medium.
- the patient telemetry device 120 - 1 is associated with a drug dispensing device 130 .
- the central server 200 may be used to control the dispensing of drugs to the patient via the drug dispensing device 130 .
- the central server 200 may cause the drug dispensing device 130 to dispense medication tending to reduce or mitigate any harm to the patient due to the event.
- the decision to dispense medication may be made locally.
- medication dispensing may be placed under the control of the patient (e.g., pain medication up to a predefined dosage rate).
- the local control of medication dispensing is communicated to the central server 200 where the patient's medical records are responsively updated.
- the patient telemetry device 120 is associated with a global positioning system (GPS) locator 135 .
- GPS global positioning system
- the GPS locator 135 comprises known GPS receiver circuitry suitable for determining the geographic position of the patient (assuming the patient is near the GPS locator).
- the geographic position of the patient is transmitted to the central server 200 for use in, e.g., directing an ambulance to the patient, performing geographical-based analysis of aggregated patient data or other functions.
- the patient telemetry device 120 is associated with an automatic external defibrillator (AED) 140 .
- AED automatic external defibrillator
- a central server or decision may indicate that defibrillation is appropriate.
- the central server or patient telemetry device causes the automatic external defibrillator to enter an active mode of operation.
- Present automatic external defibrillators include monitoring capabilities such that they do not administer an electric shock to a patient unless such an electric shock is warranted. That is, present automatic external defibrillators perform monitoring operations to confirm the need for a defibrillation. Such functionality may optionally be incorporated into the patient telemetry device 120 .
- a security system 150 associated with the patient is coupled to the patient telemetry device 120 such that in the event of a medical emergency, the central server 200 is contacted and, additionally, a security system server (not shown) is also contacted.
- the data link 127 may communicate to the central server 200 via the security system 150 rather than the data link 127 (e.g., telephone lines, cellular telephone, two-way paging and the like).
- a medical records clearing-house 180 is used to store patient medical records.
- the patient medical records are communicated to a confirmed expert (i.e., a physician accepting an offer that has been subsequently confirmed) via the internet 170 or via the central server 200 .
- FIG. 2 depicts a high level block diagram of a central server 200 suitable for use in the patient care diagnosis delivery system of FIG. 1.
- the central server 200 of FIG. 2 comprises a communications port 210 , a processor 220 , a memory 230 , support circuitry 240 and a storage device 250 .
- the communication port 210 forms an interface between the central server 200 and the physician terminal devices 110 - 1 through 110 -N, the patient telemetry devices 120 - 1 through 120 -N and, optionally, the internet 170 and the medical records clearinghouse 180 .
- the processor 220 cooperates with support circuitry 240 and memory 230 to run various programs 1200 and use various databases 300 - 700 stored in storage device 250 .
- the storage device 250 is used to store a program 1200 that will direct the processor 220 to perform the methods of the present invention and to store various databases 300 - 700 used to implement the methods of the present invention.
- the storage device 250 is used to store a reaction database 300 , a physician database 400 , a criteria database 500 , a patient database 600 ,an event database 700 , and a compensation agreement database 800 .
- the reaction database 300 will be discussed in more detail below with respect to FIG. 3, the physician database 400 will be discussed with more detail below with respect to FIG. 4, the criteria database 500 will be discussed in more detail below with respect to FIGS. 5A and 5B, the patient database 600 will be discussed in more detail below with respect to FIG.
- the event database 700 will be discussed in more detail below with respect to FIG. 7, and the compensation agreement database will be discussed in more detail below with respect to FIG. 13.
- the programs and databases may be stored locally in the central server 200 or in a remote location, such as the optional medical records clearing house 180 depicted in FIG. 1.
- the central server 200 receives a continuous signal from each patient; the received signal is analyzed to determine if any predefined patterns or data aberrations exist; any such patterns or data aberrations are further analyzed to determine whether the pattern or data aberration is pathological; if pathological, then the central server 200 searches the physician database for an expert, such as a physician, appropriate to the treatment of patients exhibiting such pattern or data aberration and, if appropriate, an ambulance is dispatched to bring the patient to a hospital; the expert is then paged and offered compensation to render an expert diagnosis on the patient's condition; in the case of an expert accepting the offer, the central server 200 confirms the acceptance and transmits to the expert a copy of at least a portion of the patient's medical history and a description of the current pattern or data aberration so that the expert diagnosis may be rendered.
- an expert such as a physician, appropriate to the treatment of patients exhibiting such pattern or data aberration and, if appropriate, an ambulance is dispatched to bring the patient to a hospital
- the expert is then paged and
- FIG. 3 depicts table 305 , exemplary of reaction database 300 , suitable for use in the central server of FIGS. 1 and 2.
- the table 305 of FIG. 3 comprises a plurality of records R 31 through R 36 , each record being associated with a respective alert field 310 and a respective system reaction field 320 .
- the alert field 310 of a record indicates a specific alert condition.
- the system reaction field 320 of the record indicates an appropriate system reaction to the corresponding alert field 310 of the record.
- the alert fields 310 of the table 305 of FIG. 3 assume that the patient telemetry devices 120 of the system 100 of FIG. 1 provide alert information to the central server 200 . That is, the patient telemetry devices 120 - 1 through 120 -N perform a local data analysis (or receive direct patient input) and responsively issue an alert code to the central server.
- the table 305 provides, for each predefined alert, an appropriate system response to the alert. Additionally, the table 305 of FIG. 3 is shown with only six records (R 31 through R 36 ). However, it will be appreciated by those skilled in the art that the reaction database 300 may comprise an unlimited number of records.
- Alert field 310 of records R 31 through R 36 is depicted as indicating alert conditions as follows: ventricular fibrillation R 31 ; loss of consciousness R 32 ; aberrant blood glucose levels R 33 ; fetal heart monitor alarm R 34 ; tachycardia R 35 ; and acutely high blood pressure R 36 .
- System reaction field 320 of records R 31 through R 36 is depicted as indicating the following system responses to corresponding alert conditions as follows: summon an ambulance and offer the case to one or more cardiologists R 31 ; summon an ambulance and offer the case to an emergency room physician R 32 ; instruct the patient to take insulin and, if the blood glucose levels do not return to normal after a predefined period of time (e.g., 15 minutes,) offer the case to one or more nurses R 33 ; alert the mother, instruct her to go to the hospital and offer the case to one or more obstetricians R 34 ; offer the case to one or more cardiologists and query the patient as to the patient's present activity level (e.g., was patient climbing stairs, playing basketball, watching television and the like) R 35 ; and offer the case to one or more internists and query the patient as to a present activity level R 36 .
- a predefined period of time e.g. 15 minutes,
- FIG. 4 depicts table 405 , exemplary of physician database 400 suitable for use in the central server of FIGS. 1 and 2.
- the table 405 of FIG. 4 comprises a plurality of records R 41 through R 49 , each record being associated with a respective physician's name field 410 , a physician identifier field 420 , a physician criteria codes field 430 , a specialty field 440 , a previous case identifiers field 450 , an availability field 460 and a contact information field 470 .
- the availability field 460 may provide conditional information, i.e., an unavailable physician will always be available if a compensation level exceeds a threshold amount such as illustrated in record R 48 .
- the physician's name field 410 indicates the name of a particular physician; the physician identifier field 420 indicates an insurance company, hospital or other identification number or code that uniquely identifies the physician; the physician criterion codes field 430 indicates physician criterion information (e.g., fee structure, board certification and the like); the specialty field 440 indicates the physician's specialty (e.g., Cardiology, Surgery and the like); the previous case identifiers field 450 indicates the case identifiers of previous cases handled by the physician; the availability field 460 indicates whether the physician is presently available to handle a case; and the contact information field 470 indicates the preferred method of contacting the physician, e.g., voice, pager, email and the like. Physicians indicate their availability by, for example, logging onto a web site or otherwise communicating by alternate means with the system to inform the system when they become available and when they cease to be available.
- physician identifier field 420 indicates an insurance company, hospital or other identification number or code that uniquely identifies the physician
- Record R 41 of table 405 indicates that a physician named John Doe has a corresponding identifier “123456”, criterion codes “UH”, “BS”, “M33” and “MP”, a specialty of “Emergency Medicine”, previous case identifiers of “C987654”, “C876543” and “C765432”, an availability indication of “yes” and contact information indicative of a pager number of 555-1234.
- Record R 42 indicates that a physician named Bob Smith has a corresponding identifier “234567”, criterion codes “UH”, “M33” and “MP”, a specialty of Cardiology, previous case identifiers of “C654321”, “C543210” and “C432109”, an availability indication of “no” and contact information indicative of a voice number of 555-2345.
- Records R 43 through R 49 contain similar data regarding other physicians.
- the physician criterion codes field 430 will be discussed in more detail below with respect to FIG. 5A.
- Record R 48 of table 405 indicates that a physician named Alex Schwartz has a corresponding identifier “890123”, criterion codes “UH”, “BS”, “BC” and “MP”, a specialty of “Endocrinology”, previous case identifiers of “C999876” and “C888765”, an availability indication of “only above $150” (i.e., only available if offer is at least $150) and contact information indicative of an email address of good_doc@hospital.com.
- the previous case identifier field 450 will be discussed in more detail below with respect to FIG. 7.
- FIG. 5A depicts table 500 A, exemplary of one embodiment of criteria database 500 suitable for use in the central server of FIGS. 1 and 2.
- the table 500 A of FIG. 5A comprises a plurality of records RA 51 through RA 58 , each record being associated with a respective physician criterion field 510 and a physician criterion code field 520 .
- the physician criterion field 510 indicates a particular objective or subjective criterion that may be applied to a physician.
- Subjective physician criteria comprise subjective preferences of the physician (e.g., preferred patients, insurance plans, hospitals and the like).
- the physician criterion code field 520 contains the corresponding code, or abbreviation, of the objective or subjective criterion contained within the respective physician criterion field 510 . If a criterion is applicable to a given physician, the code for that criterion will appear in the physician criterion codes field 430 of a record associated with that physician in the physician database 400 .
- a physician criterion of universal health approved physician criterion is associated with code UH (record RA 51 ); Blue Shield approved physician criterion is associated with code BS (record RA 52 ); board certified physician criterion is associated with code BC (record RA 53 ); fee structure in upper 33 rd percentile criterion is associated with code U33 (record RA 54 ); fee structure in middle 33 rd percentile criterion is associated with code M33 (record RA 55 ); fee structure in lower 33 rd percentile criterion is associated with code L33 (record RA 56 ); male physician criterion is associated with code MP (record RA 57 ) and female physician criterion is associated with code FP (record RA 58 ).
- FIG. 5B depicts a table 500 B, exemplary of another embodiment of criteria database 500 suitable for use in the central server 200 of FIGS. 1 and 2.
- table 500 B of FIG. 5B comprises a plurality of records RB 51 through RB 514 , each record being associated with a respective patient criterion field 530 and a patient criterion code field 540 .
- the patient criterion field 530 indicates a particular objective or subjective criterion applied to a physician treating a patient that is required or preferred by the patient or the patient's insurance provider.
- Subjective criteria comprises subjective preferences of the patient (e.g., preferred physicians, preferred hospitals and the like).
- the patient criterion code field 540 of a record contains the code, or abbreviation, of the objective criterion contained within the respective patient criterion field 530 .
- a physician having a criterion code contrary to a required patient criterion code is deemed to be undesirable to the patient.
- a physician having all criterion codes matching those of the patient is deemed to be most desirable to the patient. Physicians having some criterion codes matching the patient preferred criterion codes may be ranked in order of preference according to the amount of correlation between the patient's and physicians' criterion codes.
- the contents of the patient criterion field 530 and the patient criterion code field 540 of records RB 51 through RB 514 are as follows: require universal health approved physician criterion is associated with code R-UH (record RB 51 ); prefer universal health approved physician criterion is associated with code P-UH (record RB 52 ); require Blue Shield approved physician criterion is associated with code R-BS (record RB 53 ); prefer Blue Shield approved physician criterion is associated with code P-BS (record RB 54 ); prefer fee structure in upper 33 rd percentile criterion is associated with code P-U33 (record RB 55 ); prefer fee structure in middle 33 rd percentile criterion is associated with code P-N33 (record RB 56 ); prefer fee structure and lower 33 rd percentile criterion is associated with code P-L33 (record RB 57 ); require board certification criterion is associated with code R-BC (record RB RB ).
- FIG. 6 depicts a tabular representation 605 of an exemplary patient database 600 suitable for use in the central server 200 of FIGS. 1 and 2.
- the table 605 of FIG. 6 comprises a plurality of records R 61 through R 68 , each record being associated with a respective patient's name field 610 , patient identifier field 620 , patient criterion code field 630 , a “currently being treated for” field 640 and a past alerts field 650 .
- the patient's name field 610 indicates the name of a particular patient; the patient identifier field 620 indicates an insurance company, hospital or other identification number or code that uniquely identifies the patient; the patient criterion codes field 630 indicates patient criterion information relating to preferred objective or subjective characteristics of a treating physician (e.g., fee structure, board certification and the like); the currently being treated for field 640 indicates the current medical conditions (if any) that the patient is currently being treated for and the past alerts field 650 indicates the medical conditions (or general health) that triggered previous alerts or other events.
- a treating physician e.g., fee structure, board certification and the like
- the currently being treated for field 640 indicates the current medical conditions (if any) that the patient is currently being treated for
- the past alerts field 650 indicates the medical conditions (or general health) that triggered previous alerts or other events.
- a number of exemplary patient criteria appear in this database.
- the codes for patient criteria correspond to those for physician criteria, except that patient codes have either an “R” or “P” prefix.
- the code for a board-certified physician is BC; the patient codes for board-certified physicians are R-BC and P-BC.
- Patient criterion codes with “R” prefixes indicate that the patient requires the criterion corresponding to this code.
- Patient criterion codes with “P” prefixes indicate that the patient prefers but does not require this criterion.
- Entries in the patient criterion codes field 630 may be determined not only by the patient, but, optionally, by the patient's family physician, insurance company or other entity.
- the currently being treated for field 640 contains brief information about the patient's current medical conditions.
- a “general health” entry in this field indicates that the patient is not currently being treated for anything in particular, but is instead being monitored just in case any problems develop.
- a patient's medical records are sent to a physician by providing the physician with a hyperlink or data path, such that the physician can access the files directly from a computer terminal connected to the internet or other computer network.
- Record R 66 of table 605 indicates that a patient Matt Smith is associated with an identifier number “678901”, criteria codes P-MP, P-U33 and P-BC, is currently being treated for “general health” (i.e., no particularized ailment) and lost consciousness during a past alert on Jan. 1, 1998.
- Record R 67 of table 605 indicates that a patient Teun Van Vliet is associated with an identifier “789012”, criteria codes R-UH and P-L33, is currently being treated for “Arteriosclerosis” and has never been associated with an alert.
- Record R 68 of table 605 indicates that a patient Ana Ng is associated with an identifier “890123”, criteria codes R-BS, P-BC and R-FP, is currently being treated for “Possible Pregnancy Complications” and has never been associated with an alert. Records R 61 through R 65 contain respective data relating to other patients.
- FIG. 7 depicts a table 705 , exemplary of event database 700 , suitable for use in the central server of FIGS. 1 and 2.
- the table 705 of FIG. 7 comprises a plurality of records R 71 through R 74 , each record being associated with a respective date field 710 , case identifier field 720 , patient identifier field 730 , physician identifier field 740 , event description field 750 , outcome field 760 , offers made field 770 and offers accepted field 780 .
- the offers made field 770 and offers accepted field 780 include respective physician identifiers and compensation value offered sub-fields.
- the date field 710 indicates the date of a particular event.
- the case identifier field 720 identifies, by a unique case identifier, the particular event.
- the patient identifier field 730 and physician identifier field 740 identify, respectively, the patient and physician involved in the event.
- the event description field 750 includes a description of the event.
- the outcome field 760 includes information defining the outcome of the event (e.g., the patient was admitted to a hospital, treated in a particular manner, administered a certain drug and the like).
- the offers made field 770 include information identifying each physician to whom an offer of compensation in exchange for diagnostic services was made, and the amount of money offered for such services.
- the offers accepted field 780 includes information indicating which physician or physicians accepted the offer and at what compensation value they accepted the offer.
- a “past alerts” field contains a record of previous alerts and is used to ascertain whether certain patients (or devices) are prone to false alarm events.
- the offers made field 770 and offers accepted field 780 are optionally used to improve the system accuracy in predicting physician demand and prices. For example, the system may determine that physician “596143”, an internist, regularly accepts offers $50 below the median offer for internists. In this scenario, offers to this physician may be reduced. By graphing acceptance rate against offer values, time of day and other factors, the system continually absorbs information relating to the contracting behavior of physicians, thereby refining estimates of demand and appropriate prices.
- Record R 71 of table 705 indicates that on Jan. 1, 1998 a case “678901A” involving a patient “678901” and a physician “123456” involved a loss of consciousness.
- a first physician “123456” was offered $180
- a second physician “789012” was offered $200
- a third physician “406961” was offered $220 to accept the case.
- the first physician “123456” and the second physician “789012” accepted the case at the offered amount. The event resulted in an admission to a hospital for a narcotics overdose.
- Record R 72 of Table 705 indicates that on Jan. 11, 1998 a case “505995A” involving patient “505995” and physician “ 567890 ” involved an event of acute high blood pressure and had an outcome of the patient being queried and found him to be exercising. A physician identified as “234567” was offered $375, a second physician identified as “567890” was offered $375 and a third physician identified as “961642” was offered $385 to take the case. The first and third physicians accepted the offers at the offer price.
- FIGS. 8A and 8B depict a flow diagram of a patient care diagnosis delivery method suitable for use in the patient care diagnosis delivery system of FIG. 1.
- the patient care diagnosis delivery method 800 of FIGS. 8A and 8B is suitable for use within the central server 200 of the patient care diagnosis delivery system 100 of FIG. 1 and FIG. 2.
- the method 800 is initiated at step 802 .
- a telemetry signal is received from a patient.
- the telemetry signal may comprise compressed or uncompressed physiological data without local analysis, compressed or uncompressed physiological data with a local analysis (i.e., including an alarm code), a control signal produced by the patient and, optionally, other data.
- the data is analyzed to determine if patterns within the data are indicative of a present or pending (i.e., precursor indications of dysfunction) physiological dysfunction.
- This analysis may be conducted using one or more of a number of known data analysis techniques. In the exemplary embodiment, the analysis is conducted by comparing portions of the data to data profiles that have been determined to be indicative of such present or precursor physiological dysfunction.
- the received alarm code is compared to the alert field 310 of the records within the reaction database 300 . A favorable comparison to a record yields, from the system reaction field 320 of that record, the appropriate response to the received alarm code.
- the data profiles may be periodically updated or altered.
- the step of comparing the compressed data may be performed within the compressed data domain (i.e., frequency domain) by performing the following steps: transforming, using a frequency domain transform function, the data representative of the physiological parameter; and correlating, against each of a plurality of frequency domain profiles, the transformed data representative of the physiological parameter, where each of the frequency domain profiles is associated with at least one pathological anomaly.
- a control signal produced by the patient is also reacted to in a predefined manner based upon the signal.
- a control signal indicative of pending patient exercise indicates to the central server 200 that a subsequent increase in blood pressure is to be expected, though the system will still react appropriately to data indicative of cardiac arrest.
- a query is made as to whether the determination at step 806 indicates that the received telemetry signal should be ignored. If the query at step 808 is answered affirmatively (e.g., elevated blood pressure during exercise), then the method proceeds to step 809 where, optionally, an entry in an error log (not shown) is made and the method proceeds to step 804 where the next telemetry signal is received. If the query at step 808 is answered negatively, then the method 800 proceeds to step 812 . Optionally, if the query at step 808 is answered negatively, then the method 800 proceeds to step 810 , where an ambulance is dispatched to the patient's location, if needed. The patient's location may be determined with respect to a known location or, in the case of a patient telemetry device 120 associated with a GPS locator 135 , GPS data within the received signal will provide location information.
- one or more experts are selected to provide diagnostic services.
- the expert(s) selected to provide such services are selected based upon the physician criterion 500 A of FIG. 5A and patient criterion 500 B of FIG. 5B, as will be discussed in more detail below with respect to FIGS. 9A and 9B.
- Patient preference ranking is based upon a patient criterion within patient criterion database 500 B.
- Physician preference ranking is based upon the physician criterion database 500 A.
- Insurance company preference ranking is based upon insurance company information within either of the patient criterion database 500 B or physician criterion database 500 A or other database.
- insurance companies may have negotiated or predefined contractual arrangements with individual physicians, physician groups and/or hospitals or hospital systems. In the case of a preferred hospital system or other medical facility, an insurance company may have preferred providers within that facility and these providers may or may not be reflected in the patient preference rankings.
- the specialty of an expert selected to provide diagnostic information may be dependent upon, e.g., the received telemetry signal from the patient and/or the patient's medical data or history. In the case of an emergency situation or emergent event, it may be necessary to immediately secure some expert opinion, regardless of physician specialty or other preferential ranking. These criteria or other criteria may be combined to produce a combined ranking that may be weighted in a manner tending to favor insurance company preferences, patient preferences, physician preferences and other factors as deemed appropriate.
- At step 814 at least a portion of the patient's data is provided to the selected expert or experts.
- the patient data may comprise, e.g., the received telemetry signal, the patient's medical history and any other data appropriate or necessary to the selected experts in rendering their diagnosis.
- step 816 the diagnoses from the expert or experts is/are received.
- the method 800 then proceeds to optional step 818 , where an aggregated diagnosis is formed using a plurality of diagnoses rendered by a respective plurality of experts.
- the aggregated diagnosis forms a “most likely” diagnosis that is used to determine an appropriate course of treatment for the patient in one embodiment of the present invention.
- Forming an aggregate diagnosis may, in one embodiment, comprise selecting the diagnosis that the majority of the experts agree on. For example, if 3 out of 5 experts recommend the patient proceed to the emergency room immediately for certain treatment while the other two experts recommend 24 hours of bedrest before a trip to the emergency room is determined to be necessary, the system may select the diagnosis of the majority and instruct the patient to immediately proceed to the emergency room or summon an ambulance to the patient's location. In such an embodiment the patient may only be informed of the majority opinion selected by the system or may be provided with the two alternate diagnoses and asked to select which diagnosis he wants to proceed according to. Alternatively, at the time of the event the patient may be informed of the majority diagnosis but may at a subsequent time be informed of any alternate diagnosis that was not selected.
- the experts involved in a particular case may render independent diagnoses independently of one another or may be allowed (or required) to confer with one another in rendering the aggregate diagnosis.
- the experts may be able to communicate through the internet 170 of system 100 in order to confer or share opinions in rendering the aggregate diagnosis.
- the experts may or may not be aware that their diagnosis is part of an aggregate diagnosis.
- An aggregate diagnosis embodiment may help instill more confidence in the patient and may shield any one individual expert from sole liability for rendering a remote diagnosis.
- An aggregate diagnosis may also introduce quality assurance into the system of the present invention. Another form of quality assurance may be to have another expert review or approve a diagnosis before it is acted upon by the system. Such review or approval may be performed (i) in every case, (ii) in random or selected cases, and/or (iii) for cases involving experts who are new to the system or against complaints or grievances have been lodged.
- step 819 the diagnosis is communicated to the patient
- step 820 the expert or experts providing the diagnosis is compensated.
- the expert compensation may be based upon one of, per step 822 , a flat rate, an hourly rate, and a per event rate.
- the compensation may be based upon the time of day (e.g., higher compensation between 10:00 PM and 8:00 AM) or upon physician availability.
- the compensation may be adjusted in the case of a complex event or an especially favorable outcome.
- a complex event comprises, e.g., an event implicating several specialties or sub-specialties or otherwise causing the expert being so compensated to devote a significantly higher level of time and/or effort to a particular event.
- a favorable outcome comprises an especially efficient outcome (either monetarily or physiologically) or other superb outcome based upon, e.g., an especially high level of skill applied to an event by an expert being compensated.
- an expert may incur a “lost opportunity” cost by handling the case (i.e., failing to gain a greater compensation for another activity so that an emergency event is properly handled). In such cases an additional compensation may be provided.
- Compensation may be determined by a rules-based method where, for example, the rules for determining a compensation to offer or an adjustment to previously offered or accepted compensation is determined by applying predetermined rules.
- rules may be programmed into the software running on the system of the present invention or stored in a database utilized by the system. For example, compensation may start from a base amount and may be adjusted from this amount based on the circumstances of a case. Circumstances that may be taken into consideration may include, for example, (i) a previously established rate between the expert and the system, (ii) certain qualifications or criteria associated with the expert, (iii) the severity or urgency of the patient's potential condition, and (iv) how many other experts are available to render a diagnosis.
- the adjustment of the base amount may be an upward or downward adjustment in such an embodiment.
- an amount of compensation may be determined, for example, based on a formula that takes certain variables (e.g. qualifications of expert, expert's history of accepting offers) into account when calculating a compensation amount to offer or an adjustment to a compensation amount.
- step 824 the patient database 600 , physician database 400 , and event database 700 is updated.
- the method 800 then proceeds to step 804 to await the next telemetry signal from a patient.
- FIGS. 9A and 9B depict a flow diagram of an expert selection method suitable for use in the patient care delivery method of FIGS. 8A and 8B.
- the expert selection method 900 of FIGS. 9A and 9B is suitable for use in implementing, e.g., step 812 of the patient care delivery method 800 of FIGS. 8A and 8B.
- the expert selection method 900 is initiated at step 902 and proceeds to step 904 .
- patient data and patient criteria codes for the patient transmitting the telemetry signal received at step 804 are retrieved from, respectively, patient database 600 and patient criteria database 500 B.
- a query is made as to whether the patient requires that a first available physician be contacted (a code R-FA in the patient criteria code field 630 of the patient's record in the patient database 600 ).
- Certain alarm codes may also indicate to the system that a first available physician is to be contacted.
- a code R-FA indicates that a patient is either medically compromised to such an extent that immediate intervention or at least a diagnosis from a physician is required. Therefore, in view of the immediate need for such a diagnosis from an expert, it is imprudent to perform any sorting or preferential arranging of potential experts. Rather, it is most prudent to simply offer to all appropriate and available physicians the “job” of rendering a diagnosis for this event. If the query at step 908 is answered affirmatively, then the method 900 proceeds to step 909 . If the query at step 908 is answered negatively, then the method 900 proceeds to step 910 .
- step 909 an offer is sent to all appropriate and available physicians as determined during step 906 . That is, each physician or expert having the appropriate expertise to render a diagnosis for the present event is offered the chance to render such a diagnosis in exchange for compensation.
- the method 900 then proceeds to step 924 where it is exited (e.g., the method 800 resumes control at step 814 ).
- the patient criteria codes are compared to the physician criteria codes of the appropriate and available experts or physicians. That is, at step 910 a comparison is made between the contents of the appropriate patient criteria code field 540 of the patient criteria table 500 B and the physician criterion code field 520 of the physician criteria table 500 A to determine if any of the physicians that are appropriate and available have conflicting criterion codes. For example, in the case of a patient criteria code indicative of a requirement for a male physician having a fee structure in the lower 33 rd percentile, female physicians and those physicians having fee structures in the middle and upper 33 rd percentile would conflict. At step 912 those physicians having conflicting criterion are eliminated from consideration for an offer of compensation in exchange for diagnostic services. The method 900 then proceeds to optional step 914 or to step 916 .
- step 914 those physicians having criterion conflicting with the patient's insurance company are eliminated from consideration of receiving an offer of compensation in exchange for their diagnosis. That is, those physicians deemed by the patient's insurance company to be undesirable, too expensive, not included within the health plan or network, in competition with the patient's insurance company's preferred physicians or otherwise deemed unsuitable by the insurance company are eliminated from consideration of an offer (unless later needed, per step 918 ).
- the geographic location of the patient and the geographic are the physician is licensed to practice in may be taken into consideration by the system 100 .
- only doctors that are licensed to practice in Virginia may be selected for a case of a patient located (or whose state of residence is) Virginia.
- the areas a physician is licensed to practice in may be stored in the physician criteria table 500 A or otherwise accessed by the system 100 .
- the patient's location may be determined via GPS locator 135 or the patient may be queried for his current location. If the patient's area of residence is a relevant factor, the residence may be stored, for example, in the patient criteria table 500 B.
- a physician that is not licensed to practice in the patient's are may be contacted by the system but may need to work with or through another physician that is licensed in the patient's area to render the diagnosis (e.g. local physician may need to approve diagnosis).
- step 916 those experts and/or physicians determined to be appropriate and available (per step 906 ) and not eliminated from consideration due to conflicting criterion with a patient (step 912 ) or insurance company (step 914 ) criterion list are preferentially sorted per the patient's criteria. That is, those experts still remaining are sorted according to attributes deemed by a patient to be more favorable. For example, in the case of a patient criteria indicative of a preference for a male physician, and a preference for a board certified physician, physicians meeting these preferred criteria will be preferentially considered to physicians not meeting these criteria. Thus, the outcome of step 916 is a preferentially sorted list of physicians.
- Physicians near the top of the list are more preferable from the patient's perspective to those physicians near the bottom of the list. This does not mean that the physicians near the bottom of the list are unacceptable; rather that the physicians near the bottom of the list simply fail to meet or to confirm to the patient's criteria as well as those physicians near the top of the list.
- the method 900 then proceeds to step 918 .
- a query is made as to whether a minimum number of physicians or experts are remaining. That is, a query is made as to whether a predetermined minimum number of physicians are remaining within the pool or group of those physicians under consideration for an offer.
- the predetermined number may comprise one, three or any appropriate number.
- the predetermined minimum number of physicians being sent an offer at any one time should be low, e.g., five.
- the query at step 918 is answered negatively (e.g., only four physicians in the case of a five physician minimum avoiding elimination for consideration of an offer)
- the method 900 proceeds to step 920 . If the query at step 918 is answered affirmatively, then the method 900 proceeds to step 922 .
- step 920 the criteria of acceptability is widened such that more physicians are included within the list of physicians being considered.
- the criteria may be widened to include physicians of any gender, regardless of patient preference.
- the method 900 proceeds from step 920 to step 912 .
- step 922 an appropriate respective offer of compensation in exchange for a diagnosis for the particular event triggered by the telemetry signal received at step 804 is sent to each of the remaining physicians.
- the method 900 then proceeds to step 924 where it is exited (e.g., method 800 is re-entered at step 814 ).
- FIG. 10 depicts a flow diagram of an offer processing method suitable for use in the expert selection method of FIGS. 9A and 9B. Specifically, FIG. 10 depicts a flow diagram of a method 1000 for processing offer requests or for sending offers to remaining physicians suitable for use in, e.g., step 922 of the expert selection method 900 of FIGS. 9A and 9B.
- the offer processing method 1000 is initiated at step 1002 and proceeds to step 1004 , where a request to send an offer to one or more physicians is received.
- An appropriate compensation level may be determined with respect to, per box 1008 , historical data, current demand, insurance contracting, other contracts or other inducements.
- Historical data comprises data indicative of past offers that have been accepted or rejected by a particular physician.
- the historical data may be further refined into acceptance and rejection data associated with particular offers on particular days of a month (e.g., weekends or week days) and other historical factors relating to the order acceptance/rejection history of a physician.
- the offers made field 770 and offers accepted field 780 of the event database 700 provides useful historical data that may be correlated to individual physicians or experts. After determining the appropriate offer levels, the method 1000 then proceeds to step 1010 .
- Current demand comprises an indicator of an amount of demand for diagnostic services for a particular specialty. For example, during a heat wave compounded by an electrical failure in a city requiring air conditioning it may be the case that current demand for cardiologists and other specialists engaged in the diagnosis and/or treatment of heat-related conditions may be quite high. In this case, such an expert may be extremely busy and more likely to reject an offer to render a diagnosis in the absence of a sufficiently large monetary inducement.
- An insurance contract binding a particular physician to the treatment of a patient carrying that insurance at a set contract rate may be honored. Therefore an offer to such a physician may include the appropriate contract compensation rate.
- a patient availing himself or herself of the system of the present invention may indicate that an additional inducement is to be offered (paid by the patient) to a physician beyond any contract rate negotiated by an insurance company.
- a person of sufficient means, but insufficient cardiac strength may offer an additional cash inducement to the hospital or other medical facility or health care provider such that an offer made to a physician should include the insurance contract rate plus the additional cash inducement offered by the patient to arrive at a “bump-up” offer price.
- step 1010 the respective offers determined at step 1006 are sent to the respective physicians or experts.
- the method 1000 then proceeds to step 1012 .
- step 1012 some or all of the telemetry data, medical records and patient preferences are sent to the physicians or experts receiving offers.
- the purpose of this data transfer is primarily to provide the expert with sufficient information to make a decision as to whether or not to take the case. However, if all of the patient data is sent, then it is possible that the physician may accept and render an opinion at substantially the same time.
- the method 1000 then proceeds to step 1013 .
- the method 1000 waits for a predefined maximum period of time to receive one or more “accept” signals which are received from physicians or experts to whom offers have been sent. That is, a physician may have received an offer via his physician terminal device 110 , e.g., a personal digital assistant (PDA) or other portable communication device proximate to the physician. Upon reviewing the offer and, perhaps, some initial patient data, the physician may decide that time allows him or her to render a diagnosis to the patient. In such a situation the physician signals to the central server 200 his or her acceptance of the offer by sending a page or otherwise communicating with the central server 200 .
- PDA personal digital assistant
- a physician may sit down at a computer terminal and access the server via, e.g., the internet, thereby directly accepting the offer.
- the dissemination of telemetry data, medical records and patient preferences indicated at step 1012 is performed by the physician downloading this information to his local computing device.
- the method 1000 proceeds to step 1014 .
- step 1014 a query is made as to whether any “accept” signals have been received. If the query is answered affirmatively, then the method 1000 proceeds to step 1016 . If the query is answered negatively, then the method 1000 proceeds to step 1015 .
- each offer may be increased by a fixed amount (e.g., $25), an amount determined as a percentage (e.g., 15%) of the existing offer or some other amount. It should be noted that an increased offer may be made to less than the entirety of physicians receiving an offer. For example, if one physician is known to typically accept offers above a certain amount, that physician may be provided with a second higher offer, while other physicians may receive second offers having unchanged (or minutely changed) offer amounts. The method 1000 then proceeds to step 1010 .
- a fixed amount e.g., $25
- an amount determined as a percentage e.g. 15%
- a query is made as to whether the patient associated with the present event is also associated with a code R-FA (requires first available physician). If the query at step 1016 is answered affirmatively, then the method 1000 proceeds to step 1018 . If the query at step 1016 is answered negatively, then the method 1000 proceeds to step 1020 .
- step 1018 since the patient requires a first available physician, the first acceptance of a physician is confirmed. That is, regardless of patient preferences beyond those already used to screen the physicians to whom offers were made, the first physician indicating his or her acceptance of an offer is confirmed by the central server 200 . Confirmation of an offer by the central server 200 entails indicating, in some manner, to the physician that the physicians diagnosis is required, that compensation per the offer will be made for that diagnosis, and that the physician should now be rendering that diagnosis.
- step 1020 since the patient does not require the first available physician, at least one acceptance is confirmed based upon the preferential sorting of the physicians to whom offers were made. That is, in the case of a patient having an insurance company that will pay for the services of one physician to render a diagnosis for an event, the one accepting physician meeting all or most of the patient's preferences will be confirmed as the physician or expert involved in the event. It should be noted that in the case of the patient requiring two or more expert diagnosis to be rendered, the two or more physicians most closely conforming to the patient's preferences as indicated by the patient criterion database 500 B will be confirmed.
- a confirmation signal is sent to the one or more physicians or experts to be confirmed.
- the confirmation signal may be sent via the physician terminal device 110 (e.g., pager, cellular or terrestrial telephone link, computer network, satellite network or any other communications medium).
- step 1024 the necessary medical history, current condition and other data associated with the patient and the present event is transmitted to the physician terminal device 110 .
- this step comprises, essentially, the same functionality described above with respect to step 814 of the method 800 of FIGS. 8A and 8B.
- step 814 may be skipped if the method 1000 of FIG. 10 is being called as, e.g., a sub-method of the method 800 of FIGS. 8A and 8B.
- the method 1000 then proceeds to step 1026 where it is exited (e.g., the expert selection routine 900 of FIGS. 9A and 9B is reentered at step 924 ).
- FIG. 11 depicts a flow diagram of a patient care diagnosis delivery method 1100 suitable for use in the patient care diagnosis delivery system 100 of FIG. 1.
- the telemetry unit associated with a patient includes at least rudimentary diagnostic capability such that the alarm signal transmitted by the telemetry device includes a particular diagnosis that is associated with an element of the alert field 310 of the reaction database 300 of FIG. 3.
- an alert message indicating ventricular fibrillation is transmitted as an alarm signal to the central server 200 .
- the patient care diagnosis delivery method 1100 is initiated at step 1102 and proceeds to step 1104 , where an alarm signal is received from a patient telemetry device. The method 1100 then proceeds to step 1106 .
- This determination includes determining an appropriate type of position or expert and whether an ambulance is required.
- an appropriate system reaction comprises summoning an ambulance to pick up the patient and bring the patient to a nearby medical treatment facility and offering the case to physicians or experts comprising cardiologists or heart specialists.
- step 1108 a query is made as to whether an ambulance is required. If the query at step 1108 is answered affirmatively, then the method 1100 proceeds to step 1110 where an ambulance is summoned. The method then proceeds to step 1112 . If the query at step 1108 indicates that an ambulance is not required, then the method 1100 proceeds directly to step 1112 .
- At step 1112 at least one expert is alerted to the event associated with the received alarm, the patient's medical history, a description of the patient's current state and an offer of compensation is then made to the at least one expert in exchange for taking the case (i.e., rendering a diagnosis).
- step 1114 an “accept” or “decline” signal is received from the at least one expert or physician alerted at step 1112 .
- the method 1100 then proceeds to step 1116 .
- step 1116 At step 1116 at least one of the physicians from the pool or group of physicians or experts indicating an acceptance of the case is selected.
- the method 1100 then proceeds to step 1118 .
- step 1118 a confirmation signal is sent to the accepting expert or experts.
- the accepting and confirmed physician or expert has taken the case and is expected to render an expert diagnosis using the data transmitted at step 1112 in exchange for the compensation offered at step 1112 .
- the method 1100 then proceeds to step 1120 where it is exited.
- a patient telemetry device monitors the patient physiological parameters including heart activity via, e.g., an electrocardiogram (ECG) function.
- ECG electrocardiogram
- the ECG continuously monitors the patient's heart and the resulting data is sent to the central server 200 as part of a compressed data stream transmitted via a patient telemetry device 120 .
- the central server 200 receives the data and analyzes the data to detect any aberrant data patterns, i.e., data patterns indicative of a cardiac anomaly. When such a pattern is detected, the computer compares it with pre-defined malignant patterns (i.e., data profiles) to ascertain whether or not the pattern requires intervention on the part of the patient or the hospital. If the pattern of the received data describes a malignant aberrance such as heart palpitations or arrhythmia, a signal is sent to the patient (to apprise him or her of the situation), and one or more cardiologists are selected to receive an offer according to both patient and physician criteria, as previously described.
- pre-defined malignant patterns i.e., data profiles
- the system would summon an ambulance to the patient's location—which could be determined with a GPS unit in the patient telemetry device 120 and also contact a cardiologist. If the pattern observed by the system did not match either a benign or pathological pattern, the system would notify the patient and provide a phone number to call for further assessment of the situation.
- the physician terminal device 110 in the example comprises a Personal Digital Assistant (PDA) that is used in conjunction with wireless data transfer.
- PDA Personal Digital Assistant
- a plurality of experts meeting the appropriate criteria are paged and provided with the patient's current condition, medical records and respective monetary offers.
- An expert who accepts the case indicates that acceptance via the PDA, which provides two-way paging capability.
- the expert communicates with the central server 200 via the PDA, a mobile phone, a computer or some combination thereof.
- the expert completed the services required he or she would indicate this by way of the PDA and a financial account associated with the expert is credited with the amount offered.
- the invention provides a system that will alert physicians and/or patients when the patient's health takes a turn for the worse. Whether or not a patient lives through a cardiac arrest is often determined by how soon he receives treatment. By cutting the medical response time to the absolute minimum, the inventive system will save lives and reduce impairments to those lives.
- the expert utilizes the internet to retrieve patient information and render a diagnosis.
- the expert When contacted with an offer, the expert goes to a web site, types in his expert ID, the patient's ID (received with the offer) and is immediately provided with the patient's records and current condition.
- the central server 200 sends case offers to hospitals, which then act as clearinghouses for the doctors employed there.
- the server receives an alarm signal from a monitored patient and sends the offer to one or more hospitals, which then have the option of taking the case, depending on how busy they are.
- the invention operates as a “traffic controller” for hospitals.
- a medical facility is associated with at least one expert and comprises infrastructure suitable for remediating physiological dysfunction.
- the system procures a diagnosis from experts via the facility by transmitting offer(s) to the facility for subsequent communication to the appropriate experts.
- the facility may adapt the offer (e.g., increase the amount) to ensure that an ambulance delivers a patient to the facility where the physician has admitting rights.
- the adaptation of the offer may be performed in response to a level of facility utilization and a level of physiological dysfunction urgency associated with said offer. That is, in response to a level of facility utilization being above a threshold level and a level of physiological dysfunction urgency being below a threshold level, the offer may be adapted to cause the patient to be delivered to an alternate or affiliated medical facility for processing.
- a plurality of medical facilities may be operably linked together by a central server via a communications system such that the central server, in response to an offer received from a system controller, determines which one of the plurality of medical facilities should receive the offer and communicates the offer to the determined medical facility. Additionally, the determination of the central server may be made using at least one of the following criteria applied to said medical facilities: proximity to a patient, general facility utilization level, appropriate department utilization level (e.g., intensive care unit, trauma unit, emergency room and the like), a level of expertise in treating an indicated physiological dysfunction, possession of equipment suitable for treating the indicated physiological dysfunction, membership in a predetermined health care provider group and participation in a predetermined insurance plan.
- department utilization level e.g., intensive care unit, trauma unit, emergency room and the like
- the invention allows at least voice communication between the remote physician and the patient.
- the physician gives instructions to the patient on how best to act until an ambulance arrives. If the patient is unconscious, the physician may interact with a bystander to remotely help the patient. Additionally, the physician may optionally administer drugs remotely if a patient telemetry device 110 is equipped with a drug dispensing unit 135 .
- the expert may enter into an agreement with the system wherein the expert is paid a previously established compensation amount on a periodic basis in exchange for agreeing to accept a predetermined minimum number of cases during each compensation period. For example, a physician may agree to accept ten cases per week in exchange for receiving $1000 on a bi-weekly basis. In such an agreement there may be a further provision that the expert will receive an additional compensation for accepting more than the minimum number of cases required under the agreement. In such an embodiment an expert may still be selected and offered a case on a real-time basis (i.e.
- the offer to the expert would not necessarily include a compensation amount.
- the offer could include a reminder of the periodic compensation amount, the portion of the periodic compensation amount that this case may be worth to the expert, or how many cases the expert still has to accept within the current period in order to earn the periodic compensation amount.
- FIG. 13 depicts table 1300 , an exemplary illustration of a compensation agreement database 800 , which could be used by system 100 to track compensation agreements with experts in the embodiment where an expert is compensated by a predetermined amount on a periodic bases.
- Table 1300 comprises exemplary records 1301 through 1301 . Each record contains data stored in an agreement identifier field 1310 , a physician identifier field 1320 , a compensation amount field 1330 , a compensation periodicity field 1340 , a minimum case per period field 1350 , a bonus case amount field 1360 , and a current cases taken field 1370 .
- the agreement identifier field 1310 stores an identifier that uniquely identifies an agreement between an expert and system 100 .
- the physician identifier field 1320 stores an identifier that uniquely identifies a physician participating in the system 100 who corresponds to each respective agreement identifier.
- the compensation amount field 1330 stores the compensation amount corresponding to each respective agreement identifier, which the corresponding physician will receive in exchange for accepting cases through the system 100 . Although monetary compensation amounts are illustrated in the figure, the compensation amount could comprise other forms of compensation.
- an expert could receive (i) a reduction in insurance premiums; (ii) points or credits in a club or professional association; (iii) alternate currency such as frequent flier miles; (iv) continued access to a service, establishment, or product; or (v) public recognition for donating time to pro bono work.
- a reduction in insurance premiums for example, a reduction in insurance premiums; (ii) points or credits in a club or professional association; (iii) alternate currency such as frequent flier miles; (iv) continued access to a service, establishment, or product; or (v) public recognition for donating time to pro bono work.
- alternate forms of compensation may be implemented in all embodiments of the present invention.
- the compensation periodicity field 1340 stores the time period corresponding to each agreement identifier during which the expert must accept cases in order to qualify for the compensation amount.
- the minimum cases per period field 1350 stores the minimum number of cases corresponding to each agreement identifier which an expert has agreed to accept in order to qualify for the compensation amount.
- each case that an expert accepts will count as a single case.
- an expert may receive credit towards the minimum number of cases requirement equaling more than one case for accepting certain cases. For example, if a case is particularly complicated or the resolution of which takes an inordinately long amount of time, the expert may receive a multiple case credit for accepting that case.
- the system 100 may transmit an offer to an expert communicating that if the expert accepts this particular case it will count as two or more cases towards meeting his minimum number of cases requirement under the agreement.
- cases may comprise a single event requiring a diagnosis or multiple events associated with the same patient and the same condition that may require the expert to communicate with the system and/or patient in more than one instance.
- the bonus case amount field 1360 stores a bonus compensation amount that corresponds to each agreement identifier.
- a bonus compensation amount is an amount of compensation that an expert is to receive for each case that he accepts over the minimum number of cases required under his agreement.
- Record R 1301 illustrates that if physician “123456” accepts seven cases in a given week he will receive a total compensation amount of $600 for that week ($500 compensation amount for six required cases+$100 bonus amount for one non-required case).
- the expert may be rewarded in other ways.
- Record 1302 of table 1300 illustrates that physician “789012” will receive credit towards the minimum number of cases for the next period for any case he accepts beyond the minimum number of required cases in a current period.
- the current cases taken field 1370 stores the updated amount of cases that have been accepted to date for a given period by a physician corresponding to an agreement identifier. This field may be used by the system 100 , for example, to determine whether to (i) contact a physician with a current case; (ii) remind a physician regarding how many more cases he is still required to accept for the current period; or (iii) to provide the physician with compensation for the current period and, if so, what the compensation amount should be.
- a physician may not agree to have any offers for cases transmitted to him once he has accepted the minimum number of cases so if the number of cases accepted is equal to the minimum number of cases for a given agreement, the system may remove the physician from the pool of possible physicians to contact for a given case. Similarly, the system 100 may take into consideration whether a particular physician has met his minimum number of cases requirement and would thus require a bonus compensation amount for accepting the current case (and, perhaps, what that bonus compensation amount is) before selecting that physician to contact for a current case.
- an expert does not meet his minimum number of cases for a given period he may be penalized in a variety of methods. For example, the physician may have (i) his compensation amount for the period reduced, (ii) his entire compensation for the period forfeited, or (iii) the number of cases under the minimum number of cases for the current period added as additional required cases to a subsequent period.
- the experts may not be contacted by the system with offers for available cases. Instead, the experts may contact the system and view available offers when the experts are available to provided diagnoses.
- the experts may be combined with an embodiment where the experts are contacted by the system. For example, the system may select and contact experts as described above each time a patient is determined to be in need of help. However, while the system is awaiting responses from the contacted experts the case will be made available for consideration and acceptance by other experts (e.g. on a website of the system).
Abstract
Description
- This application is a continuation-in-part of commonly-owned, co-pending U.S. patent application Ser. No. 09/282,132 entitled PATIENT CARE DELIVERY SYSTEM, filed Mar. 31, 1999, which is incorporated by reference herein in its entirety.
- 1. Field of the Invention
- This invention generally relates to patient care diagnosis delivery and, more particularly, to facilitating, in exchange for compensation, the provision of an expert diagnosis opinion of a condition based upon data gathered from a remote monitor.
- 2. Description of the Prior Art
- It is known to remotely monitor human physiological parameters such as heart rate, blood pressure, brain waves and the like in patients. Such monitoring may be accomplished using remote monitoring, thereby allowing patients to have freedom of movement. For example, some systems use cellular telephone technology to allow patients to live at home. The patient visits the hospital if the telemetry device indicates that a visit is warranted.
- Hewlett-Packard's ECGStat software for its PalmVue handheld computer system allows emergency room clinicians to capture and transmit full 12-lead ECG data, including waveforms, computerized analysis and patient notes to cardiac specialists outside the hospital. It is a wireless system that uses paging technology to transmit data to a physician's handheld computer.
- It is well known to use ECG monitors in conjunction with software to analyze patterns in patients' heartbeats. Typically, monitoring technicians (or monitors) are alerted to the possibility that something is amiss by an alarm. Upon examining a readout of the vital sign in question, the monitor makes a decision about (i) whether the patient requires attention (ii) whether the patient requires a cardiologist's services and if so, (iii) which cardiologist to call. Typically, the technician selects the cardiologist from a list of available specialists. This list is substantially determined by availability, i.e., who is on call at the time. If a cardiologist is required, the technician must communicate to a cardiologist the patient's condition over voice or data lines. The technician may use the Hewlett-Packard ECGStat system described above to communicate with the cardiologist.
- Monitoring technicians must watch and wait for alarms to go off in all of the above-described systems. They may miss certain subtle warning signs, and if several alarms go off at once, they can only respond to one at a time. Additionally, they must find out which doctors are on call at the time and then contact the appropriate physician. If the “first choice” physician is not available, the technician must then try to contact another physician. In other words, the technician must operate in a serial manner to procure an expert opinion.
- Therefore, it is seen to be desirable to provide a system able to analyze a signal from remote monitoring equipment, e.g., medical monitoring equipment, in such a way as to make a preliminary decision about whether or not an expert, such as a physician, should be contacted and to decide which physician or physicians to contact. Moreover, it is seen to be desirable to provide a system that allows physicians and other experts to accept or decline offers made by the system to render a diagnosis, thereby implementing a “piecework” type of compensation structure within the confines of, e.g., the medical environment. Preferably, such a system minimizes or eliminates the human fallibility involved in noticing alarms and contacting experts in a timely manner.
- The invention is a method and apparatus for analyzing data from remote monitoring equipment, such as a patient telemetry device, and determining (i) if an anomaly exists, (ii) if an anomaly does exist, what kind of action should be taken, and (iii) if a physician should be contacted, which one. Further, the system operates in parallel, in that a plurality of experts (e.g., physicians) may be contacted in response to multiple anomalous events, thus ensuring the quickest possible response time.
- The present invention further contemplates methods for obtaining opinions from a plurality of experts and aggregating such diagnoses into an aggregate diagnosis. The opinions may be rendered by experts working independently or in consultation with one another. The aggregate diagnosis is obtained in response to detection of an anomaly in data from remote monitoring equipment of a patient. The invention further contemplates various compensation schemes for providing payment to experts who provide a diagnosis.
- A method for procuring a diagnosis according to the invention comprises the steps of: receiving representative data that represents at least one physiological parameter of a patient; determining whether the received data is indicative of a physiological anomaly; selecting at least one expert to provide an expert opinion regarding the indicated anomaly; communicating, to the at least one selected expert, the physiological representative data, including the determined anomaly; and receiving, from at least one selected expert, a diagnosis of the anomaly.
- A diagnostic procurement system according to the invention comprises: a monitor, for monitoring at least one parameter associated with an entity and communicating data representing the at least one entity parameter; and a controller, responsive to the data representing the at least one entity parameter, for determining whether anomalous entity operational parameters are present and, in the case of anomalous entity operational parameters being present, procuring a diagnosis from at least one of a predetermined number of experts.
- The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
- FIG. 1 depicts a high level block diagram of a patient care diagnosis delivery system;
- FIG. 2 depicts a high level block diagram of a
central server 200 suitable for use in the patient care diagnosis delivery system of FIG. 1; - FIG. 3 depicts an exemplary reaction database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 4 depicts an exemplary physician database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 5A depicts an exemplary physician criteria database in tabular form suitable for use in the central server of FIGS. 1 and 2;
- FIG. 5B depicts an exemplary patient criteria database in tabular form suitable for use in the
central server 200 of FIGS. 1 and 2; - FIG. 6 depicts an exemplary patient database in tabular form suitable for use in the
central server 200 of FIGS. 1 and 2; - FIG. 7 depicts an
exemplary event database 700 in tabular form suitable for use in the central server of FIGS. 1 and 2; - FIGS. 8A and 8B depict a flow diagram of a patient care diagnosis delivery method suitable for use in the patient care diagnosis delivery system of FIG. 1;
- FIGS. 9A and 9B depict a flow diagram of an expert selection method suitable for use in the patient delivery method of FIGS. 8A and 8B;
- FIG. 10 depicts a flow diagram of an offer processing method suitable for use in the expert selection method of FIGS. 9A and 9B; and
- FIG. 11 depicts a flow diagram of a patient care
diagnosis delivery method 1100 suitable for use in the patient carediagnosis delivery system 100 of FIG. 1. - FIG. 12 depicts a flow diagram of a patient care
diagnosis delivery method 1200 suitable for use in the patient carediagnosis delivery system 100 of FIG. 1. - FIG. 13 depicts an exemplary compensation agreement database in tabular form suitable for use in the
central server 200 of FIGS. 1 and 2 - To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
- Applicants have recognized a need in the medical treatment community that has until now not been addressed. In one embodiment, the present invention comprises a system which carries out continuous and passive monitoring of a patient, wherein the patient's physiological parameters are monitored by a system remote from the patient and which system detects and automatically processes any recognized anomalies in such parameters, such that a potential problem may be caught and analyzed before the patient even realizes that there is anything wrong. For example the system of the present invention may detect lack of movement from a fetus or a slow-down in the heartbeat of a fetus and contact an obstetrician to determine a course of action. The obstetrician may in turn study the data and determine that such a slow-down in heartbeat is normal under the circumstances and advise the system that nothing further needs to be done. The patient being monitored can rest easier and go on about her daily activities, secure in the knowledge that her health is being continuously monitored and qualified experts are being contacted as needed. The patient does not need to worry about contacting her own physician or finding an available physician. The system has access to a multitude of qualified experts, with enormous resources to find the right expert regardless of time of day or night. Further, the system may handle the monitoring of many patients and parameters simultaneously and be capable of responding to various anomalies in different patients simultaneously such that the patient's diagnosis is not delayed unnecessarily. This is because, in at least one embodiment, the system is capable of analyzing and processing the initial physiological data automatically in order to determine what type of expert to contact, rather than being dependent on a human being to monitor physiological data and attempt to contact local physicians manually
- After considering the following description, those skilled in the art will clearly realize that the teachings of the present invention can be readily utilized in any environment in which an entity (e.g., a patient) having at least one monitored operating parameter (e.g., physiological parameter) may require an expert diagnostic or other opinion if one or more of the monitored operating parameters indicates that an operating anomaly is present. The system and method provide (a) an initial screening and decision capability based upon the received operating data sufficient to determine which type of expert is needed; (b) an identification and communication of at least a portion of the operating data to one or more appropriate experts; (c) a transactional capability defining a level of compensation to be provided to the expert in exchange for the rendering of an expert diagnosis regarding the anomaly; and (d) an adaptation of an existing communications infrastructure to the procurement of the expert opinion(s).
- While the invention will be primarily described within the context of a medical monitoring system, it will be appreciated by those skilled in the art that the invention has applicability well beyond the patient care diagnosis delivery system described herein. Specifically, the invention comprises, in general terms, a centralized system procuring expert diagnosis or diagnostic opinion(s) in response to remotely monitored data indicative of an event requiring such an opinion.
- Throughout this description various terms are used to describe the invention. Unless modified by the following description, several of the terms are defined as follows: An anomaly comprises a dysfunction or precursor to a dysfunction within a monitored entity, such as a patient in a medical monitoring environment. An “expert” is an entity that provides a diagnosis relating to an anomaly. An expert is one deemed by the patient and, optionally, the system, as having expertise in treating the patient's condition. In the case of standard medical specialties, the patient and system will be in agreement as to the definition of an expert. If the patient believes in practitioners of non-standard or alternative therapies, then the system and patient may disagree. A “diagnosis” or diagnostic opinion comprises an identification of an anomaly, a recommended treatment for a patient or any expert opinion tending to remediate or ameliorate an anomalous condition. “Communication” comprises any means of transferring data to or from a communicating party, such as a patient telemetry device, a central server, a physician terminal device, a computing device or telephonic device and the like. A communication may utilize encryption/decryption protocols. “Alert information” comprises information, including local diagnostic information, real time physiological data and other information intended to be used in the rendering of a diagnosis or a determination of the type of expert needed to render such a diagnosis. A data profile is a data template against which raw or processed information is compared to produce a level of affinity between the information and the data profile. A high level of affinity indicates that the information may conform to an anomalous condition associated with the data profile. Profiles may be individualized and adapted to patients. For example, a baseline profile may be adapted over time in response to a patient's improving or degrading condition (e.g., diminished heart valve integrity will lead to changes in ECG data as the heart adapts by pumping harder and/or differently).
- FIG. 1 depicts a high level block diagram of a patient care diagnosis delivery system. Specifically, FIG. 1 depicts a high level block diagram of a patient care
diagnosis delivery system 100 comprising a plurality of physician terminal devices 110-1 through 110-N, acentral server 200 and a plurality of patient telemetry devices 120-1 through 120-N. - Each of the plurality of patient telemetry devices120-1 through 120-N is capable of monitoring at least one physiological parameter of a patient and communicating data representative of the monitored parameter to the
central server 200 via respective data paths P1 through PN. The patient telemetry device may comprise a known device capable of monitoring patient data, transmitting that data to the central server and, optionally, receiving data from thecentral server 200. - The
central server 200 examines the communicated data to determine if the at least one physiological parameter is within appropriate or “normal” parameter boundaries. If the data is not within the appropriate boundary, thecentral server 200 determines if an event or medical anomaly (e.g., cardiac arrest or other condition) may be occurring. If such a determination is made, then thecentral server 200 communicates an offer to one or more of the physician terminal devices via respective data paths E1 through EN. - Each physician terminal device110 (i.e., physician terminals 110-1 through 110-N) is associated with at least one respective expert, such as physician(s), nurse(s), and other experts. A physician receiving an offer accepts that offer by communicating an acceptance message to the
central server 200 via thephysician terminal device 110 or another means (e.g., telephone, computer network and the like). The central server then decides which one (or more than one) of the accepted offers will be confirmed by sending a confirmation signal to the physician via, e.g., the respective physician terminal device(s). The physician terminal device may comprise a known device capable of receiving information from the central server and, optionally, transmitting information to thecentral server 200. For example, a pager, a personal digital assistant (PDA) or a cellular telephone may be utilized for this purpose. - An exemplary embodiment of a patient telemetry device120-1 comprises an input/output (I/O)
circuit 125,support circuitry 123, aprocessor 124, amemory 126 and adata link 127. Theprocessor 124 cooperates withconventional support circuitry 123 such as power supplies, clock circuits, cache memory and the like as well as circuits that assist in executing the various software routines within the patient telemetry device 120-1. Input/output circuit 125 forms an interface between the patient telemetry device 120-1 and sources of patient physiological data. For example, the input/output circuit 125 may comprise sensors, transducers and other analog to digital conversion circuitry adapted to measure physiological parameters associated with a patient, such as heart rate, blood pressure, temperature, perspiration level, respiratory activity, body electrical activity, brain activity and the like. The physiological information is received and/or processed by the input/output circuitry to produce physiological parameter representative data in a form usable byprocessor 124. Theprocessor 124 communicates the physiological parameter representative data to thecentral server 200 via adata link 127. -
Data link 127 comprises a wireless or a non-wireless data link (e.g., a telephone dialer, a cellular telephone link, or a computer link) or other communications link driver suitable for providing patient data to thecentral server 200 via a respective data path (e.g., data path P1). The patient telemetry device is optionally responsive to a patient control signal. The patient control signal comprises a signal that a patient may use to communicate specific information or a request to thecentral server 200. For example, in the case of a patient sensing the onset of some physiological anomaly (e.g., the beginning of cardiac arrest) or the patient suffering a trauma (such as a fall), the patient may manually communicate this condition to thecentral server 200 such that appropriate action (e.g., summon an ambulance) is taken. The patient control signal is produced by anoptional input device 145, illustratively, a key pad. The patient control signal is used to communicate a message to thecentral server 200 comprising, e.g., a standby mode message, an impending exertion message, an equipment failure message, a medical emergency message, a non-medical emergency message, a specific physiological dysfunction message and a test message. In response to such a message, the system may choose to ignore any apparent anomalies. - An exemplary embodiment of a physician terminal device110-1 comprises an input/output (I/O)
circuit 115,support circuitry 113, aprocessor 114,memory 116, adisplay device 111 and adata entry device 112. Theprocessor 114 cooperates withconventional support circuitry 113 such as power supplies, clock circuits, cache memory and the like as well as circuits that assist in executing various software routines. The physician terminal device 110-1 also contains input/output circuitry 115 that forms an interface between thephysician terminal device 110 and thecentral server 200. Thedisplay device 111 comprises a liquid crystal display (LCD) or other display means, while thedata entry device 112 comprises a keyboard or other data entry means. Thememory 116 includes a standard control program such as a PDA or cellular telephone control program that enables a physician or expert interacting with the physician terminal device to receive information from thecentral server 200 and, optionally, transmit information back to thecentral server 200. - Referring now to the patient telemetry device120-1, in one embodiment of the invention, the physiological information received from the patient is merely converted into a digital information stream, either compressed or uncompressed, and transmitted directly to the
central server 200. That is, thepatient telemetry device 120 does not perform any analysis of the physiological data. The data is merely passed to thecentral server 200 in either a compressed or uncompressed data format as appropriate to, e.g., the format of data link P1. Compressed data transfer may be effected using various compression methods, such as the frequency domain transform functions utilized in known communications systems. - In another embodiment of the invention, the
processor 124 performs an analysis of the received physiological information to determine if, for example, monitored parameters of the patient are within appropriate boundaries. For example, theprocessor 124 may be programmed (via a control program within the memory 126) to issue an alert to thecentral server 200 in the event of a patient heart rate exceeding an upper threshold level or dropping below a lower threshold level. Multiple parameter alarms may be programmed such that particular combinations of physiological parameter levels trigger specific alerts indicative of specific conditions. - In another embodiment of the invention, the patient telemetry device120-1 and
central server 200 communicate bi-directionally. In this embodiment, parameter threshold levels are optionally updated via the data link (P1-PN) or other means (e.g., via an internet or telephone connection) such that patient monitoring may be calibrated to the changing needs of a patient. For example, if a patient is about to exercise, it is quite likely that the measured heart rate will increase. Therefore, the patient may communicate this fact to thecentral server 200 via a patient control signal produced using thekeypad 145. Bi-directional communication may be effected via theinternet 170 or other communications medium. - In another embodiment of the present invention utilizing bi-directional communication with the
central server 200, the patient telemetry device 120-1 is associated with adrug dispensing device 130. In this embodiment of the invention, thecentral server 200 may be used to control the dispensing of drugs to the patient via thedrug dispensing device 130. For example, in the case of a patient exhibiting physiological information indicative of cardiac arrest, thecentral server 200 may cause thedrug dispensing device 130 to dispense medication tending to reduce or mitigate any harm to the patient due to the event. In the case of local analysis by thepatient telemetry device 120, the decision to dispense medication may be made locally. Additionally, medication dispensing may be placed under the control of the patient (e.g., pain medication up to a predefined dosage rate). Optionally, the local control of medication dispensing is communicated to thecentral server 200 where the patient's medical records are responsively updated. - In another embodiment of the present invention utilizing bi-directional communication with the
central server 200, thepatient telemetry device 120 is associated with a global positioning system (GPS)locator 135. TheGPS locator 135 comprises known GPS receiver circuitry suitable for determining the geographic position of the patient (assuming the patient is near the GPS locator). The geographic position of the patient is transmitted to thecentral server 200 for use in, e.g., directing an ambulance to the patient, performing geographical-based analysis of aggregated patient data or other functions. - In another embodiment of the invention utilizing bi-directional communication with the
central server 200, thepatient telemetry device 120 is associated with an automatic external defibrillator (AED) 140. In the event of the physiological information of the patient being indicative of, e.g., a ventricular fibrillation, a central server or decision may indicate that defibrillation is appropriate. In this case, the central server or patient telemetry device causes the automatic external defibrillator to enter an active mode of operation. Present automatic external defibrillators include monitoring capabilities such that they do not administer an electric shock to a patient unless such an electric shock is warranted. That is, present automatic external defibrillators perform monitoring operations to confirm the need for a defibrillation. Such functionality may optionally be incorporated into thepatient telemetry device 120. - In another embodiment of the invention, a
security system 150 associated with the patient is coupled to thepatient telemetry device 120 such that in the event of a medical emergency, thecentral server 200 is contacted and, additionally, a security system server (not shown) is also contacted. In this embodiment of the invention, where a patient is paying a monitoring fee to a security system service, thedata link 127 may communicate to thecentral server 200 via thesecurity system 150 rather than the data link 127 (e.g., telephone lines, cellular telephone, two-way paging and the like). - In another embodiment of the invention, a medical records clearing-
house 180 is used to store patient medical records. In this embodiment of the invention, the patient medical records are communicated to a confirmed expert (i.e., a physician accepting an offer that has been subsequently confirmed) via theinternet 170 or via thecentral server 200. - FIG. 2 depicts a high level block diagram of a
central server 200 suitable for use in the patient care diagnosis delivery system of FIG. 1. Specifically, thecentral server 200 of FIG. 2 comprises acommunications port 210, aprocessor 220, amemory 230,support circuitry 240 and astorage device 250. Thecommunication port 210 forms an interface between thecentral server 200 and the physician terminal devices 110-1 through 110-N, the patient telemetry devices 120-1 through 120-N and, optionally, theinternet 170 and themedical records clearinghouse 180. Theprocessor 220 cooperates withsupport circuitry 240 andmemory 230 to runvarious programs 1200 and use various databases 300-700 stored instorage device 250. Specifically, thestorage device 250 is used to store aprogram 1200 that will direct theprocessor 220 to perform the methods of the present invention and to store various databases 300-700 used to implement the methods of the present invention. In an exemplary embodiment, thestorage device 250 is used to store areaction database 300, aphysician database 400, acriteria database 500, apatient database 600,anevent database 700, and acompensation agreement database 800. Thereaction database 300 will be discussed in more detail below with respect to FIG. 3, thephysician database 400 will be discussed with more detail below with respect to FIG. 4, thecriteria database 500 will be discussed in more detail below with respect to FIGS. 5A and 5B, thepatient database 600 will be discussed in more detail below with respect to FIG. 6, theevent database 700 will be discussed in more detail below with respect to FIG. 7, and the compensation agreement database will be discussed in more detail below with respect to FIG. 13. It should be noted that the programs and databases may be stored locally in thecentral server 200 or in a remote location, such as the optional medicalrecords clearing house 180 depicted in FIG. 1. - The operation of the
central server 200 will be described in more detail below with respect to FIGS. 8-12. Briefly, in one embodiment of the invention thecentral server 200 receives a continuous signal from each patient; the received signal is analyzed to determine if any predefined patterns or data aberrations exist; any such patterns or data aberrations are further analyzed to determine whether the pattern or data aberration is pathological; if pathological, then thecentral server 200 searches the physician database for an expert, such as a physician, appropriate to the treatment of patients exhibiting such pattern or data aberration and, if appropriate, an ambulance is dispatched to bring the patient to a hospital; the expert is then paged and offered compensation to render an expert diagnosis on the patient's condition; in the case of an expert accepting the offer, thecentral server 200 confirms the acceptance and transmits to the expert a copy of at least a portion of the patient's medical history and a description of the current pattern or data aberration so that the expert diagnosis may be rendered. - FIG. 3 depicts table305, exemplary of
reaction database 300, suitable for use in the central server of FIGS. 1 and 2. Specifically, the table 305 of FIG. 3 comprises a plurality of records R31 through R36, each record being associated with a respectivealert field 310 and a respectivesystem reaction field 320. Thealert field 310 of a record indicates a specific alert condition. Thesystem reaction field 320 of the record indicates an appropriate system reaction to the correspondingalert field 310 of the record. - It is noted that the
alert fields 310 of the table 305 of FIG. 3 assume that thepatient telemetry devices 120 of thesystem 100 of FIG. 1 provide alert information to thecentral server 200. That is, the patient telemetry devices 120-1 through 120-N perform a local data analysis (or receive direct patient input) and responsively issue an alert code to the central server. The table 305 provides, for each predefined alert, an appropriate system response to the alert. Additionally, the table 305 of FIG. 3 is shown with only six records (R31 through R36). However, it will be appreciated by those skilled in the art that thereaction database 300 may comprise an unlimited number of records. -
Alert field 310 of records R31 through R36 is depicted as indicating alert conditions as follows: ventricular fibrillation R31; loss of consciousness R32; aberrant blood glucose levels R33; fetal heart monitor alarm R34; tachycardia R35; and acutely high blood pressure R36. -
System reaction field 320 of records R31 through R36 is depicted as indicating the following system responses to corresponding alert conditions as follows: summon an ambulance and offer the case to one or more cardiologists R31; summon an ambulance and offer the case to an emergency room physician R32; instruct the patient to take insulin and, if the blood glucose levels do not return to normal after a predefined period of time (e.g., 15 minutes,) offer the case to one or more nurses R33; alert the mother, instruct her to go to the hospital and offer the case to one or more obstetricians R34; offer the case to one or more cardiologists and query the patient as to the patient's present activity level (e.g., was patient climbing stairs, playing basketball, watching television and the like) R35; and offer the case to one or more internists and query the patient as to a present activity level R36. - FIG. 4 depicts table405, exemplary of
physician database 400 suitable for use in the central server of FIGS. 1 and 2. Specifically, the table 405 of FIG. 4 comprises a plurality of records R41 through R49, each record being associated with a respective physician'sname field 410, aphysician identifier field 420, a physiciancriteria codes field 430, aspecialty field 440, a previouscase identifiers field 450, anavailability field 460 and acontact information field 470. It should be noted that theavailability field 460 may provide conditional information, i.e., an unavailable physician will always be available if a compensation level exceeds a threshold amount such as illustrated in record R48. - For each record, the physician's
name field 410 indicates the name of a particular physician; thephysician identifier field 420 indicates an insurance company, hospital or other identification number or code that uniquely identifies the physician; the physiciancriterion codes field 430 indicates physician criterion information (e.g., fee structure, board certification and the like); thespecialty field 440 indicates the physician's specialty (e.g., Cardiology, Surgery and the like); the previouscase identifiers field 450 indicates the case identifiers of previous cases handled by the physician; theavailability field 460 indicates whether the physician is presently available to handle a case; and thecontact information field 470 indicates the preferred method of contacting the physician, e.g., voice, pager, email and the like. Physicians indicate their availability by, for example, logging onto a web site or otherwise communicating by alternate means with the system to inform the system when they become available and when they cease to be available. - Record R41 of table 405 indicates that a physician named John Doe has a corresponding identifier “123456”, criterion codes “UH”, “BS”, “M33” and “MP”, a specialty of “Emergency Medicine”, previous case identifiers of “C987654”, “C876543” and “C765432”, an availability indication of “yes” and contact information indicative of a pager number of 555-1234. Record R42 indicates that a physician named Bob Smith has a corresponding identifier “234567”, criterion codes “UH”, “M33” and “MP”, a specialty of Cardiology, previous case identifiers of “C654321”, “C543210” and “C432109”, an availability indication of “no” and contact information indicative of a voice number of 555-2345.
- Records R43 through R49 contain similar data regarding other physicians. The physician
criterion codes field 430 will be discussed in more detail below with respect to FIG. 5A. For example, Record R48 of table 405 indicates that a physician named Alex Schwartz has a corresponding identifier “890123”, criterion codes “UH”, “BS”, “BC” and “MP”, a specialty of “Endocrinology”, previous case identifiers of “C999876” and “C888765”, an availability indication of “only above $150” (i.e., only available if offer is at least $150) and contact information indicative of an email address of good_doc@hospital.com. The previouscase identifier field 450 will be discussed in more detail below with respect to FIG. 7. - FIG. 5A depicts table500A, exemplary of one embodiment of
criteria database 500 suitable for use in the central server of FIGS. 1 and 2. Specifically, the table 500A of FIG. 5A comprises a plurality of records RA51 through RA58, each record being associated with a respectivephysician criterion field 510 and a physiciancriterion code field 520. - For each record RA51 through RA58, the
physician criterion field 510 indicates a particular objective or subjective criterion that may be applied to a physician. Subjective physician criteria comprise subjective preferences of the physician (e.g., preferred patients, insurance plans, hospitals and the like). For each record RA51 through RA58 the physiciancriterion code field 520 contains the corresponding code, or abbreviation, of the objective or subjective criterion contained within the respectivephysician criterion field 510. If a criterion is applicable to a given physician, the code for that criterion will appear in the physician criterion codes field 430 of a record associated with that physician in thephysician database 400. - The contents of the
physician criterion field 510 and the physiciancriterion code field 520 of records RA51 through RA58 are as follows: a physician criterion of universal health approved physician criterion is associated with code UH (record RA51); Blue Shield approved physician criterion is associated with code BS (record RA52); board certified physician criterion is associated with code BC (record RA53); fee structure in upper 33rd percentile criterion is associated with code U33 (record RA54); fee structure in middle 33rd percentile criterion is associated with code M33 (record RA55); fee structure in lower 33rd percentile criterion is associated with code L33 (record RA56); male physician criterion is associated with code MP (record RA57) and female physician criterion is associated with code FP (record RA58). - FIG. 5B depicts a table500B, exemplary of another embodiment of
criteria database 500 suitable for use in thecentral server 200 of FIGS. 1 and 2. Specifically, table 500B of FIG. 5B comprises a plurality of records RB51 through RB514, each record being associated with a respectivepatient criterion field 530 and a patientcriterion code field 540. - For each record, the
patient criterion field 530 indicates a particular objective or subjective criterion applied to a physician treating a patient that is required or preferred by the patient or the patient's insurance provider. Subjective criteria comprises subjective preferences of the patient (e.g., preferred physicians, preferred hospitals and the like). The patientcriterion code field 540 of a record contains the code, or abbreviation, of the objective criterion contained within the respectivepatient criterion field 530. A physician having a criterion code contrary to a required patient criterion code is deemed to be undesirable to the patient. A physician having all criterion codes matching those of the patient is deemed to be most desirable to the patient. Physicians having some criterion codes matching the patient preferred criterion codes may be ranked in order of preference according to the amount of correlation between the patient's and physicians' criterion codes. - The contents of the patient criterion field530 and the patient criterion code field 540 of records RB51 through RB514 are as follows: require universal health approved physician criterion is associated with code R-UH (record RB51); prefer universal health approved physician criterion is associated with code P-UH (record RB52); require Blue Shield approved physician criterion is associated with code R-BS (record RB53); prefer Blue Shield approved physician criterion is associated with code P-BS (record RB54); prefer fee structure in upper 33rd percentile criterion is associated with code P-U33 (record RB55); prefer fee structure in middle 33rd percentile criterion is associated with code P-N33 (record RB56); prefer fee structure and lower 33rd percentile criterion is associated with code P-L33 (record RB57); require board certification criterion is associated with code R-BC (record RB58); prefer board certification criterion is associated with code P-BC (record RB59); require m ale physician criterion is associated with code R-MP (record RB51O); prefer male physician criterion is associated with code P-MP (record RB511); require female physician criterion is associated with patient code R-FP (record RB512); prefer female physician criterion is associated with code P-FP (record RB513) and require first available physician criterion is associated with criterion code R-FA (record RB514).
- FIG. 6 depicts a
tabular representation 605 of anexemplary patient database 600 suitable for use in thecentral server 200 of FIGS. 1 and 2. Specifically, the table 605 of FIG. 6 comprises a plurality of records R61 through R68, each record being associated with a respective patient'sname field 610,patient identifier field 620, patientcriterion code field 630, a “currently being treated for”field 640 and apast alerts field 650. - For each record R61 through R68, the patient's
name field 610 indicates the name of a particular patient; thepatient identifier field 620 indicates an insurance company, hospital or other identification number or code that uniquely identifies the patient; the patientcriterion codes field 630 indicates patient criterion information relating to preferred objective or subjective characteristics of a treating physician (e.g., fee structure, board certification and the like); the currently being treated forfield 640 indicates the current medical conditions (if any) that the patient is currently being treated for and thepast alerts field 650 indicates the medical conditions (or general health) that triggered previous alerts or other events. - A number of exemplary patient criteria appear in this database. The codes for patient criteria correspond to those for physician criteria, except that patient codes have either an “R” or “P” prefix. For example, the code for a board-certified physician is BC; the patient codes for board-certified physicians are R-BC and P-BC. Patient criterion codes with “R” prefixes indicate that the patient requires the criterion corresponding to this code. Patient criterion codes with “P” prefixes indicate that the patient prefers but does not require this criterion. Some patient criteria, such as requiring the response of the first available physician, do not have corresponding physician criteria codes.
- Entries in the patient
criterion codes field 630 may be determined not only by the patient, but, optionally, by the patient's family physician, insurance company or other entity. The currently being treated forfield 640 contains brief information about the patient's current medical conditions. A “general health” entry in this field indicates that the patient is not currently being treated for anything in particular, but is instead being monitored just in case any problems develop. In one embodiment of the invention, a patient's medical records are sent to a physician by providing the physician with a hyperlink or data path, such that the physician can access the files directly from a computer terminal connected to the internet or other computer network. - Record R66 of table 605 indicates that a patient Matt Smith is associated with an identifier number “678901”, criteria codes P-MP, P-U33 and P-BC, is currently being treated for “general health” (i.e., no particularized ailment) and lost consciousness during a past alert on Jan. 1, 1998. Record R67 of table 605 indicates that a patient Teun Van Vliet is associated with an identifier “789012”, criteria codes R-UH and P-L33, is currently being treated for “Arteriosclerosis” and has never been associated with an alert. Record R68 of table 605 indicates that a patient Ana Ng is associated with an identifier “890123”, criteria codes R-BS, P-BC and R-FP, is currently being treated for “Possible Pregnancy Complications” and has never been associated with an alert. Records R61 through R65 contain respective data relating to other patients.
- FIG. 7 depicts a table705, exemplary of
event database 700, suitable for use in the central server of FIGS. 1 and 2. Specifically, the table 705 of FIG. 7 comprises a plurality of records R71 through R74, each record being associated with arespective date field 710,case identifier field 720,patient identifier field 730,physician identifier field 740,event description field 750,outcome field 760, offers madefield 770 and offers acceptedfield 780. The offers madefield 770 and offers acceptedfield 780 include respective physician identifiers and compensation value offered sub-fields. - The
date field 710 indicates the date of a particular event. Thecase identifier field 720 identifies, by a unique case identifier, the particular event. Thepatient identifier field 730 andphysician identifier field 740 identify, respectively, the patient and physician involved in the event. Theevent description field 750 includes a description of the event. Theoutcome field 760 includes information defining the outcome of the event (e.g., the patient was admitted to a hospital, treated in a particular manner, administered a certain drug and the like). The offers madefield 770 include information identifying each physician to whom an offer of compensation in exchange for diagnostic services was made, and the amount of money offered for such services. The offers acceptedfield 780 includes information indicating which physician or physicians accepted the offer and at what compensation value they accepted the offer. Optionally, a “past alerts” field contains a record of previous alerts and is used to ascertain whether certain patients (or devices) are prone to false alarm events. - The offers made
field 770 and offers acceptedfield 780 are optionally used to improve the system accuracy in predicting physician demand and prices. For example, the system may determine that physician “596143”, an internist, regularly accepts offers $50 below the median offer for internists. In this scenario, offers to this physician may be reduced. By graphing acceptance rate against offer values, time of day and other factors, the system continually absorbs information relating to the contracting behavior of physicians, thereby refining estimates of demand and appropriate prices. - Record R71 of table 705 indicates that on Jan. 1, 1998 a case “678901A” involving a patient “678901” and a physician “123456” involved a loss of consciousness. A first physician “123456” was offered $180, a second physician “789012” was offered $200 and a third physician “406961” was offered $220 to accept the case. The first physician “123456” and the second physician “789012” accepted the case at the offered amount. The event resulted in an admission to a hospital for a narcotics overdose.
- Record R72 of Table 705 indicates that on Jan. 11, 1998 a case “505995A” involving patient “505995” and physician “567890” involved an event of acute high blood pressure and had an outcome of the patient being queried and found him to be exercising. A physician identified as “234567” was offered $375, a second physician identified as “567890” was offered $375 and a third physician identified as “961642” was offered $385 to take the case. The first and third physicians accepted the offers at the offer price.
- Record R73 of Table 705 indicates that on Feb. 14, 1998 case “381884A” involving patient “381884” and physicians “567890” and “234567” involved a tachycardia event with an outcome of hospital admission for the patient. Physician “567890” was offered $350 and
physician 234567 was offered $375 for taking the case. Both physicians accepted the offer at the respective offer price. - Record R74 of Table 705 indicates that on Mar. 15, 1998 case “567890A” involving patient “567890” and physician “234567” involved an event of acute high blood pressure and resulted in an emergency room administration of appropriate drugs and a release of the patient. A first physician “234567” was offered $350 and a second physician “567890” was offered $375 for taking the case. The first physician “234567” was subsequently offered $375 and then $400 for taking the case. Physician “234567” finally accepted the $400 offer price.
- FIGS. 8A and 8B depict a flow diagram of a patient care diagnosis delivery method suitable for use in the patient care diagnosis delivery system of FIG. 1. Specifically, the patient care
diagnosis delivery method 800 of FIGS. 8A and 8B is suitable for use within thecentral server 200 of the patient carediagnosis delivery system 100 of FIG. 1 and FIG. 2. - The
method 800 is initiated atstep 802. At step 804 a telemetry signal is received from a patient. As previously noted with respect to FIG. 1, the telemetry signal may comprise compressed or uncompressed physiological data without local analysis, compressed or uncompressed physiological data with a local analysis (i.e., including an alarm code), a control signal produced by the patient and, optionally, other data. - At step806 a determination is made as to the appropriate reaction of the patient care
diagnosis delivery system 100. In the case of compressed or uncompressed physiological data without local analysis, the data is analyzed to determine if patterns within the data are indicative of a present or pending (i.e., precursor indications of dysfunction) physiological dysfunction. This analysis may be conducted using one or more of a number of known data analysis techniques. In the exemplary embodiment, the analysis is conducted by comparing portions of the data to data profiles that have been determined to be indicative of such present or precursor physiological dysfunction. In the case of compressed or uncompressed physiological data with local analysis (e.g., alarm codes), the received alarm code is compared to thealert field 310 of the records within thereaction database 300. A favorable comparison to a record yields, from thesystem reaction field 320 of that record, the appropriate response to the received alarm code. It should be noted that the data profiles may be periodically updated or altered. - In the case of compressed data that has been compressed using a frequency transform compression scheme, the step of comparing the compressed data may be performed within the compressed data domain (i.e., frequency domain) by performing the following steps: transforming, using a frequency domain transform function, the data representative of the physiological parameter; and correlating, against each of a plurality of frequency domain profiles, the transformed data representative of the physiological parameter, where each of the frequency domain profiles is associated with at least one pathological anomaly.
- A control signal produced by the patient is also reacted to in a predefined manner based upon the signal. For example, a control signal indicative of pending patient exercise indicates to the
central server 200 that a subsequent increase in blood pressure is to be expected, though the system will still react appropriately to data indicative of cardiac arrest. - At step808 a query is made as to whether the determination at
step 806 indicates that the received telemetry signal should be ignored. If the query atstep 808 is answered affirmatively (e.g., elevated blood pressure during exercise), then the method proceeds to step 809 where, optionally, an entry in an error log (not shown) is made and the method proceeds to step 804 where the next telemetry signal is received. If the query atstep 808 is answered negatively, then themethod 800 proceeds to step 812. Optionally, if the query atstep 808 is answered negatively, then themethod 800 proceeds to step 810, where an ambulance is dispatched to the patient's location, if needed. The patient's location may be determined with respect to a known location or, in the case of apatient telemetry device 120 associated with aGPS locator 135, GPS data within the received signal will provide location information. - At
step 812 one or more experts are selected to provide diagnostic services. The expert(s) selected to provide such services are selected based upon thephysician criterion 500A of FIG. 5A andpatient criterion 500B of FIG. 5B, as will be discussed in more detail below with respect to FIGS. 9A and 9B. - Briefly, the above-mentioned criteria result in a patient preference ranking of physicians, as modified by patient insurance company requirements, according to medical specialty, gender, fee structure and the like. Patient preference ranking is based upon a patient criterion within
patient criterion database 500B. Physician preference ranking is based upon thephysician criterion database 500A. Insurance company preference ranking is based upon insurance company information within either of thepatient criterion database 500B orphysician criterion database 500A or other database. For example, insurance companies may have negotiated or predefined contractual arrangements with individual physicians, physician groups and/or hospitals or hospital systems. In the case of a preferred hospital system or other medical facility, an insurance company may have preferred providers within that facility and these providers may or may not be reflected in the patient preference rankings. However, since the insurance company associated with a particular patient is likely to be the one paying the bill, it is prudent to adapt the selection of experts to the insurance company preference ranking to the extent possible. The specialty of an expert selected to provide diagnostic information may be dependent upon, e.g., the received telemetry signal from the patient and/or the patient's medical data or history. In the case of an emergency situation or emergent event, it may be necessary to immediately secure some expert opinion, regardless of physician specialty or other preferential ranking. These criteria or other criteria may be combined to produce a combined ranking that may be weighted in a manner tending to favor insurance company preferences, patient preferences, physician preferences and other factors as deemed appropriate. - At
step 814 at least a portion of the patient's data is provided to the selected expert or experts. The patient data may comprise, e.g., the received telemetry signal, the patient's medical history and any other data appropriate or necessary to the selected experts in rendering their diagnosis. - At
step 816 the diagnoses from the expert or experts is/are received. Themethod 800 then proceeds tooptional step 818, where an aggregated diagnosis is formed using a plurality of diagnoses rendered by a respective plurality of experts. The aggregated diagnosis forms a “most likely” diagnosis that is used to determine an appropriate course of treatment for the patient in one embodiment of the present invention. - Forming an aggregate diagnosis may, in one embodiment, comprise selecting the diagnosis that the majority of the experts agree on. For example, if 3 out of 5 experts recommend the patient proceed to the emergency room immediately for certain treatment while the other two experts recommend 24 hours of bedrest before a trip to the emergency room is determined to be necessary, the system may select the diagnosis of the majority and instruct the patient to immediately proceed to the emergency room or summon an ambulance to the patient's location. In such an embodiment the patient may only be informed of the majority opinion selected by the system or may be provided with the two alternate diagnoses and asked to select which diagnosis he wants to proceed according to. Alternatively, at the time of the event the patient may be informed of the majority diagnosis but may at a subsequent time be informed of any alternate diagnosis that was not selected.
- In an aggregate diagnosis embodiment the experts involved in a particular case may render independent diagnoses independently of one another or may be allowed (or required) to confer with one another in rendering the aggregate diagnosis. For example, the experts may be able to communicate through the
internet 170 ofsystem 100 in order to confer or share opinions in rendering the aggregate diagnosis. In an embodiment where the experts are each independently rendering a diagnosis which is aggregated with the other diagnoses by the system, the experts may or may not be aware that their diagnosis is part of an aggregate diagnosis. - An aggregate diagnosis embodiment may help instill more confidence in the patient and may shield any one individual expert from sole liability for rendering a remote diagnosis. An aggregate diagnosis may also introduce quality assurance into the system of the present invention. Another form of quality assurance may be to have another expert review or approve a diagnosis before it is acted upon by the system. Such review or approval may be performed (i) in every case, (ii) in random or selected cases, and/or (iii) for cases involving experts who are new to the system or against complaints or grievances have been lodged.
- After receiving an expert diagnosis (step816) or forming an aggregated diagnosis (step 818), the
method 800 proceeds to step 819, where the diagnosis is communicated to the patient, and to step 820, where the expert or experts providing the diagnosis is compensated. The expert compensation may be based upon one of, perstep 822, a flat rate, an hourly rate, and a per event rate. Optionally, the compensation may be based upon the time of day (e.g., higher compensation between 10:00 PM and 8:00 AM) or upon physician availability. Optionally, the compensation may be adjusted in the case of a complex event or an especially favorable outcome. A complex event comprises, e.g., an event implicating several specialties or sub-specialties or otherwise causing the expert being so compensated to devote a significantly higher level of time and/or effort to a particular event. A favorable outcome comprises an especially efficient outcome (either monetarily or physiologically) or other superb outcome based upon, e.g., an especially high level of skill applied to an event by an expert being compensated. In emergent situations, an expert may incur a “lost opportunity” cost by handling the case (i.e., failing to gain a greater compensation for another activity so that an emergency event is properly handled). In such cases an additional compensation may be provided. - Compensation may be determined by a rules-based method where, for example, the rules for determining a compensation to offer or an adjustment to previously offered or accepted compensation is determined by applying predetermined rules. Such rules may be programmed into the software running on the system of the present invention or stored in a database utilized by the system. For example, compensation may start from a base amount and may be adjusted from this amount based on the circumstances of a case. Circumstances that may be taken into consideration may include, for example, (i) a previously established rate between the expert and the system, (ii) certain qualifications or criteria associated with the expert, (iii) the severity or urgency of the patient's potential condition, and (iv) how many other experts are available to render a diagnosis. The adjustment of the base amount may be an upward or downward adjustment in such an embodiment. Alternatively, an amount of compensation may be determined, for example, based on a formula that takes certain variables (e.g. qualifications of expert, expert's history of accepting offers) into account when calculating a compensation amount to offer or an adjustment to a compensation amount.
- Returning now to FIG. 8B, at
step 824 thepatient database 600,physician database 400, andevent database 700 is updated. Themethod 800 then proceeds to step 804 to await the next telemetry signal from a patient. - It should be noted that the above-described
method 800 is applicable to the situation where many cases are handled at once. That is, where many patients are associated with patient telemetry devices providing a substantially continuous flow of information to the server. - FIGS. 9A and 9B depict a flow diagram of an expert selection method suitable for use in the patient care delivery method of FIGS. 8A and 8B. Specifically, the
expert selection method 900 of FIGS. 9A and 9B is suitable for use in implementing, e.g., step 812 of the patientcare delivery method 800 of FIGS. 8A and 8B. - The
expert selection method 900 is initiated atstep 902 and proceeds to step 904. Atstep 904 patient data and patient criteria codes for the patient transmitting the telemetry signal received atstep 804 are retrieved from, respectively,patient database 600 andpatient criteria database 500B. - At step906 a determination is made as to the appropriate and available experts based upon the received telemetry signal and the retrieved patient data. Specifically, the determination made at
step 806 is used to define which expertise or specialty is required to render a diagnosis for the event. Additionally, having determined which expert specialty is required, thephysician database 400 is accessed to determine which physicians associated with the appropriate specialty are available (per availability field 460). - At step908 a query is made as to whether the patient requires that a first available physician be contacted (a code R-FA in the patient
criteria code field 630 of the patient's record in the patient database 600). Certain alarm codes may also indicate to the system that a first available physician is to be contacted. A code R-FA indicates that a patient is either medically compromised to such an extent that immediate intervention or at least a diagnosis from a physician is required. Therefore, in view of the immediate need for such a diagnosis from an expert, it is imprudent to perform any sorting or preferential arranging of potential experts. Rather, it is most prudent to simply offer to all appropriate and available physicians the “job” of rendering a diagnosis for this event. If the query atstep 908 is answered affirmatively, then themethod 900 proceeds to step 909. If the query atstep 908 is answered negatively, then themethod 900 proceeds to step 910. - At
step 909 an offer is sent to all appropriate and available physicians as determined duringstep 906. That is, each physician or expert having the appropriate expertise to render a diagnosis for the present event is offered the chance to render such a diagnosis in exchange for compensation. Themethod 900 then proceeds to step 924 where it is exited (e.g., themethod 800 resumes control at step 814). - At
step 910 the patient criteria codes are compared to the physician criteria codes of the appropriate and available experts or physicians. That is, at step 910 a comparison is made between the contents of the appropriate patientcriteria code field 540 of the patient criteria table 500B and the physiciancriterion code field 520 of the physician criteria table 500A to determine if any of the physicians that are appropriate and available have conflicting criterion codes. For example, in the case of a patient criteria code indicative of a requirement for a male physician having a fee structure in the lower 33rd percentile, female physicians and those physicians having fee structures in the middle and upper 33rd percentile would conflict. Atstep 912 those physicians having conflicting criterion are eliminated from consideration for an offer of compensation in exchange for diagnostic services. Themethod 900 then proceeds tooptional step 914 or to step 916. - At
optional step 914 those physicians having criterion conflicting with the patient's insurance company are eliminated from consideration of receiving an offer of compensation in exchange for their diagnosis. That is, those physicians deemed by the patient's insurance company to be undesirable, too expensive, not included within the health plan or network, in competition with the patient's insurance company's preferred physicians or otherwise deemed unsuitable by the insurance company are eliminated from consideration of an offer (unless later needed, per step 918). - In addition to the expert and patient criteria stored in patient criteria table500B and physician criteria table 500A, respectively, the geographic location of the patient and the geographic are the physician is licensed to practice in may be taken into consideration by the
system 100. For example, only doctors that are licensed to practice in Virginia may be selected for a case of a patient located (or whose state of residence is) Virginia. The areas a physician is licensed to practice in may be stored in the physician criteria table 500A or otherwise accessed by thesystem 100. The patient's location may be determined viaGPS locator 135 or the patient may be queried for his current location. If the patient's area of residence is a relevant factor, the residence may be stored, for example, in the patient criteria table 500B. In other embodiments a physician that is not licensed to practice in the patient's are may be contacted by the system but may need to work with or through another physician that is licensed in the patient's area to render the diagnosis (e.g. local physician may need to approve diagnosis). - At
step 916 those experts and/or physicians determined to be appropriate and available (per step 906) and not eliminated from consideration due to conflicting criterion with a patient (step 912) or insurance company (step 914) criterion list are preferentially sorted per the patient's criteria. That is, those experts still remaining are sorted according to attributes deemed by a patient to be more favorable. For example, in the case of a patient criteria indicative of a preference for a male physician, and a preference for a board certified physician, physicians meeting these preferred criteria will be preferentially considered to physicians not meeting these criteria. Thus, the outcome ofstep 916 is a preferentially sorted list of physicians. Physicians near the top of the list are more preferable from the patient's perspective to those physicians near the bottom of the list. This does not mean that the physicians near the bottom of the list are unacceptable; rather that the physicians near the bottom of the list simply fail to meet or to confirm to the patient's criteria as well as those physicians near the top of the list. Themethod 900 then proceeds to step 918. - At step918 a query is made as to whether a minimum number of physicians or experts are remaining. That is, a query is made as to whether a predetermined minimum number of physicians are remaining within the pool or group of those physicians under consideration for an offer. The predetermined number may comprise one, three or any appropriate number. In the interest of ensuring that an expert diagnosis is rendered in a timely manner, it may be the case that the predetermined minimum number of physicians being sent an offer at any one time should be low, e.g., five. Thus, if the query at
step 918 is answered negatively (e.g., only four physicians in the case of a five physician minimum avoiding elimination for consideration of an offer), then themethod 900 proceeds to step 920. If the query atstep 918 is answered affirmatively, then themethod 900 proceeds to step 922. - At
step 920 the criteria of acceptability is widened such that more physicians are included within the list of physicians being considered. For example, the criteria may be widened to include physicians of any gender, regardless of patient preference. Themethod 900 proceeds fromstep 920 to step 912. - At
step 922 an appropriate respective offer of compensation in exchange for a diagnosis for the particular event triggered by the telemetry signal received atstep 804 is sent to each of the remaining physicians. Themethod 900 then proceeds to step 924 where it is exited (e.g.,method 800 is re-entered at step 814). - It should be noted that in the event of no experts indicating an acceptance of their respective offers, additional offers may be transmitted at the same or an enhanced compensation rate to the initial experts selected. Alternatively, some or all of the selected experts are replaced by alternate experts and a new round of offers is made.
- FIG. 10 depicts a flow diagram of an offer processing method suitable for use in the expert selection method of FIGS. 9A and 9B. Specifically, FIG. 10 depicts a flow diagram of a
method 1000 for processing offer requests or for sending offers to remaining physicians suitable for use in, e.g., step 922 of theexpert selection method 900 of FIGS. 9A and 9B. - The
offer processing method 1000 is initiated atstep 1002 and proceeds to step 1004, where a request to send an offer to one or more physicians is received. - At step1006 a determination is made as to the appropriate compensation level to be associated with each of the one or more offers to be made to physicians or other experts. An appropriate compensation level may be determined with respect to, per
box 1008, historical data, current demand, insurance contracting, other contracts or other inducements. - Historical data comprises data indicative of past offers that have been accepted or rejected by a particular physician. The historical data may be further refined into acceptance and rejection data associated with particular offers on particular days of a month (e.g., weekends or week days) and other historical factors relating to the order acceptance/rejection history of a physician. The offers made
field 770 and offers acceptedfield 780 of theevent database 700 provides useful historical data that may be correlated to individual physicians or experts. After determining the appropriate offer levels, themethod 1000 then proceeds to step 1010. - Current demand comprises an indicator of an amount of demand for diagnostic services for a particular specialty. For example, during a heat wave compounded by an electrical failure in a city requiring air conditioning it may be the case that current demand for cardiologists and other specialists engaged in the diagnosis and/or treatment of heat-related conditions may be quite high. In this case, such an expert may be extremely busy and more likely to reject an offer to render a diagnosis in the absence of a sufficiently large monetary inducement.
- An insurance contract binding a particular physician to the treatment of a patient carrying that insurance at a set contract rate may be honored. Therefore an offer to such a physician may include the appropriate contract compensation rate. However, by pre-arrangement, a patient availing himself or herself of the system of the present invention may indicate that an additional inducement is to be offered (paid by the patient) to a physician beyond any contract rate negotiated by an insurance company. For example, a person of sufficient means, but insufficient cardiac strength, may offer an additional cash inducement to the hospital or other medical facility or health care provider such that an offer made to a physician should include the insurance contract rate plus the additional cash inducement offered by the patient to arrive at a “bump-up” offer price. Other contractual considerations may include secondary insurance or “gap” insurance in the case of senior citizens or others availing themselves of Medicare and/or Medicaid. In such situations where insurance company contract payments are relatively low, it behooves the patient to increase the level of compensation to some extent such that it is likely a physician will accept the offer of compensation and render the necessary diagnosis.
- At
step 1010 the respective offers determined atstep 1006 are sent to the respective physicians or experts. Themethod 1000 then proceeds to step 1012. - At
step 1012 some or all of the telemetry data, medical records and patient preferences are sent to the physicians or experts receiving offers. The purpose of this data transfer is primarily to provide the expert with sufficient information to make a decision as to whether or not to take the case. However, if all of the patient data is sent, then it is possible that the physician may accept and render an opinion at substantially the same time. Themethod 1000 then proceeds to step 1013. - At
step 1013 themethod 1000 waits for a predefined maximum period of time to receive one or more “accept” signals which are received from physicians or experts to whom offers have been sent. That is, a physician may have received an offer via hisphysician terminal device 110, e.g., a personal digital assistant (PDA) or other portable communication device proximate to the physician. Upon reviewing the offer and, perhaps, some initial patient data, the physician may decide that time allows him or her to render a diagnosis to the patient. In such a situation the physician signals to thecentral server 200 his or her acceptance of the offer by sending a page or otherwise communicating with thecentral server 200. For example, upon receiving an offer via aphysician terminal device 110, a physician may sit down at a computer terminal and access the server via, e.g., the internet, thereby directly accepting the offer. In the case of a physician accepting an offer via logon to the server using the internet, the dissemination of telemetry data, medical records and patient preferences indicated atstep 1012 is performed by the physician downloading this information to his local computing device. Upon receiving at least one “accept” signal within the predefined maximum period of time, or the expiration of that time without receiving an accept signal, themethod 1000 proceeds to step 1014. - At step1014 a query is made as to whether any “accept” signals have been received. If the query is answered affirmatively, then the
method 1000 proceeds to step 1016. If the query is answered negatively, then themethod 1000 proceeds to step 1015. - At
step 1015 the offers are increased. For example, each offer may be increased by a fixed amount (e.g., $25), an amount determined as a percentage (e.g., 15%) of the existing offer or some other amount. It should be noted that an increased offer may be made to less than the entirety of physicians receiving an offer. For example, if one physician is known to typically accept offers above a certain amount, that physician may be provided with a second higher offer, while other physicians may receive second offers having unchanged (or minutely changed) offer amounts. Themethod 1000 then proceeds to step 1010. - At step1016 a query is made as to whether the patient associated with the present event is also associated with a code R-FA (requires first available physician). If the query at
step 1016 is answered affirmatively, then themethod 1000 proceeds to step 1018. If the query atstep 1016 is answered negatively, then themethod 1000 proceeds to step 1020. - At
step 1018, since the patient requires a first available physician, the first acceptance of a physician is confirmed. That is, regardless of patient preferences beyond those already used to screen the physicians to whom offers were made, the first physician indicating his or her acceptance of an offer is confirmed by thecentral server 200. Confirmation of an offer by thecentral server 200 entails indicating, in some manner, to the physician that the physicians diagnosis is required, that compensation per the offer will be made for that diagnosis, and that the physician should now be rendering that diagnosis. - At
step 1020, since the patient does not require the first available physician, at least one acceptance is confirmed based upon the preferential sorting of the physicians to whom offers were made. That is, in the case of a patient having an insurance company that will pay for the services of one physician to render a diagnosis for an event, the one accepting physician meeting all or most of the patient's preferences will be confirmed as the physician or expert involved in the event. It should be noted that in the case of the patient requiring two or more expert diagnosis to be rendered, the two or more physicians most closely conforming to the patient's preferences as indicated by thepatient criterion database 500B will be confirmed. - At step1022 a confirmation signal is sent to the one or more physicians or experts to be confirmed. The confirmation signal may be sent via the physician terminal device 110 (e.g., pager, cellular or terrestrial telephone link, computer network, satellite network or any other communications medium).
- At
step 1024 the necessary medical history, current condition and other data associated with the patient and the present event is transmitted to thephysician terminal device 110. It should be noted that this step comprises, essentially, the same functionality described above with respect to step 814 of themethod 800 of FIGS. 8A and 8B. As such,step 814 may be skipped if themethod 1000 of FIG. 10 is being called as, e.g., a sub-method of themethod 800 of FIGS. 8A and 8B. Themethod 1000 then proceeds to step 1026 where it is exited (e.g., theexpert selection routine 900 of FIGS. 9A and 9B is reentered at step 924). - FIG. 11 depicts a flow diagram of a patient care
diagnosis delivery method 1100 suitable for use in the patient carediagnosis delivery system 100 of FIG. 1. In the embodiment of FIG. 11, the telemetry unit associated with a patient includes at least rudimentary diagnostic capability such that the alarm signal transmitted by the telemetry device includes a particular diagnosis that is associated with an element of thealert field 310 of thereaction database 300 of FIG. 3. For example, in the case of apatient telemetry device 120 determining that the patient is suffering ventricular fibrillation, an alert message indicating ventricular fibrillation is transmitted as an alarm signal to thecentral server 200. - The patient care
diagnosis delivery method 1100 is initiated atstep 1102 and proceeds to step 1104, where an alarm signal is received from a patient telemetry device. Themethod 1100 then proceeds to step 1106. - At step1106 a determination is made as to the appropriate reaction to the alarm signal using the
reaction database 300. This determination includes determining an appropriate type of position or expert and whether an ambulance is required. For example, in the case of a received alarm signal indicative of ventricular fibrillation, an appropriate system reaction (persystem reaction field 320 of reaction database 300) comprises summoning an ambulance to pick up the patient and bring the patient to a nearby medical treatment facility and offering the case to physicians or experts comprising cardiologists or heart specialists. - At step1108 a query is made as to whether an ambulance is required. If the query at
step 1108 is answered affirmatively, then themethod 1100 proceeds to step 1110 where an ambulance is summoned. The method then proceeds to step 1112. If the query atstep 1108 indicates that an ambulance is not required, then themethod 1100 proceeds directly to step 1112. - At step1112 at least one expert is alerted to the event associated with the received alarm, the patient's medical history, a description of the patient's current state and an offer of compensation is then made to the at least one expert in exchange for taking the case (i.e., rendering a diagnosis).
- At
step 1114 an “accept” or “decline” signal is received from the at least one expert or physician alerted at step 1112. Themethod 1100 then proceeds to step 1116. Atstep 1116 at least one of the physicians from the pool or group of physicians or experts indicating an acceptance of the case is selected. Themethod 1100 then proceeds to step 1118. - At step1118 a confirmation signal is sent to the accepting expert or experts. At this point the accepting and confirmed physician or expert has taken the case and is expected to render an expert diagnosis using the data transmitted at step 1112 in exchange for the compensation offered at step 1112. The
method 1100 then proceeds to step 1120 where it is exited. - An example of an application of the invention will now be described with respect to a cardiac patient. Specifically, it is assumed that the cardiac patient is at a medical facility or at home and that a patient telemetry device monitors the patient physiological parameters including heart activity via, e.g., an electrocardiogram (ECG) function. The ECG continuously monitors the patient's heart and the resulting data is sent to the
central server 200 as part of a compressed data stream transmitted via apatient telemetry device 120. - The
central server 200 receives the data and analyzes the data to detect any aberrant data patterns, i.e., data patterns indicative of a cardiac anomaly. When such a pattern is detected, the computer compares it with pre-defined malignant patterns (i.e., data profiles) to ascertain whether or not the pattern requires intervention on the part of the patient or the hospital. If the pattern of the received data describes a malignant aberrance such as heart palpitations or arrhythmia, a signal is sent to the patient (to apprise him or her of the situation), and one or more cardiologists are selected to receive an offer according to both patient and physician criteria, as previously described. If a more serious condition were detected, such as a cardiac arrest, the system would summon an ambulance to the patient's location—which could be determined with a GPS unit in thepatient telemetry device 120 and also contact a cardiologist. If the pattern observed by the system did not match either a benign or pathological pattern, the system would notify the patient and provide a phone number to call for further assessment of the situation. - The
physician terminal device 110 in the example comprises a Personal Digital Assistant (PDA) that is used in conjunction with wireless data transfer. A plurality of experts meeting the appropriate criteria are paged and provided with the patient's current condition, medical records and respective monetary offers. An expert who accepts the case indicates that acceptance via the PDA, which provides two-way paging capability. Depending on the case, the expert communicates with thecentral server 200 via the PDA, a mobile phone, a computer or some combination thereof. When the expert completed the services required, he or she would indicate this by way of the PDA and a financial account associated with the expert is credited with the amount offered. - If an expert takes too long in responding, the system might make a second or third offer. However, since a large financial risk is associated with the expert attempting to “game” the system (i.e., wait for a, presumably, higher second or third offer), it is likely that the expert will respond quickly if the expert can practicably handle the case. It is noted that, in effect, the plurality of experts receiving offers are in competition with each other. The first (and possibly second) expert accepting the offer will likely exclude from contention the expert trying to elicit a larger second offer.
- Advantageously, the invention provides a system that will alert physicians and/or patients when the patient's health takes a turn for the worse. Whether or not a patient lives through a cardiac arrest is often determined by how soon he receives treatment. By cutting the medical response time to the absolute minimum, the inventive system will save lives and reduce impairments to those lives.
- In another embodiment of the invention, the expert utilizes the internet to retrieve patient information and render a diagnosis. When contacted with an offer, the expert goes to a web site, types in his expert ID, the patient's ID (received with the offer) and is immediately provided with the patient's records and current condition.
- In another embodiment of the invention, the
central server 200 sends case offers to hospitals, which then act as clearinghouses for the doctors employed there. For example, the server receives an alarm signal from a monitored patient and sends the offer to one or more hospitals, which then have the option of taking the case, depending on how busy they are. Essentially, the invention operates as a “traffic controller” for hospitals. In this embodiment, a medical facility is associated with at least one expert and comprises infrastructure suitable for remediating physiological dysfunction. The system procures a diagnosis from experts via the facility by transmitting offer(s) to the facility for subsequent communication to the appropriate experts. The facility may adapt the offer (e.g., increase the amount) to ensure that an ambulance delivers a patient to the facility where the physician has admitting rights. The adaptation of the offer may be performed in response to a level of facility utilization and a level of physiological dysfunction urgency associated with said offer. That is, in response to a level of facility utilization being above a threshold level and a level of physiological dysfunction urgency being below a threshold level, the offer may be adapted to cause the patient to be delivered to an alternate or affiliated medical facility for processing. - A plurality of medical facilities may be operably linked together by a central server via a communications system such that the central server, in response to an offer received from a system controller, determines which one of the plurality of medical facilities should receive the offer and communicates the offer to the determined medical facility. Additionally, the determination of the central server may be made using at least one of the following criteria applied to said medical facilities: proximity to a patient, general facility utilization level, appropriate department utilization level (e.g., intensive care unit, trauma unit, emergency room and the like), a level of expertise in treating an indicated physiological dysfunction, possession of equipment suitable for treating the indicated physiological dysfunction, membership in a predetermined health care provider group and participation in a predetermined insurance plan.
- In another embodiment of the invention, the invention allows at least voice communication between the remote physician and the patient. The physician gives instructions to the patient on how best to act until an ambulance arrives. If the patient is unconscious, the physician may interact with a bystander to remotely help the patient. Additionally, the physician may optionally administer drugs remotely if a
patient telemetry device 110 is equipped with adrug dispensing unit 135. - In one embodiment of a compensation scheme of the present invention, the expert may enter into an agreement with the system wherein the expert is paid a previously established compensation amount on a periodic basis in exchange for agreeing to accept a predetermined minimum number of cases during each compensation period. For example, a physician may agree to accept ten cases per week in exchange for receiving $1000 on a bi-weekly basis. In such an agreement there may be a further provision that the expert will receive an additional compensation for accepting more than the minimum number of cases required under the agreement. In such an embodiment an expert may still be selected and offered a case on a real-time basis (i.e. as a case is recognized by the system) since the expert may not be available at a time when a patient is in need the system may contact such an expert and await an accpetance in a method similar to those described above. However, unlike in some of the previously described embodiments, in this embodiment the offer to the expert would not necessarily include a compensation amount. Although the offer could include a reminder of the periodic compensation amount, the portion of the periodic compensation amount that this case may be worth to the expert, or how many cases the expert still has to accept within the current period in order to earn the periodic compensation amount.
- FIG. 13 depicts table1300, an exemplary illustration of a
compensation agreement database 800, which could be used bysystem 100 to track compensation agreements with experts in the embodiment where an expert is compensated by a predetermined amount on a periodic bases. Table 1300 comprises exemplary records 1301 through 1301. Each record contains data stored in anagreement identifier field 1310, aphysician identifier field 1320, acompensation amount field 1330, acompensation periodicity field 1340, a minimum case perperiod field 1350, a bonuscase amount field 1360, and a current cases takenfield 1370. - The
agreement identifier field 1310 stores an identifier that uniquely identifies an agreement between an expert andsystem 100. Thephysician identifier field 1320 stores an identifier that uniquely identifies a physician participating in thesystem 100 who corresponds to each respective agreement identifier. Thecompensation amount field 1330 stores the compensation amount corresponding to each respective agreement identifier, which the corresponding physician will receive in exchange for accepting cases through thesystem 100. Although monetary compensation amounts are illustrated in the figure, the compensation amount could comprise other forms of compensation. For example, in exchange for participating in thesystem 100 an expert could receive (i) a reduction in insurance premiums; (ii) points or credits in a club or professional association; (iii) alternate currency such as frequent flier miles; (iv) continued access to a service, establishment, or product; or (v) public recognition for donating time to pro bono work. Such alternate forms of compensation, of course, may be implemented in all embodiments of the present invention. - Returning now to table1300, the
compensation periodicity field 1340 stores the time period corresponding to each agreement identifier during which the expert must accept cases in order to qualify for the compensation amount. The minimum cases perperiod field 1350 stores the minimum number of cases corresponding to each agreement identifier which an expert has agreed to accept in order to qualify for the compensation amount. Typically each case that an expert accepts will count as a single case. However, it is contemplated that an expert may receive credit towards the minimum number of cases requirement equaling more than one case for accepting certain cases. For example, if a case is particularly complicated or the resolution of which takes an inordinately long amount of time, the expert may receive a multiple case credit for accepting that case. Similarly, if thesystem 100 is experiencing difficulty in obtaining an acceptance from experts for a particular case, thesystem 100 may transmit an offer to an expert communicating that if the expert accepts this particular case it will count as two or more cases towards meeting his minimum number of cases requirement under the agreement. Although the term “cases” has been used it should be understood that a case may comprise a single event requiring a diagnosis or multiple events associated with the same patient and the same condition that may require the expert to communicate with the system and/or patient in more than one instance. - Returning again to table1300, the bonus
case amount field 1360 stores a bonus compensation amount that corresponds to each agreement identifier. A bonus compensation amount is an amount of compensation that an expert is to receive for each case that he accepts over the minimum number of cases required under his agreement. Thus, for example, Record R1301 illustrates that if physician “123456” accepts seven cases in a given week he will receive a total compensation amount of $600 for that week ($500 compensation amount for six required cases+$100 bonus amount for one non-required case). Of course rather than receiving extra compensation for accepting cases beyond the minimum number of cases the expert may be rewarded in other ways. For example, Record 1302 of table 1300 illustrates that physician “789012” will receive credit towards the minimum number of cases for the next period for any case he accepts beyond the minimum number of required cases in a current period. - The current cases taken
field 1370 stores the updated amount of cases that have been accepted to date for a given period by a physician corresponding to an agreement identifier. This field may be used by thesystem 100, for example, to determine whether to (i) contact a physician with a current case; (ii) remind a physician regarding how many more cases he is still required to accept for the current period; or (iii) to provide the physician with compensation for the current period and, if so, what the compensation amount should be. For example, a physician may not agree to have any offers for cases transmitted to him once he has accepted the minimum number of cases so if the number of cases accepted is equal to the minimum number of cases for a given agreement, the system may remove the physician from the pool of possible physicians to contact for a given case. Similarly, thesystem 100 may take into consideration whether a particular physician has met his minimum number of cases requirement and would thus require a bonus compensation amount for accepting the current case (and, perhaps, what that bonus compensation amount is) before selecting that physician to contact for a current case. - If an expert does not meet his minimum number of cases for a given period he may be penalized in a variety of methods. For example, the physician may have (i) his compensation amount for the period reduced, (ii) his entire compensation for the period forfeited, or (iii) the number of cases under the minimum number of cases for the current period added as additional required cases to a subsequent period.
- In another embodiment of the present invention the experts may not be contacted by the system with offers for available cases. Instead, the experts may contact the system and view available offers when the experts are available to provided diagnoses. Of course, such an embodiment may be combined with an embodiment where the experts are contacted by the system. For example, the system may select and contact experts as described above each time a patient is determined to be in need of help. However, while the system is awaiting responses from the contacted experts the case will be made available for consideration and acceptance by other experts (e.g. on a website of the system).
- Although various embodiments which incorporate the teachings of the present invention have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that still incorporate these teachings.
Claims (51)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/893,495 US20010051765A1 (en) | 1999-03-31 | 2001-06-28 | Patient care delivery system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/282,132 US6302844B1 (en) | 1999-03-31 | 1999-03-31 | Patient care delivery system |
US09/893,495 US20010051765A1 (en) | 1999-03-31 | 2001-06-28 | Patient care delivery system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/282,132 Continuation-In-Part US6302844B1 (en) | 1999-03-31 | 1999-03-31 | Patient care delivery system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20010051765A1 true US20010051765A1 (en) | 2001-12-13 |
Family
ID=23080238
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/282,132 Expired - Lifetime US6302844B1 (en) | 1999-03-31 | 1999-03-31 | Patient care delivery system |
US09/893,495 Abandoned US20010051765A1 (en) | 1999-03-31 | 2001-06-28 | Patient care delivery system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/282,132 Expired - Lifetime US6302844B1 (en) | 1999-03-31 | 1999-03-31 | Patient care delivery system |
Country Status (1)
Country | Link |
---|---|
US (2) | US6302844B1 (en) |
Cited By (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020013538A1 (en) * | 1997-09-30 | 2002-01-31 | David Teller | Method and apparatus for health signs monitoring |
US20030093299A1 (en) * | 2001-10-25 | 2003-05-15 | Siemens Aktiengesellschaft | Method and system for providing medical consulting services, with automatic remuneration to the service provider |
US20030171955A1 (en) * | 2002-03-07 | 2003-09-11 | Werblin Theodore Paul | Method and system for implementing and tracking cost-saving measures in hospitals and compensating physicians |
EP1352608A2 (en) * | 2002-03-19 | 2003-10-15 | Colin Corporation | Diagnosis communication method |
US20030204413A1 (en) * | 2002-04-29 | 2003-10-30 | Riff Kenneth M. | Personalization software for implanted medical device patients |
US20040259494A1 (en) * | 2003-06-23 | 2004-12-23 | Cardiac Pacemakers, Inc. | Systems, devices, and methods for selectively preventing data transfer from a medical device |
US20060089538A1 (en) * | 2004-10-22 | 2006-04-27 | General Electric Company | Device, system and method for detection activity of persons |
US20060143053A1 (en) * | 2001-07-31 | 2006-06-29 | Van Rensburg Frederick R | Insurance product |
US20070150372A1 (en) * | 2005-12-19 | 2007-06-28 | Roy Schoenberg | Vendor and Consumer Matching |
US20080065414A1 (en) * | 2006-09-08 | 2008-03-13 | Roy Schoenberg | Connecting Consumers with Service Providers |
US20080133511A1 (en) * | 2006-09-08 | 2008-06-05 | American Well Inc. | Connecting Consumers with Service Providers |
US20080166992A1 (en) * | 2007-01-10 | 2008-07-10 | Camillo Ricordi | Mobile emergency alert system |
US20090055320A1 (en) * | 2007-08-22 | 2009-02-26 | Georg Goertler | System and method for providing and activating software licenses |
US20090076852A1 (en) * | 2007-08-22 | 2009-03-19 | Marc Pierson | System and method for an automated patient controlled system of health care provision and patient monitoring using personal health records |
US20090089090A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Tracking the availability of service providers across multiple platforms |
US20090089084A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Auctioning Provider Prices |
US20090089097A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Identification of Health Risks and Suggested Treatment Actions |
US20090089098A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Identifying Clinical Trial Candidates |
US20090089147A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Provider supply & consumer demand management |
US20090089074A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Identifying Trusted Providers |
US20090089096A1 (en) * | 2007-10-01 | 2009-04-02 | American Well Systems | Documenting Remote Engagements |
US20090089086A1 (en) * | 2007-10-01 | 2009-04-02 | American Well Systems | Enhancing remote engagements |
US20090112623A1 (en) * | 2007-10-22 | 2009-04-30 | American Well Systems | Connecting Consumers with Service Providers |
US20090113312A1 (en) * | 2006-09-08 | 2009-04-30 | American Well Systems | Connecting Providers of Legal Services |
US20090138317A1 (en) * | 2006-09-08 | 2009-05-28 | Roy Schoenberg | Connecting Providers of Financial Services |
US20090150252A1 (en) * | 2007-12-10 | 2009-06-11 | American Well Inc. | Connecting Service Providers And Consumers Of Services Independent Of Geographical Location |
US20090254361A1 (en) * | 2008-04-07 | 2009-10-08 | American Well Inc. | Continuity of Medical Care |
US20090262919A1 (en) * | 2008-04-18 | 2009-10-22 | American Well Inc. | Establishment of a Telephone Based Engagement |
US20090313076A1 (en) * | 2008-06-17 | 2009-12-17 | Roy Schoenberg | Arranging remote engagements |
US20090319296A1 (en) * | 2008-06-17 | 2009-12-24 | Roy Schoenberg | Patient Directed Integration Of Remotely Stored Medical Information With A Brokerage System |
US20100094659A1 (en) * | 2007-10-01 | 2010-04-15 | American Well Inc. | Consolidation of Consumer Interactions within a Medical Brokerage System |
US7746218B2 (en) | 2004-08-02 | 2010-06-29 | Hill-Rom Services, Inc. | Configurable system for alerting caregivers |
US20100222649A1 (en) * | 2009-03-02 | 2010-09-02 | American Well Systems | Remote medical servicing |
US20100293007A1 (en) * | 2009-05-18 | 2010-11-18 | Roy Schoenberg | Provider Decision Support |
US20100293487A1 (en) * | 2009-05-18 | 2010-11-18 | Roy Schoenberg | Provider-to-provider Consultations |
US7852208B2 (en) | 2004-08-02 | 2010-12-14 | Hill-Rom Services, Inc. | Wireless bed connectivity |
US7868740B2 (en) | 2007-08-29 | 2011-01-11 | Hill-Rom Services, Inc. | Association of support surfaces and beds |
US20110010197A1 (en) * | 2009-07-08 | 2011-01-13 | Roy Schoenberg | Connecting Consumers with Service Providers |
US20110046469A1 (en) * | 2003-06-10 | 2011-02-24 | Abbott Diabetes Care Inc. | Glucose Measuring Device for Use In Personal Area Network |
US20110106593A1 (en) * | 2009-10-30 | 2011-05-05 | Roy Schoenberg | Coupon Codes |
US20110224998A1 (en) * | 2010-03-10 | 2011-09-15 | Roy Schoenberg | Online Care For Provider Practices |
US20110245633A1 (en) * | 2010-03-04 | 2011-10-06 | Neumitra LLC | Devices and methods for treating psychological disorders |
US8046625B2 (en) | 2008-02-22 | 2011-10-25 | Hill-Rom Services, Inc. | Distributed fault tolerant architecture for a healthcare communication system |
US20110307272A1 (en) * | 2005-10-24 | 2011-12-15 | CellTrak Technologies, Inc. | Home Health Point-of-Care and Administration System |
US20110313257A1 (en) * | 2008-12-19 | 2011-12-22 | Klaus Abraham-Fuchs | Method for Recording and Evaluation of Measurements Related to the Condition of a Patient for Configuration of a Portable, Patient-Controlled Device Operated to Record Said Measurements and Related Device |
US20120059227A1 (en) * | 2010-09-03 | 2012-03-08 | International Business Machines Corporation | Directing a user to a medical resource |
US8150509B2 (en) | 2004-10-21 | 2012-04-03 | Cardiac Pacemakers, Inc. | Systems and methods for drug therapy enhancement using expected pharmacodynamic models |
US20120173272A1 (en) * | 2010-12-31 | 2012-07-05 | Julian Omidi | Automated System and Method for Processing Obesity Patients |
US8272892B2 (en) | 2003-08-21 | 2012-09-25 | Hill-Rom Services, Inc. | Hospital bed having wireless data capability |
US20120290638A1 (en) * | 2011-05-13 | 2012-11-15 | Dhiraj Narula | Physician regional access networking agent |
US20130116526A1 (en) * | 2011-11-09 | 2013-05-09 | Telcare, Inc. | Handheld Blood Glucose Monitoring Device with Messaging Capability |
US8461968B2 (en) | 2007-08-29 | 2013-06-11 | Hill-Rom Services, Inc. | Mattress for a hospital bed for use in a healthcare facility and management of same |
US8694612B1 (en) | 2010-02-09 | 2014-04-08 | Roy Schoenberg | Connecting consumers with providers of live videos |
US8779924B2 (en) | 2010-02-19 | 2014-07-15 | Hill-Rom Services, Inc. | Nurse call system with additional status board |
US20140214827A1 (en) * | 2013-01-28 | 2014-07-31 | International Business Machines Corporation | Data Caveats for Database Tables |
US20150105608A1 (en) * | 2013-10-14 | 2015-04-16 | Rest Devices, Inc. | Infant Sleeping Aid and Infant-Bed Accessory |
WO2015057667A1 (en) * | 2013-10-14 | 2015-04-23 | Rest Devices, Inc. | Network-based care system |
US20150154880A1 (en) * | 2013-12-02 | 2015-06-04 | Aetna Inc. | Healthcare management with a support network |
WO2015095655A1 (en) * | 2013-12-19 | 2015-06-25 | Opentv, Inc. | Remote health care via a television communication system |
US9164801B2 (en) | 2010-06-08 | 2015-10-20 | International Business Machines Corporation | Probabilistic optimization of resource discovery, reservation and assignment |
US20150363564A1 (en) * | 2014-06-13 | 2015-12-17 | Vet24seven Inc. | Remote Medical Analysis |
US9292577B2 (en) | 2010-09-17 | 2016-03-22 | International Business Machines Corporation | User accessibility to data analytics |
US9411934B2 (en) | 2012-05-08 | 2016-08-09 | Hill-Rom Services, Inc. | In-room alarm configuration of nurse call system |
US20170017769A1 (en) * | 2015-07-14 | 2017-01-19 | Xerox Corporation | Methods and systems for predicting a health condition of a human subject |
US9578152B2 (en) | 2007-06-15 | 2017-02-21 | American Well Corporation | Telephonic-based engagements |
WO2017064827A1 (en) * | 2015-10-13 | 2017-04-20 | Sony Corporation | System and method for providing assistance during medical emergency |
US9646271B2 (en) | 2010-08-06 | 2017-05-09 | International Business Machines Corporation | Generating candidate inclusion/exclusion cohorts for a multiply constrained group |
US9678636B2 (en) | 2013-01-17 | 2017-06-13 | American Well Corporation | Modalities for brokered engagements |
EP2704045A3 (en) * | 2012-08-31 | 2017-07-26 | Fujifilm Corporation | Apparatus and method for providing medical support |
US20170228516A1 (en) * | 2012-09-20 | 2017-08-10 | Masimo Corporation | Intelligent medical escalation process |
US9734293B2 (en) | 2007-10-26 | 2017-08-15 | Hill-Rom Services, Inc. | System and method for association of patient care devices to a patient |
US9830424B2 (en) | 2013-09-18 | 2017-11-28 | Hill-Rom Services, Inc. | Bed/room/patient association systems and methods |
US10136815B2 (en) | 2012-09-24 | 2018-11-27 | Physio-Control, Inc. | Patient monitoring device with remote alert |
US10268989B2 (en) * | 2015-04-20 | 2019-04-23 | Murj, Inc. | Medical device data platform |
US10380324B2 (en) | 2010-12-15 | 2019-08-13 | Ross Medical Corporation | Patient emergency response system |
US10412028B1 (en) * | 2013-05-24 | 2019-09-10 | HCA Holdings, Inc. | Data derived user behavior modeling |
US10460074B2 (en) * | 2016-04-05 | 2019-10-29 | Conduent Business Services, Llc | Methods and systems for predicting a health condition of a human subject |
US10468136B2 (en) * | 2016-08-29 | 2019-11-05 | Conduent Business Services, Llc | Method and system for data processing to predict health condition of a human subject |
CN110840425A (en) * | 2019-11-20 | 2020-02-28 | 首都医科大学宣武医院 | Health monitoring system and method for emergency patients in diagnosis |
US10629304B2 (en) | 2013-08-27 | 2020-04-21 | Whiskers Worldwide, LLC | Systems and methods for decision support for animal health queries |
US10825568B2 (en) | 2013-10-11 | 2020-11-03 | Masimo Corporation | Alarm notification system |
EP3720347A4 (en) * | 2017-12-06 | 2021-08-25 | General Electric Company | System and methods for qualification of ecg data for remote analysis |
US11109818B2 (en) | 2018-04-19 | 2021-09-07 | Masimo Corporation | Mobile patient alarm display |
US20220031163A1 (en) * | 2013-03-15 | 2022-02-03 | Zoll Medical Corporation | Patient monitor screen aggregation |
US11289200B1 (en) | 2017-03-13 | 2022-03-29 | C/Hca, Inc. | Authorized user modeling for decision support |
US11504061B2 (en) | 2017-03-21 | 2022-11-22 | Stryker Corporation | Systems and methods for ambient energy powered physiological parameter monitoring |
US11670427B2 (en) | 2018-12-04 | 2023-06-06 | Mycare Integrated Software Solutions, LLC | Remote healthcare communication systems and methods |
US11894144B2 (en) | 2013-08-27 | 2024-02-06 | Whiskers Worldwide, LLC | Animal health decision support system and methods |
US11911325B2 (en) | 2019-02-26 | 2024-02-27 | Hill-Rom Services, Inc. | Bed interface for manual location |
US11948680B2 (en) | 2022-03-15 | 2024-04-02 | Murj, Inc. | Systems and methods to distribute cardiac device advisory data |
US11955236B2 (en) | 2022-06-28 | 2024-04-09 | Murj, Inc. | Systems and methods for managing patient medical devices |
Families Citing this family (395)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7624028B1 (en) | 1992-11-17 | 2009-11-24 | Health Hero Network, Inc. | Remote health monitoring and maintenance system |
US6968375B1 (en) | 1997-03-28 | 2005-11-22 | Health Hero Network, Inc. | Networked system for interactive communication and remote monitoring of individuals |
US20010011224A1 (en) | 1995-06-07 | 2001-08-02 | Stephen James Brown | Modular microprocessor-based health monitoring system |
AU1766201A (en) | 1992-11-17 | 2001-05-30 | Health Hero Network, Inc. | Method and system for improving adherence with a diet program or other medical regimen |
US5307263A (en) | 1992-11-17 | 1994-04-26 | Raya Systems, Inc. | Modular microprocessor-based health monitoring system |
US5862223A (en) * | 1996-07-24 | 1999-01-19 | Walker Asset Management Limited Partnership | Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce |
US6673314B1 (en) | 1997-02-14 | 2004-01-06 | Nxstage Medical, Inc. | Interactive systems and methods for supporting hemofiltration therapies |
US6852090B2 (en) * | 1997-02-14 | 2005-02-08 | Nxstage Medical, Inc. | Fluid processing systems and methods using extracorporeal fluid flow panels oriented within a cartridge |
US7756721B1 (en) * | 1997-03-14 | 2010-07-13 | Best Doctors, Inc. | Health care management system |
US6036924A (en) | 1997-12-04 | 2000-03-14 | Hewlett-Packard Company | Cassette of lancet cartridges for sampling blood |
US6391005B1 (en) | 1998-03-30 | 2002-05-21 | Agilent Technologies, Inc. | Apparatus and method for penetration with shaft having a sensor for sensing penetration depth |
US8882666B1 (en) | 1998-05-08 | 2014-11-11 | Ideal Life Inc. | Personal health monitoring and/or communication system |
CN1311877C (en) * | 1998-06-03 | 2007-04-25 | 斯科特实验室公司 | Apparatus and method for providing a conscious patient relief from pain and anxiety associated with medical or surgical procedures |
US6872187B1 (en) | 1998-09-01 | 2005-03-29 | Izex Technologies, Inc. | Orthoses for joint rehabilitation |
US7305347B1 (en) | 1998-09-09 | 2007-12-04 | Raymond Anthony Joao | Apparatus and method for providing employee benefits and /or employee benefits information |
US20070112601A1 (en) * | 2005-10-04 | 2007-05-17 | Anuthep Benja-Athon | System of calibrating physicians' practices of medicine |
US20040220829A1 (en) * | 1999-03-22 | 2004-11-04 | Ofir Baharav | Distributed system and method for managing communication among healthcare providers, patients and third parties |
US6312378B1 (en) | 1999-06-03 | 2001-11-06 | Cardiac Intelligence Corporation | System and method for automated collection and analysis of patient information retrieved from an implantable medical device for remote patient care |
US6607485B2 (en) | 1999-06-03 | 2003-08-19 | Cardiac Intelligence Corporation | Computer readable storage medium containing code for automated collection and analysis of patient information retrieved from an implantable medical device for remote patient care |
US7429243B2 (en) * | 1999-06-03 | 2008-09-30 | Cardiac Intelligence Corporation | System and method for transacting an automated patient communications session |
US7134996B2 (en) * | 1999-06-03 | 2006-11-14 | Cardiac Intelligence Corporation | System and method for collection and analysis of patient information for automated remote patient care |
US6270457B1 (en) | 1999-06-03 | 2001-08-07 | Cardiac Intelligence Corp. | System and method for automated collection and analysis of regularly retrieved patient information for remote patient care |
US7416537B1 (en) | 1999-06-23 | 2008-08-26 | Izex Technologies, Inc. | Rehabilitative orthoses |
CA2314517A1 (en) | 1999-07-26 | 2001-01-26 | Gust H. Bardy | System and method for determining a reference baseline of individual patient status for use in an automated collection and analysis patient care system |
CA2314513A1 (en) | 1999-07-26 | 2001-01-26 | Gust H. Bardy | System and method for providing normalized voice feedback from an individual patient in an automated collection and analysis patient care system |
US6221011B1 (en) | 1999-07-26 | 2001-04-24 | Cardiac Intelligence Corporation | System and method for determining a reference baseline of individual patient status for use in an automated collection and analysis patient care system |
US6264614B1 (en) * | 1999-08-31 | 2001-07-24 | Data Critical Corporation | System and method for generating and transferring medical data |
AU6802000A (en) * | 1999-09-13 | 2001-04-30 | Healinx | A message and program system supporting communication |
EP1247221A4 (en) * | 1999-09-20 | 2005-01-19 | Quintiles Transnat Corp | System and method for analyzing de-identified health care data |
US6732113B1 (en) * | 1999-09-20 | 2004-05-04 | Verispan, L.L.C. | System and method for generating de-identified health care data |
US7246069B1 (en) * | 1999-10-15 | 2007-07-17 | Ue Systems, Inc. | Method and apparatus for online health monitoring |
US6527711B1 (en) | 1999-10-18 | 2003-03-04 | Bodymedia, Inc. | Wearable human physiological data sensors and reporting system therefor |
US6738754B1 (en) | 1999-10-22 | 2004-05-18 | Intermap Systems, Inc. | Apparatus and method for directing internet users to health care information |
US6648820B1 (en) * | 1999-10-27 | 2003-11-18 | Home-Medicine (Usa), Inc. | Medical condition sensing system |
US6524239B1 (en) * | 1999-11-05 | 2003-02-25 | Wcr Company | Apparatus for non-instrusively measuring health parameters of a subject and method of use thereof |
US8894577B2 (en) * | 1999-11-05 | 2014-11-25 | Elite Care Technologies, Inc. | System and method for medical information monitoring and processing |
US6368284B1 (en) | 1999-11-16 | 2002-04-09 | Cardiac Intelligence Corporation | Automated collection and analysis patient care system and method for diagnosing and monitoring myocardial ischemia and outcomes thereof |
US6336903B1 (en) | 1999-11-16 | 2002-01-08 | Cardiac Intelligence Corp. | Automated collection and analysis patient care system and method for diagnosing and monitoring congestive heart failure and outcomes thereof |
US6411840B1 (en) * | 1999-11-16 | 2002-06-25 | Cardiac Intelligence Corporation | Automated collection and analysis patient care system and method for diagnosing and monitoring the outcomes of atrial fibrillation |
US6398728B1 (en) * | 1999-11-16 | 2002-06-04 | Cardiac Intelligence Corporation | Automated collection and analysis patient care system and method for diagnosing and monitoring respiratory insufficiency and outcomes thereof |
US6440066B1 (en) * | 1999-11-16 | 2002-08-27 | Cardiac Intelligence Corporation | Automated collection and analysis patient care system and method for ordering and prioritizing multiple health disorders to identify an index disorder |
US8369937B2 (en) | 1999-11-16 | 2013-02-05 | Cardiac Pacemakers, Inc. | System and method for prioritizing medical conditions |
US7780619B2 (en) | 1999-11-29 | 2010-08-24 | Nxstage Medical, Inc. | Blood treatment apparatus |
US7490048B2 (en) * | 1999-12-18 | 2009-02-10 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US7464040B2 (en) * | 1999-12-18 | 2008-12-09 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US6980958B1 (en) * | 2000-01-11 | 2005-12-27 | Zycare, Inc. | Apparatus and methods for monitoring and modifying anticoagulation therapy of remotely located patients |
CA2435480A1 (en) * | 2000-02-10 | 2001-08-16 | Lawrence M. Sherman | System and method for providing additional insurance |
US6941271B1 (en) * | 2000-02-15 | 2005-09-06 | James W. Soong | Method for accessing component fields of a patient record by applying access rules determined by the patient |
US7218938B1 (en) | 2002-04-24 | 2007-05-15 | Chung Lau | Methods and apparatus to analyze and present location information |
US7212829B1 (en) | 2000-02-28 | 2007-05-01 | Chung Lau | Method and system for providing shipment tracking and notifications |
US7403972B1 (en) | 2002-04-24 | 2008-07-22 | Ip Venture, Inc. | Method and system for enhanced messaging |
US7321774B1 (en) | 2002-04-24 | 2008-01-22 | Ipventure, Inc. | Inexpensive position sensing device |
US7366522B2 (en) | 2000-02-28 | 2008-04-29 | Thomas C Douglass | Method and system for location tracking |
US6975941B1 (en) | 2002-04-24 | 2005-12-13 | Chung Lau | Method and apparatus for intelligent acquisition of position information |
US7194371B1 (en) * | 2000-03-27 | 2007-03-20 | Cardiobeat.Com | Medical testing system and method |
US7099801B1 (en) * | 2000-03-27 | 2006-08-29 | Cardiobeat.Com | Medical testing internet server system and method |
US7539623B1 (en) * | 2000-04-06 | 2009-05-26 | Medical Central Online | Method and a system for providing bed availability information on a computer network |
AU2001253889A1 (en) * | 2000-04-12 | 2001-10-30 | Yourdoctor.Com | An information navigation system and method for using the same |
AU5359901A (en) | 2000-04-17 | 2001-10-30 | Vivometrics Inc | Systems and methods for ambulatory monitoring of physiological signs |
US6616613B1 (en) * | 2000-04-27 | 2003-09-09 | Vitalsines International, Inc. | Physiological signal monitoring system |
KR20010105460A (en) * | 2000-05-09 | 2001-11-29 | 권기철 | Telemedicine system for fetal care |
US9741001B2 (en) | 2000-05-18 | 2017-08-22 | Carefusion 303, Inc. | Predictive medication safety |
US10062457B2 (en) | 2012-07-26 | 2018-08-28 | Carefusion 303, Inc. | Predictive notifications for adverse patient events |
WO2001088828A2 (en) | 2000-05-18 | 2001-11-22 | Alaris Medical Systems, Inc. | Distributed remote asset and medication management drug delivery system |
US9069887B2 (en) | 2000-05-18 | 2015-06-30 | Carefusion 303, Inc. | Patient-specific medication management system |
US10353856B2 (en) | 2011-03-17 | 2019-07-16 | Carefusion 303, Inc. | Scalable communication system |
US7860583B2 (en) | 2004-08-25 | 2010-12-28 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
US11087873B2 (en) | 2000-05-18 | 2021-08-10 | Carefusion 303, Inc. | Context-aware healthcare notification system |
US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
US20020010597A1 (en) * | 2000-05-19 | 2002-01-24 | Mayer Gregg L. | Systems and methods for electronic health management |
US7149774B2 (en) * | 2000-06-02 | 2006-12-12 | Bellsouth Intellectual Property Corporation | Method of facilitating access to IP-based emergency services |
US6807564B1 (en) * | 2000-06-02 | 2004-10-19 | Bellsouth Intellectual Property Corporation | Panic button IP device |
US7198600B2 (en) * | 2000-06-13 | 2007-04-03 | Canon Kabushiki Kaisha | Body temperature managing method and device, storage medium, body temperature managing system, and program |
US7689437B1 (en) | 2000-06-16 | 2010-03-30 | Bodymedia, Inc. | System for monitoring health, wellness and fitness |
BRPI0414359A (en) | 2000-06-16 | 2006-11-14 | Bodymedia Inc | body weight monitoring and management system and other psychological conditions that include interactive and personalized planning, intervention and reporting |
US20060122474A1 (en) | 2000-06-16 | 2006-06-08 | Bodymedia, Inc. | Apparatus for monitoring health, wellness and fitness |
DE60119100T2 (en) * | 2000-06-23 | 2006-08-31 | Bodymedia, Inc. | SYSTEM FOR THE MONITORING OF HEALTH, WELL-BEING AND CONDITION |
US7237205B2 (en) * | 2000-07-12 | 2007-06-26 | Home-Medicine (Usa), Inc. | Parameter evaluation system |
US8043224B2 (en) | 2000-07-12 | 2011-10-25 | Dimicine Research It, Llc | Telemedicine system |
US6949073B2 (en) * | 2002-10-03 | 2005-09-27 | Home-Medicine.Com, Inc. | Dyspnea monitor, and telemedicine system and method |
US6886045B1 (en) * | 2000-08-14 | 2005-04-26 | At&T Corp. | Subscription-based priority interactive help services on the internet |
US7702522B1 (en) * | 2000-09-01 | 2010-04-20 | Sholem Steven L | Method and apparatus for tracking the relative value of medical services |
US6658431B1 (en) * | 2000-09-06 | 2003-12-02 | Intermap Systems, Inc. | Method and apparatus for directing internet users to health care information such as names of health care providers |
US20020038430A1 (en) * | 2000-09-13 | 2002-03-28 | Charles Edwards | System and method of data collection, processing, analysis, and annotation for monitoring cyber-threats and the notification thereof to subscribers |
US8797165B2 (en) * | 2000-10-11 | 2014-08-05 | Riddell, Inc. | System for monitoring a physiological parameter of players engaged in a sporting activity |
US6826509B2 (en) | 2000-10-11 | 2004-11-30 | Riddell, Inc. | System and method for measuring the linear and rotational acceleration of a body part |
US10952671B2 (en) | 2000-10-11 | 2021-03-23 | Riddell, Inc. | System for monitoring a physiological parameter of players engaged in a sporting activity |
US7049957B2 (en) * | 2000-11-03 | 2006-05-23 | Wcr Company | Local area positioning system |
US8641644B2 (en) | 2000-11-21 | 2014-02-04 | Sanofi-Aventis Deutschland Gmbh | Blood testing apparatus having a rotatable cartridge with multiple lancing elements and testing means |
US6567502B2 (en) | 2000-12-19 | 2003-05-20 | Bellsouth Intellectual Property Corporation | Multimedia emergency services |
JP2002197186A (en) * | 2000-12-27 | 2002-07-12 | Fujitsu Ltd | Personal information management device |
US7831449B2 (en) | 2001-02-02 | 2010-11-09 | Thompson Reuters (Healthcare) Inc. | Method and system for extracting medical information for presentation to medical providers on mobile terminals |
US6819247B2 (en) | 2001-02-16 | 2004-11-16 | Locast Corporation | Apparatus, method, and system for remote monitoring of need for assistance based on change in velocity |
EP1237058A1 (en) * | 2001-02-28 | 2002-09-04 | Eta SA Fabriques d'Ebauches | Usage of a non-magnetic coating for covering parts in a horological movement |
US20030158755A1 (en) * | 2001-03-01 | 2003-08-21 | Neuman Sherry L. | System and method for conducting drug use evaluation |
US7401027B2 (en) * | 2001-03-19 | 2008-07-15 | The Jasos Group, Llc | Methods for collecting fees for healthcare management group |
US7398217B2 (en) * | 2001-03-19 | 2008-07-08 | The Jasos Group, Llc | Methods and systems for healthcare practice management |
US7873589B2 (en) | 2001-04-02 | 2011-01-18 | Invivodata, Inc. | Operation and method for prediction and management of the validity of subject reported data |
US20050119580A1 (en) | 2001-04-23 | 2005-06-02 | Eveland Doug C. | Controlling access to a medical monitoring system |
US9269116B2 (en) * | 2001-05-14 | 2016-02-23 | American Doctors Online, Inc. | System and method for delivering medical examination, treatment and assistance over a network |
US6638218B2 (en) * | 2001-05-14 | 2003-10-28 | American Doctors On-Line, Inc. | System and method for delivering medical examination, diagnosis, and treatment over a network |
US7011629B2 (en) * | 2001-05-14 | 2006-03-14 | American Doctors On-Line, Inc. | System and method for delivering medical examination, treatment and assistance over a network |
DE60234597D1 (en) | 2001-06-12 | 2010-01-14 | Pelikan Technologies Inc | DEVICE AND METHOD FOR REMOVING BLOOD SAMPLES |
US8337419B2 (en) | 2002-04-19 | 2012-12-25 | Sanofi-Aventis Deutschland Gmbh | Tissue penetration device |
US9427532B2 (en) | 2001-06-12 | 2016-08-30 | Sanofi-Aventis Deutschland Gmbh | Tissue penetration device |
US7344507B2 (en) | 2002-04-19 | 2008-03-18 | Pelikan Technologies, Inc. | Method and apparatus for lancet actuation |
US7699791B2 (en) | 2001-06-12 | 2010-04-20 | Pelikan Technologies, Inc. | Method and apparatus for improving success rate of blood yield from a fingerstick |
US7041068B2 (en) | 2001-06-12 | 2006-05-09 | Pelikan Technologies, Inc. | Sampling module device and method |
CA2448902C (en) | 2001-06-12 | 2010-09-07 | Pelikan Technologies, Inc. | Self optimizing lancing device with adaptation means to temporal variations in cutaneous properties |
US7749174B2 (en) | 2001-06-12 | 2010-07-06 | Pelikan Technologies, Inc. | Method and apparatus for lancet launching device intergrated onto a blood-sampling cartridge |
US7981056B2 (en) | 2002-04-19 | 2011-07-19 | Pelikan Technologies, Inc. | Methods and apparatus for lancet actuation |
US9226699B2 (en) | 2002-04-19 | 2016-01-05 | Sanofi-Aventis Deutschland Gmbh | Body fluid sampling module with a continuous compression tissue interface surface |
US9795747B2 (en) | 2010-06-02 | 2017-10-24 | Sanofi-Aventis Deutschland Gmbh | Methods and apparatus for lancet actuation |
US7033371B2 (en) | 2001-06-12 | 2006-04-25 | Pelikan Technologies, Inc. | Electric lancet actuator |
US20020198740A1 (en) * | 2001-06-21 | 2002-12-26 | Roman Linda L. | Intelligent data retrieval system and method |
MXPA04004246A (en) * | 2001-11-01 | 2004-09-10 | Scott Lab Inc | User interface for sedation and analgesia delivery systems and methods. |
EP1440409A2 (en) * | 2001-11-02 | 2004-07-28 | Siemens Medical Solutions USA, Inc. | Patient data mining, presentation, exploration, and verification |
US8949082B2 (en) | 2001-11-02 | 2015-02-03 | Siemens Medical Solutions Usa, Inc. | Healthcare information technology system for predicting or preventing readmissions |
US20110295621A1 (en) * | 2001-11-02 | 2011-12-01 | Siemens Medical Solutions Usa, Inc. | Healthcare Information Technology System for Predicting and Preventing Adverse Events |
US20050101841A9 (en) * | 2001-12-04 | 2005-05-12 | Kimberly-Clark Worldwide, Inc. | Healthcare networks with biosensors |
JP4091303B2 (en) * | 2002-01-07 | 2008-05-28 | 富士通株式会社 | Medical reservation system, medical reservation method, computer device, terminal device, and computer program |
JP2003224674A (en) * | 2002-01-30 | 2003-08-08 | Nec Infrontia Corp | Health management service system by portable telephone terminal |
US20050144042A1 (en) * | 2002-02-19 | 2005-06-30 | David Joffe | Associated systems and methods for managing biological data and providing data interpretation tools |
US20030233250A1 (en) * | 2002-02-19 | 2003-12-18 | David Joffe | Systems and methods for managing biological data and providing data interpretation tools |
MXPA04008255A (en) * | 2002-02-25 | 2004-11-10 | Scott Lab Inc | Remote monitoring and control of sedation and analgesia systems. |
US20040034284A1 (en) * | 2002-04-10 | 2004-02-19 | Aversano Thomas R. | Patient initiated emergency response system |
US7909778B2 (en) | 2002-04-19 | 2011-03-22 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7232451B2 (en) | 2002-04-19 | 2007-06-19 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7291117B2 (en) | 2002-04-19 | 2007-11-06 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7717863B2 (en) | 2002-04-19 | 2010-05-18 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US9314194B2 (en) | 2002-04-19 | 2016-04-19 | Sanofi-Aventis Deutschland Gmbh | Tissue penetration device |
US8579831B2 (en) | 2002-04-19 | 2013-11-12 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for penetrating tissue |
US8784335B2 (en) | 2002-04-19 | 2014-07-22 | Sanofi-Aventis Deutschland Gmbh | Body fluid sampling device with a capacitive sensor |
US7901362B2 (en) | 2002-04-19 | 2011-03-08 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7976476B2 (en) | 2002-04-19 | 2011-07-12 | Pelikan Technologies, Inc. | Device and method for variable speed lancet |
US7547287B2 (en) | 2002-04-19 | 2009-06-16 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7226461B2 (en) | 2002-04-19 | 2007-06-05 | Pelikan Technologies, Inc. | Method and apparatus for a multi-use body fluid sampling device with sterility barrier release |
US8221334B2 (en) | 2002-04-19 | 2012-07-17 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for penetrating tissue |
US7331931B2 (en) | 2002-04-19 | 2008-02-19 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7648468B2 (en) | 2002-04-19 | 2010-01-19 | Pelikon Technologies, Inc. | Method and apparatus for penetrating tissue |
US9795334B2 (en) | 2002-04-19 | 2017-10-24 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for penetrating tissue |
US8702624B2 (en) | 2006-09-29 | 2014-04-22 | Sanofi-Aventis Deutschland Gmbh | Analyte measurement device with a single shot actuator |
US7297122B2 (en) | 2002-04-19 | 2007-11-20 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7371247B2 (en) | 2002-04-19 | 2008-05-13 | Pelikan Technologies, Inc | Method and apparatus for penetrating tissue |
US7674232B2 (en) | 2002-04-19 | 2010-03-09 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US9248267B2 (en) | 2002-04-19 | 2016-02-02 | Sanofi-Aventis Deustchland Gmbh | Tissue penetration device |
US8267870B2 (en) | 2002-04-19 | 2012-09-18 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for body fluid sampling with hybrid actuation |
US7229458B2 (en) | 2002-04-19 | 2007-06-12 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7892183B2 (en) | 2002-04-19 | 2011-02-22 | Pelikan Technologies, Inc. | Method and apparatus for body fluid sampling and analyte sensing |
US7481776B2 (en) | 2002-04-19 | 2009-01-27 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US7491178B2 (en) | 2002-04-19 | 2009-02-17 | Pelikan Technologies, Inc. | Method and apparatus for penetrating tissue |
US9049571B2 (en) | 2002-04-24 | 2015-06-02 | Ipventure, Inc. | Method and system for enhanced messaging |
US9182238B2 (en) | 2002-04-24 | 2015-11-10 | Ipventure, Inc. | Method and apparatus for intelligent acquisition of position information |
US7120488B2 (en) * | 2002-05-07 | 2006-10-10 | Medtronic Physio-Control Manufacturing Corp. | Therapy-delivering portable medical device capable of triggering and communicating with an alarm system |
US7286997B2 (en) * | 2002-05-07 | 2007-10-23 | Cembex Care Solutions, Llc | Internet-based, customizable clinical information system |
CA2487255C (en) * | 2002-06-11 | 2014-05-06 | Jeffrey A. Matos | System for cardiac resuscitation |
US20040030581A1 (en) * | 2002-06-12 | 2004-02-12 | Samuel Leven | Heart monitoring device |
US20040054775A1 (en) * | 2002-06-26 | 2004-03-18 | Poliac Research Corporation | Medical data collection and deliver system |
JP2004049345A (en) * | 2002-07-17 | 2004-02-19 | Nippon Colin Co Ltd | Medical information providing system and cellular phone |
US20040030584A1 (en) * | 2002-08-12 | 2004-02-12 | Harris Jeffrey Saul | System and method for guideline-based, rules assisted medical and disability management |
US8560582B2 (en) * | 2002-08-12 | 2013-10-15 | Jeffrey Saul Harris | Method for analyzing records in a data base |
US20070100666A1 (en) * | 2002-08-22 | 2007-05-03 | Stivoric John M | Devices and systems for contextual and physiological-based detection, monitoring, reporting, entertainment, and control of other devices |
US7020508B2 (en) | 2002-08-22 | 2006-03-28 | Bodymedia, Inc. | Apparatus for detecting human physiological and contextual information |
GB2393356B (en) * | 2002-09-18 | 2006-02-01 | E San Ltd | Telemedicine system |
EP1556834A4 (en) * | 2002-10-03 | 2009-04-01 | Scott Lab Inc | Systems and methods for providing sensor fusion |
EP1554003A4 (en) * | 2002-10-03 | 2011-10-12 | Scott Lab Inc | Systems and methods for providing trend analysis in a sedation and analgesia system |
CA2501732C (en) | 2002-10-09 | 2013-07-30 | Bodymedia, Inc. | Method and apparatus for auto journaling of continuous or discrete body states utilizing physiological and/or contextual parameters |
US8332233B2 (en) * | 2002-11-13 | 2012-12-11 | Biomedical Systems Corporation | Method and system for collecting and analyzing holter data employing a web site |
US6982639B2 (en) * | 2002-11-26 | 2006-01-03 | Ge Medical Systems Information Technologies, Inc. | Wireless subject locator |
US20040111298A1 (en) * | 2002-12-10 | 2004-06-10 | Roy Schoenberg | Method of and system for integrating health information into a patient's record |
US7009511B2 (en) | 2002-12-17 | 2006-03-07 | Cardiac Pacemakers, Inc. | Repeater device for communications with an implantable medical device |
US8574895B2 (en) | 2002-12-30 | 2013-11-05 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus using optical techniques to measure analyte levels |
US7289029B2 (en) | 2002-12-31 | 2007-10-30 | Medtronic Physio-Control Corp. | Communication between emergency medical device and safety agency |
US7874983B2 (en) * | 2003-01-27 | 2011-01-25 | Motorola Mobility, Inc. | Determination of emotional and physiological states of a recipient of a communication |
AU2004207534A1 (en) * | 2003-01-27 | 2004-08-12 | Cardiac Telecom, Corporation | Defibrillation system for non-medical environments |
BRPI0408089A (en) * | 2003-03-04 | 2006-02-14 | Ethicon Endo Surgey Inc | patient monitoring and drug administration system and use process |
US20040199056A1 (en) * | 2003-04-03 | 2004-10-07 | International Business Machines Corporation | Body monitoring using local area wireless interfaces |
US7727161B2 (en) | 2003-04-10 | 2010-06-01 | Vivometrics, Inc. | Systems and methods for monitoring cough |
US7809433B2 (en) * | 2005-08-09 | 2010-10-05 | Adidas Ag | Method and system for limiting interference in electroencephalographic signals |
US7182738B2 (en) | 2003-04-23 | 2007-02-27 | Marctec, Llc | Patient monitoring apparatus and method for orthosis and other devices |
JP2004358231A (en) * | 2003-05-15 | 2004-12-24 | Seiko Instruments Inc | Living body condition monitoring system |
WO2004107964A2 (en) | 2003-06-06 | 2004-12-16 | Pelikan Technologies, Inc. | Blood harvesting device with electronic control |
US7769465B2 (en) * | 2003-06-11 | 2010-08-03 | Matos Jeffrey A | System for cardiac resuscitation |
WO2006001797A1 (en) | 2004-06-14 | 2006-01-05 | Pelikan Technologies, Inc. | Low pain penetrating |
US8034294B1 (en) | 2003-07-15 | 2011-10-11 | Ideal Life, Inc. | Medical monitoring/consumables tracking device |
US7238156B1 (en) * | 2003-07-31 | 2007-07-03 | At&T Intellectual Property, Inc. | Systems, methods, and devices for health monitoring |
US8571880B2 (en) | 2003-08-07 | 2013-10-29 | Ideal Life, Inc. | Personal health management device, method and system |
US20050038675A1 (en) * | 2003-08-12 | 2005-02-17 | Siekman Jeffrey A. | Methods and systems for at-home and community-based care |
US20050038677A1 (en) * | 2003-08-15 | 2005-02-17 | Nicholas Hahalis | Cooperative health care plan and method thereof |
US8595115B2 (en) * | 2003-08-18 | 2013-11-26 | Gilbert Leistner | Methods for managing a medical event |
US8543478B2 (en) * | 2003-08-18 | 2013-09-24 | Gilbert Leistner | System and method for identification of quasi-fungible goods and services, and financial instruments based thereon |
US20050043967A1 (en) * | 2003-08-20 | 2005-02-24 | Robinson Joseph R. | Systems and methods for documenting home care services |
CA2538710A1 (en) | 2003-09-12 | 2005-03-31 | Bodymedia, Inc. | Method and apparatus for measuring heart related parameters |
US20050066335A1 (en) * | 2003-09-23 | 2005-03-24 | Robert Aarts | System and method for exposing local clipboard functionality towards external applications |
DE10345171B4 (en) * | 2003-09-29 | 2006-11-23 | Siemens Ag | Monitoring system for patients |
WO2005033659A2 (en) | 2003-09-29 | 2005-04-14 | Pelikan Technologies, Inc. | Method and apparatus for an improved sample capture device |
US20050075145A1 (en) * | 2003-10-03 | 2005-04-07 | Dvorak Joseph L. | Method and system for coordinating use of objects using wireless communications |
US20050075902A1 (en) * | 2003-10-06 | 2005-04-07 | Wager Douglas W. | Computerized system and method for determining work in a healthcare environment |
US20060149589A1 (en) * | 2005-01-03 | 2006-07-06 | Cerner Innovation, Inc. | System and method for clinical workforce management interface |
US8000978B2 (en) * | 2003-10-06 | 2011-08-16 | Cerner Innovation, Inc. | System and method for automatically generating evidence-based assignment of care providers to patients |
US9351680B2 (en) | 2003-10-14 | 2016-05-31 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for a variable user interface |
US20050124866A1 (en) * | 2003-11-12 | 2005-06-09 | Joseph Elaz | Healthcare processing device and display system |
EP1691683B1 (en) * | 2003-11-26 | 2014-12-31 | CardioNet, Inc. | System and method for processing and presenting arrhythmia information to facilitate heart arrhythmia identification and treatment |
EP1692635A2 (en) | 2003-12-05 | 2006-08-23 | Cardinal Health 303, Inc. | System and method for network monitoring of multiple medical devices |
EP1706026B1 (en) | 2003-12-31 | 2017-03-01 | Sanofi-Aventis Deutschland GmbH | Method and apparatus for improving fluidic flow and sample capture |
US7822454B1 (en) | 2005-01-03 | 2010-10-26 | Pelikan Technologies, Inc. | Fluid sampling device with improved analyte detecting member configuration |
JP4861616B2 (en) * | 2004-01-06 | 2012-01-25 | 株式会社東芝 | HEALTHCARE SUPPORT SYSTEM AND HEALTHCARE SUPPORT DEVICE |
US8025624B2 (en) | 2004-02-19 | 2011-09-27 | Cardiac Pacemakers, Inc. | System and method for assessing cardiac performance through cardiac vibration monitoring |
IL160748A0 (en) * | 2004-03-04 | 2004-08-31 | Security system | |
DK1734858T3 (en) | 2004-03-22 | 2014-10-20 | Bodymedia Inc | NON-INVASIVE TEMPERATURE MONITORING DEVICE |
JP2005285001A (en) * | 2004-03-30 | 2005-10-13 | Sunstar Inc | Health support method and its system |
JP4406684B2 (en) * | 2004-04-08 | 2010-02-03 | 独立行政法人産業技術総合研究所 | Reservation processing method and reservation processing system |
US20050246199A1 (en) * | 2004-05-03 | 2005-11-03 | Tom Futch | Health and wellness station |
US7856035B2 (en) * | 2004-05-05 | 2010-12-21 | Welch Allyn, Inc. | Method and apparatus for wireless transmission of data |
US20050251054A1 (en) * | 2004-05-10 | 2005-11-10 | Medpond, Llc | Method and apparatus for measurement of autonomic nervous system function |
US20050251051A1 (en) * | 2004-05-10 | 2005-11-10 | Medpond, Llc | Method and apparatus for assessing autonomic function |
WO2005110214A2 (en) * | 2004-05-10 | 2005-11-24 | Meddorna, Llc | Method and apparatus for facilitating the provision of health care services |
US8828203B2 (en) | 2004-05-20 | 2014-09-09 | Sanofi-Aventis Deutschland Gmbh | Printable hydrogels for biosensors |
US9820684B2 (en) | 2004-06-03 | 2017-11-21 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for a fluid sampling device |
US9492084B2 (en) | 2004-06-18 | 2016-11-15 | Adidas Ag | Systems and methods for monitoring subjects in potential physiological distress |
AU2012201266B2 (en) * | 2004-06-18 | 2014-01-30 | Adidas Ag | Systems and methods for real-time physiological monitoring |
AU2005265092B2 (en) * | 2004-06-18 | 2012-03-15 | Adidas Ag | Systems and methods for real-time physiological monitoring |
US20050283385A1 (en) * | 2004-06-21 | 2005-12-22 | The Permanente Medical Group, Inc. | Individualized healthcare management system |
US20050283384A1 (en) * | 2004-06-21 | 2005-12-22 | The Permanete Medical Group, Inc. | System and method for assisting a care partner in monitoring a patient with chronic disease |
US20050288968A1 (en) * | 2004-06-29 | 2005-12-29 | John Collins | Method and system for evaluating a cost for health care coverage for an entity |
US7329226B1 (en) | 2004-07-06 | 2008-02-12 | Cardiac Pacemakers, Inc. | System and method for assessing pulmonary performance through transthoracic impedance monitoring |
US7261691B1 (en) * | 2004-08-02 | 2007-08-28 | Kwabena Asomani | Personalized emergency medical monitoring and transmission system |
US8412706B2 (en) * | 2004-09-15 | 2013-04-02 | Within3, Inc. | Social network analysis |
US20070260599A1 (en) * | 2004-09-15 | 2007-11-08 | Mcguire Heather A | Social network analysis |
US8635217B2 (en) | 2004-09-15 | 2014-01-21 | Michael J. Markus | Collections of linked databases |
US8880521B2 (en) * | 2004-09-15 | 2014-11-04 | 3Degrees Llc | Collections of linked databases |
US8577886B2 (en) * | 2004-09-15 | 2013-11-05 | Within3, Inc. | Collections of linked databases |
US9504410B2 (en) | 2005-09-21 | 2016-11-29 | Adidas Ag | Band-like garment for physiological monitoring |
US20060064319A1 (en) * | 2004-09-23 | 2006-03-23 | T-Med Behavioral, Inc. | Method for telemedicine services |
US20080009681A1 (en) * | 2004-10-06 | 2008-01-10 | Karim Al Hussiny | Real time arrhythmia detector for mobile applications |
US8308794B2 (en) | 2004-11-15 | 2012-11-13 | IZEK Technologies, Inc. | Instrumented implantable stents, vascular grafts and other medical devices |
WO2006055547A2 (en) | 2004-11-15 | 2006-05-26 | Izex Technologies, Inc. | Instrumented orthopedic and other medical implants |
WO2006055555A2 (en) * | 2004-11-15 | 2006-05-26 | S.M.A.R.T. Link Medical, Inc. | Collections of linked databases |
US20060106368A1 (en) * | 2004-11-15 | 2006-05-18 | Smart Technologies, Llc | Smart Surgical Device Operating System With Radio Frequency Identification |
US20060226957A1 (en) * | 2004-11-15 | 2006-10-12 | Miller Ronald H | Health care operating system with radio frequency information transfer |
US20060111620A1 (en) * | 2004-11-23 | 2006-05-25 | Squilla John R | Providing medical services at a kiosk |
US20060122864A1 (en) * | 2004-12-02 | 2006-06-08 | Gottesman Janell M | Patient management network |
US8202217B2 (en) * | 2004-12-20 | 2012-06-19 | Ip Venture, Inc. | Healthcare base |
US8273018B1 (en) | 2004-12-28 | 2012-09-25 | Cerner Innovation, Inc. | Computerized method for establishing a communication between a bedside care location and a remote care location |
US7612679B1 (en) * | 2004-12-28 | 2009-11-03 | Cerner Innovation, Inc. | Computerized method and system for providing alerts from a multi-patient display |
US8652831B2 (en) | 2004-12-30 | 2014-02-18 | Sanofi-Aventis Deutschland Gmbh | Method and apparatus for analyte measurement test time |
US8255238B2 (en) | 2005-01-03 | 2012-08-28 | Airstrip Ip Holdings, Llc | System and method for real time viewing of critical patient data on mobile devices |
WO2006074411A2 (en) * | 2005-01-07 | 2006-07-13 | Riddell, Inc. | System and method for evaluating and providing treatment to sports participants |
US20060181243A1 (en) * | 2005-02-11 | 2006-08-17 | Nortel Networks Limited | Use of location awareness to facilitate clinician-charger interaction in a healthcare environment |
US8929528B2 (en) * | 2005-02-11 | 2015-01-06 | Rockstar Consortium Us Lp | Method and system for enhancing collaboration |
US7707044B2 (en) * | 2005-02-11 | 2010-04-27 | Avaya Inc. | Use of location awareness to transfer communications sessions between terminals in a healthcare environment |
US7801743B2 (en) * | 2005-02-11 | 2010-09-21 | Avaya Inc. | Use of location awareness of establish communications with a target clinician in a healthcare environment |
US7676380B2 (en) * | 2005-02-11 | 2010-03-09 | Nortel Networks Limited | Use of location awareness to establish and suspend communications sessions in a healthcare environment |
US7966008B2 (en) * | 2005-02-11 | 2011-06-21 | Avaya Inc. | Use of location awareness to control radio frequency interference in a healthcare environment |
US20060184376A1 (en) * | 2005-02-11 | 2006-08-17 | Nortel Networks Limited | Use of location awareness to detect potentially supsicious motion or presence of equipment in a healthcare environment |
US8180650B2 (en) * | 2005-02-11 | 2012-05-15 | Avaya Inc. | Use of location awareness to request assistance for a medical event occurring in a healthcare environment |
US8050939B2 (en) * | 2005-02-11 | 2011-11-01 | Avaya Inc. | Methods and systems for use in the provision of services in an institutional setting such as a healthcare facility |
US8165893B1 (en) | 2005-02-16 | 2012-04-24 | Ideal Life Inc. | Medical monitoring and coordinated care system |
US8195481B2 (en) | 2005-02-25 | 2012-06-05 | Virtual Radiologic Corporaton | Teleradiology image processing system |
US8229761B2 (en) | 2005-02-25 | 2012-07-24 | Virtual Radiologic Corporation | Enhanced multiple resource planning and forecasting |
US8145503B2 (en) | 2005-02-25 | 2012-03-27 | Virtual Radiologic Corporation | Medical image metadata processing |
US7729928B2 (en) | 2005-02-25 | 2010-06-01 | Virtual Radiologic Corporation | Multiple resource planning system |
US20060206066A1 (en) * | 2005-03-10 | 2006-09-14 | Bozidar Ferek-Petric | Communications system for an implantable device and a drug dispenser |
US8261058B2 (en) * | 2005-03-16 | 2012-09-04 | Dt Labs, Llc | System, method and apparatus for electronically protecting data and digital content |
US20060247504A1 (en) * | 2005-04-29 | 2006-11-02 | Honeywell International, Inc. | Residential monitoring system for selected parameters |
US8781847B2 (en) | 2005-05-03 | 2014-07-15 | Cardiac Pacemakers, Inc. | System and method for managing alert notifications in an automated patient management system |
CA2606699C (en) | 2005-05-20 | 2017-04-18 | Vivometrics, Inc. | Methods and systems for determining dynamic hyperinflation |
US7881939B2 (en) * | 2005-05-31 | 2011-02-01 | Honeywell International Inc. | Monitoring system with speech recognition |
WO2007005463A2 (en) * | 2005-06-29 | 2007-01-11 | S.M.A.R.T. Link Medical, Inc. | Collections of linked databases |
US9060681B2 (en) * | 2005-06-30 | 2015-06-23 | Honeywell International Inc. | Trend monitoring system with multiple access levels |
US20070024439A1 (en) * | 2005-07-26 | 2007-02-01 | Tice Lee D | Monitoring system for a residence |
US8033996B2 (en) | 2005-07-26 | 2011-10-11 | Adidas Ag | Computer interfaces including physiologically guided avatars |
WO2007016252A2 (en) * | 2005-07-27 | 2007-02-08 | S.M.A.R.T. Link Medical, Inc. | Collections of linked databases and systems and methods for communicating about updates thereto |
US20070100213A1 (en) * | 2005-10-27 | 2007-05-03 | Dossas Vasilios D | Emergency medical diagnosis and communications device |
US10395326B2 (en) * | 2005-11-15 | 2019-08-27 | 3Degrees Llc | Collections of linked databases |
US20080287749A1 (en) * | 2005-11-23 | 2008-11-20 | Koninklijke Philips Electronics, N.V. | Method and Apparatus for Remote Patient Monitoring |
US20070123754A1 (en) * | 2005-11-29 | 2007-05-31 | Cuddihy Paul E | Non-encumbering, substantially continuous patient daily activity data measurement for indication of patient condition change for access by remote caregiver |
US20070129610A1 (en) * | 2005-12-06 | 2007-06-07 | Eastman Kodak Company | Method of providing automated medical assistance |
NO325438B1 (en) * | 2005-12-22 | 2008-05-05 | World Medical Ct Holding Sa | Procedure for securely transmitting medical data to a mobile device / terminal |
US10025906B2 (en) * | 2005-12-30 | 2018-07-17 | LifeWIRE Corporation | Mobile self-management compliance and notification method, system and computer program product |
US9144381B2 (en) * | 2005-12-30 | 2015-09-29 | LifeWIRE Corporation | Mobile self-management compliance and notification method, system and computer program product |
US8827905B2 (en) * | 2006-01-04 | 2014-09-09 | General Electric Company | Patient initiated on-demand remote medical service with integrated knowledge base and computer assisted diagnosing characteristics |
US20070179815A1 (en) * | 2006-01-20 | 2007-08-02 | Heartscreen America, Inc. | Medical screening system and method |
US8762733B2 (en) | 2006-01-30 | 2014-06-24 | Adidas Ag | System and method for identity confirmation using physiologic biometrics to determine a physiologic fingerprint |
US20070185389A1 (en) * | 2006-02-04 | 2007-08-09 | Robin Peng | Systems and methods for real time diagnostic and data correlation utilizing a computer network |
US20070191693A1 (en) * | 2006-02-04 | 2007-08-16 | Robin Peng | Systems and methods for medical monitoring and home automation |
US20070198295A1 (en) * | 2006-02-22 | 2007-08-23 | Duckert David W | Method and system for routing information to an appropriate care provider |
US8626953B2 (en) * | 2006-03-03 | 2014-01-07 | St. Louis University | System and method of communicating data for a hospital |
US20070209669A1 (en) * | 2006-03-09 | 2007-09-13 | Derchak P Alexander | Monitoring and quantification of smoking behaviors |
US8112293B2 (en) | 2006-03-24 | 2012-02-07 | Ipventure, Inc | Medical monitoring system |
US9047648B1 (en) * | 2006-03-30 | 2015-06-02 | At&T Mobility Ii Llc | Measurement, collection, reporting and processing of health condition data |
US20070270662A1 (en) * | 2006-05-19 | 2007-11-22 | Yung-Lung Chen | Apparatus and method for monitoring end user's health status via a network |
US20070282173A1 (en) * | 2006-05-31 | 2007-12-06 | Bily Wang | Vital sign sending method and a sending apparatus thereof |
US9962098B2 (en) | 2006-06-02 | 2018-05-08 | Global Cardiac Monitors, Inc. | Heart monitor electrode system |
US8126725B2 (en) * | 2006-06-07 | 2012-02-28 | Cerner Innovation, Inc. | Coordinating anatomic pathology consultations and inventory tracking |
US8131561B2 (en) * | 2006-06-07 | 2012-03-06 | Cerner Innovation, Inc. | Inventory tracking for anatomic pathology consultations |
US8475387B2 (en) | 2006-06-20 | 2013-07-02 | Adidas Ag | Automatic and ambulatory monitoring of congestive heart failure patients |
US20080021287A1 (en) * | 2006-06-26 | 2008-01-24 | Woellenstein Matthias D | System and method for adaptively adjusting patient data collection in an automated patient management environment |
US10049077B2 (en) * | 2006-06-30 | 2018-08-14 | Intel Corporation | Handheld device for elderly people |
US8396804B1 (en) | 2006-07-19 | 2013-03-12 | Mvisum, Inc. | System for remote review of clinical data |
US7974924B2 (en) | 2006-07-19 | 2011-07-05 | Mvisum, Inc. | Medical data encryption for communication over a vulnerable system |
US8380631B2 (en) | 2006-07-19 | 2013-02-19 | Mvisum, Inc. | Communication of emergency medical data over a vulnerable system |
US20080027288A1 (en) * | 2006-07-31 | 2008-01-31 | Jorg Renz | RFID enabled apparatus for monitoring a medical status and a method thereof |
JP4234163B2 (en) * | 2006-09-06 | 2009-03-04 | 株式会社タニタ | Body composition index estimation system |
US20080077430A1 (en) * | 2006-09-25 | 2008-03-27 | Singer Michael S | Systems and methods for improving medication adherence |
US8966235B2 (en) * | 2006-10-24 | 2015-02-24 | Kent E. Dicks | System for remote provisioning of electronic devices by overlaying an initial image with an updated image |
US8126731B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for medical data interchange activation |
US20090112769A1 (en) * | 2007-10-24 | 2009-04-30 | Kent Dicks | Systems and methods for remote patient monitoring |
US20080097917A1 (en) * | 2006-10-24 | 2008-04-24 | Kent Dicks | Systems and methods for wireless processing and medical device monitoring via remote command execution |
US8126735B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for remote patient monitoring and user interface |
US20080097914A1 (en) * | 2006-10-24 | 2008-04-24 | Kent Dicks | Systems and methods for wireless processing and transmittal of medical data through multiple interfaces |
US8126728B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for processing and transmittal of medical data through an intermediary device |
US9543920B2 (en) * | 2006-10-24 | 2017-01-10 | Kent E. Dicks | Methods for voice communication through personal emergency response system |
US8126734B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for adapter-based communication with a medical device |
US8126730B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for storage and forwarding of medical data |
US20080097913A1 (en) * | 2006-10-24 | 2008-04-24 | Kent Dicks | Systems and methods for wireless processing and transmittal of data from a plurality of medical devices |
US20080097550A1 (en) * | 2006-10-24 | 2008-04-24 | Kent Dicks | Systems and methods for remote patient monitoring and command execution |
US8126729B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for processing and transmittal of data from a plurality of medical devices |
US20080097912A1 (en) * | 2006-10-24 | 2008-04-24 | Kent Dicks | Systems and methods for wireless processing and transmittal of medical data through an intermediary device |
US8131566B2 (en) * | 2006-10-24 | 2012-03-06 | Medapps, Inc. | System for facility management of medical data and patient interface |
US8126732B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for processing and transmittal of medical data through multiple interfaces |
US8954719B2 (en) * | 2006-10-24 | 2015-02-10 | Kent E. Dicks | Method for remote provisioning of electronic devices by overlaying an initial image with an updated image |
US8126733B2 (en) * | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for medical data interchange using mobile computing devices |
US20080139891A1 (en) * | 2006-10-25 | 2008-06-12 | Cingular Wireless Ii, Llc | Devices and methods for communicating medical information |
US9833184B2 (en) | 2006-10-27 | 2017-12-05 | Adidas Ag | Identification of emotional states using physiological responses |
US9355273B2 (en) * | 2006-12-18 | 2016-05-31 | Bank Of America, N.A., As Collateral Agent | System and method for the protection and de-identification of health care data |
US20080167534A1 (en) * | 2007-01-04 | 2008-07-10 | National Yang-Ming University | Information collecting apparatus for collecting physiological parameters and method thereof |
CA2712040A1 (en) * | 2007-01-12 | 2008-07-24 | Healthhonors Corporation | Behavior modification with intermittent reward |
CA2619280A1 (en) * | 2007-01-30 | 2008-07-30 | Brytech Inc. | Combination level alarms and alarm persistence for patient monitoring |
US9044136B2 (en) * | 2007-02-16 | 2015-06-02 | Cim Technology Inc. | Wearable mini-size intelligent healthcare system |
US20080320029A1 (en) | 2007-02-16 | 2008-12-25 | Stivoric John M | Lifeotype interfaces |
WO2008103827A1 (en) | 2007-02-22 | 2008-08-28 | Welldoc Communications, Inc. | System and method for providing treatment recommendations based on models |
US10872686B2 (en) | 2007-02-22 | 2020-12-22 | WellDoc, Inc. | Systems and methods for disease control and management |
US10860943B2 (en) | 2007-02-22 | 2020-12-08 | WellDoc, Inc. | Systems and methods for disease control and management |
US20110124975A1 (en) * | 2007-03-16 | 2011-05-26 | Arthur Solomon Thompson | Method for Medical Diagnosis Utilizing PDA Software Robots |
US20080275732A1 (en) * | 2007-05-01 | 2008-11-06 | Best Doctors, Inc. | Using patterns of medical treatment codes to determine when further medical expertise is called for |
US20080306848A1 (en) * | 2007-06-05 | 2008-12-11 | Bank Of America Corporation | Lead Generation Platform |
US10178965B2 (en) | 2007-06-22 | 2019-01-15 | Ipventure, Inc. | Activity monitoring system for pregnant women |
CN101108125B (en) * | 2007-08-02 | 2010-06-16 | 无锡微感科技有限公司 | Dynamic monitoring system of body sign |
US7716997B2 (en) * | 2007-09-12 | 2010-05-18 | Intel Corporation | Parasitic tags for action annotation |
US20090187425A1 (en) * | 2007-09-17 | 2009-07-23 | Arthur Solomon Thompson | PDA software robots leveraging past history in seconds with software robots |
US7774852B2 (en) * | 2007-10-12 | 2010-08-10 | Panasonic Corporation | Health care system, key management server and method for managing key, and encrypting device and method for encrypting vital sign data |
US7942817B2 (en) * | 2008-01-04 | 2011-05-17 | Siemens Medical Solutions Usa, Inc. | Patient monitoring and treatment medical signal interface system |
WO2009126900A1 (en) | 2008-04-11 | 2009-10-15 | Pelikan Technologies, Inc. | Method and apparatus for analyte detecting device |
FI20085340L (en) * | 2008-04-22 | 2009-10-23 | Medixine Oy | Health screening and a method for implementing the health screening |
US9443141B2 (en) * | 2008-06-02 | 2016-09-13 | New York University | Method, system, and computer-accessible medium for classification of at least one ICTAL state |
US20090326339A1 (en) * | 2008-06-26 | 2009-12-31 | Microsoft Corporation | Connected healthcare devices with real-time and proactive capture and relay of contextual information |
US8423378B1 (en) | 2008-07-24 | 2013-04-16 | Ideal Life, Inc. | Facilitating health care management of subjects |
US8380531B2 (en) | 2008-07-25 | 2013-02-19 | Invivodata, Inc. | Clinical trial endpoint development process |
US8788476B2 (en) * | 2008-08-15 | 2014-07-22 | Chacha Search, Inc. | Method and system of triggering a search request |
US20100114607A1 (en) * | 2008-11-04 | 2010-05-06 | Sdi Health Llc | Method and system for providing reports and segmentation of physician activities |
US9375169B2 (en) | 2009-01-30 | 2016-06-28 | Sanofi-Aventis Deutschland Gmbh | Cam drive for managing disposable penetrating member actions with a single motor and motor and control system |
US9141758B2 (en) * | 2009-02-20 | 2015-09-22 | Ims Health Incorporated | System and method for encrypting provider identifiers on medical service claim transactions |
JP2012520144A (en) * | 2009-03-11 | 2012-09-06 | エアストリップ アイピー ホールディングス リミテッド ライアビリティ カンパニー | System and method for viewing patient data |
US10588527B2 (en) * | 2009-04-16 | 2020-03-17 | Braemar Manufacturing, Llc | Cardiac arrhythmia report |
US9323892B1 (en) * | 2009-07-01 | 2016-04-26 | Vigilytics LLC | Using de-identified healthcare data to evaluate post-healthcare facility encounter treatment outcomes |
US9118641B1 (en) | 2009-07-01 | 2015-08-25 | Vigilytics LLC | De-identifying medical history information for medical underwriting |
US9293060B2 (en) | 2010-05-06 | 2016-03-22 | Ai Cure Technologies Llc | Apparatus and method for recognition of patient activities when obtaining protocol adherence data |
US20110225009A1 (en) * | 2010-03-12 | 2011-09-15 | Kress Andrew E | System and method for providing geographic prescription data |
US10956867B2 (en) | 2010-03-31 | 2021-03-23 | Airstrip Ip Holdings, Llc | Multi-factor authentication for remote access of patient data |
US8965476B2 (en) | 2010-04-16 | 2015-02-24 | Sanofi-Aventis Deutschland Gmbh | Tissue penetration device |
US9883786B2 (en) | 2010-05-06 | 2018-02-06 | Aic Innovations Group, Inc. | Method and apparatus for recognition of inhaler actuation |
US10116903B2 (en) | 2010-05-06 | 2018-10-30 | Aic Innovations Group, Inc. | Apparatus and method for recognition of suspicious activities |
US9875666B2 (en) | 2010-05-06 | 2018-01-23 | Aic Innovations Group, Inc. | Apparatus and method for recognition of patient activities |
US10943676B2 (en) | 2010-06-08 | 2021-03-09 | Cerner Innovation, Inc. | Healthcare information technology system for predicting or preventing readmissions |
USD694909S1 (en) | 2011-10-12 | 2013-12-03 | HealthSpot Inc. | Medical kiosk |
US9043217B2 (en) | 2011-03-31 | 2015-05-26 | HealthSpot Inc. | Medical kiosk and method of use |
US8996392B2 (en) | 2011-03-31 | 2015-03-31 | Healthspot, Inc. | Medical kiosk and method of use |
GB201111138D0 (en) | 2011-06-30 | 2011-08-17 | Leman Micro Devices Uk Ltd | Personal health data collection |
WO2013033730A1 (en) | 2011-09-01 | 2013-03-07 | Riddell, Inc. | Systems and methods for monitoring a physiological parameter of persons engaged in physical activity |
US10276054B2 (en) | 2011-11-29 | 2019-04-30 | Eresearchtechnology, Inc. | Methods and systems for data analysis |
US9904766B2 (en) | 2012-04-04 | 2018-02-27 | Agnity Healthcare, Inc. | Method and system for collaboration for sharing patient records on low computing resources on communication devices |
WO2014033748A2 (en) * | 2012-08-07 | 2014-03-06 | Manjrekar Vaishali Nitin | A computer implemented system and method for sending/receiving information to/from users |
WO2014028680A1 (en) | 2012-08-15 | 2014-02-20 | HealthSpot Inc. | Veterinary kiosk with integrated veterinary medical devices |
US11182728B2 (en) | 2013-01-30 | 2021-11-23 | Carefusion 303, Inc. | Medication workflow management |
WO2014120927A1 (en) * | 2013-01-30 | 2014-08-07 | Quality Assured Services, Inc. | System for outpatient monitoring of ventricular assistance device patients |
US10430554B2 (en) | 2013-05-23 | 2019-10-01 | Carefusion 303, Inc. | Medication preparation queue |
US20140236915A1 (en) * | 2013-02-21 | 2014-08-21 | Baycare Health System, Inc. | System and method for retrieving physician information |
EP2973366B1 (en) | 2013-03-13 | 2020-08-19 | Carefusion 303 Inc. | Patient-specific medication management system |
CN105074766A (en) | 2013-03-13 | 2015-11-18 | 康尔福盛303公司 | Predictive medication safety |
US20140324457A1 (en) * | 2013-04-29 | 2014-10-30 | TaeSoo Sean Kim | Integrated health care predicting system |
US11587688B2 (en) | 2014-03-27 | 2023-02-21 | Raymond Anthony Joao | Apparatus and method for providing healthcare services remotely or virtually with or using an electronic healthcare record and/or a communication network |
US11246495B2 (en) | 2014-10-27 | 2022-02-15 | Vital Sines International Inc. | System and method for monitoring aortic pulse wave velocity and blood pressure |
US20160278664A1 (en) * | 2015-03-27 | 2016-09-29 | Intel Corporation | Facilitating dynamic and seamless breath testing using user-controlled personal computing devices |
US11329683B1 (en) | 2015-06-05 | 2022-05-10 | Life365, Inc. | Device configured for functional diagnosis and updates |
US9974492B1 (en) | 2015-06-05 | 2018-05-22 | Life365, Inc. | Health monitoring and communications device |
US10185513B1 (en) | 2015-06-05 | 2019-01-22 | Life365, Inc. | Device configured for dynamic software change |
US10560135B1 (en) | 2015-06-05 | 2020-02-11 | Life365, Inc. | Health, wellness and activity monitor |
US9786274B2 (en) | 2015-06-11 | 2017-10-10 | International Business Machines Corporation | Analysis of professional-client interactions |
US20160379668A1 (en) * | 2015-06-24 | 2016-12-29 | THINK'n Corp. | Stress reduction and resiliency training tool |
US10388411B1 (en) | 2015-09-02 | 2019-08-20 | Life365, Inc. | Device configured for functional diagnosis and updates |
US11265391B1 (en) * | 2016-06-21 | 2022-03-01 | Medtext Communications, LLC | Medical service provider rapid response system |
JP6145230B1 (en) * | 2016-06-30 | 2017-06-07 | 株式会社オプティム | Screen sharing remote examination system, screen sharing remote examination method, and screen sharing remote examination program |
US20180075373A1 (en) * | 2016-09-15 | 2018-03-15 | 911Care Llc | System and method for a care services marketplace |
US10916119B2 (en) | 2018-12-27 | 2021-02-09 | Hill-Rom Services, Inc. | System and method for caregiver availability determination |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216596A (en) * | 1987-04-30 | 1993-06-01 | Corabi International Telemetrics, Inc. | Telepathology diagnostic network |
US5634468A (en) * | 1992-04-03 | 1997-06-03 | Micromedical Industries Limited | Sensor patch and system for physiological monitoring |
US6144943A (en) * | 1997-10-21 | 2000-11-07 | Virginia Commonwealth University | Method of managing contract housekeeping services |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5724025A (en) * | 1993-10-21 | 1998-03-03 | Tavori; Itzchak | Portable vital signs monitor |
US5593426A (en) * | 1994-12-07 | 1997-01-14 | Heartstream, Inc. | Defibrillator system using multiple external defibrillators and a communications network |
JPH0947436A (en) * | 1995-08-09 | 1997-02-18 | Noboru Akasaka | Home medical system |
US5950632A (en) * | 1997-03-03 | 1999-09-14 | Motorola, Inc. | Medical communication apparatus, system, and method |
-
1999
- 1999-03-31 US US09/282,132 patent/US6302844B1/en not_active Expired - Lifetime
-
2001
- 2001-06-28 US US09/893,495 patent/US20010051765A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216596A (en) * | 1987-04-30 | 1993-06-01 | Corabi International Telemetrics, Inc. | Telepathology diagnostic network |
US5634468A (en) * | 1992-04-03 | 1997-06-03 | Micromedical Industries Limited | Sensor patch and system for physiological monitoring |
US6144943A (en) * | 1997-10-21 | 2000-11-07 | Virginia Commonwealth University | Method of managing contract housekeeping services |
Cited By (206)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020013538A1 (en) * | 1997-09-30 | 2002-01-31 | David Teller | Method and apparatus for health signs monitoring |
US20060143053A1 (en) * | 2001-07-31 | 2006-06-29 | Van Rensburg Frederick R | Insurance product |
US20030093299A1 (en) * | 2001-10-25 | 2003-05-15 | Siemens Aktiengesellschaft | Method and system for providing medical consulting services, with automatic remuneration to the service provider |
US20030171955A1 (en) * | 2002-03-07 | 2003-09-11 | Werblin Theodore Paul | Method and system for implementing and tracking cost-saving measures in hospitals and compensating physicians |
US7437303B2 (en) * | 2002-03-07 | 2008-10-14 | Physician Hospital Services, Llc | Method and system for implementing and tracking cost-saving measures in hospitals and compensating physicians |
EP1352608A2 (en) * | 2002-03-19 | 2003-10-15 | Colin Corporation | Diagnosis communication method |
EP1352608A3 (en) * | 2002-03-19 | 2003-11-19 | Colin Corporation | Diagnosis communication method |
US20030204563A1 (en) * | 2002-03-19 | 2003-10-30 | Colin Corporation | Diagnosis delivering method |
US7818180B2 (en) | 2002-04-29 | 2010-10-19 | Medtronic, Inc. | Personalization software for implanted medical device patients |
US20030204413A1 (en) * | 2002-04-29 | 2003-10-30 | Riff Kenneth M. | Personalization software for implanted medical device patients |
US20110046469A1 (en) * | 2003-06-10 | 2011-02-24 | Abbott Diabetes Care Inc. | Glucose Measuring Device for Use In Personal Area Network |
US20040259494A1 (en) * | 2003-06-23 | 2004-12-23 | Cardiac Pacemakers, Inc. | Systems, devices, and methods for selectively preventing data transfer from a medical device |
US7289761B2 (en) | 2003-06-23 | 2007-10-30 | Cardiac Pacemakers, Inc. | Systems, devices, and methods for selectively preventing data transfer from a medical device |
US9142923B2 (en) | 2003-08-21 | 2015-09-22 | Hill-Rom Services, Inc. | Hospital bed having wireless data and locating capability |
US8272892B2 (en) | 2003-08-21 | 2012-09-25 | Hill-Rom Services, Inc. | Hospital bed having wireless data capability |
US10206837B2 (en) | 2003-08-21 | 2019-02-19 | Hill-Rom Services, Inc. | Hospital bed and room communication modules |
US9925104B2 (en) | 2003-08-21 | 2018-03-27 | Hill-Rom Services, Inc. | Hospital bed and room communication modules |
US9572737B2 (en) | 2003-08-21 | 2017-02-21 | Hill-Rom Services, Inc. | Hospital bed having communication modules |
US9775519B2 (en) | 2004-08-02 | 2017-10-03 | Hill-Rom Services, Inc. | Network connectivity unit for hospital bed |
US11508469B2 (en) | 2004-08-02 | 2022-11-22 | Hill-Rom Services, Inc. | Hospital bed having wireless network connectivity |
US10098593B2 (en) | 2004-08-02 | 2018-10-16 | Hill-Rom Services, Inc. | Bed alert communication method |
US9336672B2 (en) | 2004-08-02 | 2016-05-10 | Hill-Rom Services, Inc. | Healthcare communication system for programming bed alarms |
US10070789B2 (en) | 2004-08-02 | 2018-09-11 | Hill-Rom Services, Inc. | Hospital bed having wired and wireless network connectivity |
US9513899B2 (en) | 2004-08-02 | 2016-12-06 | Hill-Rom Services, Inc. | System wide firmware updates to networked hospital beds |
US8120471B2 (en) | 2004-08-02 | 2012-02-21 | Hill-Rom Services, Inc. | Hospital bed with network interface unit |
US9517034B2 (en) | 2004-08-02 | 2016-12-13 | Hill-Rom Services, Inc. | Healthcare communication system for programming bed alarms |
US8421606B2 (en) | 2004-08-02 | 2013-04-16 | Hill-Rom Services, Inc. | Wireless bed locating system |
US9050031B2 (en) | 2004-08-02 | 2015-06-09 | Hill-Rom Services, Inc. | Healthcare communication system having configurable alarm rules |
US8866598B2 (en) | 2004-08-02 | 2014-10-21 | Hill-Rom Services, Inc. | Healthcare communication system with whiteboard |
US9861321B2 (en) | 2004-08-02 | 2018-01-09 | Hill-Rom Services, Inc. | Bed alarm communication system |
US8604917B2 (en) | 2004-08-02 | 2013-12-10 | Hill-Rom Services, Inc. | Hospital bed having user input to enable and suspend remote monitoring of alert conditions |
US8284047B2 (en) | 2004-08-02 | 2012-10-09 | Hill-Rom Services, Inc. | Wireless bed connectivity |
US10978191B2 (en) | 2004-08-02 | 2021-04-13 | Hill-Rom Services, Inc. | Healthcare communication method having configurable alarm rules |
US8917166B2 (en) | 2004-08-02 | 2014-12-23 | Hill-Rom Services, Inc. | Hospital bed networking system and method |
US10278582B2 (en) | 2004-08-02 | 2019-05-07 | Hill-Rom Services, Inc. | Hospital bed having wired and wireless network connectivity |
US8536990B2 (en) | 2004-08-02 | 2013-09-17 | Hill-Rom Services, Inc. | Hospital bed with nurse call system interface unit |
US10548475B2 (en) | 2004-08-02 | 2020-02-04 | Hill-Rom Services, Inc. | Method of hospital bed network connectivity |
US7852208B2 (en) | 2004-08-02 | 2010-12-14 | Hill-Rom Services, Inc. | Wireless bed connectivity |
US7746218B2 (en) | 2004-08-02 | 2010-06-29 | Hill-Rom Services, Inc. | Configurable system for alerting caregivers |
US8150509B2 (en) | 2004-10-21 | 2012-04-03 | Cardiac Pacemakers, Inc. | Systems and methods for drug therapy enhancement using expected pharmacodynamic models |
US20060089538A1 (en) * | 2004-10-22 | 2006-04-27 | General Electric Company | Device, system and method for detection activity of persons |
US20110307272A1 (en) * | 2005-10-24 | 2011-12-15 | CellTrak Technologies, Inc. | Home Health Point-of-Care and Administration System |
US20070150372A1 (en) * | 2005-12-19 | 2007-06-28 | Roy Schoenberg | Vendor and Consumer Matching |
US20100332261A1 (en) * | 2006-09-08 | 2010-12-30 | American Well Corporation, A Massachusetts Corporation | Connecting Consumers with Service Providers |
US9971873B2 (en) | 2006-09-08 | 2018-05-15 | American Well Corporation | Connecting consumers with service providers |
US20080065414A1 (en) * | 2006-09-08 | 2008-03-13 | Roy Schoenberg | Connecting Consumers with Service Providers |
US7848937B2 (en) | 2006-09-08 | 2010-12-07 | American Well Corporation | Connecting consumers with service providers |
US8738727B2 (en) | 2006-09-08 | 2014-05-27 | American Well Corporation | Connecting consumers with service providers |
US20080133511A1 (en) * | 2006-09-08 | 2008-06-05 | American Well Inc. | Connecting Consumers with Service Providers |
US7865377B2 (en) | 2006-09-08 | 2011-01-04 | American Well Corporation | Connecting consumers with service providers |
US20090313043A1 (en) * | 2006-09-08 | 2009-12-17 | American Well, Inc. A Delaware Corporation | Connecting Consumers with Service Providers |
US9652593B1 (en) | 2006-09-08 | 2017-05-16 | American Well Corporation | Search and retrieval of real-time terminal states maintained using a terminal state database |
US20090113312A1 (en) * | 2006-09-08 | 2009-04-30 | American Well Systems | Connecting Providers of Legal Services |
US20090063188A1 (en) * | 2006-09-08 | 2009-03-05 | American Well Systems | Connecting Consumers with Service Providers |
US7835928B2 (en) | 2006-09-08 | 2010-11-16 | American Well Corporation | Connecting consumers with service providers |
US8249898B2 (en) | 2006-09-08 | 2012-08-21 | American Well Corporation | Connecting consumers with service providers |
US9886551B2 (en) | 2006-09-08 | 2018-02-06 | American Well Corporation | Connecting consumers with service providers |
US20090138317A1 (en) * | 2006-09-08 | 2009-05-28 | Roy Schoenberg | Connecting Providers of Financial Services |
US20080166992A1 (en) * | 2007-01-10 | 2008-07-10 | Camillo Ricordi | Mobile emergency alert system |
US9578152B2 (en) | 2007-06-15 | 2017-02-21 | American Well Corporation | Telephonic-based engagements |
US9098840B2 (en) * | 2007-08-22 | 2015-08-04 | Siemens Aktiengesellschaft | System and method for providing and activating software licenses |
US20090076852A1 (en) * | 2007-08-22 | 2009-03-19 | Marc Pierson | System and method for an automated patient controlled system of health care provision and patient monitoring using personal health records |
US20090055320A1 (en) * | 2007-08-22 | 2009-02-26 | Georg Goertler | System and method for providing and activating software licenses |
US7868740B2 (en) | 2007-08-29 | 2011-01-11 | Hill-Rom Services, Inc. | Association of support surfaces and beds |
US8461968B2 (en) | 2007-08-29 | 2013-06-11 | Hill-Rom Services, Inc. | Mattress for a hospital bed for use in a healthcare facility and management of same |
US11574736B2 (en) | 2007-08-29 | 2023-02-07 | Hill-Rom Services, Inc. | Wireless bed and surface locating system |
US10886024B2 (en) | 2007-08-29 | 2021-01-05 | Hill-Rom Services, Inc. | Bed having housekeeping request button |
US10566088B2 (en) | 2007-08-29 | 2020-02-18 | Hill-Rom Services, Inc. | Wireless bed locating system |
US8604916B2 (en) | 2007-08-29 | 2013-12-10 | Hill-Rom Services, Inc. | Association of support surfaces and beds |
US8031057B2 (en) | 2007-08-29 | 2011-10-04 | Hill-Rom Services, Inc. | Association of support surfaces and beds |
US8510130B2 (en) | 2007-10-01 | 2013-08-13 | American Well Corporation | Documenting remote engagements |
US20090089086A1 (en) * | 2007-10-01 | 2009-04-02 | American Well Systems | Enhancing remote engagements |
US20110191119A1 (en) * | 2007-10-01 | 2011-08-04 | American Well Corporation, a Delaware corporation | Documenting Remote Engagements |
US20090089096A1 (en) * | 2007-10-01 | 2009-04-02 | American Well Systems | Documenting Remote Engagements |
US7933783B2 (en) | 2007-10-01 | 2011-04-26 | American Well Corporation | Medical listener |
US20100094659A1 (en) * | 2007-10-01 | 2010-04-15 | American Well Inc. | Consolidation of Consumer Interactions within a Medical Brokerage System |
US20110196699A1 (en) * | 2007-10-01 | 2011-08-11 | American Well Corporation, a Delaware corporation | Medical Listener |
US7945456B2 (en) | 2007-10-01 | 2011-05-17 | American Well Corporation | Documenting remote engagements |
US8515776B2 (en) | 2007-10-01 | 2013-08-20 | American Well Corporation | Medical listener |
US20090089085A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Managing Utilization |
US20090089074A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Identifying Trusted Providers |
US20090089098A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Identifying Clinical Trial Candidates |
US20090089084A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Auctioning Provider Prices |
US7890351B2 (en) | 2007-10-02 | 2011-02-15 | American Well Corporation | Managing utilization |
US20090089097A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Identification of Health Risks and Suggested Treatment Actions |
US7937275B2 (en) | 2007-10-02 | 2011-05-03 | American Well Corporation | Identifying clinical trial candidates |
US20110137683A1 (en) * | 2007-10-02 | 2011-06-09 | American Well Corporation, a Delaware corporation | Managing Utilization |
US20090089147A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Inc. | Provider supply & consumer demand management |
US7895061B2 (en) | 2007-10-02 | 2011-02-22 | American Well Corporation | Auctioning provider prices |
US7840418B2 (en) | 2007-10-02 | 2010-11-23 | American Well Corporation | Tracking the availability of service providers across multiple platforms |
US20110137756A1 (en) * | 2007-10-02 | 2011-06-09 | American Well Corporation, a Delaware corporation | Auctioning Provider Prices |
US8504382B2 (en) | 2007-10-02 | 2013-08-06 | American Well Corporation | Identifying trusted providers |
US8600773B2 (en) | 2007-10-02 | 2013-12-03 | American Well Corporation | Tracking the availability of service providers across multiple platforms |
US20090089090A1 (en) * | 2007-10-02 | 2009-04-02 | American Well Systems | Tracking the availability of service providers across multiple platforms |
US20110040569A1 (en) * | 2007-10-02 | 2011-02-17 | American Well Corporation, a Delaware corporation | Tracking the Availability of Service Providers Across Multiple Platforms |
US8521553B2 (en) | 2007-10-02 | 2013-08-27 | American Well Corporation | Identification of health risks and suggested treatment actions |
US20110004487A1 (en) * | 2007-10-22 | 2011-01-06 | American Well Corporation, A Massachusetts Corporation | Connecting Consumers with Service Providers |
US20090112623A1 (en) * | 2007-10-22 | 2009-04-30 | American Well Systems | Connecting Consumers with Service Providers |
US8510128B2 (en) | 2007-10-22 | 2013-08-13 | American Well Corporation | Connecting consumers with service providers |
US7818183B2 (en) | 2007-10-22 | 2010-10-19 | American Well Corporation | Connecting consumers with service providers |
US11031130B2 (en) | 2007-10-26 | 2021-06-08 | Hill-Rom Services, Inc. | Patient support apparatus having data collection and communication capability |
US9734293B2 (en) | 2007-10-26 | 2017-08-15 | Hill-Rom Services, Inc. | System and method for association of patient care devices to a patient |
US20090150252A1 (en) * | 2007-12-10 | 2009-06-11 | American Well Inc. | Connecting Service Providers And Consumers Of Services Independent Of Geographical Location |
US9955926B2 (en) | 2008-02-22 | 2018-05-01 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US8456286B2 (en) | 2008-02-22 | 2013-06-04 | Hill-Rom Services, Inc. | User station for healthcare communication system |
US8762766B2 (en) | 2008-02-22 | 2014-06-24 | Hill-Rom Services, Inc. | Distributed fault tolerant architecture for a healthcare communication system |
US9235979B2 (en) | 2008-02-22 | 2016-01-12 | Hill-Rom Services, Inc. | User station for healthcare communication system |
US11696731B2 (en) | 2008-02-22 | 2023-07-11 | Hill-Room Services, Inc. | Distributed healthcare communication method |
US9299242B2 (en) | 2008-02-22 | 2016-03-29 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US8803669B2 (en) | 2008-02-22 | 2014-08-12 | Hill-Rom Services, Inc. | User station for healthcare communication system |
US8392747B2 (en) | 2008-02-22 | 2013-03-05 | Hill-Rom Services, Inc. | Distributed fault tolerant architecture for a healthcare communication system |
US10307113B2 (en) | 2008-02-22 | 2019-06-04 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US8598995B2 (en) | 2008-02-22 | 2013-12-03 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US11058368B2 (en) | 2008-02-22 | 2021-07-13 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US11944467B2 (en) | 2008-02-22 | 2024-04-02 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US8169304B2 (en) | 2008-02-22 | 2012-05-01 | Hill-Rom Services, Inc. | User station for healthcare communication system |
US8046625B2 (en) | 2008-02-22 | 2011-10-25 | Hill-Rom Services, Inc. | Distributed fault tolerant architecture for a healthcare communication system |
US10638983B2 (en) | 2008-02-22 | 2020-05-05 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US9517035B2 (en) | 2008-02-22 | 2016-12-13 | Hill-Rom Services, Inc. | Distributed healthcare communication system |
US8384526B2 (en) | 2008-02-22 | 2013-02-26 | Hill-Rom Services, Inc. | Indicator apparatus for healthcare communication system |
US20110184763A1 (en) * | 2008-04-07 | 2011-07-28 | American Well Corp., a Delaware corporation | Continuity of Medical Care |
US20090254361A1 (en) * | 2008-04-07 | 2009-10-08 | American Well Inc. | Continuity of Medical Care |
US8639532B2 (en) | 2008-04-07 | 2014-01-28 | American Well Corporation | Continuity of medical care |
US7912737B2 (en) | 2008-04-07 | 2011-03-22 | American Well Corporation | Continuity of medical care |
US20090262919A1 (en) * | 2008-04-18 | 2009-10-22 | American Well Inc. | Establishment of a Telephone Based Engagement |
US7890345B2 (en) | 2008-04-18 | 2011-02-15 | American Well Corporation | Establishment of a telephone based engagement |
US20090313076A1 (en) * | 2008-06-17 | 2009-12-17 | Roy Schoenberg | Arranging remote engagements |
US20130054288A1 (en) * | 2008-06-17 | 2013-02-28 | American Well Corporation | Arranging remote engagements |
US20090319296A1 (en) * | 2008-06-17 | 2009-12-24 | Roy Schoenberg | Patient Directed Integration Of Remotely Stored Medical Information With A Brokerage System |
US8719047B2 (en) | 2008-06-17 | 2014-05-06 | American Well Corporation | Patient directed integration of remotely stored medical information with a brokerage system |
US20110313257A1 (en) * | 2008-12-19 | 2011-12-22 | Klaus Abraham-Fuchs | Method for Recording and Evaluation of Measurements Related to the Condition of a Patient for Configuration of a Portable, Patient-Controlled Device Operated to Record Said Measurements and Related Device |
US20100222649A1 (en) * | 2009-03-02 | 2010-09-02 | American Well Systems | Remote medical servicing |
US20100293007A1 (en) * | 2009-05-18 | 2010-11-18 | Roy Schoenberg | Provider Decision Support |
US9015609B2 (en) | 2009-05-18 | 2015-04-21 | American Well Corporation | Provider to-provider consultations |
US20100293487A1 (en) * | 2009-05-18 | 2010-11-18 | Roy Schoenberg | Provider-to-provider Consultations |
US8463620B2 (en) | 2009-07-08 | 2013-06-11 | American Well Corporation | Connecting consumers with service providers |
US20110010197A1 (en) * | 2009-07-08 | 2011-01-13 | Roy Schoenberg | Connecting Consumers with Service Providers |
US20110106593A1 (en) * | 2009-10-30 | 2011-05-05 | Roy Schoenberg | Coupon Codes |
US10686857B2 (en) | 2010-02-09 | 2020-06-16 | Roy Schoenberg | Connecting consumers with providers of live videos |
US8694612B1 (en) | 2010-02-09 | 2014-04-08 | Roy Schoenberg | Connecting consumers with providers of live videos |
US10341402B1 (en) * | 2010-02-09 | 2019-07-02 | Roy Schoenberg | Connecting consumers with providers of live videos |
US9787737B1 (en) | 2010-02-09 | 2017-10-10 | Roy Schoenberg | Connecting consumers with providers of live videos |
US8779924B2 (en) | 2010-02-19 | 2014-07-15 | Hill-Rom Services, Inc. | Nurse call system with additional status board |
US20110245633A1 (en) * | 2010-03-04 | 2011-10-06 | Neumitra LLC | Devices and methods for treating psychological disorders |
US20110224998A1 (en) * | 2010-03-10 | 2011-09-15 | Roy Schoenberg | Online Care For Provider Practices |
US9164801B2 (en) | 2010-06-08 | 2015-10-20 | International Business Machines Corporation | Probabilistic optimization of resource discovery, reservation and assignment |
US9646271B2 (en) | 2010-08-06 | 2017-05-09 | International Business Machines Corporation | Generating candidate inclusion/exclusion cohorts for a multiply constrained group |
US8968197B2 (en) * | 2010-09-03 | 2015-03-03 | International Business Machines Corporation | Directing a user to a medical resource |
US20120059227A1 (en) * | 2010-09-03 | 2012-03-08 | International Business Machines Corporation | Directing a user to a medical resource |
US9292577B2 (en) | 2010-09-17 | 2016-03-22 | International Business Machines Corporation | User accessibility to data analytics |
US11024432B2 (en) | 2010-12-15 | 2021-06-01 | Ross Medical Corporation | Patient emergency response system |
US10380324B2 (en) | 2010-12-15 | 2019-08-13 | Ross Medical Corporation | Patient emergency response system |
US11574744B2 (en) | 2010-12-15 | 2023-02-07 | Ross Medical Corporation | Patient emergency response system |
US20120173272A1 (en) * | 2010-12-31 | 2012-07-05 | Julian Omidi | Automated System and Method for Processing Obesity Patients |
US20120290638A1 (en) * | 2011-05-13 | 2012-11-15 | Dhiraj Narula | Physician regional access networking agent |
US20130116526A1 (en) * | 2011-11-09 | 2013-05-09 | Telcare, Inc. | Handheld Blood Glucose Monitoring Device with Messaging Capability |
US9411934B2 (en) | 2012-05-08 | 2016-08-09 | Hill-Rom Services, Inc. | In-room alarm configuration of nurse call system |
EP2704045A3 (en) * | 2012-08-31 | 2017-07-26 | Fujifilm Corporation | Apparatus and method for providing medical support |
US11887728B2 (en) | 2012-09-20 | 2024-01-30 | Masimo Corporation | Intelligent medical escalation process |
US10833983B2 (en) * | 2012-09-20 | 2020-11-10 | Masimo Corporation | Intelligent medical escalation process |
US20170228516A1 (en) * | 2012-09-20 | 2017-08-10 | Masimo Corporation | Intelligent medical escalation process |
US10136815B2 (en) | 2012-09-24 | 2018-11-27 | Physio-Control, Inc. | Patient monitoring device with remote alert |
US11457808B2 (en) | 2012-09-24 | 2022-10-04 | Physio-Control, Inc. | Patient monitoring device with remote alert |
US9678636B2 (en) | 2013-01-17 | 2017-06-13 | American Well Corporation | Modalities for brokered engagements |
US20140214828A1 (en) * | 2013-01-28 | 2014-07-31 | International Business Machines Corporation | Data caveats for database tables |
US20140214827A1 (en) * | 2013-01-28 | 2014-07-31 | International Business Machines Corporation | Data Caveats for Database Tables |
US8990205B2 (en) * | 2013-01-28 | 2015-03-24 | International Business Machines Corporation | Data caveats for database tables |
US8996521B2 (en) * | 2013-01-28 | 2015-03-31 | International Business Machines Corporation | Data caveats for database tables |
US11576576B2 (en) * | 2013-03-15 | 2023-02-14 | Zoll Medical Corporation | Patient monitor screen aggregation |
US20220031163A1 (en) * | 2013-03-15 | 2022-02-03 | Zoll Medical Corporation | Patient monitor screen aggregation |
US10412028B1 (en) * | 2013-05-24 | 2019-09-10 | HCA Holdings, Inc. | Data derived user behavior modeling |
US10812426B1 (en) * | 2013-05-24 | 2020-10-20 | C/Hca, Inc. | Data derived user behavior modeling |
US11711327B1 (en) | 2013-05-24 | 2023-07-25 | C/Hca, Inc. | Data derived user behavior modeling |
US11894143B2 (en) | 2013-08-27 | 2024-02-06 | Whiskers Worldwide, LLC | System and methods for integrating animal health records |
US11894144B2 (en) | 2013-08-27 | 2024-02-06 | Whiskers Worldwide, LLC | Animal health decision support system and methods |
US10629304B2 (en) | 2013-08-27 | 2020-04-21 | Whiskers Worldwide, LLC | Systems and methods for decision support for animal health queries |
US11011267B2 (en) | 2013-09-18 | 2021-05-18 | Hill-Rom Services, Inc. | Bed/room/patient association systems and methods |
US9830424B2 (en) | 2013-09-18 | 2017-11-28 | Hill-Rom Services, Inc. | Bed/room/patient association systems and methods |
US11699526B2 (en) | 2013-10-11 | 2023-07-11 | Masimo Corporation | Alarm notification system |
US11488711B2 (en) | 2013-10-11 | 2022-11-01 | Masimo Corporation | Alarm notification system |
US10825568B2 (en) | 2013-10-11 | 2020-11-03 | Masimo Corporation | Alarm notification system |
US10832818B2 (en) | 2013-10-11 | 2020-11-10 | Masimo Corporation | Alarm notification system |
WO2015057667A1 (en) * | 2013-10-14 | 2015-04-23 | Rest Devices, Inc. | Network-based care system |
US20150105608A1 (en) * | 2013-10-14 | 2015-04-16 | Rest Devices, Inc. | Infant Sleeping Aid and Infant-Bed Accessory |
US20150154880A1 (en) * | 2013-12-02 | 2015-06-04 | Aetna Inc. | Healthcare management with a support network |
EP3082583A4 (en) * | 2013-12-19 | 2017-08-23 | OpenTV, Inc. | Remote health care via a television communication system |
WO2015095655A1 (en) * | 2013-12-19 | 2015-06-25 | Opentv, Inc. | Remote health care via a television communication system |
US10741292B2 (en) * | 2014-06-13 | 2020-08-11 | Vet24seven Inc. | Remote medical analysis |
US20150363564A1 (en) * | 2014-06-13 | 2015-12-17 | Vet24seven Inc. | Remote Medical Analysis |
US10268989B2 (en) * | 2015-04-20 | 2019-04-23 | Murj, Inc. | Medical device data platform |
US20170017769A1 (en) * | 2015-07-14 | 2017-01-19 | Xerox Corporation | Methods and systems for predicting a health condition of a human subject |
US10448898B2 (en) * | 2015-07-14 | 2019-10-22 | Conduent Business Services, Llc | Methods and systems for predicting a health condition of a human subject |
WO2017064827A1 (en) * | 2015-10-13 | 2017-04-20 | Sony Corporation | System and method for providing assistance during medical emergency |
US10460074B2 (en) * | 2016-04-05 | 2019-10-29 | Conduent Business Services, Llc | Methods and systems for predicting a health condition of a human subject |
US10468136B2 (en) * | 2016-08-29 | 2019-11-05 | Conduent Business Services, Llc | Method and system for data processing to predict health condition of a human subject |
US11289200B1 (en) | 2017-03-13 | 2022-03-29 | C/Hca, Inc. | Authorized user modeling for decision support |
US11504061B2 (en) | 2017-03-21 | 2022-11-22 | Stryker Corporation | Systems and methods for ambient energy powered physiological parameter monitoring |
US11484241B2 (en) | 2017-12-06 | 2022-11-01 | General Electric Company | System and methods for qualification of ECG data for remote analysis |
EP3720347A4 (en) * | 2017-12-06 | 2021-08-25 | General Electric Company | System and methods for qualification of ecg data for remote analysis |
US11844634B2 (en) | 2018-04-19 | 2023-12-19 | Masimo Corporation | Mobile patient alarm display |
US11109818B2 (en) | 2018-04-19 | 2021-09-07 | Masimo Corporation | Mobile patient alarm display |
US11670427B2 (en) | 2018-12-04 | 2023-06-06 | Mycare Integrated Software Solutions, LLC | Remote healthcare communication systems and methods |
US11911325B2 (en) | 2019-02-26 | 2024-02-27 | Hill-Rom Services, Inc. | Bed interface for manual location |
CN110840425A (en) * | 2019-11-20 | 2020-02-28 | 首都医科大学宣武医院 | Health monitoring system and method for emergency patients in diagnosis |
US11948680B2 (en) | 2022-03-15 | 2024-04-02 | Murj, Inc. | Systems and methods to distribute cardiac device advisory data |
US11955236B2 (en) | 2022-06-28 | 2024-04-09 | Murj, Inc. | Systems and methods for managing patient medical devices |
Also Published As
Publication number | Publication date |
---|---|
US6302844B1 (en) | 2001-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6302844B1 (en) | Patient care delivery system | |
Dávalos et al. | Economic evaluation of telemedicine: review of the literature and research guidelines for benefit–cost analysis | |
US8489420B2 (en) | Method of optimizing healthcare services consumption | |
EP1331874B1 (en) | A health outcomes and disease management network for providing improved patient care | |
US20070073555A1 (en) | System and process for facilitating the provision of health care | |
US20080306762A1 (en) | System and Method for Managing Absenteeism in an Employee Environment | |
US20170300647A1 (en) | Health In Your Hands | |
US20050197545A1 (en) | System and method for disease management | |
US20040128161A1 (en) | System and method for ad hoc communications with an implantable medical device | |
US20080065416A1 (en) | Repeater Providing Data Exchange With A Medical Device For Remote Patient Care And Method Thereof | |
US20080306763A1 (en) | System and Method for Modifying Risk Factors by a Healthcare Individual at a Remote Location | |
US20210343381A1 (en) | Healthcare data system | |
EP1199670A2 (en) | Medical diagnosis system and diagnosis-processing method thereof | |
US20100100395A1 (en) | Method for high-risk member identification | |
US20030028442A1 (en) | Method of supplying heart screening services directly to a customer | |
de Lusignan et al. | A Controlled Pilot Study in the Use of Telemedicine in the Community on the Management of Heart Failure-a report of the first three months | |
US10622106B2 (en) | Method of optimizing healthcare services consumption | |
WO2013109973A1 (en) | System, method and computer program product for customer-selected care path for treatment of a medical condition | |
Kashem et al. | Management of heart failure patients using telemedicine communication systems | |
US20170046500A1 (en) | System to give doctors and patients easier access to each other | |
JP6819979B1 (en) | Medical Nursing Delivery Methods, Systems and Programs | |
US11482313B2 (en) | Method of optimizing healthcare services consumption | |
Trippi et al. | Dobutamine Stress Tele‐Echocardiography as a Clinical Service in the Emergency Department to Evaluate Patients With Chest Pain | |
AU2004286362B2 (en) | System and process for facilitating the provision of health care | |
Maglaveras et al. | Quality home telemedicine services for chronic cardiac disease patients through the INTERLIFE platform |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: JSW INVESTMENTS, LLC, CONNECTICUT Free format text: SECURITY INTEREST;ASSIGNOR:WALKER DIGITAL, LLC;REEL/FRAME:013740/0219 Effective date: 20021226 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: WALKER DIGITAL, LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JSW INVESTMENTS, LLC;REEL/FRAME:017783/0080 Effective date: 20050527 |
|
AS | Assignment |
Owner name: WALKER DIGITAL, LLC, CONNECTICUT Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:JSW INVESTMENTS, LLC;REEL/FRAME:018668/0615 Effective date: 20050527 |