TOMTEC-ARENA quantifies and reports cardiovascular, fetal, and abdominal structures and functions from supported clinical images and can exchange data with IMAGE-ARENA and third-party applications.
Clinical role
Medical-image processing, measurement, quantification, visualization, and reporting support.
Images and patients
Ultrasound · Heart/Cardiovascular
Key limitation
AI-assisted or semi-automated measurements require professional review and editing. The named release should not be generalized to unrelated TOMTEC modules, third-party image types, or mammography workflows.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyUltrasound · Heart/Cardiovascular
Workflow roleMedical-image processing, measurement, quantification, visualization, and reporting support.
Required inputSupported DICOM images and release-specific user inputs.
Output and human actionMeasurements, segmentations, visualizations, calculations, and reports for professional review.
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
TOMTEC-ARENA quantifies and reports cardiovascular, fetal, and abdominal structures and functions from supported clinical images and can exchange data with IMAGE-ARENA and third-party applications.
AI-assisted or semi-automated measurements require professional review and editing. The named release should not be generalized to unrelated TOMTEC modules, third-party image types, or mammography workflows.
K201632 reports software, data-transfer, quantification, reporting, and compatibility verification and validation; the FDA summary does not identify a new clinical study. The device is not intended for primary mammography interpretation.
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
K201632 reports software, data-transfer, quantification, reporting, and compatibility verification and validation; the FDA summary does not identify a new clinical study. The device is not intended for primary mammography interpretation.
Sensitivity is not the primary endpoint for this system, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-03
Specificity is not the primary endpoint for this system, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K201632 FDA performance package for TOMTEC-ARENA
DesignManufacturer software, quantification, reporting, data-transfer, and compatibility verification and validation
PopulationCardiovascular, fetal, and abdominal ultrasound quantification and reporting workflows
Scopeexact submission
Tested versionTOMTEC-ARENA
IndependenceSponsor or vendor study
K201632
Manufacturer evidence submitted for FDA clearance or approval; local clinical, technical, and workflow acceptance remains necessary.
5 unlinked candidate evidence records are retained for source review and excluded from this evidence display.
Safety and lifecycle
Postmarket record
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 K201632 by exact submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-03
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 images and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.
Scope: Product family. Current vendor materials are product-family evidence for K201632; confirm the exact cleared version, enabled options, deployment, and local compatibility.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Software on a workstation, server, or supported virtual environment with release-specific licenses.
Scope: Product family. Current vendor materials are product-family evidence for K201632; confirm the exact cleared version, enabled options, deployment, and local compatibility.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Measurements, segmentations, visualizations, calculations, and 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.
Software on a workstation, server, or supported virtual environment with release-specific licenses.
Product family
Checked 2026-09-03
Current vendor materials are product-family evidence for K201632; confirm the exact cleared version, enabled options, deployment, and local compatibility.
DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.
Product family
Checked 2026-09-03
Current vendor materials are product-family evidence for K201632; confirm the exact cleared version, enabled options, deployment, and local compatibility.
Only qualified imaging professionals and physicians trained for the represented anatomy and workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
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. Track these product-specific limits: AI-assisted or semi-automated measurements require professional review and editing. The named release should not be generalized to unrelated TOMTEC modules, third-party image types, or mammography workflows.
Product family
Checked 2026-09-03
Current vendor materials are product-family evidence for K201632; confirm the exact cleared version, enabled options, deployment, and local compatibility.
DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.
product family · checked 2026-09-03
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally. Vendor statements are current product-family context; confirm the exact cleared release and installed options.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. AI-assisted or semi-automated measurements require professional review and editing. The named release should not be generalized to unrelated TOMTEC modules, third-party image types, or mammography workflows.
exact submission · checked 2026-09-03
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-03
No exact-product price was found in the reviewed public material; vendor productivity claims are scenario inputs, not guaranteed local savings.
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. Track these product-specific limits: AI-assisted or semi-automated measurements require professional review and editing. The named release should not be generalized to unrelated TOMTEC modules, third-party image types, or mammography workflows.
product family · checked 2026-09-03
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. Vendor statements are current product-family context; confirm the exact cleared release and installed options.
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-04Last searched
25Fields reviewed
12Source classes checked
15Awaiting review PubMed leads
2Awaiting review trial leads
0Unreviewed FDA recall leads
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA decision materials were reviewed for identity, indication, users, workflow, limitations, and submitted performance. Current vendor material is labeled product-family context where it does not establish the exact release. PubMed and ClinicalTrials.gov results are retained as candidate evidence with version applicability pending; CMS reimbursement context and exact-identifier openFDA postmarket results were also checked. Pricing, final security architecture, contracted services, enabled options, and local interoperability remain organization-specific evidence. Automated exact-name discovery found 15 PubMed and 2 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, acr ai central product, fda decision material, vendor product page, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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-03 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license 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 verified - checked 2026-09-03 - 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.
Ligence Heart is a fully automated software platform that processes, analyses and makes measurements on acquired transthoracic cardiac ultrasound images, automatically producing a full report with measurements of several key cardiac structural and functional parameters. The data produced by this software is intended to be used to support qualified cardiologists or sonographers for clinical decision making. Ligence Heart is indicated for use in adult patients. Ligence Heart has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g., tumors, thrombi). Limitations: Poor image capture will lead to poor annotations and subsequent measurements. Multiple image quality algorithms are used to filter out images of poor quality. Our software complements good patient care and does not exempt the user from the responsibility to provide supervision, clinically review the patient, and make appropriate clinical decisions. If no gender is present, female referenced guideline values will be used for conclusions. If Body Surface Area (BSA) is not present, indexed values cannot be provided. During image acquisition, inappropriate use of the echo machine, use of non-cardiac ultrasound probes, or use of suboptimal settings (e.g., gain, contrast, depth) may lead to lower accuracy of the software. Ligence Heart has not been validated in patients with prosthetic or surgically altered cardiac valves, implantable intracardiac devices, or irregular (non-sinus) rhythm; these conditions may affect automated measurement accuracy.
Authorized purpose: PVAD IQ supports qualified-physician clinical decision support by identifying the aortic annulus and PVAD inlet, calculating their mean distance, and identifying clips acceptable for this measurement.
Authorized purpose: Automated echocardiographic LV and RV function, wall-motion and strain, bladder-volume and image-quality measurements for clinician 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.