Authorized purpose: Careverse CoronaryDoc is a web-based tool for trained medical professionals to view and analyze CCTA CT data for coronary plaques and stenosis, with coronary measurements, visualization, automated plaque and stenosis outputs, and structured reporting for physician review.
Clinical role
Web-based post-processing, coronary measurement and visualization, automated plaque and stenosis analysis, and structured report preparation for physician review.
Images and patients
CT/CTA · Heart/Cardiovascular
Key limitation
Keep in mind: The software is not intended to replace qualified practitioner judgment and requires trained users. The reported agreement values are table-specific regulatory results, not a product-wide diagnostic sensitivity or clinical-outcome claim.
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: Careverse CoronaryDoc is a web-based tool for trained medical professionals to view and analyze CCTA CT data for coronary plaques and stenosis, with coronary measurements, visualization, automated plaque and stenosis outputs, and structured reporting for physician review.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Heart/Cardiovascular Input: DICOM 3.0-compliant CCTA CT images obtained using any CT scanner for CAD or suspected CAD evaluation.
Who uses it?Intended users: Trained medical professionals using coronary CT analysis as part of physician diagnostic decision-making.
What does the software produce?Output: Coronary-region extraction, suspected stenosis detection, plaque composition overlays, stenosis grading, vessel and lumen volumes, total, calcified, non-calcified and low-density plaque volumes, branch naming, stent and myocardial-bridge detection, and structured reports.
What is its most important limitation?Key limitation: The software is not intended to replace qualified practitioner judgment and requires trained users. The reported agreement values are table-specific regulatory results, not a product-wide diagnostic sensitivity or clinical-outcome claim.
Clinical takeaway. Clinical role: Careverse CoronaryDoc is a web-based tool for trained medical professionals to view and analyze CCTA CT data for coronary plaques and stenosis, with coronary measurements, visualization, automated plaque and stenosis outputs, and structured reporting for physician review.
Evidence takeaway. Evidence from the reviewed source record: K251656 FDA evidence is a manufacturer-submitted regulatory agreement package for coronary stenosis and plaque outputs; the stored literature and trial candidate arrays were empty and no independent study was promoted.
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
Careverse CoronaryDoc is a web-based tool for trained medical professionals to view and analyze CCTA CT data for coronary plaques and stenosis, with coronary measurements, visualization, automated plaque and stenosis outputs, and structured reporting for physician review.
Web-based post-processing, coronary measurement and visualization, automated plaque and stenosis analysis, and structured report preparation for physician review.
The software is not intended to replace qualified practitioner judgment and requires trained users. The reported agreement values are table-specific regulatory results, not a product-wide diagnostic sensitivity or clinical-outcome claim.
K251656 FDA evidence is a manufacturer-submitted regulatory agreement package for coronary stenosis and plaque outputs; the stored literature and trial candidate arrays were empty and no independent study was promoted.
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
K251656 FDA evidence is a manufacturer-submitted regulatory agreement package for coronary stenosis and plaque outputs; the stored literature and trial candidate arrays were empty and no independent study was promoted.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The wave22 exact-submission recall query returned no native recall record for K251656. This does not establish absence of family, later-version, or adverse-event information.
CMS LCD L39913 v7 and Article A59813 v6 provide conditional service-level policy context for AI-QCT/AI-CPA after completed and interpreted CCTA in WPS Medicare J5/J8 for selected symptomatic chest-pain patients; exact product/version eligibility and individual claim eligibility are not established.
Product family
Checked 2026-09-07
Service-level policy context; exact product/version and individual claim eligibility are not established. This is not a product code assignment, universal Medicare coverage determination, fee, or price.
Medicare / WPS · United States - WPS J5/J8 jurisdictions · Effective 2026-01-01
CMS policy context applies to an eligible CCTA plaque-analysis service in a limited WPS policy scope; it does not assign coverage to K251656 or establish individual claim eligibility.
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 3.0-compliant CCTA CT images obtained using any CT scanner for CAD or suspected CAD evaluation.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA summary describes a web application with DICOM CT input, transmission queues, image management, editing, and structured reports; local PACS, RIS, identity, routing, and report-ingestion behavior require testing.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: K251656 describes a web-based application; public material reviewed does not establish hosting region, PHI flow, retention, availability, or site-specific service boundaries.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Coronary-region extraction, suspected stenosis detection, plaque composition overlays, stenosis grading, vessel and lumen volumes, total, calcified, non-calcified and low-density plaque volumes, branch naming, stent and myocardial-bridge detection, and structured reports.
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.
K251656 describes a web-based application; public material reviewed does not establish hosting region, PHI flow, retention, availability, or site-specific service boundaries.
The FDA summary describes a web application with DICOM CT input, transmission queues, image management, editing, and structured reports; local PACS, RIS, identity, routing, and report-ingestion behavior require testing.
The exact submission is a web-based application for CCTA CT post-processing, coronary measurement, automated plaque and stenosis analysis, and structured reporting.
Careverse lists CoronaryDoc in its Digital Heart family alongside coronary FFR, calcium-score, cardiac-function, and plaque-analysis applications; the page presents family context rather than K251656 release documentation.
Test DICOM import, identity mapping, series selection, routing, structured-report delivery, user roles, edits, and failure recovery with the installed version before clinical use.
exact submission · checked 2026-09-07
This is buyer acceptance guidance based on the FDA-described workflow, not a verified interface contract.
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-07Last searched
24Fields reviewed
12Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The stored PubMed and ClinicalTrials.gov candidate arrays were screened and were empty. No paper or trial was promoted; empty stored arrays do not establish that no external literature or trials exist. 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, vendor product page, payer policy, fda device recall, literature index, trial registry, stored candidate metadata, 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-07 - Exact FDA submission
No public list price or contract unit for K251656 was established in the reviewed official sources.
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
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 publicly available - checked 2026-09-07 - Exact FDA submission
The reviewed exact FDA packet and Careverse family page do not establish a current scoped security attestation or deployed data-flow controls.
Authorized purpose: cvi42 Coronary Plaque supports qualified professionals with viewing, post-processing, and qualitative and quantitative evaluation of adult cardiac CT DICOM images to assess the presence and extent of coronary plaques and stenoses in CCTA for CAD or suspected CAD.
Authorized purpose: PRAEVAorta 2 assists clinical specialists, physicians, and other licensed practitioners with automatic vascular segmentation and maximum-diameter measurement on adult CT images; results require clinical assessment and physician validation when obtained by a non-physician.
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.