Ensembles of deep learning models including CNN and U-net
—
—
—
—
Clinical performance validation: sample of diverse accelerated scans (pathological and non-pathological brains)
>1 (radiologists)
Indications for Use
DeepFoqus-Accelerate is a stand-alone software solution intended to be used for acceptance, enhancement, and transfer of brain MRI images in DICOM format. It can be used for reconstruction of non-contrast enhanced MRI images acquired with 1.5T or 3T Siemens and GE scanners using Sagittal, Axial, or Coronal T1, T2, or FLAIR sequences. DeepFoqus-Accelerate is intended to be used on adult scans only and not intended for use on mobile devices.
Device Story
DeepFoqus-Accelerate is AI-powered software for reconstructing accelerated (up to 4x) brain MRI scans. Input: k-space and DICOM files from 1.5T/3T Siemens/GE scanners. Operation: software pipeline ingests undersampled data, applies ensemble of deep learning models (CNN/U-net architectures) to reconstruct clinical-quality images, and performs post-processing (windowing/resizing). Output: reconstructed DICOM images. Used in clinical settings by radiology technologists to process scans for radiologist review. Benefits: enables faster scan acquisition while maintaining image quality comparable to standard unaccelerated scans.
Clinical Evidence
No clinical trials; evidence based on analytical performance validation and clinician review. Metrics included SSIM, PSNR, and HaarPSI. Phantom testing followed ACR MRI Accreditation Program guidance. Clinical performance validation involved radiologists reviewing diverse accelerated scans (pathological/non-pathological) against ground truth. User acceptance testing and summative evaluation confirmed software usability.
Technological Characteristics
Stand-alone software; AI-based reconstruction using ensemble CNN/U-net models. Inputs: HDF5/DICOM. Outputs: DICOM. Standards: ISO 14971:2019, IEC 62366-1:2015, IEC 62304:2006, NEMA PS 3.1-3.20, ISO 15223-1, AAMI TIR 57/97, AAMI SW96:2023. No direct hardware interface.
Indications for Use
Indicated for adult patients undergoing non-contrast enhanced brain MRI (T1, T2, or FLAIR sequences) on 1.5T or 3T Siemens and GE scanners. Not for use on mobile devices.
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}
FDA U.S. FOOD & DRUG ADMINISTRATION
April 4, 2025
Foqus Technologies Inc.
Sadegh Raeisi
Official Correspondent
The Tannery, 151 Charles St W Suite# 199
Kitchener, ON N2G1H6
Canada
Re: K241982
Trade/Device Name: DeepFoqus (DeepFoqus-Accelerate)
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: QIH
Dated: February 28, 2025
Received: March 3, 2025
Dear Sadegh Raeisi:
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}
K241982 - Sadegh Raeisi
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}
K241982 - Sadegh Raeisi
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,

Daniel M. Krainak, PhD
Assistant Director
DHT8C: Division of Radiological
Imaging and Radiation Therapy Devices
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740
EF
| 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. |
| --- | --- |
| 510(k) Number (if known) K241982 | |
| Device Name DeepFoqus (DeepFoqus-Accelerate) | |
| Indications for Use (Describe) DeepFoqus-Accelerate is a stand-alone software solution intended to be used for acceptance, enhancement, and transfer of brain MRI images in DICOM format. It can be used for reconstruction of non-contrast enhanced MRI images acquired with 1.5T or 3T Siemens and GE scanners using Sagittal, Axial, or Coronal T1, T2, or FLAIR sequences. DeepFoqus-Accelerate is intended to be used on adult scans only and not intended for use on mobile devices. | |
| Type of Use (Select one or both, as applicable) ☑ 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}
FOCUS
510(k) #: K241982
Prepared on: 2025-04-04
## 1.0 Contact Details
21 CFR 807.92(a)(1)
| Applicant Name | Foqus Technologies Inc. |
| --- | --- |
| Applicant Address | The Tannery, 151 Charles St W Suite# 199 Kitchener ON N2G1H6 Canada |
| Applicant Contact Telephone | 647-4254787 |
| Applicant Contact | Mr. Sadegh Raeisi |
| Applicant Contact Email | sadegh.raeisi@foqus.ca |
## 2.0 Device Name
21 CFR 807.92(a)(2)
| Device Trade Name | DeepFoqus (DeepFoqus-Accelerate) |
| --- | --- |
| Common Name | Medical image management and processing system |
| Classification Name | Automated Radiological Image Processing Software |
| Regulation Number | 892.2050 |
| Product Code(s) | QIH |
## 3.0 Legally Marketed Predicate Devices
21 CFR 807.92(a)(3)
| Predicate # | Predicate Trade Name (Primary Predicate is listed first) | Product Code |
| --- | --- | --- |
| K210999 | SwiftMR | LLZ |
## 4.0 Device Description Summary
21 CFR 807.92(a)(4)
DeepFoqus-Accelerate is an AI-powered MRI software that accepts up to 4x accelerated scans and reconstructs them to yield acceptable scans when compared to standard unaccelerated scans.
DeepFoqus allows input of HDF5 and DICOM files, acquired with common MRI machines, containing accelerated T1, T2, and FLAIR image sets. Once inputted, DeepFoqus performs a series of reconstruction steps to produce clinical-quality scans from the undersampled data in the phase encoding direction.
Page 1 of 4
{5}
Page 2 of 4
# FOCUS
DeepFoqus-Accelerate uses AI and machine learning models to reconstruct MRI images from up to 4x accelerated MRI scans. The models combine various signal processing and machine learning techniques including several convolutional neural network (CNN) and U-net architecture models.
The full pipeline involves the following steps:
1. Ingestion of MRI scans as k-space and DICOM files.
2. Preprocessing steps to ensure that the input is in a standard format and meets acquisition requirements.
3. Processing through a pipeline that combines a collection of machine learning and signal processing modules that ensures that an appropriate range of fine-tuned models is applied to reconstruct a final volume.
4. Post-processing steps which include adjustments for windowing and image size.
5. Conversion of the final volume to DICOM format.
The overall pipeline has been trained to minimize the distance between reconstructed final images and standard accelerated scans. Training has been conducted on a range of datasets which include diverse magnet strengths, sequences, manufacturers, and image orientations.
The software provides a workflow for an MRI/Radiology Technologist to:
1. Input undersampled data into the software through a user interface
2. Start a processing pipeline and observe progress
3. Export reconstructed data for use in downstream applications
## 5.0 Intended Use/Indications for Use
**21 CFR 807.92(a)(5)**
DeepFoqus-Accelerate is a stand-alone software solution intended to be used for acceptance, enhancement, and transfer of brain MRI images in DICOM format. It can be used for reconstruction of non-contrast enhanced MRI images acquired with 1.5T or 3T Siemens and GE scanners using Sagittal, Axial, or Coronal T1, T2, or FLAIR sequences.
DeepFoqus-Accelerate is intended to be used on adult scans only and not intended for use on mobile devices.
## 6.0 Indications for Use Comparison
**21 CFR 807.92(a)(5)**
The indications for use for the predicate device and the subject device are the same.
## 7.0 Technological Comparison
**21 CFR 807.92(a)(6)**
DeepFoqus-Accelerate is substantially equivalent to AIRS Medical SwiftMR (K210999).
Both the Subject and Predicate devices are similar in terms of technology and intended use. Both software systems contain deep learning algorithms which produce automatic images quality enhancement. Both devices are only intended to be used for professional purposes and are not intended for use on mobile devices. The workflow between the two systems is the same:
* MR images are uploaded into the software
{6}
Page 3 of 4
# FOCUS
* The software uses a deep learning model to enhance the images
* The images can be downloaded in DICOM format from the software
Neither software product directly interfaces with the MRI or other data collection equipment.
The primary difference between the Predicate and Subject device is the reconstruction/enhancement algorithm. The Predicate implements an image enhancement algorithm using convolutional neural network-based filtering. The Subject implements an image reconstruction algorithm using ensembles of deep learning models. Ensembling aggregates several model architectures in order to produce a single reconstruction of accelerated image data.
This difference was verified and validated using the following methods:
* Performance and comparison evaluations (PSNR, HaarPSI, SSIM)
* Phantom Bench testing (geometric accuracy, intensity uniformity, percentage ghosting, signal-to-noise ratio, resolution, and low-contrast detectability)
* Artifact assessment (quantitative (SSIM) and qualitative assessment of images which are expected to have artifacts)
* Clinician evaluation (reconstruction quality score)
The essential underlying device outputs and use are the same. The intended uses are equivalent. Direct comparison of major functionality was possible and showed largely identical results.
The above comparison to the Predicate device in conjunction with the design verification and validation activities described in this 510(k) submission support substantial equivalence of SwiftMR.
# 8.0 Non-Clinical and/or Clinical Tests Summary & Conclusions 21 CFR 807.92(b)
Software verification, validation, and standards compliance were all relied on in the determination of substantial equivalence.
Standards Compliance
The subject device is in conformity with the requirements of the following:
* ISO 14971:2019
* IEC 62366-1:2015+AMD1:2020
* IEC 62304:2006/A1:2016
* NEMA PS 3.1-3.20 2022d
* ISO 15223-1 (2021)
* AAMI TIR 57:2016
* AAMI TIR 97:2019
* AAMI SW96:2023
{7}
Page 4 of 4
# FOCUS
## Software Verification
The following types of verification were performed, all testing met acceptance criteria.
* Software code review
* Static code analysis
* Unit verification
* SOUP verification
* Architecture and software requirements reviews
* Software functional verification
* Penetration testing, secure code review, and dependency vulnerability scanning
## Software Validation
The following types of validation were performed, all testing met acceptance criteria.
* Analytical performance validation - Three specific metrics were used to demonstrate acceptable performance and equivalence with the predicate device - Structural Similarity Index Measure (SSIM), Peak Signal to Noise Ratio (PSNR), Haar wavelet-based perceptual similarity index and (HaarPSI)
* Phantom bench testing - Done to ensure that the reconstruction algorithm meets the necessary quality standards according to "Large and Medium Phantom Test Guidance for the ACR MRI Accreditation Program".
* Artifact assessment - Conducted to demonstrate the robustness of the AI-based DeepFoqus-Accelerate reconstruction against common MRI artifacts, ensuring that no additional reconstruction errors are introduced.
* Clinical performance validation - Radiologists reviewed a sample of diverse accelerated scans (including pathological and non-pathological brains) to determine whether the accelerated scans were equivalent to the ground truth.
* User acceptance testing and summative evaluation - Radiology technologists, IT administrators, and radiologists reviewed critical tasks inherent in the software and user requirements for acceptability.
The design verifications conducted support the conclusion that DeepFoqus-Accelerate performs as intended. The design validation, along with comparison and performance evaluations, support the conclusion that DeepFoqus-Accelerate performs comparably to the predicate device that is currently marketed for the same intended use.
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.