K260211 · Hill-Rom, Inc. · MSX · Aug 13, 2026 · Cardiovascular
Device Facts
Record ID
K260211
Device Name
Dashboard (P007000)
Applicant
Hill-Rom, Inc.
Product Code
MSX · Cardiovascular
Decision Date
Aug 13, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The Dashboard is a software product indicated for use as a secondary, visual communication tool for clinical caregivers within a healthcare environment. Dashboard displays EMR data, patient location, and alarm information received from Baxter devices. The information is presented on a monitor to allow patient status and device status to be readily viewable by clinical caregivers. The Dashboard does not replace the primary monitoring, alarm, or clinical assessment functions of the connected source devices.
Device Story
Dashboard 2.0 is a software-based secondary visual communication tool for clinical caregivers in healthcare facilities. It aggregates and displays data from hospital systems (ADT, EMR) and connected Baxter medical devices (beds, stretchers, heart/respiratory rate monitors). Inputs include patient demographics, physiological data (HR, RR), risk data (fall, skin), and device status (rail position, brake, bed exit). The device functions as a read-only display, presenting this information on a monitor at nursing stations to provide an overview of patient and device status. It does not perform data processing, generate primary alarms, or control therapy; it acts as a conduit for information already generated by source devices. By consolidating data, it assists caregivers in monitoring patient status remotely. It does not replace primary monitoring or clinical assessment functions.
Clinical Evidence
No clinical data. Substantial equivalence established via software verification, bench performance testing, and design validation in a simulated-use environment with healthcare professionals.
Technological Characteristics
Software-based communication tool; read-only display. Operates on server-client architecture. Connectivity via network integration with ADT, EMR, and Baxter medical devices. Complies with IEC 62304 (software lifecycle), IEC 62366-1 (usability), and IEC 82304-1 (health software safety). Cybersecurity controls implemented per FDA guidance.
Indications for Use
Indicated for clinical caregivers in healthcare environments (intensive, acute, long-term care) to view secondary patient data, location, and alarm information from connected Baxter devices. Not for primary monitoring, alarm, or clinical assessment.
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}
**FDA** U.S. FOOD & DRUG
ADMINISTRATION
August 13, 2026
Hill-Rom, Inc.
Senthil Kumar
Sr. Manager, Regulatory Affairs
1069 State Route 46 E.
Batesville, Indiana 47006
Re: K260211
Trade/Device Name: Dashboard (P007000)
Regulation Number: 21 CFR 870.2300
Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm)
Regulatory Class: Class II
Product Code: MSX, BZQ, FNL
Dated: August 12, 2026
Received: August 12, 2026
Dear Senthil Kumar:
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 (the 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 available 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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K260211 - Senthil Kumar
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
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 Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 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-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/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-devices/device-advice-comprehensive-regulatory-
{2}
K260211 - Senthil Kumar
Page 3
assistance/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 W. SHIH -S
Jennifer Kozen
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
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K260211 | ? |
| Please provide the device trade name(s). | | ? |
| Dashboard (P007000) | | |
| Please provide your Indications for Use below. | | ? |
| The Dashboard is a software product indicated for use as a secondary, visual communication tool for clinical caregivers within a healthcare environment. Dashboard displays EMR data, patient location, and alarm information received from Baxter devices. The information is presented on a monitor to allow patient status and device status to be readily viewable by clinical caregivers. The Dashboard does not replace the primary monitoring, alarm, or clinical assessment functions of the connected source devices. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
{4}
Dashboard 2.0.100
K260211
Page 1 of 15
# K260211 510(k) Summary
# I. SUBMITTER
Hill-Rom, Inc.
1069 State Route 46
East Batesville, Indiana 47006
Kimberly Colasanti
Assoc Dir, Regulatory Affairs
kimberly_colasanti@baxter.com
Date of Summary: 23 Jan 2026
# II. SUBJECT DEVICE
Device Trade or Proprietary Name: Dashboard
Common or Usual Name: System, Network and Communication, Physiological Monitor
Regulation Number: 21CFR 870.2300
Classification Name: Cardiovascular
Primary Product Code: MSX
Associated Product code: BZQ & FNL
Class: Class II
Review Panel: Office of Cardiovascular Devices (OHT2), Cardiac Electrophysiology, Diagnostics, and Monitoring Devices (DHT2A)
# III. PREDICATE DEVICE INFORMATION
# Primary Predicate:
Device Trade Name: Central Station
510(k) Number: K242750
# Reference Predicate:
Device Trade Name: Hillrom Heart and Respiration Rate Monitoring System powered by EarlySense
{5}
Dashboard 2.0.100
K260211
Page 2 of 15
510(k) Number: K223246
Device Trade Name: iBed Wireless with iBed Mobile
510(k) Number: K202964
### IV. DEVICE DESCRIPTION
The Dashboard 2.0 is a software product indicated for use as a secondary communication measure by clinical caregivers within a healthcare environment.
(1) It is a visual communication tool to display an overview of patient data i.e., EMR data, Baxter device data and rooms/locations at nursing unit stations.
(2) This patient information is displayed on a monitor allowing patient status to be easily viewable by clinical caregivers. The Dashboard 2.0 application is not intended to prevent, diagnose, or treat illness, injury, or disease.
(3) It is used as a read-only display.
(4) The data displayed on the Dashboard 2.0 may include, but is not limited to,
- Location data (e.g. Unit, room number)
- Patient demographic, physiological, and risk data (e.g. Name, Respiratory Rate, Heart Rate, risk such as skin, pulmonary, and fall)
- Device data (e.g. rail position, brake status, bed exit, patient identification)
(5) In Dashboard 2.0 the data displayed may originate from devices and/or systems interfacing with server. The following originating source devices/systems are some examples and the information will be displays in Dashboard based on the applicability
- ADT (Admit, Discharge & Transfer of patients' data)
- EMR (Electronic Medical Record) (e.g. Epic HL7)
- Heart and Respiratory Rate monitoring System (Integrated with Centrella bed)
- Centrella bed (with or without integrated Hillrom Heart and Respiration Rate Monitoring System)
- Progressa, Progressa+ (wireless)
- Accella bed (wireless)
- Dynamo Series (Stretcher)
### V. INDICATIONS FOR USE STATEMENT
The Dashboard is a software product indicated for use as a secondary, visual communication tool for clinical caregivers within a healthcare environment. Dashboard displays EMR data, patient location, and alarm information received from Baxter devices. The information is presented on a monitor to allow patient status and device status to be readily viewable by clinical caregivers. The Dashboard does not replace the primary monitoring, alarm, or clinical assessment functions of the connected source devices..
{6}
Dashboard 2.0.100
K260211
Page 3 of 15
## VI. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE PREDICATE DEVICE
Design verification and validation testing were performed on the Dashboard and included software verification, bench performance, and design validation. Bench performance testing was conducted to ensure the Dashboard 2.0.100 performed together according to specification. Design validation testing was conducted in a simulated-use environment by health care professionals. Users were successfully able to set and view bed status parameters from remote locations within the healthcare delivery organization as intended.
**Table 1** below illustrates the comparison between the proposed device and the predicate devices.
Note: In the **Table 1**, the “Proposed Device” is defined as the Dashboard 2.0.100 device and the “Predicate Device” is defined as the Central Station (K242750) and the reference predicate devices like Hillrom Heart and Respiration Rate Monitoring System (K223246) and iBed™ Wireless with iBed™ Mobile (K202964)
{7}
Dashboard 2.0.100
K260211
Page 4 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| Device Trade or Proprietary Name | Dashboard | Central Station | Equivalent to primary predicate |
| Regulation Number | 21CFR 870.2300- Cardiac monitor (including cardiotachometer and rate alarm) | 21CFR 870.2300- Cardiac monitor (including cardiotachometer and rate alarm) | Equivalent to primary predicate |
| Product Code | **Primary Product Codes:** MSX - System, network and communication, physiological monitors **Associated Product Codes:** BZQ - Breathing Frequency Monitor FNL - AC-powered adjustable hospital bed. | **Primary Product Codes:** MSX - System, network and communication, physiological monitors **Secondary Product Codes:** MHX- Monitor, physiological, patient (with arrhythmia detection or alarms) DRQ- Amplifier and signal conditioner, transducer signal MWI Monitor, Physiological, Patient (Without Arrhythmia Detection Or Alarms) | Equivalent to primary predicate claimed network and communication function |
| Class | Class II | Class II | Same |
| Intended Use | The Dashboard is a software product intended for use as a secondary, visual communication tool for clinical caregivers within a healthcare environment. Dashboard displays EMR data, patient location, and alarm information received from Baxter devices. The information is presented on a monitor to allow patient status and device status to be readily viewable by clinical caregivers. The | Central Station is a network device, intended to display, record and print monitored physiological data from Nihon Kohden bedside monitors, telemetry receiver and/or transmitters. Central Station does not perform any data processing on the data received from the Nihon Kohden compatible devices. When Central Station is connected with the Nihon Kohden bedside monitors and telemetry | Equivalent to Primary Predicate The intended use and indications for use of the proposed device and the primary predicate and reference are the same in that they both receive patient related data from their compatible devices |
{8}
Dashboard 2.0.100
K260211
Page 5 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| | Dashboard does not replace the primary monitoring, alarm, or clinical assessment functions of the connected source devices. | receivers/transmitters the Central Station can: • Admit and discharge patients on the Nihon Kohden network. • Display and manage compatible devices' real-time patient clinical data, vital signs, alarms and waveforms. • Review and trend data calculated by connected Nihon Kohden devices. • Store and transfer historical clinical data for the connected systems. • Print patient data. Central Station is intended for use in professional medical facilities by trained medical personnel | (beds, bedside monitors) and display that data in a consolidated screen to view each individual patient status. |
| Indications for Use | The Dashboard is a software product indicated for use as a secondary, visual communication tool for clinical caregivers within a healthcare environment. Dashboard displays EMR data, patient location, and alarm information received from Baxter devices. The information is presented on a monitor to allow patient status and device status to be readily viewable by clinical caregivers. The Dashboard does not replace the primary monitoring, alarm, or clinical assessment functions of the connected source devices. | Same as Intended Use | Equivalent to primary predicate The Dashboard provides secondary display of demographic, physiologic, and risk data from compatible devices and systems. Alarm generation, alarm limits, and alarm decisions remain solely on the originating devices. The Dashboard does not control therapy, |
{9}
Dashboard 2.0.100
K260211
Page 6 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| | | | does not modify source data |
| Primary Function | One-way data communication for viewing compatible devices status parameters | One-way data communication for viewing data from the compatible devices | Equivalent to primary predicate |
| Intended Patient Population | Patients confirmed in the hospital and medical facility environments | Patients connected to Nihon Kohden bedside monitors, telemetry receivers, and transmitters | Equivalent to primary predicate |
| Intended Users | Caregivers/ Healthcare Professionals | Healthcare Professionals | Equivalent to primary predicate |
| Operational Environment | Intensive/Critical care Acute care Long-term care | Professional medical facilities | Equivalent to primary predicate |
| Primary Device Function | One-way data communication for viewing compatible devices status parameters | One -Way network device, intended to display, record and print monitored physiological data from Nihon Kohden bedside monitors, telemetry receiver and/or transmitters. | Equivalent to primary predicate But the proposed device intended to only display the patient data |
| Data Input | The data displayed on the dashboard originates from devices and/or systems interfacing with server. The following originating source devices/systems are some examples • EarlySense (Integrated with bed) | Configure the compatible devices with the Central Station. • NK Bedside Monitors (MHX): BSM: 1700, 3000, 6000, G9, G5, G7 • Vital Signs Monitor (MWI): SVM-7200 | Equivalent to primary predicate |
{10}
Dashboard 2.0.100
K260211
Page 7 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| | - Centrella bed (with or without integrated contact-free continuous monitoring devices) - Progressa/+ (wireless) - Accella bed (wireless) | - NK Telemetry (MHX/DRG): GZ-120/130/140 - Multiple Patient Receiver and Transmitters (DRG): ORG-9700/9100 (DRT): ZS-940, ZM-520/521/530/531 - Central Monitor (MHX): CNS6201/6801/2101 | |
| Third -party Systems | The following originating source systems - ADT (Admit, Discharge & Transfer of patients' data) - EMR (e.g. Epic HL7) | Following functions are supported - Admit, Discharge, Pause, and Transfer functions - Patient transfer within one central station - Patient transfer between central stations - Entering patient information (Manual, Auto) | Equivalent to primary predicate. |
| Detailed View of Location/Status | Care Unit Details - Nursing unit name/location - Configuration name | - Hospital Name, - Bed name, - Patient name | Equivalent to primary predicate |
{11}
Dashboard 2.0.100
K260211
Page 8 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| Detailed Views of patient data | Patient Status Parameters - Patient name - Patient risks - HR (Heart Rate) - RR (Respiratory rate) | Display and manage compatible devices' real-time patient clinical data, vital signs, alarms and waveforms. - Multiple Waveform, Expanded Waveform, - Trend, Tabular Trend, - Full Disclosure, - Arrhythmia Recall, - ST Recall, Event List, - Alarm Event, - ECG 12 Lead Analysis, - Hemodynamics List | Equivalent to primary predicate The patient data displayed on the subject device "Dashboard" is of less criticality compared to that displayed by the predicate device |
| Detailed Views of device data | Bed Parameters - Bed position status - Bed/stretcher rail status - Bed exit status - Bed low status - Bed brake status - Head of bed angle status - Therapy mode status: Type, time, reminders - Battery status: For stretchers (only) - Bed service required icon - CFCM on/off | - Trend window - Tabular Trend window - Full Disclosure window - Expanded Waveform window - Arrhythmia Recall window - ST Recall window - Event List window - Alarm Events window - ECG 12 Lead Analysis window - Hemodynamics List window - SpO2 Trend window | Equivalent to primary Predicate Data from the source devices is displayed on the Dashboard in a manner equivalent to that of the predicate device |
{12}
Dashboard 2.0.100
K260211
Page 9 of 15
| Features | Proposed Device: Dashboard 2.0.100 | Primary Predicate: Central Station (K242750) | Assessment of Difference |
| --- | --- | --- | --- |
| User Operation | - The healthcare professional initially sets bed/patient parameter settings at Dashboard setting screen. - Data is automatically received from the Server and display on the Dashboard screen. | - Central Station displays waveforms data and numerical data from a connected bedside monitor, vital sign telemeter, or multiple patient receiver unit on the screen - The parameters that display a list of measured values and a trend graph from the compatible device. | Equivalent to primary predicate |
# Functional Parameters comparison with Reference Predicate.
| Features | Proposed Device: Dashboard 2.0.100 | Reference Predicate: Hillrom Heart and Respiration Rate Monitoring System (K223246) | Reference Predicate: iBed™ Wireless with iBed™ Mobile (K202964) | Assessment of Difference |
| --- | --- | --- | --- | --- |
| Wireless Communications – Data Transmission | Uni- Direction data transmission: From Baxter Device to server to Dashboard 2.0.000. | Uni- Direction data transmission From Device to Display in bed flip-up monitor | Bi-directional data transmission: Bed to server to iBed™ Mobile to healthcare professional and then back to iBed™ Mobile then back to server then back to bed. | Equivalent with Hillrom Heart and Respiration rate system Partially Similar to iBed Wireless with iBed Mobile |
{13}
Dashboard 2.0.100
K260211
Page 10 of 15
| | | | | Dashboard is not intended to change the parameters in Bed |
| --- | --- | --- | --- | --- |
| Database | Healthcare delivery organization's central Information SystemBaxter Software server (Device Bridge) | There is no database involved | Healthcare delivery organization's central Information SystemSoftware server. | Equivalent to iBed Wireless with iBed Mobile |
| Data Input | The data displayed on the dashboard originates from devices and/or systems interfacing with Device Bridge. The following originating source devices/systems are some examplesHillrom Heart and Respiration Rate Monitoring System (Integrated with bed)Centrella bed (with or without integrated contact-free continuous monitoring devices)Progressa/+ (wireless) | Analyzes and interprets information from sensor and user input and Acts as a conduit to send data (respiratory rate and heart rate) to/from bed system display | Configure bed for wireless connection to the central healthcare Delivery Organization's Information System network server.Install iBedTM Mobile application from relevant mobile application stores (i.e. Apple).Configure iBedTM Mobile for use | Equivalent to Reference Predicate |
{14}
Dashboard 2.0.100
K260211
Page 11 of 15
| | - Accella bed (wireless) | | | |
| --- | --- | --- | --- | --- |
| Primary Device Function | One-way data communication for viewing compatible devices status parameters | one-way communication system intended to measure and display the patient’s respiratory rate and heart rate | Bi-directional data transmission of specific bed parameters between HDO’s central Information System software system | Equivalent with Hillrom Heart and Respiration rate system Partially Similar to iBed Wireless with iBed Mobile Dashboard is not intended for Bi-directional data transmission |
| Detailed View of information | 2. Care Unit Details - Nursing unit name/location - Configuration name Patient Status Parameters - Patient name - Patient risks - HR (Heart Rate) - RR (Respiratory rate) | Patient Status Parameters - HR (Heart Rate) - RR (Respiratory rate) | Care unit viewing of: - Room location - Bed serial number Patient Status Parameters - Display Patient fall risk - Displays rounding - Displays skin Monitoring of: | Equivalent to Reference Predicate The proposed device Dashboard displays the HR and RR information from the reference Predicate” Hillrom Heart and Respiration Rate Monitoring System” |
{15}
Dashboard 2.0.100
K260211
Page 12 of 15
| | Bed Parameters • Bed position status • Bed/stretcher rail status • Bed exit status • Bed low status • Bed brake status • Head of bed angle status • Therapy mode status: Type, time, reminders • Battery status: For stretchers (only) • Bed service required icon • CFCM on/off | | • HOB angle >30 • Bed height • Nurse call connected • Brake (locked/unlocked) • Siderail position • Bed exit zone and sensitivity • Bedside and remote locking of bed motion • Bedside and remote monitoring of bed exit sensitivity • Displays assessment and score of patients fall and rotation risk | |
| --- | --- | --- | --- | --- |
| Operational Environment | Intensive/Critical care Acute care Long-term care | Professional healthcare facilities | Healthcare delivery organization | Equivalent to Reference Predicate |
{16}
Dashboard 2.0.100
K260211
Page 13 of 15
| Alert Indications | Visual Alert | Visible and Audible alert | Visual Alert | Equivalent to Reference Predicate Dashboard is not intended for Audible Alert. |
| --- | --- | --- | --- | --- |
| Intended Users | Caregivers/ Healthcare Professionals | Healthcare Professionals | Healthcare Professionals | Equivalent to Reference Predicate |
{17}
Dashboard 2.0.100
K260211
Page 14 of 15
### SUBSTANTIAL EQUIVALENCE DISCUSSION ON COMPARISON TO PREDICATE DEVICE:
Dashboard, when compared to the above predicate devices, performs similar functions with no difference in how the devices are used. The Dashboard 2.0.100 is a single medical device that performs the functions of (a) Communication and (b) displaying data from patient bed, Hillrom Heart and Respiration Rate Monitoring System (CFCM- Contact Free Continuous Monitoring), ADT & EMR.
The Dashboard 2.0.100 has the same technology characteristics in terms of transferring the data from source devices (Beds & CFCM) and the other third-party servers like ADT and EMR to Dashboard 2.0.100.
The source of energy and the features of patient and device data that is how it displayed are equivalent to predicate device.
There are minor differences in the user interface design of the proposed device, Dashboard 2.0.100, compared to the predicate devices. These modifications do not affect the device's intended use or compromise patient safety
### Substantial Equivalence Discussion:
There are two differences between Predicate devices and proposed device Dashboard 2.0.100:
1. Dashboard 2.0.100 has a unique User Interface design compared to the Predicate device. That helps to show the Bed and CFCM related icons and it's easy to understand by the caregivers/Healthcare professionals.
2. Dashboard 2.0.100 is only used as a network and communication device, and it only acts as a secondary commenting (read only display) device. The information displayed in the Dashboard is from the source of patient/device data and the visual alarm is also from the source device.
These differences have no effect on substantial equivalence or the intended use of the device.
### VII. NON-CLINICAL PERFORMANCE DATA
Design verification and validation testing were performed on the Dashboard device because of risk analysis and product requirements. Testing requirements included software verification, bench performance, and design validation. Software verification testing was conducted to ensure the display capability and performed according to specification. Bench performance testing was conducted to ensure the Baxter Healthcare bed software and server performed together according to specification.
{18}
Dashboard 2.0.100
K260211
Page 15 of 15
Biocompatibility testing and non-clinical animal testing were not required, since Dashboard does not have direct and indirect human contact so, to demonstrate substantial equivalence to the predicate device.
The following guidance and standards were used for performance testing:
- ISO 14971Third Edition 2019-12 Medical devices - Application of risk management to medical devices (FDA consensus standard 5-125)
- IEC 62304 Edition 1.1 2015-06 CONSOLIDATED VERSION (FDA consensus standard 13-79)
- IEC 62366-1 Edition 1.1 2020-06 CONSOLIDATED VERSION (FDA consensus standard 5-129)
- IEC 82304-1 Edition 1.0 2016-10 Health software – Part 1: General requirements for product safety (FDA consensus standard 13-97)
- Content of Premarket Submissions for Device Software Functions, June 2023.
- Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, June 2025.
- Applying Human Factors and Usability Engineering to Medical Devices February 2016
- Postmarket Management of Cybersecurity in Medical Devices, January 2016.
### VIII. CLINICAL PERFORMANCE TESTING
Clinical studies are not required because the device demonstrates substantial equivalence to a legally marketed predicate device. All differences have been addressed through risk analysis and verified via software verification, bench performance, and design validation. The intended use and fundamental technology remain unchanged. Therefore, clinical data is unnecessary to establish substantial equivalence.
### IX. SUBSTANTIAL EQUIVALENCE DECISION
Based on the decision-making process outlined above and the information provided in this premarket notification, Baxter Healthcare Corporation believes the proposed Dashboard 2.0.100 is substantially equivalent, for purposes of section 510(k) of the Federal Food, Drug and Cosmetic Act only, to the predicate device(s) identified in this premarket notification.
The proposed user interface design compared to predicate devices does not have impact on the intended use or the fundamental scientific technology of the device. Per the substantial equivalence flowchart, the modified device is substantially equivalent to the currently marketed product.
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.