Authorized purpose: ANDI processes diffusion-weighted MRI with auxiliary T1 imaging to create 3D white-matter tract maps and microstructure reports for trained medical professionals as adjunctive measurement information, not diagnosis.
Clinical role
Diffusion MRI tractography, white-matter microstructure measurement, and adjunctive visualization support
Images and patients
MRI · Brain
Key limitation
Keep in mind: ANDI measures white-matter tracts only and does not predict, diagnose, or interpret brain health; it is adjunctive and not a diagnostic aid. A physician must review all clinical information. The exact packet distinguishes NIfTI/API input from DICOM-compliant report output, so local interface compatibility requires confirmation.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: ANDI processes diffusion-weighted MRI with auxiliary T1 imaging to create 3D white-matter tract maps and microstructure reports for trained medical professionals as adjunctive measurement information, not diagnosis.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Brain Input: Diffusion-weighted MRI with T1-weighted images as auxiliary input; the exact comparison describes NIfTI image input and an API-based interface, with reversed-phase-encoded B=0 as an optional input. The exact acquisition protocol was not established.
Who uses it?Intended users: Medical professionals, including neurologists and radiologists; trained professionals make the final decision.
What does the software produce?Output: 3D white-matter tract maps and a CSD-based microstructure report providing reference information for comparison with a control population and, optionally, longitudinal comparison; the subject device output is a DICOM encapsulated PDF report supported by RIS/PACS.
What is its most important limitation?Key limitation: ANDI measures white-matter tracts only and does not predict, diagnose, or interpret brain health; it is adjunctive and not a diagnostic aid. A physician must review all clinical information. The exact packet distinguishes NIfTI/API input from DICOM-compliant report output, so local interface compatibility requires confirmation.
Clinical takeaway. Clinical role: ANDI processes diffusion-weighted MRI with auxiliary T1 imaging to create 3D white-matter tract maps and microstructure reports for trained medical professionals as adjunctive measurement information, not diagnosis.
Evidence takeaway. Evidence from the reviewed source record: The FDA describes non-clinical performance testing of measured endpoints, AI brain extraction, processing-pipeline robustness, and report content/structure; it states that no clinical studies were considered necessary or performed.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
ANDI processes diffusion-weighted MRI with auxiliary T1 imaging to create 3D white-matter tract maps and microstructure reports for trained medical professionals as adjunctive measurement information, not diagnosis.
Diffusion-weighted MRI with T1-weighted images as auxiliary input; the exact comparison describes NIfTI image input and an API-based interface, with reversed-phase-encoded B=0 as an optional input. The exact acquisition protocol was not established.
3D white-matter tract maps and a CSD-based microstructure report providing reference information for comparison with a control population and, optionally, longitudinal comparison; the subject device output is a DICOM encapsulated PDF report supported by RIS/PACS.
Clinical neuroimaging for trained medical professionals such as neurologists and radiologists; the output is adjunctive to standard-of-care evaluation.
ANDI measures white-matter tracts only and does not predict, diagnose, or interpret brain health; it is adjunctive and not a diagnostic aid. A physician must review all clinical information. The exact packet distinguishes NIfTI/API input from DICOM-compliant report output, so local interface compatibility requires confirmation.
The FDA describes non-clinical performance testing of measured endpoints, AI brain extraction, processing-pipeline robustness, and report content/structure; it states that no clinical studies were considered necessary or performed.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
The FDA describes non-clinical performance testing of measured endpoints, AI brain extraction, processing-pipeline robustness, and report content/structure; it states that no clinical studies were considered necessary or performed.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
ANDI non-clinical performance and report validation
DesignNon-clinical software performance, robustness, and report-structure validation
PopulationPredefined software test protocols covering measured endpoints, AI brain extraction, processing-pipeline robustness, and a summative report evaluation; sample counts were not stated in the reviewed summary.
Scopeexact submission
Tested versionANDI submitted in K230913; build not stated
IndependenceIndependence not established
K230913
The FDA states that no clinical studies were considered necessary or performed. No independent investigators or sponsorship were established.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: Diffusion-weighted MRI with T1-weighted images as auxiliary input; the exact comparison describes NIfTI image input and an API-based interface, with reversed-phase-encoded B=0 as an optional input. The exact acquisition protocol was not established.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact submission describes API-based image input and report output, NIfTI input, and DICOM encapsulated PDF output supported by RIS/PACS; this is not evidence that the subject device accepts DICOM images directly as input.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Cloud-based image-processing software
Scope: Exact FDA submission. The FDA comparison describes both subject and predicate as cloud-based; current hosting region, retention, and data-flow controls were not separately established.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: 3D white-matter tract maps and a CSD-based microstructure report providing reference information for comparison with a control population and, optionally, longitudinal comparison; the subject device output is a DICOM encapsulated PDF report supported by RIS/PACS.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: 3D white-matter tract maps and a CSD-based microstructure report providing reference information for comparison with a control population and, optionally, longitudinal comparison; the subject device output is a DICOM encapsulated PDF report supported by RIS/PACS.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
The FDA comparison describes both subject and predicate as cloud-based; current hosting region, retention, and data-flow controls were not separately established.
The exact submission describes API-based image input and report output, NIfTI input, and DICOM encapsulated PDF output supported by RIS/PACS; this is not evidence that the subject device accepts DICOM images directly as input.
Imeka's official ANDI page describes a current family workflow from raw diffusion data to a quantitative report, including automated tract analysis, normative comparisons, longitudinal views, and a secure cloud environment; this current family description is not promoted to exact K230913 version performance or security evidence.
product family · checked 2026-09-07
Current family page context only; exact-version and local interface compatibility require confirmation.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-07Last searched
24Fields reviewed
10Source classes checked
20Screened PubMed leads
10Screened trial leads
0Unreviewed FDA recall leads
The stored PubMed, ClinicalTrials.gov, and exact-submission recall metadata candidates were screened by identifier and count. The records were not treated as a full paper, trial, or postmarket review. The current discovery snapshot contains 20 PubMed and 10 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, vendor product page, literature index, trial registry, fda device recall, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not verified - checked 2026-09-07 - Exact FDA submission
No public amount, range, currency, geography, or contract term was established.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Reimbursement: Not publicly available - checked 2026-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "Imeka ANDI reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. Only trade press (BioWorld, 2023-08-24) mentions new CPT Category III codes for quantitative brain MRI; no vendor or payer page names a code for this product. This records what was found, not that none exists; eligibility depends on payer, site of service and use case.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Security: Not verified - checked 2026-09-07 - Exact FDA submission
The reviewed sources do not establish a scoped security audit, certification, or control set.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-07 - Exact FDA submission
Training, credentialing, and implementation support terms were not established.
Monitoring: Not verified - checked 2026-09-07 - Exact FDA submission
Current post-deployment monitoring and change-control practices were not established.
Authorized purpose: ANDI 2.2 processes brain MR images for atlas-assisted visualization, segmentation and volumetric quantification, presenting adjunctive DICOM-readable information for trained medical professionals; it does not predict, diagnose or interpret brain health.
Authorized purpose: Morph automatically labels, visualizes, and volumetrically quantifies segmentable brain structures from MR images and may compare measurements with reference percentile data; it is adjunctive and not the sole basis for final decisions.
Authorized purpose: Brain MRI morphometry and white matter hyperintensity quantification, including normative comparison and longitudinal change assessment for clinician review.
Authorized purpose: Adjunctive quantitative brain MRI analysis that compares patient measures with normative and longitudinal references; a physician reviews all results and makes the clinical decision.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.