FDA-cleared profile

VisAble.IO

TechsoMed · CT/CTA · FDA-cleared (510(k))

Authorized purpose: VisAble.IO is a CT image-processing software package for liver-ablation procedures that imports CT images from CT scanners and facility PACS, assists physicians in identifying ablation targets and planning virtual ablation-needle placement, and assists in confirming ablation zones.

Clinical role
CT image processing to support liver-ablation target identification, virtual needle placement, and ablation-zone confirmation.
Images and patients
CT/CTA · Liver and ablation targets
Key limitation
Keep in mind: The exact indication states that the software is not intended for diagnosis, ablation-volume prediction, or ablation-success prediction; physician judgment remains required.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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 a CT image-processing software package for liver-ablation procedures that imports CT images from CT scanners and facility PACS, assists physicians in identifying ablation targets and planning virtual ablation-needle placement, and assists in confirming ablation zones.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Liver and ablation targets Input: CT images imported from compatible CT scanners or facility PACS within the exact labeled workflow.
  • Who uses it?Intended users: Physicians trained in image-guided liver-ablation procedures.
  • What does the software produce?Output: Displayed CT images, target and needle-planning information, and ablation-zone confirmation views.
  • What is its most important limitation?Key limitation: The exact indication states that the software is not intended for diagnosis, ablation-volume prediction, or ablation-success prediction; physician judgment remains required.

Clinical takeaway. Clinical role: VisAble.IO is a CT image-processing software package for liver-ablation procedures that imports CT images from CT scanners and facility PACS, assists physicians in identifying ablation targets and planning virtual ablation-needle placement, and assists in confirming ablation zones.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench performance testing (segmentation post-processing, image registration, measurement and quantification) and algorithm validation against primary performance goals. Primary endpoint mean DICE was 0.98 for liver segmentation (N=50; goal 0.92), 0.80 for ablation target segmentation (N=59), 0.86 for ablation zone segmentation (N=59) and 0.72 for liver vessels segmentation (N=100); PrePost ablation image registration mean corresponding distance was 4.11 mm (N=46; goal 6.06 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 a CT image-processing software package for liver-ablation procedures that imports CT images from CT scanners and facility PACS, assists physicians in identifying ablation targets and planning virtual ablation-needle placement, and assists in confirming ablation zones.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
CT image processing to support liver-ablation target identification, virtual needle placement, and ablation-zone confirmation.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
CT images imported from compatible CT scanners or facility PACS within the exact labeled workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Displayed CT images, target and needle-planning information, and ablation-zone confirmation views.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Interventional radiology or other labeled liver-ablation planning environment.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Physicians trained in image-guided liver-ablation procedures.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
The exact indication states that the software is not intended for diagnosis, ablation-volume prediction, or ablation-success prediction; physician judgment remains required.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports bench performance testing (segmentation post-processing, image registration, measurement and quantification) and algorithm validation against primary performance goals. Primary endpoint mean DICE was 0.98 for liver segmentation (N=50; goal 0.92), 0.80 for ablation target segmentation (N=59), 0.86 for ablation zone segmentation (N=59) and 0.72 for liver vessels segmentation (N=100); PrePost ablation image registration mean corresponding distance was 4.11 mm (N=46; goal 6.06 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" … "The following table provides a summary of the validation results: 6 Algorithm N Gender Mean N per CT Brand Primary Primary Endpoint Age Region Performance Goal Liver 50 M: 52% 60.6 US: 32 GE Medical Mean DICE =0.92 Mean DICE =0.98". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

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 performance testing (segmentation post-processing, image registration, measurement and quantification) and algorithm validation against primary performance goals. Primary endpoint mean DICE was 0.98 for liver segmentation (N=50; goal 0.92), 0.80 for ablation target segmentation (N=59), 0.86 for ablation zone segmentation (N=59) and 0.72 for liver vessels segmentation (N=100); PrePost ablation image registration mean corresponding distance was 4.11 mm (N=46; goal 6.06 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" … "The following table provides a summary of the validation results: 6 Algorithm N Gender Mean N per CT Brand Primary Primary Endpoint Age Region Performance Goal Liver 50 M: 52% 60.6 US: 32 GE Medical Mean DICE =0.92 Mean DICE =0.98". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact-submission and version-linked sensitivity endpoint is promoted; candidate or product-family values were not substituted.

Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact-submission and version-linked specificity endpoint is promoted; candidate or product-family values were not substituted.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

FDA submission-specific verification and validation evidence for K223639

  • DesignFDA 510(k) regulatory decision material and submission-specific verification or validation evidence for K223639; this is regulatory evidence, not an independent clinical effectiveness study.
  • PopulationThe labeled population, anatomy, images, and test materials described in the exact FDA decision material for K223639; a broader clinical population is not established here.
  • Scopeexact submission
  • Tested versionVisAble.IO (K223639)
  • IndependenceSponsor or vendor study

K223639

The exact FDA material is submission-specific and should not be generalized to other versions, enabled options, sites, protocols, or clinical outcomes.

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
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 & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: CT images imported from compatible CT scanners or facility PACS within the exact labeled workflow.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA 510(k) decision material K223639: VisAble.IO

  2. Routing

    Source context, not route validation: The exact FDA indication identifies CT import from scanners and facility PACS; local identity matching, routing, export, and procedural display require validation.

    Scope: Exact FDA submission.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-04 · FDA 510(k) decision material K223639: VisAble.IO

  3. AI processing

    Source context, not route validation: The exact FDA package describes VisAble.IO as a software system that runs on a dedicated computer for display and processing of CT images, including contrast-enhanced images. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The software system runs on a dedicated computer and is intended for display and processing, of a Computed Tomography (CT), including contrast enhanced images.". 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.

    Field checked 2026-11-14 · FDA 510(k) decision material K223639: VisAble.IO

  4. Returned objects

    Source context, not route validation: Displayed CT images, target and needle-planning information, and ablation-zone confirmation views.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA 510(k) decision material K223639: VisAble.IO

  5. Viewer/worklist/report

    Unresolved route: Displayed CT images, target and needle-planning information, and ablation-zone confirmation views.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K223639: VisAble.IO

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The exact FDA package describes VisAble.IO as a software system that runs on a dedicated computer for display and processing of CT images, including contrast-enhanced images. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The software system runs on a dedicated computer and is intended for display and processing, of a Computed Tomography (CT), including contrast enhanced images.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact FDA indication identifies CT import from scanners and facility PACS; local identity matching, routing, export, and procedural display require validation.
  • Exact FDA submission
  • Checked 2026-09-04

Workflow role

CT image processing to support liver-ablation target identification, virtual needle placement, and ablation-zone confirmation.

exact submission · checked 2026-09-04

Submission-anchored workflow summary, not a local acceptance or deployment result.

Input

CT images imported from compatible CT scanners or facility PACS within the exact labeled workflow.

exact submission · checked 2026-09-04

Exact supported inputs and protocol limits must be confirmed from the complete labeling.

Output

Displayed CT images, target and needle-planning information, and ablation-zone confirmation views.

exact submission · checked 2026-09-04

Output review, editing, approval, export, and downstream use remain release- and site-specific.

Deployment evidence

Exact deployment topology and operational boundaries remain unestablished.

exact submission · checked 2026-09-04

Confirm hosting, PHI flow, retention, access, updates, downtime, and support obligations before procurement or clinical use.

Integration evidence

The exact FDA indication identifies CT import from scanners and facility PACS; local identity matching, routing, export, and procedural display require validation.

exact submission · checked 2026-09-04

Validate the local workflow against the exact release and enabled options.

Vendor family context

Current vendor material is product-family context for K223639 only; exact release, enabled options, deployment, security, interoperability, pricing, and local workflow require confirmation.

product family · checked 2026-09-04

Vendor material is not exact-release evidence unless that linkage is separately proven.

Sources & review details FDA 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.

FDA submission
K223639
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Liver and ablation targets
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2023-08-28
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
31Fields reviewed
13Source 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, vendor product page, implementation documentation, reimbursement policy, peer reviewed literature, clinical trial registry, 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 exact-release price, license fee, subscription, contract, or implementation cost 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 applicable - checked 2026-09-04 - Not applicable

    CMS coverage-index context was checked, but no product-specific coverage or reimbursement determination is inferred.

  • 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 sources reviewed here do not establish the complete exact-release security posture, including identity, audit, encryption, retention, remote access, vulnerability management, backup, or incident response.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-10-27 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-10-27 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

7 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K223639: VisAble.IO

    U.S. Food and Drug Administration - Published 2023-08-28 - Accessed 2026-09-04

    Scope: identity, productIdentity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  5. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. TechsoMed ablation planning family context

    TechsoMed - Accessed 2026-09-04

    Scope: productFamilyContext

Research history

  1. K223639 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K252992

CT Rembra RT; CT Areta RT; CT Rembra

Philips Healthcare (Suzhou) Co., Ltd.

Authorized purpose: CT Rembra RT, CT Areta RT, and CT Rembra support whole-body diagnostic imaging, oncology, radiotherapy planning, interventional, vascular, neurological, cardiovascular, and qualified lung-screening workflows for all ages.

Modality
CT/CTA
Anatomy
Multi-region
Decision
2026-03-23
FDA-cleared K252970

BriefCase-Triage: CARE Multi-triage CT Body

Aidoc Medical, Ltd.

Authorized purpose: Adult contrast-enhanced and non-contrast CT triage for 11 chest, abdominal, and pelvic findings: diverticulitis, abdominal-pelvic abscess, appendicitis, intestinal ischemia/pneumatosis, obstructive renal stone, small- and large-bowel obstruction, spleen injury, liver injury, kidney injury, and pelvic fracture.

Modality
CT/CTA
Anatomy
Chest, Abdomen, and Pelvis
Decision
2026-01-07
FDA-cleared K252029

AI-CVD

HeartLung Corporation

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.

Modality
CT/CTA
Anatomy
Chest, abdomen, heart, lungs, liver, aorta, pulmonary artery, bone, muscle, and fat
Decision
2025-12-19
FDA-cleared K242624

Medical Image Post-processing Software (uOmnispace.CT)

Shanghai United Imaging Healthcare Co., Ltd.

Authorized purpose: uOmnispace.CT provides healthcare institutions with tools to view, manipulate, evaluate, and analyze medical CT images, including colon, lung, vessel, brain, cardiac, liver, rib, spine, dual-energy, perfusion, and cardiovascular applications described in the exact FDA submission.

Modality
CT/CTA
Anatomy
Colon, lungs and airway, vessels, brain, heart, liver, ribs, spine, and other CT regions
Decision
2025-05-14

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history