EP4133500A1 - Automated device pairing using biometric identifier - Google Patents

Automated device pairing using biometric identifier

Info

Publication number
EP4133500A1
EP4133500A1 EP21717819.3A EP21717819A EP4133500A1 EP 4133500 A1 EP4133500 A1 EP 4133500A1 EP 21717819 A EP21717819 A EP 21717819A EP 4133500 A1 EP4133500 A1 EP 4133500A1
Authority
EP
European Patent Office
Prior art keywords
patient
wireless device
biometric identifier
monitor
data
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.)
Pending
Application number
EP21717819.3A
Other languages
German (de)
English (en)
French (fr)
Inventor
Georgios Kokovidis
Juan P Eslava
Randolph Prydekker
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Draegerwerk AG and Co KGaA
Original Assignee
Draegerwerk AG and Co KGaA
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 Draegerwerk AG and Co KGaA filed Critical Draegerwerk AG and Co KGaA
Publication of EP4133500A1 publication Critical patent/EP4133500A1/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/0002Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
    • A61B5/0015Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system
    • A61B5/0024Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network characterised by features of the telemetry system for multiple sensor units attached to the patient, e.g. using a body or personal area network
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/02Detecting, 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/024Detecting, measuring or recording pulse rate or heart rate
    • A61B5/02405Determining heart rate variability
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/74Details of notification to user or communication with user or patient ; user input means
    • A61B5/742Details of notification to user or communication with user or patient ; user input means using visual displays
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/17ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT 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/60ICT 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/63ICT 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 local operation
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT 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/60ICT 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/67ICT 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50Secure pairing of devices

Definitions

  • the present disclosure generally relates to a system, method, and/or device for pairing a wireless physiological sensor to a patient monitoring device (PMD) based on a comparison of biometric identifiers.
  • PMD patient monitoring device
  • Monitors that include electronic visual displays are utilized in a large number of applications within a wide variety of industries including, for example, the healthcare industry, the military, and the oil and gas industry. Many of the applications within such industries require such monitors to, at times, be portable, and, at other times, be stationary.
  • monitors can be connected to a monitor mount.
  • monitor mounts can provide a variety of functions including providing physical support, a power source, and a conduit to one or more computer networks.
  • One type of monitor is a patient monitor which is used by healthcare facilities to monitor and display information about a patient, such as vital signs (e.g., a heart rate, electrocardiogram waveform, a blood pressure, patient temperature, and respiration rate and/or volume), status of connected devices (physiological sensors, etc.), and the like.
  • vital signs e.g., a heart rate, electrocardiogram waveform, a blood pressure, patient temperature, and respiration rate and/or volume
  • status of connected devices physiological sensors, etc.
  • Patient monitors can be portable devices that travel with the patient in order to provide continuous monitoring during care.
  • the patient monitor When a patient arrives at a hospital room or other treatment location, the patient monitor is often plugged into or otherwise connected to a patient monitor mount.
  • Patient monitor mounts provide a physical interface for the patient monitor and are generally fixed to the treatment location.
  • Patient monitor mounts can also provide electrical connection to other devices or infrastructure, such as power to recharge patient monitor batteries, network connectivity to other medical devices or hospital computer systems, and the like. Patient monitors have different sizes and provide different functionalities. With current systems, each type of patient monitor typically requires a dedicated monitor mount, a dedicated controller, and a dedicated user interface controller and the same user interface, and that can be universally docked to the monitor mount.
  • healthcare practitioners typically connect at least one type of sensor to a patient to sense, derive, or otherwise monitor at least one type of patient medical parameter.
  • Such patient connected sensors are further connected to a monitor that includes all relevant electronic components that enable conversion, manipulation and processing of the data sensed by the at least one type of sensor in order to generate patient medical parameters.
  • These patient medical parameters may be stored in one or more modules and are usable by healthcare practitioners (e.g., nurses, surgeon, doctors, physician assistants, technicians, emergency medical technicians, first responders, or any other person charged with providing a healthcare service to a patient) in monitoring a patient and determining a course of healthcare to be provided to the patient.
  • the one or more modules may contain data, such as patient treatment data, to be transferred to the dock and/or the monitor.
  • a monitor may be selectively connected to a patient at any point during which a healthcare professional comes into contact with the patient and may remain connected with the patient as the patient moves through various locations within a particular healthcare enterprise (e.g., hospital) or between different healthcare enterprises (e.g., an ambulance and/or different medical facilities).
  • a healthcare enterprise e.g., hospital
  • the monitor and/or the module can be selectively connected (docked) to a stationary or fixed dock that may serve as a gateway for connecting the monitor and/or the module to a database such as hospital information system (HIS), electronic medical records (EMR) system, and/or a central monitoring station and allowing data representing the at least one patient medical parameter to be communicated to other systems within the healthcare enterprise. This data may then be used by one or more different systems in further patient care.
  • HIS hospital information system
  • EMR electronic medical records
  • the exemplary embodiments described herein provides a system, method, and device including same that provides an automated and secure pairing of a wireless device to a patient monitor device (PMD) and/or network or network of devices using a unique biometric identifier.
  • PMD patient monitor device
  • PMD patient monitor device
  • second devices such as, without limitation, a monitoring device, a therapy device, physiological sensors including ECG sensors, peripheral capillary oxygen saturation (Sp02) sensors, temperature sensors, or non-invasive blood pressure (NIBP) sensors
  • a network preferably a hospital network
  • the system, method, and/or device described herein allows placement of multiple wireless or second device(s) (such as, without limitation, Bluetooth®, WiFi, sub GHz for example), to be paired with a first device without the need for a healthcare practitioner to manually initiate the pairing process.
  • wireless or second device(s) such as, without limitation, Bluetooth®, WiFi, sub GHz for example
  • a method comprising: acquiring a biometric identifier from a patient using a first device and uploading the biometric identifier to a database; obtaining physiological parameter data of the patient using a second device; transmitting the physiological parameter data of the patient to the database; and comparing the physiological parameter data of the second device with the biometric identifier to match the physiological parameter data with the biometric identifier in the database.
  • the second device comprises a substantially similar means for capturing the biometric identifier of the patient as the first device to see if a patient match can be established.
  • a method comprising: acquiring a biometric identifier from a patient using a first device comprising an electrocardiogram to obtain a heart rate; recording the heart rate over a certain amount of time to provide a heart rate variability of the patient; uploading the heart rate variability of the patient to a database; obtaining physiological parameter data of the patient using a second device which at least measures the heart rate; transmitting the physiological parameter data of the patient to the database; and comparing the physiological parameter data of the second device with the heart rate variability to match the physiological parameter data with the biometric identifier in the database; and the physiological parameter data of the patient from the second device is substantially identical to the heart rate variability obtained from the first device then the physiological parameter of the patient is paired in the database.
  • the present disclosure is broadly directed to a system comprising a first device and a second device which are paired using at least one biometric identifier.
  • the biometric identifier is unique to the patient and allows for the automatic and secure pairing of any data that is obtained, received, or transmitted about the patient to at least one of a second device, a database such as, without limitation, a hospital information system, or combinations thereof.
  • the system or method described herein allows a first device to be paired with a second device independent of a network.
  • the system or method described herein allows a first device to be paired with a network and/or a second device that resides on a network.
  • the first device, the second device, or both can include a sensor interface configured to receive data generated by at least one physiological sensor monitoring a physiological parameter of a patient.
  • the at least one physiological sensor can include a wired connection to the sensor interface.
  • the at least one physiological sensor can additionally or alternatively include a wireless connection to the sensor interface.
  • the first device, the second device, or both can be a multiparameter monitor for continuously monitoring adult, pediatric and neonatal patients both at a bedside and on transport and can support all patient acuity levels hospital-wide.
  • either of the first device or the second device can comprise a monitor that capture and display real-time vital signs at the bedside.
  • Either of the first monitor or the second monitor can be used as a standalone monitor or in combination.
  • the system of the present disclosure integrates patient data and provides continuous monitoring at the bedside and on transport.
  • the system of the present disclosure enables pick and go transport of a patient from one care area of a hospital to another care area of the hospital without having to disconnect the patient from a patient monitor.
  • the system of the present disclosure streamlines workflows by being able to go from bedside to transport at the push of a button. Cables and modules can remain attached to the patient and parameters and alarms can continue to be monitored in real time, while recording data during travel.
  • the system of the present disclosure can also provide seamless wired-to-wireless networking, so surveillance can be continuous. No disconnection or reconnection of leads is required and there are no gaps in monitoring or data acquisition. As a result, all parameters that are monitored at the bedside can continue to be monitored on transport.
  • the system of the present disclosure therefore allows monitors to be mixed and matched across different care areas and geographies such that workflow is optimized.
  • the system of the present disclosure also requires fewer mounting points than current systems, thereby reducing installation and maintenance costs. Since the monitor mount and one or more monitors are integrated and consolidated, the space required for the system of the present disclosure is minimized.
  • the system of the present disclosure can be used in dry and wet zones and contributes to an enhanced level of hygiene. According to caregiver preference, the system of the present disclosure can be scaled to the patient’s needs - from basic monitoring to using the full range of all of the monitors.
  • multiple monitors can be used, for example, to support anesthesiologists, perfusionists, and surgeons if a surgical display controller is used.
  • the system of the present disclosure provides a high acuity care system that improves aesthetics and ergonomics by allowing different caregivers to view the information they need at the same place.
  • the system of the present disclosure can be used as part of a healthcare enterprise solution and can bring comprehensive information to the point of care, while continuously monitoring the patient.
  • the system of the present disclosure can provide access to images, lab results and other clinical data, while displaying real-time vital signs data at the point of care securely and automatically to the patient’s record without having the practitioner continuously pair or match the first device such as a monitor and second device such as a sensor and/or the HIS using a biometric identifier.
  • FIG 1 is a diagram illustrating relevant portions of an exemplary hospital network
  • FIG. 2 is a diagram illustrating an exemplary patient monitor and monitor mount
  • FIG. 3 a flow diagram of an exemplary method for creating a biometric identifier for a patient and associating that patient with a patient monitor;
  • FIG. 4 is a flow diagram of an exemplary method for using biometric identifiers to pair a wireless device with a patient monitor
  • FIG. 5 is a flow diagram of another exemplary method for using biometric identifiers to pair a wireless device with a patient monitor;
  • FIG. 6 is a diagram illustrating an exemplary method creating a biometric identifier for a patient based on heart rate variability, associating that patient with a patient monitor, and pairing a wireless device with a patient monitor;
  • FIGS. 7A through 7C are diagrams providing a specific example of execution of the processes of FIGS. 3 and 4;
  • FIG. 8 is a diagram illustrating another exemplary embodiment of a patient monitor that is connected wirelessly to the network and uses a time of flight (TOF) sensor to create biometric identifiers.
  • TOF time of flight
  • the exemplary embodiments described herein provides a system, method, and device including same that provides an automated and secure process for associating a wireless device to a patient monitor using a unique biometric identifier.
  • a first device such as, without limitation, an ECG patient monitor
  • one or more second devices such as, without limitation, a Sp02, temperature, or NIBP
  • a network preferably a hospital network
  • the system, method, and/or device described herein allows placement of multiple wireless or second device(s) (such as, without limitation, Bluetooth, WiFi, sub GHz for example), to be paired with a first device without the need for a clinician to manually initiate the pairing process.
  • wireless or second device(s) such as, without limitation, Bluetooth, WiFi, sub GHz for example
  • the expression “and/or” includes any and all combinations of the associated listed words.
  • the expression “A and/or B” may include A, may include B, or may include both A and B.
  • expressions including ordinal numbers may modify various elements.
  • such elements are not limited by the above expressions.
  • the above expressions do not limit the sequence and/or importance of the elements.
  • the above expressions are used merely for the purpose of distinguishing an element from the other elements.
  • a first box and a second box indicate different boxes, although both are boxes.
  • a first element could be termed a second element, and similarly, a second element could also be termed a first element without departing from the scope of the present disclosure.
  • the terms “associate” and “pair” may be used interchangeably. “Pairing” is a specific type of association, such as the pairing that takes place between a Bluetooth master radio and a Bluetooth slave radio that enables the device having the slave radio to maintain a wireless communication connection with the master radio and automatically reconnect.
  • the subject matter described herein is directed to systems and apparatuses directed to monitors (e.g., display monitors having visual electronic displays) and monitor mounts providing physical support and, in some cases, power and access to a communications / computer network.
  • monitors e.g., display monitors having visual electronic displays
  • monitor mounts providing physical support and, in some cases, power and access to a communications / computer network.
  • Use of such systems and apparatuses can, for example, occur in a medical environment such as the scene of a medical event, an ambulance, a hospital or a doctor's office.
  • a minimum set of sensors can be connected to a patient to collect various types of patient information as described in detail herein.
  • the sensor are used to obtain a unique patient identifier and store it in a database.
  • the patient monitor can travel with the patient and additional patient physiological data is obtained from additional devices such as a wireless devices capable of gathering physiological data.
  • additional devices such as a wireless devices capable of gathering physiological data.
  • the data from the wireless device is compared with the biometric identifier data acquired from the sensors connected to the patient monitor at initial monitoring and recorded in the database. If the data from the wireless device matches the biometric identifier, then the data is paired.
  • the sensors are devices that are used for measuring and/or monitoring the physiological parameters of a patient (e.g., electrocardiogram (ECG) waveform, non-invasive peripheral oxygen saturation (Sp02), non-invasive blood pressure (NIBP), temperature, and/or tidal carbon dioxide (etC02), apnea detection, and other similar physiological data.
  • ECG electrocardiogram
  • Sp02 non-invasive peripheral oxygen saturation
  • NIBP non-invasive blood pressure
  • etC02 tidal carbon dioxide
  • apnea detection e.g., tidal carbon dioxide
  • FIG. 1 is a simplified schematic diagram of an exemplary hospital patient monitoring and data system 100.
  • the system 100 comprises a network 108 having a plurality of patient monitoring devices 7 that are capable of directly connecting to the network 108 or connecting through a monitor mount 10.
  • the system 100 preferable includes local storage 104 for patient data and may optionally include cloud-based storage 110.
  • a plurality of wireless devices 102a- n are provided.
  • the term “patient monitoring device” is a device that is capable of collecting and displaying (either on its own display or another connected device having a display) information concerning one or more physiological parameters of a patient.
  • FIG. 2 is a schematic diagram that shows additional detail for the patient monitoring device 7 and the monitor mount 10 to which the patient monitoring device 7 is removably mounted or docked.
  • the monitoring device 7 is capable of receiving physiological data from various sensors 17 connected to a patient 1.
  • the patient monitoring device 7 and the monitor mount 10 include electronic components or electronic computing devices operable to receive, transmit, process, store, and/or manage patient data and information associated performing the functions of the system, which encompasses any suitable processing device adapted to perform computing tasks consistent with the execution of computer-readable instructions stored in a memory or a computer-readable recording medium.
  • any, all, or some of the computing devices in the patient monitoring device 7 and the monitor mount 10 may be adapted to execute any operating system, including Linux, UNIX, Windows Server, etc., as well as virtual machines adapted to virtualize execution of a particular operating system, including customized and proprietary operating systems.
  • the patient monitoring device 7 and the monitor mount 10 are further equipped with components to facilitate communication with other computing devices over one or more network connections, which may include connections to local and wide area networks, wireless and wired networks, public and private networks, and any other communication network enabling communication in the system.
  • the patient monitoring device 7 is, for example, a patient monitor implemented to monitor various physiological parameters of the patient 1 via a plurality of sensors 17.
  • the patient monitoring device 7 could be a defibrillator, automated external defibrillator, a personal computer (e.g., a laptop or desktop computer), or a tablet computing device, a mobile computing device (e.g., smartphone or personal digital assistant) to list a few examples.
  • the patient monitoring device 7 includes a sensor interface 2, one or more processors 3, a display/GUI 4, a communications interface 6, memory 8, and a power source 9.
  • the sensor interface 2 can be implemented in software or hardware and used to connect via wired and/or wireless connections to one or more physiological sensors and/or medical devices 17 for gathering physiological data from the patient 1.
  • the data signals from the sensors 17 include, for example, data related to an electrocardiogram (ECG), non-invasive peripheral oxygen saturation (Sp02), non-invasive blood pressure (NIBP), temperature, and/or tidal carbon dioxide (etC02), apnea detection, and other similar physiological data.
  • ECG electrocardiogram
  • Sp02 non-invasive peripheral oxygen saturation
  • NIBP non-invasive blood pressure
  • etC02 tidal carbon dioxide
  • apnea detection and other similar physiological data.
  • the first device is a patient monitoring device 7 and the biometric identifier is established using a 12 lead (10 wires) ECG sensor such as that shown as 18 to capture the heart rate of the patient and is used as the biometric identifier.
  • the one or more processors 3 are used for controlling the general operations of the patient monitoring device 7.
  • Each one of the one or more processors 3 can be, but are not limited to, a central processing unit (CPU), a hardware microprocessor, a multi-core processor, a single core processor, a field programmable gate array (FPGA), a microcontroller, an application specific integrated circuit (ASIC), a digital signal processor (DSP), or other similar processing device capable of executing any type of instructions, algorithms, or software for controlling the operation and performing the functions of the patient monitoring device 7.
  • CPU central processing unit
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • the display/GUI 4 is for displaying various patient data and hospital or patient care information and includes a user interface implemented for allowing communication between a user and the patient monitoring device 7.
  • the display/GUI 4 includes, but is not limited to, a keyboard, a liquid crystal display (LCD), cathode ray tube (CRT), thin film transistor (TFT), light-emitting diode (LED), high definition (HD) or other similar display device with touch screen capabilities.
  • the patient information displayed can, for example, relate to the measured physiological parameters of the patient 1 (e.g., blood pressure, heart related information, pulse oximetry, respiration information, etc.).
  • the communications interface 6 allows the patient monitoring device 7 to directly or indirectly (via, for example, the monitor mount 10) communicate with one or more computing networks and devices.
  • the communications interface 6 can include various network cards, interfaces or circuitry to enable wired and wireless communications with such computing networks and devices.
  • the communications interface 6 can also be used to implement, for example, a Bluetooth connection, a cellular network connection, and/or a WiFi connection.
  • Other wireless communication connections implemented using the communications interface 6 include wireless connections that operate in accordance with, but are not limited to, IEEE802.11 protocol, a Radio Frequency For Consumer Electronics (RF4CE) protocol, ZigBee protocol, and/or IEEE802.15.4 protocol.
  • RF4CE Radio Frequency For Consumer Electronics
  • the communications interface 6 can enable direct (i.e. , device-to-device) communications (e.g., messaging, signal exchange, etc.) such as from the monitor mount 10 to the patient monitoring device 7 using, for example, a USB connection.
  • the communications interface 6 can also enable direct device-to-device connection to other device such as to a tablet, PC, or similar electronic device; or to an external storage device or memory.
  • the memory 8 can be a single memory or one or more memories or memory locations that include, but are not limited to, a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, hard disk or any other various layers of memory hierarchy.
  • RAM random access memory
  • EPROM erasable programmable read only memory
  • EEPROM electrically erasable programmable read only memory
  • ROM read only memory
  • flash memory hard disk or any other various layers of memory hierarchy.
  • the memory 8 can be used to store any type of instructions and patient data associated with algorithms, processes, or operations for controlling the general functions and operations of the patient monitoring device 7.
  • the power source 9 can include a self-contained power source such as a battery pack and/or include an interface to be powered through an electrical outlet (either directly or by way of the monitor mount 10).
  • the power source 9 can also be a rechargeable battery that can be detached allowing for replacement.
  • a small built-in back-up battery or super capacitor
  • Communication between the components of the patient monitoring device 7 (e.g., 2, 3, 4, 6, 8, and 9) are established using an internal bus 5.
  • the patient monitoring device 7 is connected to the monitor mount 10 via a connection 18 that establishes a communication connection between, for example, the respective communications interfaces 6, 14 of the devices 7, 10.
  • the connection 18 enables the monitor mount 10 to detachably secure the patient monitoring device 7 to the monitor mount 10.
  • “detachably secure” means that the monitor mount 10 can secure the patient monitoring device 7, but the patient monitoring device 7 can be removed or undocked from the monitor mount 10 by a user when desired.
  • the connection 18 may include, but is not limited to, a universal serial bus (USB) connection, parallel connection, a serial connection, coaxial connection, a High-Definition Multimedia Interface (HDMI) connection, or other similar connection known in the art connecting to electronic devices.
  • USB universal serial bus
  • HDMI High-Definition Multimedia Interface
  • the monitor mount 10 includes one or more processors 12, a memory 13, a communications interface 14, an I/O interface 15, and a power source 16.
  • the one or more processors 12 are used for controlling the general operations of the monitor mount 10.
  • Each one of the one or more processors 12 can be, but are not limited to, a central processing unit (CPU), a hardware microprocessor, a multi-core processor, a single core processor, a field programmable gate array (FPGA), a microcontroller, an application specific integrated circuit (ASIC), a digital signal processor (DSP), or other similar processing device capable of executing any type of instructions, algorithms, or software for controlling the operation and performing the functions of the monitor mount 10.
  • CPU central processing unit
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • the memory 13 can be a single memory or one or more memories or memory locations that include, but are not limited to a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, hard disk or any other various layers of memory hierarchy.
  • RAM random access memory
  • EPROM erasable programmable read only memory
  • EEPROM electrically erasable programmable read only memory
  • ROM read only memory
  • flash memory hard disk or any other various layers of memory hierarchy.
  • the memory can be used to store any type of instructions associated with algorithms, processes, or operations for controlling the general functions and operations of the monitor mount 10.
  • the communications interface 14 allows the monitor mount 10 to communicate with one or more computing networks (e.g., a hospital network, the Internet, third party networks/servers, cloud solutions,) and devices (e.g., the patient monitoring device 7).
  • the communications interface 14 can include various network cards, interfaces or circuitry to enable wired and wireless communications with such computing networks and devices.
  • the communications interface 14 can also be used to implement, for example, a Bluetooth connection, a cellular network connection, and a WiFi connection (e.g., 3G, 4G, and 5G networks).
  • wireless communication connections implemented using the communications interface 14 include wireless connections that operate in accordance with, but are not limited to, IEEE802.11 protocol, a Radio Frequency For Consumer Electronics (RF4CE) protocol, ZigBee protocol, and/or IEEE802.15.4 protocol.
  • IEEE802.11 protocol a Radio Frequency For Consumer Electronics (RF4CE) protocol
  • RF4CE Radio Frequency For Consumer Electronics
  • ZigBee protocol ZigBee protocol
  • IEEE802.15.4 protocol IEEE802.15.4
  • the communications interface 14 can also enable direct (i.e., device-to-device) communications (e.g., messaging, signal exchange, etc.) such as from the monitor mount 10 to the patient monitoring device 7 using, for example, a USB connection, coaxial connection, or other similar electrical connection.
  • the communications interface 14 can enable direct (i.e., device-to- device) to other device such as to a tablet, PC, or similar electronic device; or to an external storage device or memory.
  • the I/O interface 15 can be an interface for enabling the transfer of information between monitor mount 10, one or more patient monitoring devices 7, and external devices such as peripherals connected to the monitor mount 10 that need special communication links for interfacing with the one or more processors 12.
  • the I/O interface 15 can be implemented to accommodate various connections to the monitor mount 10 that include, but is not limited to, a universal serial bus (USB) connection, parallel connection, a serial connection, coaxial connection, a High-Definition Multimedia Interface (HDMI) connection, or other known connection in the art connecting to external devices.
  • USB universal serial bus
  • HDMI High-Definition Multimedia Interface
  • the power source 16 can include a self-contained power source such as a battery pack and/or include an interface to be powered through an electrical outlet (either directly or by way of the patient monitoring device 7).
  • the power source 16 can also be a rechargeable battery that can be detached allowing for replacement. Communication between the components of the monitor mount 10 (e.g., 12, 13, 14, 15 and 16) are established using an internal bus 11.
  • the first device, the second device, or both can include a sensor interface configured to receive data generated by at least one physiological sensor monitoring a physiological parameter of a patient.
  • the at least one physiological sensor can include a wired connection to the sensor interface.
  • the at least one physiological sensor can additionally or alternatively include a wireless connection to the sensor interface.
  • the first device, the second device, or both can be a multiparameter monitor for continuously monitoring adult, pediatric and neonatal patients both at a bedside and on transport and can support all patient acuity levels hospital-wide.
  • either of the first device or the second device can comprise a monitor that capture and display real-time vital signs at the bedside.
  • Either of the first monitor or the second monitor can be used as a standalone monitor or in combination.
  • the system of the present disclosure integrates patient data and provides continuous monitoring at the bedside and on transport.
  • the system of the present disclosure enables pick and go transport of a patient from one care area of a hospital to another care area of the hospital without having to disconnect the patient from a patient monitor.
  • the system of the present disclosure streamlines workflows by being able to go from bedside to transport in the push of a button. Cables and modules can remain attached to the patient and parameters and alarms can continue to be monitored in real time, while recording data during travel.
  • the system of the present disclosure can also provide seamless wired-to-wireless networking, so surveillance can be continuous. No disconnection or reconnection of leads is required and there are no gaps in monitoring or data acquisition. As a result, all parameters that are monitored at the bedside can continue to be monitored on transport.
  • the system of the present disclosure therefore allows monitors to be mixed and matched across different care areas and geographies such that workflow is optimized.
  • the system of the present disclosure also requires fewer mounting points than current systems, thereby reducing installation and maintenance costs. Since the monitor mount and one or more monitors are integrated and consolidated, the space required for the system of the present disclosure is minimized.
  • the system of the present disclosure can be used in dry and wet zones and contributes to an enhanced level of hygiene. According to caregiver preference, the system of the present disclosure can be scaled to the patient’s needs - from basic monitoring to using the full range of all the monitors. To support individual workflow, multiple monitors can be used, for example, to support anesthesiologists, perfusionists, and surgeons if a surgical display controller is used.
  • the system of the present disclosure provides a high acuity care system that improves aesthetics and ergonomics by allowing different caregivers to view the information they need at the same place.
  • the system of the present disclosure can be used as part of a healthcare enterprise solution and can bring comprehensive information to the point of care, while continuously monitoring the patient.
  • the system of the present disclosure can provide access to images, lab results and other clinical data, while displaying real-time vital signs data at the point of care securely and automatically to the patient’s record without having the practitioner continuously pair or match the first device such as a monitor and second device such as a sensor and/or the HIS using a patient identifier.
  • biometric identifier means an identifier created from physiological or biometric data that is capable of uniquely identifying a human being.
  • biometric identifiers include, without limitation, facial characteristic(s), vein characteristic(s), patient heart rate variability (HRV), fingerprint(s), retinal pattern(s), and voice pattern(s).
  • HRV patient heart rate variability
  • fingerprint(s) fingerprint(s)
  • retinal pattern(s) retinal pattern(s)
  • voice pattern(s) voice pattern
  • Each wireless device that is capable of being paired to a patient monitor much have the capability of generating data necessary to establish the biometric identifier. For example, if a facial characteristic or a vein characteristic is the biometric identifier, it will be necessary for the patient monitoring device and each wireless device to include a camera that can be used to securely authenticate a user by scanning their facial characteristics and/or scanning their unique pattern of palm veins.
  • FIG. 3 provides a flow chart of an exemplary method of creating an association between a patient and a patient monitor using a biometric identifier.
  • physiological sensors 17 associated with the patient monitor 7 are attached to a patient and physiological data (for example, ECG data, a facial image, ora vein characteristic image) is gathered (step 210).
  • physiological data for example, ECG data, a facial image, ora vein characteristic image
  • the physiological data is then processed to establish a biometric identifier for that patient (step 212).
  • Such processing could be conducted using the patient monitor 7 or could be conducted in another computing device on the network 108.
  • the biometric identifier is then uploaded to a database that is accessible by any patient monitor on the network 108 (step 214) and the patient monitor 7 is associated with the patient in the database (step 216).
  • the patient monitor 7 could store a local copy of either the entire biometric identifier database or the biometric identifier for the patient associated with that patient monitor 7. Storing a copy locally would enable a wireless device pairing to proceed when the patient monitor 7 isn’t connected to the network.
  • the database could optionally be updated dynamically during the patient’s stay at the medical facility with additional data relating to the physiological parameter(s) used to establish the biometric identifier.
  • the biometric identifier could be stored by the patient monitor 7 and uploaded to the database when the patient monitor 7 reconnects to the network 108.
  • the system 100 is capable of automatically associating wireless devices with patient monitors on the system 100.
  • An exemplary embodiment of implementing this process is shown in FIG. 4.
  • a wireless device When a wireless device is activated, it wirelessly connects to a patient monitor that is within range of the wireless device (step 310). The wireless device then transmits physiological data to the patient monitor to which it has connected (step 312). The physiological data is then processed to establish a biometric identifier for the wireless device (step 314). The biometric identifier for the wireless device is then compared to the biometric identifier for the patient associated with the patient monitor (step 316).
  • the wireless device is associated with the patient monitor (step 318). In the event that the wireless connection between the wireless device and the patient monitor uses the Bluetooth protocol, the association could consist of pairing the wireless device to the patient monitor. If the biometric identifiers do not match, the wireless device is disconnected from the patient monitor and the wireless device connects with a different patient monitor (step 320). If the wireless device is able the connect with another patient monitor, then steps 312 through 317 are repeated with the new patient monitor. A warning or alert could optionally be displayed on the patient monitor if it is determined via the comparison of step 316 that the biometric identifiers are not a match.
  • step 310 The nature of the wireless data “connection” of step 310 will depend upon the wireless protocol by which the connection is established. For example, in the case of Bluetooth protocol, steps 310 through 317 could be conducted as part of the discovery process that precedes pairing of the wireless device to the patient monitor. In other words, step 316 would correspond to the authentication step in Bluetooth protocol that is a prerequisite to pairing. Instead of using a password or PIN for authentication, physiological parameter data of a patient (collected by the device seeking to pair) is the means of authentication. Similarly, the nature of the “association” of step 318 will depend, in part, upon the wireless communication protocol. In the context of a wireless connection via Bluetooth protocol, the association could consist of successful completion of the Bluetooth pairing process.
  • a key characteristic of the “association” between a wireless device and a patient monitor is that data from the wireless device is directed to that patient monitor (and, optionally, shown on the display of that patient monitor) and not to other patient monitors. If wireless communication between the wireless device and the patient monitor is interrupted, the existence of the association may enable the wireless device to reconnect without repeating the biometric identifier comparison step (step 316). Alternatively, reconnection could require the wireless device to repeat steps 312 through 318.
  • steps 410 through 414 are the same as steps 310 through 314 of FIG. 4.
  • the biometric identifier created from data collected from the wireless device is compared to all of the biometric identifiers stored in the database (step 416). If the current biometric identifier matches any of the stored biometric identifiers in the database (step 417), then the wireless device is associated with the patient monitor associated with the stored biometric identifier (step 418), for example, using a key exchange. If no matches are found, then pairing of the wireless device is rejected and an alert is generated to notify clinicians that that attempted pairing/association failed (step 420).
  • FIG. 6 shows another exemplary embodiment of a process for associating patient with a patient monitoring device and enabling wireless devices to pair with patient monitoring devices using Bluetooth protocol.
  • HRV heart rate variability data
  • sensors including an ECG sensor
  • the ECG sensor is used to gather heart rate data, which is captured by the patient monitor (step 512), converted from analog to digital signals (step 514), and processed using an HRV algorithm to generate a biometric identifier for the patient (step 516).
  • Heart rate variability represents the fluctuation in the time intervals between adjacent heartbeats.
  • HRV is generated by heart-brain interactions and dynamic non-linear autonomic nervous system (ANS) processes.
  • HRV can be calculated via at least one of time-domain measurement, frequency-domain measurement and non-linear measurements.
  • time-domain measurement may include calculation of HRV based on one or more of standard deviation, mean, average of R-R intervals or N-N intervals (“normal” R-R intervals excluding artifacts) in a pre-determined time period.
  • Frequency-domain measurements may include estimate of distribution of absolute or relative power into different frequency bands.
  • the context information of the patient including age, gender, temperature, cardiac rhythm, respiration may also be taken into consideration when measuring HRV.
  • Any suitable algorithm could be used to generate a biometric identifier based on HRV data.
  • the biometric identifier is then stored in a database accessible on the hospital network (step 518) and the patient monitor is associated with that patient.
  • the dashed line connecting steps 518 and 610 signifies that a significant amount of time may pass and other operations may be performed using the patient monitor between the performance of steps 518 and 610.
  • the wireless sensor paring portion of the process is used.
  • the wireless device activates its Bluetooth radio and a connection is initiated with a Bluetooth master radio on a patient monitor that is within range (step 612).
  • the device must include the capability to gather physiological data sufficient to generate HRV.
  • the wireless device could be, without limitation, a NIBP, temperature, or Sp02 sensor.
  • the wireless device must also include an ECG sensor or other sensor capable of sensing the patient’s heart rate.
  • Data sufficient to establish an HRV is transmitted from the wireless sensor to the patient monitor (step 614), then the data is converted from analog to digital signals by the patient monitor (step 616).
  • the digital signals are sent to an HRV algorithm and used to generate a biometric identifier for the patient associated with the wireless device (step 618).
  • the biometric identifier for the patient associated with the wireless device is compared with the biometric identifier of the patient associated with the patient monitor (step 610). If the biometric identifiers match (step 621), then the wireless device is paired to the patient monitor (step 622). If the biometric identifiers do not match, then the wireless device disconnects from the patient monitor, searches for another patient monitor in range, and steps 612 through 621 are repeated.
  • biometric identifiers could be used.
  • both HRV and facial recognition could be used as biometric identifiers.
  • the biometric identifier comparison could either (a) require a match for both biometric identifiers or (b) compare primary biometric identifiers (HRV in this example), then compare secondary biometric identifiers (facial recognition in this example) only if the primary biometric identifiers do not match.
  • the wireless device could optionally have a back-up method of pairing with a patient monitor, such as RFID, a QR code, or NFC chip.
  • FIGs. 7A through 7C provide another visual representation and example of the processes described in Figs. 3 and 4.
  • two patients 1a, 1b are located in a hospital room.
  • Patient 1a is associated with patient monitor 7a and
  • Patient 1b is associated with patient monitor 7b
  • Wired sensors 17 that may be connected to patients 1a, 1b are omitted to simplify these figures.
  • a wireless device 102a is positioned on patient 1a and activated.
  • the patient monitors 7a, b could be any suitable patient monitor, such as a Draeger Medical System Inc. M300 or M540 patient monitors having Bluetooth capabilities.
  • the Bluetooth interface of the wireless device 102a searches for and makes a connection with the Bluetooth master radio of patient monitor 7b (see FIG. 7B).
  • the wireless device 102a then begins transmitting physiological parameter data sufficient to establish a biometric identifier for the wireless device (which is connected to patient 1a).
  • the physiological parameter data from the wireless device 102a is then processed, either by the patient monitor 7b, or using another computing device on the hospital network, to establish a biometric identifier for the wireless device 102a.
  • the biometric identifier for the wireless device 102a is then compared to the biometric identifier stored in the hospital database for the patient associated with patient monitor 7b (patient 1 b).
  • biometric identifiers will not result in a match because the wireless device 102a is measuring physiological parameters of patient 1a and patient monitor 7b is associated with patient 1b. Accordingly, the patient monitor 7b will terminate the Bluetooth connection with the wireless device 102a and the wireless device 102a will initiate a connection with another patient monitor within range
  • patient monitor 7a in this case, patient monitor 7a (see FIG. 7C).
  • the wireless device 102a then begins transmitting physiological parameter data to patient monitor 7a.
  • the physiological parameter data from the wireless device 102a is then processed, either by the patient monitor 7a, or using another computing device on the hospital network, to establish a biometric identifier for the wireless device 102a.
  • the biometric identifier for the wireless device 102a is then compared to the biometric identifier stored in the hospital database for the patient associated with patient monitor 7b (patient 1 a). The comparison of biometric identifiers will result in a match because the wireless device 102a is measuring physiological parameters of patient 1a and patient monitor 7b is associated with patient 1a. Because a match was found, the patient monitor 7a will pair with the wireless device 102a.
  • FIG. 8 shows another exemplary embodiment of a patient monitor 707 that is connected wirelessly to the hospital network and uses a time of flight (TOF) sensor 708 to generate biometric identifiers.
  • An example of such an imaging device is a time-of-flight camera such as the REAL3TM TOF camera manufactured by Infineon, Inc.
  • the patient monitor 707 includes a WiFi radio 714 that enables wireless communication with the hospital network via an access point 712.
  • the wireless devices 702a-n each include a TOF sensor 719a-n and a Bluetooth radio 718a-n.
  • the TOF sensors 708 and 719a-n are used scan a face or the veins of a wrist to establish a baseline signature which becomes the biometric identifier and is transmitted to the network.
  • the wireless connection between the wireless device and the patient monitor uses the Bluetooth wireless protocol.
  • Such wireless connections could be made with any suitable wireless protocol such as, without limitation, cellular protocol, WFi / IEEE802.11 protocol, Radio Frequency For Consumer Electronics (RF4CE) protocol, ZigBee protocol, IEEE802.15.4 protocol, and other wireless protocols that may be developed in the future.
  • RF4CE Radio Frequency For Consumer Electronics
  • biometric identifiers While the embodiments have been described with exemplary biometric identifiers, it is anticipated that future devices, sensors, or imaging technology can be used to record one more unique, patient specific identifiers, such as without limitation, glucose, EEG, respiration volume, or other commonly monitored physiological parameters or patient characteristics for automatic and secure pairing. These new or future patient-specific biometric identifiers can be used alone or in combination with any one or more of the previously mentioned biometric identifier.
  • the present disclosure may be implemented as any combination of a system, an integrated circuit, and a computer program on a non-transitory computer readable recording medium.
  • the processor and any other parts of the computing system may be implemented as Integrated Circuits (IC), Application-Specific Integrated Circuits (ASIC), or Large Scale Integrated circuits (LSI), system LSI, super LSI, or ultra LSI components which perform a part or all of the functions of the computing system.
  • IC Integrated Circuits
  • ASIC Application-Specific Integrated Circuits
  • LSI Large Scale Integrated circuits
  • system LSI system LSI
  • super LSI super LSI
  • ultra LSI components which perform a part or all of the functions of the computing system.
  • Each of the parts of the present disclosure can be implemented using many single-function components, or can be one component integrated using the technologies described above.
  • the circuits may also be implemented as a specifically programmed general purpose processor, CPU, a specialized microprocessor such as Digital Signal Processor that can be directed by program instructions on a memory, a Field Programmable Gate Array (FPGA) that can be programmed after manufacturing, or a reconfigurable processor. Some or all of the functions may be implemented by such a processor while some or all of the functions may be implemented by circuitry in any of the forms discussed above.
  • the present disclosure may be implemented as a non-transitory computer-readable recording medium having recorded thereon a program embodying methods/algorithms for instructing the processor to perform the methods/algorithms.
  • the non-transitory computer-readable recording medium can be, for example, a CD-ROM, DVD, Blu-ray disc, or an electronic memory device.
  • Each of the elements of the present disclosure may be configured by implementing dedicated hardware or a software program on a memory controlling a processor to perform the functions of any of the components or combinations thereof. Any of the components may be implemented as a CPU or other processor reading and executing a software program from a recording medium such as a hard disk or a semiconductor memory.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Public Health (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Veterinary Medicine (AREA)
  • Animal Behavior & Ethology (AREA)
  • Surgery (AREA)
  • Molecular Biology (AREA)
  • Heart & Thoracic Surgery (AREA)
  • Pathology (AREA)
  • Cardiology (AREA)
  • Biophysics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physiology (AREA)
  • Chemical & Material Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Medicinal Chemistry (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)
EP21717819.3A 2020-04-06 2021-04-06 Automated device pairing using biometric identifier Pending EP4133500A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063005839P 2020-04-06 2020-04-06
PCT/EP2021/058949 WO2021204805A1 (en) 2020-04-06 2021-04-06 Automated device pairing using biometric identifier

Publications (1)

Publication Number Publication Date
EP4133500A1 true EP4133500A1 (en) 2023-02-15

Family

ID=75441904

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21717819.3A Pending EP4133500A1 (en) 2020-04-06 2021-04-06 Automated device pairing using biometric identifier

Country Status (4)

Country Link
US (1) US20230157545A1 (zh)
EP (1) EP4133500A1 (zh)
CN (1) CN115298744A (zh)
WO (1) WO2021204805A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11955210B2 (en) * 2020-06-26 2024-04-09 Medtronic Minimed, Inc. Automatic configuration of user-specific data based on networked charger devices
CN116931835A (zh) * 2023-07-25 2023-10-24 北京领创医谷科技发展有限责任公司 一种体外程控设备数据迁移的方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8508336B2 (en) * 2008-02-14 2013-08-13 Proxense, Llc Proximity-based healthcare management system with automatic access to private information
US9000914B2 (en) * 2010-03-15 2015-04-07 Welch Allyn, Inc. Personal area network pairing
WO2013103342A1 (en) * 2012-01-04 2013-07-11 Draeger Medical Systems, Inc. Patient identification and monitoring system
US20180279918A1 (en) * 2014-10-25 2018-10-04 Sumner Bluffs, Llc. Nebulizing devices and systems having biometric data acquisition and monitoring capabilities

Also Published As

Publication number Publication date
CN115298744A (zh) 2022-11-04
WO2021204805A1 (en) 2021-10-14
US20230157545A1 (en) 2023-05-25

Similar Documents

Publication Publication Date Title
JP7355826B2 (ja) プラットフォーム非依存のリアルタイム医療データ表示システム
US11622684B2 (en) Physiological monitoring system
JP2018500090A (ja) モバイルヘルスケアハブ
US20210369113A1 (en) Acute Care Eco System Integrating Customized Devices of Personalized Care With Networked Population Based Management
US20230157545A1 (en) Automated device pairing using biometric identifier
US20230414151A1 (en) Mobile electrocardiogram system
US20140310024A1 (en) Wifi cloud electronic vital-sign monitoring system
US20210304881A1 (en) Systems and methods of producing patient encounter records
US20230095781A1 (en) Apparatus, system, method, and computer-readable recording medium for displaying transport indicators on a physiological monitoring device
US20210304860A1 (en) Systems and methods of integrating medical device case files with corresponding patient care records
US20210137468A1 (en) Portable health and wellness device
US11529061B2 (en) System and method for monitoring and analysis of blood pressure
CN112911990A (zh) 一种医疗监护设备及其状态信息展示方法
LU100553B1 (en) A Wifi cloud electronic vital-sign monitoring system
Ursache et al. Remote Monitoring of Blood Pressure by using Wireless Devices
JP7106253B2 (ja) ベッドサイドモニター及び生体情報モニタリングシステム
Sarkar et al. Exploring the Feasibility of Internet of Things in the Context of Intelligent Healthcare Solutions: A Review
WO2022185158A1 (en) Implementation of a connected medical device hub to digitise the complete workflow in an intensive care unit
EP3857563A1 (en) Medical monitoring system
PH12017000032A1 (en) Integrated healthcare system

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20221103

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)