Authorized purpose: Deep Learning Image Reconstruction is a deep-learning reconstruction method that produces cross-sectional images of the head and whole body from X-ray transmission data acquired at different angles and planes, including axial, helical or volumetric, and cardiac acquisitions for all ages. It can be used for head, whole-body, cardiac, and vascular CT applications.
Clinical role
Deep-learning reconstruction of cross-sectional CT images for labeled head, whole-body, cardiac, and vascular applications.
Images and patients
CT/CTA · Head, whole body, cardiac, and vascular anatomy
Key limitation
Keep in mind: Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace 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: Deep Learning Image Reconstruction is a deep-learning reconstruction method that produces cross-sectional images of the head and whole body from X-ray transmission data acquired at different angles and planes, including axial, helical or volumetric, and cardiac acquisitions for all ages. It can be used for head, whole-body, cardiac, and vascular CT applications.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head, whole body, cardiac, and vascular anatomy Input: X-ray transmission data acquired at different angles and planes during supported axial, helical, volumetric, or cardiac CT acquisitions.
Who uses it?Intended users: Qualified CT technologists and trained interpreting physicians.
What does the software produce?Output: Cross-sectional reconstructed CT images for head, whole-body, cardiac, and vascular review.
What is its most important limitation?Key limitation: Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace professional interpretation.
Clinical takeaway. Clinical role: Deep Learning Image Reconstruction is a deep-learning reconstruction method that produces cross-sectional images of the head and whole body from X-ray transmission data acquired at different angles and planes, including axial, helical or volumetric, and cardiac acquisitions for all ages. It can be used for head, whole-body, cardiac, and vascular CT applications.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports only non-clinical testing: design control testing and engineering bench testing in which identical raw datasets were reconstructed with DLIR or ASiR-V and compared for low contrast detectability, image noise, high-contrast spatial resolution, streak artifact suppression and other image quality measures, including pediatric phantom and low dose lung cancer screening protocol evaluations. Design verification and bench testing demonstrated that DLIR met all of its design requirement and performance criteria. 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
Deep Learning Image Reconstruction is a deep-learning reconstruction method that produces cross-sectional images of the head and whole body from X-ray transmission data acquired at different angles and planes, including axial, helical or volumetric, and cardiac acquisitions for all ages. It can be used for head, whole-body, cardiac, and vascular CT applications.
Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace professional interpretation.
The exact FDA document reports only non-clinical testing: design control testing and engineering bench testing in which identical raw datasets were reconstructed with DLIR or ASiR-V and compared for low contrast detectability, image noise, high-contrast spatial resolution, streak artifact suppression and other image quality measures, including pediatric phantom and low dose lung cancer screening protocol evaluations. Design verification and bench testing demonstrated that DLIR met all of its design requirement and performance criteria. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Summary of Non-Clinical Testing Deep Learning Image Reconstruction has successfully completed the design control testing per our quality system." … "Engineering bench testing was also performed to support substantial equivalence and the product performance claims.". 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 only non-clinical testing: design control testing and engineering bench testing in which identical raw datasets were reconstructed with DLIR or ASiR-V and compared for low contrast detectability, image noise, high-contrast spatial resolution, streak artifact suppression and other image quality measures, including pediatric phantom and low dose lung cancer screening protocol evaluations. Design verification and bench testing demonstrated that DLIR met all of its design requirement and performance criteria. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Summary of Non-Clinical Testing Deep Learning Image Reconstruction has successfully completed the design control testing per our quality system." … "Engineering bench testing was also performed to support substantial equivalence and the product performance claims.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K230807 FDA evidence package for Deep Learning Image Reconstruction
DesignFDA 510(k) non-clinical software verification and substantial-equivalence evidence for a CT reconstruction option.
PopulationHead, whole body, cardiac, and vascular anatomy
Scopeexact submission
Tested versionDeep Learning Image Reconstruction configuration described in K230807
IndependenceSponsor or vendor study
K230807
The decision material describes the same intended use as the predicate and does not establish product-wide clinical outcomes.
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 K230807 by exact native submission identifier. This does not exclude product-family, later-version, 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 or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
No separate named-product payment identified in reviewed public material
Centers for Medicare & Medicaid Services · United States
This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage 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 data acquired at different angles and planes during supported axial, helical, volumetric, or cardiac CT acquisitions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes a reconstruction option ported to named GE CT system families and using their X-ray transmission data and supported acquisition modes.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA package describes DLIR as an option on supported GE CT system families; current installed hardware, software release, reconstruction protocol, service, security, and availability remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Cross-sectional reconstructed CT images for head, whole-body, cardiac, and vascular 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 FDA package describes DLIR as an option on supported GE CT system families; current installed hardware, software release, reconstruction protocol, service, security, and availability remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA package describes a reconstruction option ported to named GE CT system families and using their X-ray transmission data and supported acquisition modes.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
GE HealthCare's Product Security Portal is described as a credentialed global portal giving customers security updates, vulnerability status and required actions for GE HealthCare products potentially impacted by critical vulnerabilities, plus historical patch views; GE HealthCare references its Cybersecurity Risk Management System and publishes a Coordinated Vulnerability Disclosure Statement for reporting vulnerabilities in GE HealthCare products.
Vendor-wide
Checked 2026-10-26
Vendor statement, not an attestation. Identity bridge: GE HealthCare's own offices page on gehealthcare.com names GE HealthCare Japan Corporation. Corporate program statement; portal content is credentialed; exact-release scope is not established.
Only qualified ct technologists and trained interpreting 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 K230807 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. Track these product-specific limits: Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace professional interpretation.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared or authorized scope; it is not a claim that the FDA package provides a live monitoring service.
The FDA package describes DLIR as an option on supported GE CT system families; current installed hardware, software release, reconstruction protocol, service, security, and availability remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes a reconstruction option ported to named GE CT system families and using their X-ray transmission data and supported acquisition modes.
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. Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace 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 reviewed public material; productivity or value claims require local evidence.
Monitor K230807 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. Track these product-specific limits: Use is limited to supported GE CT platforms, reconstruction options, acquisition protocols, patient populations, and labeled applications; reconstruction does not replace professional interpretation.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. deep-learning CT image-reconstruction method limits remain submission-specific.
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-04Last searched
26Fields reviewed
12Source classes checked
20Screened PubMed leads
8Screened trial leads
0Unreviewed FDA recall leads
Twenty PubMed records and eight trial records were screened. They concern generic deep-learning reconstruction or different modalities, vendors, protocols, and platforms; records naming GE TrueFidelity or DLIR do not identify the exact K230807 configuration and supported release, so all 28 are quarantined. The current discovery snapshot contains 20 PubMed and 8 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 decision material, fda pma record, 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 or authorized configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
Authorized purpose: Revolution Ascend produces axial, cine, helical, cardiac, and gated CT images from X-ray transmission data with or without contrast, with post-processing and analysis for head, whole-body, cardiac, and vascular diagnosis, therapy planning, guidance, and monitoring.
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.