There are thousands of hospitals across the U.S. Many of these hospitals are community or rural hospitals. These community or rural hospitals conventionally are part of a hospital system or network. An example of one such network includes several community hospitals with one major tertiary hospital. A community or rural hospital outside of any large hospital network would typically contract with a large tertiary hospital for emergent and intensive-care solutions outside of the areas of expertise of the community or rural hospital.
Electroencephalogram (EEG) monitoring is conventionally only available in the large tertiary hospitals that support a neurology department with an EEG service. Many hospitals do not offer EEG monitoring. These hospitals make arrangements with larger tertiary hospitals or their partners when such monitoring is required or desirable for patients. This conventionally takes the form of a referral of the patient to the tertiary hospital for expert of specialist services. Often this includes travel or transport of the patient to the tertiary hospital for services.
In summary, one embodiment provides a method, comprising: obtaining EEG data from one or more single-channel EEG sensor worn by a user; classifying, using a processor, the EEG data as one of nominal and abnormal; and providing an indication associated with a classification of the EEG data.
Another embodiment provides a system, comprising: an output device; a processor operatively coupled to the output device; and a memory storing instructions executable by the processor to: obtain EEG data from one or more single-channel EEG sensor worn by a user; classify the EEG data as one of nominal and abnormal; and provide an indication associated with a classification of the EEG data.
A further embodiment provides a method, comprising: obtaining EEG data from two or more single channel EEG sensors worn by a user; transmitting the EEG data to a remote device; and providing, from the remote device to a display associated with a remote user, data comprising a montage of the EEG data.
The foregoing is a summary and thus may contain simplifications, generalizations, and omissions of detail; consequently, those skilled in the art will appreciate that the summary illustrative only and is not intended to be in any way limiting.
For a better understanding of the embodiments, together with other and further features and advantages thereof, reference is made to the following description, in conjunction with the accompanying drawings.
It will be readily understood that the components of the embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations in addition to the described example embodiments. Thus, the following more detailed description of the example embodiments, as represented in the figures, is not intended to limit the scope of the claims, but is merely representative of those embodiments.
To optimize treatment following initial seizure diagnosis, epileptologists would ideally obtain high-quality, long-term EEG studies in the hospital with 19+-channel, wired EEG arrangement in the standard international ‘10-20’ system. Such studies can be difficult to perform because the process is prohibitively expensive, time consuming, and extremely inconvenient for patients. Additionally, the time spent in the epilepsy monitoring unit may not capture any or all seizure activity that a person normally has over long periods of time. However, optimal treatment often depends upon identifying the full extent of a patient's convulsive (clinical) and non-convulsive (sub-clinical) seizure activity. Currently a technique for collecting seizure activity history outside of the hospital is the seizure diary a home based, self-reported record that may be incomplete. Seizure diaries can be difficult to maintain accurately, and the diary can be inaccurate, making clinical decisions on appropriate pharmacological treatment difficult. Further, conventional EEG techniques do not adequately address the need for monitoring in many emergent care scenarios, particularly those encountered by emergency responders or clinicians in small or rural hospitals.
Turning now to the figures, representative example embodiments are described to provide a better understanding of the appended claims.
Referring to
In an example shown in
In an embodiment, an EEG monitoring sensor 101a is a self-contained recording patch including a first electrode and a second electrode, where the first and second electrodes cooperate to measure a voltage. The sensor 101a includes circuitry for generating an EEG signal from the measured voltage, amplifying the EEG signal, digitizing the EEG signal, and retrievably storing the EEG data in a memory. The sensor 101a may also include a power source and an enclosure that houses the circuitry, the power source, as well as the first and second electrodes, in a unitary package. The sensor 101a may be worn on the scalp, e.g., forehead or bi-parietal region, of the user to capture EEG data over a long period as the user goes about his or her regular, daily activities.
As illustrated in
By way of non-limiting example, a patient may initially receive a diagnosis of seizure activity with a location indicated, e.g., from a clinician. Thereafter, the patient may be asked to monitor for seizure activity using a sensor 101b. In an embodiment, a data source indicating a diagnosed location of seizure activity is accessed, such as an electronic medical record (EMR) or in an application that receives user input to a location map image or illustration. The location data may be supplied to the patient, e.g., via a companion mobile application that facilitates pairing and data communication between the sensor 101b and a local device. In another example, the location information is supplied to an online application that can be viewed by the user (e.g., patient or clinician). The location data may therefore be provided to the user in the form of an instruction that indicates acceptable placement(s) of the sensor(s), sensor 101b, to maximize the likelihood that a subsequent seizure will be detected using a single channel sensor, e.g., sensor 101b.
Due to the small size of the sensor 101b, for example on the order of an inch in length and width, and ½ inch in a depth dimension, the sensor 101b may be worn continuously for a period of days before it needs to be removed, e.g., for charging an on-board power source such as a rechargeable battery. This permits the capture, recording and analysis of a large amount of single channel EEG data using detection processes that identify seizures, including seizures a user wearing the sensor may not consciously know they are having, such as seizures that occur while sleeping.
The sensors 101a, 101b illustrated in
A consideration in making the sensor 101a, 101b a viable, long-term wearable sensor is power consumption. An example target is approximately three days of operation without recharging the sensor 101a, 101b. To enable continued monitoring, the users may have two (or multiple) sensors 101a, 101b and will use one while the other is being recharged. Such an arrangement will allow for continuous EEG data capturing, and monitoring.
To facilitate long term wear, several techniques may be employed. For example, a power consuming operation of the sensor 101a, 101b is transmitting the EEG data from the sensor 101a, 101b to another device. To reduce the power used for data communication, the sensor 101a, 101b may transmit the captured EEG data at intervals. For example, the sensor 101a, 101b can capture EEG data for a predetermined amount of time (e.g., 6 seconds) and then transmit that captured EEG data, e.g., transmit a page or pages of EEG data. By transmitting the data at intervals, the sensor 101a, 101b only needs to activate the transmission capability for a short time (e.g., 1 second). As another example, a power-efficient microprocessor may be selected for use in the sensor. For example, certain microprocessors may include a sleep processor core or capability while transmitting data by DMA to low power SRAM for data communication. This feature may significantly reduce power consumption. Further, sensors 101a, 101b may have certain components omitted, e.g., wireless radio, and may include other components, e.g., USB or other data communication element, such as near-field or RFID, in a variety of combinations, to facilitate power conservation and adequate data transfer for the given use case. In a case where a physical communication port is included, it may be covered to prevent water or contaminating element entry, such as locating it beneath a removable hydrogel or sticker that adheres the sensor 101a, 101b to the user's skin. The thickness of the sticker may be modified, e.g., the thickness of the sticker or materials thereof (e.g., hydrogel areas) may be increased to accommodate the use context, such as placement on skin that curves, whereas a thinner sticker may be used on a relatively flat surface.
The sensors 101a, 101b are suitable for use by adults, adolescents, children and neonates. In the example of
The example of
In
As with a post-diagnosis instruction, an instruction for positioning the sensors 201 may be provided using a device 202 such as a desktop computer, tablet, other hospital monitor or mobile device, which runs an application 203 and displays an instruction as a graphic indicating placement information for the sensors 201 on the patient's scalp, e.g., on the forehead, behind the ears, a combination thereof, or other or additional locations. The placement information in this case may be generalized, e.g., approximate location for seizure monitoring in patients thought to have suffered a given type of brain injury or traumatic event, or may be customized in some fashion if access to additional data is available, e.g., specific type of incident suspected for the patient or in another clinical scenario, such as for an adult or pediatric, emergent care patient. By way of specific example, an embodiment may provide a graphical instruction such as that illustrated in
In the example illustrated in
The instructions and wireless single-channel sensors permit rapid collection and analysis (even remote analysis) in the field or in a clinical setting by non-experts. This avoids or reduces the need to transport the patient to another location, such as a larger hospital with conventional EEG monitoring equipment and specialists. For example, upon seizure suspicion, emergency department staff in a community hospital can place four sensors 201, as instructed by the graphic illustrated in
In one example, the application 203 connects to the sensors 201 through BLE, receives the EEG data, buffers the EEG data, and transmits the EEG data over WIFI to the cloud 204, where it may be retrieved and viewed by another clinician in a remote location. For example, the EEG data may be retrieved from the cloud 204 and reviewed by a remote specialist on a medical grade tablet or other device 205. This facilitates review of the EEG data as displayed in an application 206 running on the device 205. EEG data from both sensors 201 may be synchronized, e.g., by the BLE commands from the tablet 205.
The cloud device 204 may provide a server instance running EEG-review software that allows a specialist such as a neonatologist or pediatric epileptologist to log on to a tablet 205 running a mobile application 206 to view the EEG in real-time and as aEEG. The aEEG data may include indications, such as a marking described in connection with
The general principals of the example in
In an embodiment, an application, e.g., running on device 202, visually guides a user, e.g., emergent care staff, with step-by-step visuals. This may include but is not necessarily limited to guiding the user through scanning a barcode on a patient bracelet and each sensor, placing sensor(s) on the scalp, and ensuring quality signals are being recorded and relayed, to the cloud. In some embodiments, additional or reduced data may be provided. For example, EEG data may not be shown at the point-of-care, e.g., at device 202. This may be done to accommodate emergency room staff and doctors, which may consider such data display to be a distraction. In other embodiments, such data may be displayed, e.g., in connection with an alert to a specific action such as a seizure type detection, a suggested treatment or transport option, etc. Therefore, in an embodiment, the application running on device 202 may be designed to only interact with the user when there is a problem in the form of a user alert, such as poor signal quality coming from an individual sensor or the like. These user alerts are designed to indicate, e.g., flash an LED red or blue on each sensor, to staff that interaction with the application is required to guide them through solving a problem, e.g., obtain guidance to relocate or reorient a sensor as described in connection with
Collection of EEG data with one or more single-channel sensors allows EEG data to be reviewed, along with event markers (as further described herein) to quickly determine areas within the EEG data that are indicative of seizure. As further described herein, the type and nature of detection, analysis or classification the EEG data is subjected to may change depending on the use case or desired outcome. For example, for triage event marking, a model with higher false positive rate may be employed as compared to a use case in which real time seizure prediction is desired. Likewise, for in-home seizure diary use, a simple thresholding process may be suitable for producing seizure counts and markers on EEG data traces.
Referring to
In an embodiment, EEG data is obtained from a single channel EEG sensor at 301. As described herein, this may be a single sensor that is placed post-diagnosis, a single sensor that is placed pre-diagnosis, or multiple sensors used in a variety of contexts. Single sensor usage may be more appropriate for in home usage, whereas multiple sensors may be more appropriate for clinical or supervised scenarios. Each such sensor provides single channel EEG data.
The single channel EEG data is classified at 302. The classification performed at 302 may be implemented using a variety of devices. For example, the classification at 302 may be performed by the sensor, at a local device communicating with the sensor via a PAN, at a remote or cloud device communicating with the sensor via a WAN, or a suitable combination of the foregoing.
The classification performed at 302 may take a variety of forms. For example, a detection model may take the form of simple thresholding to detect brain activity over a certain amount or duration for general seizure detection. One or more models may be designed to detect specific types of brain activity known to be useful in specific clinical settings, e.g., emergent care settings as described in connection with
An embodiment uses machine learning techniques for use with single channel EEG data at 302. In an embodiment, a machine learning model may be trained using EEG data from one or more sensors, e.g., sensor 101a, in combination with other EEG data, such as collected via a wired or tethered EEG system. By way of example, two-second segments of inter-ictal (pre-seizure) and ictal (seizure) EEG data may be extracted from the sensor recordings and used to identify seizure occurrences, as further described in connection with
In an embodiment, in identifying ictal states by classifying the EEG data at 302, correlations) with additional data, such as historical data (e.g., a pattern or trend, medical record information obtained from an EMR, etc.), environmental data e.g., weather data), or a user's activity (e.g., behavioral) may be used to assist in determining the onset of seizure activity or indicating its past occurrence, as indicated at 304. For example, psychological, behavioral, and environmental cues can be identified as potential information correlative to the user's ictal (seizure) state. This additional data may optionally be used to make a classification of the EEG data or improve the confidence of an independently made classification.
By way of example, user feedback may be used to improve a seizure detecting process. Initially, an automated detection of general seizure activity may be performed at 302. If an embodiment detects general seizure activity, user supplied input may be used to improve the accuracy of the detection (e.g., with respect to time, severity or the like). For example, an input interface, such as a small button included on the sensor 101a or an input element included in a mobile application, may be used to provide an indication when a user feels that seizure activity is occurring, is about to occur or just has occurred. Likewise, an interface may allow the user to record the severity, duration, or other data regarding the event. This feedback is subjective, and it may not be desirable to use as a reliable source to determine an occurrence of seizure activity. However, user supplied data may provide insight into the user's experience of non-epileptic seizures. Therefore, it may be used to confirm a detected seizure or lack of detection. For example, repeated indications by a user that a seizure is occurring where EEG data is recorded with high quality and an automated analysis indicates no seizure may indicate that a user is experiencing something else, e.g., a non-epileptic seizure, psychological event. Conversely, such data feedback may indicate that model or threshold tuning is needed or desirable.
After the EEG data has been classified at 302, e.g., as nominal (e.g., non-seizure, pre-seizure) or abnormal (e.g., pre-seizure or seizure), an embodiment may provide outputs in the form of indications. In an embodiment EEG data, such as pre-seizure EEG data, may be classified as nominal or abnormal depending on the feature(s) being used for classification, the context (e.g., a mode may be selected where pre-seizure activity is ignored and classified as nominal in favor of a lower false positive rate, etc.), a varied threshold, etc. In an embodiment, if a seizure is detected as a result of the classification at 302, this classification may be used at 303 to provide an indication at 306 such as generating an alert (e.g., to the patient or a clinician), marking the EEG segment that triggered the detection or that is correlated with additional data, incrementing a seizure count, or forming a report.
By way of specific example, and referring to
The EEG data of two or more sensors may be displayed in various manners. As illustrated in the example of
Referring back to
The indication provided at 305 may include a forecast provided to the user, e.g., the wearer of the sensor. The indication provided at 305 may take the form of a real time forecast (e.g., produced within a second or two) that changes as the EEG data or other data 304 changes. The indication provided at 305 may take other forms, e.g., an hourly, daily, weekly or other time period forecast. Time period forecasts may be influenced by historical data accessed at 304, e.g., an increasing or decreasing trend in seizure frequency may assist in forming or modifying the forecast. The forecast may take a variety of forms, for example a score or a color displayed in a mobile application that relates to a likelihood of seizure during a time period, e.g., imminent, likelihood on a day, during the coming week, etc. Similarly, the forecast may take the form of a haptic, audio or visual effect produced by the sensor or a connected local device, remote device, etc. The forecast may also be provided to other or additional users, such as a clinician or another user. In the case of a forecast provided to a clinician, the forecast may include an indication of a related diagnosis, such as hypoxic ischemic encephalopathy, and a related action, such as a suggested treatment, e.g., therapeutic hypothermia, or an automated or semi-automated action, such as requesting a consultation with an on-call specialist.
Real-time or imminent seizure forecasting or prediction adds additional complexity in that discrimination must be made in a time sensitive manner, between an inter-ictal (no-seizure coming), a pre-ictal (seizure event will happen in the next X min/hours), and an ictal (seizure is occurring) states. Similar to seizure detection, information features and machine learning techniques have been widely tested and detailed in scientific literature with respect to seizure forecasting. Seizure forecasting success is often measured by sensitivity (was a warning correct that a seizure was corning and were any missed) and by either a false alarm rate per hour or by a “time-in-warning” (how often do warnings occur). Not everyone with epilepsy can identify a psychological, behavioral, or environmental seizure precipitating factor. Yet, over half of all people with epilepsy report at least one seizure precipitating factor. The number one seizure precipitating factor is emotional stress. This is followed by behavioral factors well known to trigger seizures, such as sleep deprivation and tiredness. Other behavioral factors include alcohol consumption, anti-seizure medication non-adherence, and physical exercise. Environmental factors such as time-of-day, flickering light, and weather (e.g., ambient temperature, relative humidity) have been shown to increase susceptibility to seizures.
As with seizure detection, seizure prediction may take the form of a classification performed at 302. Likewise, additional data such as historical, environmental or user provided data may be used to generate or modify the classification of the EEG data as nominal or abnormal. This data may be used to form forecasts or predictions provided at 305.
The additional data used to classify at 302 may include but is not limited to historical data (e.g., seizure trend data, etc.), environmental data (e.g., weather, stimulus data such as exposure to flickering light, etc. and user data (e.g., behavioral data). The user data may be provided by the user directly or indirectly. For example, the user data may be input by the user directly, such as entering in self-evaluation data to a mobile application. Non-limiting examples include stress level, sleep quality rating, sleep score according to a known scale, sleep time, etc. User or other data may be obtained indirectly, e.g., from a linked health app, from a medical record, from input of another user on another device, such as a physician, inferred from another device such as a mobile phone or smart watch providing accelerometer data, etc.
In an embodiment, an indication may take the form of a report, as indicated by way of example at 306. For example, a digital seizure diary report may be provided to the patient or clinician. Epileptologists will have a precise, quantitative record of a patient's seizure activity and that will let them know if a treatment is working, enabling them to adapt the patient's treatment more rapidly and successfully.
The improvements to a seizure detection or prediction are heavily reliant on the volume and quality of EEG data collected. Currently there exists no practical EEG database. While there are some laboratory EEG databases (e.g., MIT database), the EEG data in these databases are too clean to use for prediction as the are not representative of the quality of EEG data that will be collected in the real world. Ease of the EEG data collection will improve EEG data availability, such as via the of use of the EEG data collection sensor 101a, 101b and its minimal impact on the user's everyday routine. Hence, a feature of an embodiment is use of a single channel EEG data collection sensor 101a, 101b, accompanying EEG data analysis, and seizure prediction techniques(s). While a single channel EEG data collection may not be able to accurately identify where in the user's brain seizure activity is occurring all the time or initially, the simple detection of the occurrence of seizure activity presents a valuable tool to help users manage and treat epilepsy. As described, the location or placement of the sensor may be refined over time, e.g., in connection with a preliminary or subsequent full EEG montage, in connection with analysis of the sensor's data quality, etc. Additionally, predictive capabilities may provide users with improved quality of life as they can conduct activities with reduced anxiety that an unexpected seizure may occur.
One aspect of identifying and/or predicting seizures via classification at 302 may include discriminating between the various seizure types. For example, the absence seizure typically occurs many times a day and the electrographic signature of such a seizure is the same across all ages. Therefore, it may be comparatively easier to collect extensive EEG data and improve a seizure prediction model by machine learning to detect absence seizures. The other type of seizures may occur less frequently, such as once a month, so they may be difficult to predict accurately due to the lack of EEG data on which machine learning models can be trained. However, starting from the creation of a generalized seizure prediction model for a common seizure type, an embodiment may be expanded and refined by use of a model that covers other types of seizures, particularly as long-term wear of the sensors 101a, 101b by the users continues. This EEG data may be stored and used with permission of the users to build a database suitable for forming future seizure detection and prediction models.
Turning now to
In an embodiment that utilizes a machine learning process to classify the EEG data, a training phase may include processes outlined in 501-505 of
In one example, the training data may include both single channel EEG data collected using sensors 201 as well as EEG data collected using a normal 10-20 or 10-10 multi-channel wired EEG (wired EEG) sensor or headset as part of standard of care. That is, both the sensors 201 and the wired EEG sensor or headset may be worn by the same patient at the same time to obtain a set of EEG training data.
During an EMU stay, one or more of reviewing software and an epileptologist identifies potential seizure events in the wired EEG data record. Patients and/or family in the room may also indicate, e.g., push a button, that a seizure is occurring. An epileptologist reviews the entire multi-day wired EEG, along with the reviewing software and user provided event markers, to determine when a seizure occurred (as is conventional). An epileptologist may also review the EEG data to identify what type of seizure event occurred (as is conventional). If a seizure was focal in origin, an epileptologist may indicate which wired EEG electrodes was center of focus. An epileptologist may also indicate EEG start/stop of seizure, whether the electrographic seizure is visible on the wired EEG at locations where each sensor was placed, and electrographic obscuring artifact(s) (such as patent movement) start/stop. From this information, when a seizure should be electrographically visible (per conventional techniques) is known and this may be utilized to compare with the data obtained via the four sensors 201.
Indicated at 502, a pre-processing of raw EEG data is performed. By way of example, noise removal or filtering may be applied, such as removal of 50/60-Hz line noise, low-pass filtering to remove electromyographic (EMG) muscle activity, normalization of standardization to account for inter-patient and inter-sensor differences in the data amplitude. Other or additional signal processing conducted at 501 may include electro-ocular artifact rejection (to remove the impact of eye movement), e.g., from certain sensor placements such as F7/F8 placed sensors.
Pre-processed data is segmented into short-duration segments (for example between 0.5-10 seconds) at 503. In an embodiment, each segment is labeled, e.g., as seizure or non-seizure, based on its origin from a time previously noted as during a seizure in the patient wearing phase of 501 and if the seizure was visible at the sensor 201 location(s).
Feature Extraction is performed at 504. In an embodiment, one or more of the following features are extracted from the segmented data: time domain (min, max, mean, median, range, variance, standard deviation, skew, kurtosis); frequency domain (Fast-Fourier Transforms, EEG specific bands (s, delta, theta, alpha, beta, gamma)); time-frequency domain (wavelets); complexity domain (sample/spectral entropy, non-linear energy operator, Hjorth parameters, fractal dimensions); transforms: (principal component analysis, linear discriminant analysis); and historical (past segment values, which may be weighted).
Model tuning is performed at 505. Because the EEG sensor data is highly-imbalanced (e.g., 100:1 ratio of non-seizure segments to seizure), a subset of the EEG data may be used (e.g., 3:1 for the EEG data/model). A machine learning model, for example a random forest as shown in
Metrics such as receiver operating curve (ROC) area under the curve (AUC), specificity, sensitivity, positive predictive value, false positive rate, or any combination of foregoing, may be used to determine the best model. In certain cases, e.g., where seizure detection is paramount and false positives are tolerable, e.g., in a seizure diary context, a particular model may be chosen over use in another scenario, e.g., where false positives are to be minimized, such as automated medication recommendations or providing suspected diagnoses. In an embodiment, the model employed may be exchanged or modified, e.g., by adjusting a parameter such as a probability threshold, to suit the use context. By way of example, an embodiment may adjust the model employed by offering the end user data input interfaces, such as displaying selectable elements that indicate the use context, which after selection loads a predetermined model or set of parameter(s) for the context indicated. For example, contexts such as seizure diary, real time alerting, emergent care, etc., may be indicated via selections, which loads a model or adjusts a model's parameter(s), e.g., probability threshold(s) that can be modified to adjust sensitivity, to match the context indicated. More experienced users may interface with the model parameters more directly.
Following the tuning at 505, the tuned model(s) may be saved for use in detection. For example, in steps 506-510, a model such as a previously tuned model is accessed and run on patient data, e.g., collected using one or more sensors 201 in a treatment scenario. As described herein, this may include a process of segment detection, as outlined in 506-510. By way of example, at 506 a patient, e.g., that has been previously diagnosed with a seizure disorder, wears one or more sensors 201, e.g., using a placement guided by the patient's epileptologist as to be the most likely to pick up seizure events. No wired EEG data would recorded and the patient wears the sensor(s) 201, e.g., during everyday activities. In one example, the patient wears the sensor(s) 201 up to 24-hours a day and may do so for several days.
EEG data collected by the sensors 201 may be streamed into a remote device such as a cloud-platform, as per the example of
At 510, the unlabeled, segmented, feature set is run through the trained model, the outputs of which may be utilized in a whole seizure detection process, as for example outlined at 511-514.
In the example of
At 512 segment stitching is performed. For example, segment probabilities are combined to create a start/stop time for a (whole) seizure event, i.e., consisting of multiple segments. This may be accomplished in many ways. By way of example, the segments may be stitched or combined together via individual segment thresholding (such as comparing frequency and amplitude EEG data changes to threshold(s) for each segment), a multi-segment thresholding and windowing process (combining or considering together multiple segments probabilities, e.g., in comparison to one or more thresholds), or integration windowing (e.g., weighted, leaky, etc.). The windows are typically as short as a few seconds (e.g., absence seizures) or up to minutes in duration (e.g., for focal seizures).
Annotations are generated, e.g., for a patient medical record or EEG trace display, for the start/stop time of the determined seizure events at 513. This annotation list data may be utilized in a variety of ways, e.g., as an indication per
Indicated at 514 is an epileptologist review stage. In an embodiment, clinicians may review the annotations and/or the raw EEG data and make clinical decisions. The process of epileptologist or simply user review at 514 may be influenced by the context. For example, in an embodiment, a low-threshold may be set (as described herein) that leads to many false positives. In such an embodiment, a whole seizure/no-seizure determination may or may not even be made. Rather, the annotations produced at 513 may be provided to a clinician, e.g., for more rapid review of potentially interesting EEG data, and seizure/non-seizure decisions may be made by the clinician based on this review. In other contexts, the review may be conducted by another, e.g., an at home user making a seizure diary. In this context, additional or different data may be displayed, e.g., time or location context data indicating when the potentially interesting EEG data was recorded to facilitate user review.
Referring to
In an embodiment, an application may further display instructional steps to the user. For example, the application may display instructions for turning on or activating the sensor, pairing a sensor, which may be an automated or semi-automated routine accomplished with a user input such as a button press, confirming that a sensor is connected to the mobile device, confirming that the mobile device is connected with a remote device (e.g., cloud platform), preparing a sensor to be adhered to a patient, determining the appropriate location(s) for sensor placement on the patient, re-positioning the sensors in the application, recording data, and storing data (locally or remotely). Further, the application may include additional or alternative display capabilities, e.g., the ability to have a live video call with an expert, clinician, etc., the latter of which may assist in live or real-time troubleshooting or diagnosis contexts.
Once the user has activated and connected the sensor(s) to the mobile device running the application, this is confirmed by the application as illustrated at 602. For example, the application may display the sensor(s) in a location illustration, as indicated in
Referring again to
It will be readily understood that certain embodiments can be implemented using any of a wide variety of devices or combinations of devices. Referring to
The central processing unit (CPU) 810, which may include one or more graphics processing units (GPUs) and/or micro-processing units (MPUs), includes an arithmetic logic unit (ALU) that performs arithmetic and logic operations, instruction decoder that decodes instructions and provides information to a timing and control unit, as well as registers for temporary data storage. The CPU 810 may comprise a single integrated circuit comprising several units, the design and arrangement of which vary according to the architecture chosen.
Computer 800 also includes a memory controller 840, e.g., comprising a direct memory access (DMA) controller to transfer data between memory 850 and hardware peripherals. Memory controller 840 includes a memory management unit (MMU) that functions to handle cache control, memory protection, and virtual memory. Computer 800 may include controllers for communication using various communication protocols (e.g., I2C, USB, etc.).
Memory 850 may include a variety of memory types, volatile and nonvolatile, e.g., read only memory (ROM), random access memory (RAM), electrically erasable programmable read only memory (EEPROM), Flash memory, and cache memory. Memory 850 may include embedded programs and downloaded software, e.g., EEG processing software, etc. By way of example, and not limitation, memory 850 may also include an operating system, application programs, other program modules, and program data.
A system bus permits communication between various components of the computer 800. I/O interfaces 830 and radio frequency (RF) devices 820, e.g., WIFI and telecommunication radios, BLE devices, etc., are included to permit computer 800 to send and receive data to sensor(s) 870 or remote devices 870a using wired or wireless mechanisms. The computer 800 may operate in a networked or distributed environment using logical connections to one or more other remote computers or databases. The logical connections may include a network, such as a personal area network (PAN), a local area network (LAN) or a wide area network (WAN) but may also include other networks/buses. For example, computer 800 may communicate data with and between a sensor 870 and remote devices 870a over the Internet.
The computer 800 may therefore execute program instructions configured to store and analyze EEG data, and perform other functionality of the embodiments, as described herein. A user can interface with (for example, enter commands and information) the computer 800 through input devices, which may be connected to I/O interfaces 830. A display or other type of device may also be connected or coupled to the computer 800 via an interface selected from I/O interfaces 830.
It should be noted that the various functions described herein may be implemented using executable instructions stored in a memory, e.g., memory 850, that are transmitted to and executed by a processor, e.g., CPU 810. Computer 800 includes one or more storage devices that persistently store programs and other data. A storage device, as used herein, is a non-transitory storage medium. Some additional examples of a non-transitory storage device or medium include, but are not limited to, storage integral to computer 800, such as a hard disk or a solid-state drive, and removable storage, such as an optical disc or a memory stick.
Program code stored in a memory or storage device may be transmitted using any appropriate transmission medium, including but not limited to wireless, wireline, optical fiber, cable, RF, or any suitable combination of the foregoing.
Program code for carrying out operations may be written in any combination of one or more programming languages. The program code may execute entirely on a single device, partly on a single device, as a stand-alone software package, partly on single device and partly on another device, or entirely on another device. In some cases, the devices may be connected through any type of connection or network, including a LAN, a WAN, a short-range wireless mechanism such as a PAN, a near-field communication mechanism, or the connection may be made through other devices (for example, through the Internet using an Internet Service Provider), using wireless connections or through a hard wire connection, such as over a USB connection.
Example embodiments are described herein with reference to the figures, which illustrate example methods, devices and program products according to various example embodiments. It will be understood that the actions and functionality may be implemented at least in part by program instructions. These program instructions may be provided to a processor of a device to produce a special purpose machine, such that the instructions, which execute via a processor of the device implement the functions/acts specified.
It is worth noting that while specific elements are used in the figures, and a particular ordering of elements has been illustrated, these are non-limiting examples. In certain contexts, two or more elements may be combined, an element may be split into two or more elements, or certain elements may be re-ordered or re-organized or omitted as appropriate, as the explicit illustrated examples are used only for descriptive purposes and are not to be construed as limiting.
Although illustrative example embodiments have been described herein with reference to the accompanying figures, it is to be understood that this description is not limiting, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the disclosure.
This application claims priority to U.S. patent application Ser. No. 17/019,811 filed Sep. 14, 2020, which in turn claims priority to U.S. provisional patent application Ser. No. 63/005,405, filed on Apr. 5, 2020 and having the same title, the contents of each of which are incorporated by reference in their entirety herein.
Number | Name | Date | Kind |
---|---|---|---|
4936306 | Doty | Jun 1990 | A |
5309923 | Leuchter | May 1994 | A |
5483967 | Ohtake | Jan 1996 | A |
5755230 | Schmidt et al. | May 1998 | A |
6117077 | Del Mar et al. | Sep 2000 | A |
6416471 | Kumar et al. | Jul 2002 | B1 |
6473639 | Fischell | Oct 2002 | B1 |
6496724 | Levendowski | Dec 2002 | B1 |
6735467 | Wilson | May 2004 | B2 |
7177675 | Suffin | Feb 2007 | B2 |
7489964 | Suffin | Feb 2009 | B2 |
7885706 | Ludvig et al. | Feb 2011 | B2 |
7962204 | Suffin | Jun 2011 | B2 |
7970450 | Kroecker et al. | Jun 2011 | B2 |
8204583 | Sackellares | Jun 2012 | B2 |
8224433 | Suffin | Jul 2012 | B2 |
8562523 | Osorio | Oct 2013 | B2 |
8594763 | Bibian et al. | Nov 2013 | B1 |
8626261 | Ko et al. | Jan 2014 | B2 |
8666484 | Nierenberg | Mar 2014 | B2 |
8786624 | Echauz et al. | Jul 2014 | B2 |
8805527 | Mumford et al. | Aug 2014 | B2 |
8818481 | Bly et al. | Aug 2014 | B2 |
8849390 | Echauz et al. | Sep 2014 | B2 |
8868172 | Leyde et al. | Oct 2014 | B2 |
9186083 | Osvath | Nov 2015 | B2 |
9241649 | Kumar et al. | Jan 2016 | B2 |
9439599 | Thompson et al. | Sep 2016 | B2 |
9459089 | Ganton et al. | Oct 2016 | B2 |
10206591 | Osorio | Feb 2019 | B2 |
10342451 | Girouard et al. | Jul 2019 | B2 |
10448839 | Shivkumar | Oct 2019 | B2 |
10463270 | Leyde | Nov 2019 | B2 |
10571541 | Grodzki | Feb 2020 | B2 |
10736525 | Cardenas et al. | Aug 2020 | B2 |
10743809 | Kamousi | Aug 2020 | B1 |
10929753 | Nierenberg et al. | Feb 2021 | B1 |
10980469 | Girouard et al. | Apr 2021 | B2 |
10986465 | Patel et al. | Apr 2021 | B2 |
11020035 | Dudek et al. | Jun 2021 | B2 |
11026628 | Bruinsma et al. | Jun 2021 | B1 |
11160505 | Gunasekar et al. | Nov 2021 | B2 |
11633139 | Dudek et al. | Apr 2023 | B2 |
11633144 | Elwood et al. | Apr 2023 | B2 |
11638551 | Elwood et al. | May 2023 | B2 |
20020013565 | Cinelli et al. | Jan 2002 | A1 |
20020035338 | Dear | Mar 2002 | A1 |
20020103512 | Echauz | Aug 2002 | A1 |
20020109621 | Khair et al. | Aug 2002 | A1 |
20020188216 | Kayyali et al. | Dec 2002 | A1 |
20030074033 | Pless et al. | Apr 2003 | A1 |
20030135128 | Suffin | Jul 2003 | A1 |
20030195429 | Wilson | Oct 2003 | A1 |
20040068199 | Echauz | Apr 2004 | A1 |
20040079372 | John et al. | Apr 2004 | A1 |
20050165323 | Mongomery et al. | Jul 2005 | A1 |
20050261559 | Mumford et al. | Nov 2005 | A1 |
20060111644 | Guttag | May 2006 | A1 |
20070032737 | Causevic | Feb 2007 | A1 |
20070249952 | Rubin et al. | Oct 2007 | A1 |
20070270678 | Fadem et al. | Nov 2007 | A1 |
20080082019 | Ludving et al. | Apr 2008 | A1 |
20080082020 | Collura | Apr 2008 | A1 |
20080091089 | Guillory et al. | Apr 2008 | A1 |
20080091090 | Guillory et al. | Apr 2008 | A1 |
20080125669 | Suffin | May 2008 | A1 |
20080208008 | Turner | Aug 2008 | A1 |
20080243022 | Donnett et al. | Oct 2008 | A1 |
20080275327 | Faarbaek et al. | Nov 2008 | A1 |
20080294031 | Wilson et al. | Nov 2008 | A1 |
20090054737 | Magar et al. | Feb 2009 | A1 |
20090124923 | Sackellares | May 2009 | A1 |
20090137923 | Suffin | May 2009 | A1 |
20090157662 | Suffin | Jun 2009 | A1 |
20100143256 | Suffin | Jun 2010 | A1 |
20100145217 | Otto et al. | Jun 2010 | A1 |
20100298735 | Suffin | Nov 2010 | A1 |
20110221590 | Baker et al. | Sep 2011 | A1 |
20120003933 | Baker et al. | Jan 2012 | A1 |
20120035451 | Jaffe et al. | Feb 2012 | A1 |
20120179062 | Wilson | Jul 2012 | A1 |
20120209102 | Ylotalo et al. | Aug 2012 | A1 |
20120310070 | Kumar et al. | Dec 2012 | A1 |
20120330125 | Wilson et al. | Dec 2012 | A1 |
20130012830 | Leininger | Jan 2013 | A1 |
20130310676 | Jung | Nov 2013 | A1 |
20130338473 | Bohorquez et al. | Dec 2013 | A1 |
20140012151 | Nierenberg et al. | Jan 2014 | A1 |
20140012509 | Barber | Jan 2014 | A1 |
20140051044 | Badower et al. | Feb 2014 | A1 |
20140121557 | Gannon et al. | May 2014 | A1 |
20140206975 | Lang | Jul 2014 | A1 |
20140247058 | Mortara | Sep 2014 | A1 |
20140313052 | Yarger et al. | Oct 2014 | A1 |
20150038870 | Yoo et al. | Feb 2015 | A1 |
20150088024 | Sackellares et al. | Mar 2015 | A1 |
20150134580 | Wilson | May 2015 | A1 |
20150142082 | Simon et al. | May 2015 | A1 |
20150150505 | Kaskoun et al. | Jun 2015 | A1 |
20150216436 | Bosl et al. | Aug 2015 | A1 |
20150351690 | Toth et al. | Dec 2015 | A1 |
20150374255 | Vasapollo | Dec 2015 | A1 |
20160022161 | Khair | Jan 2016 | A1 |
20160029958 | Le et al. | Feb 2016 | A1 |
20160089049 | Hung et al. | Mar 2016 | A1 |
20160256111 | Cheng et al. | Sep 2016 | A1 |
20160287127 | Kesinger et al. | Oct 2016 | A1 |
20160374583 | Cerruti et al. | Dec 2016 | A1 |
20170055896 | Al-Ali et al. | Mar 2017 | A1 |
20170076217 | Krumm | Mar 2017 | A1 |
20170085000 | Girard | Mar 2017 | A1 |
20170095176 | Sun et al. | Apr 2017 | A1 |
20170156622 | Mahoor et al. | Jun 2017 | A1 |
20170169128 | Batchu et al. | Jun 2017 | A1 |
20170172414 | Nierenberg et al. | Jun 2017 | A1 |
20170215759 | Dudek et al. | Aug 2017 | A1 |
20170264792 | Lee et al. | Sep 2017 | A1 |
20170296083 | Cardenas | Oct 2017 | A1 |
20180085000 | Weffers-Aibu et al. | Mar 2018 | A1 |
20180110466 | Ralston | Apr 2018 | A1 |
20180189678 | Gupta et al. | Jul 2018 | A1 |
20180206776 | Nogueira | Jul 2018 | A1 |
20180353084 | Right et al. | Dec 2018 | A1 |
20190059770 | Gunasekar et al. | Feb 2019 | A1 |
20190126033 | Pradeep | May 2019 | A1 |
20190371478 | Rondoni et al. | Dec 2019 | A1 |
20190380583 | Danneels et al. | Dec 2019 | A1 |
20200022603 | Cardenas et al. | Jan 2020 | A1 |
20200163629 | Dearing et al. | May 2020 | A1 |
20200229706 | Nishimura et al. | Jul 2020 | A1 |
20200237248 | Willis et al. | Jul 2020 | A1 |
20200315537 | Magar | Oct 2020 | A1 |
20210169417 | Burton | Jun 2021 | A1 |
20210220064 | Kottenstette et al. | Jul 2021 | A1 |
20210244335 | Dudek et al. | Aug 2021 | A1 |
20210282701 | Chan | Sep 2021 | A1 |
20210307672 | Elwood et al. | Oct 2021 | A1 |
20210353224 | Etkin | Nov 2021 | A1 |
20210375480 | Mahon et al. | Dec 2021 | A1 |
20220031248 | Grant et al. | Feb 2022 | A1 |
20220338780 | Dudek et al. | Oct 2022 | A1 |
20220338789 | Elwood | Oct 2022 | A1 |
20220338790 | Elwood | Oct 2022 | A1 |
20220338791 | Elwood et al. | Oct 2022 | A1 |
20220338792 | Elwood et al. | Oct 2022 | A1 |
20220338793 | Elwood et al. | Oct 2022 | A1 |
20220346695 | Elwood et al. | Nov 2022 | A1 |
20220346700 | Elwood | Nov 2022 | A1 |
Number | Date | Country |
---|---|---|
2782499 | Mar 2021 | EP |
2010527709 | Aug 2010 | JP |
WO 2005109334 | Nov 2005 | WO |
WO 2015055156 | Apr 2015 | WO |
WO 2018013569 | Jan 2018 | WO |
WO 2019046799 | Mar 2019 | WO |
Entry |
---|
Jia et al. Design of a Wireless EEG System for Point-of-Care Applications Proc IEEE Annu Northeast Bioeng Conf. Apr. 2013; 2013: 78-79. (Year: 2013). |
Lnggi Ramadhani Dwi Saputro et al 2019 J. Phys.: Conf. Ser. 1201 012065 Seizure Type Classification on EEG Signal using Support Vector Machine (Year: 2019). |
Rodriquez, K, International Search Report and Written Opinion, PCT/US21/25489, USPTO, 10 pages, dated Jul. 16, 2021. |
Rodriquez, K, International Search Report, PCT/US21/25489, USPTO, 8 pages, dated Jul. 16, 2021. |
Prabhu K.M.M., Window Functions and Their Applications in Signal Processing. ISBN-13:978-1-4665-1583-3; Taylor & Francis; 2014; in 405 pages. |
Number | Date | Country | |
---|---|---|---|
20220338789 A1 | Oct 2022 | US |
Number | Date | Country | |
---|---|---|---|
63005405 | Apr 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17019811 | Sep 2020 | US |
Child | 17811752 | US |