Authorized purpose: Visualization, measurement, pre-procedural planning and sizing, and post-procedural evaluation for left atrial appendage closure (LAAC); the software is a planning and assessment aid and not a diagnostic replacement.
Clinical role
Pre- and post-procedural LAAC planning support with machine-learning left-heart segmentation and landing-zone initialization, user review and correction, manual measurements and annotations, simulated TEE/ICE/fluoroscopic views, and reporting.
Images and patients
CT/CTA · Left atrial appendage and adjacent cardiac and extracardiac cardiovascular structures
Key limitation
Keep in mind: TruPlan is a pre-procedural planning aid and post-procedural assessment aid, not a diagnostic replacement; LAAC decisions and procedures must follow the selected LAAC device's approved IFU. No measurements are computed from landing-zone initialization until the user reviews and corrects it, and measurements are manually placed and user-modifiable. The FDA validation used 533 left-heart-segmentation samples and 100 landing-zone samples; the packet does not establish performance outside the specified CT workflow or local interfaces.
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: Visualization, measurement, pre-procedural planning and sizing, and post-procedural evaluation for left atrial appendage closure (LAAC); the software is a planning and assessment aid and not a diagnostic replacement.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Left atrial appendage and adjacent cardiac and extracardiac cardiovascular structures Input: Pre-existing vendor-independent CT data in DICOM format, manually uploaded by the end user, for adult patients undergoing or having undergone a left atrial appendage closure procedure.
Who uses it?Intended users: Qualified users, including physicians involved in LAAC pre-procedural planning and post-procedural follow-up
What does the software produce?Output: A 3D rendering of the left heart including the left ventricle, left atrium, and left atrial appendage; semi-automatic landing-zone initialization; 2D, 3D, MPR, simulated TEE, ICE, and fluoroscopic views; user-placed measurements of distance, perimeter, area, angle, signal intensity, and coordinates; annotations; and screenshots and measurements captured in a PDF report.
What is its most important limitation?Key limitation: TruPlan is a pre-procedural planning aid and post-procedural assessment aid, not a diagnostic replacement; LAAC decisions and procedures must follow the selected LAAC device's approved IFU. No measurements are computed from landing-zone initialization until the user reviews and corrects it, and measurements are manually placed and user-modifiable. The FDA validation used 533 left-heart-segmentation samples and 100 landing-zone samples; the packet does not establish performance outside the specified CT workflow or local interfaces.
Clinical takeaway. Clinical role: Visualization, measurement, pre-procedural planning and sizing, and post-procedural evaluation for left atrial appendage closure (LAAC); the software is a planning and assessment aid and not a diagnostic replacement.
Evidence takeaway. Evidence from the reviewed source record: FDA validation used 633 anonymized patient images across multiple sites: 533 samples for left-heart segmentation and 100 for landing-zone detection, with validation data independent of training. Left-heart testing showed bone removal in 532/533 cases (99.81%) and correct left-atrial-appendage visualization in 519/533 cases (97.37%). Landing-zone testing found the plane distance within 10 mm in 97/100 cases (97%, mean 3.87 mm) and the contour-center distance within 12 mm in 99/100 cases (99%, mean 2.92 mm). The FDA summary states that no clinical studies were necessary for substantial equivalence; these are visualization, segmentation, and measurement-agreement endpoints, not device-level sensitivity or specificity.
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
Visualization, measurement, pre-procedural planning and sizing, and post-procedural evaluation for left atrial appendage closure (LAAC); the software is a planning and assessment aid and not a diagnostic replacement.
Pre- and post-procedural LAAC planning support with machine-learning left-heart segmentation and landing-zone initialization, user review and correction, manual measurements and annotations, simulated TEE/ICE/fluoroscopic views, and reporting.
Pre-existing vendor-independent CT data in DICOM format, manually uploaded by the end user, for adult patients undergoing or having undergone a left atrial appendage closure procedure.
A 3D rendering of the left heart including the left ventricle, left atrium, and left atrial appendage; semi-automatic landing-zone initialization; 2D, 3D, MPR, simulated TEE, ICE, and fluoroscopic views; user-placed measurements of distance, perimeter, area, angle, signal intensity, and coordinates; annotations; and screenshots and measurements captured in a PDF report.
Hospital infrastructure or a clinical desktop/workstation used for LAAC planning and post-procedural follow-up; the FDA packet does not establish a more specific facility type.
TruPlan is a pre-procedural planning aid and post-procedural assessment aid, not a diagnostic replacement; LAAC decisions and procedures must follow the selected LAAC device's approved IFU. No measurements are computed from landing-zone initialization until the user reviews and corrects it, and measurements are manually placed and user-modifiable. The FDA validation used 533 left-heart-segmentation samples and 100 landing-zone samples; the packet does not establish performance outside the specified CT workflow or local interfaces.
FDA validation used 633 anonymized patient images across multiple sites: 533 samples for left-heart segmentation and 100 for landing-zone detection, with validation data independent of training. Left-heart testing showed bone removal in 532/533 cases (99.81%) and correct left-atrial-appendage visualization in 519/533 cases (97.37%). Landing-zone testing found the plane distance within 10 mm in 97/100 cases (97%, mean 3.87 mm) and the contour-center distance within 12 mm in 99/100 cases (99%, mean 2.92 mm). The FDA summary states that no clinical studies were necessary for substantial equivalence; these are visualization, segmentation, and measurement-agreement endpoints, not device-level sensitivity or specificity.
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 validation used 633 anonymized patient images across multiple sites: 533 samples for left-heart segmentation and 100 for landing-zone detection, with validation data independent of training. Left-heart testing showed bone removal in 532/533 cases (99.81%) and correct left-atrial-appendage visualization in 519/533 cases (97.37%). Landing-zone testing found the plane distance within 10 mm in 97/100 cases (97%, mean 3.87 mm) and the contour-center distance within 12 mm in 99/100 cases (99%, mean 2.92 mm). The FDA summary states that no clinical studies were necessary for substantial equivalence; these are visualization, segmentation, and measurement-agreement endpoints, not device-level sensitivity or specificity.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
TruPlan Computed Tomography (CT) Imaging Software regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K222593
Samplen=633
IndependenceIndependence not established
K222593
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 K222593. 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: Pre-existing vendor-independent CT data in DICOM format, manually uploaded by the end user, for adult patients undergoing or having undergone a left atrial appendage closure procedure.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The packet describes manual upload of pre-existing DICOM CT images and installation either as standalone software on a desktop or laptop or as a server within hospital infrastructure with a thick-client application on user computers. DICOM compliance and PDF reporting are described, but a specific PACS, RIS, EHR, interface version, or current local compatibility is not established.
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: The exact FDA package describes TruPlan installed either as standalone software on the user's desktop or laptop computer, or as a server within the hospital infrastructure with thick-client software on multiple users' desktop or laptop computers. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "TruPlan is installed either as a standalone software onto the user’s desktop or laptop computer," … "or as a server within the hospital infrastructure with a thick-client software on multiple users’ desktop or laptop computers.". 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: A 3D rendering of the left heart including the left ventricle, left atrium, and left atrial appendage; semi-automatic landing-zone initialization; 2D, 3D, MPR, simulated TEE, ICE, and fluoroscopic views; user-placed measurements of distance, perimeter, area, angle, signal intensity, and coordinates; annotations; and screenshots and measurements captured in a PDF report.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A 3D rendering of the left heart including the left ventricle, left atrium, and left atrial appendage; semi-automatic landing-zone initialization; 2D, 3D, MPR, simulated TEE, ICE, and fluoroscopic views; user-placed measurements of distance, perimeter, area, angle, signal intensity, and coordinates; annotations; and screenshots and measurements captured in a PDF report.
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 TruPlan installed either as standalone software on the user's desktop or laptop computer, or as a server within the hospital infrastructure with thick-client software on multiple users' desktop or laptop computers. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "TruPlan is installed either as a standalone software onto the user’s desktop or laptop computer," … "or as a server within the hospital infrastructure with a thick-client software on multiple users’ desktop or laptop computers.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The packet describes manual upload of pre-existing DICOM CT images and installation either as standalone software on a desktop or laptop or as a server within hospital infrastructure with a thick-client application on user computers. DICOM compliance and PDF reporting are described, but a specific PACS, RIS, EHR, interface version, or current local compatibility is not established.
ACR AI Central provides an exact-submission model card for TruPlan Computed Tomography (CT) Imaging Software; 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
9Source 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, 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 K222593 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.
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-08 - 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-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: 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.
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.