K212473 · Welch Allyn, Inc. · MWI · Oct 28, 2022 · Cardiovascular
Device Facts
Record ID
K212473
Device Name
Welch Allyn Connex Central Station
Applicant
Welch Allyn, Inc.
Product Code
MWI · Cardiovascular
Decision Date
Oct 28, 2022
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
The Connex Central Station is intended to be used by clinicians for the central monitoring of neonatal, pediatric and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
Device Story
Connex Central Station (v.1.8.5) is a Windows-based software application for remote, simultaneous monitoring of multiple patients in healthcare facilities. It receives physiological data, including ECG parameters, from connected bedside monitors (e.g., Welch Allyn Connex Vital Signs Monitor). The device displays real-time patient data and alarms to clinicians, facilitating patient surveillance. It includes optional modules for extended data recording and full disclosure. By centralizing patient information, the device assists clinicians in monitoring patient status and responding to alarms, potentially improving patient safety through timely clinical intervention. It is operated by clinicians in a clinical environment.
Clinical Evidence
No clinical studies were utilized. Evidence is based on bench testing, including software verification and validation, and adherence to recognized standards (IEC 62366-1, IEC 60601-1-8, IEC 62304, IEC 60601-2-27, ISO 14971, AAMI 80001-1, ISO 15223-1).
Technological Characteristics
Windows-based software; displays physiological parameters (including ECG) received from bedside monitors. Software life cycle per IEC 62304; risk management per ISO 14971; usability per IEC 62366-1. Major level of concern for software. Connectivity via IT networks (AAMI 80001-1).
Indications for Use
Indicated for central monitoring of neonatal, pediatric, and adult patients in healthcare facilities.
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
Welch Allyn® Connex® Central Station (v. 1.5) (K132807)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains 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 features the letters "FDA" in a blue square, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue text.
October 28, 2022
Welch Allyn, Inc. Megan Pellenz Regulatory Affairs Manager 4341 State Street Road Skaneateles Falls, New York 13153
Re: K212473
Trade/Device Name: Welch Allyn Connex Central Station (v.1.8.5) Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MWI, MHX Dated: August 5, 2021 Received: August 6, 2021
Dear Megan Pellenz:
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,
LCDR Stephen Browning Assistant Director 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
Form Approved: OMB No. 0910-0120 Expiration Date: 06/30/2023 See PRA Statement below.
Submission Number (if known)
K212473
Device Name
Welch Allyn® Connex® Central Station ( v.1.8.5)
#### Indications for Use (Describe)
The Connex Central Station is intended to be used by clinicians for the central monitoring of neonatal, pediatric and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
Type of Use (Select one or both, as applicable)
> Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# 510(k) Summary- K212473
## Contact Details
21 CFR 807.92(a)(1)
| Applicant Name | Welch Allyn, Inc. |
|-----------------------------|-----------------------------------------------------------------|
| Applicant Address | 4341 State Street Road Skaneateles Falls NY 13153 United States |
| Applicant Contact Telephone | 315-569-4257 |
| Applicant Contact | Mrs. Megan Pellenz |
| Applicant Contact Email | megan.pellenz@hillrom.com |
Device Name 21 CFR 807.92(a)(2)
| Device Trade Name | Welch Allyn® Connex® Central Station ( v. 1.8 .5) |
|---------------------|--------------------------------------------------------------------------|
| Common Name | Patient Monitoring Central Station |
| Classification Name | Monitor, Physiological, Patient (Without Arrhythmia Detection Or Alarms) |
| Regulation Number | 870.2300 |
| Product Code | MWI |
Legally Marketed Predicate Devices 21 CFR 807.92(a)(3)
| Predicate # | Predicate Trade Name (Primary Predicate is listed first) | Product Code |
|-------------|----------------------------------------------------------|--------------|
| K132807 | Welch Allyn® Connex® Central Station (v. 1.5) | MWI |
| K171621 | Welch Allyn® Connex® Vital Signs Monitor/CIWS | MHX |
Device Description Summary 21 CFR 807.92(a)(4)
Both the Welch Allyn primary predicate and subject Connex Central Station devices are software devices for a Windows-based operating system that provide clinicians with a means to remotely monitor the health of several patients simultaneously.
Intended Use/Indications for Use 21 CFR 807.92(a)(5)
The Connex Central Station is intended to be used by clinicians for the central monitoring of neonatal, pediatric and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
Indications for Use Comparison 21 CFR 807.92(a)(5)
The subject device Connex Central Station and the primary predicate Connex Central Station (K132807) have the same Indications for Use: The Connex Central Station is intended to be used by clinicians for the central monitoring of neonatal, pediatric, and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
Technological Comparison 21 CFR 807.92(a)(6)
{4}------------------------------------------------
The subject device Connex Central Station and the primary predicate device Connex Central Station (K132807) have the same fundamental technology characteristics. A feat the subject Connex Central Station device displays EG physiological parameters received from the Connex Vital Signs Monitor (K171621) while the primary predicate device does not. The addition of the new feature (i.e., ECG parameters) on the subject device does not alter the subject device compared to the primary predicate nor does it raise new questions of safety and effectiveness. Specifically, the methods used to add ECG parameters to the central monitoring display of the subject device are the same methods used to display the already cleared paramaty predicate Connex Central Station device. Additionally, the methods used to collect ECG parameters on the CVSM have been cleared under K171621. Thus, to support the addition of the ECG parameters and associated FDA product code MHX to the subject device, the Connex Vital Signs Monitor (K171621), is being used as a secondary predicate device in this submission.
#### Non-Clinical and/or Clinical Tests Summary & Conclusions 21 CFR 807.92(b)
The Connex Central Station was tested to evaluate its performance based on the following standards: IEC 62366-1:2015 Medical Devices - Part 1: Application of usability engineering to medical devices
IEC 60601-1- 8:2012 Medical electrical equipments for basic safety and essential performance – Collateral Standard: General requirements, tests and systems in medical electrical equipment and medical electrical systems
IEC 62304:2015 Medical Device Software - Software Life Cycle Processes
IEC 60601-2-27:2011 Medical electrical equipments for the Safety, Including Essential Performance of Electrocardiographic Monitoring Equipment
ISO 14971:2019 Application of Risk Management to Medical Devices
AAMI 80001-1:2010 Application of risk management for IT networks incorporating medical devices
ISO 15223-1:2016 Symbols to be used with medical device labelling and information to be supplied – Part 1: General requirements.
Software Verification and Validation testing were conducted, and documentation provided within this submission as recommended by FDA's Guidance for Industry and FDA Staff "Guidance for the Content of Premarket Submissions for Software in Medical Devices". Connex Central Station software was considered as a "Major" level of concern since a failure of latent flaw in the software could directly result in serious injury or death to the patient or operator. This level of concern was not changed by the ECG data feature in version 1.8.5 of the software.
Not Applicable. No clinical studies were utilized for the purpose of obtaining safety and effectiveness data.
Well-established, scientific methods are were used to evaluate the new ECG parameter features of the subject device. The methods used to add ECG parameters to the central monitoring display of the same methods used to display the already cleared parameters on the primary predicate Connex Central Station device.
The methods used to collect ECG parameters on the Welch Allyn CVSM device have been cleared under K171621. Thus, to support the addition of the ECG parameters and associated FDA product code MHX to the Connex Vital Signs Monitor (K17621), is being used as a secondary predicate device in this submission.
The performance of the subject Connex Central Station device was evaluated to the same methods utilized for the primary predicate and/or the secondary predicate. The evaluation methods include IEC 62366-1:2015, IEC 62304:2015, ISO 14971:2019, AAMI 8001-1:2010 Section 3.5, ISO 15223-1:2016 and IEC 60601-2-27:2011 Section 201.12.1.101.6 and FDA Special Controls Guidance Arrhythmia Detector and Alarm - Class II Special Controls Guidance Document for Industry and FDA Staff (October 28, 2003). The software met the design requirements and performance, functionality characteristics. The differences in the technological characteristics with the addition of the EG parameter into the Connex Central Station do not impact the safety and effectiveness of the subject device. Therefore, it can be concluded the evidence presented in this submission confirms that the Connex Central Station v1.8.5 is substantially equivalent to the primary predicate Connex Central Station v1.5 cleared in K132807.
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.