SYSTEMS AND METHODS FOR DIAGNOSING A STROKE CONDITION

Abstract

A method for estimating a likelihood of a stroke condition of a subject, the method comprising: acquiring clinical measurement data pertaining to said subject, said clinical measurement data including at least one of image data, sound data, movement data, and tactile data; extracting from said clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion; comparing said potential stroke features with classified sampled data acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset; and determining, according to said comparing, a probability of a type of said stroke condition, and a probability of a corresponding stroke location of said stroke condition with respect to a brain location of said subject.

Description

FIELD OF THE DISCLOSED TECHNIQUE

The disclosed technique relates to systems and methods for diagnosing a medical condition, in general, and to systems and methods for diagnosing a cerebral stroke condition, in particular.

BACKGROUND OF THE DISCLOSED TECHNIQUE

A cerebral stroke or stroke for short is a cerebrovascular condition in which blood flow irregularities in the brain leads to cell death. Two main types of stroke are known, namely, ischemic and hemorrhagic. In ischemic stroke there is a deficiency or insufficiency of blood flow to cells, so as to meet the oxygen requirements, which leads to cerebral hypoxia and consequently to brain cell death also known as cerebral infarction. Blood flow irregularities may be caused by a partial or complete blockage of blood vessels or arteries and is known to be caused by several factors which include thrombus (blood clot), embolus, and stenosis (internal narrowing of a blood vessel due to atheroma also known as plaque). In hemorrhagic stroke there is intracranial bleeding (due to a blood vessel rupture, leak, aneurysm), which can lead to an increase of intracranial pressure. Since brain cells die quickly after the onset of a stroke, treatment should begin as early as possible, given that stroke is currently one of the main causes of worldwide medical-related death as well as disability. Therefore, there is a need to reduce the time to first treatment of stroke once it is detected. There are various prior art approaches that aim to reduce the time to first treatment of stroke.

U.S. Pat. No. 9,619,613 B2 issued to Meyer et al., and entitled “Device and Methods for Mobile Monitoring and Assessment of Clinical Function through Sensors and Interactive Patient Responses” is directed at a mobile assessment terminal (device) and methods for sensing and assessing a patient's responses to tests. The mobile assessment terminal includes a central processor, a memory unit, a radio, input/output units, and a touch sensitive display. The input/output units are in the form of a microphone, a speaker, a camera, and a touch sensitive display. The central processor, memory unit, input/output units, camera, and display are operationally connected to communicate. The touch sensitive display provides one or more test prompts for conducting an interactive clinical assessment of a user. Specifically, the touch sensitive display provides one or more potential responses of actions that may be performed in response to the one or more test prompts. The mobile assessment terminal receives from the user an input indicative of an action performed in response to the test prompt provided on the touch sensitive display. Following reception of sensed input via the mobile assessment terminal, the central processor processes the sensed input data by comparing it to pre-programmed standards programmable into the mobile assessment device or a central monitoring station that is in communication with the mobile assessment device, so to determine whether the sensed input is within range of normal. If the sensed input is with range of the normal, the mobile assessment terminal generates a report that is displayed to the touch sensitive display; otherwise the mobile assessment terminal generates an alarm, which is displayed on the mobile assessment terminal as well as sent to the central monitoring station.

An article entitled “Remote Assessment of Stroke Using the iPhone 4” to Anderson, Smith, Ido and Frankel, is directed at a study using hand-held technology in a telestroke network for evaluating the National Institutes of Health Stroke Scale (NIHSS) remotely using an iPhone 4, as well as at the bedside. The study included 20 patients with stroke being assessed by one physician at each of the patients' bedsides, while transmitting video of the patients via the iPhone to another remotely located physician whose task was to examine the patients remotely. Each physician was blinded to the other's NIHSS scores. The iPhone used a wireless Internet network to transmit video (audiovisual information) for the use of NIHSS examinations. The results of the study showed excellent agreement between remote examination and bedside examination for the majority of the NIHSS components, but moderate agreement for dysarthria, facial palsy, and gaze, and poor agreement for ataxia.

SUMMARY OF THE PRESENT DISCLOSED TECHNIQUE

It is an object of the disclosed technique to provide a novel system for estimating a likelihood of a stroke condition of a subject. The system includes a patient database (“database” for brevity), and a processor. The database contains classified sampled datasets acquired from a plurality of subjects positively diagnosed with a stroke condition, defining a positive stroke dataset. The processor is configured to receive clinical measurement data pertaining to the subject. The clinical measurement data is acquired from at least one sensor that is configured to sense at least one of image data, sound data, movement data, and tactile data pertaining to the subject. The processor is configured to extract from the clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion. The processor is configured to compare the potential stroke features with the classified sample data in the patient database, and to determine a probability of a type of stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject.

In accordance with another aspect of the disclosed technique it is thus provided a method for estimating a likelihood of a stroke condition of a subject. The method includes acquiring clinical measurement data pertaining to the subject, extracting potential stroke features from the clinical measurement data, comparing the potential stroke features with classified sampled data, and determining, according to the comparing, a probability for a type of the stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. The clinical measurement data includes at least one of image data, sound data, movement data, and tactile data. The extraction of potential stroke features from the clinical measurement data is according to at least one predetermined stroke assessment criterion. The classified sampled data is acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset.

In accordance with a further aspect of the disclosed technique, there is thus provided a system for estimating a likelihood of a stroke condition of a subject, in which the system includes a client device enabled for communication with a remote computer. The client device includes at least one sensor, a user-interface, and a communication module. The at least one sensor is configured to acquire at least one of image data, sound data, movement data, and tactile data, all of which constitute clinical measurement data pertaining to the subject. The user-interface is configured to provide an indication of a probability for a type of the stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. The communication module is enabled for communication with the remote computer. The communication module is configured to send the clinical measurement data to the remote computer, and to receive from the remote computer the indication. The indication is based on a comparison between potential stroke features extracted from the clinical measurement data according to at least one predetermined stroke assessment criterion, with classified sampled data in a patient database acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed technique will be understood and appreciated more fully from the following detailed description taken in conjunction with the drawings in which:

FIG. 1A is a schematic diagram illustrating a system for estimating a likelihood of a stroke condition of a subject, according to one implementation, constructed and operative in accordance with an embodiment of the disclosed technique;

FIG. 1B is a schematic diagram illustrating a system for estimating a likelihood of a stroke condition of a subject, according to another implementation, constructed and operative in accordance with an embodiment of the disclosed technique;

FIG. 2 is a schematic illustration of the acquisition of clinical measurement data from a subject, by a plurality of different types of sensors, constructed and operative in accordance with the embodiment of the disclosed technique;

FIG. 3 is a schematic illustration of an example extraction of potential stroke features from clinical measurement image data, according to the disclosed technique;

FIG. 4 is a schematic illustration showing examples of the extraction of potential stroke features from various types of clinical measurement data at various times, according to the disclosed technique;

FIG. 5 is a schematic diagram illustrating comparison between extracted potential stroke features and classified data in a database, constructed and operative according to the disclosed technique;

FIG. 6 is a schematic diagram partly showing procedures involved in producing an estimation to the likelihood of a stroke condition, according to the principles of the disclosed technique;

FIG. 7 is a schematic diagram further showing procedures involved in producing an estimation to the likelihood of a stroke condition, according to the principles of the disclosed technique;

FIG. 8 is a schematic diagram of a method for estimating a likelihood of a stroke condition of a subject, constructed and operative in accordance with the disclosed technique;

FIG. 9A is an exemplary screenshot of a facial palsy subtest in an example NIHSS test performed by the system of the disclosed technique;

FIG. 9B is an exemplary screenshot of a motor arm subtest in an example NIHSS test performed by the system of the disclosed technique;

FIG. 9C is an exemplary screenshot of a language subtest of an example NIHSS test performed by the system of the disclosed technique;

FIG. 10 is an exemplary screenshot showing acquired clinical measurement data pertaining to the subject that is provided remotely to a physician via at least one external communication device;

FIG. 11 is an exemplary screenshot showing an example of a spatial region of interest (ROI) from a temporal point of interest (POI) in image data (video), identified as being a potential stroke feature;

FIG. 12 is an exemplary screenshot, showing an example of image analysis of facial bilateral symmetry as a function of time for the case shown in FIG. 11 (asymmetric smile);

FIG. 13 is a collection of images acquired from several subjects, showing their lower faces superimposed with a plurality of image markers for algorithmically tracking facial landmarks, according to the disclosed technique;

FIG. 14 is an exemplary screenshot showing an example of individual scores for various subtests in an example NIHSS test as yielded by the systems of the disclosed technique;

FIG. 15 is an exemplary screenshot showing an example of timing information relating to the onset of a detected a stroke condition of a subject and personal information relating thereto;

FIG. 16 is an exemplary screenshot showing a further example of individual scores of various subtests performed on the subject;

FIG. 17A is an exemplary screenshot of a system-generated stroke type and stroke location interpretation report that includes a generic brain image superimposed with a highlighted region corresponding to the location of the stroke condition, prior to neuroimaging;

FIG. 17B is an exemplary screenshot of a system-generated stroke type and stroke location interpretation report that includes a brain image of a subject acquired via a neuroimaging technique superimposed with a highlighted region corresponding to the location stroke condition, after neuroimaging;

FIG. 18 is an exemplary screenshot showing an example of a stroke patient evacuation to an emergency department (ED) of a medical healthcare facility using optimization criteria and global positioning data, according to the disclosed technique; and

FIG. 19 is an exemplary screenshot of a system-generated stroke classification report for providing to medical personnel.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The disclosed technique overcomes the disadvantages of the prior art by providing systems and a method for electronically estimating a likelihood of a cerebral stroke condition (cerebrovascular accident (CVA), a “stroke” for short) of a subject (e.g., an individual, a patient). The disclosed technique allows for remote (as well as on-site) neurological and neurophysiological assessment of the subject (e.g., telemedicine via a physician) so as to allow shortening of “time to treatment” in case it was determined that the subject is suffering from a stroke condition with a high-probability (e.g., above a threshold value). The systems of the disclosed technique are configured and operative to provide an indication of a stroke as soon (i.e., immediate, in real-time) as it is detected (i.e., estimated at a high likelihood, i.e., over a threshold probability). According to one implementation, the system includes a patient database (“database” for brevity), and a processor. The patient database contains classified sampled datasets acquired from a plurality of subjects positively diagnosed with a stroke condition. The patient database may further contain classified sample datasets acquired from a plurality of subjects negatively diagnosed with a stroke condition (i.e., do not have a stroke condition). The processor is configured to receive clinical measurement data pertaining to the subject. The clinical measurement data is acquired from at least one sensor that is configured to sense at least one of image data, sound data, movement data, and tactile data pertaining to the subject. The processor is configured to extract from the clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion (e.g., a test, a standard, a characterizing mark). The processor is configured to compare the potential stroke features with the classified sample data in the patient database, and to determine a probability for a type of stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. The stroke location corresponds to the type of stroke for that stroke location. The brain location of the subject is an estimate that is fine-tuned by a brain image of the subject acquired, for example, by neuroimaging techniques. The brain location may be specified by the particular anatomical brain feature (e.g., blood vessel, area, etc.), as well as via three-dimensional coordinates of a brain volume with respect to reference point(s).

According to another aspect of the disclosed technique, there is thus provided a method for estimating a likelihood of a stroke condition of a subject. The method includes acquiring clinical measurement data pertaining to the subject, extracting potential stroke features from the clinical measurement data, comparing the potential stroke features with classified sampled data in a patient database potential stroke features, and determining, according to the comparing, a probability for a type of the stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. The clinical measurement data includes at least one of image data, sound data, movement data, and tactile data. The extraction of potential stroke features from the clinical measurement data is according to at least one predetermined stroke assessment criterion. The patient database is acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, and optionally a plurality of subjects negatively diagnosed with a stroke condition.

According to a further aspect of the disclosed technique, there is thus provided a system for estimating a likelihood of a stroke condition of a subject, in which the system includes a client device enabled for communication with a remote computer. The client device includes at least one sensor, a user-interface, and a communication module. The at least one sensor is configured to acquire at least one of image data, sound data, movement data, and tactile data, all of which constitute clinical measurement data pertaining to the subject. The user-interface is configured to provide an indication of a probability for a type of the stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. The communication module is enabled for communication with the remote computer. The communication module is configured to send the clinical measurement data to the remote computer, and to receive from the remote computer the indication. The indication is based on a comparison between potential stroke features extracted from the clinical measurement data according to at least one predetermined stroke assessment criterion, with classified sampled data in a patient database acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition. The terms “stroke”, “stroke event”, and “stroke condition” are used interchangeably herein.

Reference is now made to FIG. 1A, which is a schematic diagram illustrating a system for estimating a likelihood of a stroke condition of a subject, according to one implementation, generally referenced 100₁, constructed and operative in accordance with an embodiment of the disclosed technique. The following is a top-level description of the disclosed technique, which is followed by a more detailed, low-level description. FIG. 1A shows a high-level block diagram of system 100₁, which includes a database 102, a processor 104, at least one acquisition unit 106 (also denoted interchangeably herein as “acquisition unit(s)”, and in the full plural form “acquisition units”), a communication module 108 (optional), and a user interface 110 (optional). According to one implementation, system 100₁ is a standalone (self-contained) device, which in itself can have several configurations. In one configuration of the standalone implementation, database 102, acquisition unit(s) 106, communication module 108, and user interface 110 are coupled (e.g., enabled for data communication) with processor 104, such that all of these elements are centralized (i.e., all components are not remote to one another), for example incorporated into a common housing (e.g., a computer station, a robot, etc.). According to another configuration of the standalone implementation, system 101₁ is decentralized such that at least two elements selected from database 102, processor 104, acquisition unit(s) 106, communication module 108, and user interface 110 are remote to each other. In such a decentralized configuration the remote elements are enabled for communication (e.g., wired (e.g., a telephone line, etc.), wireless (e.g., Wireless-Fidelity (Wi-Fi), etc.)) with processor 104 via communication module 108 (i.e., which may also be decentralized). One example of a decentralized configuration in the standalone implementation is where acquisition unit(s) 106 is located at a particular location (e.g., a room) at a particular site (e.g., a clinic, elderly home, retirement home, etc.), while processor 104, database 102, communication module 108, and user interface 110 are located at a separate and distant location either at that site (e.g., a server room, a control room, etc.), or alternatively, at another site (e.g., a different building, etc.).

According to another implementation, system 100₁ is a split (i.e., not standalone), in which typically both database 102, and processor 104, are separate and remote from acquisition unit(s) 106. In this typical implementation, the optional components of communication module 108 and user interface 110 are typically located with processor 104 and database 102. For example, database 102 and processor 104 are located in a cloud server (e.g., a data center, a server farm, etc.), and acquisition unit(s) 106 are dispersed at different and remote locations (e.g., different clinics). In this implementation, acquisition unit(s) 106 is/are enabled for communication with processor 104.

An overview of the block elements of system 100₁ now follows. Generally, each acquisition unit 106 includes at least one sensor (not shown in FIG. 1A) configured to acquire data of at least one modality type, i.e., at least one of image data, sound data, movement data, and tactile data, all of which constitute clinical measurement data pertaining to a subject (e.g., individual, patient, person subject to diagnosis, and the like). Database 102 (also denoted interchangeably as “patient database”) generally includes pre-classified sampled datasets acquired from a plurality of subjects positively diagnosed with at least one stroke condition, as well as pre-classified sample datasets acquired from a plurality of subjects negatively diagnosed with a stroke condition. Processor 104 is generally configured to receive the clinical measurement data pertaining to the subject, acquired from at least one sensor in each acquisition unit 106. Processor 104 is further configured to extract from the clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion (e.g., test, characteristic, attribute), and to compare the potential stroke features with pre-classified sample data in the patient database 102 at least one of positively and negatively diagnosed with a stroke condition. Processor 104 is configured to determine a probability for a type of stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject. User interface 110 includes at least one user interface, and more typically two user interfaces: (1) a management user interface that is typically embodied as a human-machine-interface (HMI) configured to interface between system 100₁ and a manager of system 100₁ (e.g., a system administrator, a data scientist, a manager, a medical professional, an operator of system 100₁, and the like), and (2) a subject or patient user interface that is embodied in the form of a HMI configured to interface between system 100₁ and the patient that is the subject of the diagnosis. User interface 110 is generally further configured to provide an indication of a these probabilities (i.e., type of stroke condition, and probability of a corresponding location (area, region, volume) of the stroke condition with respect to a brain area of the subject). User interface may be implemented as a human-machine interface (HMI) that may have various user-interfacing layers/modalities/interfaces such as visual (e.g., implemented in hardware and software as a screen, touchscreen), auditory (e.g., a speaker), voice/verbal (e.g., a microphone), tactile (e.g., touchscreen, keyboard), movement/gesture (e.g., accelerators and gyroscopes), and the like. Communication module 108 is generally configured to enable: (1) communication between the elements of system 100₁ (e.g., acquisition unit(s) 106 being remote from processor 104); (2) enable communication of system 110₁ with a system administrator thereof (manager, operator, and the like); and (3) enable communication of system 100₁ with remotely located medical professionals, hospitals, a stroke prevention and recovery center (SPARC), and the like.

According to another implementation of the disclosed technique, there is provided a system that is configured and operative in accordance with server-client architecture. To further explicate the particulars of this implementation, reference is now made to FIG. 1B, which is a schematic diagram illustrating a system for estimating a likelihood of a stroke condition of a subject, according to another implementation, generally referenced 100₂, constructed and operative in accordance with an embodiment of the disclosed technique. System 100₂ includes a server 101S at a “server side”, and a plurality of clients 101C₁, 101C₂, . . . , 101C_N (where N is an positive integer) at a “client side”. Server 101S (also denoted interchangeably herein as “server computer”) and plurality of clients 101C₁, 101C₂, . . . , 101C_N (also denoted interchangeably herein (in singular form) as “client computer”, “client device”, “client”, and “user device”) are enabled for communication with each other via a communication medium (e.g., a computer network, an intranet, the Internet, etc.). On the server side, server computer 101S includes a database 102S, a server processor 104S, communication module 108S, and a user interface 110S. Database 102S, communication module 108S, and user interface 110S are configured to be communicatively coupled with server processor 104S. Each component in server computer 101S may be implemented by distinct sub-components (e.g., server processor 104S may include a plurality of distinct processors, cores, etc.). In another example, database 102S is split into two or more sub-databases, i.e., a “positive-diagnosis” sub-database containing sampled datasets acquired from a plurality of subjects positively diagnosed with at least one stroke condition, and a “negative-diagnosis” sub-database containing sampled datasets acquired from a plurality of subjects negatively diagnosed with a stroke condition.

On the client side, there are generally N clients, where each i-th client device (1≤i≤N; i ∈ Z) includes at least one acquisition unit 106C_i and a communication module 108C_i. Each i-th client device may further include optionally, a client processor 104C_i and a user interface 110C_i. Additionally, client devices 101C₁, 101C₂, . . . , 101C_N may typically further include a memory device (not shown) for storing data acquired by acquisition unit(s). FIG. 1B shows several examples of different types of client devices. Client device 101C₁ includes a client processor 104C₁, at least one acquisition unit 106C₁, a communication module 108C₁, and a user interface 110C₁. Client device 101C₂ includes at least one acquisition unit 106C₂, a communication module 108C₂, and a user interface 110C₂. Client device 101C_N includes at least one acquisition unit 106C_N, and a communication module 108C_N. Client devices 101C₁, 101C₂, . . . , 101C_N are enabled for communication with server 101S via their respective communication modules. Specifically, communication module 108C₁ of client device 101C₁ is enabled for communication with communication module 108S of server 101S. Communication module 108C₂ of client device 101C₂ is enabled for communication with communication module 108S, and so forth to client device 101C_N. Client devices 101C₁, 101C₂, . . . , 101C_N may be embodied for example, in the form of smartphones, tablets, laptop computers, desktop computers, wearable devices (e.g., smart watches), “intelligent virtual assistant” (IVA) devices, “intelligent personal assistant” (IPA) devices, computerized home systems, and the like. Processors 104 and 104S are hereinafter referred interchangeably according to applicability to the implementations of FIG. 1A and FIG. 1B, respectively.

Reference is now made to FIG. 2, which is a schematic illustration of the acquisition of clinical measurement data from a subject, by a plurality of different types of sensors, constructed and operative in accordance with the embodiment of the disclosed technique. FIG. 2 shows a subject 10 (i.e., individual, patient) who is a subject of diagnosis via system 100₂ (FIG. 1B) of the disclosed technique. The principles described herein likewise apply to system 100₁ (FIG. 1A), with respect to acquisition units 106. Client device 101C₁ includes a plurality of acquisition units: image sensor(s) 120C₁ (camera(s)), sound sensor(s) 122C₁, movement sensor(s) 124C₁, and tactile sensor(s) 126C₁. A plurality of different sensor types are shown for the purpose of example, though only one sensor of one type may be sufficient to estimate a likelihood of a stroke condition of subject 10. Alternatively, a plurality of sensors of the same type may be sufficient. To enhance the estimation result, the system of the disclosed technique typically employ a plurality of different sensor types as such sensors are ubiquitous in many user devices (e.g., smartphones, smart wearable devices (e.g., watches), and the like). Additionally and optionally, a blood pressure measurement device (not shown) may be used as to acquire clinical measurement blood pressure data (not shown).

Prior to the process of estimating a likelihood of a stroke condition, subject 10 (or via an intermediary thereof) is usually required to set-up a user account on server 101S via client device 101C₁ that is enabled for this purpose. Typically, subject 10 (or via an intermediary thereof) may be required to input her/his identifying information into client device 101C₁ that is configured and operative to run software (e.g., an application, a program that may be downloaded to the client device, be pre-installed on the client device, etc.) and enabled for communication and the exchange of data with server 101S (FIG. 1B). Subject 10 may be typically required to register with system 100₂ of the disclosed technique prior to use (e.g., via client device 101C₁, or alternatively via any other capable device, service operator, etc.). This step is denoted herein as an “initial set-up” stage. Identifying information may include the subject's name, age, sex, as well as auxiliary information that may provide additional cues in the estimation of a likelihood of a stroke condition. Auxiliary information may include medical information (e.g., current and/or previous stroke data such as stroke type (e.g., ischemic, hemorrhagic), as well as hypertension, current and previous heart disease/conditions (e.g., atrial fibrillation), blood cholesterol data, diabetes mellitus, etc.), as well as lifestyle-related information (e.g., known risk factors such as tobacco smoking, obesity, etc.). While auxiliary information may be beneficial to the estimation result, such information is not necessary for the disclosed technique to produce accurate results. Client device 101C₁ is configured to receive via at least one of user interface 110C₁ (FIG. 1B) and acquisition units 106C₁ the subject's identifying information as well as the auxiliary information and to send these to server 101S via communication module 108C₁.

Following the initial set-up stage, the system and method of the disclosed technique are configured and operative to acquire and construct at least one baseline profile of subject 10. The baseline profile defines a time-dependent state of that subject's detected neurological state (i.e., a personalized profile) that includes an estimation to a likelihood of a stroke condition at a particular time. The disclosed technique employs a plurality of baseline profiles that are time-stamped, recorded and stored in database 102. The baseline profiles may be acquired and recorded on a timely basis (e.g., in a scheduled manner), on an initiation/prompt basis (e.g., patient initiated, medical professional initiated, third-party initiated (e.g., by a family member, relative, etc.), on the basis of measurements indicators triggers, a non-scheduled manner, and the like. Should the baseline profile of a particular individual be indicative of a high likelihood of a stroke condition (i.e., with respect to a particular threshold), systems 101₁, and 101₂ are configured and operative to alert the user, the user's relatives, and medical professionals, as will be detailed hereinbelow. Attaining a current estimation of a likelihood of a stroke condition (which can serve as a time-stamped baseline profile) is facilitated by acquiring clinical measurement data via the acquisition units. According to one implementation, the acquirement of the clinical measurement data involves prompting subject 10 to follow instructions, directions or guidance, provided by user interface 110C₁ (e.g., via a program installed in client device 101C₁, via a phone call, an Internet website, etc.). According to another implementation, clinical measurement data is acquired automatically, with or without user intervention. The baseline profile enables systems 100₁ and 100₂ to monitor, detect, and alert to changing trends in the clinical measurement data (e.g., speech irregularities get progressively worse, etc.), so as to facilitate early estimation and detection of a stroke condition before it occurs (upcoming stroke event). Furthermore, the baseline profile enables systems 100₁ and 100₂ to compare different baseline profiles (amongst themselves) of a particular subject acquired at different times (e.g., current baseline profile as well as past baseline profiles) and generate respective comparison reports (i.e., between at least two different baseline profiles).

Prior to use, systems 101₁ and 101₂ are configured (e.g., via a program, software, hardware configuration, firmware configuration, algorithm, self-modifiable program, or combinations thereof) (also denoted herein as “pre-configured”) or trained (i.e., via machine learning (ML) techniques, such as machine learning classification/classifier (MLC)) (also denoted herein as “pre-trained”) so as to be enable to classify input data (e.g., distinguish, identify) among two main classes of potential stroke features stored in two different and main datasets, namely, a positive stroke dataset, and a negative stroke dataset. The positive stroke dataset includes a plurality of entries (labeled data) that are sampled from individuals positively diagnosed with at least one stroke condition. The negative stroke dataset includes a plurality of entries that are sampled from individuals negatively diagnosed for a stroke condition (i.e., are verified not to have a stroke condition). Given a tested potential stroke feature input, systems 101₁ and 101₂ are configured and/or trained to classify, i.e., associate the input potential stroke feature with either one of the positive stroke dataset (with a particular probability of match), the negative stroke dataset (with a particular probability of match), or (untypically) be indeterminate (i.e., neither). The configuration or training is achieved at different hierarchies (i.e., types and levels of data), from the data type to a particular attribute in the data, such as per clinical measurement type (e.g., image data, sound data), per sub-type (e.g., image feature, sound feature), and so forth according to the resolution required. Following the initial configuration or training phase, systems 101₁ and 101₂ are enabled for “steady-state” operation. The MLC is trained on dataset entries that may include data pertaining or based on computer tomography (CT) scans marked and evaluated by a trained physician, as well as digital reports of subjects and their respective image data, sound data, movement data, and tactile data, and optionally, blood pressure data.

Image sensor 120C₁ in client device 101C₁ is typically part of a camera system assembly configured and operative to acquire image data 130 usually in the form of at least one image, and typically a plurality of images 130₁, 130₂, 130₃, . . . of at least a part of subject 10 (e.g., face, torso and face, entire body, etc.). Images 130₁, 130₂, 130₃ may be outputted as individual still images, as well as in the form of video. The camera system assembly may employ a plurality of individual camera modules each having its own image sensor, lens, and image software. The camera system may further be augmented by employing range imaging techniques (not shown) that capture depth information (i.e., distance between points in an external scene with respect to at least one reference point (e.g., the sensor's image plane)) that may be presented as a two-dimensional (2-D) range image. Such techniques include for example, time-of-flight (ToF) techniques, structured light techniques, stereophotogrammetry techniques, interferometry techniques, and the like. Images 130₁, 130₂, 130₃, . . . are inputted into a preprocessor 132 that is configured and operative to preprocess the images by various techniques that include for example, image cropping, scaling, correction of distortions, isolation of image background from image foreground, color adjustment, exposure adjustment, sharpening, removal of noise, edge detection, etc. Image preprocessing may typically be performed but is optional.

Sound sensor 122C₁ (e.g., a microphone) in client device 101C₁ is configured and operative to acquire sound produced by subject 10 (i.e., typically voice, speech, and the like) and to produce corresponding sound data 134 that is graphically represented in FIG. 2 as a sound waveform (shown as a variation of amplitude in the time domain). Alternatively, sound data is in a frequency domain (i.e., an amplitude value for each frequency in the frequency range of sound sensor 112C₁). Sound sensor 112C₁ outputs sound data 134 to a preprocessor 136 that is configured and operative to preprocess sound data 134 by various techniques, which include for example, equalization, frequency band-pass filtering, level compression, noise reduction, etc. Sound preprocessing may typically be performed but is optional. Sound data may be multi-dimensional (not shown) (e.g., stereo sound data). Movement sensors 124C₁ is typically embodied as at least one of a multi-axis accelerometer (e.g., tri-axis for X, Y, Z Cartesian axes) that is configured to measure acceleration for each axis and to produce a multi-dimensional accelerometer output 138_X, 134_Y, and 138_Z in the time domain for each axis, as well as a multi-axis gyroscope that is configured to measure rotational velocity (i.e., roll, pitch, and yaw) and to produce a multi-dimensional gyroscope output 138ω_X, 138ω_Y, and 138ω_Z for each axis. Movement sensors 124C₁ may further include magnetometers. The outputs (signals) of the movement sensors 124C₁ are inputted into a preprocessor 140 that is configured and operative to preprocess data from multi-axis accelerometers as well as multi-axis gyroscopes by various techniques, which include for example, noise reduction, filtering, etc. Movement data preprocessing may typically be performed but is optional. Tactile sensor 126C₁ may be embodied as a touchscreen of client device 101C₁, a pressure sensor, an electrical resistance/conductivity sensor (for measuring an electrodermal response), and the like that is configured and operative to measure and produce tactile data 142 in the time domain acquired from subject 10. Tactile data 142 is inputted into a processor 144 that is configured and operative to preprocess data by various techniques, which include, noise reduction, filtering, etc. Tactile data preprocessing may typically be performed but is optional. Preprocessors 132, 136, 140, 144, in general, are configured to respectively preprocess image data 130, sound data 134, movement data 138, and tactile data 142 via signal processing techniques and algorithms (e.g., filtering, error correction, etc.). Preprocessors 132, 136, 140, and 144 are implemented in hardware, software, or both, and may be discrete components or integrated into one processor.

Systems 100₁ and 100₂ enable sensor fusion of the acquired clinical measurement data from the acquisition units (also denoted herein as “multi-modal” data defined as clinical measurement data that is acquired from different types of sources (e.g., sensors)) in the temporal domain as well as in the spatial domain so as allow for more accurate results than clinical measurement data acquirement from a single modality (i.e., one source type, e.g., image data) (e.g., by using Kalman filtering, and the like). Sensor fusion may be complete (i.e., data fused or combined from all data source types or modalities), or alternatively, may be partial (i.e., “partial sensor fusion”) where data is not fused or combined from all data source types.

After acquiring the clinical measurement data from the acquisition units (i.e., the multi-modal), systems 100₁ and 100₂ are configured and operative to extract potential stroke features (e.g., attributes and their corresponding value) from the clinical measurement data, according to at least one predetermined stroke assessment criterion. A predetermined stroke assessment criterion is any characterizing mark, trait, standard, or rule for evaluating, assessing, deciding, or testing a likelihood to a presence of a stroke condition.

Reference is now further made to FIG. 3, which is a schematic illustration of an example extraction of potential stroke features from clinical measurement image data, according to the disclosed technique. FIG. 3 shows time-sequential images 130₁, 130₂, 130₃, . . . constituting acquired clinical measurement image data 130 of subject 10. Each of processor 104 (FIG. 1A) and server processor 104S (FIG. 1B) is configured and operative to extract potential stroke features from the clinical measurement image data. The process of extraction involves selection and isolation, and is operative in both the time domain, as well as in the spatial domain. Specifically, in the time domain, extraction involves selection and isolation of at least one image (frame) captured at a particular point in time, or a plurality of images captured at distinct points in time (or time range(s)). An extracted image is denoted herein as a point of interest (POI) in time, or “time POI” for brevity. A plurality of images captured at a particular time range is denoted herein as a region of interest (ROI) in time, or “time ROI” for brevity. Particularly for the spatial domain, extraction involves selection and isolation of at least one part in an image (i.e., a pixel having an associated spatial location (e.g., an (x, y) coordinate in the image), or group of pixels each having their respective spatial locations). Each extracted pixel from an extracted image is denoted herein as a POI in the spatial domain, or for brevity “spatial POI”. A plurality of extracted contiguous group of pixels is an image object denoted herein as a ROI in the spatial domain, or “spatial ROI” for brevity. In the example of FIG. 3, processors 104 and 104S extract a time POI, i.e., image 130₄, with respect to images 130₁, 130₂, 130₃, . . . , i.e., as well as a spatial ROI 160₁ (i.e., the captured image of the head of subject 10). The process of spatial ROI extraction may involve image segmentation techniques. Spatial ROI 160₁ may include at least one nested spatial ROI, which is a ROI within a ROI (i.e., a partial ROI within a master ROI). As diagrammatically shown in FIG. 3, spatial ROI 160₁ includes nested spatial ROIs 160₂ (a forehead wrinkle of subject 10), 160₃ (right eye), 160₄ (left eye), 160₅ (a left side smile wrinkle), 160₆ (a right side smile wrinkle), and 160₇ (lips). Alternatively, processors 104 and 104S are configured and operative to extract spatial ROIs 160₂, 160₃, 160₄, 160₅, 160₆, and 160₇ such that they don't constitute nested spatial ROIs (i.e., directly from image 130₄). The extraction of features, i.e., spatial ROIs 160₂, 160₃, 160₄, 160₅, 160₆, and 160₇ by processors 104 and 104S is generally performed according to at least one predetermined stroke assessment criterion, as defined hereinabove.

FIG. 3 shows an example of extraction of potential stroke features from clinical measurement image data, for the purposes of explicating the disclosed technique. Extraction of potential stroke features from other types of clinical measurement data is likewise applicable according to the principles of the disclosed technique. Reference is now further made to FIG. 4, which is a schematic illustration showing examples of the extraction of potential stroke features from various types of clinical measurement data at various times, according to the disclosed technique. FIG. 4 shows the extraction of potential stroke features from image data 130 (images 130₁, 130₂, 130₃, . . . ) (as detailed in FIG. 3), as well as sound data 134 in the time domain, movement data 138_X, 134_Y, 138_Z, 138ω_X, 138ω_Y, 138ω_Z in the time domain, and tactile data 142 in the time domain. Processors 104 and 104S are configured and operative to extract potential stroke features in image data 130, i.e., POI image 130₄ in the time domain, denoted herein as time t₁ (or simply “t₁”), as well as spatial features within image 130₄, namely, spatial ROIs 160₂, 160₃, 160₄, 160₅, 160₆. Furthermore, processors 104 and 104S are configured and operative to extract potential stroke features in sound data 134 denoted as ROI 162₁ in the time domain transpiring between t₂ and t₃ (along a time axis, where t₂<t₃), potential stroke features in movement data 138 denoted as multi-dimensional ROI 164₁ (i.e., that includes 164_1X, 164_1Y, 164_1Z, 164₁ω_X, 164₁ω_Y, 164₁ω_Z in the time domain transpiring between time t₄ and t₅, as well as potential stroke features in tactile data 142 denoted as ROI 166₁ in the time domain transpiring between time t₆ and t₇.

The extraction of potential stroke features from different types of clinical measurement data (i.e., acquired from different sources (e.g., sensors) of data, i.e., “multi-modal data”) may time-wise correspond to each other (i.e., be synchronized in time), may overlap in time (at least partially or fully), or may be mutually exclusive in time. The example in FIG. 4 shows that POI image 130₁ acquired at t₁ is included in a time range [t₂,t₃] between t₂ and t₃ (i.e., t₂≤t₁≤t₃). This indicates that extracted potential stroke features 160₂, 160₃, 160₄, 160₅, and 160₆ from image data 130 coincide in the time range [t₂,t₃] with extracted potential stroke feature 162₁ extracted from sound data 134. According to another example in FIG. 4, extracted potential stroke features 164₁ do not coincide in time with extracted potential stroke feature 166₁, although these extracted features may be linked to a common potential stroke event whose likelihood is estimated by the disclosed technique. The disclosed technique may employ correlation, as well as cross-correlation techniques to assess a statistical relationship between multi-modal data that occur in proximity to each other (e.g., within a particular time range) possibly interrelated to a common potential (suspected) stroke event, also denoted herein as “cerebrovascular accident” (CVA).

The POIs and ROIs (in the time and spatial domains) are extracted according to least one predetermined stroke assessment criterion (typically a plurality of individual criteria) that may be: (1) a standardized test (e.g., the National Institutes of Health Stroke Scale (NIHSS), the face-arm-speech-time (FAST) test, the ABCD² score, the CHADS₂ score and its refinement the CHA₂DS₂VASc score (calculates stroke risk for subjects with non-rheumatic atrial fibrillation (“AF” or “A-fib”) (early stage diagnosis), Los Angeles Pre-hospital Stroke Screen (LAPSS) test, etc.); (2) a non-standardized test; (3) a modified test based on a standardized test (e.g., a modified NIHSS (mNIHSS); (4) a customized test based on a standardized test (e.g., NIHSS), where the customized version doesn't necessarily include all sub-tests of the standardized test, and may include variations of sub-tests, as well as additional sub-tests, etc.); and (5) at least one characterizing mark or trait that can serve as a direct and/or indirect possible indication in the assessment of the likelihood of a stroke condition (e.g., a determined statistical correlation between clinical measurement data and likelihood to a stroke condition). Systems 100₁ and 100₂ are configured and operative to run a computerized version of each selected stroke assessment test (whether standardized or non-standardized). Tables 1-12 hereinbelow show examples of predetermined stroke assessment criteria based on NIHSS, a computerized version of which according to the disclosed technique is denoted interchangeably herein as “modified NIHSS” (mNIHSS), and “adopted NIHSS”. As aforementioned, the extraction of clinical measurement data by the acquisition units may be with user intervention (e.g., prompting the subject to perform instructions, such as raising hands, speaking, etc.), be without user intervention (e.g., automatic), or be a hybridizes between (partial) user intervention and (partial) user non-intervention.

In the alternative implementation, the acquirement of of clinical measurement data is achieved without user (subject) intervention (i.e., non-interactive approach), for example automatically, by monitoring the subject's normal activities (e.g., during walking, sitting, standing, talking, during computer use, smartphone use, etc.). Systems 101₁ and 101₂ acquire the clinical measurement data and extract potential stroke features from the acquired clinical measurement data without prompting the user to perform tasks required for standardized tests (e.g., NIHSS) or other types of user interactive tests. This implementation may typically employ machine learning techniques for modeling the user's various routine activities via training data that is inputted into and/or acquired by systems 101₁ and 101₂.

Following the extraction of the potential stroke features from the clinical measurement data, the extracted potential stroke features are then compared with classified sampled data in a patient database (interchangeably denoted herein as “database”) acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition. To further detail this step of the disclosed technique, reference is now made to FIG. 5, which is a schematic diagram illustrating comparison between extracted potential stroke features and classified data in a database, constructed and operative according to the disclosed technique. FIG. 5 illustrates an exemplary implementation of internal elements (blocks) within server database 102S (likewise applicable to database 102) and server processor 104S (likewise applicable to processor 104) that are involved in the comparing step of the disclosed technique. Specifically, server database 102S includes a classified data section 180 that includes a positive stroke dataset 182, and a negative stroke dataset 184. Server database 102S further includes subject-specific data stored therein that includes subject-specific extracted potential stroke features 160₂, 160₃, 160₄, 160₅, 160₆, 160₇, 162₁, 164₁, 166₁, as well as a subject-specific baseline(s) dataset 186. The subject specific data is part of the user (subject's) account stored in server database 102S of server 101S. Alternatively, all or at least part of the subject-specific data is stored in a memory storage (i.e., at least one of the hardware device, in software, firmware, removable storage medium, etc.) of client device 101C₁ associated with the subject (e.g., an owner, a user, of the client device). For example, baseline(s) dataset 186 is stored in memory storage of the client device (i.e., “in-memory database”) and the extracted potential stroke features are stored on server database 102S. Other combinations of distributing the subject-specific data among various data storage entities (e.g., as in a distributed database) that may include server database 102S, client devices 101, as well as external cloud database(s), are also viable options according to the disclosed technique.

Baseline(s) dataset 186 includes at least one entry 186_i that is a time-dependent baseline profile of subject 10 (where i denotes a general index of the i-th entry in baseline dataset 186 at a particular point in time). There may typically be a plurality of baseline entries for subject 10 that are time-wise ordered, as shown in FIG. 5. Positive stroke dataset 182 includes a plurality of entries 182_i, (where i denotes a general index of an i-th entry), where each entry 182_i is sampled data associated with an individual positively diagnosed (and verified) with at least one stroke condition. Each entry 182_i constitutes as labeled sampled data (interchangeably denoted herein “labeled sampled data entry”, and “labeled sampled data item”). Each entry 182_i in positive stroke dataset 182 acquired from an individual positively diagnosed with a stroke condition includes at least two fields: stroke type (i.e., ischemic, and hemorrhagic), and its corresponding brain location (generic)). There may be only one entry sampled from a particular individual in a population, or a plurality of entries sampled from the same individual. Each entry 182_i includes at least one quantified extracted feature that is associated with a probability threshold that may be indicative to at least one stroke condition. For example, an individual positively diagnosed with a stroke condition may experience partial facial paralysis that manifests as one-sided facial drooping of particular facial landmarks. An entry in positive stroke dataset 182 corresponding to that example can be represented by a multi-dimensional matrix or vectors representing individual facial landmarks points (coordinates), the direction and magnitude of change with respect to corresponding features on the other side of the face (e.g., drooping of one eye with respect to another). Note that extracted potential stroke features can possess attributes that may indicate, for example facial paralysis, which in itself may not necessarily be conclusive to the presence of a stroke condition, as there may be other causes such as Bell's palsy, and Lyme disease that exhibit similar clinical features. The disclosed technique therefore relies on extracting a plurality of potential stroke features so as to enable differential diagnosis of a stroke condition from various other unrelated diseases, symptoms, and conditions, as well as for the purpose of enhancing the estimation to the probability of a stroke condition. This enables differential diagnosis of stroke mimics that are generally non-vascular conditions that simulate acute ischemic stroke (e.g., seizures, psychiatric disorders, etc.) but are not a stroke. Another example of an entry in positive stroke dataset 182 includes a particular parametric representation of a voice data model that is characteristic to slurred speech of an individual positively diagnosed with at least one stroke condition. The individual entries 182_i in positive stroke dataset 182 are labeled sampled data that are classified according to various criteria type (e.g., image data, sound data), quantitative measures, and the like.

Negative stroke dataset 184 includes a plurality of entries 184i where each entry 184i includes data sampled from an individual negatively diagnosed for a stroke condition (i.e., are verified not to have a stroke condition (“ground truth”)). Likewise, there may be only one entry sampled from a particular individual in a population, or a plurality of entries sampled from the same individual. Processor 104S includes a main comparator block 190, which in turn may include a plurality of individual comparators 190₁, 190₂, 190₃, 190₄, 190₅, 190₆, 190₇, 190₈, 190₉ (collectively denoted herein as “comparators 190₁-190₉”). Main comparator block 190 may be implemented in at least one of hardware, software, firmware, and a combination thereof. Main comparator block 190 is configured and operative to compare subject-specific extracted potential stroke features 160_1-7, 162₁, 164₁, and, 166₁ with classified sampled data in positive stroke dataset 182. Specifically, comparator 190₁ compares extracted potential stroke feature 160₁ with positive stroke dataset 182 so as to produce a result that represents a quantitative measure that indicates how extracted potential stroke feature 160₁ matches with corresponding entries 182_i of the same type (i.e., image data). Similarly, comparators 190₂-190₉ respectively compare extracted potential stroke features 160_2-7, 162₁, 164₁, and 166₁ with positive stroke dataset 182, so as to produce respective outputs that represent quantitative measures that indicate how these extracted potential stroke features match with corresponding entries 182_i of their same type. An output of the comparison is a quantitative measure to how a particular extracted potential stroke feature matches either one of positive stroke dataset 182, negative stroke dataset 184, or both (i.e., an indeterminate result, e.g., in case there's a 50% match to positive stroke dataset 182 and 50% match to negative stroke dataset 184). In addition (and optionally), comparators 190₁-190₉ are configured and operative to compare extracted potential stroke features 160₁-160₇, 162₁, 164₁, and 166₁ with negative stroke dataset 184, so as to produce respective outputs that represent quantitative measures indicating how these extracted potential stroke features match with corresponding entries 184_i of their same type. Generally, the use of both positive stroke dataset 182 and negative stroke dataset 184 in the comparison enhances the estimation of the likelihood in determining the presence of a stroke condition of the subject.

Alternatively, there is one comparator associated for each modality type (e.g., image data, sound data, etc.) (not shown). According to this alternative configuration, one comparator is used to compare extracted potential stroke features 160₁, 160₂, 160₃, 160₄, 160₅, 160₆, and 160₇ (image data) with classified data in positive stroke dataset 182, and optionally with negative stroke dataset 184. Similarly, there are separate and distinct comparators, respectively employed to compare extracted potential stroke feature 162₁ (sound data), extracted potential stroke feature 164₁ (movement data), as well as extracted potential stroke feature 166₁ (tactile data) with classified data in positive stroke dataset 182, and optionally with negative stroke dataset 184. Further alternatively, there is one comparator that is configured and operative to perform all the required comparisons.

According to a particular configuration, main comparator block 190 is implemented as a machine learning classifier (denoted herein “MLC”) that is configured and operative to employ both positive stroke dataset 182 as well as negative stroke dataset 184, both of which constitute as training data in which the MLC bases and produces an output that corresponds to an input of an extracted potential stroke feature. Generally, the input to the MLC is an extracted (and preprocessed) potential stroke feature, and the corresponding output of the MLC is a quantitative measure to how the inputted extracted potential stroke feature fits to the trained data, the latter of which can be represented by a mathematical model, as will be further detailed hereinbelow. In one implementation, there is a plurality of different MLCs (i.e., equal to the number of comparators 190₁-190₉) for each subject-specific extracted potential stroke feature. According to another implementation, there is one MLC for each modality type (e.g., image data, sound data, etc.) (not shown). According to a further implementation, there is one MLC (e.g., main comparator 190 is implemented by one MLC). Typical examples of MLCs include artificial neural networks (ANNs), decision trees, support vector machines (SVMs), Bayesian networks, k-nearest neighbor (KNN) classifiers, regression analysis (e.g., linear, logistic), etc.

To further explicate the particulars of the disclosed technique, reference is now further made to FIG. 6, which is a schematic diagram partly showing procedures involved in producing an estimation to the likelihood of a stroke condition, according to the principles of the disclosed technique. FIG. 6 shows processor 104S (or 104) that includes main comparator block 190 having a plurality of discrete comparators 190₁-190₉ (e.g., implemented by MLCs), as well as a modeler 192. Modeler 192 may be subdivided into a positive stroke modeler 192₁ sub-block and a negative stroke modeler 192₂ sub-block. Modeler 192 is generally implemented in at least one of hardware, software, firmware, and a combination thereof. Modeler 192 is generally configured and operative to construct mathematical models from the positive stroke dataset 182 as well as from negative stroke dataset 184. Specifically, positive stroke modeler 192₁ sub-block is configured and operative to construct mathematical models 194₁, 194₂, 194₃, 194₄, 194₅, 194₆, 194₇, 194₈, and 194₉from positive stroke dataset 182. Analogously, negative stroke modeler 192₂ sub-block is configured an operative to construct mathematical models 196₁, 196₂, 196₃, 196₄, 196₅, 196₆, 196₇, 196₈, and 196₉ from negative stroke dataset 184. The mathematical model may be, for example represented by a probability distribution function (also denoted interchangeably herein as “probability density function”, and “PDF” for short) that is basically a function having at least one input and whose possible output values are probabilities of occurrence of different results/outcomes of an experiment (i.e., different outcomes and their associated probabilities). There are various types of PDFs (e.g., Gaussian distribution function, Gamma distribution function, etc.) each of which is defined by its respective parameters (e.g., mean (μ), variance (σ²), and the like). Modeler 192 is configured and operative to construct the individual models 194₁-194₉ and 196₁-196₉ which includes determining the parameters for each model (not shown). The disclosed technique may continuously update (“learn”) each model via its defining parameters by using training data (in database 102) through a process of parameter estimation and optimization, such that the best values for these parameters are determined e.g., via maximum-likelihood techniques.

Each comparator (also herein MLC) 190₁-190₉ is configured and operative to receive as input the extracted and preprocessed potential stroke features (as detailed in conjunction with FIG. 5), which may be termed herein as a “feature vectors”, denoted respectively as v₁, v₂, v₃, v₄, v₅, v₆, v₇, v₈, and v₉ in FIG. 6. Each MLC or comparator is then configured and operative to assess how each respective input feature vector compares with positive stroke dataset 182 and negative stroke dataset 184, and then further configured to output a result that optimally matches a sample space in data sets 182 and 184. The comparison result the can be represented as an interval in the sample space of positive stroke dataset 182 and/or as an interval in the sample space of negative stroke dataset 184. Processor 104S is then configured to compute a respective probability by integrating the PDF over that interval as denoted by 198₁, 198₂, 198₃, 198₄, 198₅, 198₆, 198₇, 198₈, and 198₉ in FIG. 6. Particularly, comparator 190₁ compares feature vector v₁ with positive stroke dataset 182 (the plurality of entries 182_i thereof) as well as negative stroke dataset 184 (the plurality of entries 182_i thereof) and determines an optimal match of this comparison by outputting at least one interval [a₁, a₂] in the sample space (i.e., in datasets 182 and 184), where the optimal match occurs (i.e., in positive stroke dataset 182 or negative stroke dataset 184). In this particular example the optimal match occurs in positive stroke dataset 182, the corresponding model of which is PDF 194₁. Processor 104S integrates PDF 194₁ over the determined interval [a₁, b₁], represented by 198₁, thereby yielding a probability p₁. Note that in this example, the interval is one-dimensional, however, the sample space is typically multi-dimensional and so is the integration of several variables (e.g., a multiple integral, and multivariate probability distribution). Analogously, comparator 190₂ compares feature vector v₂ with positive stroke dataset 182 (the plurality of entries 182_i thereof) as well as negative stroke dataset 184 (the plurality of entries 182_i thereof) and determines an optimal match of this comparison thereby outputting at least one interval [a₂, b₂] in the sample space where the optimal match occurs. In this particular example the optimal match occurs in negative stroke dataset 184, the corresponding model is PDF 196₂. Processor 104S integrates PDF 196₂ over the determined interval [a₂, b₂], represented by 198₂ thereby yielding a probability p₂. Analogously, processor 104S performs this process for v₃, v₄, v₅, v₆, v₇, v₈, and v₉ thereby yielding respective probabilities p₃, p₄, p₅, p₆, p₇, p₈, and p₉. Although the above description is with respect to PDFs is for continuous random variables, the disclosed technique is likewise applicable to probability mass functions (PMFs) of discrete random variables. Without loss of generality, the PDF approach is an example implementation of the disclosed technique.

In determining a probability for a type of a stroke condition, and a probability of a corresponding stroke location, processor 104S is configured and operative to use the results of the comparisons between the potential stroke features and the classified sampled data in the positive stroke dataset (as well as optionally with the negative stroke dataset). To further detail the particulars of this aspect of the disclosed technique, reference is further made to FIG. 7, which is a schematic diagram further showing procedures involved in producing an estimation to the likelihood of a stroke condition, according to the principles of the disclosed technique. FIG. 7 shows server processor 104S further including a comparator 200 that may be implemented for example by a MLC, an ANN, and the like. Comparator 200 receives probabilities p₁, p₂, p₃, p₄, p₅, p₆, p₇, p₈, and p₉ and is configured and operative to determine probabilities P_T and P_L as outputs 202₁ and 202₂, respectively by use of database 102S. As aforementioned, each entry 182_i in positive stroke dataset 182 that has been acquired from an individual positively diagnosed with a stroke condition includes at least two fields: (1) stroke type; and (2) its corresponding brain location. According to one standard implementation of comparator 200, the collective as well as individual contributions of the probabilities p₁-p₉ are weighted so as to find an optimal match with respect to sampled data entries in database 102S. According to another implementation, comparator 200 is an MLC (e.g., ANN) that is pre-trained (e.g., via an MLC) to yield a result that optimally fits with labeled sampled data in database 102. Comparator 200 yields an output 202₁ as a probability P_T for a type of stroke condition of subject 10, and an output 202₂ as a probability P_L for a corresponding location of a stroke condition with respect to a brain location of subject 10. The determined probability of a stroke condition at a particular brain location may be described in terms of a generic brain location, as various brain locations, areas, or regions are associated with different brain functions (e.g., motor and speech production, voluntary eye movement, vision, language comprehension, equilibrium and muscle coordination, etc.). For example, a stroke in the posterior cerebral artery (PCA) may typically affect vision; while cerebellar strokes may typically affect balance and coordination, etc. Processor 101S conveys outputs 202₁ and 202₂ to communication module 108, which in turn is configured and operative to communicate (e.g., transmit) these outputs through signals encoding data pertaining to P_T and P_L to communication module 108C₁ of client device 101C₁. Communication module 108C₁ receives the data encoded signals and provides them to client processor 104₁, which in turn is configured and operative to direct user interface 110C₁ to present the P_T and P_L data via at least one sensory modality, e.g., visually via a display 111C₁, audibly (not shown), etc. Display 111C₁ is configured and operative to display the determined stroke type and its probability P_T as well as a corresponding stroke location and its respective probability P_L, as well as a graphical representation of a brain model that includes a superimposed highlighted region 206 that corresponds to the determined stroke location. Furthermore, systems 101₁ and 101₂ of the disclosed technique may use baseline dataset 186 for augmenting the estimated probabilities P_T and P_L by using its corresponding data to minimize false positive classifications, as well as false negative classifications. Baseline dataset 186 is, according to a particular implementation, inputted to main comparator 190 (FIG. 5) so as to take into account time-dependent baseline entries 186_i in the comparison (this also applies to the MLC implementation of the disclosed technique). In case baseline dataset 186 includes baseline subject-specific entries 186_i acquired at different times, systems 100₁ and 100₂ are configured and operative to compare between them and to use their deltas (i.e., differences) for the purpose of augmenting at least one of: (1) the comparison (i.e., between potential stroke features and classified sampled data), and (2) the determination of a probability of stroke type and a probability of corresponding stroke location.

In addition, communication module 108S is configured and operative to communicate outputs 202₁ and 202₂ through signals encoding data pertaining to P_T and P_L to external communication devices 220 (also denoted herein interchangeably as mobile or immobile “patient management console units”, “management console units”, and “management console”) of various entities such as: (1) a medical emergency response service (e.g., operating an ambulance service); (2) medical professional(s) (e.g., a doctor specialized in treating strokes, a personal doctor of subject 10, paramedics, etc.); (3) a hospital emergency room (ER) including a neuroimaging department (e.g., employing computerized tomography (CT), magnetic resonance imaging (MRI) in general and functional-MRI (fMRI) in particular, positron-emission tomography (PET), and the like); (4) subject's 10 relatives (e.g., family member(s)); (5) an operator of systems 101₁ and 101₂ of the disclosed technique; and the like. Probabilities P_T and P_L transmitted to external communication devices 220 also include information about subject 10 that can include name, identification number, age, current location, etc. The system and method of the disclosed technique are configured and operative to present (e.g., provide, display) at least one ROI, and POI in the extracted clinical measurement data that corresponds with a highest estimated likelihood of the stroke condition, according to the determined probabilities P_T and P_L so as to reduce time for treatment by medical staff, physician, etc.

Reference is now made to FIG. 8, which is a schematic diagram of a method, generally referenced 250, for estimating a likelihood of a stroke condition of a subject, constructed and operative in accordance with the disclosed technique. Method 250 includes a plurality of procedures (steps), which initiates with procedure 252. In procedure 252, clinical measurement data pertaining to a subject is acquired. The clinical measurement data includes at least one of image data, sound data, movement data, and tactile data. With reference to FIGS. 1A, 1B, and 2, acquisition unit 106 of system 100₁ (FIG. 1A) and acquisition units 106C₁, 106C₂, . . . , 106C_N of respective client devices 101C₁, 101C₂, . . . , 101_N of system 100₂ (FIG. 1B) include at least one of image sensor 120C₁ (FIG. 2, exemplary shown for client device 101C₁), sound sensor 122C₁, movement sensor 124C₁, and tactile sensor 126C₁ that are each configured respectively to acquire image data 130, sound data 134, movement data 138, and tactile data 142 pertaining to subject 10.

In procedure 254, from the clinical measurement data, potential stroke features are extracted according to at least one predetermined stroke assessment criterion. With reference to FIGS. 1A, 1B, 34, and Tables 1-12 potential stroke features are extracted, via processors 104 (FIG. 1A) and 104S (FIG. 1B) as follows. Spatial ROIs 160₂, 160₃, 160₄, 160₅, 160₆, and 160₇ from a time POI, i.e., image 130₄ are extracted from image data 130. ROI 162₁ is extracted from sound data 134. Multi-dimensional ROI 164₁ is extracted from movement data 138. ROI 166₁ is extracted from tactile data 142. The potential stroke features are extracted according to at least one predetermined stroke assessment criterion in Tables 1-12.

In procedure 256, the potential stroke features are compared with classified sampled data acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset. With reference to FIGS. 1B and 5, main comparator 190 (e.g., MLC) (FIG. 5) which may include a plurality of comparators 190₁-190₂ compares (extracted) potential stroke features 160₁-160₇, 162₁, 164₁, and 166₁ with classified data section of database 180 (FIG. 5) of server database 102S (FIG. 1B) acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition. The classified data pertaining to the plurality of subjects positively diagnosed with at least one stroke condition is part of positive stroke dataset 182. Optionally additionally, the potential stroke features are compared with classified sampled data in a patient database acquired from a plurality of subjects, each negatively diagnosed with a stroke condition. The classified data pertaining to the plurality of subjects negatively diagnosed with a stroke condition is part of negative stroke dataset 184 (FIG. 5).

In procedure 256, a probability of a type of stroke condition, and a probability of a corresponding stroke location of the stroke condition with respect to a brain location of the subject are determined according to the comparing procedure. With reference with FIGS. 6 and 7, modeler (block) 192 (of processor 104S) (FIG. 6) constructs models from positive stroke dataset 182 as well as optionally from negative stroke dataset 184. Main comparator (block) 190 (of processor 104S) assesses (e.g., by comparison) how each respective input feature vector compares with positive stroke dataset 182 and negative stroke dataset 184, and then outputs a result that optimally matches a sample space in data sets 182 and 184. Processor 104S computes respective probabilities p₁, p₂, p₃, p₄, p₅, p₆, p₇, p₈, and p₉ according to the results of main comparator block 190. Comparator (block) 200 (FIG. 7) of processor 104S receives probabilities p₁, p₂, p₃, p₄, p₅, p₆, p₇, p₈, and p₉ and determines probability P_T (i.e., for a type of stroke condition of subject 10), and a probability P_L (i.e., for a corresponding location of the stroke condition with respect to a brain location of subject 10).

A real-world example implementation of the disclosed technique now follows. Reference is now made to FIGS. 9A, 9B, and 9C. FIG. 9A is an exemplary screenshot, generally referenced 300, of a facial palsy subtest in an example NIHSS test performed by the system of the disclosed technique. FIG. 9B is an exemplary screenshot, generally referenced 310, of a motor arm subtest of an example NIHSS test performed by the system of the disclosed technique. FIG. 9C is an exemplary screenshot, generally referenced 320, of a language subtest of an example NIHSS test performed by the system of the disclosed technique. Screenshot 300 (also denoted herein interchangeably as “screen capture”) in FIG. 9A shows a user interaction prompt of system 100₂ for subject 10 using (directly or indirectly) client device (e.g., 101C₁) that instructs subject 10 via user interface 110C₁ (FIG. 1B) (e.g., screen) to smile and show teeth: “Please smile and show your teeth”. Acquisition unit 106C₁ of client device 101C₁ captures clinical measurement data (e.g., video data that includes image data 130 and sound data 134) pertaining to subject 10. Screenshot 310 in FIG. 9B shows a user interaction prompt of system 100₂ via client device 101C₁ instructing subject 10 to raise both hands vertically: “Please raise both hands vertically” (e.g., for 10 seconds). Acquisition unit 106C₁ of client device 101C₁ captures clinical measurement data pertaining to subject 10 during this subtest. Screenshot 320 in FIG. 9C shows a user interaction prompt of system 100₂ via client device 101C₁ instructing subject 10 to read several words displayed (e.g., appearing on a screen of user interface 110C₁): “Down to Earth.” Acquisition unit 106C₁ of client device 101C₁ captures clinical measurement data pertaining to subject 10 during this subtest.

Reference is now further made to FIG. 10, which is an exemplary screenshot, generally referenced 330, showing acquired clinical measurement data pertaining to the subject that is provided remotely to a physician via at least one external communication device. FIG. 10 shows an example of clinical measurement data in the form of video files (i.e., video examination) acquired from subject during a user interaction prompt of system 100₂ for each different subtest in the example NIHSS test. Systems 100₁ and 100₂ enables a physician to remotely view clinical measurement data shown in FIG. 10 via external communication device 220 embodied as and interchangeably denoted as a mobile patient management console unit that is installed with software and/or firmware that facilitates review and analysis of the acquired clinical measurement data.

Reference is now further made to FIG. 11, which is an exemplary screenshot, generally referenced 340, showing an example of a spatial region of interest (ROI) from a temporal point of interest (POI) in image data (video), identified as being a potential stroke feature. FIG. 11 shows an example of processor 104S identifying a potential stroke feature (i.e., an asymmetric smile), a spatial ROI in a particular frame (temporal POI) in video data (image data 130 and sound data 134. The mobile patient management console 220 enables the physician (e.g., located remotely from subject 10, such as at a hospital, clinic, etc.) to view only the relevant ROIs and POIs (i.e., and not the entire clinical measurement data, such as the entire video), thereby saving time in the treatment of a stroke event. Furthermore the systems of the disclosed technique may employ medical data compartmentalization techniques so that each physician in a medical team may have his/her own patient management console that is customized for his/her specific role and authority in the stroke diagnosis and treatment process (e.g., a list of commands, functions, and medical data (e.g. raw data, medical reports, etc.) may only be available or viable to those users authorized to view and make use of them).

Reference is now further made to FIG. 12, which is an exemplary screenshot, generally referenced 350, showing an example of image analysis of facial bilateral symmetry as a function of time for the case shown in FIG. 11 (asymmetric smile). Specifically, processor 104S is configured and operative to analyze the progress (i.e., change) of potential stroke features as a function of time, and to present the analysis to a physician (particularly, the most informative image frame(s)). FIG. 12 shows a graph of an amalgamated position of right facial landmarks as well as a graph of an amalgamated position of left facial landmarks that are related to smiling of a subject of FIG. 11, and their interrelationship.

Reference is now further made to FIG. 13, which is a collection of images acquired from several subjects, generally referenced 360, showing their lower faces superimposed with a plurality of image markers for algorithmically tracking facial landmarks, according to the disclosed technique. Specifically, FIG. 13 shows five different images of five peoples' lower faces, whose facial landmarks are superimposed by image markers (objects). Processor 104S is configured and operative to operate a program (e.g., an algorithm) that analyzes image data 130 as well as and sound data 134 typically in the form of video for each subject, such that facial landmarks (e.g., lips, face contour nose, etc.) in individual image frames from the video are identified and tracked in time so as to identify potential stroke features such as smile asymmetry, speech irregularities such as irregular connection between word pronunciation and lip movements (e.g., checked with respect to subject's baseline profile), and the like. Processor 104S is configured to derive mathematical relationships between the individually tracked image markers (and sound markers—not shown) from the clinical measurement data (in this example, video) such as speed, acceleration of the image markers between image frames, open/close time of lips, facial asymmetry characteristics, etc.

Reference is now further made to FIG. 14, which is an exemplary screenshot, generally referenced 370, showing an example of individual scores for various subtests in an example NIHSS test as yielded by the systems of the disclosed technique. Specifically, screenshot 370 shows different categories and subtests in an example NIHSS test performed on subject 10 and its corresponding scores. Processor 104S is configured and operative to calculate a score based on extracted clinical measurement data, according to at least one predetermined stroke assessment criterion, which in this case are a plurality of criteria that are part of the NIHSS test (see Tables 1-12). The mobile management consoles 220 are configured and operative to display the individual scores, as well as enable a physician to observe the scores, approve the scores, remark on individual scores, modify the scores (e.g., digitally fill, change, update the individual medical score rubrics, as well as receive automatic suggestions from the system for each one of the individual medical scale categories).

Reference is now further made to FIG. 15, which is an exemplary screenshot, generally referenced 380, showing an example of timing information relating to the onset of a detected a stroke condition of a subject and personal information relating thereto. Processor 104S calculates and continuously tracks a detected and ongoing stroke condition in real-time (i.e., real-time diagnosis), as well as operative to facilitate presentation (i.e., directs the display of) the timing information via the management consoles 220. The timing information may be presented as a continuously real-time updated time (e.g., a clock) from the onset of detected symptoms, a continuously real-time updated time (e.g., a clock) from a detected stroke condition by the system of the disclosed technique, and the like. Patient's/subject's personal information may include subject's name, age, symptoms reported by a paramedic in an ambulance, in subject's location (e.g., home, etc.).

Reference is now further made to FIG. 16, which is an exemplary screenshot, generally referenced 390, showing a further example of individual scores of various subtests performed on the subject. Screenshot 390 illustrates a typical graphical user interface (GUI) that enables interactivity with a patient, and a physician.

Reference is now further made to FIGS. 17A and 17B. FIG. 16A is an exemplary screenshot of a system-generated stroke type and stroke location interpretation report, generally referenced 410, that includes a generic brain image superimposed with a highlighted region corresponding to the location of the stroke condition, prior to medical brain imaging. FIG. 17B is an exemplary screenshot of a system-generated stroke type and stroke location interpretation report, generally referenced 410 that includes a brain image of a subject acquired via a neuroimaging technique superimposed (e.g., fused, combined image data layers, etc.) with a highlighted region corresponding to the location stroke condition, after neuroimaging. These reports generally include summarized information as well as expanded information pertaining to the brain region (location, area, volume) of suspected brain damage during two critical phases of a stroke event based on acquired neurophysiological data (i.e., clinical measurement data from a subject), as well as after neuroimaging of the brain has been performed (e.g., via CT, fMRI, PET, etc.). Processor 104S is configured and operative to generate a stroke type and stroke location interpretation report which includes: (1) a generic image of a brain (FIG. 17A) superimposed with a highlighted region indicating at least one estimated location of the detected stroke condition (“brain damage”); (2) a brain image of a subject (FIG. 17B) superimposed with a highlighted region indicating at least one estimated location of the detected stroke condition (“brain damage”); (3) information pertaining to the stroke type (ischemic, hemorrhagic), as well as stroke sub-type (e.g., large vessel occlusion (LVO), small vessel occlusion (SVO), transient ischemic attack (TIA)); (4) brain location of stroke (e.g., M2); (5) estimated probabilities (e.g., statistics, confidence levels) pertaining to the type and location of detected possible stroke (e.g., hemorrhagic: 9.3%), ischemic M1: 14.1%, ischemic M2: 55.1%; and no stroke 21.5% (as shown in FIG. 16A); and (6) an indication of brain-hemispheric location of suspected stroke condition (e.g., left hemisphere, right hemisphere). Processors 104 and 104S and thus configured and operative include the function of a “stroke scale quantification module”. Systems 101₁ and 101₂ are configured and operative to revise (e.g., update, modify, tweak) the probabilities to the type and location of stroke following the acquisition of a brain image from the subject (via at least one neuroimaging technique such as CT) as shown by the statistics in FIG. 16B with respect to those in FIG. 17A. FIG. 16B illustrates the following updated probabilities (statistics, confidence levels): no stroke: 2.4%; hemorrhagic: 1.2%; ischemic M1: 10.3%; and ischemic M2: 86.1%.

Reference is now made to FIG. 18, which is an exemplary screenshot, generally referenced 450, showing an example of a stroke patient evacuation to an emergency department (ED) of a medical healthcare facility using optimization criteria and global positioning data, according to the disclosed technique. FIG. 18 shows an aspect of controlling and managing a stroke event (CVA) where a stroke patient is evacuated to an ED that is chosen so as to minimize commuting time thereto. Processor 104S is configured and operative (e.g., with corresponding software and/or firmware) to utilize a location determining module (e.g., a satellite-based radio-navigation receiver, such as Global Positioning System (GPS) receiver—not shown) in client device 101C₁ so as localize subject with respect to at least one ED in patient's vicinity, and to optimally manage the stroke event (e.g., along a medical “management pipeline”). Example management techniques employed by the disclosed technique include choosing an ED for evacuation according to optimization criteria, such as commuter-traffic considerations, relevant stroke care workforce capacity known to be in the ED, stroke-care equipment known to be in the ED, sorting a plurality of simultaneous stroke patients among different medical healthcare facilities, aiding physicians in medical decisions (e.g., interventions and operations such as brain catheterization, administration of tissue plasminogen activator (tPA)), etc. The disclosed technique provides several “decision-making configurations” to determine (e.g., quantify) a stroke scale, among which include physician only, system only (e.g., ML, without physician intervention), as well as a hybrid configuration of both physician and system interventions. Processor 104S is further configured and operative to send an automated message via communication module 108S for scheduling urgent neuroimaging of the patient (e.g., remotely scheduling a CT scan), scheduling urgent cerebral angiography of the patient, as well as automatically alerting relevant medical teams (e.g., a stroke center team, a neuro-radiologist, an intensive care team, a neuroimaging department, a telemedicine service team, a stroke “hotline” service) to prepare for the arrival of the patient, send a stroke type and stroke location interpretation report (FIG. 17A), and to guide the neuro-radiologist toward a suspected stroke location and stroke type in advance of a CT scan (so as to enable early warning and faster preparation), etc. Processor 104S is configured and operative to provide a computerized interpretation of a CT image based on the determined estimated probabilities P_T and P_L (i.e., probability of stroke type and probability of stroke location (respectively) with respect to either a generic brain image of the subject, or a previously acquired and database-stored CT image of the subject—not shown).

Reference is now made to FIG. 19, which is an exemplary screenshot, generally referenced 470, of a system-generated stroke classification report for providing to medical personnel. Processor 104S is configured and operative to generate a stroke classification report that includes stroke scale quantification, and to send this report via communication module 108S to at least one management console 220 for at least one medical professional, typically for medical personnel or staff. The stroke classification report may be pre-approved by a neurologist. The stroke classification report may include an estimated stroke severity (e.g., NIHSS score), the most informative image (or group of images) for “manual evaluation” of the physician (a neurologist), and a confidence level (i.e., how well the system is confident in the suggested estimation).

Another aspect of the disclosed technique involves using the infrastructure of systems 100₁ and 100₂ to estimate diseases, conditions, and neurological disorders other than stroke, such as Parkinson's disease, dementia, psychiatric and mental diseases, facial visual disorders, etc. Estimation to a likelihood of a variety of medical conditions can be covered by a modified version of a stroke scale described herein and/or can be covered by other medical scales, e.g., Unified Parkinson's Disease Rating Scale (UPDRS) for Parkinson's disease). For example, some symptoms of Parkinson's disease can be detected during diagnostic tests for stroke (such as the NIHSS test).

TABLE 1
		Adopted/
		Modified
		NIHSS
		Computer-
NIHSS	NIHSS	ized	Extraction of potential
Category	Task	Test	stroke features
Level of	The examiner	Acquire and	POI and ROI extraction:
Conscious-	first assesses	record image and	Processors 104 and
ness	if the subject is	sound data from	104S are configured and
	fully alert to	subject who is	operative to extract
	his/her	instructed to	potential stroke features
(LOC)	surroundings.	provide verbal	in the image data and in
responsive-	If the subject is	feedback when	the sound data by
ness	not completely	touched on both	detecting and extracting
	alert, examiner	sides of body and	POI and ROI (e.g.,
	attempts a	then asked	image and voice
	verbal stimulus	several basic	segments of the subject
	to arouse the	questions (e.g.,	voice segments of a
	subject. Failure	age, the current	narrator, while the
	of verbal	month).	subject is being touched
	stimuli leads to		during questioning).
	an attempt to		In case there's no
	arouse the		feedback from the
	subjec via		subject, the algorithm
	repeated		outputs the maximum
	physical		score for this category.
	stimuli. If none		Measurements/Features
	of these stimuli		extraction:
	are successful		Processors 104 and
	in eliciting a		104S (e.g., employing an
	response, the		algorithm) are configured
	subject can be		and operative measures
	considered		the response time
	totally		intervals between the
	unresponsive.		narrator's commands
LOC	Subject is		(human or synthetic) and
questions	verbally asked		the patient's feedback.
	his/her age		Medical report outputs:
	and for the		1) The test
	name of the		recordings.
	current month.		2) TRUE/FASE
			indication for
			responsiveness in
			each test.
			3) Response time
			interval values
			between the
			narrator's
			instructions and
			the patient's
			responses for each
			test.
			4) NIHSS score—guided
			by the MLC.
			Note: MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous
			analyzed subjects and
			their NIHSS scores as
			ground truth).

TABLE 2
		Adopted/
		Modified
		NIHSS
		Computer-
NIHSS	NIHSS	ized	Extraction of potential
Category	Task	Test	stroke features
LOC	The	Acquire and	POI and ROI extraction:
commands	subject is	record	Processors 104 and 104S are
	instructed	images of the	configured and operative to
	to first	subject's face	extract potential stroke features
	open and	with sound	in the image data and in the
	close his/	while the	sound data by detecting and
	her eyes	subject is	extracting POI and ROI (e.g.,
	and then	instructed to	image features, and voice
	grip and	close and	segments of the subject patient
	release	open eyes,	and a narrator, while the
	his/her	then record	subject is visually responding
	hand	subject's	to the instructions: open-close
		body while he	eyes, grip-release hand.
		is instructed	If patient feedback does not
		to grip and	exist, the algorithm outputs the
		release his	maximum score for this
		hand.	category.
			Measurements/Features
			extraction:
			Processors 104 and 104S
			(e.g., via an algorithm) detect
			and tracks the eyes in the
			video and also detects blinking
			or closing of the eyes. The
			algorithm measures the
			response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			visual feedback.
			Another algorithm detects and
			tracks the hands of the patient
			in the video, and also detects
			the grip and release gestures
			in the video.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			eye tracker
			algorithm
			animation/hand
			tracking animation.
			c. Snapshots from
			the video, for
			example, eyes
			close, eyes open,
			hand grip and
			release.
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 3
		Adopted/
		Modified
		NIHSS
		Computer-
NIHSS	NIHSS	ized	Extraction of potential
Category	Task	Test	stroke features
Horizontal	Assesses	Record the	POI and ROI extraction:
eye	ability of	patient's face	Processors 104 and 104S are
movement	the patient	with camera	configured and operative (e.g.,
	to track a	and	via an algorithm) to analyze
	pen or	microphone	the video and voice signals
	finger from	while he is	and detect moments when the
	side to side	instructed to	narrator gives the current
	only using	look straight	instructions, and the moments
	his or her	into the	when the patient responds to
	eyes. This	camera.	the instructions, looking
	is designed		straight at the camera.
	to assess		If patient feedback does not
	the motor		exist, the algorithm outputs the
	ability to		maximum score for this
	gaze		category.
	towards		Measurements/Features
	the hemi-		extraction:
	sphere		Processors 104 and 104S are
	opposite		configured and operative (e.g.,
	to injury.		an algorithm) to detect and
			track the facial landmarks of
			the patient, specifically the
			eyes and the symmetry axis of
			the face. The algorithm
			analysis of the patient's gaze is
			quantified by calculating the
			head pose of the patient
			relative to the camera during
			this test. The algorithm
			measures every frame of the
			video, if one side of the
			patient's face is more gaze-
			deviated (relative to the
			camera plane) compared
			to the other side of his face.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			eye tracker/facial
			symmetry axis
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example,
			maximum gaze
			asymmetry frame,
			minimum gaze
			asymmetry frame.
			d. Eye coordination
			and the facial
			symmetry axis
			position for all
			video frames
			(including
			calculation of more
			measurements
			from these data
			such as variance,
			average speed,
			distance, etc.).
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 4
		Adopted/
		Modified
		NIHSS
		Computer-
NIHSS	NIHSS	ized	Extraction of potential
Category	Task	Test	stroke features
Visual	Assess the	Record the	POI and ROI extraction:
field test	patient's	patient's face	Processors 104 and 104S are
	vision in	with camera	configured and operative (e.g.,
	each visual	and	via an algorithm) to analyze
	field. Each	microphone	the video and voice signals
	eye is	while he	and detects the moments
	tested	instructed to	when the narrator gives the
	individually,	cover one of	current instructions, and the
	by	his eyes and	moments when the patient
	covering	then say the	responds to the instructions,
	one eye	number that	covers the eye, says the
	and then	he sees, from	presented number, for both
	the other.	a screen or	sides separately.
	Each upper	by the	If patient feedback does not
	and lower	fingers	exist, the algorithm outputs the
	quadrant is	of the	maximum score for this
	tested by	instructor,	category.
	asking the	This test is	Measurements/Features
	patient to	conducted	extraction:
	indicate	for	Processors 104 and 104S are
	how many	both sides	configured and operative (e.g.,
	fingers the	separately.	via an algorithm) to detect and
	investigator		track the eyes of the patient.
	is		The analysis of the patient's
	presenting		visual field test is quantified by
	in each		detecting the moments that the
	quadrant.		patient covers one of his eyes
			until he recognizes and says
			the presented number and the
			voice of the spoken number is
			analyzed.
			The algorithm measures the
			response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			verbal feedback.
			The algorithm also analyzes
			the speech of the patient by
			trying to recognize a valid
			number within the voice
			recording.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			eye tracker
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example, right eye
			covered, left eye
			covered, neutral
			face and face
			while speaking.
			d. Eye coordination
			for all video
			frames (including
			calculation of more
			measurements
			from these data
			such as variance,
			average speed,
			distance, etc.).
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 5
		Adopted/
		Modified
		NIHSS
NIHSS		Computer-
Cat-	NIHSS	ized	Extraction of potential stroke
egory	Task	Test	features
Facial	Facial	Record the	POI and ROI extraction:
palsy	palsy is	patient's	Processors 104 and 104S are
	partial or	face with	configured and operative (e.g.,
	complete	camera and	via an algorithm) to analyze
	paralysis	microphone	the video and voice signals
	of	while he	and to detect the moments
	portions	instructed	when the narrator gives the
	of	to smile	current instructions, and the
	the face.	and show	moments when the patient
	Typically,	his teeth	responds to the instructions,
	this		smiles and shows the teeth.
	paralysis		If patient feedback does not
	is most		exist, the algorithm outputs the
	pro-		maximum score for this
	nounced		category.
	in the		Measurements/Features
	lower half		extraction:
	of one		Processors 104 and 104S are
	facial side.		configured and operative (e.g.,
			via an algorithm) to detect and
			track the facial landmarks of
			the patient, including the
			patient's eyes, lips and facial
			symmetry axis. The analysis of
			the patient's facial palsy is
			quantified by measuring the
			asymmetry between correlated
			face part coordinates and their
			relative distance from the facial
			symmetry axis during the
			entirev ideo.
			The algorithm also measures
			the response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			visual feedback.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between narrator's
			instructions and patient's
			responses for each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			face tracker
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example, neutral
			face, most
			asymmetrical face,
			smile climax.
			d. Face part
			coordinates and
			symmetry axis
			position for all
			video frames
			(including
			calculation of more
			measurements
			from these data
			such as variance,
			average speed,
			distance, etc.).
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 6
		Adopted/
		Modified
		NIHSS	Extraction of
NIHSS	NIHSS	Computerized	potential stroke
Category	Task	Test	features
Motor	With	Record the	POI and ROI extraction:
arm	palm	patient's	Processors 104 and 104S are
	facing	upper body	configured and operative (e.g.,
	down-	with camera	via an algorithm) to analyze
	wards,	and	the video and voice signals
	have the	microphone	and to detect the moments
	patient	while he is	when the narrator gives the
	extend	instructed to	current instructions, and the
	one arm	lift his arms	moments when the patient
	90	simultane-	responds to the instructions,
	degrees	ously	lifting his hands.
	out in	to 90	If patient feedback does not
	front	degrees.	exist, the algorithm outputs the
	if the		maximum score for this
	patient is		category.
	sitting,		Measurements/Features
	and 45		extraction:
	degrees		An algorithm detects and
	out in		tracks the hands of the patient;
	front		the analysis of the patient's
	if the		motor arm is quantified by
	patient is		measuring the distance, height,
	lying		and angle of each hand
	down.		separately from the body. It
			calculated from the start of the
			motion to the end of the
			motion, and then asymmetry
			measurements between the
			hands are calculated relating to
			the whole video.
			The algorithm also measures
			the response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			visual feedback.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score-guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			hand tracker
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example, neutral
			hands, max hand
			lift, most
			asymmetric frame
			between hand
			height.
			d. Hand and body
			distances, heights,
			and angles for all
			video frames.
			e. Summarizing
			asymmetry
			measurements
			between hands
			during the whole
			video.
			Note: The MLC outputs a
			score according to the current
			NIHSS category (the classifier
			is pre-trained with previous
			analyzed subjects and their
			NIHSS scores as ground
			truth).

TABLE 7
		Adopted/
		Modified
		NIHSS
		Computer-	Extraction of
NIHSS	NIHSS	ized	potential stroke
Category	Task	Test	features
Motor	With the	Record the	POI and ROI extraction:
leg	patient in	patient's	Processors 104 and 104S are
	the supine	lower body	configured and operative (e.g.,
	position,	with camera	via an algorithm) to analyze
	one leg is	and	the video and voice signals
	placed 30	microphone	and to detect the moments
	degrees	while he is	when the narrator gives the
	above	instructed to	current instructions and the
	horizontal,	lift each one	moments that the patient
	As soon	of his legs	responds to theinstructions
	as the	separately to	to lift his legs. If patient
	patient's	30 degrees.	feedback does not exist, the
	leg is in		algorithm outputs the
	position,		maximum score for this
	the		category.
	investigator		Measurements/Features
	should		extraction:
	begin		An algorithm detects and
	verbally		tracks the legs of the patient.
	counting		The analysis of the patient's
	down from		motor leg is quantified by
	5 while		measuring the distance, height,
	simultane-		and angle of each leg
	ously		separately from the body. It
	counting		calculates from the start of the
	down on		motion to the end of the
	his or her		motion, and then asymmetry
	fingers in		measurements between the
	full view of		legs are calculated relating to
	the patient.		the whole video.
	Observe		The algorithm also measures
	any		the response time intervals
	downward		between the narrator's
	leg drift		commands (human or
	prior to the		synthetic) and the patient's
	end of the		visual feedback.
	5 seconds.		Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			hand tracker
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example, neutral
			legs, max leg lift
			for each leg, most
			asymmetric
			frames between
			legs.
			d. Leg and body
			distances, heights,
			and angles for all
			video frames.
			e. Summarizing
			asymmetry
			measurements
			between legs
			during the whole
			video.
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 8
		Adopted/
		Modified
		NIHSS
		Computer-	Extraction of
NIHSS	NIHSS	ized	potential stroke
Category	Task	Test	features
Limb	This tests	Record the	POI and ROI extraction:
ataxia	for the	patient's	Processors 104 and 104S are
	presence	face and	configured and operative (e.g.,
	of	upper	via an algorithm) to analyze
	a unilateral	body with	the video and voice signals
	cerebellar	camera and	and to detect the moments
	lesion, and	micro-	when the narrator gives the
	distinguishes	phone	current instructions, and the
	between	while he is	moments that the patient
	general	instructed	visually responds to the
	weakness	to touch	instructions, the first touch
	and inco-	the screen	of his finger to instructor's
	ordination.	or the	finger or screen, and the
	The	instructor's	second touch of the same
	patient	finger, and	finger with his nose. If
	should be	then touch	patient feedback does not
	instructed	his nose	exist, the algorithm outputs
	to first	with the	the maximum score for
	touch his	same	this category.
	or her	finger.	Measurements/Features
	finger to		extraction:
	the		An algorithm detects and
	examiner's		tracks the hands and the finger
	finger, then		used by the patient, and also
	move that		detects and tracks the patient's
	finger back		facial landmarks, including his
	to his or		nose. The analysis of the
	her nose		patient's limb ataxia is
			quantified by measuring the
			distance and speed of motion
			between the finger-to-finger
			touching and between finger-
			to-nose touching during this
			test. The video is analyzed
			from the start of the motion to
			the end of the motion, then a
			total score is calculated for the
			patient's motion performance
			(success/failure/partial
			success) relating the whole
			video.
			The algorithm also measures
			the response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			visual feedback.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			hand tracker
			algorithm
			animation and
			face tracker
			algorithm
			animation.
			c. Snapshots from
			the video, for
			example, touch
			between fingers,
			touch between
			finger to nose,
			closest point
			between nose and
			finger.
			d. Finger-to-nose
			and finger-to-
			finger distances
			and speeds for all
			video frames.
			e. Summarizing
			score measure for
			success
			failure/partial
			success of the
			touching during
			the whole video.
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 9
		Adopted/
		Modified
		NIHSS
		Computer-	Extraction of
NIHSS	NIHSS	ized	potential stroke
Category	Task	Test	features
Language	This item	Record the	POI and ROI extraction:
	measures	patient's	Processors 104 and 104S are
	the	responses	configured and operative (e.g.,
	patient's	with camera	via an algorithm) to analyze
	language	and	the video and voice signals
	skills. After	microphone	and to detect the moments
	completing	while the	when the narrator gives the
	items	instructor is	current instructions, and the
	(Tables) 1-	guiding the	moments that the patient
	8, it is	patient to	visually and verbally responds
	likely the	read	to the instructions, reading a
	investigator	sentences	sentence or naming an object
	has gained	and describe	from a picture.
	an approx-	a picture of	If patient feedback does not
	imation	several	exist, the algorithm outputs the
	of the	objects,	maximum score for this
	patient's	which is	category.
	language	presented to	Measurements/Features
	skills;	the patient	extraction:
	however, it	on the	An algorithm detects and
	is important	mobile	tracks the patient's facial
	to confirm	device	landmarks, including his
	this	screen.	mouth. The algorithm also
	measure-		detects the voice segments
	ment		that the narrator or the patient
	at this		speaks based on the mouth
	time The		movement and audio signals.
	stroke		The analysis of the patient's
	scale		language and speech is
	includes a		quantified by measuring the
	picture of a		similarity between the recorded
	picture of a		voice segments of the patient
	scenario, a		and the words and objects that
	list of		are presented to him during the
	simple		test.
	sentences,		The video is analyzed from the
	a figure of		start of the test to the end of
	assorted		the test, then a total score is
	random		calculated for the patient's
	objects,		verbal feedback
	and a list of		(success/failure/partial
	words. The		success) relating to the whole
	patient		video. The algorithm also
	should be		measures the motion of the
	asked to		patient's mouth.
	explain the		The algorithm also measures
	scenario		the response time intervals
	depicted in		between the narrator's
	the first		commands (human or
	figure.		synthetic) and the patient's
	Next, he or		visual feedback.
	she should		Medical report outputs:
	read the		1) The test recordings.
	list of		2) TRUE/FALSE value for
	sentences		each test regarding the
	and name		responsiveness.
	each of the
	objects
	depicted in
	the next
	figure.

TABLE 10
		Adopted/
		Modified
		NIHSS
		Computer-	Extraction of
NIHSS	NIHSS	ized	potential stroke
Category	Task	Test	features
Speech	Dysarthria is	Record the	POI and ROI extraction:
	the lack of	patient's	Processors 104 and 104S are
	motor skills	responses	configured and operative (e.g.,
	required to	with	via an algorithm) to analyze
	produce	camera and	the video and voice signals
	understand-	microphone	and to detect the moments
	able speech.	while the	when the narrator gives the
	Dysarthria is	instructor is	current instructions, and the
	strictly a	guiding the	moments that the patient
	motor	patient to	visually and verbally responds
	problem and	read	to the instructions, reading a
	is not	sentences	sentence or naming an object
	related to	and	from a picture.
	the patient's	describe a	If patient feedback does not
	ability to	picture of	exist, the algorithm outputs the
	comprehend	several	maximum score for this
	speech.	objects,	category.
	Strokes that	which is	Measurements/Features
	cause	presented to	extraction:
	dysarthria	the patient	An algorithm detects and
	typically	on the	tracks the patient's facial
	affect areas	mobile	landmarks, including his
	such as the	device	mouth. The algorithm also
	anterior	screen.	detects the voice segments
	opercular,		that the narrator or the patient
	medial		speaks based on the mouth
	prefrontal		movement and audio signals.
	and		The analysis of the patient's
	premotor,		language and speech is
	and anterior		quantified by measuring the
	cingulate		similarity between the recorded
	regions.		voice segments of the patient
	These brain		and the words and objects that
	regions are		are presented to him during the
	vital in		test.
	coordinating		The video is analyzed from the
	motor		start of the test to the end of
	control of		the test, then a total score is
	the tongue,		calculated for the patient's
	throat, lips,		verbal feedback
	and		(success/failure/partial
	lungs. To		success) relating to the whole
	perform this		video. The algorithm also
	test, the		measures the motion of the
	patient is		patient's mouth.
	asked to		The algorithm also measures
	read from		the response time intervals
	the list of		between the narrator's
	words		commands (human or
	provided		synthetic) and the patient's
	with the		visual feedback.
	stroke scale		Medical report outputs:
	while the		1) The test recordings.
	examiner		a. TRUE/FALSE
	observes		value for each test
	the patient's		regarding the
	articulation		responsiveness.
	and clarity
	of speech.

TABLE 11
		Adopted/
		Modified
		NIHSS
		Computer-	Extraction of
NIHSS	NIHSS	ized	potential stroke
Category	Task	Test	features
Sensory	Sensory	Record the	POI and ROI extraction:
	testing is	patient's	Processors 104 and 104S are
	performed	responses	configured and operative (e.g.,
	via pinpricks	with	via an algorithm) to analyze
	in the	camera and	the video and voice signals
	proximal	micro-	and to detect the moments
	portion of	phone	when the narrator speaks the
	all four	while the	current instructions, and
	limbs. While	instructor	while he touches the patient.
	applying	is applying	The algorithm also analyzes
	pinpricks,	pinpricks	the moments that the patient
	the	on the	visually and verbally responds
	investigator	patient's	to the instructions and
	should ask	body on	touching.
	whether or	both sides	If patient feedback does not
	not the	separately.	exist, the algorithm outputs the
	patient feels		maximum score for this
	the pricks,		category.
	and if he or		Measurements/Features
	she feels the		extraction:
	pricks		An algorithm detects the voice
	differently		segments when the narrator
	on one side		asks the patient if he feels his
	when		touching. The algorithm also
	compared to		detects the voice feedback of
	the other		the patient to the touching. The
	side.		analysis of the patient's
			responses is quantified by
			analyzing the voice feedback to
			the touching, specifically if the
			feedback is positive or
			negative.
			The video is analyzed from the
			start of the test to the end of
			the test, then a total score is
			calculated to summarize the
			verbal feedback of the touching
			(negative/positive/partial)
			relating to the whole video.
			The algorithm also measures
			the response time intervals
			between the narrator's
			commands (human or
			synthetic) and the patient's
			visual feedback.
			Medical report outputs:
			1) The test recordings.
			2) TRUE/FALSE value for
			each test regarding the
			responsiveness.
			3) Response time intervals
			between the narrator's
			instructions and the
			patient's responses for
			each test.
			4) NIHSS score—guided
			by the MLC.
			5) According to the
			detected region of
			interest:
			a. Cropped videos
			for each test.
			b. Cropped videos
			for each test with
			mouth tracker
			algorithm
			animation and the
			moments of
			answering of the
			patient.
			c. Snapshots from
			the video, for
			example, while
			patient is being
			touched.
			d. Summarizing
			score measure for
			negative/positive
			response of
			patient touching
			feedback during
			the whole video.
			Note: The MLC outputs a
			score according to the
			current NIHSS category
			(the classifier is pre-
			trained with previous analyzed
			subjects and their NIHSS
			scores as ground truth).

TABLE 12
		Adopted/	Ex-
		Modified	trac-
		NIHSS	tion of
		Computer-	potential
NIHSS	NIHSS	ized	stroke
Category	Task	Test	features
Extinction	Sufficient information regarding	Note: The extinction
and	this item may have been obtained	and inattention
inattention	by the examiner to properly score	category is covered
	the patient in items 1-10. However,	by the other NIHSS
	if any ambiguity exists, the	categories described
	examiner should test this item via	in this table (For
	a technique referred to as “double	example, see “LOC
	simultaneous stimulation”. This is	Commands”
	performed by having the patient	category,
	close his or her eyes and asking	specifically the eyes
	him or her to identify the side on	closing test).
	which they are being touched by
	the examiner. During this time,
	the examiner alternates between
	touching the patient on the right
	and left a sides. Next, the
	examiner touches the patient on
	both sides at the same time. This
	should be repeated on the patient's
	face, arms, and legs. To test
	extinction in vision, the
	examiner should hold up one
	finger in front of each of the
	patient's eyes and ask the patient
	to determine which finger is
	wiggling or if both are wiggling.
	The examiner should then
	alternate between wiggling
	each finger and wiggling both
	fingers at the same time.

After quantifying each category of the NIHSS, the total score can define the stroke severity according as follows: a score of 0 indicates no stroke symptoms; a score between 1 and 4 indicates a minor stroke; a score between 5 and 15 indicates a moderate stroke; a score between 16 and 20 indicates a moderate to severe stroke; and a score of 21-42 indicates a severe stroke. The disclosed technique is configured and operative to calculate the total severity score in a “decision-making” mode. The quantified scores can also be treated as recommendations for the physician, when the system configured to “decision support mode”.

It will be appreciated by persons skilled in the art that the disclosed technique is not limited to what has been particularly shown and described hereinabove. Rather the scope of the disclosed technique is defined only by the claims, which follow.

Claims

1. A method for estimating a likelihood of a stroke condition of a subject, the method comprising: acquiring clinical measurement data pertaining to said subject, said clinical measurement data including at least one of image data, sound data, movement data, and tactile data;extracting from said clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion;comparing said potential stroke features with classified sampled data acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset; anddetermining, according to said comparing, a probability of a type of said stroke condition, and a probability of a corresponding stroke location of said stroke condition with respect to a brain location of said subject.

2. The method according to claim 1, wherein said comparing is further performed on classified sampled data acquired from a plurality of subjects negatively diagnosed with a stroke condition, defining a negative stroke dataset.

3. The method according to claim 2, wherein said acquiring, said extracting, said comparing, and said determining are performed for constructing a baseline profile of said subject, wherein said baseline profile defines a time-dependent estimated neurological state of said subject.

4. The method according to claim 3, further comprising comparing between at least two said baseline profiles acquired at different times to determine changes in said clinical measurement data at said different times.

5. The method according to claim 4, further comprising generating a report from comparison between said at least two said baseline profiles.

6. The method according to claim 2, wherein said comparing involves pre-configuration to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

7. The method according to claim 2, wherein said comparing involves pre-training via at least one machine learning classifier (MLC) to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

8. The method according to claim 1, further comprising preprocessing of at least part of said clinical measurement data, prior to said extracting.

9. The method according to claim 1, wherein said extraction is of at least one of a region of interest (ROI), and a point of interest (POI) in at least one of a spatial domain, and a temporal domain.

10. The method according to claim 9, wherein said comparing further involves assessing a statistical correlation between said image data, said sound data, said movement data, and said tactile data.

11. The method according to claim 1, wherein said at least one predetermined stroke assessment criterion is selected from a list consisting of: a standardized test;a National Institutes of Health Stroke Scale (NIHSS) test;a face-arm-speech-time (FAST) test;a ABCD2 score;a CHADS2 score;a CHA2DS2VASc score;a Los Angeles Pre-hospital Stroke Screen (LAPSS) test a non-standardized test;a modified test based on a standardized test;a modified NIHSS (mNIHSS) test;a customized test based on a standardized test; andat least one characterizing mark.

12. The method according to claim 2, wherein said positive stroke dataset includes entries, each entry includes at least two fields: a stroke type and corresponding brain location.

13. The method according to claim 2, wherein said determining uses results outputted from said comparing that respectively represent quantitative measures indicating how extracted said stroke features match with corresponding said entries in said positive stroke dataset and entries in said negative stroke dataset.

14. The method according to claim 2, further comprising: constructing of at least one positive stroke model from at least part of said positive stroke dataset, and at least one negative stroke model from at least part of said negative stroke dataset.

15. The method according to claim 14, wherein said at least one positive stroke model is constructed for each of said potential stroke features.

16. The method according to claim 1, further comprising communicating information pertaining to said probability for said type of said stroke condition, and said probability of said corresponding stroke location to at least one device that is associated with at least one of said subject, a physician, and a medical facility.

17. The method according to claim 16, further comprising presenting least one of a region of interest (ROI), and a point of interest (POI) in extracted said clinical measurement data that corresponds with a highest estimated said likelihood of said stroke condition, according to determined said probability of said type of said stroke condition, and said probability of said corresponding stroke location.

18. A system for estimating a likelihood of a stroke condition of a subject, the system comprising: a database, containing classified sampled datasets acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset; anda processor, configured to receive clinical measurement data pertaining to said subject, and acquired from at least one sensor that is configured to acquire at least one of image data, sound data, movement data, and tactile data pertaining to said subject, said processor configured to extract from said clinical measurement data, potential stroke features according to at least one predetermined stroke assessment criterion; to compare said potential stroke features with said classified sample data; and to determine a probability of a type of said stroke condition, and a probability of a corresponding stroke location of said stroke condition with respect to a brain location of said subject.

19. The system according 18, wherein said processor is further configured to compare said potential stroke features with classified sampled data acquired from a plurality of subjects negatively diagnosed with a stroke condition, defining a negative stroke dataset.

20. The system according to claim 19, wherein said processor said acquires, said extracts, said compares, and said determines is for constructing a baseline profile of said subject, wherein said baseline profile defines a time-dependent estimated neurological state of said subject.

21. The system according to claim 20, wherein said processor is further configured to compare between at least two said baseline profiles acquired at different times to determine changes in said clinical measurement data at said different times.

22. The system according to claim 21, further wherein said processor is further configured to generate a report from comparison between said at least two said baseline profiles.

23. The system according to claim 19, wherein said comparing involves pre-configuration to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

24. The system according to claim 19, wherein said comparing involves pre-training via at least one machine learning classifier (MLC) to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

25. The system according to claim 18, further wherein said processor is configured to preprocess of at least part of said clinical measurement data, prior to said extraction of said potential stroke features.

26. The system according to claim 18, wherein said extraction is of at least one of a region of interest (ROI), and a point of interest (POI) in at least one of a spatial domain, and a temporal domain.

27. The system according to claim 26, wherein said comparing further involves assessing a statistical correlation between said image data, said sound data, said movement data, and said tactile data.

28. The system according to claim 18, wherein said at least one predetermined stroke assessment criterion is selected from a list consisting of: a standardized test;a National Institutes of Health Stroke Scale (NIHSS) test;a face-arm-speech-time (FAST) test;a ABCD2 score;a CHADS2 score;a CHA2DS2VASc score;a Los Angeles Pre-hospital Stroke Screen (LAPSS) testa non-standardized test;a modified test based on a standardized test;a modified NIHSS (mNIHSS) test;a customized test based on a standardized test; andat least one characterizing mark.

29. The system according to claim 19, wherein said positive stroke dataset includes entries, each entry includes at least two fields: a stroke type and corresponding brain location.

30. The system according to claim 19, wherein said determining uses results outputted from said comparing that respectively represent quantitative measures indicating how extracted said stroke features match with corresponding said entries in said positive stroke dataset and entries in said negative stroke dataset.

31. The system according to claim 19, wherein said processor is configured to construct at least one positive stroke model from at least part of said positive stroke dataset, and at least one negative stroke model from at least part of said negative stroke dataset.

32. The system according to claim 31, wherein said at least one positive stroke model is constructed for each of said potential stroke features.

33. The system according to claim 18, further comprising a communication module enabled for communication with said processor, said communication module is configured to communicate information pertaining to said probability for said type of said stroke condition, and said probability of said corresponding stroke location to at least one device that is associated with at least one of said subject, a physician, and a medical facility.

34. The system according to claim 18, further including a user interface configured to interface between said system and at least one of said subject, an operator of said system, a manager of said system, and a physician using said system.

35. The system according to claim 19, wherein said user interface is configured to provide an indication to at least one of said probability of said stroke type, and said probability of said corresponding stroke location.

36. The system according to claim 35, wherein said user interface is configured to present at least one of a region of interest (ROI), and a point of interest (POI) in extracted said clinical measurement data that corresponds with a highest estimated said likelihood of said stroke condition, according to determined said probability for said type of said stroke condition, and said probability of said corresponding stroke location.

37. A system for estimating a likelihood of a stroke condition of a subject, the system comprising: a client device including: at least one sensor, configured to acquire at least one of image data, sound data, movement data, and tactile data, all of which constitute clinical measurement data pertaining to said subject;a user interface, configured to provide an indication of a probability for a type of said stroke condition, and a probability of a corresponding stroke location of said stroke condition with respect to a brain location of said subject; anda communication module, enabled for communication with a remote computer, said communication module configured to send said clinical measurement data to said remote computer, and to receive from said remote computer said indication;wherein said indication is based on a comparison between potential stroke features extracted from said clinical measurement data according to at least one predetermined stroke assessment criterion, with classified sampled data in a database acquired from a plurality of subjects, each positively diagnosed with at least one stroke condition, defining a positive stroke dataset.

38. The system according 37, wherein said remote computer includes a processor that is configured to compare said potential stroke features with classified sampled data acquired from a plurality of subjects negatively diagnosed with a stroke condition, defining a negative stroke dataset.

39. The system according to claim 38, wherein said remote computer is configured to construct a baseline profile of said subject, wherein said baseline profile defines a time-dependent estimated neurological state of said subject.

40. The system according to claim 39, wherein said processor is further configured to compare between at least two said baseline profiles acquired at different times to determine changes in said clinical measurement data at said different times.

41. The system according to claim 40, further wherein said processor is further configured to generate a report from comparison between said at least two said baseline profiles.

42. The system according to claim 38, wherein said comparing involves pre-configuration to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

43. The system according to claim 38, wherein said comparing involves pre-training via at least one machine learning classifier (MLC) to enable classification of said potential stroke features to said positive stroke dataset, and to said negative stroke dataset.

44. The system according to claim 38, said processor is configured to preprocess of at least part of said clinical measurement data, prior to said extraction of said potential stroke features.

45. The system according to claim 38, wherein said extraction is of at least one of a region of interest (ROI), and a point of interest (POI) in at least one of a spatial domain, and a temporal domain.

46. The system according to claim 45, wherein said comparing further involves assessing a statistical correlation between said image data, said sound data, said movement data, and said tactile data.

47. The system according to claim 37, wherein said at least one predetermined stroke assessment criterion is selected from a list consisting of: a standardized test;a National Institutes of Health Stroke Scale (NIHSS) test;a face-arm-speech-time (FAST) test;a ABCD2 score;a CHADS2 score;a CHA2DS2VASc score;a Los Angeles Pre-hospital Stroke Screen (LAPSS) testa non-standardized test;a modified test based on a standardized test;a modified NIHSS (mNIHSS) test;a customized test based on a standardized test; andat least one characterizing mark.

48. The system according to claim 38, wherein said positive stroke dataset includes entries, each entry includes at least two fields: a stroke type and corresponding brain location.

49. The system according to claim 38, wherein said determining uses results outputted from said comparing that respectively represent quantitative measures indicating how extracted said stroke features match with corresponding said entries in said positive stroke dataset and entries in said negative stroke dataset.

50. The system according to claim 38, wherein said processor is configured to construct at least one positive stroke model from at least part of said positive stroke dataset, and at least one negative stroke model from at least part of said negative stroke dataset.

51. The system according to claim 50, wherein said at least one positive stroke model is constructed for each of said potential stroke features.

52. The system according to claim 38, wherein said communication module is configured to communicate information pertaining to said probability for said type of said stroke condition, and said probability of said corresponding stroke location to at least one device that is associated with at least one of said subject, a physician, and a medical facility.

53. The system according to claim 37, wherein said user interface is configured to interface between said system and at least one of said subject, an operator of said system, a manager of said system, and a physician using said system.

54. The system according to claim 38, wherein said user interface is configured to provide an indication to at least one of said probability of said stroke type, and said probability of said corresponding stroke location.

55. The system according to claim 54, wherein said user interface is configured to present at least one of a region of interest (ROI), and a point of interest (POI) in extracted said clinical measurement data that corresponds with a highest estimated said likelihood of said stroke condition, according to determined said probability of said type of said stroke condition, and said probability of said corresponding stroke location.