K252302 · Biosense Webster, Inc. · DQK · Aug 22, 2025 · Cardiovascular
Device Facts
Record ID
K252302
Device Name
CARTO™ 3 EP Navigation System V8.1
Applicant
Biosense Webster, Inc.
Product Code
DQK · Cardiovascular
Decision Date
Aug 22, 2025
Decision
SESE
Submission Type
Special
Regulation
21 CFR 870.1425
Device Class
Class 2
Attributes
Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K252302 · Aug 22, 2025
CARTO™ 3 EP Navigation System V8.1
Biosense Webster, Inc.
Historic clinical EP procedure records
Retrospective validation testing was conducted using historic clinical procedure data to verify the clinical functionality and quality of new software modules and enhancements.
Clinical functionality and quality of introduced modules
Indications for Use
The intended use of the CARTO™ 3 System is catheter-based cardiac electrophysiological (EP) procedures. The CARTO™ 3 System provides information about the electrical activity of the heart and about catheter location during the procedure. The system can be used on patients who are eligible for a conventional electrophysiological procedure. The system has no special contraindications.
Device Story
CARTO™ 3 EP Navigation System V8.1 is a catheter-based atrial and ventricular mapping system. It acquires intracardiac ECG signals and navigation catheter location data using magnetic sensor and Advanced Catheter Location (ACL) technologies. The system processes these inputs to generate 3D anatomical and electroanatomical maps of the heart. Used in clinical EP labs by physicians, the system displays real-time catheter visualization, tissue proximity indication (TPI), and electroanatomical data. It supports various catheters, including FARAWAVE, VARIPULSE, and SOUNDSTART ultrasound catheters. The system aids physicians in navigating the heart, identifying complex signals, and performing cardiac mapping, which facilitates clinical decision-making during ablation or diagnostic procedures. Benefits include enhanced visualization and real-time feedback on catheter-tissue proximity.
Clinical Evidence
No clinical trials were conducted. Evidence consists of bench-level verification and validation testing, including proof of design, functional verification, unit tests, and retrospective validation using historic clinical procedure data. Animal testing was performed to evaluate functionality under simulated clinical workflows. All testing met acceptance criteria.
Technological Characteristics
Hardware platform identical to predicate. Uses magnetic sensor and Advanced Catheter Location (ACL) technology. Components include Patient Interface Unit, workstation, monitors, signal processing unit, and location pad. Software-based system with enhancements to legacy modules (e.g., VISITAG, Confidence Module, CARTOSOUND). Connectivity supports various specialized catheters via XML-based recognition.
Indications for Use
Indicated for patients eligible for conventional catheter-based cardiac electrophysiological (EP) procedures. No special contraindications.
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
Predicate Devices
CARTO® 3 EP Navigation System Version 8.0 (K231207)
Submission Summary (Full Text)
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
August 22, 2025
Biosense Webster, Inc.
% Eyal Hendel
Associate Director of Regulatory Affairs
Biosense Webster, Ltd.
4 Hatnufa Street
Yokneam, 2066717
Israel
Re: K252302
Trade/Device Name: CARTO™ 3 EP Navigation System V8.1
Regulation Number: 21 CFR 870.1425
Regulation Name: Programmable Diagnostic Computer
Regulatory Class: Class II
Product Code: DQK
Dated: July 24, 2025
Received: July 24, 2025
Dear Eyal Hendel:
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}
K252302 - Eyal Hendel
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}
K252302 - Eyal Hendel
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,
# Aneesh S. Deoras -S
Aneesh Deoras
Assistant Director
Division of Cardiac Electrophysiology,
Diagnostics, and Monitoring Devices
Office of Cardiovascular Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K252302 | ? |
| Please provide the device trade name(s). | | ? |
| CARTO™ 3 EP Navigation System V8.1 | | |
| Please provide your Indications for Use below. | | ? |
| The intended use of the CARTO™ 3 System is catheter-based cardiac electrophysiological (EP) procedures. The CARTO™ 3 System provides information about the electrical activity of the heart and about catheter location during the procedure. The system can be used on patients who are eligible for a conventional electrophysiological procedure. The system has no special contraindications. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
{4}
510(K) SUMMARY
Applicant: Biosense Webster, Inc.
31 Technology Drive, Suite 200
Irvine, CA 92618, USA
Tel.: (800) 729-9010
Fax: (909) 839-8500
Contact Result: Eyal Hendel
Person: Associate Director of Regulatory Affairs
Biosense Webster (Israel), Ltd.
Phone: +972-52-5246178
Authored by: Eyal Hendel
Associate Director of Regulatory Affairs
Biosense Webster (Israel), Ltd.
Hen Keren Lap
Sr. Regulatory Affairs Program Lead
Biosense Webster (Israel), Ltd.
Date: July 23, 2025
Device Trade Name: CARTO™ 3 EP Navigation System V8.1
510(k) Number: K252302
Device Common Name: Cardiac Mapping System
Manufacturing Number: FG-5400-00
Device Classifications: Programmable diagnostic computer
Class II, 21 CFR 870.1425
Product Code: DQK
Predicate Device: CARTO® 3 EP Navigation System Version 8.0 510(k)#: K231207
1 of 5
{5}
2 of 5
# Manufacturing Facilities:
Biosense Webster (Israel), Ltd.
a Johnson & Johnson Company
4 Hatnufa Street
Yokneam, ISRAEL 2066717
Biosense Webster, Inc.,
23 Hubble Dr, Irvine, CA 92618
USA
# Device Description:

The CARTO™ 3 EP Navigation System V8.0, is a catheter-based atrial and ventricular mapping system designed to acquire and analyze navigation catheter's location and intracardiac ECG signals and use this information to display 3D anatomical and electroanatomical maps of the human heart. The location information needed to create the cardiac maps and the local electrograms are acquired using specialized mapping catheters and reference devices. The CARTO™ 3 System uses two distinct types of location technology – magnetic sensor technology and Advanced Catheter Location (ACL) technology.
The CARTO™ 3 System V8.1 consists of the following hardware components:
- Patient Interface Unit (PIU)
- Workstation with Graphic User Interface (GUI)
- Wide-Screen monitors, keyboard, and mouse
- Intracardiac In Port
- Intracardiac Out Port
- Power Supply
- Patches Connection Box and Cables (PU)
- Pedals
- Location Pad (LP)
- Signal Processing Unit (SPU)
All hardware components of the CARTO™ 3 system V8.1 are the same as those found in the predicate device.
# Indications for Use:
The intended use of the CARTO™ 3 System is catheter-based cardiac electrophysiological (EP) procedures. The CARTO™ 3 System provides information about the electrical activity of the heart and about catheter location during the procedure. The system can be used on
{6}
patients who are eligible for a conventional electrophysiological procedure.
The system has no special contraindications.
The indications for use for the CARTO™ 3 System V8.1 are identical to the indications for use of the predicate device, the CARTO® 3 System, software V8.0.
## Technological Characteristics:
The modified CARTO™ 3 EP Navigation System V8.1 has the same technological characteristics (i.e., design, material, chemical composition, energy source) as the predicate CARTO™ 3 EP Navigation System, software V8.0 (K231207). A summary of the technological characteristics of the new device compared to the predicate device is as follows:
- Have identical intended use.
- Use the same fundamental scientific technology.
- Have the same hardware platform.
- Have identical magnetic and ACL location mapping technology.
- Have identical magnetic location sensor and ACL location accuracy.
The differences between the predicate device and the modified device are the addition of new software features, improvements of the legacy modules.
## 1 CATHETERS SUPPORT
### 1.1 CARTO™ 3 SYSTEM SUPPORT OF FARAWAVE CATHETER VISUALIZATION
The Boston Scientific FARAWAVE catheter is supported by the CARTO™ 3 System through a validated XML file containing the catheter essential physical characteristics, such as shape, number of electrodes, and relative distances. This allows the system to recognize the catheter and accurately display its representation among other connected devices, maps and CT/MR imaging. Additionally, the CARTO™ 3 System provides Tissue Proximity Indication (TPI) for the FARAWAVE catheter, offering real-time feedback on electrode proximity to cardiac tissues.
### 1.2 SUPPORT WITH VARIPULSE™ CATHETER AND TRUPULSE™ GENERATOR
The PFA Support Module provides real-time display of the VARIPULSE™ Catheter in the CARTO™ 3 System. In addition, the
3 of 5
{7}
catheter can be used for standard functionality such as FAM acquisition, Electro anatomical MEM point acquisition, pacing, and building the visualization matrix.
## 1.3 CARTO™ 3 SYSTEM SUPPORT OF SOUNDSTART™ CRYSTAL ULTRASOUND CATHETER
When used with CARTO™ 3 EP Navigation System Version V8.1, the SOUNDSTART™ Crystal Ultrasound Catheter provides location information and is compatible with the legacy CARTO™ 3 CARTOSOUND™ SW and CARTOSOUND FAM LA Modules.
## 2 LEGACY FEATURES ENHANCEMENTS
Minor enhancement to the following legacy features:
1. Complex Signal Identification,
2. VISITAG Module Stability+,
3. Confidence Module,
4. Multipolar Mapping,
5. Qdot Micro support,
6. CARTOSOUND™ 4D, and
7. CARTOSOUND™ FAM LA.
4 of 5
{8}
Performance Data:
The CARTO™ 3 EP Navigation System V8.1 underwent verification and validation testing under simulated clinical conditions to verify the new features and to demonstrate with regression testing that the modifications performed did not negatively affect existing features.
Verification and Validation Testing
Software Verification and Validation testing completed for CARTO™ 3 System V8.1 included:
- Proof of Design – Testing was performed to verify the CARTO™ 3 System V8.1 design meets its accuracy specifications. All tests were successfully completed and met the acceptance criteria.
- Functional verification – Testing was performed to verify the functional requirements of CARTO™ 3 System V8.1, including testing of the new features and improvements as well as regression testing to verify continued functionality of CARTO™ 3 System legacy features. All system features were found to perform according to specifications and met the tests acceptance criteria.
- Unit Tests – Testing was performed to verify the design implementation in CARTO™ 3 V8.1 software aligns perfectly with the design specifications. All tests were successfully completed and met the acceptance criteria.
- Retrospective Validation Tests – Testing was performed to validate the clinical functionality and quality of the introduced modules. Testing was performed retrospectively, on clinical recorded data from historic EP procedures performed with the CARTO™ 3 System. All testing performed were successfully completed and met the acceptance criteria.
Animal Testing:
Animal testing was conducted to evaluate the CARTO™ 3 System V8.1 functionality under simulated clinical workflow and conditions. All test protocol steps were successfully completed and expected results were achieved.
All testing passed in accordance with appropriate test criteria, and the modified device did not raise new questions of safety or effectiveness.
Conclusions:
The CARTO™ 3 EP Navigation System V8.1 is substantially equivalent to the currently cleared CARTO™ 3 EP Navigation System with software version V8.0, based on the completion of verification and validation testing.
5 of 5
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.