Authorized purpose: Post-processing segmentation, measurement, threshold labeling, and export of quantitative lumbar-spine measurements to support clinical review; not diagnosis.
Clinical role
Post-processing segmentation and measurement support with user-controlled thresholds and clinician review before reporting or interpretation
Images and patients
X-ray/Radiography · Lumbar spine, including vertebrae and sacrum
Key limitation
Keep in mind: The output is a starting point for clinical workflow and is not a diagnosis or treatment recommendation. Users confirm or modify settings and review measurements. Use is limited to adult DICOM x-ray images; pregnancy, post-operative complications, tumors, and infections are unsupported.
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: Post-processing segmentation, measurement, threshold labeling, and export of quantitative lumbar-spine measurements to support clinical review; not diagnosis.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Lumbar spine, including vertebrae and sacrum Input: Previously acquired DICOM lumbar-spine radiograph x-ray images from patients aged 18 or older; the labeled input excludes pregnancy, post-operative complications, tumors, and infections.
Who uses it?Intended users: Radiologists and neuro- and spine surgeons at hospitals and other medical institutions
What does the software produce?Output: Segmentation of vertebrae and sacrum; quantitative spine and spondylolisthesis-slippage measurements; threshold-based labeling of out-of-range measurements; and exportable measurement results.
What is its most important limitation?Key limitation: The output is a starting point for clinical workflow and is not a diagnosis or treatment recommendation. Users confirm or modify settings and review measurements. Use is limited to adult DICOM x-ray images; pregnancy, post-operative complications, tumors, and infections are unsupported.
Clinical takeaway. Clinical role: Post-processing segmentation, measurement, threshold labeling, and export of quantitative lumbar-spine measurements to support clinical review; not diagnosis.
Evidence takeaway. Evidence from the reviewed source record: FDA packet: software verification/validation plus an external clinical-data software performance assessment of 100 image studies from 100 patients across different genders, ages, and racial groups. Software output and physician-with/without-software output were compared with ground truth defined by three radiologists for segmentations and measurements; no numeric sensitivity, specificity, or AUC was disclosed.
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
Post-processing segmentation, measurement, threshold labeling, and export of quantitative lumbar-spine measurements to support clinical review; not diagnosis.
Segmentation of vertebrae and sacrum; quantitative spine and spondylolisthesis-slippage measurements; threshold-based labeling of out-of-range measurements; and exportable measurement results.
The output is a starting point for clinical workflow and is not a diagnosis or treatment recommendation. Users confirm or modify settings and review measurements. Use is limited to adult DICOM x-ray images; pregnancy, post-operative complications, tumors, and infections are unsupported.
FDA packet: software verification/validation plus an external clinical-data software performance assessment of 100 image studies from 100 patients across different genders, ages, and racial groups. Software output and physician-with/without-software output were compared with ground truth defined by three radiologists for segmentations and measurements; no numeric sensitivity, specificity, or AUC was disclosed.
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
FDA packet: software verification/validation plus an external clinical-data software performance assessment of 100 image studies from 100 patients across different genders, ages, and racial groups. Software output and physician-with/without-software output were compared with ground truth defined by three radiologists for segmentations and measurements; no numeric sensitivity, specificity, or AUC was disclosed.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
CoLumboX regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K250367
Samplen=100
IndependenceIndependence not established
K250367
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K250367. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: Previously acquired DICOM lumbar-spine radiograph x-ray images from patients aged 18 or older; the labeled input excludes pregnancy, post-operative complications, tumors, and infections.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Processes previously acquired DICOM images and exports measurement results; the FDA packet does not establish a specific PACS, RIS, or EHR interface or a GE-only restriction.
Scope: Exact FDA submission.
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 document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-11-14 ·
Returned objects
Source context, not route validation: Segmentation of vertebrae and sacrum; quantitative spine and spondylolisthesis-slippage measurements; threshold-based labeling of out-of-range measurements; and exportable measurement results.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Segmentation of vertebrae and sacrum; quantitative spine and spondylolisthesis-slippage measurements; threshold-based labeling of out-of-range measurements; and exportable measurement results.
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.
Processes previously acquired DICOM images and exports measurement results; the FDA packet does not establish a specific PACS, RIS, or EHR interface or a GE-only restriction.
Smart Soft Healthcare announces on the CoLumbo product site that the company received ISO/IEC 27001 certification (stated as ISO/IEC 27001:2017) for its information security management system, covering development and delivery of AI-powered medical imaging solutions such as CoLumbo AI Spine Assistant.
Vendor-wide
Checked 2026-10-27
Vendor statement on the official CoLumbo product site operated for Smart Soft Healthcare (the page states CoLumbo is developed by Smart Soft Healthcare); the certificate itself was not read, and the page states the version as ISO/IEC 27001:2017 as published. Exact-release scope is not established.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
24Fields reviewed
9Source 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, acr ai central product, 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 verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K250367 configuration 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 publicly available - checked 2026-09-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Deployment: Not publicly available - checked 2026-11-14 - Exact FDA submission
The exact FDA decision document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
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
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: View and quantify bone age from 2D posteroanterior left-hand radiographs to aid pediatric radiologists assessing patients aged 2-18 years.
Authorized purpose: Analyzes two-dimensional bitewing and periapical radiographs of permanent teeth in patients aged 15 and older to identify and localize caries, calculus, periapical radiolucency, root canal filling deficiency, discrepancy at an existing restoration margin, and bone loss; also supports alveolar bone-level measurement and restoration/dental-anatomy segmentation as an adjunct to dentist review.
Authorized purpose: VEA Align is cloud-based software for orthopedic applications in adult and pediatric populations using two-dimensional X-ray images from EOS imaging systems to display interactive landmarks and assess patient-specific global alignment, with angle and length measurements for spinal deformities, degenerative diseases, and lower-limb alignment disorders or deformities. It is suitable for patients aged 7 years and older. spineEOS assists healthcare professionals with preoperative planning of spine surgery using EOS images, associated three-dimensional datasets, measurements, and patient-specific surgical-planning tools.
Modality
X-ray/Radiography
Anatomy
Spine and lower-limb alignment; frontal and lateral EOS images and associated 3D datasets
Authorized purpose: Aids dentists reviewing bitewing and periapical radiographs of permanent teeth by detecting/segmenting caries and periapical radiolucencies, identifying restorations and dental anatomy, and measuring mesial/distal bone levels; it does not replace dentist 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.