Authorized purpose: uAI Portal is a software solution for viewing, manipulating, communicating, and storing medical images and for supporting interpretation and evaluation in healthcare institutions. The FDA material describes lower-extremity vessel, head-and-neck vessel, coronary, pulmonary-artery, and aorta analysis functions for the corresponding CT angiography studies.
Clinical role
Medical-image processing, segmentation, enhancement, measurement, quantification, visualization, or reporting support under professional review.
Images and patients
CT/CTA · Head and neck, coronary and cardiac, pulmonary arteries, lower-extremity vessels, and aorta
Key limitation
Keep in mind: Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
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: uAI Portal is a software solution for viewing, manipulating, communicating, and storing medical images and for supporting interpretation and evaluation in healthcare institutions. The FDA material describes lower-extremity vessel, head-and-neck vessel, coronary, pulmonary-artery, and aorta analysis functions for the corresponding CT angiography studies.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head and neck, coronary and cardiac, pulmonary arteries, lower-extremity vessels, and aorta Input: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Who uses it?Intended users: Qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow.
What does the software produce?Output: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
What is its most important limitation?Key limitation: Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
Clinical takeaway. Clinical role: uAI Portal is a software solution for viewing, manipulating, communicating, and storing medical images and for supporting interpretation and evaluation in healthcare institutions. The FDA material describes lower-extremity vessel, head-and-neck vessel, coronary, pulmonary-artery, and aorta analysis functions for the corresponding CT angiography studies.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports algorithm segmentation testing on 150 images collected from US, independent of training data, against ground truth from two radiologists' independent annotations with an adjudicator selecting the final set. Average Dice: coronary vessels 0.920, heart 0.980, head vessel 0.902, neck vessel 0.967, aorta trunk 0.946, aorta branches 0.846, pulmonary arteries 0.953, pulmonary veins 0.933, lower extremity arteries 0.892. No clinical study was required. 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
uAI Portal is a software solution for viewing, manipulating, communicating, and storing medical images and for supporting interpretation and evaluation in healthcare institutions. The FDA material describes lower-extremity vessel, head-and-neck vessel, coronary, pulmonary-artery, and aorta analysis functions for the corresponding CT angiography studies.
Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
The exact FDA document reports algorithm segmentation testing on 150 images collected from US, independent of training data, against ground truth from two radiologists' independent annotations with an adjudicator selecting the final set. Average Dice: coronary vessels 0.920, heart 0.980, head vessel 0.902, neck vessel 0.967, aorta trunk 0.946, aorta branches 0.846, pulmonary arteries 0.953, pulmonary veins 0.933, lower extremity arteries 0.892. No clinical study was required. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Regarding the validation of the algorithm, the test data was used independently from training dataset. The algorithm testing of uAI Portal has been performed using 150 images collected from US," … "During the ground truthing process, two Chinese radiologists, each with at least 5 years of clinical experience, independently annotated vessel mask for each patient case, resulting in two sets of annotations per case.". 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 algorithm segmentation testing on 150 images collected from US, independent of training data, against ground truth from two radiologists' independent annotations with an adjudicator selecting the final set. Average Dice: coronary vessels 0.920, heart 0.980, head vessel 0.902, neck vessel 0.967, aorta trunk 0.946, aorta branches 0.846, pulmonary arteries 0.953, pulmonary veins 0.933, lower extremity arteries 0.892. No clinical study was required. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Regarding the validation of the algorithm, the test data was used independently from training dataset. The algorithm testing of uAI Portal has been performed using 150 images collected from US," … "During the ground truthing process, two Chinese radiologists, each with at least 5 years of clinical experience, independently annotated vessel mask for each patient case, resulting in two sets of annotations per case.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not a product-wide endpoint for this system or software function. 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 a product-wide endpoint for this system or software function. 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.
K240411 FDA decision evidence for uAI Portal
DesignFDA 510(k) substantial-equivalence review of the exact submission, device description, indications, and verification or validation documentation.
PopulationHead and neck, coronary and cardiac, pulmonary arteries, lower-extremity vessels, and aorta
Scopeexact submission
Tested versionuAI Portal
IndependenceSponsor or vendor study
K240411
The FDA decision material is manufacturer-submitted regulatory evidence. 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 K240411 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, surgical, or diagnostic 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: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes uAI Portal transferring images in DICOM 3.0 format over a medical imaging network or local file system, and letting users save images or results to PACS for storage or send them to Filming for printing. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "It can transfer images in DICOM 3.0 format over a medical imaging network or local file system." … "Users have the options to save images or results to PACS for storage or send them to Filming for printing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Images, segmentations, measurements, models, calculations, overlays, or reports that require 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.
The exact FDA package describes uAI Portal transferring images in DICOM 3.0 format over a medical imaging network or local file system, and letting users save images or results to PACS for storage or send them to Filming for printing. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "It can transfer images in DICOM 3.0 format over a medical imaging network or local file system." … "Users have the options to save images or results to PACS for storage or send them to Filming for printing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Only qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow should operate or interpret this product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K240411 before acceptance. Later family features are not evidence for this exact submission.
The exact FDA material does not establish a complete interoperability contract. Establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
The exact FDA material does not establish hosting, deployment topology, availability, upgrade path, or service responsibility. Obtain site-specific evidence before procurement.
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. Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
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. No exact-product price was found.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: Automated or quantitative outputs require professional review, appropriate source images, and the exact licensed application. The FDA submission does not establish a universal diagnostic-performance or patient-outcome claim.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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-20Last searched
33Fields 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 summary, 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 or approved 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service 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
Security: Not publicly available - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
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: 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.
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.