Authorized purpose: Analyzes functional, dynamic, and derived CT or MRI datasets for brain perfusion, vascular assessment, tissue blood volume, and related parametric maps to assist physician diagnosis.
Clinical role
Software that applies motion correction and calculates brain perfusion analysis results from dynamic CT or MRI datasets, delivering DICOM results to image viewing systems such as PACS to assist the physician in diagnosis.
Images and patients
CT/CTA; MRI · Brain
Key limitation
Keep in mind: Use by trained users; physician judgment and final patient-management decisions remain required; CT-only restriction applies to Tmax, mismatch, and hypoperfusion maps.
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: Analyzes functional, dynamic, and derived CT or MRI datasets for brain perfusion, vascular assessment, tissue blood volume, and related parametric maps to assist physician diagnosis.
Which images or clinical context are in scope?Modality: CT/CTA; MRI Anatomy or clinical context: Brain Input: Functional, dynamic, and derived CT/MRI image data, including dynamic brain-perfusion data, acquired via DICOM-compliant imaging devices.
Who uses it?Intended users: Trained professionals, including physicians, surgeons, and medical clinicians.
What does the software produce?Output: Perfusion parameter maps (TTP, TOT, RT, MTT, BV/CBV, BF/CBF, Tmax), mismatch/hypoperfusion maps with volumes and ratios, and 2D/3D brain and vessel visualization; Tmax, mismatch, and hypoperfusion maps are CT-only.
What is its most important limitation?Key limitation: Use by trained users; physician judgment and final patient-management decisions remain required; CT-only restriction applies to Tmax, mismatch, and hypoperfusion maps.
Clinical takeaway. Clinical role: Analyzes functional, dynamic, and derived CT or MRI datasets for brain perfusion, vascular assessment, tissue blood volume, and related parametric maps to assist physician diagnosis.
Evidence takeaway. Evidence from the reviewed source record: FDA reports software testing, quantitative phantom testing, qualitative clinical user evaluation, and quantitative Tmax comparison; sample size and sensitivity/specificity are not reported.
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
Analyzes functional, dynamic, and derived CT or MRI datasets for brain perfusion, vascular assessment, tissue blood volume, and related parametric maps to assist physician diagnosis.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Software that applies motion correction and calculates brain perfusion analysis results from dynamic CT or MRI datasets, delivering DICOM results to image viewing systems such as PACS to assist the physician in diagnosis.
Exact FDA submission
Checked 2026-11-14
Packet wording: "TeraRecon Neuro allows motion correction and processes, calculates and outputs brain perfusion analysis results for functional, dynamic, and derived imaging datasets acquired with CT or MRI." … "or other image viewing systems like PACS that can support DICOM results generated by the TeraRecon Neuro Algorithm.". Read from the exact FDA decision document on 2026-11-14.
Perfusion parameter maps (TTP, TOT, RT, MTT, BV/CBV, BF/CBF, Tmax), mismatch/hypoperfusion maps with volumes and ratios, and 2D/3D brain and vessel visualization; Tmax, mismatch, and hypoperfusion maps are CT-only.
Use by trained users; physician judgment and final patient-management decisions remain required; CT-only restriction applies to Tmax, mismatch, and hypoperfusion maps.
Exact FDA submission
Checked 2026-09-19
FDA-labeled use boundary; no broader performance or deployment claim is made.
FDA reports software testing, quantitative phantom testing, qualitative clinical user evaluation, and quantitative Tmax comparison; sample size and sensitivity/specificity are not reported.
Exact FDA submission
Checked 2026-09-19
Submission-reported FDA evidence summary, not independent validation.
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
FDA reports software testing, quantitative phantom testing, qualitative clinical user evaluation, and quantitative Tmax comparison; sample size and sensitivity/specificity are not reported.
FDA source
Exact FDA submission
Checked 2026-09-19
Submission-reported FDA evidence summary, not independent validation.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
TeraRecon Neuro regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K220349
IndependenceIndependence not established
K220349
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K220349. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: Functional, dynamic, and derived CT/MRI image data, including dynamic brain-perfusion data, acquired via DICOM-compliant imaging devices.
Scope: Exact FDA submission. FDA input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Perfusion parameter maps (TTP, TOT, RT, MTT, BV/CBV, BF/CBF, Tmax), mismatch/hypoperfusion maps with volumes and ratios, and 2D/3D brain and vessel visualization; Tmax, mismatch, and hypoperfusion maps are CT-only.
Scope: Exact FDA submission. FDA output description.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Perfusion parameter maps (TTP, TOT, RT, MTT, BV/CBV, BF/CBF, Tmax), mismatch/hypoperfusion maps with volumes and ratios, and 2D/3D brain and vessel visualization; Tmax, mismatch, and hypoperfusion maps are CT-only.
Scope: Exact FDA submission. FDA output description.
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.
Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-09-01
Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
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.
Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
ACR AI Central provides an exact-submission model card for TeraRecon Neuro; FDA labeling remains controlling for clinical use, limitations, and performance.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
24Fields reviewed
10Source 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 device recall, literature index, trial registry, fda decision summary packet, 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.
Care setting: Not yet reviewed - checked 2026-08-31 - Exact FDA submission
Confirm the intended care setting, patient population, and service line.
Public pricing: Not verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K220349 configuration was established in this review.
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-09-09 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by 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
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: View, post-process, and qualitatively and quantitatively evaluate cardiovascular MR and CT images in DICOM format to obtain diagnostic information as part of a comprehensive diagnostic decision-making process.
Modality
CT/CTA; MRI
Anatomy
Cardiovascular system; heart, coronary and adjacent vessels, and cardiac valves
Authorized purpose: Create, review, analyze, annotate, export, and use 3D cardiac models to support reading, reporting, and therapeutic-intervention planning.
Modality
CT/CTA; MRI
Anatomy
Cardiac structures, including the aorta, atria, ventricles, pulmonary artery trunk, and right atrium/inferior vena cava structures described in the FDA performance table
Authorized purpose: Process, review, analyze, communicate, and exchange multidimensional CT or MR images, including preliminary segmentation of normal anatomy, for preoperative surgical planning and intraoperative display; healthcare professionals make all final patient-management decisions. Machine-learning algorithms are for adults aged 22 years and older, while images for patients under 22 or of unknown age are generated without machine learning.
Modality
CT/CTA; MRI
Anatomy
Multi-region normal anatomy represented in CT or MR images; validated examples include prostate, bladder, neurovascular bundles, kidney, artery, and vein
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.