WO2017055128A1 - Context input for pulse oximeter - Google Patents

Context input for pulse oximeter Download PDF

Info

Publication number
WO2017055128A1
WO2017055128A1 PCT/EP2016/072211 EP2016072211W WO2017055128A1 WO 2017055128 A1 WO2017055128 A1 WO 2017055128A1 EP 2016072211 W EP2016072211 W EP 2016072211W WO 2017055128 A1 WO2017055128 A1 WO 2017055128A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
patient
pulse oximeter
acquired
physiological data
Prior art date
Application number
PCT/EP2016/072211
Other languages
French (fr)
Inventor
John Cronin
Joseph George Bodkin
Original Assignee
Koninklijke Philips N.V.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Koninklijke Philips N.V. filed Critical Koninklijke Philips N.V.
Publication of WO2017055128A1 publication Critical patent/WO2017055128A1/en

Links

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
    • 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/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/0205—Simultaneously evaluating both cardiovascular conditions and different types of body conditions, e.g. heart and respiratory condition
    • 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/02416—Detecting, measuring or recording pulse rate or heart rate using photoplethysmograph signals, e.g. generated by infrared radiation
    • 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/1455—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 using optical sensors, e.g. spectral photometrical oximeters
    • A61B5/14551—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 using optical sensors, e.g. spectral photometrical oximeters for measuring blood gases
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/74—Details of notification to user or communication with user or patient ; user input means
    • A61B5/746—Alarms related to a physiological condition, e.g. details of setting alarm thresholds or avoiding false alarms
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/74—Details of notification to user or communication with user or patient ; user input means
    • A61B5/7475—User input or interface means, e.g. keyboard, pointing device, joystick
    • 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
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/20—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for electronic clinical trials or questionnaires
    • 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
    • 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/30—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for calculating health indices; for individual health risk assessment
    • 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/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients

Definitions

  • Patient monitoring is an essential aspect of hospitals, emergency rooms, intensive care units, surgery rooms, nursing homes, and doctors' offices. It involves the use of health monitoring devices such as thermometers, sphygmomanometers, and pulse oximeters.
  • health monitoring devices such as thermometers, sphygmomanometers, and pulse oximeters.
  • a pulse oximeter is used to measure oxygen saturation level and perfusion index to aid in determining a patient's health status or condition.
  • Pulse oximetry is an effective method of monitoring of and acquiring oxygen saturation (Sp0 2 ) level and perfusion index of a patient. It is very useful in many situations where monitoring a patient's oxygenation level is important. However, the accuracy and reliability of pulse oximeter measurements require consideration of the physiological condition of the patient. Inaccurate pulse oximeter measurements may lead to false assessments on the patient's health.
  • the medical personnel can properly assess the health status of the patient by adding contextual data. In determining the patient's health status, the medical personnel may also analyze the correlation of the pulse oximeter data with the other physiological measurements, symptoms being experienced by the patient, and drugs being administered to the patient. SUMMARY OF THE CLAIMED INVENTION
  • An embodiment of the present invention relates to systems and methods for triggering an alert concerning a patient using a patient monitoring device.
  • the method of the present invention comprises acquiring pulse oximeter data and physiological data at a set time interval using a pulse oximeter and at least one medical device connected to the pulse oximeter, respectively. At least one symptom experienced by the patient and at least one drug administered to the patient are selected via a user interface.
  • a graph is generated using at least one of the acquired pulse oximeter data and the acquired physiological data.
  • a marker is added on the displayed graph, wherein the marker corresponds to data representing at least one of the time interval during which the at least one symptom is experienced by the patient and the time the at least one drug is administered to the patient.
  • An alert is then triggered by matching a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in an alert threshold range database.
  • a physician database is updated by uploading the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient.
  • a cloud database is accessed to acquire information on one or more effects of the at least one drug administered to the patient.
  • An embodiment of the present invention also relates to a system comprising a pulse oximeter for acquiring pulse oximeter data, an at least one medical device for acquiring physiological data, a user interface for selecting at least one symptom experienced by the patient and at least one drug administered to the patient, a display device for displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data, an alert threshold range database for storing thresholds corresponding to a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data, a physician database for storing the acquired
  • physiological data the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient, and a cloud database for storing information on one or more effects of the at least one drug administered to the patient.
  • FIG. 1 illustrates a block diagram of a system for triggering an alert using a patient monitoring device.
  • FIG. 2 illustrates a flowchart according to a preferred embodiment of the present invention.
  • FIG. 3 illustrates an exemplary display in accordance with an embodiment of the invention.
  • FIG. 4 illustrates an exemplary user interface in accordance with an
  • FIG. 5 illustrates an exemplary user interface in accordance with an embodiment of the invention.
  • FIG. 6 illustrates an exemplary alert range threshold database in accordance with an embodiment of the invention.
  • FIG. 7 illustrates a flowchart describing a software for adding user-provided context information to at least of the acquired pulse oximeter data and the acquired physiological data.
  • FIG. 8 illustrates a flowchart describing a software for adding an audio note.
  • FIG. 9 illustrates a flowchart describing a software for prompting a user to select a symptom being experienced.
  • FIG. 10 illustrates a flowchart describing a software for triggering an alert
  • FIG. 11 illustrates an exemplary physician database in accordance with an embodiment of the invention.
  • An embodiment of the present invention relates to a method for triggering an alert concerning a patient (user) using a patient monitoring device comprising: acquiring pulse oximeter data at a set time interval using a pulse oximeter; acquiring physiological data at a set time interval using an at least one medical device connected to the pulse oximeter; selecting via a user interface at least one symptom experienced by the patient and at least one drug administered to the patient; displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data; adding a marker on the displayed graph, wherein the marker corresponds to data representing at least one of the time interval during which the at least one symptom is experienced by the patient and the time the at least one drug is administered to the patient; triggering an alert by matching a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in an alert threshold range database; updating a physician database by uploading the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by
  • An embodiment of the present invention also relates to a system for triggering an alert using a patient monitoring device comprising: a pulse oximeter for acquiring pulse oximeter data, an at least one medical device for acquiring physiological data, a user interface for selecting at least one symptom experienced by the patient and at least one drug administered to the patient, a display device for displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data, an alert threshold range database for storing thresholds corresponding to a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data, a physician database for storing the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient, and a cloud database for storing information on one or more effects of the at least one drug administered to the patient.
  • a typical pulse oximeter comprises an electronic processor and a couple of small light- emitting diodes (LEDs) facing a photodiode through a translucent portion of a patient's body, typically a fingertip or an earlobe.
  • LEDs small light- emitting diodes
  • One of the LEDs emits light in the red portion of the visible region of the electromagnetic spectrum (red LED) while the other emits in the infrared region.
  • the amount of light absorbed at these two wavelengths differs significantly between oxygen- rich blood and blood deficient in oxygen.
  • Oxygenated hemoglobin absorbs more infrared light and allows more red light to pass through.
  • deoxygenated hemoglobin allows more infrared light to pass through and absorbs more red light.
  • Oxy-hemoglobin and its deoxygenated form have significantly different absorption pattern.
  • the LEDs alternately turn on and off, and then both off approximately for a predetermined period of time.
  • the amount of light that is transmitted (that is, not absorbed) is measured, and separate normalized signals are produced for each wavelength.
  • FIG. 1 illustrates a preferred embodiment of a system for triggering an alert using a patient monitoring device.
  • a pulse oximeter 100 is provided to which an at least one medical device 102 is connected.
  • the pulse oximeter 100 is connected to a patient monitoring device 104 which is communicably connected to a physician database 106, an alert threshold range database 108, and a cloud database 110.
  • the pulse oximeter 100 comprises a first processor 112, a first communications module 114, and a first memory 116.
  • Each of the at least one medical device 102 comprises a second communications module 118 and second memory_120.
  • the patient monitoring device 104 comprises a display 122, a user interface 124, a third processor 126, a third_communications module 128, a third_memory 130, and a clock 132.
  • FIG. 2 illustrates a preferred method of the present invention.
  • Pulse oximeter data are acquired at a set time interval using the pulse oximeter 100 (step 200).
  • pulse oximetry data include Sp0 2 level, pulse rate, and perfusion index, among others, of the patient.
  • the pulse oximetry data are then stored in the memory 116.
  • physiological data are acquired at the set time interval using the at least one medical device 102 (step 202).
  • the at least one medical device 102 is connected to the pulse oximeter 100 via communications modules 114 and 118.
  • physiological data include respiratory rate, body temperature and blood pressure, among others, of the patient.
  • the physiological data are then stored in the memory 120.
  • the stored physiological data are transmitted, via the communications modules 114 and 118, to the pulse oximeter 100 and are stored in the memory 116.
  • a user is able, via a user interface 124, to provide information regarding an occurring event (step 204).
  • information can be a symptom experienced by the patient or a drug administered to the patient.
  • a patient monitoring device 104 retrieves the acquired pulse oximeter data and acquired physiological data via the communications modules 114 and 128.
  • a graph is generated by the patient monitoring device using at least one of the acquired pulse oximeter data and the acquired physiological data.
  • the generated graph is presented via display 122 (step 206).
  • at least one of the acquired pulse oximeter data and the acquired physiological data is plotted as a function of time.
  • a marker is then added on the displayed graph, wherein the marker corresponds to data representing the user-provided context information (step 208).
  • the data representing the user-provided context information can be the time interval during which a symptom is experienced by the patient or the time at which a drug is administered to the patient.
  • the medical personnel may choose to select antiarrhythmic medicine. Subsequently, the time-dependent graph for the patient's blood oxygen saturation levels is displayed with the marker overlaying the time-dependent graph to allow the medical personnel to analyze the correlation and possible effects of the anti-arrhythmic medicine to the patient's blood oxygen saturation levels.
  • the patient monitoring device 104 accesses an alert threshold range database 108 via the communications module 126.
  • the alert threshold range database 108 contains threshold ranges for pulse oximeter data and physiological data.
  • the threshold ranges in the alert threshold range database 108 correspond to different
  • the threshold ranges are set by the user (e.g., patient) via the user interface 124. Threshold ranges used during data acquisition are adjusted accordingly by matching the combination of at least two of the symptoms being experienced by the patient, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in the alert threshold range database 108. An alert is then triggered when at least one of the acquired pulse oximetry data and the acquired physiological data reaches (falls within) the adjusted threshold (step 210).
  • the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient are transmitted via the communications module 128 to be stored to a physician database 106 (step 212).
  • a cloud database 110 can be accessed to acquire, and the cloud database 110 provides, information on one or more effects of the at least one drug administered to the patient (step 214).
  • FIG. 3 illustrates an exemplary display 122 described in the present invention.
  • a display graph 300 shows a graph of at least one of the acquired pulse oximeter data and the acquired physiological data versus time. This display graph 300 enables the medical practitioner to view the acquired pulse oximeter data and the acquired physiological data over time (previously acquired data) as well as the line trend of the acquired data.
  • the current numerical values of the currently acquired pulse oximeter data and acquired physiological data are displayed on a readings display 302.
  • the graph of Sp0 2 levels and pulse rate are displayed in the display graph 300 and the current Sp0 2 levels, pulse rate, and perfusion index are displayed in the readings display 302.
  • an options display 304 is provided on the display 122 to allow the user to select the at least one drug administered to a patient.
  • an "Audio Note” button 306 is provided on the display 122 to allow the user to add an audio note for the acquired pulse oximeter data and the acquired physiological data. Once an option is selected via the options display 304 or an audio note is added via the "Audio Note” button 306, a marker is overlaid on the time-dependent graph displayed on the display graph 300.
  • FIG. 4 illustrates an exemplary user interface 124 described in the present invention.
  • the user interface 124 allows the user to select at least one symptom being experienced by the patient.
  • the at least one symptom can be selected from the list comprising shortness of breath, tiredness, sweatiness, coughing, and wheezing.
  • a marker is overlaid on the time-dependent graph displayed on the display graph 300.
  • the user interface 124 may be integrated in a hand-held device, which a patient can readily access when the patient is experiencing a symptom.
  • the hand-held device is preferably connected to the patient monitoring device 104 via the communications module 128.
  • the user is prompted to select a symptom via the user interface 124 if at least one of the acquired pulse oximeter data and the acquired
  • physiological data reaches a threshold range.
  • FIG. 5 illustrates another exemplary user interface 124 described in the present invention.
  • the user interface 124 allows the user to set the threshold ranges for at least one of the pulse oximetry data and the physiological data corresponding to at least one symptom being experienced by the patient.
  • the user sets the base threshold ranges for Sp0 2 levels and pulse rate. This is used as the default thresholds during data acquisition.
  • the user also sets the threshold ranges for Sp0 2 levels and pulse rate that corresponds to a patient's symptoms.
  • the threshold ranges used during data acquisition are automatically adjusted according to the user set thresholds once a symptom is selected via the user interface 124.
  • the set threshold ranges are stored and can be accessed in the alert threshold range database.
  • An example of the alert threshold range database 108 is shown in FIG. 6.
  • FIG. 7 illustrates a "Context Software" for adding a user-provided context information to at least one of the acquired pulse oximeter data and the acquired physiological data described in the present invention.
  • At least one set of pulse oximeter data are measured using the pulse oximeter 100 (step 700).
  • the pulse oximeter 100 polls for at least one connected medical device 102 (step 702). If at least one medical device 102 is detected, the pulse oximeter 100 sends a request for at least one set of physiological data stored in the memory 120 of at least one of the detected medical devices 102 (step 704). Subsequently, the pulse oximeter 100 receives the requested at least one set of physiological data and stores the received data in memory 116 (step 706).
  • At least one of the acquired pulse oximetry data and the acquired physiological data are then sent to the patient monitoring device 104 (step 708). If there were no medical devices 102 detected, the at least one acquired pulse oximetry data are sent to the patient monitoring device 104 (step 708).
  • the "Context Software” illustrated in FIG. 7 determines if a user - provided any context information - drug administered, symptom being experienced, and audio note (step 710). If a user-provided context information, the "Context Software” determines if the context information was an audio note (step 712). If so, an "Audio
  • the software initializes. Once the "Audio Software" run is finished, the system continues running the "Context Software". If the context information is not an audio note, the software associates the user-provided context information with at least one of the acquired pulse oximetry data and the acquired physiological data. For both scenarios corresponding to the presence and absence of user-provided context information, a timestamp is added accordingly (step 714). The "Context Software” then proceeds to storing all data to the physician database 106 (step 716). The "Context Software” also determines if a network is available (step 718). In the case where a network is available, all data are sent to the cloud database 110 (step 720). The software then loops back to acquire at least one set of pulse oximeter data (step 700). If there were no networks available, the software just loops back to acquire at least one set of pulse oximeter data (step 700).
  • FIG. 8 illustrates the "Audio Software” for adding an audio note as described previously.
  • the "Audio Software” initializes once a user chooses to add an audio note via the "Audio Note” button 306 on the display 122.
  • the microphone is activated (step 800).
  • An audio recording is then acquired (step 802).
  • the audio recording is stored in the memory 130 (step 804).
  • the audio recording is converted to text (step 806).
  • the system connects to a network in order to convert the audio file to text.
  • FIG. 9 illustrates the "Monitoring Software” for prompting a user to select a symptom being experienced as described in the present invention.
  • At least one set of pulse oximeter data and at least one set of physiological data are acquired using the pulse oximeter 100 and the at least one medical device 102, respectively (step 900).
  • the system accesses the alert threshold range database 108 and determines if any of the acquired pulse oximeter data and the acquired physiological data reaches a threshold range.
  • the system loops back to acquire at least one set of pulse oximeter data and at least one set of physiological data (step 900). Otherwise, the user is prompted to select at least one symptom being experienced (step 904). The user then selects at least one symptom being experienced via the user interface 124. The at least one selected symptom being experienced is associated with the most recent at least one set of pulse oximeter data and at least one set of physiological data (step 906) and is stored in the physician database 106 (step 908). Afterwards, the "Monitoring Software" proceeds to the "Alert Software.”
  • FIG. 10 illustrates the "Alert Software" for triggering an alert as described by the present invention.
  • At least one set of pulse oximeter data and at least one set of physiological data are acquired using the pulse oximeter 100 and the at least one medical device 102, respectively (step 1000).
  • the system also acquires at least one symptom being experienced by the patient.
  • the system accesses the alert threshold range database 108 and determines if any of the acquired pulse oximeter data and the acquired physiological data reaches a threshold range. If at least one of the acquired pulse oximeter data and acquired physiological data reaches a threshold range, an alert is triggered to notify a medical personnel. Otherwise, the "Alert Software" is terminated.
  • FIG. 11 illustrates an exemplary physician database 106 as described in the present invention.
  • the physician database 106 stores the patient ID, timestamp, symptom being experienced by the patient, drug administered to the patient, at least one set of pulse oximetry data and at least one set of physiological data.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Public Health (AREA)
  • Medical Informatics (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • Pathology (AREA)
  • Biophysics (AREA)
  • Heart & Thoracic Surgery (AREA)
  • Molecular Biology (AREA)
  • Surgery (AREA)
  • Animal Behavior & Ethology (AREA)
  • Veterinary Medicine (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Physiology (AREA)
  • Cardiology (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Pulmonology (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Optics & Photonics (AREA)
  • Measurement Of The Respiration, Hearing Ability, Form, And Blood Characteristics Of Living Organisms (AREA)

Abstract

The present invention relates to systems and methods for triggering an alert concerning a patient using a patient monitoring device. The method of the present invention comprises acquiring pulse oximeter data and physiological data at a set time interval using a pulse oximeter and at least one medical device connected to the pulse oximeter, respectively.

Description

Context input for pulse oximeter
BACKGROUND OF THE INVENTION
Patient monitoring is an essential aspect of hospitals, emergency rooms, intensive care units, surgery rooms, nursing homes, and doctors' offices. It involves the use of health monitoring devices such as thermometers, sphygmomanometers, and pulse oximeters. One example of non-invasive monitoring devices is a pulse oximeter, which is used to measure oxygen saturation level and perfusion index to aid in determining a patient's health status or condition.
Pulse oximetry is an effective method of monitoring of and acquiring oxygen saturation (Sp02) level and perfusion index of a patient. It is very useful in many situations where monitoring a patient's oxygenation level is important. However, the accuracy and reliability of pulse oximeter measurements require consideration of the physiological condition of the patient. Inaccurate pulse oximeter measurements may lead to false assessments on the patient's health.
The medical personnel can properly assess the health status of the patient by adding contextual data. In determining the patient's health status, the medical personnel may also analyze the correlation of the pulse oximeter data with the other physiological measurements, symptoms being experienced by the patient, and drugs being administered to the patient. SUMMARY OF THE CLAIMED INVENTION
An embodiment of the present invention relates to systems and methods for triggering an alert concerning a patient using a patient monitoring device. The method of the present invention comprises acquiring pulse oximeter data and physiological data at a set time interval using a pulse oximeter and at least one medical device connected to the pulse oximeter, respectively. At least one symptom experienced by the patient and at least one drug administered to the patient are selected via a user interface. A graph is generated using at least one of the acquired pulse oximeter data and the acquired physiological data. A marker is added on the displayed graph, wherein the marker corresponds to data representing at least one of the time interval during which the at least one symptom is experienced by the patient and the time the at least one drug is administered to the patient. An alert is then triggered by matching a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in an alert threshold range database. Thereafter, a physician database is updated by uploading the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient. A cloud database is accessed to acquire information on one or more effects of the at least one drug administered to the patient.
An embodiment of the present invention also relates to a system comprising a pulse oximeter for acquiring pulse oximeter data, an at least one medical device for acquiring physiological data, a user interface for selecting at least one symptom experienced by the patient and at least one drug administered to the patient, a display device for displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data, an alert threshold range database for storing thresholds corresponding to a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data, a physician database for storing the acquired
physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient, and a cloud database for storing information on one or more effects of the at least one drug administered to the patient.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are included to provide a further understanding of the invention, are incorporated herein to illustrate embodiments of the invention. Along with the description, they also serve to explain the principle of the invention. In the drawings:
FIG. 1 illustrates a block diagram of a system for triggering an alert using a patient monitoring device.
FIG. 2 illustrates a flowchart according to a preferred embodiment of the present invention.
FIG. 3 illustrates an exemplary display in accordance with an embodiment of the invention.
FIG. 4 illustrates an exemplary user interface in accordance with an
embodiment of the invention. FIG. 5 illustrates an exemplary user interface in accordance with an embodiment of the invention.
FIG. 6 illustrates an exemplary alert range threshold database in accordance with an embodiment of the invention.
FIG. 7 illustrates a flowchart describing a software for adding user-provided context information to at least of the acquired pulse oximeter data and the acquired physiological data.
FIG. 8 illustrates a flowchart describing a software for adding an audio note. FIG. 9 illustrates a flowchart describing a software for prompting a user to select a symptom being experienced.
FIG. 10 illustrates a flowchart describing a software for triggering an alert FIG. 11 illustrates an exemplary physician database in accordance with an embodiment of the invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
An embodiment of the present invention relates to a method for triggering an alert concerning a patient (user) using a patient monitoring device comprising: acquiring pulse oximeter data at a set time interval using a pulse oximeter; acquiring physiological data at a set time interval using an at least one medical device connected to the pulse oximeter; selecting via a user interface at least one symptom experienced by the patient and at least one drug administered to the patient; displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data; adding a marker on the displayed graph, wherein the marker corresponds to data representing at least one of the time interval during which the at least one symptom is experienced by the patient and the time the at least one drug is administered to the patient; triggering an alert by matching a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in an alert threshold range database; updating a physician database by uploading the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient; and accessing a cloud database to acquire information on one or more effects of the at least one drug administered to the patient.
An embodiment of the present invention also relates to a system for triggering an alert using a patient monitoring device comprising: a pulse oximeter for acquiring pulse oximeter data, an at least one medical device for acquiring physiological data, a user interface for selecting at least one symptom experienced by the patient and at least one drug administered to the patient, a display device for displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data, an alert threshold range database for storing thresholds corresponding to a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data, a physician database for storing the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient, and a cloud database for storing information on one or more effects of the at least one drug administered to the patient.
A typical pulse oximeter comprises an electronic processor and a couple of small light- emitting diodes (LEDs) facing a photodiode through a translucent portion of a patient's body, typically a fingertip or an earlobe. One of the LEDs emits light in the red portion of the visible region of the electromagnetic spectrum (red LED) while the other emits in the infrared region. The amount of light absorbed at these two wavelengths differs significantly between oxygen- rich blood and blood deficient in oxygen. Oxygenated hemoglobin absorbs more infrared light and allows more red light to pass through. On the other hand, deoxygenated hemoglobin allows more infrared light to pass through and absorbs more red light. Oxy-hemoglobin and its deoxygenated form have significantly different absorption pattern.
In operation, the LEDs alternately turn on and off, and then both off approximately for a predetermined period of time. This allows the light sensor, for example, a photodiode, to respond to the red and infrared light separately and also to correct for the light detected due to ambient light (measured when both LEDs are off; used as baseline or reference signal). The amount of light that is transmitted (that is, not absorbed) is measured, and separate normalized signals are produced for each wavelength. These signals due to transmitted light vary with time because the amount of arterial blood that is present increases with each heartbeat. By subtracting the minimum transmitted light from the peak transmitted light in each wavelength, the effects of other tissues and materials (e.g., venous blood, skin, bone, muscle, fat, including nail polish) can be corrected for because they normally absorb a constant amount of light over a period of time. The ratio of the measured red light to the measured infrared light is calculated by the processor. This ratio, which represents the ratio of oxygenated hemoglobin to deoxygenated hemoglobin, is then converted to a Sp02 reading by the processor. FIG. 1 illustrates a preferred embodiment of a system for triggering an alert using a patient monitoring device. As shown, a pulse oximeter 100 is provided to which an at least one medical device 102 is connected. In addition, the pulse oximeter 100 is connected to a patient monitoring device 104 which is communicably connected to a physician database 106, an alert threshold range database 108, and a cloud database 110. The pulse oximeter 100 comprises a first processor 112, a first communications module 114, and a first memory 116. Each of the at least one medical device 102 comprises a second communications module 118 and second memory_120. The patient monitoring device 104 comprises a display 122, a user interface 124, a third processor 126, a third_communications module 128, a third_memory 130, and a clock 132.
FIG. 2 illustrates a preferred method of the present invention. Pulse oximeter data are acquired at a set time interval using the pulse oximeter 100 (step 200). Examples of pulse oximetry data include Sp02 level, pulse rate, and perfusion index, among others, of the patient. The pulse oximetry data are then stored in the memory 116. Simultaneously, physiological data are acquired at the set time interval using the at least one medical device 102 (step 202). Preferably, the at least one medical device 102 is connected to the pulse oximeter 100 via communications modules 114 and 118. Examples of physiological data include respiratory rate, body temperature and blood pressure, among others, of the patient. The physiological data are then stored in the memory 120. The stored physiological data are transmitted, via the communications modules 114 and 118, to the pulse oximeter 100 and are stored in the memory 116. During acquisition of pulse oximeter data and physiological data (steps 200 and 202), a user is able, via a user interface 124, to provide information regarding an occurring event (step 204). Preferably, information can be a symptom experienced by the patient or a drug administered to the patient.
Afterwards, a patient monitoring device 104 retrieves the acquired pulse oximeter data and acquired physiological data via the communications modules 114 and 128. A graph is generated by the patient monitoring device using at least one of the acquired pulse oximeter data and the acquired physiological data. The generated graph is presented via display 122 (step 206). Preferably, at least one of the acquired pulse oximeter data and the acquired physiological data is plotted as a function of time. A marker is then added on the displayed graph, wherein the marker corresponds to data representing the user-provided context information (step 208). The data representing the user-provided context information can be the time interval during which a symptom is experienced by the patient or the time at which a drug is administered to the patient. For example, while the time-dependent graph of the Sp02 levels is being displayed, the medical personnel may choose to select antiarrhythmic medicine. Subsequently, the time-dependent graph for the patient's blood oxygen saturation levels is displayed with the marker overlaying the time-dependent graph to allow the medical personnel to analyze the correlation and possible effects of the anti-arrhythmic medicine to the patient's blood oxygen saturation levels.
Also shown in FIG. 2, the patient monitoring device 104 accesses an alert threshold range database 108 via the communications module 126. The alert threshold range database 108 contains threshold ranges for pulse oximeter data and physiological data. The threshold ranges in the alert threshold range database 108 correspond to different
combinations of at least two of the following variables: symptom, pulse oximeter data, and physiological data. In one embodiment, the threshold ranges are set by the user (e.g., patient) via the user interface 124. Threshold ranges used during data acquisition are adjusted accordingly by matching the combination of at least two of the symptoms being experienced by the patient, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in the alert threshold range database 108. An alert is then triggered when at least one of the acquired pulse oximetry data and the acquired physiological data reaches (falls within) the adjusted threshold (step 210).
Subsequently, the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient are transmitted via the communications module 128 to be stored to a physician database 106 (step 212). Also, a cloud database 110 can be accessed to acquire, and the cloud database 110 provides, information on one or more effects of the at least one drug administered to the patient (step 214).
FIG. 3 illustrates an exemplary display 122 described in the present invention. A display graph 300 shows a graph of at least one of the acquired pulse oximeter data and the acquired physiological data versus time. This display graph 300 enables the medical practitioner to view the acquired pulse oximeter data and the acquired physiological data over time (previously acquired data) as well as the line trend of the acquired data. The current numerical values of the currently acquired pulse oximeter data and acquired physiological data are displayed on a readings display 302. In the case of the example shown in FIG. 3, the graph of Sp02 levels and pulse rate are displayed in the display graph 300 and the current Sp02 levels, pulse rate, and perfusion index are displayed in the readings display 302.
As shown in FIG. 3, an options display 304 is provided on the display 122 to allow the user to select the at least one drug administered to a patient. Also, an "Audio Note" button 306 is provided on the display 122 to allow the user to add an audio note for the acquired pulse oximeter data and the acquired physiological data. Once an option is selected via the options display 304 or an audio note is added via the "Audio Note" button 306, a marker is overlaid on the time-dependent graph displayed on the display graph 300.
FIG. 4 illustrates an exemplary user interface 124 described in the present invention. The user interface 124 allows the user to select at least one symptom being experienced by the patient. In the example shown in FIG. 4, the at least one symptom can be selected from the list comprising shortness of breath, tiredness, sweatiness, coughing, and wheezing. Once an option is selected via the user interface 124, a marker is overlaid on the time-dependent graph displayed on the display graph 300. In one embodiment, the user interface 124 may be integrated in a hand-held device, which a patient can readily access when the patient is experiencing a symptom. The hand-held device is preferably connected to the patient monitoring device 104 via the communications module 128.
In another embodiment, the user is prompted to select a symptom via the user interface 124 if at least one of the acquired pulse oximeter data and the acquired
physiological data reaches a threshold range.
FIG. 5 illustrates another exemplary user interface 124 described in the present invention. The user interface 124 allows the user to set the threshold ranges for at least one of the pulse oximetry data and the physiological data corresponding to at least one symptom being experienced by the patient. In the case of the example shown in FIG. 5, the user sets the base threshold ranges for Sp02 levels and pulse rate. This is used as the default thresholds during data acquisition. The user also sets the threshold ranges for Sp02 levels and pulse rate that corresponds to a patient's symptoms. The threshold ranges used during data acquisition are automatically adjusted according to the user set thresholds once a symptom is selected via the user interface 124. The set threshold ranges are stored and can be accessed in the alert threshold range database. An example of the alert threshold range database 108 is shown in FIG. 6.
FIG. 7 illustrates a "Context Software" for adding a user-provided context information to at least one of the acquired pulse oximeter data and the acquired physiological data described in the present invention. At least one set of pulse oximeter data are measured using the pulse oximeter 100 (step 700). Then, the pulse oximeter 100 polls for at least one connected medical device 102 (step 702). If at least one medical device 102 is detected, the pulse oximeter 100 sends a request for at least one set of physiological data stored in the memory 120 of at least one of the detected medical devices 102 (step 704). Subsequently, the pulse oximeter 100 receives the requested at least one set of physiological data and stores the received data in memory 116 (step 706). At least one of the acquired pulse oximetry data and the acquired physiological data are then sent to the patient monitoring device 104 (step 708). If there were no medical devices 102 detected, the at least one acquired pulse oximetry data are sent to the patient monitoring device 104 (step 708).
Afterwards, the "Context Software" illustrated in FIG. 7 determines if a user - provided any context information - drug administered, symptom being experienced, and audio note (step 710). If a user-provided context information, the "Context Software" determines if the context information was an audio note (step 712). If so, an "Audio
Software" initializes. Once the "Audio Software" run is finished, the system continues running the "Context Software". If the context information is not an audio note, the software associates the user-provided context information with at least one of the acquired pulse oximetry data and the acquired physiological data. For both scenarios corresponding to the presence and absence of user-provided context information, a timestamp is added accordingly (step 714). The "Context Software" then proceeds to storing all data to the physician database 106 (step 716). The "Context Software" also determines if a network is available (step 718). In the case where a network is available, all data are sent to the cloud database 110 (step 720). The software then loops back to acquire at least one set of pulse oximeter data (step 700). If there were no networks available, the software just loops back to acquire at least one set of pulse oximeter data (step 700).
FIG. 8 illustrates the "Audio Software" for adding an audio note as described previously. The "Audio Software" initializes once a user chooses to add an audio note via the "Audio Note" button 306 on the display 122. The microphone is activated (step 800). An audio recording is then acquired (step 802). Once the user chooses to end the recording via the "Audio Note" button 306 on the display 122, the audio recording is stored in the memory 130 (step 804). Thereafter, the audio recording is converted to text (step 806). In one embodiment, the system connects to a network in order to convert the audio file to text. The "Audio Software" then proceeds to the "Context Software" to store at least one of the acquired pulse oximeter data and the acquired physiological data with added audio note to the physician database 106. [0035] FIG. 9 illustrates the "Monitoring Software" for prompting a user to select a symptom being experienced as described in the present invention. At least one set of pulse oximeter data and at least one set of physiological data are acquired using the pulse oximeter 100 and the at least one medical device 102, respectively (step 900). The system then accesses the alert threshold range database 108 and determines if any of the acquired pulse oximeter data and the acquired physiological data reaches a threshold range. If no data reach the threshold range, the system loops back to acquire at least one set of pulse oximeter data and at least one set of physiological data (step 900). Otherwise, the user is prompted to select at least one symptom being experienced (step 904). The user then selects at least one symptom being experienced via the user interface 124. The at least one selected symptom being experienced is associated with the most recent at least one set of pulse oximeter data and at least one set of physiological data (step 906) and is stored in the physician database 106 (step 908). Afterwards, the "Monitoring Software" proceeds to the "Alert Software."
FIG. 10 illustrates the "Alert Software" for triggering an alert as described by the present invention. At least one set of pulse oximeter data and at least one set of physiological data are acquired using the pulse oximeter 100 and the at least one medical device 102, respectively (step 1000). The system also acquires at least one symptom being experienced by the patient. The system then accesses the alert threshold range database 108 and determines if any of the acquired pulse oximeter data and the acquired physiological data reaches a threshold range. If at least one of the acquired pulse oximeter data and acquired physiological data reaches a threshold range, an alert is triggered to notify a medical personnel. Otherwise, the "Alert Software" is terminated.
FIG. 11 illustrates an exemplary physician database 106 as described in the present invention. The physician database 106 stores the patient ID, timestamp, symptom being experienced by the patient, drug administered to the patient, at least one set of pulse oximetry data and at least one set of physiological data.
The present invention is not intended to be restricted to the several exemplary embodiments of the invention described above. Other variations that may be envisioned by those skilled in the art are intended to fall within the disclosure.

Claims

CLAIMS:
1. A system for triggering an alert concerning a patient using a patient monitoring device, the system comprising:
a pulse oximeter that acquires at least one pulse oximeter data of the patient, the pulse oximeter comprising a first processor, a first communications module, and a first memory that stores the acquired pulse oximeter data;
at least one medical device connected to the pulse oximeter that acquires physiological data, each of the at least one medical device comprising a second processor and a second memory that stores the acquired physiological data;
a patient monitoring device connected to the pulse oximeter, the patient monitoring device comprising:
a display for displaying a graph generated using at least one of the acquired pulse oximeter data, and the acquired physiological data;
a user interface for selecting at least one symptom experienced by the patient and at least one drug administered to the patient;
a third processor; a third communications module;
a third memory; and
a clock;
an alert threshold range database communicably connected to the patient monitoring device, the alert threshold range database storing one or more threshold ranges corresponding to a combination of at least two of: the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data;
a physician database for storing and researching the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient; and
a cloud database for storing information on one or more effects of the at least one drug administered to the patient.
2. The system of claim 1, wherein the pulse oximeter data are acquired at a set time interval using the pulse oximeter.
3. The system of claim 2, wherein the pulse oximeter data is selected from an
Sp02 level, a pulse rate, a perfusion index, or a combination thereof.
4. The system of claim 1, wherein the at least one medical device is connected to the pulse oximeter via the first communications modules and the second communications module.
5. The system of claim 1, wherein the physiological data is selected from a respiratory rate, a body temperature, a blood pressure, and a combination thereof.
6. The system of claim 4, wherein the stored physiological data are transmitted to the pulse oximeter via the first communications module and the second communications module and stored in the first memory.
7. The system of claim 1, wherein the patient monitoring device retrieves the acquired pulse oximeter data and the acquired physiological data via the first
communications module and the third communications module.
8. The system of claim 1, wherein at least one of the acquired pulse oximeter data and the acquired physiological data is plotted as a function of time.
9. The system of claim 1, wherein the displayed graph includes a marker that corresponds to data representing a user-provided context information.
10. The system of claim 9, wherein the data representing a user-provided context information is selected from a time interval during which the patient experiences the at least one symptom, time at which the at least one drug is administered to the patient, or both.
11. The system of claim 1 , wherein the patient monitoring device accesses an alert threshold range database via the third communications module.
12. The system of claim 1, wherein the threshold ranges are set by a user via the user interface.
1 3 . The system of claim 1 , wherein the one or more threshold ranges are adjusted by matching the combination of at least two of: the symptoms being experienced by the patient, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in the alert threshold range database.
14. The system of claim 13, wherein an alert is triggered when at least one of the acquired pulse oximeter data and the acquired physiological data reaches the one or more adjusted threshold ranges.
15. The system of claim 14, wherein the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient are transmitted via the third communications module to the physician database and stored thereon.
16. The system of claim 14, wherein the cloud database provides information on one or more effects of the at least one drug administered to the patient.
17. The system of claim 1, wherein the graph includes a line trend of the acquired pulse oximeter data and the acquired physiological data, and one or more current numerical values each representing the acquired pulse oximeter data or the acquired physiological data.
18. The system of claim 1, wherein the display includes an optional display that allows a user to select the at least one drug administered to a patient.
19. The system of claim 1, wherein the display includes a button that allows a user to add an audio note for the acquired pulse oximeter data and the acquired physiological data.
20. The system of claim 1, wherein the user interface is integrated in a hand-held device.
21. A method for triggering an alert using a patient monitoring device comprising:
acquiring pulse oximeter data at a set time interval using a pulse oximeter; acquiring physiological data at a set time interval using an at least one medical device connected to the pulse oximeter;
selecting via a user interface at least one symptom experienced by the patient and at least one drug administered to the patient;
displaying a graph generated using at least one of the acquired pulse oximeter data and the acquired physiological data;
adding a marker on the displayed graph, wherein the marker corresponds to data representing at least one of the time interval during which the at least one symptom is experienced by the patient and the time the at least one drug is administered to the patient;
triggering an alert by matching a combination of at least two of the at least one symptom, the acquired pulse oximeter data, and the acquired physiological data with corresponding data in an alert threshold range database;
updating a physician database by uploading the acquired physiological data, the acquired pulse oximeter data, the at least one symptom experienced by the patient, and the at least one drug administered to a patient; and
accessing a cloud database to acquire information on one or more effects of the at least one drug administered to the patient.
PCT/EP2016/072211 2015-09-28 2016-09-20 Context input for pulse oximeter WO2017055128A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562233549P 2015-09-28 2015-09-28
US62/233,549 2015-09-28
EP16161254.4 2016-03-18
EP16161254 2016-03-18

Publications (1)

Publication Number Publication Date
WO2017055128A1 true WO2017055128A1 (en) 2017-04-06

Family

ID=55637197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/072211 WO2017055128A1 (en) 2015-09-28 2016-09-20 Context input for pulse oximeter

Country Status (1)

Country Link
WO (1) WO2017055128A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108903922A (en) * 2018-05-23 2018-11-30 夏文才 The medical healthy mobile interchange monitoring of one kind and service system

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7871394B2 (en) * 2006-06-13 2011-01-18 Carefusion 303, Inc. System and method for optimizing control of PCA and PCEA system
US20110082711A1 (en) * 2009-10-06 2011-04-07 Masimo Laboratories, Inc. Personal digital assistant or organizer for monitoring glucose levels
US20110202495A1 (en) * 2010-02-18 2011-08-18 Ute Gawlick Adjustable alert rules for medical personnel
US20120286955A1 (en) * 2011-04-20 2012-11-15 Masimo Corporation System for generating alarms based on alarm patterns
US20140235975A1 (en) * 2013-02-15 2014-08-21 Covidien Lp System and method for adjusting configuration parameter collection rates received from a plurality of medical devices
US20150018648A1 (en) * 2013-07-15 2015-01-15 Covidien Lp Systems and methods for monitoring patients on ventilation
US20150173674A1 (en) * 2013-12-20 2015-06-25 Diabetes Sentry Products Inc. Detecting and communicating health conditions
US20150351698A1 (en) * 2014-06-04 2015-12-10 Grandios Technologies, Llc Health and medical smartphone
US20160051206A1 (en) * 2014-08-22 2016-02-25 Koninklijke Philips N.V. Usage of observed alarm settings for alarm management

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7871394B2 (en) * 2006-06-13 2011-01-18 Carefusion 303, Inc. System and method for optimizing control of PCA and PCEA system
US20110082711A1 (en) * 2009-10-06 2011-04-07 Masimo Laboratories, Inc. Personal digital assistant or organizer for monitoring glucose levels
US20110202495A1 (en) * 2010-02-18 2011-08-18 Ute Gawlick Adjustable alert rules for medical personnel
US20120286955A1 (en) * 2011-04-20 2012-11-15 Masimo Corporation System for generating alarms based on alarm patterns
US20140235975A1 (en) * 2013-02-15 2014-08-21 Covidien Lp System and method for adjusting configuration parameter collection rates received from a plurality of medical devices
US20150018648A1 (en) * 2013-07-15 2015-01-15 Covidien Lp Systems and methods for monitoring patients on ventilation
US20150173674A1 (en) * 2013-12-20 2015-06-25 Diabetes Sentry Products Inc. Detecting and communicating health conditions
US20150351698A1 (en) * 2014-06-04 2015-12-10 Grandios Technologies, Llc Health and medical smartphone
US20160051206A1 (en) * 2014-08-22 2016-02-25 Koninklijke Philips N.V. Usage of observed alarm settings for alarm management

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108903922A (en) * 2018-05-23 2018-11-30 夏文才 The medical healthy mobile interchange monitoring of one kind and service system

Similar Documents

Publication Publication Date Title
US11839470B2 (en) Active-pulse blood analysis system
US9775547B2 (en) System and method for storing and providing patient-related data
US9980666B2 (en) System and method for determining a vital sign of a subject
US7438683B2 (en) Application identification sensor
CN108778099B (en) Method and apparatus for determining a baseline of one or more physiological characteristics of a subject
EP3053518A1 (en) System for monitoring blood pressure in real-time
CN114504310A (en) System and method for detecting changes in heart rate of a user
US11026607B2 (en) Regional saturation shock detection method and system
WO2010031070A2 (en) Patient monitor including multi-parameter graphical display
Dresher Wearable forehead pulse oximetry: Minimization of motion and pressure artifacts
CN110582228A (en) Method and apparatus for determining the health status of an infant
JP6665282B2 (en) Physiological monitoring kit with USB drive
Natarasan et al. Design and Implementation of Heartbeat rate and SpO2 Detector by using IoT for patients
JP7462572B2 (en) Apparatus, system for determining stress and/or pain levels, method of operating said system, and computer readable medium having computer readable code for carrying out the method of operating said system
Gohlke et al. An IoT based low-cost heart rate measurement system employing PPG sensors
WO2017055128A1 (en) Context input for pulse oximeter
US20220287579A1 (en) System and method for continuous non-invasive blood pressure measurement
US10213550B2 (en) Systems and methods for monitoring clinical procedures using regional blood oxygen saturation
US11857294B2 (en) Medical devices for measuring tissue properties and methods of use
Anuar Heart Rate Monitoring and Alert System Using Smartphone
Palaniappan et al. IoT Based Heart Beat And Body Temperature Measurement

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16767276

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16767276

Country of ref document: EP

Kind code of ref document: A1