QMAPP® is intended for use by professional healthcare providers for physiological/hemodynamic monitoring. The system may be used to display and analyze surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), End tidal CO2 (EtCO2), fractional flow reserve (FFR), non-invasive blood pressure (NiBP), surface body temperature, cardiac output and intra-cardiac ECG. QMAPP® provides also clinical data acquisition, medical image/data processing and analytical assessment. QMAPP® is intended for use in the areas of, but not limited to cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology. QMAPP® can be used standalone and in networked environments. The system is intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical calculations and exporting various representations of the acquired data. Data may also be acquired from and/or send to other devices, such as physiological monitoring system, information management systems, image acquisition/storage devices and other medical devices.
Device Story
QMAPP® is a physiological/hemodynamic monitoring and reporting system comprising an Amplifier Unit, Live Monitoring CPU, and Reporting CPU. The Amplifier connects to patient sensors (ECG, SpO2, NiBP, EtCO2, invasive pressure, temperature, cardiac output, intra-cardiac ECG). The Amplifier transmits data via Ethernet to the Live Monitoring CPU for real-time visualization and parameter control. The Reporting CPU, typically in a technical room, manages a database for storage, retrieval, clinical calculations, and reporting. The system operates standalone or within a hospital network, interfacing with third-party equipment via HL7/DICOM. Healthcare providers use the system to monitor vital signs, document procedures, and perform analytical assessments during cardiac or radiological interventions. The output assists clinicians in real-time patient status assessment and procedural data management, potentially improving clinical decision-making and workflow efficiency.
Clinical Evidence
Bench testing only. Testing included performance verification for ECG, heart rate, SpO2, NiBP, IBP, cardiac output, intra-cardiac ECG, skin temperature, and respiratory effort. System met requirements for EMC (IEC 60601-1-2), electrical safety (AAMI/ANSI EC 60601-1), and specific performance standards for ECG (IEC 60601-2-27), NIBP (IEC 80601-2-30), IBP (IEC 60601-2-34), thermometers (ISO 80601-2-56), and pulse oximeters (ISO 80601-2-61). Usability testing was also conducted.
Technological Characteristics
System consists of an Amplifier Unit (298x233x47mm, 2200g), Live Monitoring CPU, and Reporting CPU. Connectivity via Ethernet, HL7, and DICOM. Power: 24 VDC. Sensing principles: Impedance pneumography, oscillometric NIBP, thermistor temperature, pressure transducers, and electrophysiology catheters. Software performs data acquisition, visualization, and analysis. Sterilization: N/A (non-sterile).
Indications for Use
Indicated for professional healthcare providers for physiological/hemodynamic monitoring in cardiology, cardiac catheterization, electrophysiology, radiology, and invasive radiology. Patient population: adults.
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 27, 2025
Fysicon BV
% Patsy Trisler
Consultant and Official Correspondent
Trisler Consulting
306 Turnberry Court
Lebanon, Indiana 46052
Re: K241766
Trade/Device Name: QMAPP® (Hemo, Hemo Lite, PCM, GO, Hybrid)
Regulation Number: 21 CFR 870.2300
Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm)
Regulatory Class: Class II
Product Code: MWI, DQK
Dated: December 9, 2024
Received: December 9, 2024
Dear Patsy Trisler:
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}
K241766 - Patsy Trisler
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 System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 systems (QS) regulation (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}
K241766 - Patsy Trisler
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,
Stephen C. Browning -S
LCDR Stephen Browning
Assistant Director
Division of Cardiac Electrophysiology,
Diagnostics, and Monitoring Devices
Office of Cardiovascular Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
K241766
Device Name
QMAPP® (Hemo, Hemo Lite, PCM, GO, Hybrid)
Indications for Use (Describe)
QMAPP® is intended for use by professional healthcare providers for physiological/hemodynamic monitoring. The system may be used to display and analyze surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), End tidal CO2 (EtCO2), fractional flow reserve (FFR), non-invasive blood pressure (NiBP), surface body temperature, cardiac output and intra-cardiac ECG.
QMAPP® provides also clinical data acquisition, medical image/data processing and analytical assessment.
QMAPP® is intended for use in the areas of, but not limited to cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology.
QMAPP® can be used standalone and in networked environments. The system is intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical calculations and exporting various representations of the acquired data. Data may also be acquired from and/or send to other devices, such as physiological monitoring system, information management systems, image acquisition/storage devices and other medical devices.
☐ 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."
{4}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
510(k) SUMMARY – QMAPP® – K241766-S001
| SUBMITTER | |
| --- | --- |
| Submitter Name: | Fysicon B.V. |
| Submitter Address: | Hoogheuvelstraat 114, 5349 BA Oss, The Netherlands |
| Contact Person: Telephone #: | C.W.A. (Eric) van Antwerpen
+31 412 653333 |
| Date Prepared: | 25 July 2025 |
| DEVICE | |
| Device Trade Name: | QMAPP® (Hemo, Hemo Lite, PCM, GO, Hybrid) |
| Common and Classification Name(s): | Monitor, Physiological, Patient (Without Arrhythmia Detection Or Alarms) |
| Classification #: | 21 CFR 870.2300, 21 CFR 870.1425 |
| Product Code | MWI, DQK |
| Regulatory Class | 2 |
| Review Panel | Cardiovascular |
| PREDICATE DEVICE | |
| Primary Predicate Device | K170032, QMAPP® |
| Secondary Predicate Device | K131497, McKesson Cardiology™ Hemo |
| DEVICE DESCRIPTION | The QMAPP® system offers a complete physiological/hemodynamic monitoring and reporting system. The system is built from three units: an Amplifier, Live Monitoring CPU and Reporting CPU. The Amplifier Unit has various sensors connected with the patient, e.g. ECG, SpO2 and NiBP. The Amplifier Unit is connected to the Live Monitoring CPU via a dedicated Ethernet connection. The acquired patient information can be visualized on a Live Monitoring CPU. Typically located in the technical room. A software application executed on the Live Monitoring CPU can visualize the patient information. Also the Amplifier Unit can be controlled, i.e. most importantly, to set acquisition and filtering parameters for the different sensors, by the Live Monitoring CPU. Optionally the Monitoring unit can be connected via a dedicated Ethernet connection to a Reporting CPU, typically located in the technical room. On the Reporting CPU a database is installed which facilitates data storage and retrieval. A software application executed on the Reporting CPU serves as a patient data management system. It can e.g. be used for analysis, calculation and reporting in various representations of patient information. |
510(k) Summary
Page 1 of 11
K241766
{5}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| | The QMAPP® system, can operate standalone or it can be part of a typical hospital network infrastructure. The latter offers the possibility to send or receive information from and to other devices. The software has several communication modules, based on HL7 or DICOM protocols to interface with third party equipment/systems.
•The QMAPP® system works with 3rd party 510(k) cleared SpO2 module (Covidien Nellcor, K083325), NiBP module (CAS Medical Systems, MAXNIBP ND+, e.g. used in FDA cleared device CAS Medical Systems, 740 Select, K150620) and EtCO2 sensors e.g. used in FDA cleared device CLEO Patient Monitor, K142244. |
| --- | --- |
| PHYSICAL DESCRIPTION | QMAPP® Amplifier dimensions: 298 x 233 x 47 mm, Weight +/- 2200g, Power External 24 VDC |
| INTENDED USE / INDICATIONS FOR USE | QMAPP® is intended to be used by professional healthcare providers for physiological/hemodynamic monitoring. The system may be used to display and analyze surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), End tidal CO2 (EtCO2), fractional flow reserve (FFR), non-invasive blood pressure (NiBP), surface body temperature, cardiac output and intra-cardiac ECG.
QMAPP® provides also clinical data acquisition, medical image/data processing and analytical assessment.
QMAPP® is intended for use in the areas of, but not limited to cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology.
QMAPP® can be used standalone and in networked environments. The system is intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical calculations and exporting various representations of the acquired data. Data may also be acquired from and/or send to other devices, such as physiological monitoring system, information management systems, image acquisition/storage devices and other medical devices. |
| --- | --- |
| SUMMARY OF TECHNOLOGICAL CHARACTERISTICS | The QMAPP® system offers vital signs measuring, visualization, monitoring and analysis. The QMAPP Amplifier offers Surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), end tidal CO2 (EtCO2), Respiration effort, non-invasive blood pressure (NiBP), surface body temperature, cardiac output and intra-cardiac ECG measurements. Typically made in areas of, but not limited to |
510(k) Summary
Page 2 of 11
K241766
{6}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| | cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology.
The vital signs data is transferred to a Live Monitoring CPU, which offers visualization of the vital sign information. The vital signs information can also be transferred to a Reporting CPU, which offers data storage, connection to Hospital Information Systems and PACS. The Reporting CPU also offers vital signs analysis and reports capabilities. |
| --- | --- |
| NON-CLINICAL TESTS | |
| Bench testing | was carried out on the following characteristics:
• Electrocardiograph (EGG)
• Heart rate
• SpO2
• NiBP
• IBP
• Cardiac Output
• Intra cardiac ECG
• Skin Temperature
• ECG impedance for Rate of respiratory effort
• Measurement accuracy
• Electromagnetic compatibility (EMC)
• Electrical safety testing
• Mechanical safety testing
• Software verification and validation testing |
| Usability Testing | In addition to the above, usability testing was also conducted. |
| Referenced Standards and Performance Testing | The QMAPP® system was tested and meets the requirements of following performance Standards.
• AAMI/ANSI EC 60601-1:2005/(R)2012 & A1:2012 C1:2009/(R)2012 & A2:2010/(R)2012 Medical electrical equipment - General requirements for basic safety and essential performance.
• IEC 60601-1-2:2014 Medical electrical equipment - Part 1-2: General requirements for safety – Collateral standard: Electromagnetic compatibility – Requirements and tests.
• IEC 60601-2-27:2016 Medical Electrical Equipment - Part 2-27: Particular Requirements for The Basic Safety and Essential Performance of Electrocardiographic Monitoring Equipment.
• IEC 80601-2-30:2018 Medical Electrical Equipment - Part 2-30: Particular Requirements for The Basic Safety and Essential Performance of Automated Non-Invasive Sphygmomanometers.
• IEC 60601-2-34:2011 Medical Electrical Equipment - Part 2-34: Particular Requirements for The Basic Safety, Including Essential Performance, Of Invasive Blood Pressure Monitoring Equipment. |
510(k) Summary
Page 3 of 11
K241766
{7}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| | • ISO 80601-2-56:2017 Medical Electrical Equipment - Part 2-56: Particular Requirements for Basic Safety and Essential Performance of Clinical Thermometers for Body Temperature Measurement.
• ISO 80601-2-61:2017 Medical electrical equipment -- Part 2-61: Particular requirements for basic safety and essential performance of pulse oximeter equipment. |
| --- | --- |
| CONCLUSION | The following comparison table shows the similarities and differences in technological characteristics. None of the differences raise new questions of safety and effectiveness.
The non-clinical data support the safety of the device and the hardware and software verification and validation testing demonstrate that the QMAPP® system should perform as intended in the specified use conditions. |
| STATEMENT OF SUBSTANTIAL EQUIVALENCE | The information and data provided in this Traditional 510(k) establish that the modified device is substantially equivalent in the intended use, design, principle of operation, technology, materials, specifications and performance to the predicates. |
510(k) Summary
Page 4 of 11
K241766
{8}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
Substantial Equivalence Summary Table
| TRADE NAME > FEATURE | Proposed (modified) Device: QMAPP®, QMAPP® GO, QMAPP® PCM, QMAPP Hemo and QMAPP® Hybrid | Primary Predicate Device: QMAPP®, QMAPP® GO, QMAPP® AP and QMAPP® EP | Secondary Predicate Device: McKesson Cardiology™ Hemo |
| --- | --- | --- | --- |
| 510(k) Number | K241766 | K170032 | K131497 |
| Regulation, Product Code and Regulatory Name | Same as primary predicate device | 21 CFR 870.1425, DQK Programmable diagnostic computer
21 CFR 870.2300, MWI Cardiac monitor (including cardiotachometer and rate alarm) | 21 CFR 870.1425, DQK Programmable diagnostic computer
21 CFR 870.2300, MWI Cardiac monitor (including cardiotachometer and rate alarm) |
| Manufacturer | Same as primary predicate device | Fysicon B.V. | McKesson Israel Ltd. |
| Device description summary | Same as primary predicate device | The QMAPP® system offers a complete physiological/ hemodynamic monitoring and reporting system. The system is built from three units: an Amplifier, Live Monitoring CPU and Reporting CPU. The Amplifier Unit has various sensors connected with the patient, e.g. ECG, SpO2 and NiBP. The Amplifier Unit is connected to the Live Monitoring CPU via a dedicated Ethernet connection. The acquired patient information can be visualized on a Live Monitoring CPU. Typically located in the technical room. A software application executed on the Live Monitoring CPU can visualize the patient information. Also the Amplifier Unit can be controlled, i.e. most importantly, set acquisition and filtering parameters for the different sensors, by the Live Monitoring CPU. Optionally | McKesson Cardiology™ Hemo device is a hemodynamic monitoring system for monitoring vital signs, performing measurements and calculations, documenting procedure and patient data and interfacing to other systems and devices during and after procedures in the areas of: cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology and other areas where patient/ procedural data management is needed. McKesson Cardiology™ Hemo also acquires patient information from other hospital information systems and makes hemodynamic information available to them. It facilitates seamless interfacing with hospital information systems and cardiac image management, archiving and reporting systems. |
510(k) Summary
{9}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| | | the Monitoring unit can be connected via a dedicated Ethernet connection to a Reporting CPU, typically located in the technical room.
On the Reporting CPU a database is installed which facilitates data storage and retrieval. A software application executed on the Reporting CPU serves as a patient data management system. It can be used for analysis, calculation and reporting in various representations of patient information.
The QMAPP® system, can operate standalone or it can be part of a typical hospital network infrastructure. The latter offers the possibility to send or receive information from and to other devices. The software has several communication modules, based on HL7 or DICOM protocols to interface with third party equipment/systems. | McKesson Cardiology™ Hemo incorporates the FDA cleared ARGUS PB vital signs monitoring device (K012226), which provides patient monitoring via; ECG Leads; Invasive Blood Pressure; SpO2; NiBP; Body temperature; Thermal Dilution Cardiac output and CO2.
McKesson Cardiology™ Hemo is composed of:
A control and documentation unit (information System) which is used for administration, performing measurements, recording full disclosure, taking samples and entering procedure notes and overall data input and management of the patient and procedure data.
A Clinical Unit that incorporates the “Clinical Systems” and the “Front-End” unit (which incorporates the Schiller Argus PB device – K012226). The clinical unit is responsible for acquiring, analyzing and displaying patient vitals and other pertinent clinical dat. The data is displayed on monitors. |
| --- | --- | --- | --- |
| Intended Use/Indications for Use Statement | QMAPP® is intended to be used by professional healthcare providers for physiological/hemodynamic monitoring. The system may be used to display and analyze surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), End tidal CO2 (EtCO2), fractional flow reserve (FFR), non-invasive blood pressure (NiBP), surface | QMAPP® is intended for use by professional healthcare providers for physiological/ hemodynamic monitoring. The system may be used to display and analyze surface ECG (Electrocardiogram), respiration, invasive pressures, pulse oximetry (SpO2), end tidal CO2 (EtCO2), fractional flow reserve (FFR), non-invasive blood pressure (NiBP), surface | McKesson Cardiology Hemo™ is intended for complete physiological/ hemodynamic monitoring, clinical data acquisition, medical image and data processing, and analytical assessment.
McKesson Cardiology™ Hemo is also intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical |
510(k) Summary
Page 6 of 11
{10}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| | body temperature, cardiac output and intra-cardiac ECG.
QMAPP® provides also clinical data acquisition, medical image/data processing and analytical assessment.
QMAPP® is intended for use in the areas of, but not limited to cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology.
QMAPP® can be used standalone and in networked environments. The system is intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical calculations and exporting various representations of the acquired data. Data may also be acquired from and/or send to other devices, such as physiological monitoring system, information management systems, image acquisition/storage devices and other medical devices. | body temperature, cardiac output and intra-cardiac ECG.
QMAPP® is intended to be used on the patient population of adults.
QMAPP® provides also clinical data acquisition, medical image/data processing and analytical assessment.
QMAPP® is intended for use in the areas of, but not limited to cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology.
QMAPP® can be used standalone and in networked environments. The system is intended for patient/procedural data management, such as documentation, logging, reporting, trending, storing, reviewing, carrying out clinical calculations and exporting various representations of the acquired data. Data may also be acquired from and/or send to other devices, such as physiological monitoring system, information management systems, image acquisition/storage devices and other medical devices. | calculations and exporting various representations of the acquired data. Data may also be acquired from and/or sent to other devices, such as physiological monitoring systems, information management systems, image acquisition/storage devices, and other medical devices.
McKesson Cardiology™ Hemo is intended for use in the areas of: cardiology, cardiac catheterization, electrophysiology, radiology, invasive radiology, and other areas where patient/procedural data management is needed.
User-adjustable alarms (both visual and audible) available in the system alert the operator to anomalous occurrences and facilitate timely responses.
Use of the system is not intended for unattended patient monitoring or in situations where arrhythmia detection is required. |
| --- | --- | --- | --- |
| Intended Populations | No restrictions or limitations | Adults | No restrictions or limitations |
| Dimensions | Same as primary predicate device | 298 x 233 x 47 mm
11.7 x 9.2 x 1.9 inch | 280 x 135 x 130 mm
11.0 x 5.3 x 5.1 inch |
K241766
510(k) Summary
Page 7 of 11
{11}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| Weight | Same as primary predicate device | 2200 grams
4.85 pounds | 3800 grams
8.38 pounds |
| --- | --- | --- | --- |
| Energy source | Same as primary predicate device | 90 - 264V
24V DC at tableside | 100-264V
24V at tableside |
| Amplifier – Monitor CPU | Same as primary predicate device | 100 Mbit | RS232 |
| Monitor CPU – Reporting CPU | Same as primary predicate device | 100 MB | 100 MB |
| CPU LAN | Same as primary predicate device | Intel i5, 2.00 GHz | > Intel Pentium 4 |
| Data sent to central server | Same as primary predicate device | Yes, if a networked system is chosen | Yes, if a networked system is chosen |
| MONITORS SURFACE ECG | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | ECG lead wires attached to disposable electrodes to the skin | ECG lead wires attached to disposable electrodes to the skin |
| Resolution | Same as primary predicate device | 24 bit | 12 bit |
| Input impedance | Same as primary predicate device | > 2.5 MOhm | > 2.5 MOhm |
| Common mode rejection | Same as primary predicate device | > 100 dB | > 100 dB |
| Sampling frequency | Same as primary predicate device | 2 – 32 KHz | 1 KHz |
| Channels | Same as primary predicate device | 12 | 12 |
| MONITORS HEART RATE | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | QRS detection | QRS detection |
| HR range | Same as secondary predicate device | 15 – 300 bpm | 15 – 350 bpm |
| Accuracy | Same as primary predicate device | ± 2% | ± 2% |
510(k) Summary
Page 8 of 11
{12}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| MONITORS RESPIRATION EFFORT | Same as primary predicate device | Yes | Yes |
| --- | --- | --- | --- |
| Method | Same as primary predicate device | Impedance Pneumography | Impedance Pneumography |
| Resolution | Same as primary predicate device | 1/min | 1/min |
| Range | Same as primary predicate device | 0 – 150 / Min | 0 – 200 / Min |
| Channels | Same as primary predicate device | 1 | 1 |
| MONITORS NIBP | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | Oscillometric (CAS Max module) | Oscillometric |
| Range | Same as primary predicate device | 15 - 260 mm Hg | 15 – 200 mm Hg |
| Accuracy | Same as primary predicate device | ± 5 mm Hg | ± 5 mm Hg |
| (Third party) Module | Same as primary predicate device | CAS Medical Systems, 740 Select, (K150620) | Part of device: ARGUS PB vital signs monitoring Device, (K012226), |
| MONITORS OXYGEN SATURATION | Same as primary predicate device | Yes | Yes |
| --- | --- | --- | --- |
| Method | Same as primary predicate device | Nellcor Oximax | Masimo Set |
| Range | Same as primary predicate device | 1 -100% | 1 – 100% |
| Accuracy | Same as primary predicate device | ± 1% | ± 3% |
| Channels | Same as primary predicate device | 1 | 1 |
| (Third party) Module | Same as primary predicate device | OxiMax N-600x Pulse Oximeter (K083325) | Part of device ARGUS PB-1000 Masimo Set (K012226), |
| MONITORS IBP | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | Pressure transducer | Pressure transducer |
| Accuracy | Same as primary predicate device | ± 2 mm Hg or ± 1 % | ± 2 mm Hg or ± 1 % |
510(k) Summary
K241766
Page 9 of 11
{13}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| Range | Same as primary predicate device | -30 - 320 mm Hg | - 400 – 400 mm Hg |
| --- | --- | --- | --- |
| Channels | Same as primary predicate device | 4 | 4 |
| **MONITORS SKIN TEMPERATURE** | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | Thermistor, YSI compatible | Thermistor, YSI compatible |
| Range | Same as primary predicate device | 20° – 45° C
68° – 113° F | 15° – 45° C
59° – 113° F |
| Accuracy | Same as primary predicate device | ± 0.1° C
± 0.18° F | ± 0.1° C
± 0.18° F |
| Channels | Same as primary predicate device | 2 | 1 |
| **MONITORS CARDIAC OUTPUT** | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | Thermo Dilution and (calculated) FICK | Thermo Dilution and (calculated) FICK |
| Range | Same as primary predicate device | 0.1 – 20 L | 0.1 – 20 L |
| Accuracy | Same as primary predicate device | ± 0.1 L | ± 0.1 L |
| **MONITORS EtCO_{2}** | Same as primary predicate device | Yes | Yes |
| Method | Same as primary predicate device | Low flow Side stream | Low Flow Side stream |
| CO_{2} resolution | Same as primary predicate device | 0.1 mm Hg 0 to 49 mm Hg
0.2 mm Hg 49 to 152 mm Hg | 0.1 mm Hg 0 to 69 mm Hg
0.25 mm Hg 70 to 150 mm Hg |
| CO_{2} Accuracy | Same as primary predicate device | 0 – 40 mm Hg, ± 2 mm Hg;
41 – 70 mm Hg, ± 5%;
71-100 mm Hg, ± 8%;
>101 10% | 0– 40mmHg, ±2 mm Hg
41– 70mmHg, ±5%
71–100mmHg, ±8%
101–150mmHg, ±10%
Above 80 BPM, ±12% |
| (Third party) Module | Same as primary predicate device | GoldWEI C300
Part of device CLEO Patient Monitor,
(K142244) | Respironics
Capnostat 5 sensor,
(K042601) |
510(k) Summary
Page 10 of 11
{14}
Submitter: Fysicon BV
QMAPP®
Premarket Notification: Traditional 510(k)
| MONITORS
Intra Cardiac
ECG | Same as primary predicate device | Yes | No |
| --- | --- | --- | --- |
| Method | Same as primary predicate device | Electro Physiology catheter | n/a |
| Resolution | Same as primary predicate device | 24 Bit | n/a |
| Input impedance | Same as primary predicate device | > 2.5 MOhm | n/a |
| Common mode
rejection | Same as primary predicate device | > 100 dB | n/a |
| HR range | Same as primary predicate device | 15 – 300 bpm | n/a |
| Sampling
frequency | Same as primary predicate device | 2 - 32 kHz | n/a |
| Channels | Same as primary predicate device | 8, 16 or 32 (bipolar) Channels | 0 |
510(k) Summary
Page 11 of 11
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.