Methods and systems for remote vital monitoring and automated triage

Abstract

The present disclosure describes a wearable device and a system that enables real-time, automated triage and monitoring of physiological parameters from a plurality of users. The wearable device includes an array of sensors to detect parameters such as heart rate, oxygen saturation, respiration rate, body temperature, or blood pressure. The device's communication module and processor evaluate these parameters to determine the user's health and priority status, triggering the automated triage process. Visual, auditory, or vibratory alerts can be activated based on the triage results. In a broader system context, these devices can communicate with an external device, which maintains a dashboard displaying real-time data and status updates from all wearable devices. By providing a high level of automation in triaging large volumes of users' data, the system can significantly enhance healthcare efficiency and outcomes, particularly in large-scale settings like healthcare facilities or combat zones.

Description

METHODS AND SYSTEMS FOR REMOTE VITAL MONITORING AND AUTOMATED TRIAGECROSS-REFERENCE

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 662,360 filed June 20, 2024 and U.S. Provisional Application No. 63 / 778,199 filed March 26, 2025, which applications are incorporated herein by reference.BACKGROUND

[0002] The present disclosure relates to medical and health information management systems and methods. There is a risk of increased patient mortality and severe health deterioration due to incomplete and untimely access to vital patient information. This issue is compounded by high patient volumes and a shortage of resources and healthcare personnel. It underlines the urgent need for a practical solution that can be rapidly implemented. This solution should facilitate live monitoring of vital patient data and enable automated triage, assisting healthcare professionals in making timely and informed decisions, ultimately leading to better patient outcomes.SUMMARY

[0003] The present disclosure provides devices, systems, and methods for medical and health information management that addresses at least some of the above-mentioned challenges.

[0004] Described herein is a wearable device designed for monitoring the physiological parameters of a user. The device may comprise at least one sensor, inclusive of a first sensor configured to detect at least one physiological parameter. The wearable device comprises a substrate that supports the at least one sensor. The substrate comprises an adhesive layer that can adhere to a portion of the skin of a user proximate the user’s carotid artery. The device may comprise a communication module. This module may be configured to both communicate with the at least one sensor and an external device, determining a status based on the at least one physiological parameter, and transmitting the status or the at least one physiological parameter to the external device. The device can comprise a processor, configured to generate an indicator based on the determined status.

[0005] In some embodiments, the module may be configured to determine a status based at least in part on one or more vital data streams. The vital data streams may include heart rate, blood pressure, oxygen level, respirations, temperature, oxygen level, sodium concentrations, potassium concentrations, and / or chloride level. In some cases, the status is based at least in part on a derivation of a vital data stream and a deviation of the vital value from a set point for that vital. For example, the status may be determined at least in part by a patient’s heart rate, and / ora deviation of that patient’s heart rate from a set point. The set point may be tailored for that patient based on historical patient data, or set across a group of patients.

[0006] In some embodiments, the processor within the wearable device may be configured to process data from the at least one sensor. Additionally, the communication module present in the wearable device may be configured to transmit this processed data to the external device. In some embodiments, the processor within the wearable device may be configured to filter and analyze physiological data to provide user triage. The triage may be one or more of real-time or automated. In some embodiments, the indicator in the wearable device may include illumination on at least one of the following: a surface of the communication module, a surface of the substrate, or on a display in operative communication with the external device. In some embodiments, the indicator within the wearable device may include at least one of a visual alert, a vibration alert, or an audible alert based on the determined status. The one or more of the visual alert, the vibration alert, or the audible alert is provided on one or more of the communication module, the surface of the substrate, or the external device. In some embodiments, the illumination in the wearable device varies in at least one of color, intensity, or pattern. In some embodiments, the determined status within the wearable device may include at least one of a health status or a priority status. In some embodiments, the communication module within the wearable device includes a power source. In some embodiments, the substrate within the wearable device may include a power source, which is configured to power the communication module. In some embodiments, the substrate within the wearable device may include a charging coil, which is configured to receive power. In some embodiments, the substrate within the wearable device may include a charging coil, which is configured to charge a power source. In some embodiments, the substrate within the wearable device may include a module interface. In some embodiments, the at least one physiological parameter within the wearable device may include at least one of the following: heart rate, heart rate variability, oxygen saturation, body temperature, respiration rate, user motion, or blood pressure. In some embodiments, the indicator can be configured to indicate different heart rate (HR) indicators at different ranges of heart rates comprising a first HR indicator with a heart rate at a first beats per minute (BPM) range (e.g., between 60-100 BPM), a second HR indicator with a heart rate at a lower second BPM range less than the first BPM range (e.g., between 50-60 BPM) or a higher second BPM range higher than the first BPM range (e.g., between 100-150 BPM), a third HR indicator with a heart rate at a lower third BPM range lower than the lower second BPM range (e.g., between 30-50 BPM) or a higher third BPM ranger higher than the higher second BPM range (e.g., higher than 150 BPM), or a fourth HR indicator at a fourth BPM range lower than the lower third BPM range (e.g., lower than 30 BPM).

[0007] In some embodiments, the indicator can be configured to indicate different oxygen saturation (Ox) indicators at different ranges of oxygen saturations comprising a first Ox indicator with an oxygen saturation at a first range (e.g., higher than 90%), a second Ox indicator with an oxygen saturation at a second range lower than the first range (e.g., between 84%-90%), a third Ox indicator with an oxygen saturation at a third range lower than the second range (e.g., between 60%-84%), or a fourth Ox indicator lower than the third range (e.g., lower than 60%).

[0008] In some embodiments, the indicator can be configured to indicate different respiration rates at different ranges comprising a first respiration rate (RR) indicator with a first range of respiration rates (e.g., between 12-22 breaths per minute), a second RR indicator with a second lower range of respiration rates lower than the first range (e.g., between 8-12 breaths per minute) or a second higher range of respiration rates higher than the first range (e.g., between 22-27 breaths per minute), a third RR indicator with a third lower range of respiration rates lower than the second lower range (e.g., between 5-8 breaths per minute) or a third higher range of respiration rate higher than the second higher range (e.g., greater than 27 breaths per minute), or a fourth RR indicator with a respiration rate lower than the third lower range (e.g., lower than 5 breaths per minute).

[0009] In some embodiments, the indicator can be configured to indicate different temperatures for temperature ranges comprising a first indicator with a temperature between first temperature range (e.g., between 97.5°F to 99.0°F), a second indicator with a temperature at a second lower temperature range lower than the first temperature range (e.g., between 96°F to 97.5°F) or at a second higher temperature range higher than the first temperature range (e.g., between 99.0°F to 101 ,5°F), a third indicator with a temperature at a third lower temperature range lower than the second lower temperature range (e.g., between 90.0°F to 96.0°F) or at a third higher temperature range higher than the second temperature range (e.g., higher than 101.5 °F), or a fourth indicator with a temperature less than the third lower temperature range (e.g., lower than 90.0°F).

[0010] In some embodiments, the indicator can be configured to indicate different blood pressures for different blood pressure ranges comprising a first blood pressure (BP) indicator with a blood pressure at a first range of systolic (e.g., between 90 millimeters of mercury (mmHg) to 140 mmHg) and diastolic (e.g., between 60 mmHg to 85 mmHg) blood pressures, a second BP indicator with a blood pressure at a second lower range of systolic (e.g., between 80 mmHg to 90 mmHg) and diastolic (e.g., between 50 mmHg to 60 mmHg) blood pressures lower than the first range or at a second higher range of systolic (e.g., between 140 mmHg to 180 mmHg) and diastolic (e.g., between 85 mmHg to 100 mmHg) blood pressures higher than the first range, a third BP indicator at a third lower range of systolic (e.g., between 60 mmHg to 80 mmHg) and diastolic (e.g., between 0 mmHg to 50 mmHg) blood pressures lower than thesecond lower range or at a third higher range of systolic (e.g., higher than 180 mmHg) and diastolic (e.g., higher than 100 mmHg) blood pressures higher than the second higher range, or a fourth BP indicator with the systolic blood pressure lower than the third lower range (e.g., lower than 60 mmHg).

[0011] In some embodiments, the indication within the wearable device is configured to display a vital sign status for each of the physiological parameters of a user. In some embodiments, the indication within the wearable device is configured to display a priority vital sign status based on each of the physiological parameters of a user. In some embodiments, the adhesive layer within the wearable device is hypoallergenic. In some embodiments, the substrate within the wearable device is made from a biocompatible polymer material. In some embodiments, the communication module within the wearable device is configured to communicate using the long range (LoRa) protocol. In some embodiments, the at least one sensor within the wearable device may include an optical sensor that is configured to detect heart rate by measuring blood flow. In some embodiments, the at least one sensor within the wearable device may include a thermistor that is configured to measure body temperature.

[0012] In some embodiments, the at least one sensor within the wearable device may include one or more of an ultrasound device or motion sensor, both of which are configured to record respiration. In some embodiments, the at least one sensor within the wearable device may include an ultrasonic sensor that is configured to measure blood pressure. In some embodiments, the wearable device may additionally comprise a memory module integrated into the substrate for storing detected physiological data. In some embodiments, the wearable device may further comprise a user interface on the external device. This user interface could be configured to display real-time data and alerts based on the detected at least one physiological parameter. In some embodiments, the communication module within the wearable device is waterproof and hermetically sealed to the substrate. In some embodiments, the indication within the wearable device is configured to display a priority vital sign status based on a priority hierarchy, starting with an oxygenation status, followed by a heart rate status, and then a respiration status. In some embodiments, the indication within the wearable device is configured to display a priority vital sign status based on a priority order starting with systolic pressure, followed by oxygen status, heart rate status, temperature status, and finally respiration status. In some embodiments, when indicating the priority vital sign status, the wearable device gives higher priority to low systolic pressures over high systolic pressures. In some embodiments, the at least one sensor within the wearable device is configured to be in contact with a portion of the user's skin proximate the user’s carotid artery. The sensor within the wearable device may be near or at the user’s suprasternal notch. In some cases, the wearable device may detect placement in a location thatdoes not enable correct sensor readings. In some embodiments, the at least one sensor within the wearable device further comprises a second sensor. Both the first and second sensors are configured to provide sensor fusion, which can serve to increase accuracy, decrease sensor drifting, or enable electrolyte monitoring. In some cases, the sensor fusion may be achieved through algorithmic processing of two or more data streams from two or more sensors.

[0013] Described herein is a system that can monitor a plurality of sensor devices collecting physiological parameters of a plurality of users. The system may comprise a plurality of wearable devices and an external device which can communicate with the communication modules of the wearable devices. The external device may be configured to receive at least one of the status or the at least one physiological parameter from the communication module and may update a dashboard of status from the plurality of wearable devices. In some embodiments, the status within the system may include at least one of a health status or a priority status. In some embodiments, the dashboard within the system is configured to continuously update a triage status based on the status received from the array of devices. In some embodiments, triaging the status from the array of devices within the system may be configured to change the indication on the wearable device. In some embodiments, changing the indication on the wearable device within the system can include providing at least one of a visual alert, a vibration alert, or an audible alert. In some embodiments, the dashboard within the system may include a locator button that is configured to cause the wearable device to change the indication. In some embodiments, the dashboard within the system may include an automated triage of the array of devices. In some embodiments, the system may comprise a plurality of wearable devices, anywhere from 2 to 1000 devices. In some embodiments, the plurality of devices within the system may be distributed within a venue. In some embodiments, the plurality of devices within the system may be distributed within a healthcare facility. In some embodiments, the plurality of devices within the system may be distributed within a combat zone. In some embodiments, the plurality of devices within the system may be distributed across a geographic area that may include more than one healthcare facility. In some embodiments, the plurality of devices within the system may be distributed in both moving and non-moving locations.

[0014] Described herein is a method for monitoring a plurality of devices collecting physiological parameters of a plurality of users. The method may comprise collecting at least one physiological parameter from a first device associated with a first user. This collection is based on a first sensor in contact with a portion of the skin of the first user proximate the first user’s carotid artery, and also on a first location of the first user. The method may also entail collecting from at least one second device associated with another user, at least one physiological parameter based on a second sensor in contact with a portion of skin of at least asecond user proximate the second user’s carotid artery, and a second location of the at least second user. The method may further involve determining a status of the first user and the at least second user based on their respective at least one physiological parameter and respective first and second locations. Lastly, the method may include modifying an indicator based on at least one of the status and respective at least one physiological parameter. In some embodiments, the first device and the at least one second device mentioned in the method may be the wearable devices. In some embodiments, the method may further comprise assigning a provider for at least one of the first user and the at least one second user. In some embodiments, assigning a provider within the method may include designating a provider location based on the status. In some embodiments, the first location and the second location mentioned in the method may be geographically distinct. In some embodiments, the status within the method may include at least one of a health status or a priority status.

[0015] Another aspect of the present disclosure provides a system comprising one or more computer processors and computer memory coupled thereto. The computer memory comprises machine executable code that, upon execution by the one or more computer processors, implements any of the methods above or elsewhere herein.

[0016] Additional aspects and advantages of the present disclosure will become readily apparent to those skilled in this art from the following detailed description, wherein only illustrative embodiments of the present disclosure are shown and described. As will be realized, the present disclosure is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the disclosure.Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The novel features of the present disclosure are set forth with particularity in the appended claims. A better understanding of the features and advantages of the present disclosure will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of the present disclosure are utilized, and the accompanying drawings (also “Figure” and “FIG.” herein), of which:

[0018] FIG. 1 illustrates a block diagram of an example wearable device encompassing the components and communications thereof.

[0019] FIG. 2 illustrates a block diagram of substrate components for an example wearable device.

[0020] FIG. 3 illustrates a schematic view and block diagram of an example wearable device encompassing the components and communications.

[0021] FIG. 4 illustrates an exploded view of an example wearable device.

[0022] FIG. 5A and 5B illustrate perspective views of an example wearable device attached to a patient's body.

[0023] FIG. 6A-6C illustrate a perspective view of an example wearable device, demonstrating the color-changing feature of the screen that corresponds to triage levels.

[0024] FIG. 7A-7C illustrate example views of user interface displays for managing the wearable devices described herein.

[0025] FIG. 8A-8C illustrate another example view of user interface displays.

[0026] FIG. 9 illustrates an example triage method for two wearable devices.

[0027] FIG. 10 illustrates a block diagram of an example computer system.

[0028] FIG. 11 illustrates a block diagram of an example application provision system.

[0029] FIG. 12 illustrates a block diagram of another example application provision system.DETAILED DESCRIPTION

[0030] An objective of the present disclosure is to address a patient’s or a user’s mortality risk and health deterioration due to incomplete or untimely access to vital information, typically attributed to high patient volumes and limited resources. This solution can be achieved through a wearable device equipped with sensors to monitor physiological parameters, including heart rate, oxygen saturation, body temperature, respiration rate, and blood pressure. The wearable device may communicate with an external device, allowing healthcare professionals to determine a patient's status in real-time, creating alerts based on patient health status, and facilitating data- driven decision-making. Moreover, the system can accommodate multiple wearable devices, allowing simultaneous monitoring of numerous patients in high-demand settings such as healthcare facilities or combat zones, thereby enhancing patient care in resource-strapped settings.

[0031] WEARABLE DEVICE

[0032] In some embodiments, the wearable device may comprise components including one or more sensors, one or more processors, one or more communication modules and one of more external devices. The components may interact through wired or wireless communications. FIG. 1 illustrates a block diagram of the wearable device encompassing the components and communications. In some embodiments, such as in FIG. 1, the wearable device may comprise a set of sensors such as Sensor #1 104, Sensor #2 106, Sensor #3 108, up to Sensor #N 110. The sensors can detect physiological parameters from a wearer. The wearable device may alsoinclude a Processor 112, which is electronically connected to all the sensors. The Processor 112 may receive data from the sensors and processes it to generate a status based on the detected physiological parameters. Furthermore, the wearable device may include a Communication Module 114. The Communication Module 114 is connected with one or more sensors such as Sensor #1 104, Sensor #2 106, Sensor #3 108, and Sensor #N 110, as well as the Processor 112, facilitating data transfer between the components. The one or more sensors may comprise one or more photoplethysmography sensors, one or more ultrasound sensors, one or more microphones or audio sensors, one or more thermistors, and / or one or more microfluidic ion- selective sensors. The Communication Module 114 may be configured to determine the status of a wearer based on the physiological parameters detected by the sensors and processed by the Processor 112. It can also have the ability to transmit the status or the detected physiological parameters to an External Device 116. In some cases, the frequency of transmission of data from the wearable device may be based at least in part on the determined status of the user wearing the wearable device. For example, a wearable device on a user with a determined status of high priority may transmit data from the wearable device every 5 seconds. A wearable device on a user with a determined status of medium priority may transmit every 30 seconds. The External Device 116 could be a computer, smartphone, or any other suitable device capable of receiving and processing data. The Communication Module 114 and the External Device 116 can interact wirelessly. The wearable device can allow for a real-time monitoring and an automated triaging of the wearer's physiological parameters, providing rapid and accessible health status updates. In some embodiments, a total number of sensors within the wearable device, designated as N, can be between 1 sensor to 50 sensors.

[0033] In some embodiments, the sensors within the wearable device can detect physiological parameters such as a heart rate, a heart rate variability, an oxygen saturation, a body temperature, a respiration rate, a user motion, a blood pressure, a glucose levels, a hydration status, a galvanic skin response, a skin temperature, an electrical activity of a heart (ECG), an electrical activity of a brain (EEG), a sleep patterns, a muscle movement or tension, a pulse wave velocity, a circadian rhythm, stress levels, biomarker levels in sweat, lactate levels, an electrolyte balance, or an arterial stiffness. For example, biomarker levels in sweat may include concentrations of calcium, sodium, or potassium. In some cases, arterial stiffness may be measured by an ultrasound sensor of the wearable device. The ultrasound sensor may measure changes in an arterial diameter during a cardiac cycle and determine an arterial stiffness.

[0034] In some embodiments, a thermistor can be used for measuring body temperature, while a motion sensor can capture user motion and physical activity patterns. Ultrasound or ultrasonic sensors can assess blood pressure or respiration rate. The heart rate, heart rate variability, andelectrical activity of the heart (ECG) can be measured using an optical sensor or an electrocardiogram sensor. The oxygen saturation can be monitored using pulse oximetry sensors. The galvanic skin response, indicating stress levels, can be detected by sensors measuring electrical conductance of a skin. The sleep patterns and electrical activity of the brain (EEG) can be tracked using specialized EEG sensors. For monitoring muscle movement or tension, electromyography (EMG) sensors can be employed. The hydration status and sweat biomarker levels may be tracked using biosensors, while glucose and lactate levels may be detected using specialized biochemical sensors. An application of sensor fusion, where data from multiple sensors are combined, can result in increased accuracy, reduced sensor drifting, and additional monitoring capabilities such as electrolyte levels.

[0035] SUBSTRATE

[0036] In some embodiments, the wearable device comprises the Substrate 202 which adheres to a portion of the skin of a user proximate the user’s carotid artery. The substrate may comprise a Composite Adhesive 260, a StatPatch Device 220, and / or a long-range wide area network (LoRaWAN) Gateway Device 210. In some cases, the LoRaWAN Gateway Device may be a node. The StatPatch Device may comprise a node that sends or receives one or more signals to / from a Gateway Device. The StatPatch Device 220 may comprise Sensors 230, Physical Controls 240, at least one Display 250, a StatPatch Firmware 222, a StatPatch Device database (DB) 224 and / or a StatPatch Processing App 226. FIG. 2 illustrates the block diagram of the Substrate 202 that forms a part of a patient monitoring system. The Composite Adhesive 260 holds the Substrate 202 in place on a patient’s body, serving as a physical interface between the patient's body and the Substrate 202. An adhering feature can ensure a coupling with the patient's body and allows StatPatch Device 220 to securely gather health data from the patient without interruption. Within the StatPatch Device 220, several components can work in harmony. There may be Sensors 230 that are responsible for capturing physiological data from a patient. Collected data can then be communicated in a step 280 to the StatPatch Firmware 222. The StatPatch Firmware 222, a kind of specific operating system for the wearable device, may handle the collected data and pass it to the StatPatch DB 224 for storage and retrieval. The StatPatch Device 220 may include Physical Controls 240 and at least one Display 250. Both can interact in steps 282, 284, respectively, with the StatPatch Processing App 226, which may manage the collected data and control the operation of the StatPatch Device 220 based on an input from Physical Controls 240 and StatPatch DB 224. Information processed by the StatPatch Device 220 can then be relayed 270 to the LoRaWAN Gateway Device 210.

[0037] COMPONENTS AND INTERACTIONS

[0038] As depicted in FIG. 3, the LoRaWAN Gateway Device 210 can maintain a connection with a base station PC 320. FIG. 3 illustrates an overview of the wearable device including components and their interactions. In some embodiments, the wearable device comprises the Substrate 302, the LoRaWAN Gateway Device 310, a Base Station 320, an Administration Unit 340, a Wi-Fi hotspot Device 350 and / or at least one External Display 360. The Base Station 320 further comprises a LoRaWAN Network Server 322, a BaseStation Data Management (Mgmt) Module 324, a BaseStation Web Server 326, a BaseStation Admin Module 328 and / or a StatPatch BaseStation DB 330. The Base Station 320 may be a central hub for data transmission and reception. In some embodiments, the StatPatch Device 220 embedded on the Substrate 302 collects the physiological data from the patient and wirelessly transmit 370 the physiological data to the LoRaWAN Gateway Device 310. The LoRaWAN Gateway Device 310 may interact with the LoRaWAN Network Server 322. The physiological data is processed within the Base Station 320 and processed data is communicated 374 / 376 with the Wi-Fi hotspot Device 350 through BaseStation Web Server 326 and / or the BaseStation Admin Module 328. In some cases, processing the physiological data within the Base Station 320 may include encoding the data in binary format. In some cases, processing the physiological data may include decoding the binary data for display. The Wi-Fi hotspot Device 350 may transmit the processed data to the Administration Unit 340 and / or External Display 360.

[0039] FEATURES

[0040] FIG. 4 illustrates an exploded view of the substrate 202. In some embodiments, the substrate 202 may comprise a composite patch system including an interactive screen 450, a polarity of Light-Emitting Diodes (LEDs) 404, a housing 402 for the polarity of LEDs 404, the interactive screen 450 and data processing / displaying / transmitting units. In some embodiments, circuits 408 and sensors 406 are embedded in a composite adhesive 460, all designed to interact with each other as part of the larger patient monitoring system. In some embodiments, a primary visual feature is a circular face that includes the interactive screen 450. In some embodiments, the polarity of LEDs 404 is located on sides of the interactive screen 450 and distributed equally or unequally on the sides. In some embodiments, the polarity of LEDs 404 is capable of changing colors in variable wavelengths, patterns or intensities, providing visual indicators or alerts for system's operations. In some embodiments, housing 402 is a made of plastic or other materials. In some embodiments, the housing 402, the polarity of LEDs 404, and the interactive screen 450 are assembled and can be connected to or disconnected from the composite adhesive 460. In some cases, an adhesive surface of the wearable device is attached to the computer. In some cases, the adhesive surface and computer of the wearable device may be releasablycoupled via a twist lock, push-pull engagement, or other type of removably coupled fastener. In some embodiments, the embedded circuits 408 interact with sensors 406. In some embodiments, sensors 406 collect physiological parameters from users’ bodies and communicate with data processing / displaying / transmitting units embedded in the housing 402 of the substrate.

[0041] FIGs. 5 A and 5B illustrate a schematic and 3D-view representations of the substrate attached to a user’s body. In some embodiments, the substrate is attached to the user’s body in proximity to a carotid artery 518. In some embodiments, the sensors 514 are in contact with the user’s body and collect physiological parameters from a skin, tissue and / or carotid artery. In some embodiments, the embedded circuits 512 are connecting the sensors 514 to the composite patch system 520. As depicted in FIG. 5B, the composite adhesive 560 can ensure an effective coupling and secure placement of sensors 514 and composite patch system 520 on the users’ bodies.

[0042] FIG. 6A-6C illustrate 3D-views of the composite patch system, demonstrating a colorchanging feature of the screen that corresponds to triage levels. In some embodiments, the polarity of LEDs 604a-604c are distributed around the interactive screen 602a-602c. In an aspect, the interactive screen may be customized according to the user’s preference. The housing 620a-620c may contain the polarity of LEDs, interactive screen and data processing / displaying / transmitting units. In some embodiments, the polarity of LEDs is capable of changing colors in variable wavelengths, patterns or intensities according to triage levels. In some embodiments, the colors range from a light hue, such as light gray (in black and white scale) or green (in color scale), to more intense colors like dark gray (in black and white scale) or yellow or red (in color scale). Each color is carefully selected to represent a specific level of triage, providing immediate visual cues to medical personnel about an urgency of each user's condition. In some embodiments, the interactive screen provides user’s information, physiological parameters, notifications, and instructions.

[0043] User Interface

[0044] FIG. 7A-7C illustrate an example user interface 710 displayed on an external display 360 as depicted in FIG. 3. In some embodiments, the user interface contains independent windows associated with different users as depicted in FIG. 7B. In some embodiments, the user interface 710 has an overall status bar located at the top of the user interface. FIG. 7A shows a zoomed view of the status bar. From left to right, the status bar shows a total number of users 712; users with high-priority conditions including a textual indicator such as “High” meaning high priority, a numerical value showing a total number of users in a high-priority category, and a symbolic sign, such as an emoji, representing the high-priority category 714; users with moderate-priority conditions including a textual indicator such as “Moderate” meaning moderate priority, anumerical value showing a total number of users in a moderate-priority category, and a symbolic sign, such as an emoji, representing the moderate-priority category 716; users with low-priority conditions including a textual indicator such as “Low” meaning low priority, a numerical value showing a total number of users in a low-priority category, and a symbolic sign, such as an emoji, representing the low-priority category 718; users with very low- priority conditions including a textual indicator such as “Very Low” meaning low priority, a numerical value showing a total number of users in a low-priority category, and a symbolic sign, such as an emoji, representing the low-priority category 720; a symbolic or textual indicator of selected physiological parameters for display within the interface including blood pressure (BP) 724, heart rate (HR) 726, oxygen saturation (SpO2) 728, body temperature (Temp) 730, respiration rate (RR) 732 or selecting all of the listed physiological parameters for display (Any) 722. FIG. 7C shows a zoomed view of the associated window for each user 740. In some embodiments, the window includes the symbolic sign, such as an emoji, with a color-coded background representing the priority category 744; another symbolic sign, such as an emoji, representing a location of each user; an identification (ID) or number for each user 756; physiological parameters for display including BP in millimeter of mercury (mmHG) 746 representing systolic and diastolic values and an arrow representing a trend compared to previous values 758; HR in Beats Per Minute (BPM) 748 representing heart rate (HR) and an arrow representing a trend compared to previous values 760; SpO2 in percentage (%) 750 representing oxygen saturation levels and an arrow representing a trend compared to previous values 762; Temp in degree Celsius (°C) 752 representing body temperature levels and an arrow representing a trend compared to previous values 764; RR in breaths per minute (BPM) 754 representing respiration rates and an arrow representing a trend compared to previous values 766.

[0045] FIG. 8A-8C illustrate another example rendition of the user interface showcasing features including priority level 812, patch ID 814, battery status 816, highlight mode 818, user’s location 820, physiological parameters including blood pressure (BP) 826, heart rate (HR) 828, oxygen saturation (SpO2) 830, body temperature (Temp) 832, respiration rate (RR) 834 or selecting all of the listed physiological parameters for display (Any) 824 and an option 822 for going back to grid 710 as depicted in FIG. 7B, and a screen mode option 836. In some embodiments as depicted in FIG. 8B, the user interface displays an active time of the monitoring system 840, showcasing selectable time periods such as the last 3, 5, or 10 minutes 858. The selectable time period feature may enable users to view recent health data trends at a glance. Further vital details may be given, including physiological parameters 842 and 848, units 842 and 848, last recorded values 846 and 852, trend changes 846 and 854, and a graph depicting the collected data over time. The screen can be designed to be interactive, allowing the user to selectand review previous data points by moving a slide bar 850 and 856. In some embodiments as depicted in FIG. 8C, the user interface presents sorted triage, categorizing users based on an urgency and priority of medical attention required. The sorted triage may be represented in a color-coded system along with numerical values and trend indicators such as the user ID and priority level 860 and physiological parameters including BP 862, HR 864, SpO2 866, Temp 868 and RR 870.

[0046] METHOD

[0047] FIG. 9 illustrates an example flowchart outlining the method of using the wearable devices for monitoring vitals and performing triage, including steps for attaching the device, establishing communication, collecting and processing vitals, conducting triage, and displaying and storing results. In some embodiments, the flowchart represents a use of two wearable devices for two users. First step may involve attaching the wearable device to each user 902 and 922. Once the wearable devices are attached, a process to establish communication 904 and 924 between each wearable device with an external device 116 can begin. The communication may be vital for a proper functioning of the wearable devices and transmission of user data. The successful communication is verified 906 and 926. If the communication is not established successfully, wearable devices may need to be reattached or replaced. The wearable device can ensure that it is optimally positioned for an accurate data collection and transmission. If the communication is successful, the device can proceed to collect physiological parameters from users 908 and 928. The physiological parameters may then be processed within the composite patch, ready to be transferred to a server. Data collected and processed by the wearable device may form the basis for conducting users’ triage which categorizes the users’ health status based on the urgency of attention required. Once the triage has been conducted 914, results may then be displayed on designated screens and devices 916. An automated triage may allow healthcare providers to be promptly informed about the user's condition and the level of care required. In addition to being displayed, the triage results may also be stored in databases for future reference, contributing to a comprehensive health record of the user.

[0048] COMPUTER SYSTEMS

[0049] Referring to FIG. 10, a block diagram is shown depicting an exemplary machine that includes a computer system 1000 (e.g., a processing or computing system) within which a set of instructions can execute for causing a device to perform or execute any one or more of the aspects and / or methodologies for static code scheduling of the present disclosure. The components in FIG. 10 are examples only and do not limit the scope of use or functionality of any hardware, software, embedded logic component, or a combination of two or more such components implementing particular embodiments.

[0050] Computer system 1000 may include one or more processors 1001, a memory 1003, and a storage 1008 that communicate with each other, and with other components, via a bus 1040. The bus 1040 may also link a display 1032, one or more input devices 1033 (which may, for example, include a keypad, a keyboard, a mouse, a stylus, etc.), one or more output devices1034, one or more storage devices 1035, and various tangible storage media 1036. All of these elements may interface directly or via one or more interfaces or adaptors to the bus 1040. For instance, the various tangible storage media 1036 can interface with the bus 1040 via storage medium interface 1026. Computer system 1000 may have any suitable physical form, including but not limited to one or more integrated circuits (ICs), printed circuit boards (PCBs), mobile handheld devices (such as mobile telephones or PDAs), laptop or notebook computers, distributed computer systems, computing grids, or servers.

[0051] Computer system 1000 includes one or more processor(s) 1001 (e.g., central processing units (CPUs), general purpose graphics processing units (GPGPUs), or quantum processing units (QPUs)) that carry out functions. Processor(s) 1001 optionally contains a cache memory unit1002 for temporary local storage of instructions, data, or computer addresses. Processor(s) 1001 are configured to assist in execution of computer readable instructions. Computer system 1000 may provide functionality for the components depicted in Fig. 10 as a result of the processor(s) 1001 executing non-transitory, processor-executable instructions embodied in one or more tangible computer-readable storage media, such as memory 1003, storage 1008, storage devices1035, and / or storage medium 1036. The computer-readable media may store software that implements particular embodiments, and processor(s) 1001 may execute the software. Memory1003 may read the software from one or more other computer-readable media (such as mass storage device(s) 1035, 1036) or from one or more other sources through a suitable interface, such as network interface 1020. The software may cause processor(s) 1001 to carry out one or more processes or one or more steps of one or more processes described or illustrated herein.Carrying out such processes or steps may include defining data structures stored in memory 1003 and modifying the data structures as directed by the software.

[0052] The memory 1003 may include various components (e.g., machine readable media) including, but not limited to, a random access memory component (e.g., RAM 1004) (e.g., static RAM (SRAM), dynamic RAM (DRAM), ferroelectric random access memory (FRAM), phasechange random access memory (PRAM), etc.), a read-only memory component (e.g., ROM 1005), and any combinations thereof. ROM 1005 may act to communicate data and instructions unidirectionally to processor(s) 1001, and RAM 1004 may act to communicate data and instructions bidirectionally with processor(s) 1001. ROM 1005 and RAM 1004 may include any suitable tangible computer-readable media described below. In one example, a basic input / outputsystem 1006 (BIOS), including basic routines that help to transfer information between elements within computer system 1000, such as during start-up, may be stored in the memory 1003.

[0053] Fixed storage 1008 is connected bidirectionally to processor(s) 1001, optionally through storage control unit 1007. Fixed storage 1008 provides additional data storage capacity and may also include any suitable tangible computer-readable media described herein. Storage 1008 may be used to store operating system 1009, executable(s) 1010, data 1011, applications 1012 (application programs), and the like. Storage 1008 can also include an optical disk drive, a solid- state memory device (e.g., flash-based systems), or a combination of any of the above. Information in storage 1008 may, in appropriate cases, be incorporated as virtual memory in memory 1003.

[0054] In one example, storage device(s) 1035 may be removably interfaced with computer system 1000 (e.g., via an external port connector (not shown)) via a storage device interface 1025. Particularly, storage device(s) 1035 and an associated machine-readable medium may provide non-volatile and / or volatile storage of machine-readable instructions, data structures, program modules, and / or other data for the computer system 1000. In one example, software may reside, completely or partially, within a machine-readable medium on storage device(s) 1035. In another example, software may reside, completely or partially, within processor(s) 1001.

[0055] Bus 1040 connects a wide variety of subsystems. Herein, reference to a bus may encompass one or more digital signal lines serving a common function, where appropriate. Bus 1040 may be any of several types of bus structures including, but not limited to, a memory bus, a memory controller, a peripheral bus, a local bus, and any combinations thereof, using any of a variety of bus architectures. As an example and not by way of limitation, such architectures include an Industry Standard Architecture (ISA) bus, an Enhanced ISA (EISA) bus, a Micro Channel Architecture (MCA) bus, a Video Electronics Standards Association local bus (VLB), a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, an Accelerated Graphics Port (AGP) bus, HyperTransport (HTX) bus, serial advanced technology attachment (SATA) bus, and any combinations thereof.

[0056] Computer system 1000 may also include an input device 1033. In one example, a user of computer system 1000 may enter commands and / or other information into computer system 1000 via input device(s) 1033. Examples of an input device(s) 1033 include, but are not limited to, an alpha-numeric input device (e.g., a keyboard), a pointing device (e.g., a mouse or touchpad), a touchpad, a touch screen, a multi-touch screen, a joystick, a stylus, a gamepad, an audio input device (e.g., a microphone, a voice response system, etc.), an optical scanner, a video or still image capture device (e.g., a camera), and any combinations thereof. In someembodiments, the input device is a Kinect, Leap Motion, or the like. Input device(s) 1033 may be interfaced to bus 1040 via any of a variety of input interfaces 1023 (e.g., input interface 1023) including, but not limited to, serial, parallel, game port, USB, FIREWIRE, THUNDERBOLT, or any combination of the above.

[0057] In particular embodiments, when computer system 1000 is connected to network 1030, computer system 1000 may communicate with other devices, specifically mobile devices and enterprise systems, distributed computing systems, cloud storage systems, cloud computing systems, and the like, connected to network 1030. Communications to and from computer system 1000 may be sent through network interface 1020. For example, network interface 1020 may receive incoming communications (such as requests or responses from other devices) in the form of one or more packets (such as Internet Protocol (IP) packets) from network 1030, and computer system 1000 may store the incoming communications in memory 1003 for processing. Computer system 1000 may similarly store outgoing communications (such as requests or responses to other devices) in the form of one or more packets in memory 1003 and communicated to network 1030 from network interface 1020. Processor(s) 1001 may access these communication packets stored in memory 1003 for processing.

[0058] Examples of the network interface 1020 include, but are not limited to, a network interface card, a modem, and any combination thereof. Examples of a network 1030 or network segment 1030 include, but are not limited to, a distributed computing system, a cloud computing system, a wide area network (WAN) (e.g., the Internet, an enterprise network), a local area network (LAN) (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a direct connection between two computing devices, a peer-to-peer network, and any combinations thereof. A network, such as network 1030, may employ a wired and / or a wireless mode of communication. In general, any network topology may be used.

[0059] Information and data can be displayed through a display 1032. Examples of a display 1032 include, but are not limited to, a cathode ray tube (CRT), a liquid crystal display (LCD), a thin film transistor liquid crystal display (TFT-LCD), an organic liquid crystal display (OLED) such as a passive-matrix OLED (PMOLED) or active-matrix OLED (AMOLED) display, a plasma display, and any combinations thereof. The display 1032 can interface to the processor(s) 1001, memory 1003, and fixed storage 1008, as well as other devices, such as input device(s) 1033, via the bus 1040. The display 1032 is linked to the bus 1040 via a video interface 1022, and transport of data between the display 1032 and the bus 1040 can be controlled via the graphics control 1021. In some embodiments, the display is a video projector. In some embodiments, the display is a head-mounted display (HMD) such as a VR headset. In furtherembodiments, suitable VR headsets include, by way of non-limiting examples, HTC Vive, Oculus Rift, Samsung Gear VR, Microsoft HoloLens, Razer OSVR, FOVE VR, Zeiss VR One, Avegant Glyph, Freefly VR headset, and the like. In still further embodiments, the display is a combination of devices such as those disclosed herein.

[0060] In addition to a display 1032, computer system 1000 may include one or more other peripheral output devices 1034 including, but not limited to, an audio speaker, a printer, a storage device, and any combinations thereof. Such peripheral output devices may be connected to the bus 1040 via an output interface 1024. Examples of an output interface 1024 include, but are not limited to, a serial port, a parallel connection, a USB port, a FIREWIRE port, a THUNDERBOLT port, and any combinations thereof.

[0061] In addition or as an alternative, computer system 1000 may provide functionality as a result of logic hardwired or otherwise embodied in a circuit, which may operate in place of or together with software to execute one or more processes or one or more steps of one or more processes described or illustrated herein. Reference to software in this disclosure may encompass logic, and reference to logic may encompass software. Moreover, reference to a computer-readable medium may encompass a circuit (such as an IC) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware, software, or both.

[0062] Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality.

[0063] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0064] The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by one or more processor(s), or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0065] In accordance with the description herein, suitable computing devices include, by way of non-limiting examples, server computers, desktop computers, laptop computers, notebook computers, sub-notebook computers, netbook computers, netpad computers, set-top computers, media streaming devices, handheld computers, Internet appliances, mobile smartphones, tablet computers, personal digital assistants, video game consoles, and vehicles. Those of skill in the art will also recognize that select televisions, video players, and digital music players with optional computer network connectivity are suitable for use in the system described herein. Suitable tablet computers, in various embodiments, include those with booklet, slate, and convertible configurations, known to those of skill in the art.

[0066] In some embodiments, the computing device includes an operating system configured to perform executable instructions. The operating system is, for example, software, including programs and data, which manages the device’s hardware and provides services for execution of applications. Those of skill in the art will recognize that suitable server operating systems include, by way of non-limiting examples, FreeBSD, OpenBSD, NetBSD®, Linux, Apple® Mac OS X Server®, Oracle® Solaris®, Windows Server®, and Novell® NetWare®. Those of skill in the art will recognize that suitable personal computer operating systems include, by way of nonlimiting examples, Microsoft® Windows®, Apple® Mac OS X®, UNIX®, and UNIX-like operating systems such as GNU / Linux®. In some embodiments, the operating system is provided by cloud computing. Those of skill in the art will also recognize that suitable mobile smartphone operating systems include, by way of non-limiting examples, Nokia® Symbian® OS, Apple® iOS®, Research In Motion® BlackBerry OS®, Google® Android®, Microsoft® Windows Phone® OS, Microsoft® Windows Mobile® OS, Linux®, and Palm® WebOS®. Those of skill in the art will also recognize that suitable media streaming device operating systems include, by way of non-limiting examples, Apple TV®, Roku®, Boxee®, Google TV®, Google Chromecast®, Amazon Fire®, and Samsung® HomeSync®. Those of skill in the artwill also recognize that suitable video game console operating systems include, by way of nonlimiting examples, Sony® PS3®, Sony® PS4®, Sony® PS5®, Microsoft® Xbox 360®, Microsoft® Xbox One, Microsoft® Xbox Series X, Microsoft® Xbox Series S, Nintendo® Wii®, Nintendo® Wii U®, Nintendo® SwitchTM, and Ouya®.

[0067] Another aspect of the disclosure herein describes a non-transitory, computer-readable medium comprising executable instructions, wherein when a processor, when executing the executable instructions, performs a method as described herein.

[0068] Web application

[0069] In some embodiments, a computer program includes a web application. In light of the disclosure provided herein, those of skill in the art will recognize that a web application, in various embodiments, utilizes one or more software frameworks and one or more database systems. In some embodiments, a web application is created upon a software framework such as Microsoft® .NET or Ruby on Rails (RoR). In some embodiments, a web application utilizes one or more database systems including, by way of non-limiting examples, relational, non-relational, object oriented, associative, XML, and document oriented database systems. In further embodiments, suitable relational database systems include, by way of non-limiting examples, Microsoft® SQL Server, mySQL™, and Oracle®. Those of skill in the art will also recognize that a web application, in various embodiments, is written in one or more versions of one or more languages. A web application may be written in one or more markup languages, presentation definition languages, client-side scripting languages, server-side coding languages, database query languages, or combinations thereof. In some embodiments, a web application is written to some extent in a markup language such as Hypertext Markup Language (HTML), Extensible Hypertext Markup Language (XHTML), or extensible Markup Language (XML). In some embodiments, a web application is written to some extent in a presentation definition language such as Cascading Style Sheets (CSS). In some embodiments, a web application is written to some extent in a client-side scripting language such as Asynchronous JavaScript and XML (AJAX), Flash® ActionScript, JavaScript, or Silverlight®. In some embodiments, a web application is written to some extent in a server-side coding language such as Active Server Pages (ASP), ColdFusion®, Perl, Java™, JavaServer Pages (JSP), Hypertext Preprocessor (PHP), Python™, Ruby, Tel, Smalltalk, WebDNA®, or Groovy. In some embodiments, a web application is written to some extent in a database query language such as Structured Query Language (SQL). In some embodiments, a web application integrates enterprise server products such as IBM® Lotus Domino®. In some embodiments, a web application includes a media player element. In various further embodiments, a media player element utilizes one or more ofmany suitable multimedia technologies including, by way of non-limiting examples, Adobe® Flash®, HTML 5, Apple® QuickTime®, Microsoft® Silverlight®, Java™, and Unity®.

[0070] Referring to FIG. 11, in a particular embodiment, an application provision system comprises one or more databases 1100 accessed by a relational database management system (RDBMS) 1110. Suitable RDBMSs include Firebird, MySQL, PostgreSQL, SQLite, Oracle Database, Microsoft SQL Server, IBM DB2, IBM Informix, SAP Sybase, Teradata, and the like. In this embodiment, the application provision system further comprises one or more application severs 1120 (such as Java servers, .NET servers, PHP servers, and the like) and one or more web servers 1130 (such as Apache, IIS, GWS and the like). The web server(s) optionally expose one or more web services via app application programming interfaces (APIs) 1140. Via a network, such as the Internet, the system provides browser-based and / or mobile native user interfaces.

[0071] Referring to FIG. 12, in a particular embodiment, an application provision system alternatively has a distributed, cloud-based architecture 1200 and comprises elastically load balanced, auto-scaling web server resources 1210 and application server resources 1220 as well synchronously replicated databases 1230.

[0072] Mobile application

[0073] In some embodiments, a computer program includes a mobile application provided to a mobile computing device. In some embodiments, the mobile application is provided to a mobile computing device at the time it is manufactured. In other embodiments, the mobile application is provided to a mobile computing device via the computer network described herein.

[0074] In view of the disclosure provided herein, a mobile application is created by techniques known to those of skill in the art using hardware, languages, and development environments known to the art. Those of skill in the art will recognize that mobile applications are written in several languages. Suitable programming languages include, by way of non-limiting examples, C, C++, C#, Objective-C, Java™, JavaScript, Pascal, Object Pascal, Python™, Ruby, Rails, VB.NET, WML, and XHTML / HTML with or without CSS, or combinations thereof.

[0075] Suitable mobile application development environments are available from several sources. Commercially available development environments include, by way of non-limiting examples, AirplaySDK, alcheMo, Appcelerator®, Celsius, Bedrock, Flash Lite, .NET Compact Framework, Rhomobile, and WorkLight Mobile Platform. Other development environments are available without cost including, by way of non-limiting examples, Lazarus, MobiFlex, MoSync, and Phonegap. Also, mobile device manufacturers distribute software developer kits including, by way of non-limiting examples, iPhone and iPad (iOS) SDK, Android™ SDK, BlackBerry® SDK, BREW SDK, Palm® OS SDK, Symbian SDK, webOS SDK, and Windows® Mobile SDK.

[0076] Those of skill in the art will recognize that several commercial forums are available for distribution of mobile applications including, by way of non-limiting examples, Apple® App Store, Google® Play, Chrome WebStore, BlackBerry® App World, App Store for Palm devices, App Catalog for webOS, Windows® Marketplace for Mobile, Ovi Store for Nokia® devices, Samsung® Apps, and Nintendo® DSi Shop.

[0077] Standalone application

[0078] In some embodiments, a computer program includes a standalone application, which is a program that is run as an independent computer process, not an add-on to an existing process, e.g., not a plug-in. Those of skill in the art will recognize that standalone applications are often compiled. A compiler is a computer program(s) that transforms source code written in a programming language into binary object code such as assembly language or machine code. Suitable compiled programming languages include, by way of non-limiting examples, C, C++, Objective-C, COBOL, Delphi, Eiffel, Java™, Lisp, Python™, Visual Basic, and C# .NET, or combinations thereof. Compilation is often performed, at least in part, to create an executable program. In some embodiments, a computer program includes one or more executable complied applications.

[0079] Web browser plug-in

[0080] In some embodiments, the computer program includes a web browser plug-in (e.g., extension, etc.). In computing, a plug-in is one or more software components that add specific functionality to a larger software application. Makers of software applications support plug-ins to enable third-party developers to create abilities which extend an application, to support easily adding new features, and to reduce the size of an application. When supported, plug-ins enable customizing the functionality of a software application. For example, plug-ins are commonly used in web browsers to play video, generate interactivity, scan for viruses, and display particular file types. Those of skill in the art will be familiar with several web browser plug-ins including, Adobe® Flash® Player, Microsoft® Silverlight®, and Apple® QuickTime®. In some embodiments, the toolbar comprises one or more web browser extensions, add-ins, or add-ons. In some embodiments, the toolbar comprises one or more explorer bars, tool bands, or desk bands.

[0081] In view of the disclosure provided herein, those of skill in the art will recognize that several plug-in frameworks are available that enable development of plug-ins in various programming languages, including, by way of non-limiting examples, C++, Delphi, Java™, PHP, Python™, and C# .NET, or combinations thereof.

[0082] Web browsers (also called Internet browsers) are software applications, designed for use with network-connected computing devices, for retrieving, presenting, and traversinginformation resources on the World Wide Web. Suitable web browsers include, by way of nonlimiting examples, Microsoft® Internet Explorer®, Mozilla® Firefox®, Google® Chrome, Apple® Safari®, Opera Software® Opera®, and KDE Konqueror. In some embodiments, the web browser is a mobile web browser. Mobile web browsers (also called microbrowsers, minibrowsers, and wireless browsers) are designed for use on mobile computing devices including, by way of non-limiting examples, handheld computers, tablet computers, netbook computers, subnotebook computers, smartphones, music players, personal digital assistants (PDAs), and handheld video game systems. Suitable mobile web browsers include, by way of non-limiting examples, Google® Android® browser, RIM BlackBerry® Browser, Apple® Safari®, Palm® Blazer, Palm® WebOS® Browser, Mozilla® Firefox® for mobile, Microsoft® Internet Explorer® Mobile, Amazon® Kindle® Basic Web, Nokia® Browser, Opera Software® Opera® Mobile, and Sony® PSP™ browser.

[0083] Software modules

[0084] In some embodiments, the platforms, systems, media, and methods disclosed herein include software, server, and / or database modules, or use of the same. In view of the disclosure provided herein, software modules are created by techniques known to those of skill in the art using machines, software, and languages known to the art. The software modules disclosed herein are implemented in a multitude of ways. In various embodiments, a software module comprises a file, a section of code, a programming object, a programming structure, a distributed computing resource, a cloud computing resource, or combinations thereof. In further various embodiments, a software module comprises a plurality of files, a plurality of sections of code, a plurality of programming objects, a plurality of programming structures, a plurality of distributed computing resources, a plurality of cloud computing resources, or combinations thereof. In various embodiments, the one or more software modules comprise, by way of nonlimiting examples, a web application, a mobile application, a standalone application, and a distributed or cloud computing application. In some embodiments, software modules are in one computer program or application. In other embodiments, software modules are in more than one computer program or application. In some embodiments, software modules are hosted on one machine. In other embodiments, software modules are hosted on more than one machine. In further embodiments, software modules are hosted on a distributed computing platform such as a cloud computing platform. In some embodiments, software modules are hosted on one or more machines in one location. In other embodiments, software modules are hosted on one or more machines in more than one location.

[0085] Databases

[0086] In some embodiments, the platforms, systems, media, and methods disclosed herein include one or more databases, or use of the same. In view of the disclosure provided herein, those of skill in the art will recognize that many databases are suitable for storage and retrieval of data, or any combination thereof. In various embodiments, suitable databases include, by way of non-limiting examples, relational databases, non-relational databases, object oriented databases, object databases, entity -relationship model databases, associative databases, XML databases, document oriented databases, and graph databases. Further non-limiting examples include SQL, PostgreSQL, MySQL, Oracle, DB2, Sybase, and MongoDB. In some embodiments, a database is Internet-based. In further embodiments, a database is web-based. In still further embodiments, a database is cloud computing-based. In a particular embodiment, a database is a distributed database. In other embodiments, a database is based on one or more local computer storage devices.

[0087] Data transmission

[0088] The subject matter described herein, including methods and systems as described herein and may be configured to be performed in one or more facilities at one or more locations. Facility locations are not limited by country and include any country or territory. In some instances, one or more steps are performed in a different country than another step of the method. In some embodiments, one or more method steps involving a computer system are performed in a different country than another step of the methods provided herein. In some embodiments, data processing and storage are performed in a different country or location than one or more steps of the methods described herein. In some embodiments, one or more products or data are transferred from one or more of the facilities to one or more different facilities for analysis or further analysis. Data includes, but is not limited to, information regarding the stratification of a subject, and any data produced by the methods disclosed herein. In some embodiments of the methods and systems described herein, the subject information is compiled, and a subsequent data transmission step will transmit or store the subject information.

[0089] In some embodiments, any step of any method described herein is performed by a software program or module on a computer. In additional or further embodiments, data from any step of any method described herein is transferred to and from facilities located within the same or different countries, including analysis performed in one facility in a particular location and the data shipped to another location or directly to an individual in the same or a different country. In additional or further embodiments, data from any step of any method described herein is transferred to and / or received from a facility located within the same or different countries, including analysis of a data input, such as queries, objects, properties, types, filters, tables, orany combination thereof, performed in one facility in a particular location and corresponding data transmitted to another location.

[0090] The methods described herein may utilize one or more computers. The computer may be used for managing customer and subject information. The computer may include a monitor or other user interface for displaying data, results, billing information, marketing information (e.g. demographics), customer information, or sample information. The computer may also include means for data or information input. The computer may include a processing unit and fixed or removable media or a combination thereof. The computer may be accessed by a user in physical proximity to the computer, for example via a keyboard and / or mouse, or by a user that does not necessarily have access to the physical computer through a communication medium such as a modem, an internet connection, a telephone connection, or a wired or wireless communication signal carrier wave. In some cases, the computer may be connected to a server or other communication device for relaying information from a user to the computer or from the computer to a user. In some cases, the user may store data or information obtained from the computer through a communication medium on media, such as removable media. It is envisioned that data relating to the methods can be transmitted over such networks or connections for reception and / or review by a party.

[0091] The entity entering or reviewing information into a database for the purpose of one or more of the following: inventory tracking, order tracking, customer management, customer service, billing, and sales. Sample information may include, but is not limited to: customer name, unique customer identification, or any information suitable for storage in a database.

[0092] The database may be accessible by a user. Database access may take the form of electronic communication such as a computer or telephone. The database may be accessed through an intermediary such as a customer service representative, business representative, or consultant. The availability or degree of database access may change upon payment of a fee for products and services rendered or to be rendered.

[0093] While preferred embodiments of the present disclosure have been shown and described herein, it will be obvious to those skilled in the art that such embodiments are provided by way of example only. It is not intended that the present disclosure be limited by the specific examples provided within the specification. While the present disclosure has been described with reference to the aforementioned specification, the descriptions and illustrations of the embodiments herein are not meant to be construed in a limiting sense. Numerous variations, changes, and substitutions will now occur to those skilled in the art without departing from the scope of the present disclosure. Furthermore, it shall be understood that all aspects of the present disclosure are not limited to the specific depictions, configurations or relativeproportions set forth herein which depend upon a variety of conditions and variables. It should be understood that various alternatives to the embodiments of the present disclosure described herein may be employed in practicing the embodiments of the present disclosure. It is therefore contemplated that the present disclosure shall also cover any such alternatives, modifications, variations, or equivalents. It is intended that the following claims define the scope of the invention and that methods and structures within the scope of these claims and their equivalents be covered thereby.

[0094] Whenever the term “at least,” “greater than,” or “greater than or equal to” precedes the first numerical value in a series of two or more numerical values, the term “at least,” “greater than” or “greater than or equal to” applies to each of the numerical values in that series of numerical values. For example, greater than or equal to 1, 2, or 3 is equivalent to greater than or equal to 1, greater than or equal to 2, or greater than or equal to 3.

[0095] Whenever the term “no more than,” “less than,” or “less than or equal to” precedes the first numerical value in a series of two or more numerical values, the term “no more than,” “less than,” or “less than or equal to” applies to each of the numerical values in that series of numerical values. For example, less than or equal to 3, 2, or 1 is equivalent to less than or equal to 3, less than or equal to 2, or less than or equal to 1.

[0096] Certain inventive embodiments herein contemplate numerical ranges. When ranges are present, the ranges include the range endpoints. Additionally, every sub range and value within the range is present as if explicitly written out. The term “about” or “approximately” may mean within an acceptable error range for the particular value, which will depend in part on how the value is measured or determined, e.g., the limitations of the measurement system. For example, “about” may mean within 1 or more than 1 standard deviation, per the practice in the art. Alternatively, “about” may mean a range of up to 20%, up to 10%, up to 5%, or up to 1% of a given value. Where particular values are described in the application and claims, unless otherwise stated the term “about” meaning within an acceptable error range for the particular value may be assumed.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A wearable device for monitoring physiological parameters of a user, the device comprising: at least one sensor including a first sensor configured to detect at least one physiological parameter of the user; a substrate supporting the at least one sensor and comprising an adhesive layer configured to adhere to a portion of skin of the user proximate the user’s carotid artery; a communication module in communication with the at least one sensor and an external device, the communication module configured to determine a status based on the at least one physiological parameter of the user and to transmit at least one of the status or the at least one physiological parameter to the external device; and a processor configured to generate an indicator for the user based on the determined status.

2. The device of claim 1, wherein the processor is configured to process data from the at least one sensor, and wherein the communication module is configured to transmit the processed data to the external device.

3. The device of claim 2, wherein at least one of the external device or the processor is configured to filter and analyze the physiological data to provide user triage, the triage being one or more of real-time or automated.

4. The device of any one of claims 1-3, wherein the indicator includes illumination on at least one of a surface of the communication module, on a surface of the substrate, or on a display in operative communication with the external device.

5. The device of any one of claims 1-4, wherein the indicator includes at least one of a visual alert, a vibration alert, or an audible alert based on the determined status, and wherein the one or more of the visual alert, the vibration alert, or the audible alert is provided on one or more of the communication module, the surface of the substrate, or the external device.

6. The device of claim 4 or 5, wherein the illumination varies in at least one of color, intensity, or pattern.

7. The device of any one of claims 1-6, wherein the determined status includes at least one of a health status or a priority status.

8. The device of any one of claims 1-7, wherein the communication module includes a power source.

9. The device of any one of claims 1-8, wherein the substrate includes a power source configured to power the communication module.

10. The device of any one of claims 1-9, wherein the substrate includes charging coil configured to receive power.

11. The device of any one of claims 1-10, wherein the substrate includes charging coil configured to charge a power source.

12. The device of any one of claims 1-11, wherein the substrate includes a module interface.

13. The device of any one of claims 1-12, wherein at least one physiological parameter includes at least one of heart rate, heart rate variability, oxygen saturation, body temperature, respiration rate, user motion, or blood pressure.

14. The device of any one of claims 1-13, wherein the indicator is configured to indicate different heart rate (HR) indicators at different ranges of heart rates.

15. The device of claim 14, wherein the different HR indicators comprise a first heart rate (HR) indicator with a heart rate at a first BPM range, a second HR indicator with a heart rate at a lower second BPM range less than the first BPM range or a higher second BPM range higher than the first BPM range, a third HR indicator with a heart rate at a lower third BPM range lower than the lower second BPM range or a higher third BPM ranger higher than the higher second BPM range, or a fourth HR indicator at a fourth BPM range lower than the lower third BPM range.

16. The device of any one of claims 1-15, wherein the indicator is configured to indicate different oxygen saturation (Ox) indicators at different ranges of oxygen saturations.

17. The device of claim 16, wherein the different ranges of oxygen saturations comprise a first Ox indicator with an oxygen saturation at a first range, a second Ox indicator with an oxygen saturation at a second range lower than the first range, a third Ox indicator with an oxygen saturation at a third range lower than the second range, or a fourth Ox indicator lower than the third range.

18. The device of any one of claims 1-17, wherein the indicator is configured to indicate different respiration rates at different ranges thereof.

19. The device of claim 18, wherein the different ranges of respiration rate comprise a first respiration rate (RR) indicator with a first range of respiration rates, a second RR indicator with a second lower range of respiration rates lower than the first range or a second higher range of respiration rates higher than the first range, a third RR indicator with a third lower range of respiration rates lower than the second lower range or a third higher range of respiration rate higher than the second higher range, or a fourth RR indicator with a respiration rate lower than the third lower range.

20. The device of any one of claims 1-19, wherein the indicator is configured to indicate different temperatures for temperature ranges.

21. The device of claim 20, wherein the temperature indicators comprise a first indicator with a temperature between first temperature range, a second indicator with a temperature at a second lower temperature range lower than the first temperature range or at a second higher temperature range higher than the first temperature range, a third indicator with a temperature at a third lower temperature range lower than the second lower temperature range or at a third higher temperature range higher than the second temperature range, or a fourth indicator with a temperature less than the third lower temperature range.

22. The device of any one of claims 1-21, wherein the indicator is configured to indicate different blood pressures for different blood pressure ranges.

23. The device of claim 22, wherein the indicator comprises a first blood pressure (BP) indicator with a blood pressure at a first range of systolic and diastolic blood pressures, a second BP indicator with a blood pressure at a second lower range of systolic and diastolic blood pressures lower than the first range or at a second higher range of systolic and diastolic blood pressures higher than the first range, a third BP indicator at a third lower range of systolic and diastolic blood pressures lower than the second lower range or at a third higher range of systolic and diastolic blood pressures higher than the second higher range, or a fourth BP indicator with a blood pressure lower than the third lower range.

24. The device of any one of claims 1-23, wherein the indicator is configured to indicate a vital sign status for each of the physiological parameters of a user.

25. The device of any one of claims 1-24, wherein the indicator is configured to indicate a priority vital sign status based on each of the physiological parameters of a user.

26. The device of any one of claims 1-25, wherein the adhesive layer is hypoallergenic.

27. The device of any one of claims 1-26, wherein the substrate is made from a biocompatible polymer material.

28. The device of any one of claims 1-27, wherein the communication module is configured to communicate using LoRa protocol.

29. The device of any one of claims 1-28, wherein the at least one sensor includes an optical sensor configured to detect heart rate by measuring blood flow.

30. The device of any one of claims 1-29, wherein the at least one sensor includes a thermistor configured to measure body temperature.

31. The device of any one of claims 1-30, wherein the at least one sensor includes one or more of an ultrasound device or motion sensor configured to record respiration.

32. The device of any one of claims 1-31, wherein the at least one sensor includes an ultrasonic sensor configured to measure blood pressure.

33. The device of any one of claims 1-32, further comprising a memory module integrated into the substrate for storing detected physiological data.

34. The device of any one of claims 1-33, further comprising a user interface on the external device, wherein the user interface is configured to display real-time data and alerts based on the detected at least one physiological parameter.

35. The device of any one of claims 1-34, wherein the communication module is waterproof and hermetically sealed to the substrate.

36. The device of any one of claims 1-35, wherein the indication is configured to indicate a priority vital sign status based on a priority of an oxygenation status, followed by a heart rate status, followed by a respiration status.

37. The device of any one of claims 1-36, wherein the indication is configured to indicate a priority vital sign status based on a priority of a systolic pressure, followed by an oxygen status, followed by a heart rate status, followed by a temperature status, followed by a respiration status.

38. The device of claim 37, wherein a low systolic pressure has a higher priority than a high systolic pressure.

39. The device of any one of claims 1-38, wherein the at least one sensor is configured to be in contact with a portion of skin of the user proximate the user’s carotid artery.

40. The device of any one of claims 1-39, wherein the at least one sensor further comprises a second sensor, and wherein the first and second sensors are configured to provide sensor fusion to at least one of increase accuracy, decrease in sensor drifting, or enabling electrolyte monitoring.

41. A system for monitoring a plurality of sensor devices collecting physiological parameters of a plurality of users, the system comprising: a plurality of wearable devices according to any one of claims 1-40; and an external device in communication with the communication modules of the wearable devices, the external device configured to receive at least one of the status or the at least one physiological parameter from the communication module and update a dashboard of status from the plurality of wearable devices.

42. The system of claim 41, wherein the status includes at least one of a health status and a priority status.

43. The system of claims 41-42, wherein the dashboard continuously updates a triage status based on the status from the array of devices.

44. The system of any one of claims 41-43, wherein triaging the status from the array of devices is configured to change the indication on the wearable device.

45. The system of any one of claims 41-44, wherein changing the indication on the wearable device includes providing at least one of a visual alert, a vibration alert, or an audible alert.

46. The system of any one of claims 41-45, wherein the dashboard includes a locator button configured to cause the wearable device to change the indication.

47. The system of any one of claims 41-46, wherein the dashboard includes an automated triage of the array of devices.

48. The system of any one of claims 41-47, wherein the plurality of wearable devices comprises between 2-1000 devices.

49. The system of any one of claims 41-48, wherein the plurality of devices are distributed within a venue.

50. The system of any one of claims 41-49, wherein the plurality of devices are distributed within a healthcare facility.

51. The system of any one of claims 41-50, wherein the plurality of devices are distributed within a combat zone.

52. The system of any one of claims 41-51, wherein the plurality of devices are distributed across a geographic area including more than one healthcare facility.

53. The system of any one of claims 41-52, wherein the plurality of devices are distributed in moving and non-moving locations.

54. A method for monitoring a plurality of devices collecting physiological parameters of a plurality of users, the method comprising: collecting, from a first device associated with a first user, at least one physiological parameter based on a first sensor in contact with a portion of skin of the first user proximate the first user’s carotid artery, and a first location of a first user and, from at least one second device associated with another user, at least one physiological parameter based on a second sensor in contact with a portion of skin of at least a second user proximate the second user’s carotid artery, and a second location of the at least second user; determining a status of the first user and the at least second user based on their respective at least one physiological parameter and respective first location and second location; and modifying an indicator based on at least one of the status and respective at least one physiological parameter.

55. The method of claim 54, wherein the first device and the at least one second device is the wearable device of any of claims 1-41.

56. The method of claim 54 or 55, further comprising assigning a provider for at least one of the first user and the at least one second user.

57. The method of any one of claims 54-56, wherein assigning a provider includes assigning a provider location based on the status.

58. The method of any one of claims 54-57, wherein the first location and the second location are geographically distinct.

59. The method of any one of claims 54-58, wherein the status includes at least one of a health status and a priority status.

Images