Authorized purpose: Cardiac CT segmentation, measurement and valve-intervention planning
Clinical role
Segmentation or contouring; measurement and planning support
Images and patients
CT/CTA · Heart/Cardiovascular
Key limitation
Keep in mind: Automated segmentations and measurements can be reviewed and adjusted manually. Clinical validation described patients aged 62 and older.
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: Cardiac CT segmentation, measurement and valve-intervention planning
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Heart/Cardiovascular Input: DICOM-compliant CT images of heart and vessels for aortic, mitral and tricuspid valve intervention planning
Who uses it?Intended users: Cardiologists, radiologists, heart surgeons and healthcare professionals
What does the software produce?Output: Cardiovascular and calcification segmentations; splines, distances, angulation and volume measurements; MPR and surface-rendered views; assessments and PDF planning reports
What is its most important limitation?Key limitation: Automated segmentations and measurements can be reviewed and adjusted manually. Clinical validation described patients aged 62 and older.
Evidence takeaway. Evidence from the reviewed source record: Multicenter standalone observational evaluation of 60 CT cases, divided equally across aortic, mitral and tricuspid planning; expert manual measurements using 3mensio served as comparator. Patients were aged 62-97; 45% were male.
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
Cardiac CT segmentation, measurement and valve-intervention planning
Cardiovascular and calcification segmentations; splines, distances, angulation and volume measurements; MPR and surface-rendered views; assessments and PDF planning reports
Multicenter standalone observational evaluation of 60 CT cases, divided equally across aortic, mitral and tricuspid planning; expert manual measurements using 3mensio served as comparator. Patients were aged 62-97; 45% were male.
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
Multicenter standalone observational evaluation of 60 CT cases, divided equally across aortic, mitral and tricuspid planning; expert manual measurements using 3mensio served as comparator. Patients were aged 62-97; 45% were male.
Reviewed measurement-comparison evidence does not establish a general diagnostic sensitivity.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-05
A diagnostic specificity was not established in the reviewed planning study.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K242500 cardiac CT planning performance study
DesignMulticenter observational standalone comparison against expert 3mensio measurements
Population20 aortic, 20 mitral and 20 tricuspid CT cases; age 62-97
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
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-compliant CT images of heart and vessels for aortic, mitral and tricuspid valve intervention planning
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes LARALAB as cloud-based, with cloud-based access as a new feature versus its predicate, requiring patient data to be uploaded rather than imported directly from a PACS. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "While LARALAB introduces new features, such as cloud-based access and automatic preprocessing through deep learning algorithms" … "The limited difference is due to the cloud-based nature of the subject device, which requires that patient data be uploaded, as opposed to directly importing data from a PACS system, into the local predicate device.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Cardiovascular and calcification segmentations; splines, distances, angulation and volume measurements; MPR and surface-rendered views; assessments and PDF planning reports
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cardiovascular and calcification segmentations; splines, distances, angulation and volume measurements; MPR and surface-rendered views; assessments and PDF planning 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.
The exact FDA package describes LARALAB as cloud-based, with cloud-based access as a new feature versus its predicate, requiring patient data to be uploaded rather than imported directly from a PACS. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "While LARALAB introduces new features, such as cloud-based access and automatic preprocessing through deep learning algorithms" … "The limited difference is due to the cloud-based nature of the subject device, which requires that patient data be uploaded, as opposed to directly importing data from a PACS system, into the local predicate device.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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-05Last searched
21Fields reviewed
11Source classes checked
1Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
PMID40155128 identifies the family planning tool in a single case and is retained contextually. NCT06951126 stored metadata concerns CT prediction for transcatheter tricuspid interventions; exact product/version applicability remains unestablished. Registry page returned a JavaScript shell; no trial outcomes promoted. The current discovery snapshot contains 1 PubMed and 1 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, literature index, peer reviewed publication, trial registry, recall database, 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-05 - Exact FDA submission
Reviewed vendor pages did not establish a dated exact-version license or planning-case rate.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "Laralab reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. No result was a vendor or payer page naming this product with coding or payment; any results were general billing guidance. This records what was found, not that none exists.
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-05 - Exact FDA submission
FDA-described access/encryption controls are not a current scoped security certification. Hosting region, retention, contractual data controls and dated attestations were not established.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-05 - Exact FDA submission
User qualification requirements beyond intended-user categories and the contracted onboarding package remain to be confirmed.
Monitoring: Not verified - checked 2026-09-05 - Exact FDA submission
Site acceptance should address segmentation corrections and report transfer; this is editorial guidance, not a verified monitoring capability.
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: 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.
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.