US20210244281A1 - Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers - Google Patents
Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers Download PDFInfo
- Publication number
- US20210244281A1 US20210244281A1 US17/052,479 US201917052479A US2021244281A1 US 20210244281 A1 US20210244281 A1 US 20210244281A1 US 201917052479 A US201917052479 A US 201917052479A US 2021244281 A1 US2021244281 A1 US 2021244281A1
- Authority
- US
- United States
- Prior art keywords
- vital sign
- patient
- measurement data
- computer system
- computer
- 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
Links
- 238000012806 monitoring device Methods 0.000 claims abstract description 72
- 238000009528 vital sign measurement Methods 0.000 claims abstract description 69
- 238000012544 monitoring process Methods 0.000 claims abstract description 32
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 230000036772 blood pressure Effects 0.000 claims description 3
- 230000029058 respiratory gaseous exchange Effects 0.000 claims description 2
- 230000000977 initiatory effect Effects 0.000 claims 2
- 238000000034 method Methods 0.000 abstract description 14
- 238000004891 communication Methods 0.000 description 13
- 230000036541 health Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 238000005259 measurement Methods 0.000 description 4
- 238000013479 data entry Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 210000003484 anatomy Anatomy 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003601 intercostal effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 210000000779 thoracic wall Anatomy 0.000 description 1
- 238000002604 ultrasonography Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/08—Detecting, measuring or recording devices for evaluating the respiratory organs
- A61B5/0816—Measuring devices for examining respiratory frequency
-
- 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/021—Measuring pressure in heart or blood vessels
- A61B5/02108—Measuring pressure in heart or blood vessels from analysis of pulse wave characteristics
- A61B5/02125—Measuring pressure in heart or blood vessels from analysis of pulse wave characteristics of pulse wave propagation time
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
- A61B5/024—Detecting, measuring or recording pulse rate or heart rate
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/103—Detecting, measuring or recording devices for testing the shape, pattern, colour, size or movement of the body or parts thereof, for diagnostic purposes
- A61B5/11—Measuring movement of the entire body or parts thereof, e.g. head or hand tremor, mobility of a limb
- A61B5/113—Measuring movement of the entire body or parts thereof, e.g. head or hand tremor, mobility of a limb occurring during breathing
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/24—Detecting, measuring or recording bioelectric or biomagnetic signals of the body or parts thereof
- A61B5/25—Bioelectric electrodes therefor
- A61B5/279—Bioelectric electrodes therefor specially adapted for particular uses
- A61B5/28—Bioelectric electrodes therefor specially adapted for particular uses for electrocardiography [ECG]
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6801—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
- A61B5/6813—Specially adapted to be attached to a specific body part
- A61B5/6823—Trunk, e.g., chest, back, abdomen, hip
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6801—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
- A61B5/6813—Specially adapted to be attached to a specific body part
- A61B5/6824—Arm or wrist
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6801—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
- A61B5/683—Means for maintaining contact with the body
- A61B5/6831—Straps, bands or harnesses
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6801—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
- A61B5/683—Means for maintaining contact with the body
- A61B5/6832—Means for maintaining contact with the body using adhesives
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6801—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient specially adapted to be attached to or worn on the body surface
- A61B5/683—Means for maintaining contact with the body
- A61B5/6832—Means for maintaining contact with the body using adhesives
- A61B5/6833—Adhesive patches
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/72—Signal processing specially adapted for physiological signals or for diagnostic purposes
- A61B5/7221—Determining signal validity, reliability or quality
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/72—Signal processing specially adapted for physiological signals or for diagnostic purposes
- A61B5/7235—Details of waveform analysis
- A61B5/7246—Details of waveform analysis using correlation, e.g. template matching or determination of similarity
-
- 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/7405—Details of notification to user or communication with user or patient ; user input means using sound
-
- 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/742—Details of notification to user or communication with user or patient ; user input means using visual displays
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/02—Measuring pulse or heart rate
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/42—Details of probe positioning or probe attachment to the patient
- A61B8/4272—Details of probe positioning or probe attachment to the patient involving the acoustic interface between the transducer and the tissue
- A61B8/4281—Details of probe positioning or probe attachment to the patient involving the acoustic interface between the transducer and the tissue characterised by sound-transmitting media or devices for coupling the transducer to the tissue
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/44—Constructional features of the ultrasonic, sonic or infrasonic diagnostic device
- A61B8/4483—Constructional features of the ultrasonic, sonic or infrasonic diagnostic device characterised by features of the ultrasound transducer
- A61B8/4494—Constructional features of the ultrasonic, sonic or infrasonic diagnostic device characterised by features of the ultrasound transducer characterised by the arrangement of the transducer elements
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/48—Diagnostic techniques
- A61B8/488—Diagnostic techniques involving Doppler signals
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/52—Devices using data or image processing specially adapted for diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/5207—Devices using data or image processing specially adapted for diagnosis using ultrasonic, sonic or infrasonic waves involving processing of raw data to produce diagnostic data, e.g. for generating an image
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B8/00—Diagnosis using ultrasonic, sonic or infrasonic waves
- A61B8/56—Details of data transmission or power supply
- A61B8/565—Details of data transmission or power supply involving data transmission via a network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
- G06F21/6254—Protecting personal data, e.g. for financial or medical purposes by anonymising data, e.g. decorrelating personal data from the owner's identification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
-
- 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/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- 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/63—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 local 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
- 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
-
- 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
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/24—Detecting, measuring or recording bioelectric or biomagnetic signals of the body or parts thereof
- A61B5/316—Modalities, i.e. specific diagnostic methods
- A61B5/318—Heart-related electrical modalities, e.g. electrocardiography [ECG]
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B7/00—Instruments for auscultation
- A61B7/02—Stethoscopes
- A61B7/04—Electric stethoscopes
Definitions
- the conventional equipment used to detect and monitor patients is typically large, bulky, and expensive. While such equipment may be workable in certain settings, it can limit the freedom of movement and comfort of the patient. Further, the vital sign data collected with the conventional equipment is typically not made readily available to the patient or other caretakers. For example, although the patient or caretaker may be able to look to a bedside display to see some vital sign information, the equipment is often designed simply to periodically monitor the patient and sound an alarm (typically an audible alarm) if the measured vital sign falls above or below some threshold level.
- an alarm typically an audible alarm
- a healthcare provider For patient monitoring outside of a dedicated healthcare facility, a healthcare provider must send personnel to the home of the patient or the patient must make frequent visits to the healthcare provider. This conventional practice is limited by the frequency at which the healthcare provider can monitor the patient. Often, personnel limitations prevent the healthcare provider from checking on a patient more than a few times a week. Likewise, a patient may not be able visit the healthcare provider with sufficient frequency. Complications may arise between visits that could be avoided with more frequent health monitoring.
- monitoring devices used to gather patient vital sign information may fail to properly communicate with remote computer systems. Loss of vital sign data could result in a failure to identify a critical health situation.
- monitoring devices used to gather patient vital sign information may fail to properly communicate with remote computer systems. Loss of vital sign data could result in a failure to identify a critical health situation.
- sensitive patient data is being handled and communicated, there is a risk of disclosing data that should be secured. Finding a proper balance between enabling effective utilization of the vital sign data while protecting personal information is a serious challenge.
- the present disclosure describes systems, devices, and related methods for remotely measuring one or more vital signs of a patient, securely storing and communicating the resulting vital sign data, and configuring the vital sign data for secure access by a healthcare provider computer system to enable remote monitoring of the patient's vital signs.
- One or more vital sign monitoring devices detect patient vital signs and securely transmit the resulting vital sign data to an external computer device such as the patient's smart phone or a base station computer device.
- the external computer device communicates with a server system, such as a secure cloud storage system, which configures the vital sign measurement data and received patient identification data and makes it accessible to one or more healthcare provider computer systems.
- a computer system for securing vital sign measurement data and configuring the vital sign measurement data for accessibility by a remote system is configured to generate a unique patient identifier relating to a patient to which one or more wearable vital sign monitoring devices are associated.
- the system is also configured to receive, from a user-associated computer device, patient identification information relating to the patient. Based on the received patient identification information, and based on the unique patient identifier, the system generates a patient identity database unique to the patient to store the patient identification information (such as patient protected health information (PHI)).
- PHI patient protected health information
- the system also receives, from the user-associated computer device, vital sign measurement data indicative of one or more vital signs of the patient/user as measured by one or more wearable vital sign monitoring devices worn by the patient/user. Based on the received vital sign measurement data, and based on the unique patient identifier, the system generates a vital sign measurements database unique to the patient to store the vital sign measurement data.
- the vital sign measurements database is separate from the patient identity database.
- the system is also configured to send the vital sign measurement data from the vital sign measurement database to one or more remote computer systems to thereby enable remote monitoring of the one or more vital signs while protecting the patient's personal information.
- the internal controller is configured to receive vital sign measurement data from the sensor assembly, and to locally store the vital sign measurement data. The controller may then determine a connectivity status to an external computer device (e.g., a user-associated device such as the patient's smartphone, tablet, or personal computer).
- an external computer device e.g., a user-associated device such as the patient's smartphone, tablet, or personal computer.
- the controller Based on the determined connectivity status, when a connection is confirmed, the controller sends the vital sign measurement data to the external computer device and flags the vital sign measurement data for deletion from local storage. Alternatively, when no connection is confirmed, the controller maintains the vital sign measurement data in local storage and continue to periodically determine the connectivity status. The controller may also generate an alarm/alert/notification to notify the patient/user of the issue.
- FIGS. 1A and 1B illustrates exemplary vital sign monitoring systems comprising wearable monitoring devices
- FIG. 2 illustrates an exemplary computer architecture for a vital sign remote monitoring system
- FIG. 3 is a schematic of a server system, showing various database types that may be included within the server system;
- FIGS. 4 through 6 illustrate data structures that may be included within the various databases of the server system
- FIG. 7 is a schematic of a wearable monitoring device showing various components associated with the wearable monitoring device
- FIG. 8 is a schematic of a user-associated device communicatively linked to the wearable monitoring device of FIG. 7 and the server system of FIG. 3 , showing a vital sign measurement application and its associated components;
- FIG. 9 is a schematic of a device associated with a healthcare practitioner or facility communicatively linked to the server system, showing a differently configured vital sign measurement application.
- FIGS. 10 through 12 illustrate exemplary computer-implemented methods for configuring vital sign measurement data and enabling remote monitoring of vital sign measurement data.
- FIG. 1A illustrates an exemplary vital sign monitoring system 100 configured to monitor one or more vital signs while worn by a user.
- the wearable monitoring system 100 includes a torso monitoring device 102 and a limb monitoring device 104 .
- the torso monitoring device 102 is preferably positioned on the user's chest wall as shown, and the limb monitoring device 104 is preferably positioned on the user's upper arm as shown.
- the monitoring system 100 may be used, for example, to monitor blood pressure, temperature, respiration rate, pulse rate, and the like.
- the torso monitoring device 102 and limb monitoring device 104 may include one or more position sensors (e.g., a 9-axis sensor includes a 3-axis gyroscope, a 3-axis accelerometer, and a 3-axis magnetometer) that enable determination of the spatial position of the limb monitoring device 104 relative to the torso monitoring device 102 .
- This spatial position data can be utilized to calibrate blood pressure readings obtained using the limb monitoring device 104 .
- the torso monitoring device 102 and limb monitoring device 104 are communicatively linked to one another through a suitable communication network, such as via a Bluetooth connection and/or other personal area network (PAN).
- PAN personal area network
- the torso monitoring device 102 is shown placed on the torso wall at the fourth intercostal space in a mid-axillary position.
- the torso monitoring device 102 is also tilted relative to the transverse plane of the user in order to better receive the electrocardiogram signal from the user.
- This position also provides an effective baseline level of the height of the heart, which is useful when the torso monitoring device 102 is used in conjunction with the limb monitoring device 104 . While this represents a typical placement of the torso monitoring device 102 , it will be understood that placement may vary according to particular application requirements and according to particular user preferences, needs, and/or anatomy. Further, while the components of the monitoring system 100 are shown here as being worn on the user's right side, one or both components may be worn on the left side.
- FIG. 1B illustrates an alternative vital sign monitoring system 600 with several similarities to the system 100 .
- the system 600 includes a torso monitoring device 602 and a limb monitoring device 604 .
- the separate monitoring devices 602 and 604 are communicatively linked to one another and are configured to monitor vital signs in the same manner as like components of system 100 .
- FIG. 2 illustrates an exemplary computer system architecture for a remote monitoring system 101 .
- the system 101 enables remote monitoring of vital signs and configuring of the vital sign data for accessibility by a healthcare entity.
- the limb monitoring device 104 is communicatively linked to one or both of a user device 106 and a base station 108 .
- the torso monitoring device 102 may additionally or alternatively be connected to the user device 106 and/or base station 108 , though preferred embodiments allow the limb monitoring device 104 to manage these connections in order to minimize the size/complexity of the torso monitoring device 102 .
- the user device 106 and the base station 108 receive the vital sign data collected and sent by the monitoring devices 102 and/or 104 .
- the user device 106 may be a user's smartphone, tablet, or personal computer, for example, and will typically be associated with the monitoring devices 102 , 104 in a home monitoring setting.
- the base station 108 may be a hospital or healthcare provider computer system, and will typically be associated with the monitoring devices 102 , 104 in a healthcare facility setting.
- the user device 106 and/or base station 108 are preferably connected to the monitoring device 104 and/or monitoring device 102 with a PAN or NFC link, though they may additionally or alternatively be connected via other wired or wireless networks (with wireless being more preferred) such as a local area network (LAN), wide area network (WAN), and/or the Internet. While the remainder of the connections illustrated in FIG. 1 are preferably secured, the connection between monitoring devices 102 and 104 may simply be encrypted, as data transferred between the monitoring devices 102 and 104 will only include vital sign information and will not include sensitive patient identifying data. It is therefore less critical to have high level protection.
- LAN local area network
- WAN wide area network
- the user device 106 and/or base station 108 are configured to relay the vital sign measurement data to a secure server system 110 , which may be a dedicated computer system, a distributed computer environment, and/or a cloud computing environment.
- a secure server system 110 may be a dedicated computer system, a distributed computer environment, and/or a cloud computing environment.
- cloud computing is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services).
- the connection to the secure server system 110 should be secured, as it will likely contain private, identifying patient data.
- the user device 106 and/or base station 108 may communicate with the server system 110 via a secured cellular network connection or secured Internet connection (e.g., WiFi or Ethernet), for example.
- the server system 110 may be connected to one or more computer systems or devices associated with a healthcare facility, such as healthcare facility system 112 and/or practitioner device 114 (also referred to herein as remote devices or systems).
- the healthcare facility system 112 may include, for example, a monitoring station computer device where a nurse or other caretaker can see vital sign information from multiple patients at the same time.
- the healthcare facility system 112 may include an application enabling the system 112 to pull vital sign data from the server system 110 related to multiple patients within a ward, floor, or other division of a hospital or clinic.
- the practitioner device 114 may be, for example, a tablet or smartphone device that a doctor or nurse can interact with to visualize patient vital sign data pulled from the server system 110 .
- FIG. 3 schematically illustrates components that may be included in the server system 110 .
- the server system 110 may include a patient ID database 116 .
- a patient ID from the patient ID database 116 is assigned.
- the patient ID preferably omits any information related to region, time, date, or other information related to private patient data.
- the patient ID may be, for example, a random string of characters.
- a start time is also recorded, at the time the patient ID is assigned, to function as a baseline for determining the relative time of subsequent vital sign measurements.
- FIG. 4 provides an example of an entry 301 that could be included within the patient ID database 116 .
- the entry 301 includes a patient ID 302 , a “used” field 304 indicating whether it has been assigned to a patient, and a start time 306 .
- the patient ID 302 is preferably a pre-defined, unique, random number of at least 8 digits, though other embodiments may include differently configured patient IDs.
- the start time 306 may be based on Greenwich Mean Time, as shown, or may utilize any other suitable base time measurement.
- the server system 110 may also include separate databases created for each patient. For example, once a patient ID has been recorded as assigned in the patient ID database 116 , a vital sign measurement database 118 and a protected health information (PHI) database 120 are each separately created for the patient.
- the vital sign measurement database 118 includes de-identified vital sign measurements related to the patient and the relative time the vital sign measurements were obtained, and the PHI database 120 includes private protected health information (PHI) such as name, age, weight, etcetera.
- PHI protected health information
- FIG. 5 illustrates an example of a vital sign measurement entry 307
- FIG. 6 illustrates an example of a patient identity data entry 317
- the data within the vital sign measurement entry 307 is de-identified from any PHI related to the patient, and the private PHI information stored within the patient identity data entry 317 is only linkable to the other data by way of the unique patient ID 302 .
- the vital sign measurement entry 307 includes the patient ID 302 , the relative time 310 since the start time that the measurement was taken, the data type 312 (e.g., vital sign measured), the data value 314 in units according to data type 312 , and a data quality score 316 assigned based on the determined accuracy or quality of the measurement.
- the patient identity data entry 317 separately stores PHI such as patient name, address, birthdate/age, height, weight, gender, and the like. Generating and storing separate databases 118 and 120 for vital sign measurement data and patient identification information, respectively, beneficially “quarantines” the private PHI to reduce or eliminate the risk of unintended dissemination of PHI.
- the vital sign measurement data is made remotely accessible to healthcare personnel and/or caretakers remote from the user.
- the vital sign measurement data is not directly linked to any identifiable patient, and can only be linked to a particular patient using the unique patient ID 302 .
- the PHI database 120 may have greater security than the vital sign measurement database 118 , and will only be accessible to those with authority, such as the user and possibly the user's primary physician.
- FIG. 7 schematically illustrates components that may be included as part of the vital sign monitoring device 102 and/or 104 .
- a sensor assembly 172 is configured for measuring one or more of the patient's vital signs, as described above.
- a controller 161 includes memory 162 and a processor 164 . As with other processors described herein, the processor 164 can perform Boolean logic or can produce a pre-determined output based on input.
- the processor 164 can include ROM memory, programmable logic device (PLD), programmable array logic (PAL), generic array logic (GAL), complex programmable logic device (CPLD), field programmable gate arrays (FPGA), logic gates, processors, or any other logic function.
- the memory 162 may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other physical and tangible storage medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computing system.
- Such memory devices may also be referred to herein as “computer-readable storage media” or a “hardware storage device.”
- the vital sign monitoring device 102 and/or 104 also includes a communication module 166 to enable communications with one or more external devices (e.g., the user device 106 and/or base station 108 ).
- these communications utilize NFC and/or a PAN, such as through a Bluetooth connection.
- the connection between the vital sign monitoring device(s) and the user device 106 and/or base station 108 may additionally or alternatively include a hardwired connection and/or the use of other communication modalities that utilize other communication media, such as optical (e.g., infrared), ultrasound, or infrasound transmissions.
- the communication protocol is intended to allow seamless connection between the monitoring device(s) and the user device 106 and/or base station 108 .
- the typical user may not be technically savvy and the pairing process should therefore be straightforward and relatively simple.
- the pairing process utilizes one or more of Bluetooth BR/EDR Secure Simple Pairing (SSP) and Bluetooth Low Energy (BLE) Out-of-Band (OOB) pairing protocols.
- SSP Bluetooth BR/EDR Secure Simple Pairing
- BLE Bluetooth Low Energy
- OOB Out-of-Band
- the vital sign monitoring device 102 and/or 104 also includes a connectivity determiner 170 configured to determine the connectivity status between the monitoring device 102 and/or 104 and the external device.
- the connectivity determiner 170 operates in conjunction with a vital sign data router 171 to minimize the risk of vital sign data loss. For example, when the connectivity determiner 170 determines that there is an adequate connection to the external device, the vital sign data router 171 operates to send the vital sign data to the external device and flags the vital sign data for deletion (e.g., upon acknowledgment from the external device that the communication has been received). On the other hand, when the connectivity determiner 170 determines that there is no or insufficient connectivity to the external device, the vital sign data router 171 operates to store vital sign data in local storage/memory 162 until an adequate connection can be established.
- sent vital sign data may be flagged for deletion to minimize data storage requirements at the monitoring device 102 and/or 104 .
- the vital sign data that has been confirmed as sent does not need to be immediately deleted.
- sent data may be stored for a predetermined time period or until another event occurs to provide for deletion.
- unsent data should be locally stored for as long as possible until a connection can be established.
- the connectivity determiner 170 may also operate to give a notification or warning to alert the user when connectivity is lost.
- the monitoring device 102 and/or 104 may include a light, display, and/or speaker configured to give an audio and/or visual notification when no connection is determined.
- FIG. 8 schematically illustrates components that may be included as part of the user device 106 and/or the base station 108 (referred to hereafter for simplicity as the user device 106 ).
- the user device 106 includes memory 122 , a processor 124 , and a communications module 126 configured to enable communications with the monitoring device(s) 102 and/or 104 and to enable communications with the server system 110 .
- the user device 106 may include a vital sign application 128 configured to provide several features related to vital sign monitoring. In a typical embodiment, these features are included as part of the vital sign application 128 , but they need not all be provided as part of the same dedicated application, and one or more of the illustrated modules/operations may be provided by other applications and/or by the native programming of the user device 106 itself.
- the vital sign application 128 includes a connectivity notifier 130 configured to notify a user of the connection status of the user device 106 to the monitoring device 102 , 104 and/or to the server system 110 .
- the vital sign application 128 also includes a vital sign data display 132 configured to organize the received vital sign data into displayable results for display on a user interface of the user device 106 .
- the application 128 also includes a vital sign data configuration module 134 that enables a user to configure the vital sign data transmitted to the server system 110 .
- the configuration module 134 may provide user-selectable options controlling, for example, an on/off state of data transmission, how often vital sign data is sent, which vital sign data types to send, and time periods in which vital sign data is sent (e.g., off during the day, on at night).
- the illustrated application 128 also includes vital sign monitoring device controls 136 which provides user-selectable controls for configuring the monitoring device 102 and/or 104 .
- the monitoring device controls 136 may include controls related to, for example, power settings, device registration, account settings, monitoring frequency, vital signs to monitor, monitoring time periods, and on/off controls.
- the application 128 may also include a patient ID information interface 138 configured to provide for input and control of the user's identification information such as the patient information shown in FIG. 6 .
- the interface 138 may be secured (e.g., via password, biometric key, and/or other security feature) so that only the authorized user is able to access and input patient identity information.
- the user device 106 may include components that cause it to locally store sufficient vital sign data to minimize or reduce data loss. For example, similar to the monitoring devices 102 and/or 104 , the user device 106 may locally store the received vital sign data until connection with the server system 110 has been confirmed and the data has been securely transmitted. Once transmitted, the data may be flagged for deletion, or at least flagged to be deleted or overwritten prior to any non-transmitted vital sign data.
- FIG. 9 schematically illustrates components that may be included as part of a healthcare facility system 112 and/or practitioner device 114 .
- the illustrated device includes memory 142 , a processor 144 , and a communications module 146 to enable communication with the server system 110 .
- the vital sign application 148 may be similar to the vital sign application 128 of the user device 106 , except it may omit certain features that are unique to the user device 106 and that are preferably maintained under user control.
- the application 148 includes a connectivity notifier 150 and a vital sign data display 152 , it omits a vital sign data configuration module, leaving control over the frequency and type of available vital sign data to the user.
- the illustrated embodiment includes vital sign monitoring controls 156 , allowing healthcare personnel to adjust the acuity, vital sign type, or sampling rate of the monitoring device as needed.
- the application 148 includes a patient ID display 158 , which may allow patient ID information to be visualized but not edited. Thus, a doctor or nurse with access permission may be able to visualize, but not change, the patient's private information.
- Other embodiments may include other differences between the vital sign application at the user device and at the healthcare facility device. For instance, some of the features omitted from vital sign application 148 in the illustrated embodiment may in some circumstances be included, such as where it is beneficial to allow healthcare personnel to configure/control the gathered vital sign data. Some embodiments may omit or limit the vital sign monitoring device controls 156 of the application 148 , leaving the user with greater control over the related options.
- FIG. 10 illustrates an example method 200 of configuring vital sign data using the remote monitoring system 101 and in particular the server system 110 as shown in FIG. 3 .
- the system determines whether the patient is a new patient (step 202 ). For new patients, the system then initializes the patient into the system by getting or generating a patient ID from the patient ID database (step 204 ), marks the patient ID as used (step 206 ), and defines and records a start time associated with the patient ID (step 208 ).
- the system also creates two separate databases for each patient by creating a patient vital sign measurement database (step 210 ) and a patient private PHI database (step 212 ).
- the method 200 determines whether it is time for a new reading (step 214 ). This may be done according to a predefined schedule and/or may occur based on a push command (e.g., initiated at the user device 106 ) or a pull command (e.g., initiated at the server system 110 ).
- the system Upon receipt of a new vital sign reading, the system records the vital sign data in the vital sign measurement database (step 216 ) and records the associated relative time of the measurement in the vital sign measurement database (step 218 ).
- the method 200 may also determine whether to update patient private PHI (step 220 ), and if needed, update the patient private PHI database (step 222 ).
- FIG. 11 illustrates an exemplary method 400 of configuring the transmission of vital sign data using the monitoring device(s) 102 and/or 104 as shown in FIG. 7 .
- the controller 161 of the monitoring device receives vital sign measurement data from the sensor assembly 172 (step 402 ).
- the received vital sign data is then locally stored (step 404 ).
- the controller 161 determines a connectivity status to an external computer device (e.g., the user device 106 and/or base station 108 ) (step 406 ). Based on the determined connectivity status, when sufficient connectivity is established, the controller 161 sends the vital sign data to the external computer device and flags the vital sign data for deletion from local storage (step 408 ).
- an external computer device e.g., the user device 106 and/or base station 108
- the controller maintains the vital sign measurement data in local storage and continues to periodically determine the connectivity status (step 410 ).
- vital sign data that has been “flagged for deletion” does not necessarily need to be immediately deleted. However, such data will be deleted or overwritten prior to any vital sign data that has not yet been confirmed as transmitted.
- FIG. 12 illustrates an exemplary method 500 of configuring the transmission of vital sign data using the user device 106 and/or base station 108 as shown in FIG. 8 .
- the device receives vital sign data from the monitoring device(s) 102 and/or 104 (step 502 ) and locally stores the vital sign data (step 504 ).
- the device determines a connectivity status to the server computer system (step 506 ). Based on the determined connectivity status, the device sends the vital sign measurement data to the server computer system (step 508 ) or maintains the vital sign data in local storage and generates a notification message (e.g., for display at an interface of the user device 106 /base station 108 ) indicating a lack of connectivity (step 510 ).
- a notification message e.g., for display at an interface of the user device 106 /base station 108
- module refers to a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof.
- structure of an executable component may include software objects, routines, methods, and so forth, that may be executed on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media.
- embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors (of the associated computing system that performs the act) direct the operation of the computing system in response to having executed computer-executable instructions that constitute an executable component.
- processors of the associated computing system that performs the act
- computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product.
Landscapes
- Health & Medical Sciences (AREA)
- Life Sciences & Earth Sciences (AREA)
- Engineering & Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Biomedical Technology (AREA)
- Public Health (AREA)
- Physics & Mathematics (AREA)
- Pathology (AREA)
- Animal Behavior & Ethology (AREA)
- Surgery (AREA)
- Molecular Biology (AREA)
- Biophysics (AREA)
- Heart & Thoracic Surgery (AREA)
- Veterinary Medicine (AREA)
- Physiology (AREA)
- Cardiology (AREA)
- Radiology & Medical Imaging (AREA)
- Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
- Pulmonology (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Primary Health Care (AREA)
- Epidemiology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Computer Networks & Wireless Communication (AREA)
- Bioethics (AREA)
- Dentistry (AREA)
- Oral & Maxillofacial Surgery (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Psychiatry (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Signal Processing (AREA)
- Artificial Intelligence (AREA)
- Gynecology & Obstetrics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
Abstract
Disclosed herein are systems, devices, and methods for remotely measuring one or more vital signs of a patient, securely storing and communicating the resulting vital sign data, and configuring the vital sign data for secure access by a healthcare provider computer system to enable remote monitoring of the patients vital signs. One or more vital sign monitoring devices detect patient vital signs and securely transmit the resulting vital sign data to an external computer device such as the patients smart phone or abase station computer device. The external computer device communicates with a server system, such as a secure cloud storage system, which configures the vital sign measurement data and received patient identification data and makes it accessible to one or more healthcare provider computer systems.
Description
- Hospitals and other healthcare facilities routinely monitor patients' vital signs. The conventional equipment used to detect and monitor patients is typically large, bulky, and expensive. While such equipment may be workable in certain settings, it can limit the freedom of movement and comfort of the patient. Further, the vital sign data collected with the conventional equipment is typically not made readily available to the patient or other caretakers. For example, although the patient or caretaker may be able to look to a bedside display to see some vital sign information, the equipment is often designed simply to periodically monitor the patient and sound an alarm (typically an audible alarm) if the measured vital sign falls above or below some threshold level.
- In addition, some patients may require health monitoring outside of a dedicated healthcare facility, such as in their own homes. In cases where monitoring is insufficient or the gathered vital sign data is not properly managed, complications may arise and emergency situations may develop. In many cases these complications are preventable and can be avoided if the patient's health is properly monitored and communicated.
- Typically, for patient monitoring outside of a dedicated healthcare facility, a healthcare provider must send personnel to the home of the patient or the patient must make frequent visits to the healthcare provider. This conventional practice is limited by the frequency at which the healthcare provider can monitor the patient. Often, personnel limitations prevent the healthcare provider from checking on a patient more than a few times a week. Likewise, a patient may not be able visit the healthcare provider with sufficient frequency. Complications may arise between visits that could be avoided with more frequent health monitoring.
- Accordingly, there is a long felt and ongoing need for systems, devices, and methods for enabling remote monitoring of patients. Providing remote monitoring of patients presents several technical challenges. For example, monitoring devices used to gather patient vital sign information may fail to properly communicate with remote computer systems. Loss of vital sign data could result in a failure to identify a critical health situation. In addition, whenever sensitive patient data is being handled and communicated, there is a risk of disclosing data that should be secured. Finding a proper balance between enabling effective utilization of the vital sign data while protecting personal information is a serious challenge.
- The present disclosure describes systems, devices, and related methods for remotely measuring one or more vital signs of a patient, securely storing and communicating the resulting vital sign data, and configuring the vital sign data for secure access by a healthcare provider computer system to enable remote monitoring of the patient's vital signs. One or more vital sign monitoring devices detect patient vital signs and securely transmit the resulting vital sign data to an external computer device such as the patient's smart phone or a base station computer device. The external computer device communicates with a server system, such as a secure cloud storage system, which configures the vital sign measurement data and received patient identification data and makes it accessible to one or more healthcare provider computer systems.
- In one embodiment, a computer system for securing vital sign measurement data and configuring the vital sign measurement data for accessibility by a remote system is configured to generate a unique patient identifier relating to a patient to which one or more wearable vital sign monitoring devices are associated. The system is also configured to receive, from a user-associated computer device, patient identification information relating to the patient. Based on the received patient identification information, and based on the unique patient identifier, the system generates a patient identity database unique to the patient to store the patient identification information (such as patient protected health information (PHI)).
- The system also receives, from the user-associated computer device, vital sign measurement data indicative of one or more vital signs of the patient/user as measured by one or more wearable vital sign monitoring devices worn by the patient/user. Based on the received vital sign measurement data, and based on the unique patient identifier, the system generates a vital sign measurements database unique to the patient to store the vital sign measurement data. The vital sign measurements database is separate from the patient identity database. The system is also configured to send the vital sign measurement data from the vital sign measurement database to one or more remote computer systems to thereby enable remote monitoring of the one or more vital signs while protecting the patient's personal information.
- In another embodiment, a wearable vital sign monitoring system configured to enable remote monitoring of vital sign measurements comprises a sensor assembly and an internal controller. The internal controller is configured to receive vital sign measurement data from the sensor assembly, and to locally store the vital sign measurement data. The controller may then determine a connectivity status to an external computer device (e.g., a user-associated device such as the patient's smartphone, tablet, or personal computer).
- Based on the determined connectivity status, when a connection is confirmed, the controller sends the vital sign measurement data to the external computer device and flags the vital sign measurement data for deletion from local storage. Alternatively, when no connection is confirmed, the controller maintains the vital sign measurement data in local storage and continue to periodically determine the connectivity status. The controller may also generate an alarm/alert/notification to notify the patient/user of the issue.
- Additional features and advantages will be set forth in part in the description that follows. It is to be understood that both the foregoing summary and the following detailed description are exemplary and explanatory only, and are not to be read as limiting the disclosure to any particular set of embodiments.
- A more particular description will be rendered by the embodiments illustrated in the appended drawings. It is appreciated that these drawings depict only exemplary embodiments of the disclosure and are therefore not to be considered limiting of its scope. In the accompanying drawings:
-
FIGS. 1A and 1B illustrates exemplary vital sign monitoring systems comprising wearable monitoring devices; -
FIG. 2 illustrates an exemplary computer architecture for a vital sign remote monitoring system; -
FIG. 3 is a schematic of a server system, showing various database types that may be included within the server system; -
FIGS. 4 through 6 illustrate data structures that may be included within the various databases of the server system; -
FIG. 7 is a schematic of a wearable monitoring device showing various components associated with the wearable monitoring device; -
FIG. 8 is a schematic of a user-associated device communicatively linked to the wearable monitoring device ofFIG. 7 and the server system ofFIG. 3 , showing a vital sign measurement application and its associated components; -
FIG. 9 is a schematic of a device associated with a healthcare practitioner or facility communicatively linked to the server system, showing a differently configured vital sign measurement application; and -
FIGS. 10 through 12 illustrate exemplary computer-implemented methods for configuring vital sign measurement data and enabling remote monitoring of vital sign measurement data. -
FIG. 1A illustrates an exemplary vitalsign monitoring system 100 configured to monitor one or more vital signs while worn by a user. Thewearable monitoring system 100 includes atorso monitoring device 102 and alimb monitoring device 104. Thetorso monitoring device 102 is preferably positioned on the user's chest wall as shown, and thelimb monitoring device 104 is preferably positioned on the user's upper arm as shown. Themonitoring system 100 may be used, for example, to monitor blood pressure, temperature, respiration rate, pulse rate, and the like. - The
torso monitoring device 102 andlimb monitoring device 104 may include one or more position sensors (e.g., a 9-axis sensor includes a 3-axis gyroscope, a 3-axis accelerometer, and a 3-axis magnetometer) that enable determination of the spatial position of thelimb monitoring device 104 relative to thetorso monitoring device 102. This spatial position data can be utilized to calibrate blood pressure readings obtained using thelimb monitoring device 104. Thetorso monitoring device 102 andlimb monitoring device 104 are communicatively linked to one another through a suitable communication network, such as via a Bluetooth connection and/or other personal area network (PAN). - In
FIG. 1A , thetorso monitoring device 102 is shown placed on the torso wall at the fourth intercostal space in a mid-axillary position. Thetorso monitoring device 102 is also tilted relative to the transverse plane of the user in order to better receive the electrocardiogram signal from the user. This position also provides an effective baseline level of the height of the heart, which is useful when thetorso monitoring device 102 is used in conjunction with thelimb monitoring device 104. While this represents a typical placement of thetorso monitoring device 102, it will be understood that placement may vary according to particular application requirements and according to particular user preferences, needs, and/or anatomy. Further, while the components of themonitoring system 100 are shown here as being worn on the user's right side, one or both components may be worn on the left side. -
FIG. 1B illustrates an alternative vitalsign monitoring system 600 with several similarities to thesystem 100. Thesystem 600 includes atorso monitoring device 602 and alimb monitoring device 604. Theseparate monitoring devices system 100. -
FIG. 2 illustrates an exemplary computer system architecture for aremote monitoring system 101. Thesystem 101 enables remote monitoring of vital signs and configuring of the vital sign data for accessibility by a healthcare entity. Thelimb monitoring device 104 is communicatively linked to one or both of a user device 106 and abase station 108. Thetorso monitoring device 102 may additionally or alternatively be connected to the user device 106 and/orbase station 108, though preferred embodiments allow thelimb monitoring device 104 to manage these connections in order to minimize the size/complexity of thetorso monitoring device 102. - The user device 106 and the base station 108 (also referred to herein as “external computer devices”) receive the vital sign data collected and sent by the
monitoring devices 102 and/or 104. The user device 106 may be a user's smartphone, tablet, or personal computer, for example, and will typically be associated with themonitoring devices base station 108 may be a hospital or healthcare provider computer system, and will typically be associated with themonitoring devices - The user device 106 and/or
base station 108 are preferably connected to themonitoring device 104 and/ormonitoring device 102 with a PAN or NFC link, though they may additionally or alternatively be connected via other wired or wireless networks (with wireless being more preferred) such as a local area network (LAN), wide area network (WAN), and/or the Internet. While the remainder of the connections illustrated inFIG. 1 are preferably secured, the connection betweenmonitoring devices monitoring devices - The user device 106 and/or
base station 108 are configured to relay the vital sign measurement data to asecure server system 110, which may be a dedicated computer system, a distributed computer environment, and/or a cloud computing environment. In this description and the following claims, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The connection to thesecure server system 110 should be secured, as it will likely contain private, identifying patient data. The user device 106 and/orbase station 108 may communicate with theserver system 110 via a secured cellular network connection or secured Internet connection (e.g., WiFi or Ethernet), for example. - As shown, the
server system 110 may be connected to one or more computer systems or devices associated with a healthcare facility, such ashealthcare facility system 112 and/or practitioner device 114 (also referred to herein as remote devices or systems). Thehealthcare facility system 112 may include, for example, a monitoring station computer device where a nurse or other caretaker can see vital sign information from multiple patients at the same time. For example, thehealthcare facility system 112 may include an application enabling thesystem 112 to pull vital sign data from theserver system 110 related to multiple patients within a ward, floor, or other division of a hospital or clinic. Thepractitioner device 114 may be, for example, a tablet or smartphone device that a doctor or nurse can interact with to visualize patient vital sign data pulled from theserver system 110. -
FIG. 3 schematically illustrates components that may be included in theserver system 110. As shown, theserver system 110 may include apatient ID database 116. When a new patient is entered into the system, a patient ID from thepatient ID database 116 is assigned. The patient ID preferably omits any information related to region, time, date, or other information related to private patient data. The patient ID may be, for example, a random string of characters. A start time is also recorded, at the time the patient ID is assigned, to function as a baseline for determining the relative time of subsequent vital sign measurements. -
FIG. 4 provides an example of anentry 301 that could be included within thepatient ID database 116. Theentry 301 includes apatient ID 302, a “used” field 304 indicating whether it has been assigned to a patient, and a start time 306. As shown, thepatient ID 302 is preferably a pre-defined, unique, random number of at least 8 digits, though other embodiments may include differently configured patient IDs. The start time 306 may be based on Greenwich Mean Time, as shown, or may utilize any other suitable base time measurement. - The
server system 110 may also include separate databases created for each patient. For example, once a patient ID has been recorded as assigned in thepatient ID database 116, a vital sign measurement database 118 and a protected health information (PHI)database 120 are each separately created for the patient. The vital sign measurement database 118 includes de-identified vital sign measurements related to the patient and the relative time the vital sign measurements were obtained, and thePHI database 120 includes private protected health information (PHI) such as name, age, weight, etcetera. -
FIG. 5 illustrates an example of a vitalsign measurement entry 307, andFIG. 6 illustrates an example of a patientidentity data entry 317. The data within the vitalsign measurement entry 307 is de-identified from any PHI related to the patient, and the private PHI information stored within the patientidentity data entry 317 is only linkable to the other data by way of theunique patient ID 302. As shown, the vitalsign measurement entry 307 includes thepatient ID 302, therelative time 310 since the start time that the measurement was taken, the data type 312 (e.g., vital sign measured), thedata value 314 in units according todata type 312, and adata quality score 316 assigned based on the determined accuracy or quality of the measurement. - The patient
identity data entry 317 separately stores PHI such as patient name, address, birthdate/age, height, weight, gender, and the like. Generating and storingseparate databases 118 and 120 for vital sign measurement data and patient identification information, respectively, beneficially “quarantines” the private PHI to reduce or eliminate the risk of unintended dissemination of PHI. At the same time, the vital sign measurement data is made remotely accessible to healthcare personnel and/or caretakers remote from the user. The vital sign measurement data is not directly linked to any identifiable patient, and can only be linked to a particular patient using theunique patient ID 302. ThePHI database 120 may have greater security than the vital sign measurement database 118, and will only be accessible to those with authority, such as the user and possibly the user's primary physician. -
FIG. 7 schematically illustrates components that may be included as part of the vitalsign monitoring device 102 and/or 104. Asensor assembly 172 is configured for measuring one or more of the patient's vital signs, as described above. Acontroller 161 includesmemory 162 and aprocessor 164. As with other processors described herein, theprocessor 164 can perform Boolean logic or can produce a pre-determined output based on input. - The
processor 164 can include ROM memory, programmable logic device (PLD), programmable array logic (PAL), generic array logic (GAL), complex programmable logic device (CPLD), field programmable gate arrays (FPGA), logic gates, processors, or any other logic function. As with other memory components described herein, thememory 162 may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other physical and tangible storage medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computing system. Such memory devices may also be referred to herein as “computer-readable storage media” or a “hardware storage device.” - The vital
sign monitoring device 102 and/or 104 also includes acommunication module 166 to enable communications with one or more external devices (e.g., the user device 106 and/or base station 108). Preferably, these communications utilize NFC and/or a PAN, such as through a Bluetooth connection. The connection between the vital sign monitoring device(s) and the user device 106 and/orbase station 108 may additionally or alternatively include a hardwired connection and/or the use of other communication modalities that utilize other communication media, such as optical (e.g., infrared), ultrasound, or infrasound transmissions. - The communication protocol is intended to allow seamless connection between the monitoring device(s) and the user device 106 and/or
base station 108. In particular, the typical user may not be technically savvy and the pairing process should therefore be straightforward and relatively simple. In one embodiment, for example, the pairing process utilizes one or more of Bluetooth BR/EDR Secure Simple Pairing (SSP) and Bluetooth Low Energy (BLE) Out-of-Band (OOB) pairing protocols. The benefits of a simple pairing process should be balanced against the need to provide sufficient security, however, because the transmitted data will include sensitive health information. As such, some preferred embodiments utilize BLE at reduced power to ensure that the transmissions are limited to the proximity of the linked monitoring device(s). For example, whereas a standard class 1 Bluetooth device has a range of about 100 m, the disclosed connection transmissions may limit this by about 25%, or by about 50%, or by about 75%, or by about 90%. - The vital
sign monitoring device 102 and/or 104 also includes aconnectivity determiner 170 configured to determine the connectivity status between themonitoring device 102 and/or 104 and the external device. Theconnectivity determiner 170 operates in conjunction with a vitalsign data router 171 to minimize the risk of vital sign data loss. For example, when theconnectivity determiner 170 determines that there is an adequate connection to the external device, the vitalsign data router 171 operates to send the vital sign data to the external device and flags the vital sign data for deletion (e.g., upon acknowledgment from the external device that the communication has been received). On the other hand, when theconnectivity determiner 170 determines that there is no or insufficient connectivity to the external device, the vitalsign data router 171 operates to store vital sign data in local storage/memory 162 until an adequate connection can be established. - These operations ensure that no vital sign data is lost due to connectivity issues. At the same time, once connectivity is established, sent vital sign data may be flagged for deletion to minimize data storage requirements at the
monitoring device 102 and/or 104. Of course, the vital sign data that has been confirmed as sent does not need to be immediately deleted. Even sent data may be stored for a predetermined time period or until another event occurs to provide for deletion. However, such “flagged for deletion” data will be managed differently than data that has not been sent to the external device. Such unsent data should be locally stored for as long as possible until a connection can be established. - The
connectivity determiner 170 may also operate to give a notification or warning to alert the user when connectivity is lost. For example, themonitoring device 102 and/or 104 may include a light, display, and/or speaker configured to give an audio and/or visual notification when no connection is determined. -
FIG. 8 schematically illustrates components that may be included as part of the user device 106 and/or the base station 108 (referred to hereafter for simplicity as the user device 106). The user device 106 includesmemory 122, aprocessor 124, and acommunications module 126 configured to enable communications with the monitoring device(s) 102 and/or 104 and to enable communications with theserver system 110. The user device 106 may include avital sign application 128 configured to provide several features related to vital sign monitoring. In a typical embodiment, these features are included as part of thevital sign application 128, but they need not all be provided as part of the same dedicated application, and one or more of the illustrated modules/operations may be provided by other applications and/or by the native programming of the user device 106 itself. - In the illustrated embodiment, the
vital sign application 128 includes aconnectivity notifier 130 configured to notify a user of the connection status of the user device 106 to themonitoring device server system 110. Thevital sign application 128 also includes a vital sign data display 132 configured to organize the received vital sign data into displayable results for display on a user interface of the user device 106. Theapplication 128 also includes a vital sign data configuration module 134 that enables a user to configure the vital sign data transmitted to theserver system 110. The configuration module 134 may provide user-selectable options controlling, for example, an on/off state of data transmission, how often vital sign data is sent, which vital sign data types to send, and time periods in which vital sign data is sent (e.g., off during the day, on at night). - The illustrated
application 128 also includes vital sign monitoring device controls 136 which provides user-selectable controls for configuring themonitoring device 102 and/or 104. The monitoring device controls 136 may include controls related to, for example, power settings, device registration, account settings, monitoring frequency, vital signs to monitor, monitoring time periods, and on/off controls. Theapplication 128 may also include a patientID information interface 138 configured to provide for input and control of the user's identification information such as the patient information shown inFIG. 6 . Theinterface 138 may be secured (e.g., via password, biometric key, and/or other security feature) so that only the authorized user is able to access and input patient identity information. - The user device 106 may include components that cause it to locally store sufficient vital sign data to minimize or reduce data loss. For example, similar to the
monitoring devices 102 and/or 104, the user device 106 may locally store the received vital sign data until connection with theserver system 110 has been confirmed and the data has been securely transmitted. Once transmitted, the data may be flagged for deletion, or at least flagged to be deleted or overwritten prior to any non-transmitted vital sign data. -
FIG. 9 schematically illustrates components that may be included as part of ahealthcare facility system 112 and/orpractitioner device 114. The illustrated device includesmemory 142, aprocessor 144, and acommunications module 146 to enable communication with theserver system 110. Thevital sign application 148 may be similar to thevital sign application 128 of the user device 106, except it may omit certain features that are unique to the user device 106 and that are preferably maintained under user control. For example, while theapplication 148 includes aconnectivity notifier 150 and a vital sign data display 152, it omits a vital sign data configuration module, leaving control over the frequency and type of available vital sign data to the user. The illustrated embodiment includes vital sign monitoring controls 156, allowing healthcare personnel to adjust the acuity, vital sign type, or sampling rate of the monitoring device as needed. - In another example, the
application 148 includes apatient ID display 158, which may allow patient ID information to be visualized but not edited. Thus, a doctor or nurse with access permission may be able to visualize, but not change, the patient's private information. Other embodiments may include other differences between the vital sign application at the user device and at the healthcare facility device. For instance, some of the features omitted fromvital sign application 148 in the illustrated embodiment may in some circumstances be included, such as where it is beneficial to allow healthcare personnel to configure/control the gathered vital sign data. Some embodiments may omit or limit the vital sign monitoring device controls 156 of theapplication 148, leaving the user with greater control over the related options. -
FIG. 10 illustrates anexample method 200 of configuring vital sign data using theremote monitoring system 101 and in particular theserver system 110 as shown inFIG. 3 . The system determines whether the patient is a new patient (step 202). For new patients, the system then initializes the patient into the system by getting or generating a patient ID from the patient ID database (step 204), marks the patient ID as used (step 206), and defines and records a start time associated with the patient ID (step 208). The system also creates two separate databases for each patient by creating a patient vital sign measurement database (step 210) and a patient private PHI database (step 212). - If the patient has already been initialized into the system, the
method 200 determines whether it is time for a new reading (step 214). This may be done according to a predefined schedule and/or may occur based on a push command (e.g., initiated at the user device 106) or a pull command (e.g., initiated at the server system 110). Upon receipt of a new vital sign reading, the system records the vital sign data in the vital sign measurement database (step 216) and records the associated relative time of the measurement in the vital sign measurement database (step 218). Themethod 200 may also determine whether to update patient private PHI (step 220), and if needed, update the patient private PHI database (step 222). -
FIG. 11 illustrates anexemplary method 400 of configuring the transmission of vital sign data using the monitoring device(s) 102 and/or 104 as shown inFIG. 7 . Thecontroller 161 of the monitoring device receives vital sign measurement data from the sensor assembly 172 (step 402). The received vital sign data is then locally stored (step 404). Thecontroller 161 determines a connectivity status to an external computer device (e.g., the user device 106 and/or base station 108) (step 406). Based on the determined connectivity status, when sufficient connectivity is established, thecontroller 161 sends the vital sign data to the external computer device and flags the vital sign data for deletion from local storage (step 408). - Alternatively, when connectivity is not established, the controller maintains the vital sign measurement data in local storage and continues to periodically determine the connectivity status (step 410). As described above, vital sign data that has been “flagged for deletion” does not necessarily need to be immediately deleted. However, such data will be deleted or overwritten prior to any vital sign data that has not yet been confirmed as transmitted.
-
FIG. 12 illustrates anexemplary method 500 of configuring the transmission of vital sign data using the user device 106 and/orbase station 108 as shown inFIG. 8 . The device receives vital sign data from the monitoring device(s) 102 and/or 104 (step 502) and locally stores the vital sign data (step 504). The device determines a connectivity status to the server computer system (step 506). Based on the determined connectivity status, the device sends the vital sign measurement data to the server computer system (step 508) or maintains the vital sign data in local storage and generates a notification message (e.g., for display at an interface of the user device 106/base station 108) indicating a lack of connectivity (step 510). - The terms “module,” “component,” and the like refer to a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods, and so forth, that may be executed on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media.
- Within this disclosure, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors (of the associated computing system that performs the act) direct the operation of the computing system in response to having executed computer-executable instructions that constitute an executable component. For example, such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product.
- Terms such as “approximately,” “about,” and “substantially,” as used herein represent an amount or condition close to the stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a stated amount or condition.
- Specific elements or components described in relation to any particular embodiment described herein may be substituted for or combined with elements described in relation to any other embodiment described herein. For example, any of the methods described in
FIGS. 10 through 12 may make use of any of the computer system embodiments and components shown inFIGS. 1 through 9 .
Claims (20)
1. A computer system for securing vital sign measurement data and configuring the vital sign measurement data for accessibility by a remote system to enable remote monitoring of one or more patient vital signs, the computer system being communicatively coupled to one or more wearable vital sign monitoring devices, the computer system comprising:
one or more processors;
one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to
generate a unique patient identifier relating to a patient to which one or more wearable vital sign monitoring devices are associated;
receive, from a user-associated computer device, patient personal information relating to the patient;
based on the received patient personal information, and based on the unique patient identifier, generate a patient protected information database unique to the patient to store the patient personal information;
receive, from the user-associated computer device, vital sign measurement data indicative of one or more vital signs of the patient as measured by the one or more wearable vital sign monitoring devices;
based on the received vital sign measurement data, and based on the unique patient identifier, generate a vital sign measurements database unique to the patient to store the vital sign measurement data, the vital sign measurements database being separate from the patient protected information database; and
send vital sign measurement data from the vital sign measurement database to one or more remote computer systems to thereby enable remote monitoring of the one or more vital signs.
2. The computer system of claim 1 , wherein the computer-executable instructions are further configured to cause the computer system to generate a time stamp representing a start time when the unique patient identifier is generated.
3. The computer system of claim 2 , wherein the computer-executable instructions are further configured to cause the computer system to, for each vital sign measurement stored within the vital sign measurements database, generate a relative time stamp representing a relative time at which the vital sign was measured with respect to the start time.
4. The computer system of claim 1 , wherein vital sign measurement data is received at pre-determined intervals.
5. The computer system of claim 1 , wherein the vital sign measurement data includes data associated with one or more vital signs selected from the group consisting of; temperature, pulse rate, respiration rate, blood pressure, and body part position.
6. The computer system of claim 1 , wherein the one or more remote computer systems includes a computer system associated with a healthcare facility and/or a healthcare practitioner.
7. The computer system of claim 1 , wherein the computer-executable instructions are further configured to cause the computer system to:
receive, from the user-associated computer device, an initiation or stop command for collecting patient vital sign measurement data, and
based on the initiation or stop command, initiate or stop receiving vital sign measurement data from the user-associated computer device.
8. The computer system of claim 1 , wherein the computer-executable instructions are further configured to cause the computer system to:
receive, from the remote computer system, a vital sign measurement data request;
receive, from the remote computer system, the unique patient identifier; and
based on the received vital sign measurement data request and the received unique patient identifier, send corresponding vital sign measurement data to the remote computer system.
9. The computer system of claim 8 , wherein the computer-executable instructions are further configured to cause the computer system to limit or block the sending of patient personal information from the patient protected information database to the remote computer system to a greater degree than the vital sign measurement data from the vital sign measurement database.
10. A wearable vital sign monitoring system configured to enable remote monitoring of vital sign measurements, the system comprising one or more wearable vital sign monitoring devices adapted to be worn by a patient and to measure one or more patient vital signs, the system comprising:
a sensor assembly for measuring the one or more patient vital signs;
an internal controller physically connected to at least one of the one or more vital sign monitoring devices, the internal controller including one or more processors and one or more hardware storage devices having stored thereon computer-executable instructions which are executable by the one or more processors to cause the controller to
receive vital sign measurement data from the sensor assembly,
locally store the vital sign measurement data,
determine a connectivity status to an external computer device, and
based on the determined connectivity status,
send the vital sign measurement data to the external computer device and flag the vital sign measurement data for deletion from local storage, or
maintain the vital sign measurement data in local storage and continue to periodically determine the connectivity status.
11. The system of claim 10 , wherein the one or more wearable vital sign monitoring devices includes an arm band monitoring device.
12. The system of claim 10 , wherein the one or more wearable vital sign monitoring devices includes a torso monitoring device.
13. The system of claim 10 , further comprising an indicator configured to activate when the internal controller determines a lack of connectivity.
14. The system of claim 10 , wherein the external computer device is a user-associated device communicatively coupled to the one or more vital sign monitoring devices via a Personal Area Network.
15. The system of claim 10 , the system further comprising the external computer device, the external computer device comprising:
one or more processors;
one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to
receive vital sign measurement data from the internal controller of the one or more vital sign monitoring devices;
locally store the vital sign measurement data;
determine a connectivity status to a server computer system; and
based on the determined connectivity status,
send the vital sign measurement data to the server computer system, or
generate a notification message identifying lack of connectivity.
16. The system of claim 15 , wherein the notification message is delivered for display at an interface of the external computer device.
17. The system of claim 15 or claim 16 , wherein the notification message is delivered to the internal controller of the one or more vital sign monitoring devices.
18. The system of claim 17 , wherein the controller is configured to, upon receiving the notification message, activate an indicator on the one or more vital sign monitoring devices.
19. The system of claim 18 , wherein the indicator includes a light and/or speaker.
20. The system of claim 15 , wherein the server computer system is the computer system as in claim 1 .
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/052,479 US20210244281A1 (en) | 2018-05-03 | 2019-05-03 | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862666579P | 2018-05-03 | 2018-05-03 | |
US201862666576P | 2018-05-03 | 2018-05-03 | |
US201862666567P | 2018-05-03 | 2018-05-03 | |
PCT/US2019/030670 WO2019213575A1 (en) | 2018-05-03 | 2019-05-03 | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers |
US17/052,479 US20210244281A1 (en) | 2018-05-03 | 2019-05-03 | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210244281A1 true US20210244281A1 (en) | 2021-08-12 |
Family
ID=68386682
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/052,479 Pending US20210244281A1 (en) | 2018-05-03 | 2019-05-03 | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers |
US17/052,475 Pending US20210169369A1 (en) | 2018-05-03 | 2019-05-03 | Device and methods for deriving a respiration rate from multiple biometric sources |
US17/052,477 Active US11839350B2 (en) | 2018-05-03 | 2019-05-03 | Ultrasound transducer system for wearable monitoring device |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/052,475 Pending US20210169369A1 (en) | 2018-05-03 | 2019-05-03 | Device and methods for deriving a respiration rate from multiple biometric sources |
US17/052,477 Active US11839350B2 (en) | 2018-05-03 | 2019-05-03 | Ultrasound transducer system for wearable monitoring device |
Country Status (4)
Country | Link |
---|---|
US (3) | US20210244281A1 (en) |
EP (3) | EP3787483A4 (en) |
JP (3) | JP2021522965A (en) |
WO (3) | WO2019213559A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023076467A1 (en) * | 2021-10-27 | 2023-05-04 | Monovo, LLC | Encrypting data generated from medical devices |
US11839350B2 (en) | 2018-05-03 | 2023-12-12 | Monovo, LLC | Ultrasound transducer system for wearable monitoring device |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USD890933S1 (en) * | 2018-07-12 | 2020-07-21 | Monovo Llc | Medical arm band |
CN111265196B (en) * | 2020-03-04 | 2021-03-09 | 云南大学 | Carotid pulse wave velocity estimation method and system |
WO2024119150A1 (en) * | 2022-12-02 | 2024-06-06 | Invensense, Inc. | Transversal ultrasonic sensing for cardiovascular monitoring |
CN116649959B (en) * | 2023-05-31 | 2024-07-12 | 北京欧应科技有限公司 | Monitoring system, method for judging positioning of wearing device and storage medium |
CN116965785B (en) * | 2023-08-28 | 2024-07-16 | 首都医科大学附属北京世纪坛医院 | Vital sign monitoring and analyzing method, system, terminal and storage medium |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130172691A1 (en) * | 2006-05-16 | 2013-07-04 | Bao Tran | Health monitoring appliance |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6471655B1 (en) * | 1999-06-29 | 2002-10-29 | Vitalwave Corporation | Method and apparatus for the noninvasive determination of arterial blood pressure |
US20040044288A1 (en) | 2002-09-03 | 2004-03-04 | Miguel Gorenberg | Apparatus and method for non-invasive monitoring of cardiac output |
AU2004224345B2 (en) * | 2003-03-21 | 2010-02-18 | Welch Allyn, Inc. | Personal status physiologic monitor system and architecture and related monitoring methods |
US7559894B2 (en) * | 2003-09-18 | 2009-07-14 | New Paradigm Concepts, LLC | Multiparameter whole blood monitor and method |
WO2006124623A2 (en) * | 2005-05-18 | 2006-11-23 | Rachelle Van Wyk | System, method, and kit for positioning a monitor transducer on a patient |
US8886281B2 (en) | 2006-06-08 | 2014-11-11 | Suunto Oy | Snap and electrode assembly for a heart rate monitor belt |
WO2009009761A1 (en) | 2007-07-11 | 2009-01-15 | Triage Wireless, Inc. | Device for determining respiratory rate and other vital signs |
WO2009144717A2 (en) * | 2008-05-27 | 2009-12-03 | Volusonics Medical Imaging Ltd. | Ultrasound garment |
US8740807B2 (en) * | 2009-09-14 | 2014-06-03 | Sotera Wireless, Inc. | Body-worn monitor for measuring respiration rate |
US8205370B2 (en) * | 2010-03-01 | 2012-06-26 | Disney Enterprises, Inc. | Two-piece wristband with interchangeable lasso band element for user selectable sizing |
JP6008409B2 (en) | 2011-09-23 | 2016-10-19 | オルソセンサー・インコーポレイテッドOrthosensor, Inc. | Prosthetic component for monitoring joint health |
US20150366535A1 (en) * | 2011-10-10 | 2015-12-24 | Tractus Corporation | Method, apparatus and system for complete examination of tissue with hand-held imaging devices having mounted cameras |
ITPI20110127A1 (en) * | 2011-11-08 | 2013-05-09 | W I N Wireless Integrated Network S R L | WEARABLE TONOMETER STRUCTURE |
US10405791B2 (en) | 2013-03-15 | 2019-09-10 | Yingchang Yang | Method and continuously wearable noninvasive apparatus for automatically detecting a stroke and other abnormal health conditions |
US10244949B2 (en) | 2012-10-07 | 2019-04-02 | Rhythm Diagnostic Systems, Inc. | Health monitoring systems and methods |
US20140228657A1 (en) * | 2013-02-09 | 2014-08-14 | Spire, Inc. | System and method for monitoring respiration |
US9808206B1 (en) | 2013-09-09 | 2017-11-07 | Scanadu, Inc. | Data acquisition quality and data fusion for personal portable wireless vital signs scanner |
US9848786B2 (en) | 2013-09-12 | 2017-12-26 | Mattel, Inc. | Infant monitoring system and methods |
EP3323342B1 (en) | 2013-11-15 | 2020-11-11 | Leaf Healthcare, Inc. | Prevention and treatment of bed exits, falls, and other conditions |
CA2935598C (en) | 2014-01-27 | 2021-10-26 | Rhythm Diagnostic Systems, Inc. | Ppg processing method and wearable device using the same |
FR3031665B1 (en) * | 2015-01-19 | 2017-01-13 | Univ Bretagne Occidentale | PORTABLE ECHOGRAPHIC MEASUREMENT DEVICE ADAPTED TO MEASURE OF PELVIC VERSION. |
US20160206277A1 (en) | 2015-01-21 | 2016-07-21 | Invensense Incorporated | Systems and methods for monitoring heart rate using acoustic sensing |
US10750996B2 (en) * | 2015-06-02 | 2020-08-25 | Cardiac Pacemakers, Inc. | Multi-sensor body fluid volume index |
US20160371438A1 (en) | 2015-06-19 | 2016-12-22 | ProQual-I.T., Inc. | System and method for biometric-based authentication of a user for a secure event carried out via a portable electronic device |
US11147531B2 (en) * | 2015-08-12 | 2021-10-19 | Sonetics Ultrasound, Inc. | Method and system for measuring blood pressure using ultrasound by emitting push pulse to a blood vessel |
JP2017093850A (en) | 2015-11-25 | 2017-06-01 | セイコーエプソン株式会社 | Ultrasonic probe, control device and measurement device |
WO2017096318A1 (en) | 2015-12-02 | 2017-06-08 | Echo Labs, Inc. | Systems and methods for detecting photoplethysmographic device usage |
US11020057B2 (en) | 2016-02-12 | 2021-06-01 | Qualcomm Incorporated | Ultrasound devices for estimating blood pressure and other cardiovascular properties |
US20170251967A1 (en) | 2016-03-04 | 2017-09-07 | FlourishiQ Inc. | System, apparatus and method for individualized stress management |
US10531797B2 (en) * | 2016-09-19 | 2020-01-14 | International Business Machines Corporation | Wearable blood pressure monitoring system |
MX2019003185A (en) | 2016-09-20 | 2019-08-29 | Walmart Apollo Llc | Systems and methods for tracking users of wearable devices. |
US11744553B2 (en) * | 2016-09-29 | 2023-09-05 | Koninklijke Philips N.V. | Ultrasound system, method and computer program product |
US20180092622A1 (en) * | 2016-09-30 | 2018-04-05 | Robert Bosch Gmbh | Phased Array for Detecting Artery Location to Measure Blood Velocity |
US10548487B2 (en) | 2017-04-24 | 2020-02-04 | Monovo, LLC | Wearable vital sign monitor |
EP3494894A1 (en) * | 2017-12-05 | 2019-06-12 | Koninklijke Philips N.V. | Smart compression sleeve |
US20210244281A1 (en) | 2018-05-03 | 2021-08-12 | Monovo, LLC | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers |
-
2019
- 2019-05-03 US US17/052,479 patent/US20210244281A1/en active Pending
- 2019-05-03 WO PCT/US2019/030653 patent/WO2019213559A1/en active Application Filing
- 2019-05-03 US US17/052,475 patent/US20210169369A1/en active Pending
- 2019-05-03 EP EP19797029.6A patent/EP3787483A4/en not_active Withdrawn
- 2019-05-03 JP JP2021510292A patent/JP2021522965A/en active Pending
- 2019-05-03 WO PCT/US2019/030685 patent/WO2019213587A1/en active Application Filing
- 2019-05-03 EP EP19796520.5A patent/EP3787516A4/en not_active Withdrawn
- 2019-05-03 EP EP19795870.5A patent/EP3787498A4/en not_active Withdrawn
- 2019-05-03 JP JP2021510291A patent/JP7344282B2/en active Active
- 2019-05-03 US US17/052,477 patent/US11839350B2/en active Active
- 2019-05-03 WO PCT/US2019/030670 patent/WO2019213575A1/en active Application Filing
- 2019-05-03 JP JP2021510293A patent/JP2021522966A/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130172691A1 (en) * | 2006-05-16 | 2013-07-04 | Bao Tran | Health monitoring appliance |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11839350B2 (en) | 2018-05-03 | 2023-12-12 | Monovo, LLC | Ultrasound transducer system for wearable monitoring device |
WO2023076467A1 (en) * | 2021-10-27 | 2023-05-04 | Monovo, LLC | Encrypting data generated from medical devices |
Also Published As
Publication number | Publication date |
---|---|
US20210169443A1 (en) | 2021-06-10 |
JP2021522964A (en) | 2021-09-02 |
EP3787516A1 (en) | 2021-03-10 |
WO2019213587A1 (en) | 2019-11-07 |
US11839350B2 (en) | 2023-12-12 |
JP2021522966A (en) | 2021-09-02 |
EP3787516A4 (en) | 2022-03-23 |
EP3787498A4 (en) | 2021-12-29 |
WO2019213559A1 (en) | 2019-11-07 |
EP3787498A1 (en) | 2021-03-10 |
JP2021522965A (en) | 2021-09-02 |
JP7344282B2 (en) | 2023-09-13 |
US20210169369A1 (en) | 2021-06-10 |
EP3787483A1 (en) | 2021-03-10 |
WO2019213575A1 (en) | 2019-11-07 |
EP3787483A4 (en) | 2022-06-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210244281A1 (en) | Securing patient vital sign data and configuring vital sign data for remote access by healthcare providers | |
RU2571590C2 (en) | Remote monitoring system for monitoring medical devices via wireless communication systems | |
CA2737086C (en) | Device, system and method for providing contextualized medical data | |
JP6685664B2 (en) | Patient status reporting device, patient status reporting system, and reporting method in patient status reporting device | |
ES2690569T3 (en) | Patient monitor and method to monitor a patient | |
US20160180044A1 (en) | Mobile healthcare hub | |
Mustafa et al. | Review of the internet of things for healthcare monitoring | |
KR102020284B1 (en) | Healthcare data providing server, providing method and program | |
US20180225944A1 (en) | System and Method for Monitoring Multiple Patients | |
KR20190111851A (en) | Healthcare data providing server, providing method and program | |
US20220133243A1 (en) | Terminal device, information providing system, and computer program | |
Görges et al. | Using machine-to-machine/“Internet of Things” communication to simplify medical device information exchange | |
Alsulami et al. | An enhanced conceptual model for using ambient assisted living to provide a home proactive monitoring system for elderly Saudi Arabians | |
KR20200021671A (en) | System of integrated management for patient | |
JP7009667B2 (en) | Equipment and control method of equipment | |
Carrizales-Villagómez et al. | A Platform for e‐Health Control and Location Services for Wandering Patients | |
TWI552106B (en) | Medical care platform and integrated inquire system | |
CN111489836A (en) | Remote medical treatment integrated management system | |
Jahrsdoerfer | Case study: reducing interruption fatigue through improved alarm support | |
KR20170017493A (en) | Bio checking wearable device and method for processing thereof | |
Afifi et al. | An Efficient IoT-based Mobile Application for Continuous Monitoring of Patients | |
Rani et al. | Interoperable framework solution to ICU health care monitoring | |
JP2022062042A (en) | Device and control method of device | |
Sultana et al. | Mobile Patient Surveillance | |
TW201709135A (en) | Personalized cloud health care system incorporating a storage system, a personal healthcare system (PHS) and a hospital information system (HIS) into a cloud platform |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MONOVO, LLC, UTAH Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CLOWARD, PAUL RANDAL;JOHNSTUN, ROBERT D.;HORNE, JOSHUA S.;AND OTHERS;SIGNING DATES FROM 20201027 TO 20201030;REEL/FRAME:055520/0862 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |