(135 days)
The Monitoring Waveform Viewer is indicated for use as follows:
The Monitoring Waveform Viewer is a software component utilized within another software application.
The Monitoring Waveform Viewer performs the following:
- Display of data generated by multi-parameter patient monitoring systems continuously producing waveforms and parameters.
- Display of reported alarm states produced by such monitoring systems.
- Display of static waveforms for review of existing data, with the possibility to activate a magnification tool. The magnification tool will enlarge the signal located under the magnification icon.
- Perform measurements with the support of a caliper tool (providing horizontal/time measurements and vertical/signal amplitude measurements). The caliper tool can be activated when the Monitoring Waver displays still waveforms.
- Provide selected waveform episodes to the host application for printing or inclusion in the patient record.
The Monitoring Waveform Viewer:
- Is not a primary or secondary alarm device.
- Does not provide a user interface for acknowledging or silencing active alarms.
- Does not generate audible or visual (flashing) notifications of active alarms.
The Monitoring Waveform Viewer does not provide any support for implementing an application that is part of an alarm system.
The Monitoring Waveform Viewer is a software component that includes a system for reviewing snapshots of monitoring data and offers a measurement module with user controlled calipers and magnifier glass.
Medical device data or information system applications may utilize the Monitoring Waveform Viewer software component that includes a stand-alone executable module that functions as a host application. The Monitoring Waveform Viewer is organized as a drawing surface with three areas:
- a parameters area located at the bottom of the window, .
- a parameter waveform area located at the right and
- . a main waveform area.
The parameters area is dedicated to report the values of parameters not associated with displayed waveforms. The parameter waveform area is dedicated to report the values of parameters associated to the displayed waveforms.
The application supports several numerical parameters such as: ECG (electrocardiogram), ART (arterial pressure), PA (pulmonary artery invasive blood pressure), ICP (intracranial pressure), IABP (intra-aotic balloon pump pressure), RR (respiration rate), EtCO2 (end tidal carbon dioxide), SpO2 (oxygen saturation), etc.
The Monitoring Waveform Viewer receives data parameters and waveforms supplied from multi-parameter patient monitoring systems. The Monitoring Waver is able to display alarm states by highlighting the corresponding parameter box. The Monitoring Waveform Viewer operating in near real time mode supports alarm priorities of High Priority, Medium Priority, and Low Priority.
The Monitoring Waveform Viewer allows the user to right-click over any ECG lead or the ECG parameter box to activate a context menu for selecting the ECG gain and displayed leads. The user is able to select a list of active (with data) ECG leads received from the host application. It also allows the user to select gains of 5, 10, 20 and 40mm/mV. The Monitoring Waveform Viewer provides a caliper tool for performance amplitude and interval measurements on the displayed traces. The caliper can be placed anywhere on the waveform display area.
The provided document is a 510(k) notification for the Mortara Monitoring Waveform Viewer, a software component. It primarily focuses on demonstrating substantial equivalence to a predicate device rather than presenting a detailed clinical study with acceptance criteria in the typical sense of diagnostic metrics (e.g., sensitivity, specificity).
However, based on the Performance Testing: Software Testing section, we can infer some aspects related to acceptance criteria and the "study" that proves the device meets those criteria.
Here's an attempt to extract the requested information, understanding that this is a software component and not a diagnostic device with traditional performance metrics:
Acceptance Criteria and Device Performance for Mortara Monitoring Waveform Viewer
1. Table of Acceptance Criteria and Reported Device Performance
Given that this is a software component for viewing and measuring waveforms, the "acceptance criteria" are related to its functional and performance specifications. Since specific quantitative thresholds are not provided in the document beyond a general statement of compliance, the table below represents the implicit criteria and reported performance.
| Acceptance Criteria Category | Specific Criteria (Inferred from device function) | Reported Device Performance |
|---|---|---|
| Functional Accuracy | Display data generated by multi-parameter patient monitoring systems continuously. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Functional Accuracy | Display reported alarm states (High, Medium, Low Priority) by highlighting the corresponding parameter box. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Functional Accuracy | Display static waveforms for review of existing data. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Functional Accuracy | Magnification tool correctly enlarges the signal. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Measurement Accuracy | Caliper tool performs accurate horizontal/time and vertical/signal amplitude measurements on displayed traces. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Integration/Compatibility | Provides selected waveform episodes to the host application for printing or inclusion in patient record. | "Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| General Software Quality | Meets all predetermined software specifications and requirements. | "Software for the Mortara Monitoring Waveform Viewer was designed and developed according to a robust software development process, and was rigorously verified and validated. Test results indicated that the Mortara Monitoring Waver complies with its predetermined specification." |
| Safety - Non-Alarm Device | Does not function as a primary/secondary alarm, acknowledge/silence alarms, or generate audible/visual alarm notifications. | Explicitly stated in "Indications for Use" and "Description" as design constraints. Implicitly confirmed by adherence to design. |
2. Sample Size Used for the Test Set and Data Provenance
- Sample Size: Not explicitly stated. The document mentions "test results." For software testing, the "sample size" would typically refer to the number of test cases executed. This information is not provided.
- Data Provenance: Not specified. The testing was conducted internally by Mortara Instrument, Inc. It's likely simulated or recorded patient data was used, but the origin (e.g., country, retrospective/prospective) is not detailed.
3. Number of Experts Used to Establish the Ground Truth for the Test Set and Qualifications
- Number of Experts: Not applicable or not specified. For functional software testing, "ground truth" often refers to the expected output of the software for given inputs, which is derived from the software's specified requirements. There is no mention of external human experts establishing ground truth for evaluating the software's performance on patient data, as this is a viewing and measurement tool, not a diagnostic one. The accuracy of measurements would likely be benchmarked against known values or manual measurements on the displayed data, rather than expert consensus on a clinical outcome.
- Qualifications of Experts: Not applicable or not specified.
4. Adjudication Method for the Test Set
- Adjudication Method: Not applicable. Since expert consensus on clinical diagnoses is not explicitly used to establish ground truth for this type of device, an adjudication method for conflicting expert opinions is not relevant or described. The "adjudication" in this context would likely be comparing software output to predetermined correct outputs based on specifications.
5. If a Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study was Done
- MRMC Study: No. The document does not describe an MRMC study. The device is a "viewer" and "measurement tool," not a diagnostic AI intended to assist human readers in interpretation that would typically warrant an MRMC study. The focus is on the software component's ability to accurately display and measure, not on improving human diagnostic accuracy.
6. If a Standalone (i.e. algorithm only without human-in-the-loop performance) was Done
- Standalone Performance: Yes, in essence. The "Software Testing" and "Performance Testing – Bench" sections describe the device's performance as software. This testing evaluates the algorithm (software component) independently against its predetermined specifications for display, measurement, and functionality. There is no human-in-the-loop performance described beyond the general statement that "The data and analysis provided by the Monitoring Waveform Viewer is reviewed, confirmed, and used by trained medical personnel." The performance tests themselves assess the software's outputs directly.
7. The Type of Ground Truth Used
- Type of Ground Truth: The ground truth for this software component would be based on its functional specifications and expected outputs. For display features, it would be whether the waveforms and parameters are displayed correctly and accurately represent the input data. For the caliper tool, ground truth would be the known accurate measurements of simulated or recorded waveforms. This is essentially "specification-based verification" or "expected output" rather than clinical ground truth like pathology or outcomes data.
8. The Sample Size for the Training Set
- Sample Size: Not applicable. This device is a software component for viewing and measurement; it does not appear to employ machine learning or AI that would require a "training set" in the conventional sense. The software is developed based on deterministic algorithms and rules.
9. How the Ground Truth for the Training Set was Established
- How Ground Truth was Established: Not applicable, as there is no "training set" for this type of software component. Its functionality is based on direct programming logic and specifications rather than learning from data.
§ 870.1025 Arrhythmia detector and alarm (including ST-segment measurement and alarm).
(a)
Identification. The arrhythmia detector and alarm device monitors an electrocardiogram and is designed to produce a visible or audible signal or alarm when atrial or ventricular arrhythmia, such as premature contraction or ventricular fibrillation, occurs.(b)
Classification. Class II (special controls). The guidance document entitled “Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm” will serve as the special control. See § 870.1 for the availability of this guidance document.