Hepatic VCAR

K193281

GE Medical Systems SCS · cleared 2020-03-20 · product code JAK · Radiology

Premarket evidence — what FDA accepted

Device typesamd
source quote (p.3)
Hepatic VCAR is a CT image analysis software package that allows the analysis and visualization of Liver CT data derived from DICOM 3.0 compliant CT scans.
Algorithmdeep learning convolutional neural networks
source quote (p.5)
The modified Hepatic VCAR employs two deep learning convolutional neural networks to segment the liver contour and the hepatic artery on CT liver exams while the predicate device uses a traditional deterministic method to segment the liver and manual tools to segment the vascular structure including the hepatic artery.
Adaptive (vs locked)FDA source did not state this
PCCPNo
Cybersecurity addressedNo

Validation studies (2)

Bench

sample size not stated

standards: ISO 13485

Reader study (MRMC)

sample size not stated

endpoints: capability of liver segmentation and hepatic artery segmentation

standards: ISO 13485

Reported performance (0 observations)

FDA source did not state a quantitative performance metric — non-reporting is itself the signal.

Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.

Predicate network

Postmarket — what happened after clearance

75
recalls in product code, 24mo
192
MAUDE reports in code, 12mo
-22%
vs code's own 3-yr baseline
9
drift signals on this device
  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (GE Medical Systems, LLC, initiated 2026-03-26): "GE HealthCare has become aware of a potential security vulnerability impacting AW Server deployed via Edison Health Link (EHL) based CT Smart Subscription used in conjunction with " Recalling firm matches this device's applicant.

    first seen 2026-07-08 · recall res_event_number:98738

  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (PHILIPS MEDICAL SYSTEMS, initiated 2026-03-07): "Philips has identified three software issues: 1. During a continuous CT (CCT) scan, there is the potential that the Gantry could remain at the current scan position after pressing" Recalling firm is another firm in the same product code.

    first seen 2026-07-08 · recall res_event_number:98588

  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (Siemens Medical Solutions USA, Inc, initiated 2025-12-19): "To remove the software applications from certain CT systems as the applications have not received FDA 510(k) clearance." Recalling firm is another firm in the same product code.

    first seen 2026-07-08 · recall res_event_number:98206

  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (PHILIPS MEDICAL SYSTEMS, initiated 2025-09-25): "Issue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axia" Recalling firm is another firm in the same product code.

    first seen 2026-07-08 · recall res_event_number:97699

  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (Philips North America Llc, initiated 2025-05-29): "Devices with affected software may experience two unintended motion issues that may lead to contact between the Gantry or table with the operator or patient, along with additional " Recalling firm is another firm in the same product code.

    first seen 2026-07-08 · recall res_event_number:97010

  • recall_reason_pattern

    Software/algorithm-related recall in product code JAK (, initiated 2025-05-23): "Due to a software bug the robotic arm may incorrectly guide the instrument compared to the planning defined by user." Recalling firm is another firm in the same product code.

    first seen 2026-07-08 · recall res_event_number:96967

  • …and 3 more.

Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.

Reimbursement — how devices like this got paid

Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).

RIGOR™ Precedent · public FDA/CMS data · descriptive decision-support, not regulatory or reimbursement advice. Share this page: radar.healthai.com/precedent/device/K193281