Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
| Name | Class |
|---|---|
| Nihon Kohden | INDUSTRY |
Not provided
Not provided
Not provided
This is a feasibility study for an investigational clinical decision support system ("the System") intended to optimize the management of blood pressure (BP) for patients during vasopressor infusion. The investigational outcomes are the perceptions of the nurse-subjects who are managing the BP of the patient-subjects; the operational performance of the System; and any technical failures of the software during real-time operation.
This is a feasibility study for an investigational clinical decision support system ("the System") intended to optimize the management of blood pressure (BP) for patients during vasopressor infusion. Enrollment is planned of a convenience sample of 20 individual patient-subjects and also the 20 nurse-subjects who correspond to the primary nurses managing the patient-subjects. Consent will be obtained by the investigative team from the patient-subject (or close family member or healthcare proxy) and from the nurse-subject. The nurse will receive training in the intended use and important limitations of the System. The System will be deployed to the patient's bedside and the System will be initiated. This intervention will continue for a duration of between 4 to 8 hours. A Technical Observer ("TO") will be present to continually oversee the operation of the System, watching to ensure that there are no observable technical failures. The TO will also watch to see if any early termination conditions are met (specifically any concerns by the clinical staff or the patient or the patient's family; any observed technical operational problems; maximum dose vasopressors or hypoxia despite maximum respiratory support; or unplanned bedside response by the clinical care team) and also will make annotations about the exact time that specific clinical interventions are performed. After the intervention, the nurse-subject will be surveyed. Prior to enrollment of a subsequent subject, additional data analysis -- sufficient to identify or exclude any early stoppage condition -- will be performed on the System's archived electronic data and log files. Any adverse events will be reported to the IRB and the FDA as per FDA and institutional policy.
Not provided
Not provided
Not provided
Not provided
| Label | Type | Description | Intervention Names |
|---|---|---|---|
| Intervention group | Experimental | The investigational system will be evaluated for safety and user acceptance in 20 patient-subjects and associated nurse-subjects |
|
| Name | Type | Description | Arm Group Labels | Other Names |
|---|---|---|---|---|
| VIGORIS Blood Pressure Management Clinical Decision Support System | Device | Software system to optimize tight blood pressure management during vasopressor infusion |
|
| Measure | Description | Time Frame |
|---|---|---|
| Quantitative Nurse-subject Survey Response | Nurse-subject quantitative survey response (yes/no) about any confusion or perceived inaccuracies of the system; perceived risk of patient management error; or perceived distraction that impacted care delivery | Up to 8 hours |
| Software Operation (Based on Real-time Observation) | System malfunction (yes/no) observed in real-time by the Technical Observer | Up to 8 hours |
| Data Completeness | Completeness (yes/no) of flowsheet (data archive of the investigational System) without any lapses in input data from the bedside monitor during connectivity; and without lapses in associated BP forecasts. | Up to 8 hours |
| Software Operation (Based on Review of Error Logs) | Error-level and critical-level software errors in the runtime log (yes/no) | Up to 8 hours |
| Measure | Description | Time Frame |
|---|---|---|
| Percentage of Time That the BP Forecast is Operative (Outcome 2.1) | Median percentage (%) of time, per patient, during the session when inclusion criteria were otherwise met that the BP forecast was operative (i.e., time intervals when no InOp criteria detected by the System leading to the InOp state) | up to 8 hours |
Not provided
Inclusion Criteria:
Exclusion Criteria:
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
| Name | Affiliation | Role |
|---|---|---|
| Andrew T Reisner, MD | Massachusetts General Hospital | Principal Investigator |
| Facility | Status | City | State | ZIP | Country | Contacts |
|---|---|---|---|---|---|---|
| Massachusetts General Hospital | Boston | Massachusetts | 02114 | United States |
IPD may be shared if consistent with our institutional policy and approved by Nihon Kohden Innovation Center
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
Not provided
| ID | Title | Description |
|---|---|---|
| FG000 | Intervention Group | The investigational system will be evaluated for safety and user acceptance in 20 patient-subjects and associated nurse-subjects VIGORIS Blood Pressure Management Clinical Decision Support System: Software system to optimize tight blood pressure management during vasopressor infusion |
| Title | Milestones | Reasons Not Completed | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Overall Study |
|
|
Not provided
Not provided
| ID | Title | Description |
|---|---|---|
| BG000 | Intervention Group | The investigational system will be evaluated for safety and user acceptance in 20 patient-subjects and associated nurse-subjects VIGORIS Blood Pressure Management Clinical Decision Support System: Software system to optimize tight blood pressure management during vasopressor infusion |
| Units | Counts |
|---|---|
| Participants |
|
| Title | Description | Population Description | Parameter Type | Dispersion Type | Unit of Measure | Calculate Percentage | Denominator Units Selected | Denominators | Classes |
|---|---|---|---|---|---|---|---|---|---|
| Age, Categorical | Count of Participants |
| Type | Title | Description | Population Description | Reporting Status | Anticipated Posting Date | Parameter Type | Dispersion Type | Unit of Measure | Calculate Percentage | Time Frame | Units Analyzed | Denominator Units Selected | Arm/Group Information | Denominators | Classes | Analyses | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Primary | Quantitative Nurse-subject Survey Response | Nurse-subject quantitative survey response (yes/no) about any confusion or perceived inaccuracies of the system; perceived risk of patient management error; or perceived distraction that impacted care delivery | Posted | Count of Participants | Participants | Up to 8 hours |
|
|
4-8 hours (duration of investigational protocol)
Adverse events (AEs) were determined systematically by a real-time technical observer; nurse-subject surveys; and the software logs. Expected AEs in a population of ICU patients on vasopressors included all sustained hypotension episodes; tachyarrhythmias (HR > 150 bpm) or bradyarrhythmias (HR < 50 bpm) that persist for more than ten minutes; need for chest compressions or defibrillation; or any unscheduled bedside response by the ICU care team involving more than the patient's primary nurse.
Not provided
| ID | Title | Description | Deaths (Affected) | Deaths (At Risk) | Serious Events (Affected) | Serious Events (At Risk) | Other Events (Affected) | Other Events (At Risk) |
|---|---|---|---|---|---|---|---|---|
| EG000 | Intervention Group | The investigational system will be evaluated for safety and user acceptance in 20 patient-subjects and associated nurse-subjects VIGORIS Blood Pressure Management Clinical Decision Support System: Software system to optimize tight blood pressure management during vasopressor infusion |
| Term | Organ System | Source Vocabulary | Assessment Type | Notes | Statistical Information |
|---|---|---|---|---|---|
| Multi-clinician response | Cardiac disorders | Systematic Assessment |
| Term | Organ System | Source Vocabulary | Assessment Type | Notes | Statistical Information |
|---|---|---|---|---|---|
| Unable to electronically communicate with GE monitor | Investigations | Systematic Assessment |
Not provided
| Title | Organization | Phone | Extension | |
|---|---|---|---|---|
| Dr. Andrew Tomas Reisner | Massachusetts General Hospital | 617-726-2241 | areisner@mgh.harvard.edu |
Not provided
| Type | Includes Protocol | Includes SAP | Includes ICF | Document Label | Document Date | Document Uploaded Date | Document File Name |
|---|---|---|---|---|---|---|---|
| Prot_SAP | Yes | Yes | No | Study Protocol and Statistical Analysis Plan | Mar 14, 2022 | Mar 31, 2023 | Prot_SAP_000.pdf |
Not provided
| ID | Term |
|---|---|
| D007022 | Hypotension |
| D012769 | Shock |
| ID | Term |
|---|---|
| D014652 | Vascular Diseases |
| D002318 | Cardiovascular Diseases |
| D010335 | Pathologic Processes |
| D013568 | Pathological Conditions, Signs and Symptoms |
Not provided
Not provided
This is a single arm feasibility study
Not provided
Not provided
No masking
Not provided
| Accuracy of the MAP Forecast (Outcome 2.2) |
Accuracy of the future 20 min median MAP forecast (average error between the MAP forecast and the future 20 min median MAP; for purposes of computing future 20 min median MAP, MAP < 10 mmHg and MAP > 250 mmHg is treated as a missing number) over time intervals during the session when inclusion criteria were otherwise met; the BP forecast was operative; and the analysis window criteria were met [at least 19 minutes remaining to the end of the record from the time of the forecast; and the analysis window has no more than 9 min of non-physiological MAP data (non-physiological MAP criteria are MAP < 10mmHg or MAP > 250mmHg or 'NaN')]. |
| Up to 8 hours |
| Percentage of Time That the True Future 20 Min Median MAP Falls Within the Forecast Cone (Outcome 2.3) | Median percentage (%) of time, per patient, that the true future 20 min median MAP falls within the computed forecast cone over time intervals during the session when inclusion criteria were otherwise met; the BP forecast was operative; and the analysis window criteria were met [at least 19 minutes remaining to the end of the record from the time of the forecast; and the analysis window has no more than 9 min of non-physiological MAP data (non-physiological MAP criteria are MAP < 10mmHg or MAP > 250mmHg or 'NaN')] | Up to 8 hours |
| SHE Incidence (Outcome 3.1) | SHE incidence per 24 hrs [Sustained hypotensive event "SHE" is any interval commencing upon MAP < goal & 20-min future median MAP is also < goal; terminating upon time point when MAP >= goal and & 20-min future median MAP >= goal; SHEs occurring sequentially within 10 min are merged; any remaining SHEs not persisting at least 10 min are excluded]. [Clarification: We are reporting the mean "events per patient-day" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Percentage of Total SHEs Predicted by {Index > 35%} Prior to Earliest Hypotension (Outcome 3.2.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to the SHE's earliest hypotension [hypotension is defined as MAP < goal, with the exclusion of MAP < 10 mmHg, which is treated as a missing number]. Notification events are intervals that begin when there is an Index value that meets the notification criteria and terminate when there is an Index value output that does not meet the notification criteria. | Up to 8 hours |
| Advance Warning Times (AWTs) for SHEs Predicted by {Index > 35%} Prior to Earliest Hypotension (Outcome 3.2.2) | AWTs (median) for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to the SHE's earliest hypotension [i.e., MAP < goal]. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Earliest Hypotension (Outcome 3.2.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to the SHE's earliest hypotension [i.e., MAP < goal] | Up to 8 hours |
| AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Earliest Hypotension (Outcome 3.2.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to the SHE's earliest hypotension [i.e., MAP < goal]. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total SHEs Predicted by {Index > 35%} Prior to Continuous Hypotension (Outcome 3.3.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to continuous hypotension [intervals of ≥ 10 minutes of physiological MAP continuously below the hypotension threshold (physiological MAP are samples that do not meet the non-physiological criteria)]. NOTE: excluding SHEs predicted prior to earliest hypotension | Up to 8 hours |
| AWTs for SHEs Predicted by {Index > 35%} Prior to Continuous Hypotension (Outcome 3.3.2) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to continuous hypotension and excluding SHEs predicted prior to earliest hypotension. NOTE: A negative AWT denotes a notification event that occurs chronologically after the onset of the SHE event. For example, an AWT of -3 would mean the first notification event occurred 3 minutes after the onset of the SHE event, although still in advance of continuous hypotension. | Up to 8 hours |
| Percentage of Total SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Continuous Hypotension (Outcome 3.3.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to continuous hypotension [intervals of ≥ 10 minutes of physiological MAP continuously below the hypotension threshold (physiological MAP are samples that do not meet the non-physiological criteria)]. NOTE: excluding SHEs predicted prior to earliest hypotension | Up to 8 hours |
| AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Continuous Hypotension (Outcome 3.3.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to continuous hypotension and excluding SHEs predicted prior to earliest hypotension. NOTE: A negative AWT denotes a notification event that occurs chronologically after the onset of the SHE event. For example, an AWT of -3 would mean the first notification event occurred 3 minutes after the onset of the SHE event, although still in advance of continuous hypotension. | Up to 8 hours |
| Percentage of Total SHEs Detected by {Index > 35%} After Continuous Hypotension Onset (Outcome 3.4.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) after onset of continuous hypotension | Up to 8 hours |
| AWTs for SHEs Predicted by {Index > 35%} After Continuous Hypotension Onset (Outcome 3.4.2) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) after onset of continuous hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total SHEs Detected by {Index > User's Index Threshold Setting} After Continuous Hypotension Onset (Outcome 3.4.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) after onset of continuous hypotension | Up to 8 hours |
| AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} After Continuous Hypotension Onset (Outcome 3.4.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) after onset of continuous hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total SHEs With False Resolutions (Outcome 3.5.1) | Percentage of total SHEs with false resolutions [i.e., MAP >= goal transiently during SHE] | Up to 8 hours |
| Percentage of Total SHE False Resolutions Detected by {Index > 35%} (Outcome 3.5.2) | Percentage (%) of total SHE false resolutions with a contiguous notification event where {Index > 35%} | Up to 8 hours |
| Percentage of Total SHE False Resolutions Not Detected by {Index > 35%} With InOp State During False Resolution (Outcome 3.5.3) | Percentage of total SHE false resolutions that were not detected by {Index > 35%} and had InOp state occurring during the index false resolution episode | Up to 8 hours |
| Percentage of Total SHE False Resolutions Not Detected by {Index > 35%} Without InOp State During False Resolution (Outcome 3.5.4) | Percentage (%) of total SHE false resolutions that were not detected by {Index > 35%} and did not have InOp state occurring during the index false resolution episode | Up to 8 hours |
| Percentage of Total SHE False Resolutions Detected by {Index > User's Index Threshold Setting} (Outcome 3.5.5) | Percentage (%) of total SHE false resolutions with a contiguous notification event where {Index > user's Index threshold setting} | Up to 8 hours |
| Percentage of Total SHE False Resolutions Not Detected by {Index > User's Index Threshold Setting} With InOp State During False Resolution (Outcome 3.5.6) | Percentage (%) of total SHE false resolutions that were not detected by {Index > user's Index threshold setting} and had InOp state occurring during the index false resolution episode | Up to 8 hours |
| Percentage of Total SHE False Resolutions Not Detected by {Index > User's Index Threshold Setting} Without InOp State During False Resolution (Outcome 3.5.7) | Percentage (%) of total SHE false resolutions that were not detected by {Index > user's Index threshold setting} and did not have InOp state occurring during the index false resolution episode | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} That Are Contiguous With SHEs (Outcome 3.6.1) | Incidence of notification events {Index > 35%} that are contiguous with SHEs, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} That Are Contiguous With SHEs (Outcome 3.6.2) | Incidence of notification events {Index > user's Index threshold setting} that are contiguous with SHEs, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} That Are Sentinel Notifications (Outcome 3.6.3) | Incidence of notification events {Index > 35%} that are sentinel notifications [sentinel notification is a notification event that occurs within 60 min prior to an SHE; recorded dose increase; or during stuttering hypotension (defined in 3.7.1)], excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} That Are Sentinel Notifications (Outcome 3.6.4) | Incidence of notification events {Index > user's Index threshold setting} that are sentinel notifications, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} That Are False Notifications (Outcome 3.6.5) | Incidence of notification events {Index > 35%} that are false notifications (defined as notification events not contiguous with an SHE and not a sentinel notification, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} That Are False Notifications (Outcome 3.6.6) | Incidence of notification events {Index > user's Index threshold setting} that are false notifications. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} Contiguous With an SHE False Resolution (Outcome 3.6.7) | Incidence of notification events {Index > 35%} contiguous with an SHE false resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE False Resolution (Outcome 3.6.8) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE false resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} Contiguous With an SHE True Resolution, Overall (Outcome 3.6.9) | Incidence of notification events {Index > 35%} contiguous with an SHE true resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE True Resolution, Overall (Outcome 3.6.10) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE true resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} Contiguous With an SHE True Resolution, Suppressible (Outcome 3.6.11) | Incidence of notification events {Index > 35%} contiguous with an SHE true resolution after excluding all notification event interval that were within 8 min of a documented clinical intervention. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE True Resolution, Suppressible (Outcome 3.6.12) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE true resolution after excluding all notification event interval that were within 8 min of a documented clinical intervention. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > 35%} With Onset During an SHE (Outcome 3.6.13) | Incidence of notification events {Index > 35%} with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Incidence of Notification Events {Index > User's Index Threshold Setting} With Onset During an SHE (Outcome 3.6.14) | Incidence of notification events {Index > user's Index threshold setting} with onset during an SHE. [Clarification: We are using "notification events / patient-day (24h)" as the Unit of Measure for several reasons. First, different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Duration of False Notification Events {Index > 35%} (Outcome 3.6.15) | Median duration of false notification events {Index > 35%} | Up to 8 hours |
| Duration of False Notification Events {Index > User's Index Threshold Setting} (Outcome 3.6.16) | Median duration of false notification events {Index > user's Index threshold setting} | Up to 8 hours |
| Stuttering Hypotension Incidence (Outcome 3.7.1) | Stuttering hypotension incidence [Stuttering hypotension event commences upon hypotension and with >= 10 min of cumulative hypotension within subsequent 60 min; terminates upon next time point when onset condition is no longer met AND when MAP >= goal; intervals that qualify as an SHE are excluded from stuttering hypotension]. [Clarification: We are reporting the mean "events per patient-day" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.2) | Percentage (%) of total stuttering hypotension episodes detected by {Index > 35%} prior to the stuttering hypotension's first hypotension | Up to 8 hours |
| AWTs for Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.3) | AWTs for stuttering hypotension episodes detected by {Index > 35%} prior to the stuttering hypotension's first hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.4) | Percentage (%) of total stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the stuttering hypotension's first hypotension | Up to 8 hours |
| AWTs for Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.5) | AWTs for stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the stuttering hypotension's first hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.6) | Percentage (%) of total stuttering hypotension episodes detected by {Index > 35%} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode (excluding episodes detected prior to first hypotension) | Up to 8 hours |
| AWTs for Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.7) | AWTs for stuttering hypotension episodes detected by {Index > 35%} prior to 10 cumulative min of hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.8) | Percentage (%) of total stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode (excluding episodes detected prior to first hypotension) | Up to 8 hours |
| AWTs for Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.9) | AWTs for stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to 10 cumulative min of hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Not Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.10) | Percentage (%) of total stuttering hypotension episodes not detected by {Index > 35%} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode | Up to 8 hours |
| Percentage of Total Stuttering Hypotension Episodes Not Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.11) | Percentage (%) of total stuttering hypotension episodes not detected by {Index > user's Index threshold setting} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode | Up to 8 hours |
| Participants |
|
| Age, Continuous | Median | Full Range | years |
|
| Sex: Female, Male | Count of Participants | Participants |
|
| Ethnicity (NIH/OMB) | Count of Participants | Participants |
|
| Race (NIH/OMB) | Count of Participants | Participants |
|
| Region of Enrollment | Number | participants |
|
| Participants |
|
|
| Primary | Software Operation (Based on Real-time Observation) | System malfunction (yes/no) observed in real-time by the Technical Observer | Posted | Count of Participants | Participants | Up to 8 hours |
|
|
|
| Primary | Data Completeness | Completeness (yes/no) of flowsheet (data archive of the investigational System) without any lapses in input data from the bedside monitor during connectivity; and without lapses in associated BP forecasts. | Posted | Count of Participants | Participants | Up to 8 hours |
|
|
|
| Primary | Software Operation (Based on Review of Error Logs) | Error-level and critical-level software errors in the runtime log (yes/no) | Posted | Count of Participants | Participants | Up to 8 hours |
|
|
|
| Secondary | Percentage of Time That the BP Forecast is Operative (Outcome 2.1) | Median percentage (%) of time, per patient, during the session when inclusion criteria were otherwise met that the BP forecast was operative (i.e., time intervals when no InOp criteria detected by the System leading to the InOp state) | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Percentage of time | up to 8 hours |
|
|
|
| Secondary | Accuracy of the MAP Forecast (Outcome 2.2) | Accuracy of the future 20 min median MAP forecast (average error between the MAP forecast and the future 20 min median MAP; for purposes of computing future 20 min median MAP, MAP < 10 mmHg and MAP > 250 mmHg is treated as a missing number) over time intervals during the session when inclusion criteria were otherwise met; the BP forecast was operative; and the analysis window criteria were met [at least 19 minutes remaining to the end of the record from the time of the forecast; and the analysis window has no more than 9 min of non-physiological MAP data (non-physiological MAP criteria are MAP < 10mmHg or MAP > 250mmHg or 'NaN')]. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Mean | 95% Confidence Interval | mmHg | Up to 8 hours |
|
|
|
| Secondary | Percentage of Time That the True Future 20 Min Median MAP Falls Within the Forecast Cone (Outcome 2.3) | Median percentage (%) of time, per patient, that the true future 20 min median MAP falls within the computed forecast cone over time intervals during the session when inclusion criteria were otherwise met; the BP forecast was operative; and the analysis window criteria were met [at least 19 minutes remaining to the end of the record from the time of the forecast; and the analysis window has no more than 9 min of non-physiological MAP data (non-physiological MAP criteria are MAP < 10mmHg or MAP > 250mmHg or 'NaN')] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Percentage of time | Up to 8 hours |
|
|
|
| Secondary | SHE Incidence (Outcome 3.1) | SHE incidence per 24 hrs [Sustained hypotensive event "SHE" is any interval commencing upon MAP < goal & 20-min future median MAP is also < goal; terminating upon time point when MAP >= goal and & 20-min future median MAP >= goal; SHEs occurring sequentially within 10 min are merged; any remaining SHEs not persisting at least 10 min are excluded]. [Clarification: We are reporting the mean "events per patient-day" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Events per patient-day (24 hours) | Up to 8 hours |
|
|
|
| Secondary | Percentage of Total SHEs Predicted by {Index > 35%} Prior to Earliest Hypotension (Outcome 3.2.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to the SHE's earliest hypotension [hypotension is defined as MAP < goal, with the exclusion of MAP < 10 mmHg, which is treated as a missing number]. Notification events are intervals that begin when there is an Index value that meets the notification criteria and terminate when there is an Index value output that does not meet the notification criteria. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Advance Warning Times (AWTs) for SHEs Predicted by {Index > 35%} Prior to Earliest Hypotension (Outcome 3.2.2) | AWTs (median) for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to the SHE's earliest hypotension [i.e., MAP < goal]. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Earliest Hypotension (Outcome 3.2.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to the SHE's earliest hypotension [i.e., MAP < goal] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Earliest Hypotension (Outcome 3.2.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to the SHE's earliest hypotension [i.e., MAP < goal]. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs Predicted by {Index > 35%} Prior to Continuous Hypotension (Outcome 3.3.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to continuous hypotension [intervals of ≥ 10 minutes of physiological MAP continuously below the hypotension threshold (physiological MAP are samples that do not meet the non-physiological criteria)]. NOTE: excluding SHEs predicted prior to earliest hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | AWTs for SHEs Predicted by {Index > 35%} Prior to Continuous Hypotension (Outcome 3.3.2) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) prior to continuous hypotension and excluding SHEs predicted prior to earliest hypotension. NOTE: A negative AWT denotes a notification event that occurs chronologically after the onset of the SHE event. For example, an AWT of -3 would mean the first notification event occurred 3 minutes after the onset of the SHE event, although still in advance of continuous hypotension. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Continuous Hypotension (Outcome 3.3.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to continuous hypotension [intervals of ≥ 10 minutes of physiological MAP continuously below the hypotension threshold (physiological MAP are samples that do not meet the non-physiological criteria)]. NOTE: excluding SHEs predicted prior to earliest hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} Prior to Continuous Hypotension (Outcome 3.3.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) prior to continuous hypotension and excluding SHEs predicted prior to earliest hypotension. NOTE: A negative AWT denotes a notification event that occurs chronologically after the onset of the SHE event. For example, an AWT of -3 would mean the first notification event occurred 3 minutes after the onset of the SHE event, although still in advance of continuous hypotension. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs Detected by {Index > 35%} After Continuous Hypotension Onset (Outcome 3.4.1) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) after onset of continuous hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | AWTs for SHEs Predicted by {Index > 35%} After Continuous Hypotension Onset (Outcome 3.4.2) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > 35%) after onset of continuous hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs Detected by {Index > User's Index Threshold Setting} After Continuous Hypotension Onset (Outcome 3.4.3) | Percentage (%) of total SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) after onset of continuous hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | AWTs for SHEs Predicted by {Index > User's Index Threshold Setting} After Continuous Hypotension Onset (Outcome 3.4.4) | AWTs for SHEs predicted by an SHE-contiguous notification event (i.e., Index > user's Index threshold setting) after onset of continuous hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHEs With False Resolutions (Outcome 3.5.1) | Percentage of total SHEs with false resolutions [i.e., MAP >= goal transiently during SHE] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total SHE events | Up to 8 hours | Sustained hypotensive events (SHE) | Sustained hypotensive events (SHE) |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Detected by {Index > 35%} (Outcome 3.5.2) | Percentage (%) of total SHE false resolutions with a contiguous notification event where {Index > 35%} | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Not Detected by {Index > 35%} With InOp State During False Resolution (Outcome 3.5.3) | Percentage of total SHE false resolutions that were not detected by {Index > 35%} and had InOp state occurring during the index false resolution episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Not Detected by {Index > 35%} Without InOp State During False Resolution (Outcome 3.5.4) | Percentage (%) of total SHE false resolutions that were not detected by {Index > 35%} and did not have InOp state occurring during the index false resolution episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Detected by {Index > User's Index Threshold Setting} (Outcome 3.5.5) | Percentage (%) of total SHE false resolutions with a contiguous notification event where {Index > user's Index threshold setting} | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Not Detected by {Index > User's Index Threshold Setting} With InOp State During False Resolution (Outcome 3.5.6) | Percentage (%) of total SHE false resolutions that were not detected by {Index > user's Index threshold setting} and had InOp state occurring during the index false resolution episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Percentage of Total SHE False Resolutions Not Detected by {Index > User's Index Threshold Setting} Without InOp State During False Resolution (Outcome 3.5.7) | Percentage (%) of total SHE false resolutions that were not detected by {Index > user's Index threshold setting} and did not have InOp state occurring during the index false resolution episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total false resolutions | Up to 8 hours | SHE false resolutions | SHE false resolutions |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} That Are Contiguous With SHEs (Outcome 3.6.1) | Incidence of notification events {Index > 35%} that are contiguous with SHEs, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} That Are Contiguous With SHEs (Outcome 3.6.2) | Incidence of notification events {Index > user's Index threshold setting} that are contiguous with SHEs, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} That Are Sentinel Notifications (Outcome 3.6.3) | Incidence of notification events {Index > 35%} that are sentinel notifications [sentinel notification is a notification event that occurs within 60 min prior to an SHE; recorded dose increase; or during stuttering hypotension (defined in 3.7.1)], excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} That Are Sentinel Notifications (Outcome 3.6.4) | Incidence of notification events {Index > user's Index threshold setting} that are sentinel notifications, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} That Are False Notifications (Outcome 3.6.5) | Incidence of notification events {Index > 35%} that are false notifications (defined as notification events not contiguous with an SHE and not a sentinel notification, excluding notification events with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} That Are False Notifications (Outcome 3.6.6) | Incidence of notification events {Index > user's Index threshold setting} that are false notifications. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} Contiguous With an SHE False Resolution (Outcome 3.6.7) | Incidence of notification events {Index > 35%} contiguous with an SHE false resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE False Resolution (Outcome 3.6.8) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE false resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} Contiguous With an SHE True Resolution, Overall (Outcome 3.6.9) | Incidence of notification events {Index > 35%} contiguous with an SHE true resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE True Resolution, Overall (Outcome 3.6.10) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE true resolution. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} Contiguous With an SHE True Resolution, Suppressible (Outcome 3.6.11) | Incidence of notification events {Index > 35%} contiguous with an SHE true resolution after excluding all notification event interval that were within 8 min of a documented clinical intervention. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} Contiguous With an SHE True Resolution, Suppressible (Outcome 3.6.12) | Incidence of notification events {Index > user's Index threshold setting} contiguous with an SHE true resolution after excluding all notification event interval that were within 8 min of a documented clinical intervention. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > 35%} With Onset During an SHE (Outcome 3.6.13) | Incidence of notification events {Index > 35%} with onset during an SHE. [Clarification: We are reporting the mean "notification events / patient-day (24h)" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Incidence of Notification Events {Index > User's Index Threshold Setting} With Onset During an SHE (Outcome 3.6.14) | Incidence of notification events {Index > user's Index threshold setting} with onset during an SHE. [Clarification: We are using "notification events / patient-day (24h)" as the Unit of Measure for several reasons. First, different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Notification events / patient-day (24h) | Up to 8 hours |
|
|
|
| Secondary | Duration of False Notification Events {Index > 35%} (Outcome 3.6.15) | Median duration of false notification events {Index > 35%} | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Notification events | Notification events |
|
|
|
| Secondary | Duration of False Notification Events {Index > User's Index Threshold Setting} (Outcome 3.6.16) | Median duration of false notification events {Index > user's Index threshold setting} | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Notification events | Notification events |
|
|
|
| Secondary | Stuttering Hypotension Incidence (Outcome 3.7.1) | Stuttering hypotension incidence [Stuttering hypotension event commences upon hypotension and with >= 10 min of cumulative hypotension within subsequent 60 min; terminates upon next time point when onset condition is no longer met AND when MAP >= goal; intervals that qualify as an SHE are excluded from stuttering hypotension]. [Clarification: We are reporting the mean "events per patient-day" as the Unit of Measure. Different subjects were observed for different intervals of time, with a maximum 8 hours specified in the protocol. Because subjects were observed for different time intervals, it is helpful to standardize findings as events per unit of time. Standardizing the events to units of time allows for valid inter-subject comparison when subjects have differing observation intervals. Next, events per DAY is a conventional Unit of Measurement that is both valid and easy to interpret, even though subjects were not observed for an entire day.] | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Events per patient-day (24 hours) | Up to 8 hours |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.2) | Percentage (%) of total stuttering hypotension episodes detected by {Index > 35%} prior to the stuttering hypotension's first hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | AWTs for Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.3) | AWTs for stuttering hypotension episodes detected by {Index > 35%} prior to the stuttering hypotension's first hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.4) | Percentage (%) of total stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the stuttering hypotension's first hypotension | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | AWTs for Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to the Stuttering Hypotension's First Hypotension (Outcome 3.7.5) | AWTs for stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the stuttering hypotension's first hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.6) | Percentage (%) of total stuttering hypotension episodes detected by {Index > 35%} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode (excluding episodes detected prior to first hypotension) | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | AWTs for Stuttering Hypotension Episodes Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.7) | AWTs for stuttering hypotension episodes detected by {Index > 35%} prior to 10 cumulative min of hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.8) | Percentage (%) of total stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode (excluding episodes detected prior to first hypotension) | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | AWTs for Stuttering Hypotension Episodes Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.9) | AWTs for stuttering hypotension episodes detected by {Index > user's Index threshold setting} prior to 10 cumulative min of hypotension. NOTE: A positive AWT denotes a notification event that occurs chronologically in advance of the onset of the SHE event. For example, an AWT of +3 would mean the first notification event occurred 3 minutes before the onset of the SHE event. | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Median | Inter-Quartile Range | Minutes | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Not Detected by {Index > 35%} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.10) | Percentage (%) of total stuttering hypotension episodes not detected by {Index > 35%} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| Secondary | Percentage of Total Stuttering Hypotension Episodes Not Detected by {Index > User's Index Threshold Setting} Prior to 10 Cumulative Min of Hypotension (Outcome 3.7.11) | Percentage (%) of total stuttering hypotension episodes not detected by {Index > user's Index threshold setting} prior to the occurrence of 10 cumulative minutes of hypotension within that stuttering hypotension episode | Out of the 20 total patient-subjects, 2 subjects did not begin the protocol which leaves n=18 for the analysis population. | Posted | Number | Percentage of total stuttering events | Up to 8 hours | Stuttering hypotension episodes | Stuttering hypotension episodes |
|
|
|
| 0 |
| 20 |
| 9 |
| 20 |
| 1 |
| 20 |
| Sustained hypotensive event | Cardiac disorders | Systematic Assessment |
|
Not provided
Not provided
Not provided