Pulsation reclassification
By receiving ECG data and metadata, using deep learning neural networks to perform preliminary classification of cardiac events and pulsations, and allowing users to reclassify, solving the problem of misclassification in the cardiac monitoring system and improving the accuracy and efficiency of cardiac activity analysis.
Patent Information
- Application Number
- CN202380036962.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-27
- Filing Date
- 2023-04-26
- Publication Date
- 2024-12-06
AI Technical Summary
Existing cardiac monitoring systems are prone to misclassification when categorizing cardiac events and pulsation, resulting in inaccuracy in cardiac event types and pulsation classifications, which in turn affects treatment decisions.
By receiving ECG data and related metadata, the deep learning neural network is used for preliminary classification, and users can reclassify cardiac events and pulsations in the user interface. The initial pulsation classification is automatically modified based on subsequent cardiac event types, reducing the burden of manual analysis and improving accuracy sex.
It improves the accuracy of cardiac events and pulsation classification, reduces the possibility of misclassification, saves computing resources and manpower, and improves the efficiency and accuracy of cardiac activity analysis.
Smart Images

Figure CN119095534A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Provisional Application No. 63 / 335,621, filed on April 27, 2022, the entire contents of which are incorporated herein by reference in their entirety. Technical Field
[0003] The present disclosure relates to devices, methods and systems for analyzing cardiac activity and cardiac events. Background Art
[0004] Monitoring devices for collecting biometric data are becoming increasingly common in diagnosing and treating patients' medical conditions. For example, mobile devices can be used to monitor a patient's cardiac data. Such cardiac monitoring can provide doctors with valuable information about the occurrence and regularity of various cardiac conditions and irregularities in a patient. Cardiac monitoring can be used, for example, to identify abnormal heart rhythms so that critical alerts can be provided to the patient, doctor, or other care provider, and the patient can be treated. Summary of the invention
[0005] In Example 1, a method includes receiving, by a first computing system, electrocardiogram (ECG) data and metadata associated with the ECG data. The metadata includes an initial cardiac event classification and an initial beat classification of a beat occurring during a first event associated with the initial cardiac event classification. The method also includes displaying the ECG data in a user interface; receiving a command to change the initial cardiac event classification to a subsequent cardiac event classification; and automatically modifying the initial beat classification to a subsequent beat classification based on the subsequent cardiac event classification.
[0006] In Example 2, a method according to Example 1 is described, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a ventricular tachycardia event, wherein the subsequent cardiac event classification is a supraventricular event, and wherein the subsequent beat classification is a supraventricular beat.
[0007] In Example 3, a method according to Example 1 is described, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, and wherein the subsequent beat classification is a ventricular beat.
[0008] In Example 4, the method of Example 1 is described, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is a normal sinus event, and wherein the subsequent beat classification is a normal beat.
[0009] In Example 5, the method of Example 1 is described, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is an atrial fibrillation event, and wherein the subsequent beat classification is a normal beat.
[0010] In Example 6, according to any of the methods of the preceding examples, wherein the initial beat classification includes a first beat type and a second beat type, wherein automatically modifying the initial beat classification to a subsequent beat classification includes modifying only the first beat type.
[0011] In Example 7, the method according to any of the preceding examples further includes: displaying an initial beat classification and an initial cardiac event classification in the UI, and after the automatic modification step, displaying a subsequent beat classification and a subsequent cardiac event classification.
[0012] In Example 8, according to any of the methods of the preceding examples, wherein the initial beat classification and the initial cardiac event classification are determined by a deep learning neural network operated by a server, and wherein subsequent beat classifications are determined by the first computing system.
[0013] In Example 9, the method of Example 8, wherein the subsequent beat classification is determined by executing computer code by a web browser operating on the first computing system.
[0014] In Example 10, the method of Example 8 further includes: receiving, by the first computing system, computer code in a data packet, the data packet further including the ECG data and the metadata.
[0015] In Example 11, according to any of the preceding examples, the command is generated in response to receiving input from a user via the UI.
[0016] In Example 12, the method according to any of the preceding examples further includes: receiving, by the first computing system, a second set of ECG data and a second set of metadata associated with the second set of ECG data. The second set of metadata includes a first cardiac event classification and a first beat classification for each beat occurring during a second event associated with the first cardiac event classification. The method also includes receiving a first command to change the first cardiac event classification to a second cardiac event classification, and maintaining the first beat classification as a second beat classification based on the second cardiac event classification.
[0017] In Example 13, a computer program product includes instructions for causing one or more processors to perform the steps of the method of Examples 1 to 12.
[0018] In Example 14, a computer readable medium stores the computer program product of Example 13.
[0019] In Example 15, a computer includes the computer readable medium of Example 14.
[0020] In Example 16, the system includes a remote computing system having a UI, a first processor, and a first computer-readable medium having a first set of computer-executable instructions embodied thereon. The first set of instructions is configured to be executed by the first processor to cause the first processor to: display ECG data in the UI after receiving ECG data and metadata. The metadata includes an initial cardiac event classification and an initial beat classification of beats occurring during a first event associated with the initial cardiac event classification. The first set of instructions is also configured to receive a command to change the initial cardiac event classification to a subsequent cardiac event classification, and based on the subsequent cardiac event classification, automatically modify the initial beat classification to a subsequent beat classification.
[0021] In Example 17, the system of Example 16, wherein the command is generated in response to receiving input from a user via the UI.
[0022] In Example 18, the system of Example 16, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, and wherein the subsequent beat classification is a ventricular beat.
[0023] In Example 19, the system of Example 16, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, and wherein the subsequent beat classification is a ventricular beat.
[0024] In Example 20, the system of Example 16, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is a normal sinus event, and wherein the subsequent beat classification is a normal beat.
[0025] In Example 21, the system of Example 16, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is an atrial fibrillation event, and wherein the subsequent beat classification is a normal beat.
[0026] In Example 22, the system of Example 16, wherein the initial beat classification includes a first beat type and a second beat type, wherein automatically modifying the initial beat classification to a subsequent beat classification includes modifying only the first beat type.
[0027] In Example 23, according to the system of Example 16, wherein the first set of instructions is configured to be executed by the first processor to cause the first processor to: display the initial beat classification and the initial cardiac event classification in the UI, and after the automatic modification step, display the subsequent beat classification and the subsequent cardiac event classification.
[0028] In Example 24, the system of Example 16, wherein the first set of instructions is configured to be executed via a web browser at a remote computing system.
[0029] In Example 25, the system according to Example 16 further includes: a server having a database, a second processor, and a second computer-readable medium, the second computer-readable medium having a second set of computer-executable instructions embodied thereon. The second set of instructions is configured to be executed by the second processor to cause the second processor to: determine an initial cardiac event classification and an initial beat classification using a machine learning model operated by the server and based on ECG data. The instructions are also configured to cause the second processor to: store the initial cardiac event classification and the initial beat classification in the database; send the initial ECG data strip, the initial cardiac event classification, the initial beat classification, and the first set of instructions to a remote computing system; receive subsequent cardiac event classifications and subsequent beat classifications from the remote computing system; and replace the initial cardiac event classification with the subsequent cardiac event classification in the database, and replace the initial beat classification with the subsequent beat classification.
[0030] In Example 26, the system of Example 25, wherein the first set of instructions is executed by a web browser at the remote computing system.
[0031] In Example 27, a method includes receiving, by a first computing system, ECG data and metadata associated with the ECG data. The metadata includes an initial cardiac event classification and an initial beat classification of beats occurring during a first event associated with the initial cardiac event classification. The method also includes displaying the ECG data in a UI, receiving a command to change the initial cardiac event classification to a subsequent cardiac event classification, and automatically modifying the initial beat classification to a subsequent beat classification based on the subsequent cardiac event classification.
[0032] In Example 28, the method of Example 27 is described, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, and wherein the subsequent beat classification is a ventricular beat.
[0033] In Example 29, the method of Example 27 is described, wherein the initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, and wherein the subsequent beat classification is a ventricular beat.
[0034] In Example 30, the method of Example 27 is described, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is a normal sinus event, and wherein the subsequent beat classification is a normal beat.
[0035] In Example 31, the method of Example 27 is described, wherein the initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is an atrial fibrillation event, and wherein the subsequent beat classification is a normal beat.
[0036] In Example 32, the method of Example 27 is described, wherein the initial beat classification includes a first beat type and a second beat type, wherein automatically modifying the initial beat classification to a subsequent beat classification includes modifying only the first beat type.
[0037] In Example 33, the method of Example 27, wherein the subsequent beat classification is determined by executing computer code by a web browser operating on the first computing system.
[0038] In Example 34, a method includes determining (using a machine learning model operated by a server and based on ECG data) an initial cardiac event classification and an initial beat classification of beats that occurred during the event. The method also includes storing the initial cardiac event classification and the initial beat classification in a database of the server. The method also includes sending (to a remote computing system) the initial ECG data strip, the initial cardiac event classification, the initial beat classification, and executable code. The method also includes receiving subsequent cardiac event classifications and subsequent beat classifications from the remote computing system, and replacing the initial cardiac event classification with the subsequent cardiac event classification in the database, and replacing the initial beat classification with the subsequent beat classification.
[0039] In Example 35, the method according to Example 34 further includes: training the machine learning model with subsequent cardiac event classification and subsequent beat classification.
[0040] Although multiple examples are disclosed, other examples of the present disclosure will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative examples of the present disclosure. Therefore, the drawings and detailed description should be regarded as illustrative in nature and not restrictive. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 A cardiac monitoring system according to certain examples of the present disclosure is shown.
[0042] Figure 2 A server, a remote computer, and a user interface are shown according to certain examples of the present disclosure.
[0043] Figures 3 to 5 Various views of a report construction page according to certain examples of the present disclosure are shown.
[0044] Figure 6 A flow chart depicting an illustrative method for reclassifying cardiac events and beat classifications according to examples of the present disclosure is shown.
[0045] Figure 7 A flow chart depicting an illustrative method for hosting a SaaS platform and updating a hosted database in response to remotely made changes to metadata according to examples of the present disclosure is shown.
[0046] Figure 8 is a block diagram depicting an illustrative computing device according to examples of the present disclosure.
[0047] Although the disclosed subject matter is susceptible to various modifications and alternative forms, specific examples have been shown by way of example in the drawings and are described in detail below. However, it is not intended to limit the disclosure to the specific examples described. On the contrary, the disclosure is intended to cover all modifications, equivalents, and alternatives that fall within the scope of the disclosure as defined by the appended claims. DETAILED DESCRIPTION
[0048] The present disclosure relates to devices, methods, and systems for facilitating analysis of cardiac activity and cardiac events (eg, abnormal heart rhythms or other problems).
[0049] Electrocardiogram (ECG) data of a patient can be used to identify whether the patient has experienced a cardiac event and what type of cardiac event has occurred. One input to determining the type of cardiac event includes the type (or classification) of heartbeats experienced during the cardiac event. Therefore, an ECG analysis system can automatically determine that a certain type of cardiac event has occurred based on - among other things - how the system classifies the beats that occurred during the event. However, if the beats are initially misclassified, the type of cardiac event determined may also be misclassified. The cardiac event may then need to be reclassified. Then, from this conclusion, the potential beats may also need to be reclassified. Therefore, examples of the present disclosure are directed to systems, methods, and devices for facilitating the reclassification of ECG data.
[0050] Figure 1Patient 10 and example system 100 are shown. System 100 includes a monitor 102 attached to patient 10 to detect cardiac activity of patient 10. Monitor 102 can generate electrical signals representing cardiac activity of patient 10. For example, monitor 102 can detect the patient's heartbeat (e.g., using infrared sensors, electrodes) and convert the detected heartbeat into electrical signals representing ECG data. Monitor 102 transmits the ECG data to mobile device 104 (e.g., mobile phone).
[0051] The mobile device 104 may include a program (e.g., a mobile phone application) for receiving, processing, and analyzing ECG data. For example, the program may analyze ECG data and detect or mark cardiac events (e.g., irregular cardiac activity periods) contained in the ECG data. As noted above, because ECG data may be generated continuously, the amount of ECG data may be unbearable to store and process locally on the mobile device 104. Therefore, the mobile device 104 may periodically send ECG data blocks to another device or system, which may process, attach, and archive ECG data blocks and metadata associated with the ECG data blocks (e.g., time, duration, cardiac events detected / marked). In some instances, the monitor 102 may be programmed to send ECG data directly to other devices or systems without utilizing the mobile device 104. In addition, in some instances, the monitor 102 and / or the mobile device 104 include buttons or touch screen icons that allow the patient 10 to initiate an event. Such instructions may be recorded and transmitted to other devices or systems. In other instances involving multi-day studies, ECG data and associated metadata are sent in larger blocks.
[0052] Cardiac Event Server
[0053] exist Figure 1 In the example shown, mobile device 104 sends ECG data (and associated metadata, if any) to cardiac event server 106 (hereinafter referred to as "server 106" for brevity). Server 106 includes multiple platforms, layers, or modules that work together to process and analyze ECG data so that cardiac events can be detected, filtered, prioritized, and ultimately reported to the patient's physician for analysis and treatment. Figure 1 In the example of , the server 106 includes one or more machine learning models 108 (e.g., a type of deep neural network), a cardiac event router 110, a reporting platform 112, and a notification platform 114. Figure 1Only one server 106 is shown, but server 106 may include multiple separate physical servers, and the various platforms / modules / layers may be distributed among the multiple servers. Each of the platforms / modules / layers may represent a separate program, application, and / or code block, where the output of one of the platforms / modules / layers is the input of another of the platforms / modules / layers. Each platform / module / layer may communicate between or among other platforms / modules / layers and systems and devices external to server 106 using an application programming interface.
[0054] The server 106 applies the machine learning model 108 to the ECG data to classify the cardiac activity of the patient 10. For example, the machine learning model 108 can compare the ECG data with the labeled ECG data to determine which labeled ECG data the ECG data is most similar to. The labeled ECG data can identify specific cardiac events, including but not limited to ventricular tachycardia, bradycardia, atrial fibrillation, pause, normal sinus rhythm, or artifact / noise. In addition, the labeled ECG data can identify beat classifications such as normal, ventricular, and supraventricular.
[0055] In some embodiments, the machine learning model 108 includes two paths, where the first path is a deep convolutional neural network and the second path is a deep fully connected neural network. The deep convolutional neural network receives one or more groups of beats (e.g., a beat training with 3-10 beats), which are processed through a series of layers in the deep convolutional neural network. This series of layers may include a convolutional layer for performing convolution on the time series data in the beat training; a batch normalization layer for normalizing the output from the convolutional layer (e.g., centering the results around the origin); and a nonlinear activation function layer for receiving the normalized values from the batch normalization layer. The beat training is then passed through a set of repeated layers, such as another convolutional layer, a batch normalization layer, and a nonlinear activation function layer. This set of layers can be repeated multiple times.
[0056] The deep fully connected neural network receives RR interval data (e.g., the time interval between adjacent beats) and processes the RR interval data through a series of layers: a fully connected layer, a nonlinear activation function layer, another fully connected layer, another nonlinear activation function layer, and a regularization layer. The outputs from both paths are then provided to a fully connected layer. The resulting values are passed through a fully connected layer and a softmax layer to produce a probability distribution for beat classification.
[0057] If the machine learning model 108 determines that the ECG data is most similar to the labeled ECG data associated with the cardiac event, the machine learning model 108 can determine that the patient 10 experienced the cardiac event. In addition, the machine learning model 108 can measure or determine certain characteristics of the patient's 10 cardiac activity based on the ECG data. For example, the machine learning model 108 can determine the patient's 10 heart rate, duration, or beat count during the cardiac event based on the ECG data. The server 106 stores the cardiac event (and associated metadata, such as information like beat classification, heart rate, duration, beat count, etc.) in a database for storage. Subsequently, the server 106 can retrieve the cardiac event and associated information from the database.
[0058] In some instances, the mobile device 104 (or monitor 102) may initially classify a cardiac event based on the ECG data. The server 106 may then reclassify or confirm the cardiac event using the machine learning model 108. Doing so allows the computational resources of the server 106 to be used instead of the limited resources of the mobile device 104 to perform a more computationally expensive analysis of the ECG data.
[0059] In some instances, once the ECG data is processed by the machine learning model 108, the ECG data and metadata are available to a reporting platform 112. As will be described in more detail below, the reporting platform 112 can be accessed by a user at a clinic or laboratory 118 via a remote computer 116 (e.g., a client device such as a laptop, mobile phone, desktop computer, etc.).
[0060] In other examples, the cardiac event router 110 is used to determine which platform further processes the ECG data based on the classification associated with the cardiac event. For example, if the identified cardiac event is severe, the cardiac event router 110 may flag or send the ECG data, etc. to a notification platform 114. The notification platform 114 may be programmed to immediately send a notification (along with the relevant ECG data and associated metadata) to the patient's physician / care team remote computer and / or the patient 10 (e.g., to their computer system, email, mobile phone application).
[0061] Reporting Platform
[0062] Figure 2 The server 106 is shown communicatively coupled (e.g., via a network) to a remote computer 116. Figure 2In the example of FIG. 1 , remote computer 116 includes a monitor showing a user interface 122 (hereinafter referred to as “UI 122” for brevity) that displays features of reporting platform 112 hosted by server 106. UI 122 includes multiple pages or screens for tracking and facilitating analysis of patient ECG data.
[0063] In some examples, the reporting platform 112 is a software-as-a-service (SaaS) platform hosted by the server 106. To access the reporting platform 112, a user (e.g., a technician) interacts with the UI 122 to log into the reporting platform 112 via a web browser so that the user can use and interact with the reporting platform 112. When a user at the clinic or laboratory 118 is ready to analyze the patient's ECG data, the user can select the patient's profile through the UI 122.
[0064] The server 106 (e.g., via programming associated with the reporting platform 112) can initiate a process for sending data to the remote computer 116. The data includes ECG data and metadata associated with the ECG data. As noted above, once the ECG data from the monitored patient is collected, the machine learning model 108 can determine certain features of the patient's 10 cardiac activity based on the ECG data, including estimating that a cardiac event has occurred, and associate or generate metadata for the determined event. The metadata may include information about the patient 10, the patient's 10 heart rate during the cardiac event, the duration of the cardiac event, the beat count of the cardiac event, the confidence level of the machine learning model's identification of the cardiac event, and / or the beat classification (e.g., normal beat, ventricular beat, supraventricular beat, unclassified beat).
[0065] In some examples, the machine learning model 108 assigns a beat classification to each beat, and assigns a cardiac event type (e.g., atrial fibrillation, ventricular tachycardia, flutter) to certain groups and patterns of beats. To distinguish among the beats, each individual beat can therefore be assigned a unique identifier (e.g., a unique number).
[0066] Accessing, processing, and displaying one or more days' worth of ECG data and metadata can consume a large amount of computing resources, network bandwidth resources, and human resources. To help relieve the burden on these resources, server 106 (e.g., via reporting platform 112) can selectively send ECG data and metadata packages to remote computer 116.
[0067] The initial data packet may include: (1) a short strip of ECG data surrounding the detected cardiac event, (2) metadata associated with the strip, and (3) executable code (e.g., JavaScript code). In some instances, only ECG data associated with the highest priority cardiac event is initially transmitted. After the initial data packet is sent from the server to the remote computer 116, additional data packets may be sent in response to selections made by the user in the UI 122.
[0068] Report building page
[0069] With these initial data packets, the user can access (via remote computer 116 and UI 122) Figures 3 to 5 1. The report construction page 200 is shown. The report construction page 200 facilitates the analysis of cardiac events and metadata associated with cardiac events. These pages are generated at the remote computer 116 based on the data packets, and they are selectively displayed via the UI 122. As will be described in more detail below, when the user interacts with the report construction page 200, the metadata is updated in real time at the remote computer 116.
[0070] Figure 3 A screen shot of a report construction page 200 is shown. The report construction page 200 is used by a user to review and analyze a patient's ECG data and metadata. The report construction page 200 includes a plurality of windows for displaying data, plots, icons, links, tags, indicators, and the like.
[0071] Window 202 displays a heart rate graph for multiple days' worth of ECG data. This window 202 provides an initial visual insight into which time periods appear to contain abnormal heart rate activity. Figure 3 In the example shown, window 202 displays four days of ECG data, although shorter or longer time periods may be displayed by default, or changed by the user.
[0072] Window 204 allows the user to view a shorter ECG data graph. For example, window 204 can display ECG data associated with a detected cardiac event along with ECG data before and after the detected event. This window 204 provides visual insight into the start of the detected event and whether the detected event may be an artifact, a subsequent event, etc. When the user scrolls through window 204, window 202 can display an indicator (e.g., a vertical line) showing the position of the ECG data of window 204 within the heart rate graph of window 202.
[0073] Window 208 shows a shorter graph of ECG data (e.g., approximately 10 beats) than the graphs of windows 202 and 204. Window 208 displays a closer view of a portion of the ECG data of windows 202 and 204. A user may use window 204 to select which shorter ECG data set to display in window 208. Each of windows 202, 204, and 208 may include a marker, indicator, icon, etc. to visually draw attention to the location of a detected cardiac event within the ECG data strip.
[0074] Event and beat reclassification
[0075] As noted above, the machine learning model 108 can be programmed to automatically identify and classify cardiac events and beat types. These initial classifications are sent from the server 106 to the remote computer 116 for analysis. If during the analysis, the user determines that the initial classification should be updated, the report construction page 200 allows the user to reclassify cardiac events and beats via the UI 122 at the computer 116. As described in more detail below, the reclassification of cardiac events in the report construction page 200 can result in automatically reclassifying the beats that occur during the event, rather than requiring the user to manually analyze and reclassify each beat. This automatic reclassification of beats saves time analyzing ECG data and generating summary reports, while also improving the accuracy of the overall ECG study.
[0076] Figure 4 A portion of a report construction page 200 is shown. Figure 4 The top portion of shows an ECG data strip 210 containing cardiac events and their initial event and beat classifications, and Figure 4 The bottom portion of shows a bar 210 of ECG data with modified (or subsequent) event and beat classifications.
[0077] exist Figure 4 In the upper half of the diagram, ECG data strip 210 displays an initial classification of cardiac events and an initial beat classification in respective icons 212A and 214A. The initial classification is based on metadata generated by machine learning model 108 at server 106 and received by remote computer 116.
[0078] exist Figure 4 In the example of , the initial cardiac event classification is shown in icon 212A as an atrial fibrillation event. The length of the initial cardiac event is visually shown by a band 216A extending horizontally along the ECG data strip 210 between the start of the event and the end of the event.
[0079] Each identified beat is given its own classification, which is shown by an icon 214A adjacent to each beat. Figure 4In the example of FIG. 214A, the beats are classified as normal beats, which is indicated by the letter "N" in icon 214A. ECG data strip 210 also displays the RR interval lengths for each identified beat pair.
[0080] When analyzing ECG data, a user viewing ECG data strip 210 may determine that the initial cardiac event classification should be changed to a different cardiac event classification. Using icon 212A (or a button on report construction page 200), the user can modify the initial cardiac event classification. Figure 4 In the example of FIG. 1 , a user may change the classification of a cardiac event from an atrial fibrillation event to a ventricular tachycardia event. For example, a user may select a feature on UI 122 (e.g., icon 212A or various buttons) that generates a command to change the initial classification from an atrial fibrillation event to a subsequent classification of a ventricular tachycardia event. The metadata may then be updated to reflect this reclassification of the cardiac event.
[0081] In addition to reclassifying cardiac events using UI 122, beat classifications may also be automatically updated. As noted above, certain types of beats are typically associated with certain types of cardiac events. As an example, a supraventricular tachycardia event is typically associated with beats that are classified as supraventricular beats. Thus, when a cardiac event is subsequently classified as a supraventricular tachycardia event, each beat that occurs during the event may be reclassified as a supraventricular beat. As another example, an atrial fibrillation event is typically associated with beats that are classified as normal beats. Thus, when a cardiac event is subsequently classified as an atrial fibrillation event, each beat that occurs during the event may be reclassified as a normal beat. Below is a table outlining an example of how beats may be automatically classified based on subsequent cardiac event classifications:
[0082]
[0083] Table 1
[0084] The first column represents the initial cardiac event classification, and the upper row represents the subsequent cardiac event classification. In Table 1, Afib represents an atrial fibrillation event, NSR represents a normal sinus event, VT represents a ventricular tachycardia event, and SVT represents a supraventricular tachycardia event.
[0085] A single letter in a cell indicates the subsequent beat classification. In Table 1, "S" indicates a supraventricular beat, "V" indicates a ventricular beat, "N" indicates a normal beat, and "Z" indicates no change.
[0086] As indicated by the cells with a "Z", some changes in cardiac event classification do not affect the beat classification. In this case, the underlying beat classification is compatible with the subsequent cardiac event classification, and thus the initial beat classification is maintained despite the change in cardiac event classification.
[0087] Furthermore, in some instances, not all beats within a cardiac event may initially be classified as the same. In such cases, only a subset of the beats may be reclassified in response to modifying the initial cardiac event classification.
[0088] Return to reference Figure 4 and applying Table 1, it can be seen that changing the classification of a cardiac event from an atrial fibrillation event to a ventricular tachycardia event results in the beat occurring within the event being changed to a ventricular beat classification.
[0089] Figure 5 Another example is provided. Figure 5 A portion of a report construction page 200 is shown. Figure 5 The top portion of shows ECG data strips 220 containing cardiac events and their initial event and beat classifications, and Figure 5 The bottom portion of shows a bar 220 of ECG data with modified (or subsequent) event and beat classifications.
[0090] exist Figure 5 In the upper portion of the ECG data strip 220, the initial classification of the cardiac event and the initial beat classification are displayed in corresponding icons. Figure 5 In the example of , the initial cardiac event classification is shown as normal sinus events. These beats are classified as normal beats.
[0091] exist Figure 5 In the example of , the user can change the cardiac event classification from a normal sinus event to an atrial fibrillation event. Applying Table 1, it can be seen that changing the cardiac event classification from a normal sinus event to an atrial fibrillation event causes the beats occurring in the event to remain normal beats. This is because both types of cardiac events may include normal beats, but not other types of beats. Therefore, for this specific example, in response to the change in cardiac event classification, the beat classification is not modified.
[0092] To conserve processing and network resources, and to allow these changes to metadata to occur in real time, the calculation and changes to the cardiac event classifications and the automatic updating of the beat classifications may be performed locally on the remote computer 116, rather than sending data back and forth between the server 106 and the remote computer 116. For example, a cache memory 124 (in Figure 1108) and the processing power (e.g., one or more microprocessors) of the remote computer 116 to perform the reclassification. To enable local processing and updating, the reporting platform 112 can send the remote computer 116 code to be executed locally. The code uses (or operates on) the output of the machine learning model 108, such as beat classification and rhythm classification (as opposed to the underlying or raw ECG data), which reduces the computing resources required to process changes made locally by the user at the remote computer 116. In some embodiments, the code is executed by an Internet browser operating on the remote computer 116.
[0093] In some instances, once the report is constructed and completed, the remote computer 116 can send any changes to the metadata (e.g., subsequent beat classifications and subsequent rhythm classifications) to the server 106 and its database. The server 106 can then replace the metadata originally created by the machine learning model (and saved to the database) with the metadata generated by the remote computer as the user reviews and edits the metadata. Thus, if the ECG and metadata need to be accessed again, the server's database has the latest version of the metadata. In addition, the machine learning model 108 can be further trained on the metadata generated by the user at the remote computer.
[0094] method
[0095] Figure 6 A block diagram of a method 400 for reclassifying a beat is shown. The method 400 includes receiving ECG data and metadata associated with the ECG data ( Figure 6 The metadata includes an initial cardiac event classification and an initial beat classification for each beat occurring during a first event associated with the initial cardiac event classification. The method 400 also includes displaying the ECG data in a user interface (UI) ( Figure 6 Method 400 also includes receiving a command to change the initial cardiac event classification to a subsequent cardiac event classification ( Figure 6 The method 400 also includes automatically modifying the initial beat classification to a subsequent beat classification based on the subsequent cardiac event classification ( Figure 6 408 in FIG.
[0096] Figure 7 A block diagram of a method 500 for hosting a SaaS platform and updating a hosted database in response to remotely made changes to metadata is shown. The method 500 includes identifying cardiac events within ECG data using a machine learning model operated by a server and determining an initial cardiac event classification and an initial beat classification ( Figure 7The method 500 also includes sending (to a remote computing system) the ECG data strip, the initial cardiac event classification, the initial beat classification, and the executable code ( Figure 7 The method also includes replacing the initial cardiac event classification and the initial beat classification generated by the remote computing system in the database ( Figure 7 506 in FIG.
[0097] Computing devices and systems
[0098] Figure 8 is a block diagram depicting an illustrative computing device 500 according to an example of the present disclosure. The computing device 500 may include any type of computing device suitable for implementing aspects of an example of the disclosed subject matter. Examples of computing devices include dedicated computing devices or general-purpose computing devices, such as workstations, servers, laptops, desktops, tablet computers, handheld devices, smartphones, general-purpose graphics processing units (GPGPUs), etc. Each of the various components shown and described in the figure may include their own dedicated set of computing device components. Figure 5 For example, mobile device 104, server 106, and remote computer 116 may each include their own set of components. Figure 8 is shown in and described below.
[0099] In the example, computing device 500 includes bus 510, which directly and / or indirectly couples one or more of the following devices: processor 520, memory 530, input / output (I / O) port 540, I / O component 550, and power supply 560. Any number of additional components, different components, and / or combinations of components may also be included in computing device 500.
[0100] Bus 510 represents one or more buses (such as, for example, an address bus, a data bus, or a combination thereof). Similarly, in an example, computing device 500 may include multiple processors 520, multiple memory components 530, multiple I / O ports 540, multiple I / O components 550, and / or multiple power supplies 560. In addition, any number or combination of these components may be distributed and / or replicated across multiple computing devices.
[0101] In an example, the memory 530 includes computer-readable media in the form of volatile and / or non-volatile memory, and may be removable, non-removable, or a combination thereof. Examples of media include random access memory (RAM); read only memory (ROM); electronically erasable programmable read only memory (EEPROM); flash memory; optical or holographic media; cassettes, tapes, disk storage or other magnetic storage devices; data transmission; and / or any other medium that can be used to store information and can be accessed by a computing device. In an example, the memory 530 stores computer-executable instructions 570 for causing the processor 520 to implement aspects of the examples of the components discussed herein and / or to perform aspects of the examples of the methods and processes discussed herein. The memory 530 may include a non-temporary computer-readable medium storing computer-executable instructions 570.
[0102] Computer executable instructions 570 may include, for example, computer code, machine usable instructions, etc., such as, for example, program components that can be executed by one or more processors 520 (e.g., microprocessors) associated with computing device 500. Program components can be programmed using any number of different programming environments, including various languages, development toolkits, frameworks, and / or the like. Some or all of the functionality contemplated herein may also or alternatively be implemented in hardware and / or firmware.
[0103] According to an example, for example, the instructions 570 may be configured to be executed by the processor 520 and, when executed, cause the processor 520 to perform certain processes. In some examples, the processor 520, the memory 530, and the instructions 570 are part of a controller such as an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or the like. Such devices may be used to perform the functions and steps described herein.
[0104] The I / O components 550 may include presentation components configured to present information to a user, such as, for example, a display device, a speaker, a printing device, and / or the like, and / or input components, such as, for example, a microphone, a joystick, a satellite dish, a scanner, a printer, a wireless device, a keyboard, a pen, a voice input device, a touch input device, a touch screen device, an interactive display device, a mouse, and / or the like.
[0105] The devices and systems described herein may be communicatively coupled via a network, which may include a local area network (LAN), a wide area network (WAN), a cellular data network, via the Internet using an Internet service provider, and the like.
[0106] Aspects of the present disclosure are described with reference to flowchart illustrations and / or block diagrams of methods, devices, systems, and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions.
[0107] Various modifications and additions may be made to the illustrative examples discussed without departing from the scope of the disclosed subject matter. For example, while the examples described above refer to specific features, the scope of the present disclosure also includes examples with different combinations of features and examples that do not include all of the described features. Therefore, the scope of the disclosed subject matter is intended to include all such substitutions, modifications, and variations as fall within the scope of the claims, together with all equivalents thereof.
Claims
1. A method comprising: receiving, by a first computing system, electrocardiogram (ECG) data and metadata associated with the ECG data, the metadata comprising an initial cardiac event classification and an initial beat classification of beats occurring during a first event associated with the initial cardiac event classification; Displaying the ECG data in a user interface (UI); receiving a command to change the initial cardiac event classification to a subsequent cardiac event classification; and The initial beat classification is automatically modified to a subsequent beat classification based on the subsequent cardiac event classification.
2. The method according to claim 1, wherein: The initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a ventricular tachycardia event, wherein the subsequent cardiac event classification is a supraventricular event, wherein the subsequent beat classification is a supraventricular beat.
3. The method according to claim 1, wherein: The initial cardiac event classification is an atrial fibrillation event, a normal sinus event, or a supraventricular event, wherein the subsequent cardiac event classification is a ventricular tachycardia event, wherein the subsequent beat classification is a ventricular beat.
4. The method according to claim 1, wherein: The initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is a normal sinus event, wherein the subsequent beat classification is a normal beat.
5. The method according to claim 1, wherein: The initial cardiac event classification is a ventricular tachycardia event or a supraventricular event, wherein the subsequent cardiac event classification is an atrial fibrillation event, wherein the subsequent beat classification is a normal beat.
6. A method according to any one of the preceding claims, wherein: The initial beat classification includes a first beat type and a second beat type, wherein automatically modifying the initial beat classification to the subsequent beat classification includes modifying only the first beat type.
7. The method according to any one of the preceding claims, further comprising: displaying the initial beat classification and the initial cardiac event classification in the UI; and After the automatic modification step, the subsequent beat classification and the subsequent cardiac event classification are displayed.
8. A method according to any one of the preceding claims, wherein: The initial beat classification and the initial cardiac event classification are determined by a deep learning neural network operated by a server, wherein the subsequent beat classification is determined by the first computing system.
9. The method according to claim 8, wherein: The subsequent beat classification is determined by execution of computer code by a web browser operating on the first computing system.
10. The method according to claim 8, further comprising: Computer code is received by the first computing system in a data packet including the ECG data and the metadata.
11. A method according to any one of the preceding claims, wherein: The command is generated in response to receiving input from a user via the UI.
12. The method according to any one of the preceding claims, further comprising: receiving, by the first computing system, a second set of ECG data and a second set of metadata associated with the second set of ECG data, the second set of metadata comprising a first cardiac event classification and a first beat classification for each beat occurring during a second event associated with the first cardiac event classification; receiving a first command to change the first cardiac event classification to a second cardiac event classification; and The first beat classification is maintained based on the second cardiac event classification.
13. A computer program product comprising instructions for causing one or more processors to perform the steps of the method of claims 1 to 12.
14. A computer readable medium having stored thereon the computer program product of claim 13.
15. A computer comprising the computer-readable medium of claim 14.
