Patent Grant
11864917
This invention relates generally to the intoxication monitoring device field, and more specifically to a new and useful method and system for transdermal alcohol monitoring.
Alcohol use remains the third leading cause of death both in the USA (85,000 deaths annually) and worldwide (up to 2.5 million deaths annually). The economic costs associated with excessive drinking exceed $223 billion annually in the USA alone. Some of the objective methods for measuring alcohol, such as breathalyzers and biological assays, can have significant drawbacks, such as invasiveness, constant user interaction, and/or the inability to provide real-time (or near real-time) quantitative measurements of alcohol usage (e.g., as opposed to metabolites). Transdermal alcohol detection, which measures alcohol permeating through the skin and correlates that measurement to the blood alcohol concentration, can offer the capacity to provide a noninvasive, continuous, and quantitative measurement of bodily alcohol. Thus, there is a need in the intoxication monitoring field to create an improved transdermal alcohol monitoring system and method.
This invention creates such a new and useful transdermal alcohol monitoring system and method.
The following description of the preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
As shown in
The system 200 functions to enable continuous or near-continuous monitoring of a user's intoxication level, which can in turn function to provide any number of suitable triggers, notifications, or other actions based on the intoxication level. For a high-risk user (e.g., user on probation, user with a history of a DUI, user deemed to be at risk to himself or other, user diagnosed as an alcoholic, etc.) this can enable the user to live outside of a facility (e.g., correctional facility, rehabilitation facility, etc.) while still being closely monitored, determine at an early time point when the user may be in danger or in violation of a sobriety plan, or otherwise intoxicated. For moderate or low-risk users (e.g., conscientious users, etc.), the system can function to optimize a night out (e.g., plan a timing of drinking events) for a user, present a user with easy-to-interpret intoxication assessments (e.g., graphical displays or other visual indicators), help educate a user in his or her drinking and the effects of it specifically on his or her body, help a user achieve safe and/or moderate drinking, help a user achieve sobriety, or provide any other output and/or achieve any other outcome.
As shown in
The method 100 functions to provide intoxication monitoring to a user in substantially real time during a drinking session. A drinking session is preferably a period of time (e.g., a time window) during which a user is consuming alcoholic beverages and/or blood alcohol levels continue to be elevated (e.g., at a level above 0.00 BAC after consuming one or more alcoholic beverages, at a level above a threshold level such as 0.01, 0.02, 0.08, etc.), but can additionally or alternatively include any other suitable period of time. The method 100 can also function to provide alcohol monitoring capability to a remote entity associated with the user (e.g., a parole officer, a parent, a friend, an accountability acquaintance, etc.).
The method can include aggregating data (e.g., intoxication metric time series) at a database. Aggregated data can be used as a training dataset for building models of user intoxication state and/or related parameters in relation to a wide range of factors. Building models of breathalyzer sensor state based on training data can be performed using any suitable machine learning algorithm(s) (e.g., as described below). As such, models of user intoxication state can be used to inform analyses associated with subsequent sensor readings.
In a first example, as shown in
In a second example, the method 100 can include determining correlations between drinking events (e.g., sipping detected based on accelerometer data) and blood alcohol content and/or user performance on intoxication tests (e.g., puzzles, speech clarity, pupil dilation), presenting the correlations to the user, and/or preventing user actions (e.g., placing phone calls or sending text messages to predetermined contacts).
In a third example, the method 100 can include detecting user intoxication (e.g., through a worn alcohol sensor and/or an alcohol sensor integrated into a piece of equipment, such as a steering wheel of a vehicle or a sensor associated with an employee time logging system) and, in response to detecting intoxication, providing a warning (e.g., to the user, to a supervisor of the user, etc.) and/or preventing use of the equipment.
In a fourth example, the method 100 can include presenting a visual indication of a user's ongoing sobriety (e.g., units of time such as days, weeks, or years since the user's last drinking event; awards associated with sobriety; etc.).
In a fifth example, the method 100 can include presenting a visual indication of a user's current intoxication to another person (e.g., bartender) and/or preventing alcohol purchases by intoxicated users.
In a sixth example, the method 100 can include determining a user's current, past, and/or projected intoxication and/or presenting an indication (e.g., visual indication, such as a numerical value, directed arrow, trendline, etc.) of the intoxication (e.g., to the user, at a wearable electronic device, etc.).
The method 100 can be implemented, at least in part, using embodiments, variations, and/or examples of the system 200 described below, wherein the system is configured to be used outside of a “law enforcement setting”, and instead, used by users in their normal daily lives.
In variations, the system 200 can be configured to perform at least a portion of the method 100 described below, and can additionally or alternatively be configured to perform any suitable method for collecting and/or analyzing biological samples indicative of blood alcohol content.
The system 200 can additionally or alternatively include one or more embodiments, variations, and examples of system elements (e.g., transdermal alcohol sensing device components, mobile computing device components, computing system components, etc.) described in U.S. application Ser. No. 14/169,029 entitled “Method and System for Monitoring Intoxication” and filed on 30 Jan. 2014, U.S. application Ser. No. 14/602,909 entitled “Method and System for Remotely Monitoring Intoxication” and filed on 22 Jan. 2015, U.S. application Ser. No. 14/631,125 entitled “Method and System for Monitoring Intoxication” and filed on 25 Feb. 2015, and U.S. application Ser. No. 15/375,801 entitled “Wearable System and Method for Monitoring Intoxication” and filed on 12 Dec. 2016, each of which is incorporated herein in its entirety by this reference. Variations of the system 100 can, however, be implemented at least in part using any other suitable system elements.
Additionally or alternatively, variations of the system 200 can be configured such that the user can select between information that is optimized for speed and information that is optimized for accuracy. For instance, information optimized for speed can be cause upon analyses of a peak of a breath sample signal, while information that is optimized for accuracy can be based upon analysis of the integrated area of a breath sample signal. Alternatively, the system 200 can be configured to automatically switch between different modes (e.g., speed mode, accuracy mode) based upon detected environmental conditions and/or any other suitable factors.
Additionally or alternatively, variations of the system 200 can interact with beacon systems (e.g., iBeacon, Estimote systems, etc.) in order to perform background functions, even when mobile applications associated with the system 100 are in an inactive state. In one example, the system 100 can be configured to enable background operations of the system 100 in line with the method 100 described above, whenever the system 100 interacts with a beacon system (e.g., if an iOS of an Apple device detects an iBeacon system). In an example operation of such a system 200, upon detection of a beacon system (e.g., using a BlueTooth LE advertising packet that facilitates invoking of devices when specific beacon types are detected), an individual can be prompted to turn on the breathalyzer device and/or select a notification on a mobile application associated with the breathalyzer device. Then, the breath sample provision process could be initiated within the application in a streamlined process. The beacon system can be associated with a specific environment.
Further additionally or alternatively, the system can include and/or interface with a breathalyzer system during any or all of the method 100. In some variations, for instance, a breathalyzer system is used in training one or more models for TAC to BAC conversion (e.g., as described below). A breathalyzer system can additionally or alternatively be used for any or all of: calibration and/or recalibration of the transdermal device; as a supplemental system for remote monitoring of a user (e.g., in an event that the transdermal device stops working, when the transdermal device is charging, etc.); to independently determine both a TAC intoxication curve and a BAC intoxication curve; to confirm a drinking event (e.g., upon determining a change in TAC value suggesting a drinking event); and/or for any other purpose(s). The data from the breathalyzer system can be any or all of: integrated with the TAC data, supplement the TAC data, serve as a backup for the TAC data, used to determine BAC data from TAC data, and/or be otherwise used. In some variations of the system and method, for instance, during remote monitoring applications, if it is detected that the transdermal system is not working and/or has been removed from the user (e.g., for longer than a threshold period of time) and/or it is suspected that another individual is using the device, a notification can be sent to the user instructing him or her to take a breath sample with a breathalyzer system (e.g., as requested in
Furthermore, variations of the method 100 can be implemented at least in part by one or more embodiments, variations, and examples of system elements described in U.S. application Ser. No. 14/169,029 entitled “Method and System for Monitoring Intoxication” and filed on 30 Jan. 2014, U.S. application Ser. No. 14/602,909 entitled “Method and System for Remotely Monitoring Intoxication” and filed on 22 Jan. 2015, and U.S. application Ser. No. 14/631,125 entitled “Method and System for Monitoring Intoxication” and filed on 25 Feb. 2015, each of which is incorporated herein in its entirety by this reference. However, the method 100 can additionally or alternatively be implemented using any other suitable system. Furthermore, the method 100 is preferably configured for processing of data associated with fuel cell sensors; however, the method 100 can additionally or alternatively be adapted for processing of data associated with semiconductor sensors and/or any other suitable sensors for processing samples associated with intoxication or substance use.
Variations of the method and/or system can confer several benefits and/or advantages.
First, variants of the method and/or system can enable a user to know the amount of alcohol they have consumed during a drinking session, and can include notifying the user of the amount of alcohol consumed. For example, the method can include computing a number of standard alcoholic beverages (e.g., drinks) consumed based on a time-series of transdermal alcohol content (TAC) values, and displaying the number at a display of a mobile device associated with the user. In the same or a different example, the method can include determining a type of alcoholic beverage consumed by the user (e.g., beer vs. wine vs. cocktail vs. shot), which can function, for instance, to improve an accuracy of an estimated time point (e.g., time until sober, time until peak intoxication), or any other suitable parameter (e.g., blood alcohol content level at peak intoxication). In yet another example, the method can include computing a blood alcohol content (BAC) value associated with a user.
Second, variants of the method and/or system can enable determination of a peak intoxication metric value (e.g., BAC value) reached during a time window (e.g., time period). The time window can be a current time window associated with an ongoing drinking session, a past time window associated with a historical drinking session, and/or a time window associated with a future time period (e.g., a future drinking session, a non-drinking session, etc.).
Third, variants of the method and/or system can enable continuous determination (e.g., tracking, monitoring) of an intoxication metric value (e.g., BAC value, TAC value) of a user, in order to generate a curve of intoxication metric value versus time associated with a user (e.g., during a drinking session). Alternatively or additionally, variants of the system and/or method can extrapolate the intoxication metric between data collection timestamps (e.g., between two known intoxication metric values; extrapolate a predicted intoxication metric value; etc.). This can function, for instance, to better understand complex and/or persisted impacts of alcohol on health (e.g., caloric intake, recovery time after a night of drinking, sleep, etc.), as intoxication and its associated parameters (e.g., duration, timing, amount of alcohol, speed of consumption, etc.) can affect any or all of: blood pressure, arrhythmia, resting heart rate, mobilization of fat and/or nutrients absorbed, dehydration, physical fitness parameters (e.g., lactic acid buildup, exercise intensity, maximum heart rate, etc.), or any number of other parameters. By better understanding these effects for a single user and/or an aggregated set of users, more accurate intoxication guidelines, warnings, and predictions of potential threats to intoxicated individuals can be determined.
In one set of examples, for instance, continuous or near-continuous monitoring is enabled by a system in the form of a wearable wristband configured to receive transdermal samples (e.g., vapor, ethanol vapor, sweat, insensible perspiration, sensible perspiration, etc.) from a skin surface (e.g., wrist, ankle, etc.) of the user and determine TAC values based on the transdermal samples. The TAC values can then optionally be used to determine any or all of: BAC values, a number of drinks a user has consumed (e.g., for a drinking session, over a predetermined time window, etc.), a type of drink the user has consumed, an actual or predicted time point (e.g., time at which user began drinking, time at which user consumed a drink, predicted time at which user will reach peak intoxication, predicted time at which user will reach sobriety, etc.), an alcohol elimination time, and/or any other suitable parameter (e.g., those described below for notifications).
Note that a wristband device herein refers to a device which can be worn on (e.g., circumscribes) any or all of: a wrist of the user, an ankle of the user, a finger of the user, a limb of the user (e.g., arm, leg, etc.), and/or any other suitable region of the user.
In a specific example, the system and/or method can predict when the BAC will fall below a predetermined value (e.g., 0.08%, the legal limit, a manually-set value, 0.00%, a value associated with sobriety, etc.). In specific examples, the TAC curve (or value) can be used to determine a BAC curve (or value), wherein the estimated time at which the BAC value falls below the predetermined value can be estimated from the BAC or TAC curve (or value) using the method disclosed in U.S. application Ser. No. 15/979,220 filed 14 May 2018 (incorporated herein in its entirety by this reference), or using any other suitable method.
In another set of examples, continuous remote monitoring can be especially beneficial in the case of high risk individuals, enabling faster response times in the event that a user exceeds a threshold intoxication level and preventing potential harm to the user or others (e.g., by notifying a monitoring agency, providing instructions to the user, disabling a user's access to a vehicle, etc.).
In yet another set of examples, the system and/or method can enable the prediction of a peak intoxication state (e.g., peak TAC value and associated time peak is reached, peak BAC value and associated time peak is reached, etc.) or any other suitable predetermined intoxication state (e.g., a predetermined TAC or BAC value, etc.), which can function, for instance, to assist a user in planning his or her evening. The peak can be determined based on any or all of: a current intoxication level, a drinking plan, a sample parameter (e.g., volume of sweat), or any other suitable parameter. The peak is preferably dynamically updated (e.g., based on a current intoxication value, based on a user input for planned drink consumption, based on a user input classifying a drink just consumed, etc.), but can alternatively be static, updated at a predetermined interval (e.g., every hour), updated continuously, or otherwise determined. In a specific example, a user can use a predicted peak to determine whether or not to consume another drink.
Fourth, variants of the method and/or system can enable real-time notification of a user's intoxication level, thereby improving users' ability to moderate their alcohol consumption. For example, the method can include determining that a user has consumed a number of drinks exceeding a threshold number (e.g., set by the user as a preference) and notifying a user in response to determining that the threshold number has been exceeded. In another example, the method can include determining that a rate of alcohol consumption has exceeded a threshold rate (e.g., based on demographics of the user) and transmitting a notification to an entity (e.g., the user, a monitoring agent) in response to the rate of alcohol consumption exceeding the threshold rate.
Fifth, variants of the method and/or system can enable an accurate and/or precise determination of a BAC value from a TAC value as measured from a skin surface (e.g., wrist region, arm region, shoulder region, etc.) of a user. In an example, for instance, a TAC value can be used to determine a BAC value with greater than 80% confidence (e.g., greater than 90% confidence, 95% confidence, etc.). The method and/or system can additionally or alternatively confer the benefit of determining a BAC value from a TAC value with minimal lag from the first time point of alcohol consumption until a first reading indicating an intoxication metric (e.g., actual intoxication, predicted intoxication, etc.) above baseline is determined and/or provided to the user (e.g., less than 20 minutes, less than 30 minutes, between 2 minutes and 1 hour, greater than 10 minutes, etc.).
Sixth, variants of the method can enable an improved (e.g., faster, more accurate, higher confidence, etc.) prediction and/or determination of alcoholism of a user. In some examples, for instance, continuous monitoring of a user's intoxication with the system and/or method can determine an intoxication parameter used to assess whether or not the user is an alcoholic. In a specific example, for instance, a rate of alcohol processing is determined and compared with a predetermined threshold (e.g., 0.015 grams per 100 milliliters per hour [g/100 mL/hr]), and if the determined rate is greater than the threshold, an assessment of alcoholism is attributed to the user. This can then serve, for instance, as a suitable trigger for any number of outcomes (e.g., call to a monitoring agency, notification to a user, recommendation to the user, etc.).
Seventh, variants of the method and/or system can enable the scheduling of a night out for a user or set of users, which can be optimized for any or all of: safety, convenience, cost (e.g., ensuring that a user can legally drive himself the entire night), timing (e.g., planned last drink time to ensure user reaches a legal level before bar closes), enjoyment (e.g., reaching and sustaining a baseline intoxication level, preventing a hangover, etc.), or any other suitable factor.
Eighth, variants of the method and/or system can enable an accurate reading and assessment of the effects of alcohol on a second factor, such as effects of alcohol use on the effectiveness of a drug being tested by a pharmaceutical company. In an example, for instance, the system and/or method can be used to determine how alcohol affects the effectiveness of a drug, which can provide more accurate data and robust analyses than current data (e.g., user self-reporting, infrequent urine tests, etc.).
Ninth, variants of the method and/or system can enable an integrated approach to intoxication analysis, utilizing information (e.g., user location information, user calendar, user history, user preferences, etc.) from additional information sources (e.g., client applications executing on a user device, web pages, etc.), which can function to provide instructions, notifications, and triggers of maximum usefulness to each user. In some examples of this variant, the integrated approach is enabled through a client application executing on a user device having access to other client applications executing on the user device. In one example, detecting that a user is located in a bar (e.g., based on GPS data of mobile phone) and that the user did not utilize a ride share service (e.g., by checking history of ride share application) to get to the bar, a notification can be provided to a user a set time before the bar closes to encourage the user to stop drinking so that he or she can legally drive home once the bar closes.
Tenth, variants of the method and/or system can enable a user to achieve and/or maintain a desired intoxication “sweet spot,” such as any or all of: an ideal level of buzz for an extended period of time, a mitigation of hangovers, and a mitigation of the impact of drinking on user health (e.g., sleep, weight, fitness, wellness, etc.). In some examples, for instance, a continuously updated intoxication curve can be provided to a user to determine when and how often the user should drink to achieve a desired effect.
Eleventh, variants of the method and/or system can enable a consumer to track alcohol use for fun and out of curiosity. In some examples, for instance, the system and/or method can function to provide easy-to-interpret data (e.g., in the form of one or more graphical displays or other visual identifiers), which can then be shared with others (e.g., texted), uploaded to social media, used to plan a social event (e.g., meet-up at current bar where user is located), or otherwise used.
Twelfth, variants of the method and/or system can enable a remote monitoring entity to determine and/or detect when a transdermal system is not being worn by the user and/or is being worn by an individual other than a user, which can further enable the transdermal system to be removable and low profile while still having high confidence results related to a particular user's sobriety (e.g., by preventing tampering). In specific examples of a wristband system, the wristband is configured with a mechanism to detect if one or more adjustment settings have been altered and the method includes notifying a user in that event (e.g., to request that the user take a photo of himself or herself wearing the device, to instruct the user to place the wristband back on and/or reposition, etc.).
However, variants of the method and/or system can confer any other suitable benefits and/or advantages.
As shown in
Further additionally or alternatively, the system 200 can include and/or interface with any or all of the systems, components, embodiments, and/or examples described in any or all of: U.S. application Ser. No. 16/218,357, filed 12 Dec. 2018, U.S. application Ser. No. 15/979,220, filed 14 May 2018, U.S. application Ser. No. 16/431,130, filed 4 Jun. 2019, U.S. application Ser. No. 16/846,110, filed 10 Apr. 2020, U.S. application Ser. No. 16/362,289, filed 22 Mar. 2019, and U.S. application Ser. No. 16/823,017, filed 28 Mar. 2020, each of which is incorporated herein in its entirety by this reference.
The system 200 preferably receives one or more inputs in the form of a biological sample (e.g., vapor from skin surface, ethanol vapor, sweat, breath, urine, saliva, blood, etc.) from a user. Biological samples are preferably received at a housing 210 of the system 200 but can additionally or alternatively be received at a secondary device (e.g., a breathalyzer), a user device, a remote server or database, or any other suitable location. The system 200 can additionally or alternatively receive other suitable inputs (e.g., settings, triggers between operation modes, user preferences, etc.), such as through one or more input elements (e.g., buttons, sliders, touch-sensitive surfaces, knobs, dials, etc.) of the system 200.
The system 200 preferably provides a set of one or more outputs to a user, which function to indicate an intoxication level of the user. In some variations, the outputs are provided at a housing 210 of the system (e.g., through a light emitter, vibration motor, speaker, etc.). Additionally or alternatively, outputs can be provided at a user device 260 or any other suitable component or system.
In variations of the system 200 including and/or configured to interact with (e.g., communicatively couple, wirelessly connect, etc.) a user device 260, any or all of the inputs and outputs can be received or provided, respectively, at the user device. In an example, for instance, an input in the form a biological sample is received at an inlet 220 of the system, an input in the form of a user schedule is received at a client application executing on a user device 260 wirelessly connected to the system, an output in the form of a blinking light is provided at a light emitter of the housing 210 (e.g., wherein a color, blinking frequency, and/or brightness indicates an intoxication level of the user), and an output in the form of a graphic display depicting an intoxication curve is provided at a display of a user device 260.
The sensor 230 functions to determine a signal (e.g., electrical signal) based on a set of one or more samples (e.g., biological samples) received from the user. The sensor 230 preferably includes a fuel cell sensor, but can additionally or alternatively include an enzymatic sensor, or any other suitable sensor. The sensor preferably receives one or more samples from a user, further preferably one or more biological samples. Additionally or alternatively, the sensor 230 can receive user information, environmental information, contextual information, or any other suitable information. The sensor can be removable from the system 200, or be permanently coupled to the system 200.
The system 200 can optionally include any number of supplementary sensors, which can function to receive environmental and/or contextual information. The supplementary sensors can include any or all of: a skin conductance sensor, temperature sensor, moisture sensor (e.g., galvanic skin response sensor), microphone (e.g., to determine an environment of a user such as a noisy bar vs. a quiet home, to recognize a noisy bar setting, to recognize the sound of a vehicle being operated, to determine if the user is drinking alone and/or with others, etc.), camera (e.g., to image surroundings of a user), other ambient environment sensors (e.g., humidity sensor, ambient light sensor, etc.), accelerometer or other kinematic sensor (e.g., to determine if a user is exercising to induce sweating), a biomonitoring sensor (e.g., heart rate monitor, electroencephalography sensor, etc.), sensors to determine calories burned by a user and/or caloric output, a step counter, a location sensor (e.g., GPS sensor, other position sensors, to determine distance traveled, to determine if a user is outside his home, etc.), a clock (e.g., to determine time of day), an elevation sensor, and/or any other suitable sensor. The supplementary sensors can be any or all of: arranged onboard a wearable portion of the system (e.g., onboard/coupled to a wristband), onboard a breathalyzer, onboard a user device (e.g., user device coupled to the transdermal system such as a smart watch, user device remote from the transdermal system such as a smart phone, etc.), remote from the system (e.g., in an environment of the user), and/or at any other suitable locations or combination of locations.
In some variations, the system 200 includes a heart rate sensor (e.g., at a housing including the TAC sensor, at a smart watch coupled to a wristband, etc.), wherein data from the heart rate sensor are used to establish a relationship (e.g., correlation) between TAC and/or BAC values and the heart rate value. This can be used, for instance, to provide insights (e.g., to the user, to a remote monitoring entity, to a family member, to a database and/or trained model, etc.) into how the user's drinking and/or sobriety is related to his or her heart rate and how his or her body's response to drinking has changed over time.
Any or all of the sensors can be used to determine if a system (e.g., wristband) is being worn by a user (e.g., the intended user, a user other than the intended user, etc.), which can function to enable any or all of: determining when to collect transdermal samples and when to stop; determining if somebody is using the device (e.g., to trigger a measurement to detect if the proper user is using the device, to transmit a notification, etc.); determining if the correct user is using the device; and/or determining any other suitable information.
In one variation, the system 200 includes an accelerometer (e.g., in a transdermal alcohol sensing device, in a user device, in a breathalyzer device, etc.), which functions to measure a user's personal gait pattern and use the personal gait pattern as a unique identifier (e.g., in a two-factor authentication process). The gait pattern can then, for instance, be associated with an alcohol signal received at the device (e.g., contemporaneously with the gait pattern) having the accelerometer. A second verification signal (e.g., video of user displaying gait pattern and user's face for identification) can be taken as well to associate the user's identity with the gait pattern (e.g., determined through image analysis of video of the user walking). In a specific example, for instance, a sample received at a transdermal alcohol sensing device (e.g., wristband device) can be recorded contemporaneously (e.g., during an overlapping time period, with a delay of less than 1 minute, etc.) with a gait pattern received at an accelerometer in the transdermal alcohol sensing device. A second verification signal which associates the user's identity with the gait pattern can be recorded at a camera (e.g., of a user device). Based on these two authentication processes, it can be confirmed that the alcohol signal is associated with the appropriate user.
An accelerometer can additionally or alternatively be used in detecting whether or not the system is being worn by the user/the proper user (e.g., for remote monitoring), such as by detecting any or all of: a numeric tightness level of the device; a movement and/or rotation and/or orientation of the device (e.g., relative to a user), such as a detection of twisting and/or fastening to determine that the device is being fastened on and/or unfastened from a user; and/or any other suitable information.
Additionally or alternatively, any other motion sensors (e.g., speedometer) can be implemented into the system (e.g., wristband) and/or user device.
In a first variation of the sensor system, the sensor system collects motion data, temperature data (e.g., skin temperature), and TAC values. In specific examples, the sensor system additionally or alternatively collects heart rate information and/or any other suitable information with any suitable sensors.
The housing 210 functions to support one or more components of the system 200, and to receive one or more samples (e.g., biological samples) from the user. Additionally or alternatively, the housing 210 can function to prevent ingress of matter from the environment (which could affect analysis of a biological sample, for instance), retain the system 200 against the user, or perform any other suitable function.
The system 200 can additionally include any or all of: a power source (e.g., rechargeable battery), memory, a processing system (e.g., processor, microprocessor, CPU, etc.), control module, a fastener (e.g., band, wristband, clip, etc.), a sealing mechanism (e.g., gasket) configured to create a gaseous seal between the sensor and the environment (e.g., to prevent particulate matter from being introduced to a transdermal sensor), and/or any other suitable components and/or combination of components.
In a first variation of the system 200 (e.g., as shown in
In some examples, the system 200 periodically syncs with a secondary device, such as a user device 260, where the secondary device is configured for any or all of: receiving and processing a signal from the system (e.g., a signal based on sensor measurements, based on supplementary sensor measurements, etc.), receiving and processing an electrical signal from a sensor (e.g., at a wristband device), receiving and processing an intoxication parameter, providing one or more notifications to a user, receiving user input, or any other suitable process. In a specific example, an averaged electrical signal is received from a sensor at a client application executing on the user device (e.g., as shown in
Examples of the user device 260 include a tablet, smartphone, mobile phone, laptop, watch, wearable device (e.g., glasses), or any other suitable user device. The user device can include power storage (e.g., a battery), processing systems (e.g., CPU, GPU, memory, etc.), user outputs (e.g., display, speaker, vibration mechanism, etc.), user inputs (e.g., a keyboard, touchscreen, microphone, etc.), a location system (e.g., a GPS system), sensors (e.g., optical sensors, such as light sensors and cameras, orientation sensors, such as accelerometers, gyroscopes, and altimeters, audio sensors, such as microphones, etc.), data communication system (e.g., a WiFi transceiver(s), Bluetooth transceiver(s), cellular transceiver(s), etc.), or any other suitable component.
The system 200 can optionally further include a mechanism and/or component(s) for detecting any or all of: the system being off of the user (e.g., wristband is not on the user's wrist); the system being actively removed from the user (e.g., wristband is being moved off [e.g., slid off, unfastened, unbuckled, stretched, etc.] of the user's wrist); the system is being used by and/or worn by another user; and/or can detect any other indication that the intended user is not using the system as intended. This can have numerous functions in the remote monitoring space, such as in probation monitoring and/or criminal justice form, as detecting misuse of the system is critical. In some variations, this enables the system to be removable (e.g., for charging, during showering, etc.) while still having a high confidence that the recorded data corresponds to the correct person.
This can be implemented with one or more system components and/or features of system components, such as in a fastener of the system. In variations wherein the transdermal sensing system is arranged at a wrist of the user with a wristband fastener, the wristband can include one or more components configured to detect any or all of: whether the wristband is on or off the user; whether the wristband is being removed from the user (e.g., moving relative to the user, going over a user's hand, being stretched, under high tension, etc.) and/or switching wrists; whether the wristband is at a different size setting than the user's normal setting; and/or any other suitable features. The system components can include
Additionally or alternatively, any or all of the sensor system (e.g., temperature sensor to detect temperature of skin, humidity sensor, biometric sensor, heartrate sensor, etc.) can be used to detect any or all of this information. In some variations, for instance, the sensor system is used to determine whether a wristband is on or off the user and a fastener system is used to determine what size setting (e.g., length of wristband, amount of stretch in wristband, etc.) is associated with the user.
The fastener system in wristband variations can include any suitable variations, such as any or all of: a deployant clasp, a push-button deployant clasp, a fold-over push-button deployant clasp, a double-locking fold-over clasp, a butterfly clasp/hidden clasp, a jewelry clasp, an ardillon/Tang buckle (e.g., with a pin that engages with an eyelet/aperture), a Velcro strap, and/or any other suitable fastener(s)>
The method 100 can optionally include one or more processes (e.g., as described below) to perform any or all of: processing the information; determining misuse of the system; triggering one or more actions (e.g., notifications, reminders, alerts); and/or any other suitable processes.
In a first set of variations of a wristband system configured to detect misuse, the system includes a wristband fastener with a mechanism (e.g., a tightness detection subsystem) configured to detect one or both of removal of the fastener from the user and a change in setting associated with the fastener, wherein the sensor system is optionally used to determine if the wristband is on a user (e.g., or on a surface). Each user is preferably associated with a predetermined wristband setting parameter (e.g., length of wristband as measured relative to a clip/hook/buckle/magnet or other feature for setting a tightness, tightness, tension, amount of stretch, width, etc.), but can additionally or alternatively be associated with (e.g., assigned, assigned during an onboard process, etc.) multiple values and/or any other suitable values.
In a first set of specific examples (e.g., as shown in
In a second set of specific examples (e.g., as shown in
Additionally or alternatively, instead of induction coils, the system can include a magnetic subsystem, such as with one or more embedded fixed magnets on one side of the band and one or more Hall effect sensors on the other side. This can confer the benefit, for instance, of enabling the wristband to be small in size (e.g., thickness).
As shown in
Further additionally or alternatively, the method 100 can include and/or interface with any or all of the methods, processes, embodiments, and/or examples described in any or all of: U.S. application Ser. No. 16/218,357, filed 12 Dec. 2018, U.S. application Ser. No. 15/979,220, filed 14 May 2018, U.S. application Ser. No. 16/431,130, filed 4 Jun. 2019, U.S. application Ser. No. 16/846,110, filed 10 Apr. 2020, U.S. application Ser. No. 16/362,289, filed 22 Mar. 2019, and U.S. application Ser. No. 16/823,017, filed 28 Mar. 2020, each of which is incorporated herein in its entirety by this reference.
4.1 Method: Receiving a Set of Samples from a Body Region of a User S110
Block S110 includes: receiving a set of samples from a body region of a user. Block S110 functions to obtain biological samples from a user that contain material that can be analyzed to determine an intoxication metric of the user. Block S110 is preferably performed using a wearable transdermal alcohol sensing device, such as the system 200 described above, but can additionally or alternatively be performed using a breathalyzer, a patch attached to a user by adhesive, and/or any other suitable alcohol sensing device.
The body region of the user preferably includes a wrist region (e.g., palm-side skin surface below hand, skin surface below hand opposing palm, skin surface opposing a watch face, skin surface beneath a watch face, etc.), but can additionally or alternatively include an arm region (e.g., shoulder region, upper arm skin surface, lower arm skin surface, etc.), leg region, torso region, head region (e.g., mouth region, forehead skin surface, neck skin surface, earlobe, etc.), or any other suitable region. For variations involving transdermal alcohol sensing, the body region is selected based on a perspiration level (e.g., does not experience excessive perspiration, is not too dry, etc.) of the body region. In some variations, for instance, regions of excessive perspiration (e.g., armpit) are avoided. Additionally or alternatively, the body region can be selected to avoid oily regions (e.g., avoid a sebaceous gland, etc.), excessive hair, or otherwise be selected in any other suitable way. In one variation, for instance, a bottom wrist region (e.g., adjacent to the palm of the hand) is chosen over an opposing top wrist region because the bottom wrist region experiences higher yet controlled perspiration, as well closer proximity to the bloodstream and better access to the skin.
Block S110 is preferably performed during a time window, and thus the set of samples is preferably a time-series of samples collected sequentially within the time window. The time window preferably includes a drinking session, but can additionally or alternatively include multiple drinking sessions, non-drinking time periods, pre-drinking time periods, post-drinking time periods, and any other suitable time periods. The time window is preferably continuous, but in alternative variations of Block S110 the time window can be discontinuous.
The time-series of samples is preferably taken at a predetermined regular frequency (e.g., 1 sample every second, 1 sample every 20 seconds, 1 sample every minute, 1 sample between every 1 second and every 20 minutes, less than 1 sample every 20 minutes, greater than 1 sample every minute, etc.). Additionally or alternatively, the frequency of sampling can be dynamic, adjustable (e.g., based on user and/or remote monitoring entity preferences), determined based on an intoxication level of the user (e.g., most recent TAC value, most recent BAC value, slope of intoxication curve, etc.), determined based on an environmental parameter (e.g., temperature, humidity, etc.), determined based on contextual or historical data (e.g., user intoxication history, user schedule, fitness activity, user profile, etc.), periodically updated (e.g., based on a software update of a client application executing on a user device), or otherwise determined. In a specific example, the frequency at which the time-series of samples is taken is based on an intoxication level of the user, such that when the user has a relatively high level of intoxication (and/or a rapidly increasing level of intoxication), samples are taken more frequently than when the user has a relatively low level of intoxication. In determining that the user has reached sobriety, for instance, S110 can optionally include stopping sample collection, turning off the sampling device, or performing any other suitable function.
One or more sampling parameters (e.g., frequency, timing, etc.) can additionally or alternatively be determined based on a particular application or goal (e.g., consumer use, criminal monitoring, pharmaceutical testing, etc.) for alcohol monitoring. Samples may be taken more frequently (e.g., every second) for pharmaceutical testing, for instance, than routine remote alcohol monitoring (e.g., 4 times per day).
In a first variation, S110 includes receiving a biological sample (e.g., ethanol vapor) transdermally from a transdermal alcohol sensing device. In preferred examples of this variation, a time series of transdermal samples are received regularly at the transdermal alcohol sensing device (e.g., at an inlet defined by the housing) from the user (e.g., wrist region of the user, arm region of the user, etc.), while the device is in an active sensing state (e.g., “on” state). The active sensing state can be initiated by any suitable triggers, such as—but not limited to—detection that the transdermal alcohol sensing device has been placed on the user, initiation of the “on” state by the user (e.g., upon pressing a power button of the housing), based on a calendar, based on a clock, based on a predetermined schedule, randomly, or based on any other suitable trigger. In alternative examples, a single sample is taken, a set of samples are taken at irregular intervals, or samples are otherwise taken.
In a second variation, multiple types of biological samples (e.g., transdermal skin samples and breath samples) are taken from a user (e.g., from the same body region, from different body regions, from the same alcohol sensing device, from different alcohol sensing devices, etc.), which can function, for instance, to determine a correlation function of the method (e.g., TAC to BAC conversion, BAC to time-to-sober conversion, etc.), to account for a limitation of a first type of biological sample with a second type of biological sample (e.g., account for lag of transdermal alcohol response with breath samples for an initial of period of time), otherwise supplement alcohol data determined from the samples, or perform any other suitable function. In a specific example, transdermal samples are taken from a user with a transdermal alcohol sensing device contemporaneously (e.g., at the same time, during an overlapping time interval, with a temporal separation of between 0 seconds and 1 hour, etc.) with breath samples taken from the user at a breathalyzer. The paired transdermal and breath samples are then used to determine and/or refine a correlation function for converting TAC values into BAC values. In a second specific example, the system can be calibrated for a given user by taking TAC values when the user is alcohol-free (e.g., as verified using a breathalyzer, as stated by the user, etc.), and by taking TAC values (and/or corresponding BAC values) at predetermined time intervals after the user has been dosed with a known amount of alcoholic beverage over a predetermined time period (e.g., 750 ml of beer in an hour). In a third specific example, one or more of the correlation functions can optionally identify environmental alcohol based on: the curve slope (e.g., wherein the slope is steeper than the slope due to ingested alcohol), the curve spread (e.g., wherein the spread is narrower than that for ingested alcohol), or otherwise determined.
In a third variation, multiple different indicators (e.g., chemicals, precursor chemicals, proteins, secretions, etc.) are collected and assessed from a single alcohol sensing device (e.g., transdermal alcohol sensing device, etc.). This can function to more accurately predict a future intoxication value, minimize lag in determining a TAC value, or perform any other suitable function. In one example, for instance, the method includes collecting transdermal oxygen at a transdermal alcohol sensing device, which can be used to detect and/or predict an intoxication level of the user (e.g., current intoxication, future intoxication, peak intoxication, etc.) earlier than the primary indicator (e.g., ethanol vapor). In this example, the method can optionally preferentially use TAC values determined from insensible perspiration measurements to determine BAC values after a predetermined time period (e.g., corresponding to insensible perspiration delay; such as 30 minutes, 45 minutes, 60 minutes, a period of time specific to the user or the user parameters, etc.). However, a combination of measurements can be otherwise cooperatively used to refine or serially determine the BAC measurement. Alternatively, any number and type of indicators can be collected at any single device or set of multiple devices.
4.2 Method: Generating an Intoxication Metric Based on the Set of Samples S120
Block S120 includes: generating an intoxication metric based on the set of samples. Block S120 functions to determine a parameter of interest, related to the intoxication of the user, using the received samples. Block S120 preferably functions to quantitatively assess an intoxication level of a user, which can optionally further function to trigger any number of notifications (e.g., to the user, to a monitoring agency, to another entity, etc.) or actions (e.g., automatically ordering a ride share vehicle for an intoxicated user). Additionally or alternatively, Block S120 can function to qualitatively assess an intoxication level of a user (e.g., track general progress of a user), share an intoxication level of a user (e.g., through social media, with an employer, etc.), or perform any other suitable function.
Block S120 is preferably performed at a processing system outside of the alcohol sensing device (e.g., transdermal alcohol sensing device, breathalyzer, etc.), such as a processing system associated with any or all of: a user device (e.g., processing system onboard the user device), client application executing on a user device, remote server, local server, or any other suitable location. Additionally or alternatively, any or all of Block S120 can be performed at a processing system onboard the alcohol sensing device.
The intoxication metric (e.g., as measured in grams of alcohol per deciliter of blood [g/dL], milligrams of alcohol per deciliter of blood [mg/dL], grams of alcohol per 210 liters of breath, etc.) can include a blood alcohol content (BAC) value, a transdermal alcohol content (TAC) value, a breath alcohol concentration (BrAC) value, a qualitative indicator of intoxication (e.g., wording such as “you're drunk”, “you're tipsy”, “you're stone cold sober”, a color indicator of level of intoxication, etc.), a binary metric (e.g., a go/no-go indicator based on a threshold parameter value), a timing metric (e.g., time until sober, time until peak, time until it's okay to drive, whether or not the user will wake up the next day and be sober, etc.), a confidence level of the measurement (e.g., TAC value, BAC value, etc.), or any other suitable metric. The intoxication metric is preferably determined based on a signal (e.g., electrical signal) determined at the sensor based on the sample, but can additionally or alternatively be determined based directly on the sample, additional data from a supplementary sensor of the system, or any other suitable data.
The intoxication metric can additionally or alternatively include a parameter related to an intoxication curve (e.g., TAC curve, BAC curve, etc.) or function (e.g., constructed from a time series of intoxication metrics, predicted based on a set of intoxication metrics, predicted based on theory, etc.), such as—but not limited to—a slope, peak, span, average value, median value, area under the curve, the temporal proximity of the curve relative to adjacent curves (e.g., inter-peak distance), correlation with curve parameters for auxiliary compounds (e.g., sampled contemporaneously with the primary compound), or any other suitable parameter. Examples of auxiliary compounds (e.g., associated with intoxication) can include: transdermal oxygen, carbon dioxide, In an example, for instance, S120 includes determining a slope of an intoxication curve (e.g., TAC curve), which can effectively indicate a rate of drinking, wherein when the slope surpasses a predetermined threshold steepness, a trigger is initiated (e.g., notification to mobile phone to warn user, notification with instructions to stop drinking, suspension of payment through a mobile payment application, etc.).
Block S120 can optionally include determining a BAC value based on a TAC value. This variation preferably includes determining the BAC value based on a set of one or more predetermined correlation functions (e.g., retrieved from a database, stored at a processing unit of the alcohol monitoring device, etc.) that relates measured TAC values (and/or auxiliary compound measurements) to corresponding BAC values. However, this variation can additionally or alternatively include determining a correlation function in real time (e.g., based on simultaneously measured signals corresponding to BAC and TAC values) and determining the BAC value based on the correlation function determined in real time, and otherwise suitably determining the BAC value with or without a correlation function.
Each of the set of correlation functions can be an equation (e.g., linear regression) with weighted variables (e.g., time to peak TAC, gender, etc.), be a neural network, decision trees, rule sets, or be any suitable function or method. This variation can additionally or alternatively include: determining the BAC based on implementing a learning-based model (e.g., a learning agent or neural network trained according to machine learning principles, wherein TAC values are inputs to the model and BAC values are outputs of the model, wherein the model can be trained on-line or off-line using supervised learning, unsupervised learning, reinforcement learning, deep learning, etc.); determining the BAC based on a set of rules that transform a TAC value into a corresponding BAC value; and/or any other suitable means for determining the BAC value based on the TAC value. The BAC determination model (e.g., correlation function, etc.) can be: generic to all users; specific to a user (e.g., based on the user's use history; user's parameters, such as gender or location, based on a user's sweat volume, etc.); specific to a user population (e.g., wherein the population can share a common user parameter, such as gender or geographic location); or be otherwise used for different users.
In preferred variations, the BAC values are determined based on a set of one or more machine learning models and/or decision trees. The models can be supervised, unsupervised, and/or determined based on any learning and/or combination of learning. In specific examples, the models include and/or involve one or more of: a Random Forest decision tree, clustering (e.g., regression clustering), a support vector machine, logistic regression, and a neural networks. Additionally or alternatively, the correlation function can include any other suitable models.
In specific examples, a BAC value is determined from a TAC value with a Random Forest decision tree.
Additionally or alternatively, the models can include any other suitable Each model can utilize one or more of: supervised learning (e.g., using logistic regression, using back propagation neural networks, using random forests, decision trees, etc.), unsupervised learning (e.g., using an Apriori algorithm, using K-means clustering), semi-supervised learning, reinforcement learning (e.g., using a Q-learning algorithm, using temporal difference learning), and any other suitable learning style. Each model can implement any one or more of: a regression algorithm (e.g., ordinary least squares, logistic regression, stepwise regression, multivariate adaptive regression splines, locally estimated scatterplot smoothing, etc.), an instance-based method (e.g., k-nearest neighbor, learning vector quantization, self-organizing map, etc.), a regularization method (e.g., ridge regression, least absolute shrinkage and selection operator, elastic net, etc.), a decision tree learning method (e.g., classification and regression tree, iterative dichotomiser 3, C4.5, chi-squared automatic interaction detection, decision stump, random forest, multivariate adaptive regression splines, gradient boosting machines, etc.), a Bayesian method (e.g., naïve Bayes, averaged one-dependence estimators, Bayesian belief network, etc.), a kernel method (e.g., a support vector machine, a radial basis function, a linear discriminate analysis, etc.), a clustering method (e.g., k-means clustering, expectation maximization, etc.), an associated rule learning algorithm (e.g., an Apriori algorithm, an Eclat algorithm, etc.), an artificial neural network model (e.g., a Perceptron method, a back-propagation method, a Hopfield network method, a self-organizing map method, a learning vector quantization method, etc.), a deep learning algorithm (e.g., a restricted Boltzmann machine, a deep belief network method, a convolution network method, a stacked auto-encoder method, etc.), a dimensionality reduction method (e.g., principal component analysis, partial lest squares regression, Sammon mapping, multidimensional scaling, projection pursuit, etc.), an ensemble method (e.g., boosting, boostrapped aggregation, AdaBoost, stacked generalization, gradient boosting machine method, random forest method, etc.), and any suitable form of machine learning algorithm. Each model can additionally or alternatively be a: probabilistic model, heuristic model, deterministic model, or be any other suitable model leveraging any other suitable computation method, machine learning method, or combination thereof.
Each model can be validated, verified, reinforced, calibrated, or otherwise updated based on newly received, up-to-date measurements; past measurements recorded during the operating session; historic measurements recorded during past operating sessions; or be updated based on any other suitable data. Each model can be run or updated: once; at a predetermined frequency; every time the method is performed; every time an unanticipated measurement value is received; or at any other suitable frequency. The set of models can be run or updated concurrently with one or more other modules, serially, at varying frequencies, or at any other suitable time. Each model can be validated, verified, reinforced, calibrated, or otherwise updated based on newly received, up-to-date data; past data or be updated based on any other suitable data. Each model can be run or updated: in response to determination of an actual result differing from an expected result; or at any other suitable frequency.
The method can optionally include training any or all of the set of models, such as with aggregated user data. In some variations, for instance, a set of test subjects are provided with a predetermined set of drinks at predetermined intervals (or are able to drink randomly/as desired), wherein a TAC value is collected at a transdermal sensing device simultaneously and/or contemporaneously with the recording of a BAC value at a breathalyzer at a set of times and/or at a predetermined frequency.
The set of one or more correlation functions (e.g., implemented as one or more machine learning models) can optionally additionally or alternatively be determined based on any number of factors specific to a user, specific to the general population, determined by theory, or otherwise characterized. A correlation function, such as one specific to a user, can be determined based on any or all of the following user body information: fat content, sweat or perspiration level (e.g., sweat measurements, hyperhidrosis indication, etc.), activity level (e.g., heart rate, resting heart rate, workout log, etc.), skin type (e.g., color, race, dryness, oiliness, etc.), hair (e.g., type, amount, coarseness, etc.), tattoos, age (e.g., to determine a level of wrinkling), height, weight, food intake, ethnicity, or any other suitable user parameter. In some variations, a large density of hair can cause a weaker signal to be detected and therefore can be incorporated into a correlation function to achieve more accurate results.
In some variations, determining one or more features of an intoxication curve, such as area under the curve (and therefore a number of drinks consumed by the user) involves taking into account user demographic information (e.g., gender, height, weight, etc.), which can be used when training the model.
An amount of sweat (e.g., volume of sweat, overall volume of sweat produced by user, daily volume, average volume per time period, rate of perspiration, etc.) generated by a user or set of users can potentially be useful to incorporate into a correlation function. When using a transdermal alcohol sensing device to take a sample from a skin surface of a user, for instance, a volume of sweat collected from a user can be used to better approximate a TAC value, a predicted future intoxication value, a predicted time until sober, or any other suitable value. In a specific example, for instance, an inflated intoxication parameter (e.g., “too high” TAC value) could result from a user having a high level of perspiration—a correlation function could take that into account (e.g., predict a sooner time until sober than would be otherwise determined), be calibrated based on a sweat level, or be otherwise determined.
Additionally or alternatively, one or more correlation functions can be determined or adjusted (e.g., reweighted, corrected, newly selected, etc.) based on any suitable contextual (e.g., environmental) data (e.g., as determined by supplementary sensors of the alcohol sensing device, as determined by a sensor of a user device, etc.). These can include any or all of: temperature, humidity, location, or any other suitable parameter. A cold environment (e.g., below 50 degrees Fahrenheit [deg F.], between 30 and 70 deg F., between 0 and 30 deg F., etc.) could, for instance, cause the sensor to respond more slowly, which could in turn trigger any or all of: the system having a larger delay prior to taking measurements (e.g., to preserve battery life), a notification to the user instructing him to step inside to take measurements, an adjustment within the correlation function, or any other suitable outcome. A hot environment (e.g., above room temperature, above 70 deg F., above 90 deg F., between 80 deg F. and 110 deg F., etc.) could be used to predict a user sweat volume, trigger an adjustment within the correlation function, or result in any other suitable outcome. An environment filled with many people drinking (e.g., a crowded bar) could optionally be taken into account when determining a TAC and/or a BAC value, as alcohol in the air could inflate results.
Block S120 can optionally include determining a correlation function based on multiple sample types. A comparison between a set of TAC values and a set of BrAC values (which can, in some instances, more closely correlate with BAC) contemporaneously taken (e.g., with a breathalyzer) can be used, for instance, in the determination of a correlation function. In a specific example, a set of samples is taken from a transdermal alcohol sensing device contemporaneously with a set of BrAC samples taken at any of the systems described in U.S. application Ser. No. 15/979,220, filed 14 May 2018, U.S. application Ser. No. 15/882,825, filed 29 Jan. 2018, U.S. application Ser. No. 16/010,093, filed 15 Jun. 2018, U.S. application Ser. No. 15/205,876, filed 8 Jul. 2016, and U.S. application Ser. No. 15/492,216, filed 20 Apr. 2017, which are each herein incorporated in its entirety by this reference.
As shown by example in
Block S120 can additionally or alternatively include one or more signal processing processes applied to an intoxication curve, which can function to identify specific features and patterns of the user's drinking, as represented in the details of the intoxication curve. A convolution process (e.g., convolution of peaks), for instance, can be applied to an intoxication curve, which can enable the determination or approximation of the times at which the user consumed a beverage, the type of beverage, and/or any other suitable information. In an example, a convolution analysis of an intoxication curve resulting in the determination that three sudden spikes occurred during the drinking session, which corresponds to the user taking three shots of alcohol in a row. Based on the steepness of the curves (e.g., spikes), it could be determined, for instance, that the user instead sipped a cocktail over a longer period of time. Additionally or alternatively, the type of beverage can be determined from one or more intoxication curve parameters, wherein the parameter values (or derivative features thereof, such as patterns) can be correlated or otherwise associated with different beverage types. Additionally or alternatively, Block S120 can include any other suitable processing of an intoxication curve.
Block S120 can additionally or alternatively include determining a recovery rate from alcohol (rate at which alcohol is processed by the liver and eliminated from the body), which can be used to initiate a trigger (e.g., notification to user to stop drinking), update a user schedule (e.g., suggest a last drink time in light of a proposed driving time), or be used for any other suitable outcome. In the event that the recovery rate is higher than a predetermined threshold (e.g., 0.015 g/100 mL/hr), a notification can be provided that the user is classified as an alcoholic or in danger of becoming an alcoholic.
Block S120 can optionally include any suitable type of data transmission, data processing, and data storage. To preserve memory (e.g., onboard an alcohol sensing device), for instance, Block S120 can include taking an average or otherwise aggregating a set of sample signals (e.g., every 20 seconds, every 20 collected sample signals, between every 2 and every 1000 sample signals, etc.) and storing only the average/aggregated value. This can be performed at regular time intervals (e.g., every 20 seconds, between every 1 second and every hour, more than once per second, less than once per hour, etc.), at irregular time intervals (e.g., dynamically updated, random, etc.), in response to a trigger (e.g., when alcohol sensing device is in close proximity with a user device), or at any other suitable time. Additionally or alternatively, Block S120 can include any or all of: storing a subset of samples (e.g., each sample at a predetermined interval, every third sample, random subset, etc.), storing all samples, storing a median value of samples, storing minimum values, maximum values, or any other suitable sample signals.
In variations of the method including a user device in communication with the alcohol sensing device, Block S120 can include periodically (e.g., at predetermined intervals of time, after a predetermined number of samples have been collected, etc.), syncing the alcohol sensing device and the user device (e.g., a foreground client application executing on the user device, a background client application executing on the user device, etc.). This can function to preserve battery life onboard the alcohol sensing device while still regularly communicating signals to the user device for processing. Alternatively, the alcohol sensing device can be continuously synced with a user device, never synced, synced in response to a trigger (e.g., prompting by the user, prompting from the user device, based on a charge level of the alcohol sensing device, when the wristband device and user device are in close proximity, etc.). In these variations, Block S120 can additionally or alternatively include removing (e.g., deleting, not storing, etc.) redundant parameter values (e.g., redundant signal values, redundant intoxication metrics, etc.). In an example, for instance, Block S120 includes comparing a set of signal values (e.g., averaged values) received from the alcohol sensing device (e.g., received contemporaneously, sequentially, at different points in time, etc.) and not storing (or removing if already stored) redundant values from memory associated with the user device. Block S120 can further additionally or alternatively include pushing data (e.g., intoxication metrics, signal values, etc.) to a server (e.g., remote server, cloud-based server, etc.) or other remote system (e.g., user device 260) for any or all of: further processing, association with user data stored at the server, storage of data, or any other suitable process.
In a first variation, Block S120 includes estimating a peak intoxication metric reached during a drinking session. Estimating the peak intoxication metric can include estimating the peak BAC value, the peak TAC value, and the peak of any other suitable value related to intoxication. Estimating the peak can include interpolating, extrapolating, modeling, directly measuring, and/or any other suitable technique for determining the peak value. For example, Block S120 can include interpolating between values in the set of samples collected over the time period of the drinking session to evaluate a continuous curve of BAC or TAC values in which the peak value resides. Interpolating in accordance with this and other examples can be performed according to a linear interpolation model, a quadratic interpolation model, a piecewise cubic interpolation model, a nonlinear model for intoxication metric dynamics over time, and any other suitable technique for interpolation.
In a second variation, Block S120 includes receiving a set (e.g., 20, greater than 2, between 2 and 1000, greater than 1000, etc.) of electrical signals (e.g., current values) from a sensor of an alcohol sensing device, the set of electrical signals determined based on a set of samples; averaging the values of the set of signals to determine an averaged value; syncing the alcohol sensing device with a user device after receiving the set of signals; transmitting the averaged value to the user device; checking for redundancy between the averaged value and previously received averaged values; eliminating redundant values; determining an intoxication metric based the averaged value; and updating an intoxication curve.
4.3 Method: Providing a Notification S130
Block S130 includes: providing a notification to the user and/or another entity. The notification is preferably determined based on the intoxication metric, but can additionally or alternatively be determined based on detecting that the device has been removed from the user and/or is on another individual, and/or based on any other sensor information. Block S130 functions to inform the user of the user's level of intoxication and/or consequential information pursuant to the user's level of intoxication. Rendering information can be considered as providing a notification irrespective of whether the notification is in response to a trigger or otherwise suitably generated (e.g., persistent notification and rendering data at a client application executing on a mobile device of the user can be considered substantially equivalent).
The notification can include any or all of: an audio notification (e.g., through a speaker of a user device, through a speaker of the alcohol sensing device, etc.), visual notification (e.g., as shown in
A visual notification can include one or more graphical representations of a set of one or more intoxication metrics (e.g., an intoxication metric curve), a progress bar (e.g., indicating number of drinks consumed, percentage of peak intoxication reached, percentage of time left until sober, etc.), a total amount of alcohol consumed (e.g., as illustrated in a visual showing number of drinks and/or volume of alcohol, as illustrated in a visual indicating the types of drinks consumed, as shown in a glass or bottle outline that gets filled up on screen, as shown in a color flush across screen, a predicted number of drinks consumed and/or a timing of drinks consumed, etc.), a type of alcohol consumed (e.g., shots vs. beer vs. wine vs. cocktails), a timing of drinking (e.g., when user starts and stops a drinking event, when individual drinks are consumed, etc.), and/or any other suitable visual. In some examples, the visual notification can include extrapolated (e.g., nonlinear extrapolation) and or predicted regions of an intoxication curve (e.g., a curve with a predicted peak based on historical data for user). Additionally or alternatively, the visual input can include and/or be based on a current slope of an intoxication curve, a user input (e.g., number of drinks planned to be consumed, etc.), or any other suitable information. In another example, a visual notification in the form of a color indication, such as the activation of a light emitter (e.g., green light emitter for sober and red light emitter for intoxication above legal limit) can be provided. The light emitter can be a point source, a light pipe (e.g., forming the wristband of the system 200), a display, or any other suitable light emitter. Providing color indications indicating “drunkenness” (binary drunkenness or degree of drunkenness) at a user wristband, for instance, could be useful in an event (e.g., concert) setting, where all the attendees have wristbands indicating their intoxication.
The notification (e.g., type, timing, etc.) is preferably determined based on one or more intoxication metrics, but can additionally or alternatively be determined based on any or all of: user historical data (e.g., previous intoxication peak, duration of time user spends at a particular bar, etc.), behavioral data, biological data (e.g., notification requesting that user wipe of off sweat prior to subsequent sampling, etc.), detection of an adjustment in settings to the system (e.g., indicating that it is not being worn by the proper user), or any other suitable data.
In some variations, for instance, one or more notifications are determined and/or triggered based on an adjustment parameter (e.g., length of wristband, eyelet being used to close wristband, tightness, etc.) associated with a transdermal system worn by the user and/or a detection that the system is not being worn by the intended user and/or is being taken off of the intended user and/or is being worn by another user. These parameters can include any or all of the following parameters (and/or any described above): a length parameter (e.g., length of wristband relative to a closure component, eyelet/hole at which device is fastened, etc.); a stress and/or tension and/or strain in a wristband or other fastener or garment; an electrical parameter (e.g., resistance, voltage, current, etc.); a feature of the user used to locate the system (e.g., surface texture of user's skin at a predetermined location of device, skin temperature, moisture of user's skin, etc.); and/or any other suitable parameters.
The notifications can include, for instance, any or all of: a reminder to put the device back on; a time limit (e.g., and a timer) with which to put the device back on; a request to provide information (e.g., evidence that the device is on the proper user such as a photo and/or video); a request to provide an additional sample (e.g., at a breathalyzer); a notification to re-position, tighten, and/or loosen a wristband or other garment; a request to recalibrate a device; and/or any other suitable information.
Additional or alternative to notifications, any other suitable actions can be triggered based on any suitable information (e.g., intoxication metric, adjustment parameter, etc.), such as any or all of: turning on of a camera (e.g., on the device, on a user device, etc.); calling the user; calling a family member of the user; initiating the checking of whether or not the device is coupled to the user (e.g., at a later time, at a predetermined frequency, etc.); and/or any other suitable actions.
In some variations, a notification is sent to the user and/or other entity (e.g., remote monitoring and/or criminal justice entity) to alert them that they should recalibrate and/or replace a sensor of the device. This can be based on any or all of: a time since last calibration and/or replacement (e.g., in number of days, weeks, months, years, etc.; in number of uses of the sensor; in a duration of time used; in an amount of data collected with the sensor; etc.); the detected signals (e.g., and determining that they are outside of the norm; that they exceed a threshold; that they do not reach a minimum threshold; that an intoxication curve is outside of an expected shape and/or range of parameters such as slope, maximum, minimum, range, etc.); supplementary information (e.g., determining that the user has been in a humid region; determining that the user has been in a hot region; determining that the user has been in a cold region; etc.); based on input from the user (e.g., noting wear on the device; indicating that the device and/or sensor has been damaged; etc.); and/or based on any other suitable information. The information can be received from any or all of: the device itself (e.g., onboard sensors, onboard memory/storage, onboard processing system, etc.); the user device (e.g., from a weather application, based on a user's location, etc.); another computing system and/or database (e.g., remote computing system, separate local computing system, etc.); a remote monitoring entity; and/or any other suitable source(s).
The notification can optionally guide the user (e.g., with a set of instructions, with a series of notifications, with a set of images, with a digital presentation, with a video, with an audio recording, with a call and/or teleconference with a support person, etc.) and/or other entity into any or all of: recalibrating the device; replacing the sensor; replacing the device; and/or any other suitable processes.
A notification and/or any combination of notifications can be sent to any or all of: a user (e.g., at the device, at a client application executing on a user device, etc.) such as the wearer of the wristband and/or any individual (e.g., involved in the user's care, family member, friend, etc.); a remote monitoring entity (e.g., probation officer, family member, monitoring account associated with the user account of the user, etc.); a computing system and/or memory/storage; any other destination; a server (e.g., remote server); a database; and/or any combination.
In some variations, for instance, one or more notifications can be configured for the remote monitoring (e.g., probation, sobriety, rehabilitation, etc.) of the user and sent to and/or accessible by a remote monitoring entity (e.g., probation officer, family member of user, etc.). These can also and/or instead be delivered to any suitable individual and/or entity. These notifications can include any or all of the notifications described above and/or any suitable notifications. In specific examples, for instance, notifications related to the detection and/or monitoring of a drinking event can be conveyed to a remote monitoring entity associated with the user. These can include any or all of: visual notifications, audio notifications, and/or any or all of the notification types described above. This can be particularly valuable for remote monitoring, which would want to know if the user drinks and how the drinking is progressing at various different times and frequency throughout the drinking event. In specific examples, upon detection that a drinking event has occurred (e.g., based on TAC values, based on other sensor information, etc.), a TAC intoxication curve and/or a BAC intoxication curve (e.g., individually, overlaid together, etc.) can be sent to a remote monitoring entity, such that the recipient can be how the curve(s) rise and fall. The notification(s) can include any or all of: an alert, updates (e.g., at a predetermined frequency, when threshold limits are reached, etc.), a visual of an intoxication curve being generated in real-time and/or substantially real time, a visual of an entire completed intoxication curve (e.g., upon detecting that the user has stopped drinking), a graph and/or plot, a piecewise intoxication curve and/or graph (e.g., after a predetermined interval of time has passed), a predicted curve and/or parameter (e.g., time until sober, number of drinks consumed, number of drinks expected to be consumed, etc.), a parameter associated with an intoxication curve (e.g., maximum slope, slope at multiple intervals of time, maximum intoxication and/or predicted maximum intoxication, etc.), and/or any other suitable information. In some embodiments, for instance, a remote monitoring entity might want to know something associated with how steep the intoxication curve and be regularly updated on it, such as known how steep the curve is in the 1st hour and how the slope progresses at predetermined time intervals (e.g., every 30 minutes) after. This can include, for instance, transmitting a drinking episode visual at the predetermined time intervals to show whether or not the person is sobering up. In additional or alternative embodiments, the method can include detecting when a parameter associated with the intoxication of the user (e.g., TAC value, BAC value, slope of intoxication curve, etc.) is greater than a predetermined threshold, and triggering the system to pull any data below or above that threshold in a predetermined time period (e.g., 2-hour period). Additionally or alternatively, any other notifications can be determined and transmitted.
Block S130 can include rending one or more notifications at a display of a user device (e.g., mobile device) associated with the user; the user device can, in variations, be the transdermal alcohol sensing device (e.g., a smartwatch including the TAC sensor and a display), a separate device (e.g., the user's smartphone, the user's laptop, etc.), a web page, and any other suitable device or location. Block S130 can additionally or alternatively include providing the notification without rendering the notification (e.g., via a text message, via a phone call, via an audio output, via a haptic output, etc.). In variations, Block S130 can include rendering any suitable information in relation to the intoxication metric and/or the set of samples indicative thereof at a display of a mobile device of the user, as shown by example in
Block S130 can additionally or alternatively include providing one or more notifications at the alcohol sensing device, such as through one or more light emitters, speakers, vibration motors, or any other suitable outputs.
Block S130 can include providing a plurality of notifications, at one or more mobile devices. The plurality of notifications can be provided independently and/or in conjunction; for example, as shown in
Block S130 can optionally include providing one or more notifications for the purposes of social applications; this can include, for instance, inviting contacts out for a night out upon determining that the user is drinking at a bar.
Block S130 can include rendering a time series of values selectable between a TAC display mode and a BAC display mode. For example, as shown in
In relation to Block S130, time series values can be rendered such that error bars (e.g., based on measurement error, sensitivity analyses, the measurement method or system, etc.) are rendered in conjunction with the measured values of TAC and/or determined values of BAC. For example, as shown in
Block S130 can include providing a notification to the user based on contextual data (e.g., determined in Block S150 as described below). For example, Block S130 can include rendering a curve of skin temperature values versus time at a display of a mobile device of the user, as shown in
Block S130 can include providing notifications to a user through a client application executing on a user device in communication with an alcohol sensing device. The client application preferably can also receive one or more inputs from the user, as well as optionally interact with other client applications executing on the user device (e.g., scheduling applications, ride share applications, user information applications, weather applications, etc.). The integration of this client application with other client applications can function to trigger notifications on the other applications and/or receive notifications at the client application from the other applications. These other applications can be configured to include any or all of: time information (e.g., time of day, day of week, etc.), calendar information (e.g., general calendar information, user-specific calendar information, etc.), location information (e.g., GPS data, user location, name of bar at which user is located, etc.), information related to the user's location (e.g., bar's business hours, type of alcohol served, etc.), payment information (e.g., knowledge that user has purchased a particular drink), transportation information (e.g., through a ride-sharing application), or any other suitable information.
In one variation, S130 includes prompting a user to use a ride share application (e.g., through a notification at a ride share application, through a test message, by opening the ride share application, etc.), which can be initiated in response to any or all of: determining that a user has reached a predetermined intoxication threshold, determining that a time until sober is later than a bar closing time, or any other suitable information.
Block S130 can optionally provide notifications based on a schedule of a user (e.g., as indicated in a calendar application of the user, as input by the user into the client application, etc.). Additionally or alternatively, a user schedule can be updated based on the intoxication metric. Having access to a user schedule can function, for instance, to plan a user's night out, provide instructions to a user to enable them to follow their schedule (e.g., stop drinking now to be able to drive home at a predetermined time point, call a cab instead of driving home, wait an hour before your next drink to maintain a buzz and not reach a particular intoxication peak, drink a glass of water, etc.).
The notification can optionally be correlated with one or more health metrics of the user, such as—but not limited to—sleep quality (e.g., indicating that a user's drinking session has impacted or will impact the user's sleep quality), a hangover likelihood and/or predicted severity, a user weight change or overall weight, an exercise or workout (e.g., indicating when a user should perform a workout), overall nutrition, or other area of the user's health.
Block S130 can include Block S135, which includes receiving user input related to notification provision. Block S135 functions to receive input from the user that define the user's desired notification parameters. For example, as shown in
In a specific example, receiving user input in accordance with Block S135 includes receiving a unique signature emitted by the alcohol sensing device. The unique signature is preferably received by a second device (e.g., at a sensor of a mobile device associated with the user that is distinct from the alcohol sensing device as shown in
In another specific example, Block S135 includes receiving a block list of entities, and preventing contact of the entities on the block list (e.g., ex-partners, coworkers, etc.). Contact prevention is preferably performed in cases wherein the user's intoxication metric exceeds a threshold value (e.g., a BAC of 0.0, a TAC of 0.01, a BAC of 0.10, etc.), but can additionally or alternatively be performed based on alternative metrics (e.g., temporal metrics, including preventing contact between predetermined hours of the day according to a schedule) and/or combinations of alternative metrics and intoxication metrics. Preventing contact can include disabling features of the user's mobile device that facilitate contact (e.g., calling features, text messaging features, internet navigation features, etc.) in a general (e.g., globally limiting mobile device functionality) and/or specific (e.g., in relation to solely those entities on the block list) manner. Preventing contact can additionally or alternatively include providing a suggestion to the user that the user desist from contacting the entities on the block list (e.g., as shown in
4.4 Method: Modifying Operation of the Transdermal Alcohol Sensing Device Based on the Intoxication Metric S140
The method can include Block S140, which includes: modifying operation of the transdermal alcohol sensing device based on the intoxication metric. Block S140 functions to optimize alcohol sensing device operation based on measured and/or derived data (e.g., the set of samples and/or the intoxication metric, respectively).
As shown in
4.5 Method: Determining Contextual Data S150
The method can include Block S150, which includes: determining contextual data. Block S150 functions to determine data that can be used to augment the determination of the intoxication metric (e.g., in accordance with Block S120). For example, Block S150 can include measuring skin temperature values at a contact temperature sensor of the transdermal alcohol monitoring device.
Block S150 can include determining correlations between alcohol consumption and other health metrics (e.g., sleep quality, weight, exercise, diet, heart rate, blood pressure, hangover symptoms, behavior characteristics, etc.) and presenting data about the other health metrics and/or the correlations to a user (e.g., at a user device, at the alcohol sensing system) determined as and/or by way of contextual data.
4.6 Method: Hydrating the Transdermal Alcohol Sensing Device
The method 100 can optionally include hydrating a transdermal alcohol sensing device, which functions to keep the sensor of the transdermal alcohol sensing device function properly (e.g., such that the sensor can properly adsorb the sample, to wash off prior sample residue, etc.). Hydrating can include any or all of: wetting a membrane of the sensor with a fluid (e.g., water), applying active humidification, active or passive application of a liquid to a membrane or surface of the sensor (e.g., through wicking, capillary action, pressure, vacuum, etc.), capping the sensor (e.g., at the inlet) in between uses, or any other process.
In one variation, hydrating includes moistening a membrane of the sensor at a predetermined interval of time (e.g., every two months).
Blocks of the method 100 can be repeated in order to build out a database of sensor data, in a similar manner as described above in relation to data aggregation. Furthermore, Blocks of the method 100 can be repeated over time for an individual user and/or multiple users, in order to generate models that describe longitudinal behavior (e.g., of a user's intoxication state) over time, as described in relation to the machine learning models and training data described above.
Furthermore, in relation to repetition of blocks of the method 100, each instance of sample provision can be performed without re-establishment of a baseline test result. For instance, if there is residual alcohol interacting with a sensor in association with sample provision and analysis, Blocks of the method 100 can be used to account for residual alcohol effects, such that the individual does not have to wait for an extended period of time between subsequent instances of sample provision.
However, the method 100 can include any other suitable blocks or steps, some embodiments, variations, and examples of which are described in in U.S. application Ser. No. 15/294,317 filed on 14 Oct. 2016, U.S. application Ser. No. 14/470,376 filed 27 Aug. 2014, U.S. application Ser. No. 14/602,919, and U.S. application Ser. No. 15/205,876, which are each incorporated herein in their entireties by this reference. For example, the system 200 can include an output (e.g., optical output, such as a light emitter or electronic display; audio output; etc.) operable to output a unique signature, and the method 100 can include acquiring sensor data including a photograph or video displaying the user wearing the system 200 and including the unique signature (e.g., in the photograph or video), an example of which is shown in
The method 100 can additionally or alternatively include any other suitable blocks or steps configured to facilitate use of data to provide more dynamic and accurate information related to intoxication test results. Furthermore, as a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the method 100 without departing from the scope of the method 100.
In one variation of the method, the method 100 includes: receiving a set of ethanol samples from a user at an inlet of a transdermal wristband device (e.g., as shown in
In a second variation of the method used in remote monitoring (e.g., as shown in
Additionally or alternatively, the device can be other than a wristband device (e.g., anklet).
The preferred embodiments include every combination and permutation of the various system components and the various method processes. Furthermore, various processes of the preferred method can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the system and one or more portions of the electronics subsystem 150. The computer-readable medium can be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processing subsystem, but any suitable dedicated hardware device or hardware/firmware combination device can additionally or alternatively execute the instructions.
The FIGURES illustrate the architecture, functionality and operation of possible implementations of systems, methods and computer program products according to preferred embodiments, example configurations, and variations thereof. In this regard, each block in the flowchart or block diagrams may represent a module, segment, step, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block can occur out of the order noted in the FIGURES. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application is a continuation of U.S. application Ser. No. 17/033,501, filed 25 Sep. 2020, which is a continuation-in-part of U.S. application Ser. No. 16/362,444, filed 22 Mar. 2019, which claims the benefit of U.S. Provisional Application Ser. No. 62/646,706, filed 22 Mar. 2018, which are each incorporated in their entirety by this reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3560010 | Hohwart | Feb 1971 | A |
| 3824538 | Slemp | Jul 1974 | A |
| 4487055 | Wolf | Dec 1984 | A |
| 4738333 | Collier et al. | Apr 1988 | A |
| 4749553 | Lopez et al. | Jun 1988 | A |
| 4902628 | Blair | Feb 1990 | A |
| 4914038 | Jewitt | Apr 1990 | A |
| 4996161 | Conners et al. | Feb 1991 | A |
| 5157601 | Jones et al. | Oct 1992 | A |
| D333441 | Greene | Feb 1993 | S |
| 5216415 | Ono et al. | Jun 1993 | A |
| 5220919 | Phillips et al. | Jun 1993 | A |
| 5291898 | Wolf | Mar 1994 | A |
| 5416468 | Baumann | May 1995 | A |
| 5426415 | Prachar et al. | Jun 1995 | A |
| 5433863 | Braden et al. | Jul 1995 | A |
| D362642 | Howse | Sep 1995 | S |
| D381885 | Lane | Aug 1997 | S |
| 5944661 | Swette et al. | Aug 1999 | A |
| 6026674 | Gammenthaler | Feb 2000 | A |
| 6075444 | Sohege et al. | Jun 2000 | A |
| 6433863 | Weiss | Aug 2002 | B1 |
| 6454723 | Montagnino | Sep 2002 | B1 |
| 6556905 | Mittelsteadt et al. | Apr 2003 | B1 |
| 6608399 | McConnell et al. | Aug 2003 | B2 |
| 6726636 | Der et al. | Apr 2004 | B2 |
| 6748792 | Freund et al. | Jun 2004 | B1 |
| 6824520 | Orr et al. | Nov 2004 | B2 |
| 6853956 | Ballard et al. | Feb 2005 | B2 |
| 6858182 | Ito et al. | Feb 2005 | B1 |
| 6899683 | Mault et al. | May 2005 | B2 |
| 6956484 | Crespo | Oct 2005 | B2 |
| 6958691 | Anderson et al. | Oct 2005 | B1 |
| D521885 | Eddy et al. | May 2006 | S |
| D530424 | Manser et al. | Oct 2006 | S |
| D539683 | Shaw et al. | Apr 2007 | S |
| D539684 | Kitamura et al. | Apr 2007 | S |
| 7204335 | Stewart et al. | Apr 2007 | B2 |
| 7256700 | Ruocco et al. | Aug 2007 | B1 |
| 7311665 | Hawthorne et al. | Dec 2007 | B2 |
| 7341693 | Der et al. | Mar 2008 | B2 |
| 7451852 | Stewart et al. | Nov 2008 | B2 |
| 7462149 | Hawthorne et al. | Dec 2008 | B2 |
| D586677 | Nothacker et al. | Feb 2009 | S |
| D603281 | Gonzalez | Nov 2009 | S |
| 7611461 | Hawthorne et al. | Nov 2009 | B2 |
| 7611611 | Belt | Nov 2009 | B2 |
| D606434 | Castrodale et al. | Dec 2009 | S |
| 7636047 | Sempek | Dec 2009 | B1 |
| 7641611 | Hawthorne et al. | Jan 2010 | B2 |
| 7823681 | Crespo et al. | Nov 2010 | B2 |
| 7930927 | Cooper et al. | Apr 2011 | B2 |
| 7934577 | Walter et al. | May 2011 | B2 |
| 8040233 | Adappa et al. | Oct 2011 | B2 |
| 8078334 | Goodrich | Dec 2011 | B2 |
| 8126735 | Dicks et al. | Feb 2012 | B2 |
| 8165824 | Iiams et al. | Apr 2012 | B2 |
| 8240419 | Zimmermann et al. | Aug 2012 | B2 |
| 8258968 | Ghazarian et al. | Sep 2012 | B2 |
| 8280436 | Harris | Oct 2012 | B2 |
| 8317697 | Hawthorne et al. | Nov 2012 | B2 |
| 8359901 | Freund et al. | Jan 2013 | B2 |
| 8370027 | Pettersson et al. | Feb 2013 | B2 |
| 8381573 | Keays | Feb 2013 | B2 |
| 8453492 | Tsuzuki et al. | Jun 2013 | B2 |
| 8466796 | Mejia et al. | Jun 2013 | B1 |
| 8505360 | Ruocco et al. | Aug 2013 | B2 |
| 8525668 | Alouani et al. | Sep 2013 | B1 |
| 8549318 | White et al. | Oct 2013 | B2 |
| 8590364 | Lopez et al. | Nov 2013 | B2 |
| 8657744 | Rompa et al. | Feb 2014 | B2 |
| 8693597 | Sexton et al. | Apr 2014 | B2 |
| 8707758 | Keays | Apr 2014 | B2 |
| D705100 | Nothacker et al. | May 2014 | S |
| 8808228 | Brister et al. | Aug 2014 | B2 |
| 8814804 | Walden et al. | Aug 2014 | B2 |
| 8844337 | Kountotsis et al. | Sep 2014 | B2 |
| 8849387 | Gilbert et al. | Sep 2014 | B2 |
| 8862152 | Buchholz et al. | Oct 2014 | B1 |
| 8878669 | Nothacker et al. | Nov 2014 | B2 |
| 8899748 | Migdal | Dec 2014 | B1 |
| 8920725 | Withrow et al. | Dec 2014 | B2 |
| 8941501 | Debijl | Jan 2015 | B1 |
| 8957771 | Arringdale et al. | Feb 2015 | B2 |
| D724980 | Nothacker et al. | Mar 2015 | S |
| D727763 | Nothacker et al. | Apr 2015 | S |
| D727764 | Nothacker et al. | Apr 2015 | S |
| 9011657 | Parselle et al. | Apr 2015 | B2 |
| 9020773 | Son et al. | Apr 2015 | B2 |
| D731341 | Kobayakawa | Jun 2015 | S |
| 9045101 | Phelan | Jun 2015 | B2 |
| 9063120 | Park | Jun 2015 | B2 |
| 9076317 | Nothacker et al. | Jul 2015 | B2 |
| 9095251 | Purks et al. | Aug 2015 | B2 |
| 9192324 | Phillips et al. | Nov 2015 | B2 |
| 9192334 | Nothacker et al. | Nov 2015 | B2 |
| 9228997 | Keays | Jan 2016 | B2 |
| 9239323 | Keays | Jan 2016 | B2 |
| 9241659 | Rompa et al. | Jan 2016 | B2 |
| 9241661 | Shnaper et al. | Jan 2016 | B2 |
| 9250228 | Nothacker et al. | Feb 2016 | B2 |
| 9278696 | Yi et al. | Mar 2016 | B2 |
| 9301719 | Abreu | Apr 2016 | B2 |
| 9398858 | Phillips et al. | Jul 2016 | B2 |
| 9417232 | Keays et al. | Aug 2016 | B2 |
| 9442103 | Goad | Sep 2016 | B1 |
| 9481245 | Nelson | Nov 2016 | B2 |
| 9489487 | Hawthorne et al. | Nov 2016 | B2 |
| 9609921 | Feinstein | Apr 2017 | B1 |
| 9643186 | Ahmad et al. | May 2017 | B1 |
| 9662065 | Nothacker et al. | May 2017 | B2 |
| 9746456 | Keays | Aug 2017 | B2 |
| 9781984 | Baranski et al. | Oct 2017 | B2 |
| 9788772 | Nothacker et al. | Oct 2017 | B2 |
| 9820114 | Greenhut et al. | Nov 2017 | B2 |
| 9829480 | Wojcik et al. | Nov 2017 | B2 |
| 9848815 | Abreu | Dec 2017 | B2 |
| 9855000 | Lansdorp et al. | Jan 2018 | B2 |
| 9867539 | Heikenfeld et al. | Jan 2018 | B2 |
| 9872649 | Nothacker et al. | Jan 2018 | B2 |
| 9881997 | Sakata et al. | Jan 2018 | B2 |
| 9915644 | Nothacker et al. | Mar 2018 | B2 |
| 9922508 | Keays et al. | Mar 2018 | B2 |
| 10040349 | Devries et al. | Aug 2018 | B2 |
| 10182752 | Nothacker et al. | Jan 2019 | B2 |
| 10352923 | Nothacker et al. | Jul 2019 | B2 |
| 10631767 | Nothacker et al. | Apr 2020 | B2 |
| 10987038 | Nothacker et al. | Apr 2021 | B2 |
| 11278222 | Moeller et al. | Mar 2022 | B2 |
| 11324449 | Nothacker et al. | May 2022 | B2 |
| 11646120 | Nothacker et al. | May 2023 | B2 |
| 20020008966 | Fjelstad et al. | Jan 2002 | A1 |
| 20020084130 | Der et al. | Jul 2002 | A1 |
| 20020089660 | Weiss | Jul 2002 | A1 |
| 20020128769 | Der et al. | Sep 2002 | A1 |
| 20020140289 | McConnell et al. | Oct 2002 | A1 |
| 20020143267 | Montagnino | Oct 2002 | A1 |
| 20030028120 | Mault et al. | Feb 2003 | A1 |
| 20030116159 | Orr et al. | Jun 2003 | A1 |
| 20030117287 | Crespo | Jun 2003 | A1 |
| 20030176803 | Gollar | Sep 2003 | A1 |
| 20030177119 | Cole | Sep 2003 | A1 |
| 20030208110 | Mault et al. | Nov 2003 | A1 |
| 20040233058 | Dodds | Nov 2004 | A1 |
| 20040233061 | Johns | Nov 2004 | A1 |
| 20040236199 | Hawthorne et al. | Nov 2004 | A1 |
| 20040242976 | Abreu | Dec 2004 | A1 |
| 20050053523 | Brooke | Mar 2005 | A1 |
| 20050184870 | Galperin et al. | Aug 2005 | A1 |
| 20050241871 | Stewart et al. | Nov 2005 | A1 |
| 20060182661 | Aquila | Aug 2006 | A1 |
| 20060193749 | Ghazarian et al. | Aug 2006 | A1 |
| 20060217624 | Myklebust et al. | Sep 2006 | A1 |
| 20060217625 | Forrester | Sep 2006 | A1 |
| 20060237252 | Mobley et al. | Oct 2006 | A1 |
| 20060237253 | Mobley et al. | Oct 2006 | A1 |
| 20060282344 | Brown | Dec 2006 | A1 |
| 20060293613 | Fatehi et al. | Dec 2006 | A1 |
| 20070024454 | Singhal | Feb 2007 | A1 |
| 20070093725 | Shaw | Apr 2007 | A1 |
| 20070107728 | Ricciardelli et al. | May 2007 | A1 |
| 20070144812 | Stewart et al. | Jun 2007 | A1 |
| 20070296601 | Sultan et al. | Dec 2007 | A1 |
| 20080045806 | Keppler | Feb 2008 | A1 |
| 20080097793 | Dicks et al. | Apr 2008 | A1 |
| 20080169924 | Belden | Jul 2008 | A1 |
| 20080183388 | Goodrich | Jul 2008 | A1 |
| 20080216561 | Cooper et al. | Sep 2008 | A1 |
| 20080262469 | Brister et al. | Oct 2008 | A1 |
| 20090043409 | Ota | Feb 2009 | A1 |
| 20090090577 | Takahashi et al. | Apr 2009 | A1 |
| 20090111486 | Burstrom | Apr 2009 | A1 |
| 20090164141 | Lee | Jun 2009 | A1 |
| 20090182216 | Roushey et al. | Jul 2009 | A1 |
| 20090187111 | Reilly et al. | Jul 2009 | A1 |
| 20090201138 | Ghazarian et al. | Aug 2009 | A1 |
| 20090212957 | Burris | Aug 2009 | A1 |
| 20090309711 | Adappa et al. | Dec 2009 | A1 |
| 20100010689 | Yasushi et al. | Jan 2010 | A1 |
| 20100012417 | Walter et al. | Jan 2010 | A1 |
| 20100036592 | Osaki et al. | Feb 2010 | A1 |
| 20100108425 | Crespo et al. | May 2010 | A1 |
| 20100121502 | Katayama et al. | May 2010 | A1 |
| 20100152976 | White et al. | Jun 2010 | A1 |
| 20100234064 | Harris | Sep 2010 | A1 |
| 20100268425 | Pettersson et al. | Oct 2010 | A1 |
| 20100274411 | Ozaki | Oct 2010 | A1 |
| 20100294583 | Biondo et al. | Nov 2010 | A1 |
| 20100310011 | Sexton et al. | Dec 2010 | A1 |
| 20110079073 | Keays | Apr 2011 | A1 |
| 20110266160 | Campbell et al. | Nov 2011 | A1 |
| 20110291827 | Baldocchi et al. | Dec 2011 | A1 |
| 20110304465 | Boult et al. | Dec 2011 | A1 |
| 20110308297 | Tsuzuki et al. | Dec 2011 | A1 |
| 20110309932 | Arringdale et al. | Dec 2011 | A1 |
| 20120020837 | Withrow et al. | Jan 2012 | A1 |
| 20120031165 | Ruocco et al. | Feb 2012 | A1 |
| 20120075094 | Keays | Mar 2012 | A1 |
| 20120132524 | Parselle et al. | May 2012 | A1 |
| 20120157871 | Walden et al. | Jun 2012 | A1 |
| 20120330175 | Phillips et al. | Dec 2012 | A1 |
| 20130021153 | Keays | Jan 2013 | A1 |
| 20130035602 | Gemer | Feb 2013 | A1 |
| 20130111979 | Park | May 2013 | A1 |
| 20130123570 | Ly et al. | May 2013 | A1 |
| 20130150727 | Phillips et al. | Jun 2013 | A1 |
| 20130218039 | Sotos et al. | Aug 2013 | A1 |
| 20130253360 | Wang et al. | Sep 2013 | A1 |
| 20130282321 | Son et al. | Oct 2013 | A1 |
| 20130305808 | Yoo | Nov 2013 | A1 |
| 20140003676 | Baughman et al. | Jan 2014 | A1 |
| 20140012143 | Gilbert et al. | Jan 2014 | A1 |
| 20140032596 | Fish et al. | Jan 2014 | A1 |
| 20140052567 | Bhardwaj et al. | Feb 2014 | A1 |
| 20140059066 | Koloskov | Feb 2014 | A1 |
| 20140062703 | Purks et al. | Mar 2014 | A1 |
| 20140062722 | Ofir et al. | Mar 2014 | A1 |
| 20140086590 | Ganick et al. | Mar 2014 | A1 |
| 20140165697 | Mochizuki et al. | Jun 2014 | A1 |
| 20140165698 | Mochizuki et al. | Jun 2014 | A1 |
| 20140188398 | Cohen et al. | Jul 2014 | A1 |
| 20140204334 | Stoll | Jul 2014 | A1 |
| 20140210627 | Nothacker et al. | Jul 2014 | A1 |
| 20140234172 | Burgi et al. | Aug 2014 | A1 |
| 20140240132 | Bychkov | Aug 2014 | A1 |
| 20140273858 | Panther | Sep 2014 | A1 |
| 20140281523 | Golino | Sep 2014 | A1 |
| 20140303836 | Phelan | Oct 2014 | A1 |
| 20140311215 | Keays et al. | Oct 2014 | A1 |
| 20140361900 | Nothacker et al. | Dec 2014 | A1 |
| 20140365142 | Baldwin | Dec 2014 | A1 |
| 20140371603 | Fujita et al. | Dec 2014 | A1 |
| 20150084774 | Wojcik et al. | Mar 2015 | A1 |
| 20150164416 | Nothacker et al. | Jun 2015 | A1 |
| 20150251660 | Nelson | Sep 2015 | A1 |
| 20150325104 | Greenhut et al. | Nov 2015 | A1 |
| 20150359469 | Jacobs et al. | Dec 2015 | A1 |
| 20150360696 | Yi et al. | Dec 2015 | A1 |
| 20160021228 | Roberts | Jan 2016 | A1 |
| 20160284200 | Song et al. | Sep 2016 | A1 |
| 20160324442 | Zdeblick | Nov 2016 | A1 |
| 20160338627 | Lansdorp et al. | Nov 2016 | A1 |
| 20170079574 | Rodriguez Restrepo et al. | Mar 2017 | A1 |
| 20170086714 | Nothacker et al. | Mar 2017 | A1 |
| 20170086743 | Bushnell | Mar 2017 | A1 |
| 20170103166 | Oh et al. | Apr 2017 | A1 |
| 20170231571 | Rogers et al. | Aug 2017 | A1 |
| 20170303819 | Nothacker et al. | Oct 2017 | A1 |
| 20170313189 | Walter et al. | Nov 2017 | A1 |
| 20170354354 | Nothacker et al. | Dec 2017 | A1 |
| 20180085058 | Chakravarthi et al. | Mar 2018 | A1 |
| 20180086264 | Pedersen | Mar 2018 | A1 |
| 20180164285 | Nothacker et al. | Jun 2018 | A1 |
| 20180184920 | Rabinovich | Jul 2018 | A1 |
| 20180209955 | Moeller | Jul 2018 | A1 |
| 20180263538 | Heikenfeld et al. | Sep 2018 | A1 |
| 20190246958 | Moeller et al. | Aug 2019 | A1 |
| 20190290197 | Nothacker et al. | Sep 2019 | A1 |
| 20200101982 | Bowers et al. | Apr 2020 | A1 |
| 20200124589 | Gonzales | Apr 2020 | A1 |
| 20220192597 | Feldman | Jun 2022 | A1 |
| 20220240849 | Spector et al. | Aug 2022 | A1 |
| 20230138641 | Graham et al. | May 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2975522 | Nov 2012 | FR |
| 100673261 | Jan 2007 | KR |
| Entry |
|---|
| Kim, J et al. Noninvasive alcohol monitoring using a wearable tattoo-based iontophoretic-biosensing system. ACS Sensors. Jul. 12, 2016. vol. 1. No. 8; abstract. |
| Kuswandi, B et al. A simple visual ethanol biosensor based on alcohol oxidase immobilized onto polyaniline film for halal verification of fermented beverage samples. Sensors. 2014. vol. 14. No. 2; p. 2144, figure 6. |
| STIC Search Results. 15205876-528781-Search Results.pdf. |
| Zettl, Robert J., “The Determination of Blood Alcohol Concentration by Transdermal Measurement”, Commissioned by Alcohol Monitoring Systems, Inc., Highlands Ranch, Colorado, Jul. 2002, 13 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220287641 A1 | Sep 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62646706 | Mar 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17033501 | Sep 2020 | US |
| Child | 17714745 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16362444 | Mar 2019 | US |
| Child | 17033501 | US |
