Cardiac CT Function Software Application

Evidence summary

FDA K241038 states that no clinical studies were necessary for substantial equivalence. ML validation used data from 9 sites, with 90% sampled from US sources and validation data separated from development data; reference standards used three expert readers. Reported segmentation endpoints were LV cavity MAE <10%, Dice >86%, Hausdorff distance <9.5 mm, and EF bias 1.3% (95% CI -12 to 14); RV cavity MAE <18%, Dice >85%, Hausdorff distance <18 mm, and EF bias -5.5% (95% CI -15 to 4.4); LV myocardium MAE <17%, Dice >82%, and Hausdorff distance <15 mm.

• FDA source
• Exact FDA submission
• Checked 2026-09-08

• Source

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

Postmarket safety review

The exact-identifier FDA recall query returned no native recall record for K241038. 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.

• Public source
• Exact FDA submission
• Checked 2026-09-08

• Source

• Verify deployment and data flow: The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
• Verify security and privacy controls: Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
• Verify training: Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
• Verify pricing and total cost: No public price or quote for the exact K241038 configuration was established in this review.
• Verify reimbursement and coding relevance: No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
• Verify local validation and lifecycle monitoring: Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA scope controls clinical claims. ACR provides bounded exact-submission catalog context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. Automated exact-name discovery found 0 PubMed and 0 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 device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall