Authorized purpose: VisAble.IO is CT and MR image-processing software for liver-ablation procedures. It imports images from CT and MR scanners and facility PACS systems, assists physicians with ablation-target identification and virtual ablation-needle placement, and assists confirmation of ablation zones.
Radiological images; modality varies or is not specified in FDA list · Liver, hepatic and portal veins, ablation targets, and ablation zones
Key limitation
Keep in mind: The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
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: VisAble.IO is CT and MR image-processing software for liver-ablation procedures. It imports images from CT and MR scanners and facility PACS systems, assists physicians with ablation-target identification and virtual ablation-needle placement, and assists confirmation of ablation zones.
Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Liver, hepatic and portal veins, ablation targets, and ablation zones Input: Supported patient images, DICOM metadata, source-image geometry, and user-selected planning inputs.
Who uses it?Intended users: Qualified surgeons, radiologists, dentists, radiation professionals, and other trained users for the labeled planning workflow.
What does the software produce?Output: Segmentations, models, measurements, templates, needle or implant plans, or planning views for review and approval.
What is its most important limitation?Key limitation: The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
Clinical takeaway. Clinical role: VisAble.IO is CT and MR image-processing software for liver-ablation procedures. It imports images from CT and MR scanners and facility PACS systems, assists physicians with ablation-target identification and virtual ablation-needle placement, and assists confirmation of ablation zones.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing of segmentation post-processing, image registration, and measurement and quantification. Reported results: CT liver segmentation (N 50) Mean DICE 0.98, ablation target (59) 0.82, ablation zone (59) 0.88, liver vessels (100) 0.72; MR liver (25) 0.93, ablation target (50) 0.76; registration MCD for pre-ablation CT to post-ablation CT (46) 4.09 mm and pre-ablation MR to post-ablation CT (25) 4.72 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
VisAble.IO is CT and MR image-processing software for liver-ablation procedures. It imports images from CT and MR scanners and facility PACS systems, assists physicians with ablation-target identification and virtual ablation-needle placement, and assists confirmation of ablation zones.
The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
The exact FDA document reports bench testing of segmentation post-processing, image registration, and measurement and quantification. Reported results: CT liver segmentation (N 50) Mean DICE 0.98, ablation target (59) 0.82, ablation zone (59) 0.88, liver vessels (100) 0.72; MR liver (25) 0.93, ablation target (50) 0.76; registration MCD for pre-ablation CT to post-ablation CT (46) 4.09 mm and pre-ablation MR to post-ablation CT (25) 4.72 mm. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance testing (Bench) was performed on the following features, to ensure that performance and accuracy was as expected: • Segmentation post-processing Testing • Image Registration Testing • Measurement and Quantification Testing" … "CT Processing Liver 50 M: 52% 60.6 US: 32 GE Medical Mean DICE =0.92 Mean DICE =0.98 Segmentation F: 48% OUS: 18 Systems, Siemens Ablation Target 59 M: 54% 60.0 US: 30 GE Medical Mean DICE = 0.70 Mean DICE = 0.82". 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 bench testing of segmentation post-processing, image registration, and measurement and quantification. Reported results: CT liver segmentation (N 50) Mean DICE 0.98, ablation target (59) 0.82, ablation zone (59) 0.88, liver vessels (100) 0.72; MR liver (25) 0.93, ablation target (50) 0.76; registration MCD for pre-ablation CT to post-ablation CT (46) 4.09 mm and pre-ablation MR to post-ablation CT (25) 4.72 mm. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance testing (Bench) was performed on the following features, to ensure that performance and accuracy was as expected: • Segmentation post-processing Testing • Image Registration Testing • Measurement and Quantification Testing" … "CT Processing Liver 50 M: 52% 60.6 US: 32 GE Medical Mean DICE =0.92 Mean DICE =0.98 Segmentation F: 48% OUS: 18 Systems, Siemens Ablation Target 59 M: 54% 60.0 US: 30 GE Medical Mean DICE = 0.70 Mean DICE = 0.82". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K240773 FDA decision evidence for VisAble.IO
DesignFDA 510(k) substantial-equivalence review of the exact submission, device description, indications, and verification or validation documentation.
PopulationLiver, hepatic and portal veins, ablation targets, and ablation zones
Scopeexact submission
Tested versionVisAble.IO
IndependenceSponsor or vendor study
K240773
The FDA decision material is manufacturer-submitted regulatory evidence. 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 K240773 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, surgical, or diagnostic 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 patient images, DICOM metadata, source-image geometry, and user-selected planning inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA indication describes CT and MR import from scanners and facility PACS systems for planning and confirmation; validate patient identity, registration, image geometry, source selection, export, and procedure-room fallback locally.
Scope: Exact FDA submission. The exact FDA material describes this input or interface boundary; local interoperability acceptance remains necessary.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Segmentations, models, measurements, templates, needle or implant plans, or planning views for review and approval.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Segmentations, models, measurements, templates, needle or implant plans, or planning views for review and approval.
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 FDA indication describes CT and MR import from scanners and facility PACS systems for planning and confirmation; validate patient identity, registration, image geometry, source selection, export, and procedure-room fallback locally.
Exact FDA submission
Checked 2026-09-04
The exact FDA material describes this input or interface boundary; local interoperability acceptance remains necessary.
Only qualified surgeons, radiologists, dentists, radiation professionals, and other trained users for the labeled planning workflow should operate or interpret this product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K240773 before acceptance. Later family features are not evidence for this exact submission.
The FDA indication describes CT and MR import from scanners and facility PACS systems for planning and confirmation; validate patient identity, registration, image geometry, source selection, export, and procedure-room fallback locally. Test representative identifiers, geometry, measurements, units, routing, failure handling, and round trips locally.
The exact FDA material does not establish hosting, deployment topology, availability, upgrade path, or service responsibility. Obtain site-specific evidence before procurement.
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. The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
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. No exact-product price was found.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: The FDA indication states that VisAble.IO is not intended for diagnosis and does not predict ablation volumes or ablation success. Planning and treatment-confirmation outputs require physician review and do not replace procedural judgment.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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-20Last searched
33Fields 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 or approved 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
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.
Authorized purpose: Cercare Neurosuite with Capillary Function and Oncology Virtual Expert processes CT or MR information to provide perfusion, tissue-blood-volume, diffusion, labeling, and quantification support for adult brain glioma workflows.
Modality
Radiological images; modality varies or is not specified in FDA list
Authorized purpose: HistoSonics Planning Tool is a stand-alone visualization and comparison tool for CT and MR studies used to plan histotripsy target localization, treatment volume, acoustic path, and patient position.
Modality
Radiological images; modality varies or is not specified in FDA list
Beijing Infervision Healthcare Medical Technology Co., Ltd.
Authorized purpose: InferCare RECIST is a post-processing application for longitudinal medical-image display, lesion measurement, registration, tracking, segmentation, three-dimensional reconstruction, and RECIST reporting by trained professionals.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Tumors and lesions in adult patients age 21 and older
Authorized purpose: MI View&GO is a medical diagnostic application for viewing, manipulating, quantifying, analyzing, and comparing PET, nuclear-medicine, CT, and MR images across one or more time points, including labeled oncology, cardiology, neurology, organ-function, and radiotherapy-planning workflows.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Whole body, organs, tumors, heart, brain, and oncology regions
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.