Limbus Contour
K201232Limbus AI Inc. · cleared 2020-08-13 · product code LLZ · Radiology
Premarket evidence — what FDA accepted
source quote (p.3)
“Limbus Contour is a software-only medical device intended for use by trained radiation oncologists, dosimetrists and physicists to derive optimal contours for input to radiation treatment planning.”
source quote (p.4)
“It is a single purposes cross-platform application for automatic contouring (segmentation) of CT/MRI DICOM images via pre-trained and expert curated machine learning models. The software is intended to be used by trained medical professionals to derive contours for input to radiation treatment planning. The Limbus Contour software segments normal tissues using machine learning models and further post-processing on machine learning model prediction outputs.”
Validation studies (1)
Bench
sample size not stated
endpoints: Automatic Contouring – Validation Test
standards: FDA's Guidance for Industry and FDA Staff, “Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices.”
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
- re_clearance
The FDA AI/ML device list shows a newer 510(k) K241837 (decision 2024-10-09) from Limbus AI Inc. for a matching device line ("Limbus Contour") — a new clearance for the same line is a change event.
first seen 2026-07-08 · k_number:K241837
- re_clearance
The FDA AI/ML device list shows a newer 510(k) K230575 (decision 2023-04-07) from Limbus AI Inc. for a matching device line ("Limbus Contour") — a new clearance for the same line is a change event.
first seen 2026-07-08 · k_number:K230575
- adverse_event_inflection
MAUDE adverse-event reports for product code LLZ: 295 in the 12 months ending 2026-06, vs a 37.7/12mo average over the prior 3 windows (+683%). Code-level count — reports are not attributed to this specific device.
first seen 2026-07-08 · openFDA /device/event.json count=date_received product_code=LLZ
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (GE Medical Systems SCS, initiated 2026-05-08): "GE HealthCare has become aware of a context synchronization issue in AW Server 3.2 ext. 6.5. When a user selects a patient or exam in the AW Server Web Client worklist and launches" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:99042
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (PHILIPS MEDICAL SYSTEMS NEDERLAND B.V. Veenpluis 4-6 Best Netherlands, initiated 2026-03-05): "Potential that mis-ordered frames in Vue Motion during dynamic cine runs may cause images frames to display out of sequence." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98520
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (GE Medical Systems, LLC, initiated 2026-01-30): "There is a potential cybersecurity vulnerability affecting certain versions of Centricity Universal Viewer. User login credentials may be exposed on the local client workstation, w" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98428
- …and 22 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).