FDA-cleared profile

Neuro.Al Algorithm

TeraRecon, Inc. · Radiological images; modality varies or is not specified in FDA list · FDA-cleared (510(k))

Authorized purpose: Neuro.Al Algorithm processes static, functional, dynamic, and derived CT or MR images to support brain perfusion analysis, tissue blood-volume and parametric-map review, ventricular visualization, and DICOM return to clinical viewers for trained professional interpretation.

Clinical role
Brain perfusion visualization, quantitative map review, and DICOM result delivery.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Brain and intracranial perfusion regions
Key limitation
Keep in mind: CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Neuro.Al Algorithm processes static, functional, dynamic, and derived CT or MR images to support brain perfusion analysis, tissue blood-volume and parametric-map review, ventricular visualization, and DICOM return to clinical viewers for trained professional interpretation.
  • Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Brain and intracranial perfusion regions Input: Supported CT or MR static, functional, dynamic, perfusion, and derived studies.
  • Who uses it?Intended users: Trained radiologists, neurologists, and other qualified physicians.
  • What does the software produce?Output: Perfusion maps, blood-volume views, reformats, overlays, and DICOM result series.
  • What is its most important limitation?Key limitation: CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.

Clinical takeaway. Clinical role: Neuro.Al Algorithm processes static, functional, dynamic, and derived CT or MR images to support brain perfusion analysis, tissue blood-volume and parametric-map review, ventricular visualization, and DICOM return to clinical viewers for trained professional interpretation.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software testing and performance evaluation of the Neuro.AI Algorithm, with software development and testing per IEC 62304:2006/A1:2015 using a risk-based testing methodology and risk evaluated per ISO 14971:2007; defined acceptance criteria were met and all software test cases passed. Results are as reported in the FDA submission, not independent validation.

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
Neuro.Al Algorithm processes static, functional, dynamic, and derived CT or MR images to support brain perfusion analysis, tissue blood-volume and parametric-map review, ventricular visualization, and DICOM return to clinical viewers for trained professional interpretation.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Brain perfusion visualization, quantitative map review, and DICOM result delivery.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported CT or MR static, functional, dynamic, perfusion, and derived studies.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Perfusion maps, blood-volume views, reformats, overlays, and DICOM result series.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Hospital neuroimaging and acute-care workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Trained radiologists, neurologists, and other qualified physicians.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports software testing and performance evaluation of the Neuro.AI Algorithm, with software development and testing per IEC 62304:2006/A1:2015 using a risk-based testing methodology and risk evaluated per ISO 14971:2007; defined acceptance criteria were met and all software test cases passed. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Safety and performance of the Neuro.AI Algorithm have been verified and validated through software testing and performance evaluation." … "Software development and testing were performed in accordance with IEC 62304:2006/A1:2015, Medical Device Software – Software life cycle processes, utilizing a risk-based testing methodology.". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

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 exact FDA document reports software testing and performance evaluation of the Neuro.AI Algorithm, with software development and testing per IEC 62304:2006/A1:2015 using a risk-based testing methodology and risk evaluated per ISO 14971:2007; defined acceptance criteria were met and all software test cases passed. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Safety and performance of the Neuro.AI Algorithm have been verified and validated through software testing and performance evaluation." … "Software development and testing were performed in accordance with IEC 62304:2006/A1:2015, Medical Device Software – Software life cycle processes, utilizing a risk-based testing methodology.". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.

Reported specificity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

K200750 FDA evidence package for Neuro.Al Algorithm

  • DesignFDA 510(k) or PMA decision evidence and product verification described in the exact submission.
  • PopulationBrain and intracranial perfusion regions
  • Scopeexact submission
  • Tested versionNeuro.Al Algorithm configuration described in K200750
  • IndependenceSponsor or vendor study

K200750

Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.

Safety and lifecycle

Postmarket record

Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.

Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K200750 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-04

Exact-identifier review does not prove absence of all product-family safety signals.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
  • Service-level, not product-specific
  • Checked 2026-09-04

No product-specific code

No separate named-product payment identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Supported CT or MR static, functional, dynamic, perfusion, and derived studies.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA 510(k) decision material K200750: Neuro.Al Algorithm

  2. Routing

    Source context, not route validation: The FDA package describes DICOM input and output for CT or MR studies.

    Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-04 · FDA 510(k) decision material K200750: Neuro.Al Algorithm

  3. AI processing

    Source context, not route validation: The FDA package describes standalone Windows, container, and cloud deployment options; the configured mode, hosting, security, and service boundary remain unverified.

    Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-04 · FDA 510(k) decision material K200750: Neuro.Al Algorithm

  4. Returned objects

    Source context, not route validation: Perfusion maps, blood-volume views, reformats, overlays, and DICOM result series.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA 510(k) decision material K200750: Neuro.Al Algorithm

  5. Viewer/worklist/report

    Unresolved route: Perfusion maps, blood-volume views, reformats, overlays, and DICOM result series.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K200750: Neuro.Al Algorithm

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The FDA package describes standalone Windows, container, and cloud deployment options; the configured mode, hosting, security, and service boundary remain unverified.
  • Exact FDA submission
  • Checked 2026-09-04

This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.

Integration
The FDA package describes DICOM input and output for CT or MR studies.
  • Exact FDA submission
  • Checked 2026-09-04

This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

Security
TeraRecon announces it has been recognized as an ISO 27001:2022 certified company, maintaining an information security management system with documented processes for managing sensitive company information, HR processes, and IT systems; the announcement names TeraRecon's Intuition product and Eureka Clinical AI platform.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement; the certificate was not read (a certificate PDF is hosted on the same owning domain). Applicant name variants (TeraRecon Inc. with punctuation/case variants) are bridged via the identical distinctive name. Exact-release scope is not established.

Training
Only trained radiologists, neurologists, and other qualified physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K200750 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.
  • Exact FDA submission
  • Checked 2026-09-04

Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K200750 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared release includes them.

Deployment boundary

The FDA package describes standalone Windows, container, and cloud deployment options; the configured mode, hosting, security, and service boundary remain unverified.

exact submission · checked 2026-09-04

FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.

Interoperability acceptance

The FDA package describes DICOM input and output for CT or MR studies.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.

product family · checked 2026-09-04

No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.

Lifecycle monitoring

Monitor K200750 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: CT or MR acquisition, perfusion timing, image quality, and trained-professional review limits apply; the output does not replace physician interpretation.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. brain CT and MR perfusion software limits remain submission-specific.

Sources & review details FDA 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.

FDA submission
K200750
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Radiological images; modality varies or is not specified in FDA list
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Brain and intracranial perfusion regions
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-11-06
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Human reviewedStatus
2026-09-20Last searched
27Fields reviewed
13Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, 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 publicly available - checked 2026-09-04 - Exact FDA submission

    No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.

  • 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
  • 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
  • Installation timeline: Not yet reviewed

8 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K200750: Neuro.Al Algorithm

    U.S. Food and Drug Administration - Published 2020-11-06 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. Neuro.Al Algorithm model card (K200750)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  8. TeraRecon: ISO 27001:2022 Certification Announcement

    TeraRecon - Published 2023-05-30 - Accessed 2026-10-27

    Scope: security

Research history

  1. K200750 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K250831

Annalise Enterprise

Annalise-AI

Authorized purpose: Triage and prioritization of adult CXR and non-contrast brain CT studies for specified suspected findings, including pneumoperitoneum, pleural effusion, pneumothorax and tension pneumothorax on CXR, and acute extra-axial hemorrhage, subarachnoid hemorrhage, intra-axial hemorrhage, intraventricular hemorrhage, mass effect, obstructive hydrocephalus and vasogenic edema on brain CT.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Chest/Lung; Brain
Decision
2025-04-23
FDA-cleared K233582

Rapid

iSchema View Inc.

Authorized purpose: Rapid is image-viewing, processing, and analysis software for DICOM CT, CT perfusion, CT angiography, C-arm CT perfusion, and MRI data, including perfusion maps and acute-stroke selection support under the labeled occlusion and imaging criteria.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Brain, cerebral vasculature, and perfusion regions
Decision
2024-04-22
FDA-cleared K233512

Rapid (6.0)

iSchemaView, Inc.

Authorized purpose: Rapid Platform v6.0 is image-processing software for trained professionals that views, processes, and analyzes DICOM images from CT and MRI. It supports functional and dynamic datasets including CT perfusion, CT angiography, diffusion-weighted MRI, and dynamic contrast-enhanced CT or MRI, with maps and measurements for tissue perfusion, diffusion, and blood volume. Rapid CT-Perfusion and Rapid MR-Perfusion may aid physicians in selecting acute stroke patients with known occlusion of the intracranial internal carotid artery or proximal middle cerebral artery for endovascular thrombectomy, subject to the labeled imaging criteria, clinical requirements, and exclusions.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Brain and intracranial vessels represented in CT perfusion, CTA, and MRI; tissue perfusion, diffusion, and contrast dynamics
Decision
2024-01-16
FDA-cleared K213165

Rapid

iSchema View Inc.

Authorized purpose: Rapid processes CT, CTP, CTA, diffusion MRI, and dynamic-contrast MRI for stroke viewing, perfusion, volumetry, mismatch, and large-vessel-density support for trained professionals.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Brain
Decision
2022-02-08

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history