K112650 · Connexall USA, Inc. · MSX · Feb 1, 2012 · Cardiovascular
Device Facts
Record ID
K112650
Device Name
CONNEXALL SUITE OF SOFTWARE PRODUCTS
Applicant
Connexall USA, Inc.
Product Code
MSX · Cardiovascular
Decision Date
Feb 1, 2012
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The intended use of the Connexall Suite of Software Products 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, the Connexall Suite of Software Products is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. The Connexall Suite of Software Products does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audio and/or vibrating mechanism upon receipt of the alert. The Connexall Suite of Software Products is intended for use as a secondary alarm. It does not replace the primary alarm function on the monitor.
Device Story
Connexall Suite of Software Products is an on-site messaging integration solution; functions as a secondary, redundant alarm forwarding system. Inputs: patient monitor status and alarm data from clinical systems. Processing: Notification Server manages near-real-time event processing, dispatching, and database management. Outputs: text, alarms, or data forwarded to third-party mobile display devices. Usage: clinical environment; operated by healthcare professionals. Benefit: enables awareness of patient status and alarm conditions when away from the primary monitoring system. Does not alter primary device behavior or replace primary alarm functions.
Clinical Evidence
Bench testing only. Verification and validation activities were conducted to establish performance and safety characteristics. Results demonstrated compliance with predetermined specifications.
Technological Characteristics
Client/server application; runs on Microsoft Windows 32-bit operating systems. Core component is the Notification Server (database, system administration, licensing, event processing). Connectivity: interfaces with clinical systems to forward data to third-party mobile devices. Configurations: Enterprise, Pro, Care, and LITE.
Indications for Use
Indicated for healthcare professionals to receive secondary, redundant, near real-time notifications of medical events and alarms from primary patient monitoring systems via third-party mobile display devices.
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.
{0}------------------------------------------------
K112650 P1/3
## FEB - 1 2012
## 510(k) Summary
| Submission Date: | 09 September 2011 | | |
|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------------------------------------------------------------|
| Submitter: | Connexall USA, Inc.<br>5540 Central Avenue, Suite 220<br>Boulder, CO 80301 | | |
| Submitter Contact: | Mr. John Elms<br>Connexall USA, Inc.<br>5540 Central Avenue, Suite 220<br>Boulder, CO 80301<br>+1 (720) 279-8707<br>jelms@connexall.com) | | |
| Official Contact: | Mr. Thomas Kroenke<br>Speed To Market, Inc.<br>PO Box 3018<br>Nederland, CO 80466<br>+1 (303) 956-4232<br>tkroenke@speedtomarket.net | | |
| Manufacturing Site: | Globestar Systems Inc.<br>7 Kodiak Crescent, Suite 100<br>Toronto, Ontario, Canada M3J 3E5 | | |
| Trade Name: | Connexall Suite of Software Products | | |
| Common Name: | Network and Communication Middleware | | |
| Classification Name: | System, Network And Communication, Physiological Monitors | | |
| Classification<br>Regulation: | 21 CFR §870.2300 | | |
| Product Code: | MSX | | |
| Substantially<br>Equivalent Devices: | Connexall Model | Predicate 510(k)<br>Number | Predicate Manufacturer<br>and Model |
| | Connexall Suite of<br>Software Products | K102974 | Philips Medical Systems<br>Philips Emergin Event<br>Management System |
Page 1 of 3
:
ィ
,
{1}------------------------------------------------
Image /page/1/Picture/0 description: The image shows handwritten text that appears to be a combination of alphanumeric characters. The text is "K112650 P2/3". The characters are written in black ink on a white background and appear to be part of a label or code.
Device Description: The Connexall USA. Inc. (Connexall) Suite of Software Products (Software) is an on-site messaging integration solution which forwards patient monitor status and alarm information to the user via display devices provided by third-party mobile device companies. Users receive interactive, time-critical information from patient monitoring devices directly via their display devices as text, alarms or data. Connexall Software allows users to be aware of their patients' status and alarm conditions when they are away from the patient and patient monitoring system.
> Connexall Software is a client/server application designed to run under any Microsoft Windows 32-bit operating system. At the core of the application is the Notification Server. The Notification Server includes the database application, system administration, licensing, and the resources to manage the near-real-time event processing and dispatching.
The Connexall Suite of Software Products is offered in four (4) configurations. These configurations include:
- Connexall Enterprise; -.
- . Connexall Pro:
- Connexall Care; and .
- Connexall LITE. .
Intended Use:
The intended use of the Connexall Suite of Software Products 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, the Connexall Suite of Software Products is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. The Connexall Suite of Software Products does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audio and/or vibrating mechanism upon receipt of the alert.
The Connexall Suite of Software Products is intended for use as a secondary alarm. It does not replace the primary alarm function on the monitor.
Technology Comparison: The Connexall Suite of Software Products employs the same or similar technological characteristics as the predicate device.
{2}------------------------------------------------
Image /page/2/Picture/0 description: The image shows a handwritten text string. The string appears to be an alphanumeric code or identifier. The text reads 'KI12650 P3/3' and is written in black ink on a white background.
## Performance Testing:
| Software Testing | The Connexall Suite of Software Products was designed and developed<br>according to a robust software development process, and was rigorously<br>verified and validated. |
|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Test results indicated that the Connexall Suite of Software Products<br>complies with its predetermined specifications. |
| Conclusion | Verification and validation activities were conducted to establish the<br>performance and safety characteristics of the Connexall Suite of<br>Software Products. The results of these activities demonstrate that the<br>Connexall Suite of Software Products is safe and effective when used in<br>accordance with its intended use and labeling. |
| | Therefore, the Connexall Suite of Software Products is considered<br>substantially equivalent to the predicate device. |
.
{3}------------------------------------------------
Food and Drug Administration 10903 New Hampshire Avenue Document Control Room -WO66-G609 Silver Spring, MD 20993-0002
FEB - 1 2012
Connexall USA, Inc. c/o Mr. Thomas Kroenke Speed To Market, Inc. P.O. Box 3018 Nederland, CO 80466
Re: K112650
Trade/Device Name: Connexall Suite of Software Products Regulation Number: 21 CFR 876.2300 Regulation Name: Cardiac Monitor (including cardiotachometer and rate alarm) Regulatory Class: Class II (two) Product Codes: MSX Dated: January 30, 2012 Received: January 30, 2012
Dear Mr. Kroenke:
We have reviewed your Section 510(k) premarket notification of intent to market the device we nave reviewed your becamed the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate for use stated in the encreated of the enactment date of the Medical Device Amendments, or to eonimered processified 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. The r ou may, merers, mans of the Act include requirements for annual registration, listing of general controls provisions gractice, labeling, and prohibitions against misbranding and adulteration.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it your device is elaborned (600 a00 as) as a stime 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.
{4}------------------------------------------------
Page 2 – Mr. Thomas Kroenke
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 requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHOffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default.htm.
Sincerely yours,
Bram D. Zuckerman, M.D.
Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
Indications for Use
| 510(k) Number (if known): | K |
|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Device Name: | Connexall Suite of Software Products |
| Indications for Use: | The intended use of the Connexall Suite of Software Products 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, the Connexall Suite of Software Products is intended to serve as a parallel, redundant, forwarding mechanism to inform healthcare professionals of particular medical related events. The Connexall Suite of Software Products does not alter the behavior of the primary medical devices and associated alarm annunciations. The display device provides a visual, and/or audio and/or vibrating mechanism upon receipt of the alert. |
| | The Connexall Suite of Software Products is intended for use as a secondary alarm. It does not replace the primary alarm function on the monitor. |
| Prescription Use<br>(Part 21 CFR 801 Subpart D) | X |
|-------------------------------------------------|---|
|-------------------------------------------------|---|
AND/OR
| Over-The-Counter Use<br>(21 CFR 807 Subpart C) | |
|------------------------------------------------|--|
|------------------------------------------------|--|
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF
NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
| (Division Sign-Off) |
|------------------------------------|
| Division of Cardiovascular Devices |
| 510(k) Number | K112650 |
|---------------|---------|
|---------------|---------|
・・
Page 1 of 1
:
.
·
:
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.