The IntelliVue XDS Software is intended for use as an additional, independent display for viewing screens, generated by specified network-connected Philips patient monitors. The IntelliVue XDS Software alone is not intended for remotely monitoring patients without caregivers in vicinity (unattended patients). It is indicated for local and remote operation of these Philips patient monitors. It is indicated for printing reports as generated by these Philips patient monitors. It is indicated to be used by trained healthcare professionals. Rx Only: Caution, U.S. Federal Law restricts this device to sale by or on the order of a physician.
Device Story
Bedside information system; software-only product installed on off-the-shelf IT hardware. Inputs: network-transmitted data from connected Philips patient/fetal monitors. Function: provides remote display, input device sharing (touchscreen, keyboard, mouse), and report printing services. Does not generate patient data; does not provide auditory alarm annunciation. Used by trained healthcare professionals in clinical settings. Output: visual representation of monitor screens, alarm/INOP states, and printed reports. Benefits: enables remote viewing and operation of patient monitors, facilitating clinical workflow and patient monitoring by caregivers.
Clinical Evidence
Bench testing only. Verification and validation included functional, regression, and system-level hazard analysis testing. Testing confirmed design risk mitigation effectiveness and adherence to ANSI/AAMI/IEC 62304:2006 standards.
Technological Characteristics
Software-only product; distributed system architecture; runs on customer-supplied off-the-shelf IT equipment with Microsoft OS and databases. Connectivity: network-connected to Philips patient/fetal monitors. Standards: ANSI/AAMI/IEC 62304:2006 (Software life cycle).
Indications for Use
Indicated for trained healthcare professionals to provide local and remote display, operation, and report printing for specified network-connected Philips patient and fetal/maternal monitors. Not intended for remote monitoring of unattended patients.
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}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
Philips Medizin Systeme Boeblingen GmbH Michael Asmalsky Senior Regulatory Affairs Engineer Hewlett-Packard-Str. 2 Boeblingen, Baden Wuerttemberg D-71034 GERMANY
September 1, 2023
Re: K182637
Trade/Device Name: Philips IntelliVue XDS Software Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer and Rate Alarm) Regulatory Class: Class II Product Code: MSX, DSH, OUG
Dear Michael Asmalsky:
The Food and Drug Administration (FDA) is sending this letter to notify you of an administrative change related to your previous substantial equivalence (SE) determination letter dated April 26, 2019. Specifically, FDA is updating this SE Letter to remove the secondary product code NSX as an administrative correction.
Please note that the 510(k) submission was not re-reviewed. For questions regarding this letter, please contact Aneesh Deoras, OHT2: Office of Cardiovascular Devices, 240-402-4363, Aneesh.Deoras@fda.hhs.gov.
Sincerely,
Aneesh S. Deoras -S
for
Jennifer Shih 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
{1}------------------------------------------------
Image /page/1/Picture/0 description: The image contains the logos of the Department of Health & Human Services and the U.S. Food & Drug Administration (FDA). The Department of Health & Human Services logo is on the left, and the FDA logo is on the right. The FDA logo is in blue and includes the words "U.S. Food & Drug Administration".
April 26, 2019
Philips Medizin Systeme Boeblingen GmbH Michael Asmalsky Senior Regulatory Affairs Engineer Hewlett-Packard Str. 2 Boeblingen, 71034 De
Re: K182637
Trade/Device Name: Philips IntelliVue XDS Software Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MSX, DSH, NSX, OUG Dated: March 19, 2019 Received: March 29, 2019
Dear Michael Asmalsky:
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/cfpmr/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 requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part
{2}------------------------------------------------
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/CombinationProducts/GuidanceRegulatoryInformation/ucm597488.html); good manufacturing practice requirements as set forth in the quality systems (QS) 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 http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/) and CDRH Learn (http://www.fda.gov/Training/CDRHLearn). 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 (http://www.fda.gov/DICE) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
# Arielle Drummond -S
for Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
## Indications for Use
510(k) Number (if known) K182637
Device Name Philips IntelliVue XDS Software Rev.M.1
#### Indications for Use (Describe)
The Intelli Vue XDS Software is intended for use as an additional, independent display for viewing screens, generated by specified network-connected Philips patient monitors. The IntelliVue XDS Software alone is not intended for remotely monitoring patients without caregivers in vicinity (unattended patients).
It is indicated for local and remote operation of these Philips patient monitors. It is indicated for printing reports as generated by these Philips patient monitors. It is indicated to be used by trained healthcare professionals.
Rx Only: Caution, U.S. Federal Law restricts this device to sale by or on the order of a physician.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
| <div> <span style="text-decoration: overline;">☑</span> Prescription Use (Part 21 CFR 801 Subpart D) </div> | <div> <span style="text-decoration: overline;">☐</span> Over The Counter Use (21 CFR 801 Subpart C) </div> |
## 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."
{4}------------------------------------------------
Image /page/4/Picture/0 description: The image shows the word "PHILIPS" in large, blue, bold letters. Above the word "PHILIPS" and to the right, the text "K182637 Page 1 of 3" is visible. The text is smaller and in a different font than the word "PHILIPS". The overall image appears to be a logo or a page from a document.
## 510(k) Summary
## 510(k) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirements of the Safe Medical Devices Act of 1990 and 21 C.F.R. §807.92.
1.) The submitter of this premarket notification is:
Michael Asmalsky Philips Medizin Systeme Boeblingen GmbH Hewlett-Packard-Str. 2 D-71034 Boeblingen. Germany Tel: ++49 7031 463-1277 Fax: ++49 7031 463-2442 e-mail: michael.asmalsky@philips.com
This summary was prepared on April 25th 2019.
2.) The trade names/proprietary names of the device is:
the Philips IntelliVue XDS Software with software Revision M.1.
The common/usual name is:
for the IntelliVue XDS Software: Information system, bedside (GMDN 17223)
The Classification names for the IntelliVue XDS Software are as follows:
| Device Panel | Classification | ProCode | Description |
|---------------------------|----------------|---------|--------------------------------------------------------------|
| Cardiovascular<br>Devices | 870.2300, II | MSX | System, Network and Communication,<br>Physiological Monitors |
| | §870.2800, II | DSH | Recorder, Magnetic tape, Medical |
| General Hospital | not classified | NSX | Software, transmission and storage,<br>patient data |
| General Hospital | §880.6310, I | OUG | Medical Device Data System |
3.) The modified Philips IntelliVue XDS Software (SW Rev. M.1) is substantially equivalent to the previously cleared Philips IntelliVue XDS Software marketed pursuant to K161531.
4.) Description of the Devices:
The IntelliVue XDS Software (867019) is a bedside information system. The IntelliVue XDS Software provides network services, printing services, patient monitor remote display services, launch pad services, input device sharing services and XDS database services.
The IntelliVue XDS Software can be connected to one or more specified Philips patient monitors and allows the remote viewing of the patient monitor generated data. Depending on the configuration, the remote operation of the network-connected patient monitor with standard off-the shelf information technology equipment input devices (touch screen, keyboard, and mouse) is also supported.
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the word "PHILIPS" in large, blue, bold letters. Above the word "PHILIPS" are the words "K182637" and "Page 2 of 3" in a smaller font size. The text is aligned to the right side of the image.
The IntelliVue XDS software does not modify or alter the Philips specified patient monitor. nor does it generate any data on its own. It is solely displaying the patient monitor generated data. It also displays the current alarm and INOP states for the patient, but does not provide an auditory alarm signal announciation function. The IntelliVue XDS Software is not a primary monitoring or alarming device.
The IntelliVue XDS Software is a software only product. It is intended to be installed on customer supplied compatible off-the shelf information technology equipment that meet the technical requirements as specified by Philips.
The IntelliVue XDS Software can currently be connected to the following compatible patient monitors:
The IntelliVue XDS Software can currently be connected to the following compatible patient monitors:
- Philips IntelliVue patient monitors X2/MP2, MP5, MP5SC, MP60-90, .
- . Philips IntelliVue patient monitors X3/MX100, MX400, MX 430, MX450, MX500, MX550, MX600, MX700 or MX800
- . Philips IntelliVue patient monitor XG50
The subject modification adds the Philips Avalon fetal/maternal monitors FM20. FM30. FM40 and FM50 to the list of specified network-connected Philips patient monitors compatible with the IntelliVue XDS Software.
To support the before described purposes the IntelliVue XDS Software was modified to maintain a consistent numbering scheme. The modified common software revision is Rev.M.1.
Intended Use:
The Intended Use has not changed. The Indications for Use of the subject Philips IntelliVue XDS Software (867019) have been aligned with section IV, D.1 of the FDA Guidance about Evaluating Substantial Equivalence in Premarket Notifications [510(k)] issued on: July 28, 2014. The indications for use have slightly changed as a result of this alignment and of the subject modifications.
The device has the following detailed Intended Use and Indications for Use Statements in its Instructions for Use:
## Philips IntelliVue XDS Software:
The IntelliVue XDS Software is intended for use as an additional, independent display for viewing screens, generated by specified network-connected Philips patient monitors. The IntelliVue XDS Software alone is not intended for remotely monitoring patients without caregivers in vicinity (unattended patients)
It is indicated for local and remote operation of these Philips patient monitors. It is indicated for printing reports as generated by these Philips patient monitors. It is indicated to be used by trained healthcare professionals.
Rx Only: Caution, U.S. Federal Law restricts this device to sale by or on the order of a physician.
## 5.) Technological Characteristics:
The modified device has the same technological characteristics as the legally marketed predicate device. It is a software only product intended to be installed on Philips specified standard (of-theshelf) IT devices. It uses a distributed system architecture and it is suitable for use with the specified Microsoft® Operating System and Databases.
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the word "PHILIPS" in large, bold, blue letters. Above the word "PHILIPS" and to the right, the text "K182637 Page 3 of 3" is visible in a smaller font size. The text appears to be part of a document or report, with the page number indicating it is the third and final page. The overall image has a clean and professional look, likely representing the branding of the Philips company.
## 6.) Summary of Verification, Validation and Testing Activities and Conclusion:
Verification, validation, and testing activities establish the performance, functionality, and reliability characteristics of the subject modified device with respect to the predicate. Testing involved software testing on integration level (functional testing and regression testing) and software testing on system level (hazard analysis testing and dedicated software performance testing).
Software verification and validation testing was conducted and documentation was provided as recommended by FDA's 2005 Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices."
Testing as required by the hazard analysis was conducted and all specified pass/fail criteria have been met. The test results confirmed the effectiveness of the implemented design risk mitigation measures.
Verification according to the applicable safety and performance standards was conducted as described below:
| Standard | Type |
|--------------------------|----------------------------------------------------|
| ANSI/AAMI/IEC 62304:2006 | General Standard:<br>Software life cycle processes |
Pass/Fail criteria were based on the specifications cleared for the predicate device and all test results showed substantial equivalence. The results demonstrate that the Philips IntelliVue XDS Software (SW Rev.M.1) meets all safety and reliability requirements and performance claims.
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.