Search Results

The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes:

• To remotely consult regarding a patient's status, and
• To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.

T3 can display numeric physiologic data captured by other medical devices:

• Airway flow, volume and pressure
• Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
• Bispectral index (BIS, signal quality index, suppression ratio)
• Cardiac Index
• Cardiac output
• Central venous pressure
• Cerebral perfusion pressure
• End-tidal CO2
• Heart rate
• Heart rate variability
• Intracranial pressure
• Left atrium pressure
• Oxygen saturation (intravascular, regional, SpO2)
• Premature ventricular counted beats
• Pulmonary artery pressure (systolic, diastolic, and mean)
• Pulse pressure variation
• Pulse Rate
• Respiratory rate
• Right atrium pressure
• Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
• Umbilical arterial pressure (systolic, diastolic, and mean)

It can also display laboratory measurements including arterial and venous blood gases, complete blood count, and lactic acid.

T3 includes a Patient Risk Analytics Engine that calculates an index (the Inadequate Oxygen Delivery Index) that is indicated for use by health care professionals with postsurgical patients aged zero days to twelve years weighing 2 kg or more under intensive care. The Inadequate Oxygen Delivery Index is derived by mathematical manipulations of the physiologic data and laboratory measurements received by T3. When the index is elevated, it means that there is increased risk of inadequate oxygen delivery and attention should be brought to the patient. The index presents partial quantitative information about the patient's cardiovascular condition, and no therapy or drugs can be administered based solely on the interpretation statements.

The Tracking, Trajectory, Trigger (T3) intensive care unit software solution allows clinicians and quality improvement teams in the ICU to aggregate data from multiple sources, store it in a database for analysis, and view the streaming data in real-time. System features include:

• Customizable display of physiologic parameters over entire patient stay.
• Configurable annotation.
• Web-based visualization that may be used on any standard browser.
• Minimal IT footprint.
• Software-only solution no new bedside hardware required.
• Highly reliable and robust operation.
• Auditable data storage.

The subject device is a modification of the T3 Software that expands the Indications for Use for the Inadequate Oxygen Delivery Index (IDO2) from patients aged 0 - 28 days to patients aged zero days to twelve years. The IDO2 Index is derived by mathematical manipulations of the physiologic data and laboratory measurements received by T3. This index provides an interpretation of how different the patient's physiologic measures are from normality.

In addition to the expansion in the Indications of Use for the IDO2 Index, T3 release 3.0 contains the following changes:

• 1. In previous T3 versions, the Inadequate Oxygen Delivery Index is documented as having the following limitation.
     The index will not be displayed if the following minimum measurements are not available:
• a. Heart rate from ECG or pulse at a minimum of once every 30 seconds
• b. SpO2 from pulse oximetry at a minimum of once every 30 seconds
• c. Blood Pressure (mean/diastolic/systolic) at a minimum of once every 10 minutes
  This limitation has been changed to the following:
  The index will not be displayed if the following minimum measurements are not available:
• a. Heart rate from ECG or pulse at a minimum of once every 60 seconds
• b. SpO2 from pulse oximetry at a minimum of once every 10 minutes
• c. Blood Pressure (mean/diastolic/systolic) at a minimum of once every 10 minutes
  The minimum requirement for Heart Rate data has changed from 30 seconds to 60 seconds, and the minimum requirement for SpO2 has changed from 30 seconds to 10 minutes.
• 2. In previous T3 versions, the software model used to calculate IDO2 had age independent parameters and did not include a number of potentially useful model relationships. In the updated model, parameters are now dependent on patient age. Also, new model states and relationships have been implemented to improve the performance.
• 3. In previous T3 versions, the calibration logic for IDO2 utilized the probability distribution of patient states to determine whether or not to display a given IDO2 value. The new calibration logic is simply time based, waiting 5 minutes to display IDO2 values for a new patient. In addition, if the algorithm is re-initialized for any reason, it will undergo an additional 5 minutes of calibration after the re-initialization.
• 4. The IDO2 labeling contains a list of required and optional algorithm inputs. One required input is SpO2. Previous releases of T3 accepted SpO2 captured by the patient monitor and reported with any of three different labels: "SpO2" (defined as "SpO2 from pulse oximeter"), "SpO2 l" (defined as "arterial oxygen saturation left"), and "SpO2 r" (defined as "arterial oxygen saturation right"). This release of T3 adds SpO2 as reported with two other labels: "SpO2 pr" (defined as "pre-ductal SpO2") and "SpO2 po" (defined as "post-ductal SpO2").
• 5. T3 version 3.0 also includes the following User Interface changes:
• a. A new user interface mode that displays the data originating from a single bed location, even as new patients are transferred into that location. The benefit of this change is that the T3 user is never auto-logged off due to inactivity. Instead, T3 displays either the view of the patient data or a dialog stating that no data is being received for the bed. The mode is suitable for a bedside display, and saves clinicians the time and effort of logging in and navigating to that patient's data each time they want to use T3. To mitigate possible clinician confusion about which patient the data is for, T3 only displays data for one patient at a time - the current patient. Furthermore, the patient's name, medical record number and date of birth are displayed on the screen.
• b. Views: These are predefined arrangements of labs and measures. Views are accessed through a tabbed display. The first instance of the View functionality is the Hemodynamic View, which presents information about the patient's hemodynamic system. Views save clinicians the time and effort to drag meaningful labs and measures to the central graph area in order to display them.
• c. Smart Visualization Groups: These are collections of measures and laboratory results that are graphed together as a single unit. T3 is able to insert shading, vertical lines and other visual cues to emphasize relationships in the data. For example, in the Blood Pressure group, the area between systolic and diastolic pressure is shaded. The shading represents "pulse pressure," a standard measure of the force the heart generates each time it contracts. The shading allows the clinician to see increases or decreases in pulse pressure, in addition to the systolic and diastolic blood pressure values from which pulse pressure is calculated.
• d. When T3 displays a measure it inserts the starting and ending values for the period of time being graphed on the left and right edges of the canvas. It inserts the maximum and minimum values for the measure in circles at the point in time when they occur. If two or more of these values would overlap on the graph, T3 omits all but one of them for clarity. Likewise, if one of these values would obscure the graphic icon for a laboratory result, T3 omits it so the laboratory result is shown.
• e. Night Mode. There are now application-wide configuration settings that specify when "night time" starts and ends. For example, night time can be defined to start at 7PM and end at 7AM - or whatever times are desired. When T3 runs "at night," the application recognizes that it is night based on the system clock, and automatically uses a dark background. This reduces the amount of ambient light that the T3 monitor emits. When it runs during the day, T3 similarly recognizes that it is day and automatically uses a light background. It is possible for individual users to manually override the night mode function. On the patient view screen, T3 adds buttons that let the user manually control night mode. There is a sunshine button that lightens the background, and a moon button that darkens the background. A lock button locks in the user's selection of day or night.
• f. If T3 receives data for a patient measure whose unit of measure is different from what was previously received for that patient and measure, it now displays a temporary warning banner at the top of the display that is automatically dismissed after ten seconds. Previously, T3 displayed the warning, but required the user to dismiss it by clicking on it. In many situations, needing to click to dismiss the warning was inconvenient or impractical. An example of this functionality is if T3 is receiving mean airway pressure for a patient. The monitor may report values in "millibars" then switch to "cmH2O." Both are commonly accepted ways of measuring airway pressure. In this case, the warning will say "Measure mnAWp has inconsistent unit codes. T3 is expecting units of mbar, but received data points with units of cmH2O. Those data points will not be displayed."
• g. The dialog showing additional details for a lab value is now invoked by clicking anywhere on the lab icon. Previously it was invoked by hovering the mouse cursor over the exact data point for the lab value. The new functionality is more forgiving if the mouse cursor is slightly misplaced, and is less susceptible to displaying unwanted tooltips when the user moves the mouse cursor around the screen.
• 6. Typically, a clinician enters the patient's medical record number (MRN) into the bedside monitor. The physio interface sent to T3 from that monitor then includes the MRN and bed location along with the data values for the patient. T3 now supports an alternate workflow where the hospital's Admit, Discharge and Transfer (ADT) interface is used as the definitive source of patient identity and location information. The physio interface contains bed location along with the data values for the patient, but T3 derives the MRN by matching the bed location sent in the physio interface with the bed location / MRN pairing sent in the ADT interface. In order to recover from a situation where an ADT message is not delivered to T3 for some reason, or T3 processes it incorrectly, there is also a user interface in T3 that allows an administrator to explicitly specify the MRN for the patient occupying a bed location. This has the same effect as an ADT message associating a patient with a bed location.
• 7. T3 can now send an informational email to one or more configured email addresses when it detects that data is being received from a bed location without an associated patient medical record number, or when it detects that data is simultaneously being received from multiple bed locations with the same associated MRN. The recipient of the email can then investigate and correct the problem. The email does not contain protected health information; instead it specifies the bed locations where the issue occurs.
• 8. The T3 labeling lists a series of clinical calculations that can be configured upon clinician demand. These clinical calculations are simple algebraic formulas that accept raw parameters and output a single result. An example is Pulse Width which is equal to Systolic blood pressure minus Diastolic blood pressure. This release of T3 adds the following calculations to the list that may be requested by clinicians:
     | Label | Name | Formula |
     |---|---|---|
     | P/F | P/F Ratio | PaO2 / FiO2 |
     | S/F | S/F Ratio | SpO2 / FiO2 |
     | OI | Oxygenation Index | (FiO2 * Mean Airway Pressure * 100) / PaO2 |
     | OSI | Oxygen Saturation Index | (FiO2 * Mean Airway Pressure * 100) / SpO2 |

Here is a summary of the acceptance criteria and the study that proves the device meets the acceptance criteria, based on the provided document:

1. Table of Acceptance Criteria and Reported Device Performance

The document does not explicitly present a table of acceptance criteria with numerical targets and corresponding device performance metrics for the T3 Software (Version 3.0). Instead, it focuses on demonstrating substantial equivalence to its predicate device (T3 Software Version 2.0) and supporting the expanded Indications for Use of the Inadequate Oxygen Delivery Index (IDO2).

The key "performance" aspect discussed is the validation of the IDO2 Index in the expanded patient population.

2. Sample Size Used for the Test Set and Data Provenance

• Sample Size: Clinical data from 1504 patients were used for the validation study.
• Data Provenance: The data was described as "clinical data gathered in the intended patient population" and covered "the expanded patient age range." The country of origin is not specified, but it's typically assumed to be U.S. clinical data for FDA submissions unless otherwise stated. The document doesn't specify if the data was retrospective or prospective, but clinical validation studies often leverage retrospective data for initial submissions unless a specific prospective trial is mentioned.

3. Number of Experts Used to Establish the Ground Truth for the Test Set and Qualifications

The document does not provide information on the number of experts used or their qualifications to establish ground truth for the test set. It mentions the "IDO2 Index ... correlates with changes in the patient's physical status," implying that some form of clinical assessment or patient outcome served as the ground truth, but the specifics of its establishment are not detailed.

4. Adjudication Method for the Test Set

The document does not specify any adjudication method (e.g., 2+1, 3+1, none) used for establishing ground truth or evaluating the device's performance.

5. If a Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study Was Done, and Effect Size

The document does not indicate that an MRMC comparative effectiveness study was done to assess how much human readers improve with AI vs. without AI assistance. The T3 Software, particularly the IDO2 Index, is described as an index that "presents partial quantitative information about the patient's cardiovascular condition" to aid healthcare professionals in clinical decisions, but not as an AI-assisted diagnostic tool requiring reader performance comparison.

6. If a Standalone (Algorithm Only Without Human-in-the-Loop Performance) Was Done

Yes, a form of standalone performance assessment was conducted for the IDO2 Index. The validation study "using clinical data" to demonstrate correlation with "changes in the patient's physical status" against a ground truth (even if unspecified in detail) is a standalone evaluation of the algorithm's output. The device itself (T3 Software) is also described as a "Software-only solution."

7. The Type of Ground Truth Used

The ground truth implicitly used for the IDO2 Index validation is related to "changes in the patient's physical status." This likely refers to clinically relevant changes as observed by healthcare professionals, or potentially outcomes data, but the specific nature (e.g., expert consensus on patient status, objective physiological changes, or adverse events) is not explicitly defined in this summary.

8. The Sample Size for the Training Set

The document does not provide information about the sample size used for the training set of the T3 Software or the IDO2 algorithm. It only mentions the 1504 patients for the validation study.

9. How the Ground Truth for the Training Set Was Established

The document does not provide information on how the ground truth for the training set was established, as the training set details are not included in this summary.

Ask a specific question about this device

The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes:

• To remotely consult regarding a patient's status, and
• To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.
  T3 can display numeric physiologic data captured by other medical devices:
• Airway flow, volume and pressure
• Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
• Bispectral index (BIS, signal quality index, suppression ratio)
• Cardiac Index
• Cardiac output
• Central venous pressure
• Cerebral perfusion pressure
• End-tidal CO2
• Heart rate
• Heart rate variability
• Intracranial pressure
• Left atrium pressure
• Oxygen saturation (intravascular, regional, SpO2)
• Premature ventricular counted beats
• Pulmonary artery pressure (systolic, diastolic, and mean)
• Pulse pressure variation
• Pulse Rate
• Respiratory rate
• Right atrium pressure
• Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
• Umbilical arterial pressure (systolic, diastolic, and mean)
  It can also display laboratory measurements including arterial and venous blood count, and lactic acid.
  T3 includes a Patient Risk Analytics Engine that calculates an index (the Inadequate Oxygen Delivery Index) that is indicated for use by health care professionals with post-surgical neonatal patients weighing 2 kg or more under intensive care. The Inadequate Oxygen Delivery Index is derived by mathematical manipulations of the physiologic data and laboratory measurements received by T3. When the index is elevated, it means that there is increased risk of inadequate oxygen delivery and attention should be brought to the index presents partial quantitative information about the patient's cardiovascular condition, and no therapy or drugs can be administered based solely on the interpretation statements.
  WARNING: T3 Software is not an active patient monitoring system. It is intended to supplement and not replace any part of the hospital's device monitoring. Do not rely on the T3 Software Solution as the sole source of patient status information.

The Tracking, Trajectory, Trigger (T3) intensive care unit software solution allows clinicians and quality improvement teams in the ICU to aggregate data from multiple sources, store it in a database for analysis, and view the streaming data in real-time. System features include:

• Customizable display of physiologic parameters over entire patient stay.
• Configurable annotation
• Web-based visualization that may be used on any standard browser
• Minimal IT footprint
• Software-only solution no new bedside hardware required
• Highly reliable and robust operation.
• Auditable data storage.
  The subject device is a modification of the T3 Software that includes Risk Analytics Engine that computes an Inadequate Oxygen Delivery Index (IDO2). The IDO2 Index is derived by mathematical manipulations of the physiologic data and laboratory measurements received by T3. This index provides an interpretation of how different the patient's physiologic measures are from normality.

The provided text describes the T3 Software, version 2.0.1, which includes a Patient Risk Analytics Engine calculating an Inadequate Oxygen Delivery Index (IDO2). The document is a 510(k) summary, making it a submission to the FDA for market clearance, stating that the new version is substantially equivalent to previous versions and other predicate devices.

Here's an analysis of the acceptance criteria and the study that proves the device meets them, based only on the provided text:

1. A table of acceptance criteria and the reported device performance

The document does not explicitly present specific, quantitative acceptance criteria for the IDO2 Index. Instead, it relies on demonstrating that the device's software functions as intended and that the IDO2 Index correlates with changes in physical status, similar to a predicate device.

2. Sample size used for the test set and the data provenance (e.g. country of origin of the data, retrospective or prospective)

The document states: "Additionally, validation study results using clinical data gathered in the intended patient population demonstrate the IDO2 Index included in the subject device correlates with changes in the patient's physical status, as does the Visensia Index."

• Sample Size: The sample size for the "validation study" is not specified in the provided text.
• Data Provenance: The country of origin of the data is not specified. The text only mentions "clinical data gathered in the intended patient population." It is also not specified if the data was retrospective or prospective.

3. Number of experts used to establish the ground truth for the test set and the qualifications of those experts (e.g. radiologist with 10 years of experience)

The document does not provide any information regarding the number of experts used or their qualifications for establishing ground truth in the validation study. The ground truth refers to "changes in the patient's physical status," but how this was determined by experts is not detailed.

4. Adjudication method (e.g., 2+1, 3+1, none) for the test set

The document does not specify any adjudication method used for the test set.

5. If a multi-reader multi-case (MRMC) comparative effectiveness study was done, If so, what was the effect size of how much human readers improve with AI vs without AI assistance

The document does not describe a multi-reader multi-case (MRMC) comparative effectiveness study. The study focused on the correlation of the IDO2 Index with patient physical status. There is no mention of human readers or their improvement with or without AI assistance. The device is intended to aid clinical decisions and provide quantitative information, but not in a comparative effectiveness study involving human interpretation.

6. If a standalone (i.e., algorithm only without human-in-the-loop performance) was done

Yes, the validation study appears to be a standalone performance study of the algorithm. The statement "validation study results... demonstrate the IDO2 Index... correlates with changes in the patient's physical status" indicates an evaluation of the algorithm's output (the IDO2 Index) against an independent measure of patient status, without involving human-in-the-loop performance measurement.

7. The type of ground truth used (expert consensus, pathology, outcomes data, etc.)

The ground truth used is "changes in the patient's physical status." The specific method for determining "changes in the patient's physical status" (e.g., expert consensus, specific clinical criteria, or other outcomes data) is not detailed in the provided text.

8. The sample size for the training set

The document does not specify a separate "training set" or its sample size. The description focuses on the validation of the IDO2 Index, which implies the algorithm's parameters were already established.

9. How the ground truth for the training set was established

Since a "training set" is not mentioned, the document does not provide information on how ground truth for any training set was established. The IDO2 Index is described as being "derived by mathematical manipulations of the physiologic data and laboratory measurements," suggesting a formulaic or rule-based derivation rather than a machine learning model trained on labeled data in the context usually implied by "training set ground truth."

Ask a specific question about this device

The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes:

• · To remotely consult regarding a patient's status, and
• · To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.

T3 can display numeric physiologic data captured by other medical devices:

• · Airway flow, volume and pressure
• · Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
• · Bispectral index (BIS, signal quality index, suppression ratio)
• Cardiac Index
• Cardiac output
• Central venous pressure
• · Cerebral perfusion pressure
• · End-tidal CO2
• · Heart rate
• · Heart rate variability
• · Intracranial pressure
• · Left atrium pressure
• · Oxygen saturation (intravascular, regional, SpO2)
• · Premature ventricular counted beats
• · Pulmonary artery pressure (systolic, diastolic, and mean)
• · Pulse pressure variation
• Pulse Rate
• · Respiratory rate
• · Right atrium pressure
• · Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
• · Umbilical arterial pressure (systolic, diastolic, and mean)

It can also display laboratory measurements including arterial and venous blood count, and lactic acid.

WARNING: T3 Software is not an active patient monitoring system. It is intended to supplement and not replace any part of the hospital's device monitoring. Do not rely on the T3 Software Solution as the sole source of patient status information.

The Tracking, Trajectory, Trigger (73) intensive care unit software solution allows clinicians and quality improvement teams in the ICU to aggregate data from multiple sources, store it in a database for analysis, and view the streaming data in real-time. System features include:

• Customizable display of physiologic parameters over entire patient stay ●
• Configurable annotation .
• Web-based visualization that may be used on any standard browser ●
• . Minimal IT footprint
• Software-only solution no new bedside hardware required .
• Highly reliable and robust operation
• Auditable data storage .

The T3 Software is intended for the display and recording of multiple physiological parameters of adult, pediatric and neonatal patients. T3 is not intended for alarm notification, nor is it intended to control any of the independent bedside devices to which it is connected

The T3 software can display user-defined, derived measures. These measures include the percentage of time within a time period that a particular variable is above or below a threshold. The user can configure the time period, threshold, and label of the resulting derived measure for ease of use considerations, only.

The T3 Software is not an active patient monitoring system. It is intended to supplement and not replace any part of the hospital's device monitoring.

T3 has a web architecture consisting of a user interface that runs in a browser, and a central web server. The T3 server, a set of cooperating web services written in Java, processes data as it is received, caches it in memory, and writes out copies of the data to a relational database and to the file system. In this manner, the data is available to the user interface to be visualized by the end user - a clinician.

Clinicians access the T3 user interface in a web browser. T3 runs in current browsers that support HTML5, Javascript and web sockets, such as Chrome, Firefox, Safari and Internet Explorer. The clinicians may be in the hospital, or may be outside the hospital accessing T3 over a Virtual Private Network (VPN). Clinicians use T3 in addition to the physiometric devices themselves and other information sources such as the electronic medical record to monitor the patient's condition.

The provided document is a 510(k) premarket notification for the Etiometry T3 Software Version 1.9. It outlines the device's indications for use and compares its technological characteristics to a predicate device. However, it explicitly states that clinical testing was not required for this submission.

Therefore, the document does not contain a study that proves the device meets specific acceptance criteria in terms of clinical performance. Instead, its substantial equivalence is based on software verification and validation, and comparison to a predicate device.

Given that no clinical study was conducted as part of this submission, I cannot provide the requested information about acceptance criteria, sample sizes, expert involvement, adjudication methods, MRMC studies, standalone performance, or ground truth details.

The document states:

• "Software verification and validation testing has been conducted for T3 Software and documentation has been provided in accordance with FDA 's "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices", May 11, 2005."
• "Clinical testing was not required."

This indicates that the "performance data" referred to in Section VII primarily pertains to software V&V, ensuring the software performs as designed and intended, rather than proving clinical efficacy or diagnostic accuracy against a clinical ground truth.

If you have other documents that describe clinical performance studies for this device, please provide them.

Ask a specific question about this device

The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes:

• · To remotely consult regarding a patient's status, and
• · To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.

T3 can display numeric physiologic data captured by other medical devices:

• · Airway flow, volume and pressure
• · Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
• · Bispectral index (BIS, signal quality index, suppression ratio)
• Cardiac Index
• · Cardiac output
• · Central venous pressure
• · Cerebral perfusion pressure
• · End-tidal CO2
• · Heart rate
• · Heart rate variability
• · Intracranial pressure
• · Left atrium pressure
• · Oxygen saturation (intravascular, regional, SpO2)
• · Premature ventricular counted beats
• · Pulmonary artery pressure (systolic, diastolic, and mean)
• · Pulse pressure variation
• · Pulse Rate
• · Respiratory rate
• · Right atrium pressure
• · Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
• · Umbilical arterial pressure (systolic, diastolic, and mean)

WARNING: T3 Software is not an active patient monitoring system; it is intended to supplement and not replace any part of the hospital's device monitoring. Do not rely on the T3 Software as the sole source of patient status information.

The Tracking, Trajectory, Trigger (73) intensive care unit software solution allows clinicians and quality improvement teams in the ICU to aggregate data from multiple sources, store it in a database for analysis, and view the streaming data in real-time. System features include:

• Customizable display of physiologic parameters over entire patient stay ●
• Configurable annotation ●
• Web-based visualization that may be used on any standard browser ●
• Minimal IT footprint ●
• Software-only solution no new bedside hardware required ●
• Highly reliable and robust operation ●
• Auditable data storage ●

The T3 Software is intended for the display and recording of multiple physiological parameters of adult, pediatric and neonatal patients. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected.

The T3 software can display user-defined, derived measures. These measures include the percentage of time within a time period that a particular variable is above or below a threshold. The user can configure the time period, threshold, and label of the resulting derived measure for ease of use considerations, only.

The T3 Software is not an active patient monitoring system. It is intended to supplement and not replace any part of the hospital's device monitoring.

T3 has a web architecture consisting of a user interface that runs in a browser, and a central web server. The T3 server, a set of cooperating web services written in Java, processes data as it is received, caches it in memory, and writes out copies of the data to a relational database and to the file system. In this manner, the data is available to the user interface to be visualized by the end user – a clinician.

Clinicians access the T3 user interface in a web browser. T3 runs in current browsers that support HTML5, Javascript and web sockets, such as Chrome, Firefox, Safari and Internet Explorer. The clinicians may be in the hospital, or may be outside the hospital accessing T3 over a Virtual Private Network (VPN). Clinicians use T3 in addition to the physiometric devices themselves and other information sources such as the electronic medical record to monitor the patient's condition.

The T3 Software is a medical device intended for the recording and display of multiple physiological parameters of adult, pediatric, and neonatal patients from supported bedside devices. It is not intended for alarm notification, waveform display, or to control independent bedside devices. It is meant to aid healthcare professionals in remote consultation and review of patient data for clinical decisions.

Here's an analysis of the acceptance criteria and the study that proves the device meets them:

1. Table of Acceptance Criteria and Reported Device Performance:

The document does not provide a formal table of quantitative acceptance criteria with specific performance metrics (e.g., sensitivity, specificity, accuracy) and corresponding reported device performance. Instead, it states that:

2. Sample Size Used for the Test Set and Data Provenance:

The document does not specify a "test set" in the traditional sense of a dataset used for performance evaluation of a clinical algorithm. The performance evaluation was focused on software verification and validation rather than clinical outcomes. Therefore, information on sample size for a test set and its data provenance (e.g., country of origin, retrospective/prospective) is not applicable and not provided in this context.

3. Number of Experts Used to Establish Ground Truth for the Test Set and Qualifications of those Experts:

Since there isn't a traditional "test set" and clinical ground truth in the context of an algorithm's diagnostic or predictive performance, this information is not applicable and not provided. The assessment was purely technical for software functionality.

4. Adjudication Method for the Test Set:

As there was no traditional test set with clinical ground truth requiring adjudication, this information is not applicable and not provided.

5. Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study:

A MRMC comparative effectiveness study was not conducted. The document focuses on software verification and validation, and demonstrating substantial equivalence to a predicate device, not on improving human reader performance with AI assistance.

6. Standalone (Algorithm Only) Performance:

The T3 Software itself is a "standalone" software solution in the sense that it processes data and displays it without direct human intervention in its core data processing. However, it is explicitly stated that this software is not an active patient monitoring system and is intended to supplement and not replace any part of the hospital's device monitoring. Therefore, it's not a standalone diagnostic or predictive algorithm for which performance metrics like sensitivity/specificity would typically be reported. Its "standalone" performance is its ability to accurately record and display parameters.

7. Type of Ground Truth Used:

The "ground truth" for the software validation was defined by the software requirements and performance specifications. The software was tested to confirm it functions as intended and meets these predetermined specifications. This is a technical "ground truth" rather than a clinical ground truth (e.g., pathology, outcomes data, or expert consensus on a diagnosis).

8. Sample Size for the Training Set:

The document describes software verification and validation, not the training of a machine learning algorithm. Therefore, there is no training set in this context, and this information is not applicable and not provided.

9. How the Ground Truth for the Training Set Was Established:

As there was no training set for a machine learning algorithm, the concept of establishing ground truth for it is not applicable and not provided.

Ask a specific question about this device