Mimics Cardiac Planner is intended to be used as a pre-procedural planning software to screen and plan structural heart and vascular procedures based on DICOM compliant medical images. Mimics Cardiac Planner allows the clinician to visualize, measure, annotate and edit pre-procedural plan data. The software can be used to evaluate the sizing, positioning and delivery pathway of structural heart and vascular devices. Mimics Cardiac Planner should be used in conjunction with other diagnostic tools and expert clinical judgement.
Device Story
Mimics Cardiac Planner is cloud-based pre-procedural planning software for structural heart and vascular procedures. Input: DICOM medical images, 3D anatomical models, and landmarks (generated via Materialise service). Operation: software guides clinicians through workflow steps—analyzing anatomy, planning device placement, assessing delivery pathways, and preparing fluoroscopy angles. Output: visualized 3D models, measurements, annotations, and edited pre-procedural plan data. Used in clinical settings by physicians to evaluate device sizing and positioning. Output assists clinical decision-making by providing a virtual environment to simulate and refine procedural strategy. Benefits: improved pre-procedural planning accuracy and procedural preparation.
Clinical Evidence
No clinical data. Performance established via bench testing, including software verification against defined requirements and validation against user needs, following FDA guidance for device software functions.
Technological Characteristics
Cloud-based software integrated with a Medical Device Data System. Utilizes Materialise C++ code libraries. Features include 3D model visualization, measurement tools, and device library management. Software architecture is cloud-hosted, differing from the desktop-based predicate. Verification performed via standard software development lifecycle procedures.
Indications for Use
Indicated for clinicians to screen and plan structural heart and vascular procedures using DICOM medical images. Used to evaluate device sizing, positioning, and delivery pathways. Not for primary diagnosis; must be used with other diagnostic tools and clinical judgment.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{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 Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
Materialise N.V. Victoria Becheva Regulatory Affairs Specialist Technologielaan 15 Leuven, 3001 BELGIUM
February 12, 2024
# Re: K233217
Trade/Device Name: Mimics Cardiac Planner Regulation Number: 21 CFR 892.2050 Regulation Name: Medical Image Management And Processing System Regulatory Class: Class II Product Code: LLZ Dated: January 12, 2024 Received: January 12, 2024
Dear Victoria Becheva:
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.
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).
{1}------------------------------------------------
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 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-reportingcombination-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.
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-device-safety/medical-device-reportingmdr-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/medicaldevices/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-device-advice-comprehensive-regulatoryassistance/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.
Jessica Lamb
Jessica Lamb, Ph.D. Assistant Director DHT8B: Division of Radiological Imaging Devices and Electronic Products OHT8: Office of Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K233217
Device Name Mimics Cardiac Planner
#### Indications for Use (Describe)
Mimics Cardiac Planner is intended to be used as a pre-procedural planning software to screen and plan structural heart and vascular procedures based on DICOM compliant medical images. Mimics Cardiac Planner allows the clinician to visualize, measure, annotate and edit pre-procedural plan data. The software can be used to evaluate the sizing, positioning and delivery pathway of structural heart and vascular devices.
Mimics Cardiac Planner should be used in conjunction with other diagnostic tools and expert clinical judgement.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| <div style="display:flex; align-items:center;"><span style="font-size: 20px;">☑</span> Prescription Use (Part 21 CFR 801 Subpart D)</div> | <div style="display:flex; align-items:center;"><span style="font-size: 20px;">☐</span> Over-The-Counter Use (21 CFR 801 Subpart C)</div> |
# CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
# *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# K233217 510(k) Summary
The following section is included as required by the Safe Medical Devices Act (SMDA) of 1990 and 21CFR 807.92.
| Company name | Materialise N.V. |
|-----------------------------------|----------------------------------------------|
| Establishment registration number | 3003998208 |
| Street Address | Technologielaan 15 |
| City | Leuven |
| Postal code | 3001 |
| Country | Belgium |
| Phone number | +32 16 39 66 11 |
| Fax number | +32 16 39 66 06 |
| Principal Contact person | Victoria Becheva |
| Contact title | Regulatory Affairs Specialist |
| Contact e-mail address | Regulatory. Affairs@materialise.be |
| Additional contact person | Jenny Jones |
| Contact title | Global Quality & Regulatory Manager, Medical |
| Contact e-mail address | jenny.jones@materialise.com |
# Submission date
The date of the Traditional 510(k) submission is September 25, 2023.
# Submission information
| Trade Name | Mimics Cardiac Planner |
|---------------------|---------------------------------------------------------------------|
| Common Name | Image processing system |
| Classification Name | System, Image processing, Radiological |
| Regulation | 21 CFR 892.2050 (Medical image management and<br>processing system) |
| Product code | LLZ |
#### Indications for Use
Mimics Cardiac Planner is intended to be used as a pre-procedural planning software to screen and plan structural heart and vascular procedures based on DICOM compliant medical images. Mimics Cardiac Planner allows the
{4}------------------------------------------------
clinician to visualize, measure, annotate and edit pre-procedural plan data. The software can be used to evaluate the sizing, positioning and delivery pathway of structural heart and vascular devices.
Mimics Cardiac Planner should be used in conjunction with other diagnostic tools and expert clinical judgement.
#### Description and functioning of the device
The Mimics Cardiac Planner is an online planning software, which allows the clinician to review and adjust a plan for a structural heart or vascular procedures based on DICOM images, 3D models and landmarks. The software guides the clinician through different steps of the cardio-vascular workflow, where the relevant information, like 3D models of anatomy and devices, images, landmarks and measurements are presented.
The software enables the clinician to review the anatomy and relevant workflow specific predefined set of measurements, evaluate the device size and position, assess the delivery pathway and prepare the fluoroscopy angles for the procedure.
The software provides the tools to adjust all predefined measurements, and to perform custom measurements.
The software is integrated with a Medical Device Data System, which is responsible for the case management and user management.
#### Predicate Devices
The primary predicate device to which substantial equivalence is claimed:
| Trade or proprietary or model name | Mimics Enlight |
|------------------------------------|------------------|
| 510(k) number | K190874 |
| Decision date | 06/05/2019 |
| Classification product code | LLZ |
| Manufacturer | Materialise N.V. |
The reference device:
| Trade or proprietary or model name | SurgiCase Shoulder Planner |
|------------------------------------|----------------------------|
| 510(k) number | K220452 |
| Decision date | 08/17/2022 |
{5}------------------------------------------------
| Classification product code | QHE, KWS, PHX |
|-----------------------------|------------------|
| Manufacturer | Materialise N.V. |
# Technological Characteristics
#### Comparison of technological characteristics with the predicate device (Mimics Enlight, K190874).
The subject device Mimics Cardiac Planner employs similar fundamental technologies as Mimics Enlight.
Technological similarities include:
- . Device Functionality: Both subject and predicate devices consist of a workflow to plan structural heart and vascular procedures which follows the same structure of steps which enable the procedure:
- Analyze anatomy
- Plan device
- Plan delivery
- Output ●
To perform these steps the software provides similar methods and tools to visualize, and measure based on the medical images and 3D models.
- Virtual 3D models used during planning: The geometric accuracy of the virtual models used in the subject device is the same as in the predicate device.
- Software technology: Both subject and predicate device are developed using the same underlying Materialise C++ code libraries.
- Device design and development process: Both predicate and subject device software are manufactured by the same company (Materialise NV), the subject device follows the same development cycle and testing procedures as the predicate device. The verification of predicate and subject device has been done following the same procedures and workflows.
The following technological differences exist between the subject device and the predicate device:
- . Device Functionality: Both devices require medical images as input. However, the provides segmentation and landmarking tools to create 3D models and landmarks, while the subject device also requires the input of 3D models and landmarks which is generated through a service delivered by Materialise.
- Software technology: while the predicate device is a desktop Windows software which is run locally on a computer of the clinician, the subject device is cloud software integrated with a medical device data system.
# Comparison of technological characteristics with the reference device (SurgiCase Shoulder Planner, K220452)
The subject device Mimics Cardiac Planner employs similar fundamental technologies as SurgiCase Shoulder
Planner. Technological similarities include:
{6}------------------------------------------------
- . Device functionality: much of the software functionality is shared between the subject and reference device, such as visualization of 3D models, images visualization, measurement tools, handling device libraries, positioning devices.
- . Process in which the software is used: The input for both devices is uploaded on Medical Device Data system where segmentation and landmarking is performed through a service delivered by Materialise.
- Software technology: both devices are based on the same cloud technology and are integrated with the same Medical Device Data System.
The following technological differences exist between the subject device and the reference device:
- Device functionality: While from a feature perspective the tools in the software are very similar, they are applied to a different field (Cardiac vs Orthopedic). Additionally, the reference device generates a presurgical plan data file which can be used as input data to design shoulder guides and models, while the subject device does not currently generate such output.
Following the comparison between the subject and predicate device, and between subject and reference device, it can be concluded that the abovementioned technological differences between the subject and predicate device do not impact the safety and effectiveness of the subject device for the proposed indications for use as they are covered using a reference device with matching characteristics in the subject device differs from the predicate, as well as by verification and validation.
# Performance Data
Software verification and validation were performed, and documentation was provided following the FDA guidance "Content of Premarket Submissions for Device Software Functions." This includes verification against defined requirements, and validation against user needs.
#### Summary
The characteristics that determine the functionality and performance of the subject device Mimics Cardiac Planner is substantially equivalent to the device cleared under Mimics Enlight (K190874), the primary predicate device. The non-clinical performance testing indicates that the subject device is as safe and effective as the predicate device. Therefore, it can be concluded that the Mimics Cardiac Planner is substantially equivalent to the predicate device.
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.