Authorized purpose: SpotLight and Duo produce cross-sectional images from X-ray transmission data for cardiovascular and thoracic examinations, including heart imaging with or without contrast and low-dose lung-cancer-screening protocols under established governmental or professional guidance.
Clinical role
CT acquisition, reconstruction, visualization, image processing, and examination-planning support under professional review.
Images and patients
CT/CTA · Cardiovascular, thoracic, and lung anatomy
Key limitation
Keep in mind: Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
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: SpotLight and Duo produce cross-sectional images from X-ray transmission data for cardiovascular and thoracic examinations, including heart imaging with or without contrast and low-dose lung-cancer-screening protocols under established governmental or professional guidance.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Cardiovascular, thoracic, and lung anatomy Input: X-ray transmission or projection data acquired under supported patient, protocol, contrast, dose, and reconstruction conditions.
Who uses it?Intended users: Qualified CT technologists and trained interpreting or treating physicians.
What does the software produce?Output: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional review.
What is its most important limitation?Key limitation: Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
Clinical takeaway. Clinical role: SpotLight and Duo produce cross-sectional images from X-ray transmission data for cardiovascular and thoracic examinations, including heart imaging with or without contrast and low-dose lung-cancer-screening protocols under established governmental or professional guidance.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing of the LCS protocols: all image quality metrics substantially equivalent to the predicate, CT numbers within ~3 Hounsfield Units, and all lung phantom nodule types detectable, including the smallest (4mm). In a clinical image quality assessment, two U.S. board-certified radiologists rated all fourteen (14) low-dose screening cases from two (2) U.S sites as diagnostic; the 0.25 to 2.8 mGy range was not clinically evaluated. 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
SpotLight and Duo produce cross-sectional images from X-ray transmission data for cardiovascular and thoracic examinations, including heart imaging with or without contrast and low-dose lung-cancer-screening protocols under established governmental or professional guidance.
Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
The exact FDA document reports bench testing of the LCS protocols: all image quality metrics substantially equivalent to the predicate, CT numbers within ~3 Hounsfield Units, and all lung phantom nodule types detectable, including the smallest (4mm). In a clinical image quality assessment, two U.S. board-certified radiologists rated all fourteen (14) low-dose screening cases from two (2) U.S sites as diagnostic; the 0.25 to 2.8 mGy range was not clinically evaluated. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical tests of the LCS protocols for Spotlight/Spotlight Duo systems have demonstrated that all image quality metrics are substantially equivalent to the predicate:" … "Uniformity and CT numbers for LCS protocols are maintained in the LCS protocol, comparable to the predicate device, and are within ~3 Hounsfield Units.". Read from the exact FDA decision document on 2026-11-14.
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 bench testing of the LCS protocols: all image quality metrics substantially equivalent to the predicate, CT numbers within ~3 Hounsfield Units, and all lung phantom nodule types detectable, including the smallest (4mm). In a clinical image quality assessment, two U.S. board-certified radiologists rated all fourteen (14) low-dose screening cases from two (2) U.S sites as diagnostic; the 0.25 to 2.8 mGy range was not clinically evaluated. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical tests of the LCS protocols for Spotlight/Spotlight Duo systems have demonstrated that all image quality metrics are substantially equivalent to the predicate:" … "Uniformity and CT numbers for LCS protocols are maintained in the LCS protocol, comparable to the predicate device, and are within ~3 Hounsfield Units.". Read from the exact FDA decision document on 2026-11-14.
No single product-level sensitivity value was promoted because the reviewed FDA material is workflow, module, sequence, or population specific.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No single product-level specificity value was promoted because the reviewed FDA material is workflow, module, sequence, or population specific.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K241200 FDA evidence package for SpotLight/SpotLight Duo with Low Dose Lung Cancer Screening Option
DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
PopulationLabeled population and configuration described in the K241200 FDA decision material
Scopeexact submission
Tested versionSpotLight and Duo configuration described in K241200
IndependenceSponsor or vendor study
K241200
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.
K241200 FDA evidence package for SpotLight/SpotLight Duo with Low Dose Lung Cancer Screening Option
DesignFDA 510(k) verification and validation evidence described in the exact submission
PopulationCardiovascular, thoracic, and lung anatomy
Scopeexact submission
Tested versionSpotLight and SpotLight Duo configuration described in K241200
IndependenceSponsor or vendor study
K241200
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.
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 K241200 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.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
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: X-ray transmission or projection data acquired under supported patient, protocol, contrast, dose, and reconstruction conditions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact local interoperability contract was not established by the FDA decision material; verify supported objects, routing, identifiers, archive behavior, and failure handling locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact installed deployment, hosting, service, and operational boundary is not established by the reviewed public FDA material.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cross-sectional CT images, reformats, measurements, quantitative results, and planning datasets for professional 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.
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.
Only qualified ct technologists and trained interpreting or treating physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K241200 by exact software, hardware, 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: Use is limited by the cleared patient population, acquisition and dose protocols, contrast conditions, and trained professional interpretation; the low-dose screening option has its own labeled eligibility and protocol limits.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
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 reviewed public material; productivity or value claims require local evidence.
Monitor 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.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.
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-04Last searched
26Fields reviewed
10Source classes checked
20Screened PubMed leads
10Screened trial leads
0Unreviewed FDA recall leads
Screened 20 PubMed titles and 10 trial records. The records are lexical matches for spotlight, including an unrelated concussion app, and none identifies Arineta SpotLight or SpotLight Duo under K241200; all 30 are quarantined. 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared product version was established. Obtain a written quote separating license, implementation, interfaces, compute, storage, training, support, upgrades, renewal, 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact installed deployment, hosting, service, and operational boundary is not established by the reviewed public FDA material.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact local interoperability contract was not established by the FDA decision material; verify supported objects, routing, identifiers, archive behavior, and failure handling locally.
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 publicly available - checked 2026-09-04 - Exact FDA submission
The FDA decision material does not establish the complete security posture for the exact product and deployment. Obtain architecture, identity, audit, encryption, retention, support-access, vulnerability-management, and incident-response evidence.
Authorized purpose: SpotLight and Duo produce cross-sectional images from X-ray transmission data for cardiovascular and thoracic examinations, including heart imaging with or without contrast and a low-dose lung-cancer-screening option used under established governmental or professional protocols.
Authorized purpose: An extension for syngo.via that assists trained physicians with automated and semi-automated analysis, visualization and reporting of cardiac CT angiography volume datasets for coronary-lesion evaluation, documentation, follow-up and treatment planning.
Authorized purpose: Enhanced Boundary for PCCT is a deep-learning CT processing function for improved soft-tissue delineation in routine head examinations with or without contrast.
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.