Authorized purpose: TribusConnect provides remote viewing and manipulation of CT DICOM data for pre- and post-cardiac-intervention review, including volume rendering, heart segmentation, simulated fluoroscopy, endoluminal views, MIP, and MPR; it is an adjunct and not diagnostic on mobile devices.
Clinical role
Medical-image viewing, manipulation, measurement, quantification, segmentation, comparison, or reporting support.
Images and patients
CT/CTA · Cardiac anatomy
Key limitation
Keep in mind: Modality, study type, display, timing, mobile, diagnostic, and feature-license limits are release-specific; final decisions remain with qualified professionals.
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: TribusConnect provides remote viewing and manipulation of CT DICOM data for pre- and post-cardiac-intervention review, including volume rendering, heart segmentation, simulated fluoroscopy, endoluminal views, MIP, and MPR; it is an adjunct and not diagnostic on mobile devices.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Cardiac anatomy Input: Supported DICOM or other exact-submission image and study objects from the labeled modalities and workflows.
Who uses it?Intended users: Radiologists, physicians, technologists, and other trained healthcare professionals authorized for the labeled workflow.
What does the software produce?Output: Displayed image series, reformats, measurements, annotations, segmentations, comparisons, or reports for professional review.
What is its most important limitation?Key limitation: Modality, study type, display, timing, mobile, diagnostic, and feature-license limits are release-specific; final decisions remain with qualified professionals.
Clinical takeaway. Clinical role: TribusConnect provides remote viewing and manipulation of CT DICOM data for pre- and post-cardiac-intervention review, including volume rendering, heart segmentation, simulated fluoroscopy, endoluminal views, MIP, and MPR; it is an adjunct and not diagnostic on mobile devices.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification, phantom validation of manual measurements (within 5% of the true value), and retrospective validation of the ML algorithms on 100 CTA volumes from 14 sites across the United States. Heart segmentation, qualitatively evaluated by 2 US board certified radiologists: 100% of cases bone removal correct and 99% with each structure clearly visible. LAA localization versus the predicate device: average distance 4.40 mm; 95 out of 98 cases (97%) within 10 mm. Results are as reported in the FDA submission, not independent validation.
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
TribusConnect provides remote viewing and manipulation of CT DICOM data for pre- and post-cardiac-intervention review, including volume rendering, heart segmentation, simulated fluoroscopy, endoluminal views, MIP, and MPR; it is an adjunct and not diagnostic on mobile devices.
Modality, study type, display, timing, mobile, diagnostic, and feature-license limits are release-specific; final decisions remain with qualified professionals.
The exact FDA document reports software verification, phantom validation of manual measurements (within 5% of the true value), and retrospective validation of the ML algorithms on 100 CTA volumes from 14 sites across the United States. Heart segmentation, qualitatively evaluated by 2 US board certified radiologists: 100% of cases bone removal correct and 99% with each structure clearly visible. LAA localization versus the predicate device: average distance 4.40 mm; 95 out of 98 cases (97%) within 10 mm. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "A test plan was created and executed to ensure that all requirements were implemented according to specifications, and all test cases passed successfully." … "Manual measurements were thoroughly validated using phantom studies, demonstrating that all performance criteria were met, with measurement results falling within 5% of the true value.". Read from the exact FDA decision document on 2026-11-14.
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 exact FDA document reports software verification, phantom validation of manual measurements (within 5% of the true value), and retrospective validation of the ML algorithms on 100 CTA volumes from 14 sites across the United States. Heart segmentation, qualitatively evaluated by 2 US board certified radiologists: 100% of cases bone removal correct and 99% with each structure clearly visible. LAA localization versus the predicate device: average distance 4.40 mm; 95 out of 98 cases (97%) within 10 mm. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "A test plan was created and executed to ensure that all requirements were implemented according to specifications, and all test cases passed successfully." … "Manual measurements were thoroughly validated using phantom studies, demonstrating that all performance criteria were met, with measurement results falling within 5% of the true value.". Read from the exact FDA decision document on 2026-11-14.
No exact submission-linked sensitivity endpoint with a verified population, threshold, tested version, and source was promoted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact submission-linked specificity endpoint with a verified population, threshold, tested version, and source was promoted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K242166 FDA evidence package for TribusConnect
DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
PopulationLabeled population and configuration described in the K242166 FDA decision material
Scopeexact submission
Tested versionTribusConnect configuration described in K242166
IndependenceSponsor or vendor study
K242166
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K242166 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
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: Supported DICOM or other exact-submission image and study objects from the labeled modalities and workflows.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes CT scans uploaded to the server after de-identification and a cloud-based DICOM viewer that uses CT DICOM data to output volume renderings, heart segmentation, simulated fluoroscopy, endo, MIP and MPR views. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "CT scans can be uploaded to the server and will be de-identified before the upload." … "TribusConnect is a cloud-based DICOM viewer designed for medical professionals to securely access, review, manipulate, measure and visualize DICOM images.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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 TribusConnect as provided as a SaaS solution, with a cloud component that performs rendering and a web-based viewer accessible through standard web browsers on desktops, tablets, and mobile devices. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The cloud component performs rendering, provides access to imaging data," … "provided to its users as a Saas solution, TribusMed will be in control of installation, configuration, updates etc.". 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: Displayed image series, reformats, measurements, annotations, segmentations, comparisons, or reports for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Displayed image series, reformats, measurements, annotations, segmentations, comparisons, or reports for professional review.
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 TribusConnect as provided as a SaaS solution, with a cloud component that performs rendering and a web-based viewer accessible through standard web browsers on desktops, tablets, and mobile devices. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The cloud component performs rendering, provides access to imaging data," … "provided to its users as a Saas solution, TribusMed will be in control of installation, configuration, updates etc.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes CT scans uploaded to the server after de-identification and a cloud-based DICOM viewer that uses CT DICOM data to output volume renderings, heart segmentation, simulated fluoroscopy, endo, MIP and MPR views. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "CT scans can be uploaded to the server and will be de-identified before the upload." … "TribusConnect is a cloud-based DICOM viewer designed for medical professionals to securely access, review, manipulate, measure and visualize DICOM images.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Only radiologists, physicians, technologists, and other trained healthcare professionals authorized for the labeled workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Modality, study type, display, timing, mobile, diagnostic, and feature-license limits are release-specific; final decisions remain with qualified professionals.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in reviewed public material; productivity or value claims require local evidence.
Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.
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
27Fields reviewed
12Source 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Installation timeline: Not yet reviewed
Monitoring: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision and checked recall snapshot do not establish a complete local postmarket monitoring protocol. Track version, population, anatomy, protocol, input quality, edits, failures, repeats, downstream effects, downtime, incidents, recalls, and updates locally.
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.