Critical Alert CommonPath Enterprise
K193043 · Critical Alert · MSX · May 11, 2020 · Cardiovascular
Device Facts
| Record ID | K193043 |
| Device Name | Critical Alert CommonPath Enterprise |
| Applicant | Critical Alert |
| Product Code | MSX · Cardiovascular |
| Decision Date | May 11, 2020 |
| Decision | SESE |
| Submission Type | Traditional |
| Regulation | 21 CFR 870.2300 |
| Device Class | Class 2 |
| Attributes | Software as a Medical Device |
Intended Use
The intended use of Critical Alert CommonPath Enterprise is to provide an interface with clinical systems to forward information associated to the particular event to the designated display device(s). For medical, near real time alarms, Critical Alert CommonPath Enterprise is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. Critical Alert CommonPath Enterprise does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audible and/or vibrating mechanism upon receipt of the alert. Critical Alert CommonPath Enterprise is intended for use as a secondary alert. It does not replace the alarm function on the primary device.
Device Story
Software application installed on Windows server environment; acquires alarms, events, and parameters from clinical systems via wired ethernet. Transforms inputs by formatting data for wireless delivery to third-party mobile display devices. Used in clinical settings by healthcare professionals to maintain awareness of patient status and alarm conditions when away from primary monitoring systems. Output consists of text, tones, or data on mobile devices. Does not alter primary device alarm behavior; serves as secondary notification system. Benefits include improved clinician responsiveness to patient events by providing remote, time-critical information.
Clinical Evidence
Bench testing only. Performance verified against internal requirements and standards including IEC 60601-1-8 (alarm systems) and IEC 62366-1 (usability engineering). No clinical data presented.
Technological Characteristics
Windows-based server software; hardware includes rack-mount server (16 GB RAM, 4x500GB RAID 10, 2x3.0 GHz Quad Core). Connectivity via wired ethernet (TCP/IP LAN) to clinical systems and wireless messaging to mobile devices. Supports NTPv4 time synchronization. Messaging compatibility includes Unite Connectivity Manager, TAP, ECG-SNPP, ECG-OAI, ECG-Cisco, and SMTP protocols.
Indications for Use
Indicated for use as a secondary, parallel, redundant alarm forwarding mechanism to inform healthcare professionals of medical events from primary clinical systems. Not intended to replace primary device alarm functions or alter primary device behavior.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
Predicate Devices
- Ascom Sweden AB / Unite Connect for Clinical Systems (K180566)
- Cardiopulmonary Corporation / Bernoulli Enterprise Software (K130208)
Related Devices
- K112282 — M VISUM ALERT ALARM MANAGEMENT SYSTEM · Mvisum, Inc. · Nov 4, 2011
- K112650 — CONNEXALL SUITE OF SOFTWARE PRODUCTS · Connexall USA, Inc. · Feb 1, 2012
- K102974 — INTELLISPHERE EVENT MANAGMENT SYSTEM REL. 10.00 · Philips Medical Systems · Jan 4, 2011
- K180566 — Unite Connect for Clinical Systems · Ascom Sweden AB · Apr 3, 2018
- K180430 — Digistat Smart Central · Ascom Ums Srl Unipersonale · Nov 23, 2018
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo is a blue square with the letters "FDA" in white, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue.
May 11, 2020
Critical Alert % Thomas Kroenke Principal Consultant Speed to Market, Inc. PO Box 3018 Nederland, Colorado 80466
Re: K193043
Trade/Device Name: Critical Alert CommonPath Enterprise Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MSX, PHC Dated: March 30, 2020 Received: March 31, 2020
Dear Thomas Kroenke:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's
{1}------------------------------------------------
requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Jennifer Shih Assistant Director (Acting) Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
### Indications for Use
510(k) Number (if known): K193043
Device Name: Critical Alert CommonPath Enterprise
Indications For Use: The intended use of Critical Alert CommonPath Enterprise is to provide an interface with clinical systems to forward information associated to the particular event to the designated display device(s).
For medical, near real time alarms, Critical Alert CommonPath Enterprise is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. Critical Alert CommonPath Enterprise does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audible and/or vibrating mechanism upon receipt of the alert.
Critical Alert CommonPath Enterprise is intended for use as a secondary alert. It does not replace the alarm function on the primary device.
Prescription Use × (Part 21 CFR 801 Subpart D) AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of Center for Devices and Radiological Health (CDRH)
Page 1 of _1 _________________________________________________________________________________________________________________________________________________________________
{3}------------------------------------------------
| Submission Date: | 11 May 2020 | | |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------------------------------------------------------------------------|
| Submitter: | Critical Alert<br>4901 Belfort Road, Suite 130<br>Jacksonville, FL 32256 | | |
| Submitter<br>Correspondent | Mr. John Elms<br>Phone: +1 (904) 260-6334<br>Email: JElms@criticalalert.com | | |
| Application<br>Correspondent: | Thomas Kroenke<br>Principal Consultant<br>Speed To Market, Inc.<br>PO Box 3018<br>Nederland, CO 80466 USA<br>tkroenke@speedtomarket.net<br>+1 (303) 956 4232 | | |
| Manufacturing Site: | Critical Alert<br>4901 Belfort Road, Suite 130<br>Jacksonville, FL 32256 | | |
| Trade Name: | Critical Alert CommonPath Enterprise | | |
| Common Name: | Physiological Monitors Network And Communication System | | |
| Classification<br>Name: | Physiological Monitors Network And Communication System | | |
| Classification<br>Regulation: | 21 CFR §870.2300, 21 CFR §880.5725 | | |
| Product Code: | MSX, PHC | | |
| Substantially<br>Equivalent Devices: | New Critical Alert<br>Model | Predicate<br>510(k) Number | Predicate<br>Manufacturer / Model |
| | Critical Alert<br>CommonPath<br>Enterprise | K180566 | Ascom Sweden AB / Unite<br>Connect for Clinical Systems<br>(Primary) |
| | | K130208 | Cardiopulmonary Corporation<br>/ Bernoulli Enterprise Software<br>(Secondary) |
{4}------------------------------------------------
| Device Description: | Critical Alert CommonPath Enterprise (CommonPath) is a software application installed on a Windows server environment capable of acquiring alarms, events, and parameters from clinical systems and intelligently forwarding this information as notifications to designated display devices provided by third-party mobile device companies.<br><br>Critical Alert CommonPath Enterprise is intended for use as a secondary alarm; it does not replace the alarm function on the primary device.<br><br>Users receive interactive, time-critical information from clinical systems directly via their display devices as text (visual) or alarms (audible) or data. Received attributes related to the presentation of alerts include text and tones (beeps) in addition to and in coordination with event priorities. CommonPath allows users to be aware of their patients' status and alarm conditions when they are away from the patient and patient monitoring system.<br><br>CommonPath connects to the information sources through wired ethernet connections which are part of the customer's infrastructure and acquires patient data from clinical systems. The user configures CommonPath to determine which information, including alarm notifications, is delivered to which users. CommonPath then formats the data for wireless delivery to the display devices through a messaging server. |
|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for Use: | The intended use of Critical Alert CommonPath Enterprise is to provide an interface with clinical systems to forward information associated to the particular event to the designated display device(s).<br><br>For medical, near real time alarms, Critical Alert CommonPath Enterprise is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. Critical Alert CommonPath Enterprise does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audible and/or vibrating mechanism upon receipt of the alert.<br><br>Critical Alert CommonPath Enterprise is intended for use as a secondary alarm. It does not replace the alarm function on the primary device. |
{5}------------------------------------------------
#### Technology Comparison:
Critical Alert CommonPath Enterprise employs the same technological characteristics as the predicate device.
| Characteristic | Ascom Sweden AB<br>Unite Connect for Clinical Systems<br>(K180566) | Critical Alert<br>CommonPath Enterprise<br>(Proposed Device) | |
|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for<br>Use | The intended use of the Ascom<br>Unite Connect for Clinical Systems<br>is to provide an interface with<br>clinical systems to forward<br>information associated to the<br>particular event to the designated<br>display device(s). | The intended use of Critical Alert<br>CommonPath Enterprise is to<br>provide an interface with clinical<br>systems to forward information<br>associated to the particular event to<br>the designated display device(s). | |
| | For medical, near real time alarms,<br>the Connect for Clinical Systems is<br>intended to serve as a parallel,<br>redundant, forwarding mechanism to<br>inform healthcare professionals of<br>particular medical related events. | For medical, near real time alarms,<br>Critical Alert CommonPath<br>Enterprise is intended to serve as a<br>parallel, redundant, forwarding<br>mechanism to inform healthcare<br>professionals of particular medical<br>related events. | |
| | Connect for Clinical Systems does<br>not alter the behavior of the primary<br>medical devices and associated<br>alarm annunciations. The display<br>device provides a visual, and/or<br>audio and/or vibrating mechanism<br>upon receipt of the alert. | Critical Alert CommonPath<br>Enterprise does not alter the<br>behavior of the primary medical<br>devices and associated alarm<br>annunciations. The display device<br>provides a visual, and/or audible<br>and/or vibrating mechanism upon<br>receipt of the alert. | |
| | Connect for Clinical Systems is<br>intended for use as a secondary<br>alarm. It does not replace the<br>primary alarm function on the<br>monitor. | Critical Alert CommonPath<br>Enterprise is intended for use as a<br>secondary alarm. It does not replace<br>the alarm function on the primary<br>device. | |
| Serves as<br>secondary means<br>of annunciating<br>patient events | Yes | Same | |
| Uses computer<br>hardware to<br>gather and<br>format alarm<br>event information | Windows-based personal computer<br>(PC)<br>• Memory: 4 GB RAM<br>• Processor: 2 GHz<br>• Connection: TCP/IP base LAN<br>Disk Space: 50 GB minimum<br>(recommended free disk space for<br>installation) | Typical rack mount server from a<br>vendor such as Dell or HP.<br>• Memory - 16 GB RAM<br>• Hard Disk – 4 x 500 GB 15K<br>RPM - Raid 10<br>• Processor - 2 x 3.0 GHz Quad<br>Core (4 core minimum)<br>• NIC - Support for 10-100Mbit<br>(minimum) | |
| Technology<br>Comparison<br>(continued): | Characteristic<br>(continued) | Ascom Sweden AB<br>Unite Connect for Clinical Systems<br>(K180566) | Critical Alert<br>CommonPath Enterprise<br>(Proposed Device) |
| | Duty assignments | Scale is based on maximum number<br>of locations supported per<br>integration. Current maximum<br>number of locations: 128<br>Maximum number of concurrent<br>assignment clients: 30 | Tested for 141 number of locations<br>(units) supported. |
| | | | Maximum redirection levels: 3 |
| | | | Supports a fully configurable<br>location layout. |
| | | | Supports assignment clients with<br>shift planning and assignment of<br>display and/or alerting devices to<br>staff members. |
| | | | Supports assignment of staff to<br>patients with escalation chains. |
| | | | Unassigned location warning when a<br>location or a group of events are not<br>assigned. |
| | | | Maximum number combined<br>assignees: 6,000 |
| | | | Maximum number of combined<br>locations and events per location:<br>1,200 (e.g. 128 locations with ~9<br>assignable events per location) |
| | | Time sources | NTP server (NTPv4 compatible with<br>NTPv2 and NTPv3). Time can be<br>set manually from a Web browser. |
| | | Messaging<br>component<br>compatibility list | Unite Connectivity Manager<br>(v5.10.0 and higher)<br>Unite Communication Server (1.3.1<br>and higher)<br>TAP (v1.01) |
| | | ECG-SNPP (v1.03)<br>ECG-OAI (2.05)<br>ECG-Cisco (1.21) | |
| | | SMTP (2.24) | |
| Software | Critical Alert CommonPath Enterprise software was designed and<br>developed according to a robust software development process and was<br>rigorously verified and validated.<br>Software information is provided in accordance with internal<br>requirements and the following guidance documents and standards: | | |
| | FDA guidance: The content of premarket submissions for software contained in medical devices, 11 May 05. FDA guidance: Off-the-shelf software use in medical devices, 09 Sep 99. FDA guidance: General principles of software validation; Final guidance for industry and FDA staff, 11 Jan 02. Content of Premarket Submissions for Management of Cybersecurity in Medical Devices, 02 Oct 14. Cybersecurity for Networked Medical Devices Containing Off-The-Shelf (OTS) software, 14 Jan 05. Design Considerations and Premarket Submission Recommendations for Interoperable Medical Devices, 06 Sep 17. Infusion Pumps Total Product Life Cycle, 02 Dec 14. | | |
| | Test results indicate that Critical Alert CommonPath Enterprise complies with its predetermined specifications and the guidance documents. | | |
| Performance Testing<br>– Bench | Critical Alert CommonPath Enterprise was tested for performance in accordance with internal requirements and the following standard. | | |
| | IEC 60601-1-8: 2012, Medical electrical equipment – Part 1-8: General requirements for basic safety and essential performance – Collateral standard: General requirements, Tests and guidance for alarm systems in medical electrical equipment and medical electrical systems (Clause 6.11 only). IEC 62366-1: 2015, Medical devices – Application of usability engineering to medical devices. | | |
{6}------------------------------------------------
{7}------------------------------------------------
#### Summary of Performance Testing:
Test results indicated that Critical Alert CommonPath Enterprise complies with internal requirements and the applicable Standard.
{8}------------------------------------------------
Conclusion Verification and validation activities were conducted to establish the performance and safety characteristics of the device modifications made to Critical Alert CommonPath Enterprise. The results of these activities demonstrate that Critical Alert CommonPath Enterprise is as safe and as effective in comparison to the predicate device when used in accordance with its intended use and labeling.
> Therefore, Critical Alert CommonPath Enterprise is considered substantially equivalent to the predicate device.