TrueFidelity deep-learning CT reconstruction produces low, medium, or high-strength images for supported head, whole-body, cardiac, and vascular applications on Revolution CT.
Clinical role
Integrated deep-learning reconstruction of diagnostic CT data before professional interpretation.
Images and patients
CT/CTA · Multi-region
Key limitation
The strength selection will vary with individual users' preferences and experience for the specific clinical need. Deep Learning Image Reconstruction does not introduce any new risks/hazards, warnings, or limitations.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyCT/CTA · Multi-region
Workflow roleIntegrated deep-learning reconstruction of diagnostic CT data before professional interpretation.
Required inputRaw CT projection data from supported scanner models and protocols.
Output and human actionDICOM CT images reconstructed at selectable strength levels.
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
TrueFidelity deep-learning CT reconstruction produces low, medium, or high-strength images for supported head, whole-body, cardiac, and vascular applications on Revolution CT.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.
The strength selection will vary with individual users' preferences and experience for the specific clinical need. Deep Learning Image Reconstruction does not introduce any new risks/hazards, warnings, or limitations.
Exact FDA submission
Checked 2026-09-19
These are the exact strength-selection and stated limitation boundaries; the dossier's broader universal-performance limitation is not in this packet.
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
K183202 reports the original platform-specific phantom, image-quality, and reader validation for TrueFidelity on Revolution CT.
Sensitivity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-03
Specificity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K183202 FDA performance package for Deep Learning Image Reconstruction
DesignManufacturer phantom, image-quality, and reader validation
PopulationSupported pediatric and adult CT applications on Revolution CT
Scopeexact submission
Tested versionTrueFidelity for Revolution CT
IndependenceSponsor or vendor study
K183202
Manufacturer evidence submitted for clearance or approval; local clinical, technical, 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 K183202 by exact submission identifier. This does not exclude product-family or later safety information.
Public source
Exact FDA submission
Checked 2026-09-03
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: Raw CT projection data from supported scanner models and protocols.
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: DICOM CT images reconstructed at selectable strength levels.
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
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.
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 Privacy Shield page on gehealthcare.com names GE Medical Systems LLC as a US entity of the GEHC group. Corporate program statement; portal content is credentialed; exact-release scope is not established.
Only qualified ct technologists and 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 by exact hardware, software and model 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: Bench and reader results do not establish universal dose reduction or diagnostic performance across every anatomy, protocol, patient size, or downstream quantitative application.
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. Bench and reader results do not establish universal dose reduction or diagnostic performance across every anatomy, protocol, patient size, or downstream quantitative application.
exact submission · checked 2026-09-03
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-03
Vendor productivity claims are scenario inputs, not guaranteed local savings.
Monitor by exact hardware, software and model 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: Bench and reader results do not establish universal dose reduction or diagnostic performance across every anatomy, protocol, patient size, or downstream quantitative application.
exact submission · checked 2026-09-03
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.
The exact indications identify CT applications; they do not establish the dossier's separate CTA modality label. Controlled directory display reconciled from exact FDA wording: CT. -> CT/CTA.
This audit distinguishes completed source review from fields that have not yet been researched.
Exact FDA record reviewedStatus
2026-09-19Last searched
26Fields reviewed
11Source classes checked
20Awaiting review PubMed leads
8Awaiting review trial leads
0Unreviewed FDA recall leads
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA packet assessed on 2026-09-19. Directory-backed facts were reconciled only where purpose, modality, and anatomy were each directly established. Candidate literature and postmarket candidates remain in their existing review state. Automated exact-name discovery found 20 PubMed and 8 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, acr ai central product, fda decision material, vendor product page, reimbursement policy, fda device recall, fda decision summary packet, 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.
Intended users: Withdrawn - checked 2026-09-19 - Exact FDA submission
Previous value withdrawn: The exact FDA decision-summary packet reviewed on 2026-09-19 does not establish this claim.
Public pricing: Not publicly available - checked 2026-09-03 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, enabled features, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
uCT ATLAS Astound and uCT ATLAS are whole-body CT systems for head, body, cardiac, and vascular imaging, with dual-energy analysis options and protocol-governed low-dose lung-screening use within approved programs.
Authorized purpose: uCT 780 produces whole-body cross-sectional CT images, including head, neck, cardiac, and vascular imaging, supports protocol-governed low-dose lung cancer screening and dual-energy material visualization, and uses DELTA deep-learning reconstruction for adult head, chest, abdomen, cardiac, and vascular applications.
TrueFidelity deep-learning CT reconstruction produces selectable-strength images for supported head, whole-body, cardiac, and vascular applications on the Discovery CT750 HD family.
Philips Incisive CT provides head, whole-body, cardiac, and vascular CT imaging for patients of all ages and can support qualified low-dose lung screening under labeled programs and protocols.
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.