FDA-cleared profile

StrokeViewer Perfusion

NICo-Lab B.V. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Provide quantitative perfusion information in brain tissue for suspected ischemic stroke patients using dynamic brain CT perfusion studies; medical imaging professionals use the information as additional data in the standard-of-care assessment, not as a standalone diagnostic tool.

Clinical role
Post-acquisition CT-perfusion viewing, processing, and quantitative analysis as an adjunct to standard-of-care interpretation; the output is reviewed in the clinical context and is not standalone diagnosis.
Images and patients
CT/CTA · Brain
Key limitation
Keep in mind: Not a standalone diagnostic tool and must be interpreted with patient information. The Perfusion algorithm is limited to brain CT perfusion rather than CTA or MR. The FDA indication identifies absent or inadequate bolus, excessive motion causing technically inadequate scans, and hemorrhage as contraindications; the packet does not establish a specific current PACS, RIS, EHR, or deployment configuration.

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: Provide quantitative perfusion information in brain tissue for suspected ischemic stroke patients using dynamic brain CT perfusion studies; medical imaging professionals use the information as additional data in the standard-of-care assessment, not as a standalone diagnostic tool.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain Input: DICOM-compliant dynamic brain CT perfusion images from suspected ischemic-stroke patients in the adult population. The FDA comparison states that this submission does not support CTA or MR data for the Perfusion algorithm.
  • Who uses it?Intended users: Medical imaging professionals who analyze dynamic perfusion studies, including neurologists and radiologists
  • What does the software produce?Output: Colored perfusion maps and quantitative Cerebral Blood Flow (CBF), Cerebral Blood Volume (CBV), Mean Transit Time (MTT), residue-function time-to-peak (TMax), Arterial Input Function (AIF), and affected-tissue volume calculations based on TMax and CBF abnormalities; results are exported as DICOM series and DICOM reports to a preconfigured destination for compatible DICOM-viewer review.
  • What is its most important limitation?Key limitation: Not a standalone diagnostic tool and must be interpreted with patient information. The Perfusion algorithm is limited to brain CT perfusion rather than CTA or MR. The FDA indication identifies absent or inadequate bolus, excessive motion causing technically inadequate scans, and hemorrhage as contraindications; the packet does not establish a specific current PACS, RIS, EHR, or deployment configuration.

Clinical takeaway. Clinical role: Provide quantitative perfusion information in brain tissue for suspected ischemic stroke patients using dynamic brain CT perfusion studies; medical imaging professionals use the information as additional data in the standard-of-care assessment, not as a standalone diagnostic tool.

Evidence takeaway. Evidence from the reviewed source record: FDA K231570 states that clinical data were not required. Nonclinical verification and validation included unit, end-to-end, and reproducibility testing, plus bench performance testing on simulated Kudo digital-phantom datasets comparing device output with ground truth; the packet states that performance goals and acceptance criteria were met.

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
Provide quantitative perfusion information in brain tissue for suspected ischemic stroke patients using dynamic brain CT perfusion studies; medical imaging professionals use the information as additional data in the standard-of-care assessment, not as a standalone diagnostic tool.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Post-acquisition CT-perfusion viewing, processing, and quantitative analysis as an adjunct to standard-of-care interpretation; the output is reviewed in the clinical context and is not standalone diagnosis.
  • Exact FDA submission
  • Checked 2026-09-08
Required input
DICOM-compliant dynamic brain CT perfusion images from suspected ischemic-stroke patients in the adult population. The FDA comparison states that this submission does not support CTA or MR data for the Perfusion algorithm.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
Colored perfusion maps and quantitative Cerebral Blood Flow (CBF), Cerebral Blood Volume (CBV), Mean Transit Time (MTT), residue-function time-to-peak (TMax), Arterial Input Function (AIF), and affected-tissue volume calculations based on TMax and CBF abnormalities; results are exported as DICOM series and DICOM reports to a preconfigured destination for compatible DICOM-viewer review.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Clinical setting not specified in the FDA packet; adult suspected-stroke population
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Medical imaging professionals who analyze dynamic perfusion studies, including neurologists and radiologists
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
Not a standalone diagnostic tool and must be interpreted with patient information. The Perfusion algorithm is limited to brain CT perfusion rather than CTA or MR. The FDA indication identifies absent or inadequate bolus, excessive motion causing technically inadequate scans, and hemorrhage as contraindications; the packet does not establish a specific current PACS, RIS, EHR, or deployment configuration.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
FDA K231570 states that clinical data were not required. Nonclinical verification and validation included unit, end-to-end, and reproducibility testing, plus bench performance testing on simulated Kudo digital-phantom datasets comparing device output with ground truth; the packet states that performance goals and acceptance criteria were met.
  • Exact FDA submission
  • Checked 2026-09-08

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
FDA K231570 states that clinical data were not required. Nonclinical verification and validation included unit, end-to-end, and reproducibility testing, plus bench performance testing on simulated Kudo digital-phantom datasets comparing device output with ground truth; the packet states that performance goals and acceptance criteria were met.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

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

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 exact-identifier FDA recall query returned no native recall record for K231570. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

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: DICOM-compliant dynamic brain CT perfusion images from suspected ischemic-stroke patients in the adult population. The FDA comparison states that this submission does not support CTA or MR data for the Perfusion algorithm.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K231570: StrokeViewer Perfusion

  2. Routing

    Source context, not route validation: The software is packaged as a Docker container for a standard off-the-shelf computer or virtual platform, extracts DICOM information, and exports DICOM series and reports to a preconfigured destination for compatible DICOM-viewer review. Exact current interface, PACS/RIS/EHR, and deployment details are not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K231570: StrokeViewer Perfusion

  3. AI processing

    Source context, not route validation: The exact FDA package describes StrokeViewer Perfusion as an image processing application packed as a Docker container for installation on a standard off-the-shelf computer or a virtual platform. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "StrokeViewer Perfusion is an image processing application that runs on a standard "off-the-shelf" computer or a virtual platform" … "The software is packed as a Docker container allowing installation on a standard “off-the-shelf” computer or a virtual platform.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

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

    Field checked 2026-11-14 · FDA K231570: StrokeViewer Perfusion

  4. Returned objects

    Source context, not route validation: Colored perfusion maps and quantitative Cerebral Blood Flow (CBF), Cerebral Blood Volume (CBV), Mean Transit Time (MTT), residue-function time-to-peak (TMax), Arterial Input Function (AIF), and affected-tissue volume calculations based on TMax and CBF abnormalities; results are exported as DICOM series and DICOM reports to a preconfigured destination for compatible DICOM-viewer review.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K231570: StrokeViewer Perfusion

  5. Viewer/worklist/report

    Unresolved route: Colored perfusion maps and quantitative Cerebral Blood Flow (CBF), Cerebral Blood Volume (CBV), Mean Transit Time (MTT), residue-function time-to-peak (TMax), Arterial Input Function (AIF), and affected-tissue volume calculations based on TMax and CBF abnormalities; results are exported as DICOM series and DICOM reports to a preconfigured destination for compatible DICOM-viewer review.

    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-08 · FDA K231570: StrokeViewer Perfusion

  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 exact FDA package describes StrokeViewer Perfusion as an image processing application packed as a Docker container for installation on a standard off-the-shelf computer or a virtual platform. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "StrokeViewer Perfusion is an image processing application that runs on a standard "off-the-shelf" computer or a virtual platform" … "The software is packed as a Docker container allowing installation on a standard “off-the-shelf” computer or a virtual platform.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The software is packaged as a Docker container for a standard off-the-shelf computer or virtual platform, extracts DICOM information, and exports DICOM series and reports to a preconfigured destination for compatible DICOM-viewer review. Exact current interface, PACS/RIS/EHR, and deployment details are not established.
  • Exact FDA submission
  • Checked 2026-09-08
Security
Nicolab's StrokeViewer security whitepaper (NIC-200165-07-F, 2025-08-14) states that Nicolab is ISO/IEC 27001 certified with regular third-party audits and penetration tests, that the platform follows OWASP application-security standards, that uploaded patient DICOM data is deleted per the processing agreement and never used to train AI algorithms, that personnel access follows least privilege with audit logs, and that transfers are encrypted (HTTPS/TLS) with NEN 7510-1 and ISO 13485 also listed under certifications.
  • Product family
  • Checked 2026-10-27

Vendor whitepaper; certificates and audit reports not read. Scope is the Nicolab StrokeViewer platform. HALO (K211788) is not named in the whitepaper and was not bridged. Exact-release scope is not established.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for StrokeViewer Perfusion; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K231570
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Brain
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2023-12-14
  • 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.

Exact FDA record reviewedStatus
2026-09-20Last searched
21Fields reviewed
9Source 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, 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-08 - Exact FDA submission

    No public price or quote for the exact K231570 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-08 - 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-08 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

8 sources - 3 history items

Source ledger

  1. FDA K231570: StrokeViewer Perfusion

    U.S. Food and Drug Administration - Published 2023-12-14 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. StrokeViewer Perfusion model card (K231570)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, integration, anatomy, implementationCapabilities

  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. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K231570

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

    Scope: postmarketSafety

  8. Nicolab: StrokeViewer Security Whitepaper (NIC-200165-07-F)

    Nicolab - Published 2025-08-14 - Accessed 2026-10-27

    Scope: security

Research history

  1. K231570 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K251151

Rapid CTA 360

iSchemaView

Authorized purpose: Rapid CTA 360 analyzes adult head CTA DICOM images to flag suspected large- and medium-vessel occlusion in specified intracranial and vertebral segments and notify trained clinicians for workflow triage; notifications are informational and not diagnostic.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-07-16
FDA-cleared K243294

Brainomix 360 e-ASPECTS

Brainomix Limited

Authorized purpose: Brainomix 360 e-ASPECTS registers adult non-contrast brain CT, segments ASPECTS regions, and provides an editable ASPECTS score with highlighted regions and voxel contribution views to assist trained clinicians evaluating suspected ischemic stroke within 24 hours of last known well.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-02-14
FDA-cleared K260406

Brainomix 360 Hyperdensity

Brainomix Limited

Authorized purpose: Provides volumetric hyperdensity segmentation and quantification as an aid; physicians must review original images.

Modality
CT/CTA
Anatomy
Brain
Decision
2026-06-12
FDA-cleared K251590

Methinks CTA Stroke

Methinks Software S.L.

Authorized purpose: Methinks CTA Stroke analyzes acute-setting brain CT angiography in adults over 21 with suspected stroke for suspected large-vessel occlusion in the terminal ICA, MCA-M1, or MCA-M2 and sends PACS and/or specialist notifications in parallel to standard care; previews are informational and not diagnostic.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-08-20

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