Keep in mind: Output interpretation is adjunctive to the original reconstructed image. Use with iterative reconstruction or deep-learning reconstructions may have unknown performance; advanced third-party post-processing or specialized non-standard filtering was not specifically characterized, and direct primary scanner reconstructions are recommended.
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: Process and enhance CT images from any CT scanner manufacturer or model as an adjunct to the original reconstructed image.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Multiple CT anatomies: abdomen, C-spine, cardiac, chest, chest-abdomen-pelvis, head, head/neck, L-spine, lower extremity, MSK, T-spine, and upper extremity. Input: Primary reconstructed DICOM CT images sent by a technologist through a compatible MDDS; FBP primary reconstructions at standard or higher dose were quantitatively validated. The packet also includes varied scanners, anatomies, contrast, reconstruction methods, and slice thicknesses, but warns that IR/DL reconstruction performance may be unknown.
Who uses it?Intended users: Radiologists.
What does the software produce?Output: Enhanced DICOM CT images returned through the compatible MDDS to PACS or another DICOM node; enhanced images coexist with the original reconstructed images; no user interface.
What is its most important limitation?Key limitation: Output interpretation is adjunctive to the original reconstructed image. Use with iterative reconstruction or deep-learning reconstructions may have unknown performance; advanced third-party post-processing or specialized non-standard filtering was not specifically characterized, and direct primary scanner reconstructions are recommended.
Clinical takeaway. Clinical role: Process and enhance CT images from any CT scanner manufacturer or model as an adjunct to the original reconstructed image.
Evidence takeaway. Evidence from the reviewed source record: FDA K254120 reports phantom performance validation using ACR, Digital CatPhan 600, and Mercury 4.0 phantoms plus a 270-case retrospective reader study. Phantom endpoints included detectability index, noise magnitude, NPS, CT-number accuracy, non-uniformity, and TTF, all reported as passing their stated criteria. Reader endpoints were diagnostic utility (average Likert score >=3) and artifact presence (average score >=2); no sensitivity/specificity or disease-detection accuracy was reported.
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
Process and enhance CT images from any CT scanner manufacturer or model as an adjunct to the original reconstructed image.
Primary reconstructed DICOM CT images sent by a technologist through a compatible MDDS; FBP primary reconstructions at standard or higher dose were quantitatively validated. The packet also includes varied scanners, anatomies, contrast, reconstruction methods, and slice thicknesses, but warns that IR/DL reconstruction performance may be unknown.
Enhanced DICOM CT images returned through the compatible MDDS to PACS or another DICOM node; enhanced images coexist with the original reconstructed images; no user interface.
Output interpretation is adjunctive to the original reconstructed image. Use with iterative reconstruction or deep-learning reconstructions may have unknown performance; advanced third-party post-processing or specialized non-standard filtering was not specifically characterized, and direct primary scanner reconstructions are recommended.
FDA K254120 reports phantom performance validation using ACR, Digital CatPhan 600, and Mercury 4.0 phantoms plus a 270-case retrospective reader study. Phantom endpoints included detectability index, noise magnitude, NPS, CT-number accuracy, non-uniformity, and TTF, all reported as passing their stated criteria. Reader endpoints were diagnostic utility (average Likert score >=3) and artifact presence (average score >=2); no sensitivity/specificity or disease-detection accuracy was reported.
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
FDA K254120 reports phantom performance validation using ACR, Digital CatPhan 600, and Mercury 4.0 phantoms plus a 270-case retrospective reader study. Phantom endpoints included detectability index, noise magnitude, NPS, CT-number accuracy, non-uniformity, and TTF, all reported as passing their stated criteria. Reader endpoints were diagnostic utility (average Likert score >=3) and artifact presence (average score >=2); no sensitivity/specificity or disease-detection accuracy was reported.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
SubtleHD-CT (1.x) regulatory performance study summary
DesignReader Study
PopulationAdult and Pediatric
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K254120
IndependenceIndependence not established
K254120
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K254120. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: Primary reconstructed DICOM CT images sent by a technologist through a compatible MDDS; FBP primary reconstructions at standard or higher dose were quantitatively validated. The packet also includes varied scanners, anatomies, contrast, reconstruction methods, and slice thicknesses, but warns that IR/DL reconstruction performance may be unknown.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Technologist routes the study from the CT scanner to a compatible MDDS via DICOM; the MDDS supplies images to SubtleHD-CT and returns enhanced images to PACS or another DICOM node using an AE Title.
Scope: Exact FDA submission.
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 reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-08 ·
Returned objects
Source context, not route validation: Enhanced DICOM CT images returned through the compatible MDDS to PACS or another DICOM node; enhanced images coexist with the original reconstructed images; no user interface.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Enhanced DICOM CT images returned through the compatible MDDS to PACS or another DICOM node; enhanced images coexist with the original reconstructed images; no user interface.
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.
Technologist routes the study from the CT scanner to a compatible MDDS via DICOM; the MDDS supplies images to SubtleHD-CT and returns enhanced images to PACS or another DICOM node using an AE Title.
Subtle Medical's current compliance page lists an annual SOC 2 Type II + HIPAA security audit, and ISO 13485:2016 (valid until 2027-07-12) and ISO/IEC 42001:2023 (valid until 2028-07-17) certificates. The page gives no audit period or report scope, and the SOC 2 report was not read.
Vendor-wide
Checked 2026-10-25
Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.
ACR AI Central provides an exact-submission model card for SubtleHD-CT (1.x); FDA labeling remains controlling for clinical use, limitations, and performance.
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-20Last searched
23Fields reviewed
10Source 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, acr ai central product, vendor product page, fda decision summary, 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 verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K254120 configuration was established in this review.
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
Reimbursement: Not publicly available - checked 2026-09-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Deployment: Not verified - checked 2026-09-08 - Exact FDA submission
The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
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
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: AI-CVD provides automated quantitative CT-derived anatomical and density measurements for clinician review, including calcium scores, cardiac and vascular measurements, lung and liver density, bone mineral density, and muscle/fat composition; it is opportunistic decision support, not diagnostic interpretation or risk prediction.
Authorized purpose: uOmnispace.CT provides healthcare institutions with tools to view, manipulate, evaluate, and analyze medical CT images, including colon, lung, vessel, brain, cardiac, liver, rib, spine, dual-energy, perfusion, and cardiovascular applications described in the exact FDA submission.
Modality
CT/CTA
Anatomy
Colon, lungs and airway, vessels, brain, heart, liver, ribs, spine, and other CT regions
Authorized purpose: uOmnispace.CT is software for viewing, manipulating, evaluating, and analyzing medical images within healthcare institutions. The FDA indication lists colon visualization, dental panoramic and paraxial reconstruction, lung and airway segmentation and quantitative parameters, nodule analysis, vessel and brain-perfusion analysis, heart and coronary analysis, calcium scoring, dynamic analysis, bone-structure labeling, liver evaluation, dual-energy processing, and cardiovascular combined analysis.
Modality
CT/CTA
Anatomy
Colon, jaw, lungs, airways, brain, heart, vessels, liver, spine, ribs, and other labeled CT regions
Authorized purpose: Auto-Seg and Spine Auto-Seg accept spine and pelvis CT images and provide three-dimensional segmentation and labels to support spine-surgery planning and assessment by spine surgeons.
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.