Authorized purpose: Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
Clinical role
Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
Keep in mind: Applicability depends on compatible scanner configuration, acquisition, reconstruction, patient, anatomy, and professional interpretation.
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: Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Whole body; head; chest; abdomen; pelvis; heart; extremities; and inner ear Input: CT, CT simulation, or CT angiography data within the exact submission's labeled acquisition and patient scope.
Who uses it?Intended users: Qualified healthcare professionals who interpret or use the labeled CT information.
What does the software produce?Output: Cross-sectional CT images, reconstructions, measurements, segmentation, or planning information described in the exact FDA labeling.
What is its most important limitation?Key limitation: Applicability depends on compatible scanner configuration, acquisition, reconstruction, patient, anatomy, and professional interpretation.
Clinical takeaway. Clinical role: Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench verification and validation, phantom studies, and representative clinical image evaluations. For CLEAR Motion, two board-certified radiologists reviewed representative cases from eleven (11) patients; for PIQE, two board-certified radiologists reviewed lung CT cases from ten (10) patients, all image sets were determined to be of diagnostic quality, and all cases received average scores of 4 or higher on a 1–5 scale. 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
Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
Canon Aquilion ONE V2.0 acquires and processes whole-body CT volumes, including head, chest, abdomen, pelvis, cardiac, extremity, inner-ear, and multi-energy examinations with the labeled reconstruction functions.
The exact FDA document reports bench verification and validation, phantom studies, and representative clinical image evaluations. For CLEAR Motion, two board-certified radiologists reviewed representative cases from eleven (11) patients; for PIQE, two board-certified radiologists reviewed lung CT cases from ten (10) patients, all image sets were determined to be of diagnostic quality, and all cases received average scores of 4 or higher on a 1–5 scale. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Risk analysis and verification/validation activities conducted through bench testing demonstrate that the established specifications for the device have been met." … "The PIQE Lung algorithm was evaluated using phantom studies to confirm its performance and image quality improvements.". 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 verification and validation, phantom studies, and representative clinical image evaluations. For CLEAR Motion, two board-certified radiologists reviewed representative cases from eleven (11) patients; for PIQE, two board-certified radiologists reviewed lung CT cases from ten (10) patients, all image sets were determined to be of diagnostic quality, and all cases received average scores of 4 or higher on a 1–5 scale. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Risk analysis and verification/validation activities conducted through bench testing demonstrate that the established specifications for the device have been met." … "The PIQE Lung algorithm was evaluated using phantom studies to confirm its performance and image quality improvements.". Read from the exact FDA decision document on 2026-11-14.
No exact-product, version-specific sensitivity endpoint was established for this submission in the evidence set.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact-product, version-specific specificity endpoint was established for this submission in the evidence set.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K253596 FDA evidence package for Aquilion ONE (TSX-308A/TSX-306A) V2.0
DesignFDA submission-level decision material with device, software, performance, safety, and/or usability verification as applicable; not independent clinical validation.
PopulationPopulation and workflow are limited to the exact FDA labeling summarized for this submission.
Scopeexact submission
Tested versionExact FDA submission release; version not separately stated in the public decision material
IndependenceSponsor or vendor study
K253596
Evidence submitted for the exact FDA decision is not independent clinical validation. 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 K253596 by native exact 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, dental, 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: CT, CT simulation, or CT angiography data within the exact submission's labeled acquisition and patient scope.
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 FDA decision material does not establish a complete site-specific interoperability contract.
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. Deployment details for the exact cleared configuration are not established in the public FDA decision 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, reconstructions, measurements, segmentation, or planning information described in the exact FDA labeling.
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, reconstructions, measurements, segmentation, or planning information described in the exact FDA labeling.
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.
Canon Medical's cybersecurity page states that Canon imaging systems follow a software development life cycle governed by the NIST 800-53 Risk Management Framework adhering to Defense Health Agency certification requirements; FIPS 140-2 certified cipher standards; deny-all firewall configuration and near-real-time SIEM syslog export as premium offerings; a dedicated cybersecurity risk management team for threat intelligence monitoring, advisories and incident response; and published OS and third-party update policies. Vendor statement; no certification or test report was read.
Vendor-wide
Checked 2026-10-26
Vendor statement, not an attestation. Identity bridge: the page is on us.medical.canon, Canon Medical's own site (Canon Medical Systems USA), and describes Canon Medical imaging devices generally; the FDA applicant is Canon Medical Systems Corporation, named in the corporate name-change press release on the same domain. Regional page with general device claims; exact-release scope is not established.
Use by the qualified healthcare professionals identified for the exact labeled workflow; site-specific competency and training requirements remain to be established locally.
Unknown from the exact FDA decision material; establish and test the supported input, output, identity, routing, archive, 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 supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Applicability depends on compatible scanner configuration, acquisition, reconstruction, patient, anatomy, and professional interpretation.
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 the evidence set; productivity or value claims require local evidence.
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes; exact monitoring thresholds and vendor commitments are unknown.
exact submission · checked 2026-09-04
Establish ownership for data quality, overrides, drift, incidents, recalls, and change control.
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-19Last searched
27Fields reviewed
12Source 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 material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, fda decision summary, 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 in the evidence set. Obtain a written quote covering license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, downtime, 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 verified - checked 2026-09-04 - Exact FDA submission
Deployment details for the exact cleared configuration are not established in the public FDA decision material.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish a complete site-specific interoperability contract.
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
Monitoring: Not verified - checked 2026-09-04 - Exact FDA submission
Post-deployment monitoring, drift thresholds, alerting, and revalidation commitments for the exact configuration require vendor and site confirmation.
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.
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.