K172226 · Philips Medical Systems · MHX · Nov 9, 2017 · Cardiovascular
Device Facts
Record ID
K172226
Device Name
MX40 Release B.07
Applicant
Philips Medical Systems
Product Code
MHX · Cardiovascular
Decision Date
Nov 9, 2017
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1025
Device Class
Class 2
Attributes
Pediatric
Indications for Use
The device is intended for monitoring and recording of and to generate alarms for, multiple physiological parameters of adults and pediatrics in a hospital environment and during patient transport inside hospitals. Not intended for home use. Intended for use by health care professionals.
Device Story
MX40 is a battery-operated, wearable multi-parameter patient monitor. It acquires physiological data (ECG, respiration, SpO2, NIBP) and generates alarms/technical alerts. It integrates multi-radio design (Smart Hopping 1.4GHz, 802.11a/b/g/h, Short Range Radio 2.4 GHz) for wireless connectivity to Philips telemetry networks and IntelliVue monitors. Used in hospitals and during transport by healthcare professionals. Output is transmitted to local monitoring systems, bedside monitors, or information systems. Clinicians use output for real-time patient monitoring and clinical decision-making. Benefits include continuous patient surveillance and mobility within hospital environments.
Clinical Evidence
No clinical performance testing was performed. Substantial equivalence was established through non-clinical verification and validation activities, including risk analysis, design reviews, and system-level performance testing based on cleared predicate specifications.
Technological Characteristics
Battery-operated wearable monitor. Multi-radio connectivity (1.4GHz, 802.11a/b/g/h, 2.4GHz SRR). Parameters: ECG, Resp, SpO2, NIBP. Complies with IEC60601-1 3rd edition. Includes MCS PigTail and Block Adapter for respiration. Software-based monitoring with alarm generation and network communication capabilities.
Indications for Use
Indicated for use by health care professionals whenever there is a need for monitoring the physiological parameters of patients. Intended for monitoring and recording of, and to generate alarms for, multiple physiological parameters of adults and pediatrics in hospital environments and during transport inside hospitals.
Regulatory Classification
Identification
The arrhythmia detector and alarm device monitors an electrocardiogram and is designed to produce a visible or audible signal or alarm when atrial or ventricular arrhythmia, such as premature contraction or ventricular fibrillation, occurs.
Special Controls
*Classification.* Class II (special controls). The guidance document entitled “Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm” will serve as the special control. See § 870.1 for the availability of this guidance document.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the seal of the Department of Health & Human Services. 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 FDA logo is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
November 9, 2017
Philips Medical Systems Theresa Poole Regulatory Specialist 3000 Minuteman Road Andover, Massachusetts 01810
Re: K172226
Trade/Device Name: MX40 Release B.07 Regulation Number: 21 CFR 870.1025 Regulation Name: Arrhythmia Detector And Alarm (Including ST-Segment Measurement And Alarm) Regulatory Class: Class II Product Code: MHX, DSI, DOA, DSA, DRW, DRG, MLD, MSX Dated: July 18, 2017 Received: July 25, 2017
Dear Theresa Poole:
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. 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 801); medical device reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820);
{1}------------------------------------------------
## Page 2 - Theresa Poole
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 the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
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,
M.A. Wilhelm
for Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known)
#### K172226
Device Name
MX40 Release B.07
#### Indications for Use (Describe)
The intended use of the MX40 is to:
The device is intended for monitoring and recording of and to generate alarms for, multiple physiological parameters of adults and pediatrics in a hospital environment and during patient transport inside hospitals. Not intended for home use. Intended for use by health care professionals.
#### Indications for Use
Indicated for use by health care professionals whenever there is a need for monitoring the physiological parameters of patients. Intended for monitoring and recording of, and to generate alarms for, multiple physiological parameters of adults and pediatrics in hospital environments and during transport inside hospitals.
Type of Use (Select one or both, as applicable)X 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}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the word "PHILIPS" in large, bold, blue letters. Below the word "PHILIPS" is the text "MX40 Release B.07" in a smaller font size. Underneath that, the text "Special 510(k)" is displayed.
# 510(k) Summary MX40 Release B.07
This 510(k) summary of safety and effectiveness information is prepared in accordance with 21 CFR 807.92(c).
Date Prepared: 17 July 2017
### I. Submitter's name and address
| Manufacturer: | Philips Medical Systems<br>3000 Minuteman Road<br>Andover, MA 01810 USA |
|---------------|-------------------------------------------------------------------------|
|---------------|-------------------------------------------------------------------------|
Theresa Poole Contact Person: Regulatory Affairs Specialist Philips Medical Systems 3000 Minuteman Road, MS0480 Andover, MA 01810-1099
> Tel: 978 659 7621 Fax: 978 685 5624 Email: theresa.poole@philips.com
#### II. Device information
Device Name: MX40 Release B.07 Common Name: Physiological Monitor, Patient Monitor Classification panel: 74 - Cardiovascular
Classification names are as follows:
| Classification | ProCode | Description |
|----------------|---------|-----------------------------------------------------------------------|
| §870.1025, II | DSI | Detector and alarm, arrhythmia |
| §870.1025, II | MLD | Monitor, ST Segment with Alarm |
| §870.1025, II | MHX | Monitor, Physiological, Patient (with arrhythmia detection or alarms) |
| §870.2350, II | DRW | Electrocardiograph, Lead Switching Adapter |
| §870.2700, II | DQA | Oximeter |
| §870.2900, I | DSA | Cable, Transducer and Electrode, incl. Patient Connector |
| §870.2300, II | MSX | System, Network and Communication, Physiological Monitors |
| §870.2910, II | DRG | Transmitters and Receivers, Physiological Signal, Radiofrequency |
| §870.2300, II | DRT | Monitor, Cardiac (Incl. Cardiotachometer & Rate Alarm) |
#### III. Predicate device information
{4}------------------------------------------------
Image /page/4/Picture/0 description: The image shows the word "PHILIPS" in a large, bold, blue font. Below the brand name, the text "MX40 Release B.07" is displayed, followed by "Special 510(k)" on the next line. The text is in a smaller, black font, providing additional context or information related to the Philips brand.
INTELLIVUE MX40 PATIENT MONITOR Trade name: Manufacturer: Philips Medical Systems 510(k) clearance: K103646 Classification name: Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms) Device class: Class II Classification regulation: 21 CFR 870.1025 Classification panel: Cardiovascular Product code: MHX
#### IV.Device Description
The MX40 is a multi-parameter, battery operated patient monitor that is small enough to be worn by the patient. Its multi-radio design enables device operation within existing Philips telemetry networks while providing compatibility to the IntelliVue Information Center solutions. Along with infrastructure radios, the MX40 integrates a short-range radio (SRR), enabling wireless connectivity to the IntelliVue family of monitors. Acquired physiological data, along with physiological alarms and technical alert information are provided to multiple monitoring systems (local, bedsides and /or information systems).
Previously cleared compatible Accessories are still in use, no new accessories in this filing. The MX40 is compatible with the legally marketed Philips CL SpO2 Pod and CL NBP Pod (K101600, K111905). The CL SpO2/NBP Pods are small battery powered devices that measure oxygen saturation, pulse rate and blood pressure, pulse rate, respectively. A list of all accessories is available in the Instructions for Use.
#### V. Intended use/ Indications for Use
| MX40 Intended<br>Use/Indications for Use | The intended use of the MX40 is to: |
|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | The device is intended for monitoring and recording of and to generate<br>alarms for, multiple physiological parameters of adults and pediatrics in a<br>hospital environment and during patient transport inside hospitals. Not<br>intended for home use. Intended for use by health care professionals. |
| | Indications for Use |
| | Indicated for use by health care professionals whenever there is a need<br>for monitoring the physiological parameters of patients. Intended for<br>monitoring and recording of, and to generate alarms for, multiple<br>physiological parameters of adults and pediatrics in hospital<br>environments and during transport inside hospitals. |
| | Rx only. |
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the word "PHILIPS" in a large, bold, blue font. Below the brand name, the text "MX40 Release B.07" is displayed in a smaller, black font. Underneath that, the phrase "Special 510(k)" is also written in black.
## Comparison of Technological Characteristics with the Predicate Device
The device has the same technological characteristics as the legally marketed predicate devices. The change summary includes items listed in the table starting on page 4.
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the word "PHILIPS" in large, blue, sans-serif font. Below the word "PHILIPS" is the text "MX40 Release B.07" and "Special 510(k)" in a smaller, black, sans-serif font. The text appears to be a label or identifier for a product or software release.
| Key Characteristic | Predicate MX40<br>K103646, K113125 | MX40 Release B.07 |
|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for Use<br>Intended Use<br>Statement | Indicated for use by health care<br>professionals whenever there is a need<br>for monitoring the physiological<br>parameters of patients. Intended for<br>monitoring and recording of, and to<br>generate alarms for, multiple<br>physiological parameters of adults and<br>pediatrics in hospital environments and<br>during transport inside hospitals.<br>Intended for monitoring and recording of<br>and to generate alarms for, multiple<br>physiological parameters of adults and<br>pediatrics in a hospital environment and<br>during patient transport inside hospitals.<br>Not intended for home use. Intended for<br>use by health care professionals. | Same |
| Target Patient<br>Population | Adult and pediatric | Same |
| Users | Trained health care professionals | Same |
| System Interface | Connects to the Philips IntelliVue<br>Information Center for transmission of<br>patient parameters | Same |
| Care and Cleaning | Available instructions in IFU | Same |
| Communication | Smart Hopping 1.4GHz (CTS) Radio<br>802.11a/b/g/h Radio<br>Short Range Radio 2.4 GHz | Same |
| Multi-Parameter<br>patient monitoring | ECG, Resp, SpO2, and NIBP (data<br>acquisition for NIBP is not done by the<br>MX40) | Same |
| Device Software,<br>Device safety,<br>environmental<br>specifications, and all<br>specifications of<br>measurement<br>characteristics | Unchanged, as previously submitted | 1. Heart Rate Alarm<br>from Pulse,<br>requires PIC IX<br>version C.01 or<br>higher.<br>2. Auto report<br>battery inop<br>(Technical Alert)<br>when Standby is<br>in low battery<br>state<br>3. Support CI<br>(Connection<br>Indication)<br>message<br>transport using<br>Unicast protocol<br>for WLAN<br>4. Malfunc Inop for<br>software license<br>failure - Added<br>self-test to MX40<br>to allow for<br>confirmation of<br>Software License<br>version to assist<br>users to identify<br>compatibility to<br>other systems<br>5. Claim IEC60601-1<br>3rd edition<br>update IFU and<br>Product Labeling<br>appropriately<br>6. AAMI screen - A<br>new portrait<br>screen 1-wave<br>and 2 numerics to<br>support AAMI<br>EC13 display, local<br>control only &<br>cannot default to<br>this screen from<br>PIC-iX |
| Device Accessories | Unchanged, as previously submitted | MCS PigTail and Block<br>Adapter* Hardware to<br>support Respiration<br>measurements.<br>*Use of Block Adapter<br>requires MX40<br>software B.06 or<br>higher. |
| Device Hardware | Unchanged, as previously submitted | Same |
| Charging method | Unchanged, as previously submitted | Same |
{7}------------------------------------------------
Image /page/7/Picture/1 description: The image shows the word "PHILIPS" in a large, blue, sans-serif font. Below the word "PHILIPS" are the words "MX40 Release B.07" in a smaller, black, sans-serif font. Below that is the text "Special 510(k)" in the same font.
{8}------------------------------------------------
Image /page/8/Picture/0 description: The image shows the word "PHILIPS" in large, blue, bold letters. Below the brand name, the text "MX40 Release B.07 Special 510(k)" is displayed in a smaller, black font. The text appears to be related to a specific product or software version of Philips, possibly indicating a special release or compliance with regulatory standards.
#### Summary of Non-clinical testing
No performance standards have been issued under the authority of Section 514. The MX40 Release B.07 was tested in accordance with Philips verification and validation processes. Quality Assurance measures were applied to the system design and development, including:
- Risk Analysis ●
- Product Specifications ●
- Design Reviews
- Verification & Validations ●
### Summary of Clinical Testing
Clinical Performance testing for MX40 Release B.07 was not performed, as there were no new clinical applications that had hazards or risk mitigations that required a clinical performance testing to support equivalence.
#### Conclusions drawn from the Non-clinical and Clinical testing
Verification, validation, and testing activities, where required to establish the performance, functionality, and reliability characteristics of the new device with respect to the predicate are performed. Testing involved system level tests, performance tests, and safety testing from hazard analysis. Pass/Fail criteria were based on the specifications cleared for the predicate device and test results showed substantial equivalence. The MX40 Release B.07 meets all defined reliability requirements and performance claims.
#### VI.Conclusion
In summary, there is no change in either intended use or in the fundamental scientific technology employed by the MX40 patient monitor in the modification for B.07. We consider these device modifications to be substantially equivalent to previously cleared devices. Additionally, substantial equivalence was demonstrated with non-clinical performance testing, which complied with the requirements specified in the international and FDA-recognized consensus standards. The non-clinical performance tests provided in this 510(k) premarket notification demonstrate that the subject device is as safe and effective as its predicate device without raising any new safety and/or effectiveness concerns.
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.