A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Aids physicians in assessing coronary artery calcification on non-gated, non-contrast standard- or low-dose chest CT.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest/coronary arteries Input: DICOM non-gated, non-contrast chest CT in adults aged 30 years or older.
Who uses it?Intended users: Physicians.
What does the software produce?Output: Per-artery and total Agatston scores, CAC categories, arterial age, illustrative segmentations, and optional DICOM Secondary Capture.
What is its most important limitation?Key limitation: Input is limited to slices up to 3 mm, and segmentations are not diagnostic.
Clinical takeaway. Clinical role: Aids physicians in assessing coronary artery calcification on non-gated, non-contrast standard- or low-dose chest CT.
Evidence takeaway. Evidence from the reviewed source record: The 510(k) summary reports 491 clinical-assessment cases from five sites and four CT manufacturers, with kappa 0.959 (95% CI 0.943-0.975) and Bland-Altman limits of agreement -12.20 +/- 437.84.
Evidence context: questions, not a score
Agent transcription of regulatory evidence context, not independent validation, clinical acceptance or a product recommendation. Separate studies and outcomes are not a leaderboard.
Existing study anchor: ClearRead CT CAC regulatory performance study summary. Tested version label: Exact product version not reported; regulatory study summarized for FDA submission K242188.
What was tested?
Standalone Agatston category/score agreement and calcium segmentation, not a reader workflow trial or patient-outcome study.
The clinical set had 491 cases across five sites and four CT manufacturers: 143 without CAC and 348 with CAC. Approximately 400 internal held-out cases were a separate assessment.
The summary reports quadratic-weighted category agreement and separate continuous-score Bland-Altman limits. These are different endpoints, not one combined accuracy result. Agreement is not cancer-detection sensitivity or proof of reduced work-up.
The selected score-spanning cases do not establish natural clinical prevalence or patient outcomes. Category agreement, continuous-score agreement and segmentation overlap are different endpoints. No local integration or management benefit is established.
Not established: The reviewed regulatory summary does not establish this field for this study context.
training Population
Not established: The reviewed regulatory summary does not establish this field for this study context.
evaluation Population
491 clinical-assessment cases: 143 with no CAC and 348 with CAC. Approximately 400 internal held-out cases are a separate test, not an added clinical denominator.
Clinical CAC status and Agatston measurements used consensus ground truth from three radiologists; internal testing used manually outlined calcium masks.
Clinical set: 143 CAC-negative and 348 CAC-positive out of 491 cases. Positive cases were selected to span the score range, not a natural screening prevalence estimate.
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.
Controlled-vocabulary normalization: the 510(k) summary describes a computer aided quantification system whose primary output is the Agatston score; its segmentations are illustrative only and not for diagnostic use.
The 510(k) summary reports 491 clinical-assessment cases from five sites and four CT manufacturers, with kappa 0.959 (95% CI 0.943-0.975) and Bland-Altman limits of agreement -12.20 +/- 437.84.
Exact FDA submission
Checked 2026-11-12
Manufacturer-prepared 510(k) summary in the FDA decision packet, not an independent FDA analysis.
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 510(k) summary reports 491 clinical-assessment cases from five sites and four CT manufacturers, with kappa 0.959 (95% CI 0.943-0.975) and Bland-Altman limits of agreement -12.20 +/- 437.84.
FDA source
Exact FDA submission
Checked 2026-11-12
Manufacturer-prepared 510(k) summary in the FDA decision packet, not an independent FDA analysis.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
ClearRead CT CAC regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K242188
Samplen=491
IndependenceIndependence not established
K242188
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 K242188. 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: DICOM non-gated, non-contrast chest CT in adults aged 30 years or older.
Scope: Exact FDA submission. Exact FDA input and population scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
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. Previous value withdrawn: The exact FDA decision-summary packet reviewed on 2026-11-12 does not establish this claim; it gives only an intended location of Medical Facility and no hosting model.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-11-12 ·
Returned objects
Source context, not route validation: Per-artery and total Agatston scores, CAC categories, arterial age, illustrative segmentations, and optional DICOM Secondary Capture.
Scope: Exact FDA submission. FDA output description.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Per-artery and total Agatston scores, CAC categories, arterial age, illustrative segmentations, and optional DICOM Secondary Capture.
Scope: Exact FDA submission. FDA output description.
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-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
ACR AI Central provides an exact-submission model card for ClearRead CT CAC; 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
24Fields 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, fda decision summary, acr ai central product, fda device recall, literature index, trial registry, 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.
Public pricing: Not verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K242188 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-09 - 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: Withdrawn - checked 2026-11-12 - Exact FDA submission
Previous value withdrawn: The exact FDA decision-summary packet reviewed on 2026-11-12 does not establish this claim; it gives only an intended location of Medical Facility and no hosting model.
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 verified - checked 2026-09-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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.