| CPC G16H 40/20 (2018.01) [G16H 70/20 (2018.01)] | 18 Claims | 

| 
               1. A system, comprising: 
            a plurality of medical devices comprising physiological monitoring devices and patient therapy devices at a plurality of medical facilities; 
                for each medical facility of the plurality of medical facilities, an edge device configured to receive medical device data from each of the plurality of medical devices associated with the medical facility in real-time as time-series data, wherein the edge device encrypts the medical device data; 
                a display; and 
                a computing device comprising a high-speed ingestion module, a data quality management module, a stream processing engine, an operation case database, and a data lake, wherein the computing device is operably coupled to the display and stores instructions executable to: 
                receive, at the high-speed ingestion module and from the edge device of each of the plurality of medical facilities, concurrent data streams of the encrypted medical device data at or near a frequency at which the plurality of medical devices output data, wherein the high-speed ingestion module supports ASTMF 2761, wherein the high-speed ingestion module preprocesses the received concurrent data streams of real-time data in time series format; 
                  normalize, enrich, and tag, via the data quality management module, the preprocessed concurrent data streams without impacting data latency, wherein the data quality management module converts units of measure, transforms the medical device data into a canonical data model with metadata, and stores the normalized medical device data in the data lake in a native format; 
                  identify, via the stream processing engine, clinical cases and events from the medical device data; 
                  store the identified clinical cases and events in the operational case database; 
                  determine each of an Adequacy of Anesthesia (AoA) protocol usage and an AoA protocol compliance based on the identified clinical cases and events stored in the operational case database and parameters for an AoA protocol, wherein the parameters for an AoA protocol comprise a range of a clinical measurement, and wherein determining the AoA protocol compliance comprises determining that the clinical measurement is within the range for each of the parameters; and 
                  output, to the display, a graphical user interface (GUI) that includes an AoA status dashboard and an AoA analysis dashboard, wherein the AoA status dashboard displays an AoA protocol usage indication generated based on the determined AoA protocol usage, and wherein the GUI includes an AoA protocol compliance indication generated based on the determined AoA protocol compliance; 
                wherein the physiological monitoring devices comprise heart rate monitors, blood pressure monitors, blood oxygenation monitors, respiration monitors, and electrocardiogram monitors, and wherein the patient therapy devices comprise anesthesia delivery machines; 
                wherein the high-speed ingestion module of the computing device is configured to ingest increased bandwidth of the medical device data without significant decrease in ingestion speeds; 
                wherein the parameters for the AoA protocol include lower and upper bounds for a desired maintenance phase level of consciousness (LOC), a lower bound for a desired emergence phase LOC, a lower bound for a desired extubation train of four (TOF), lower and upper bounds for a desired maintenance phase surgical pleth index (SPI), and wherein to determine the AoA protocol compliance, the computing device stores further instructions executable to: 
                analyze the medical device data to determine maintenance phase LOC values, emergence phase LOC values, extubation TOF values, and maintenance phase SPI values for each clinical case; 
                  determine that the clinical case has the AoA protocol compliance in response to the maintenance phase LOC values being within the lower and upper bounds for the desired maintenance phase LOC for at least a first threshold percentage of a total maintenance phase, the emergence phase LOC values being greater than the lower bound for the desired emergence phase LOC, the extubation TOF values being greater than the lower bound for the desired extubation TOF, and the maintenance phase SPI values being within the lower and upper bounds for the desired maintenance phase SPI for at least a second threshold percentage of the total maintenance phase; and 
                  determine that the clinical case does not have the AoA protocol compliance in response to at least one of maintenance phase LOC values not being within the lower and upper bounds for the desired maintenance phase LOC for at least the first threshold percentage of a total maintenance phase, the emergence phase LOC values not being greater than the lower bound for the desired emergence phase LOC, the extubation TOF values not being greater than the lower bound for the desired extubation TOF, and the maintenance phase SPI values not being within the lower and upper bounds for the desired maintenance phase SPI for at least the second threshold percentage of the total maintenance phase; 
                wherein the AoA status dashboard of the GUI comprises an operating room status tile for each operating room having an active case using the AoA protocol; and 
                wherein the computing device stores further instructions executable to display a real-time non-compliance alert on the operating room status tile in response to determining that the clinical case associated with the operating room status tile does not have the AoA protocol compliance. 
               |