FDA-cleared profile

UNiD™ Spine Analyzer

Medicrea International S.A.S. (Medtronic) · Radiological images; modality varies or is not specified in FDA list · FDA-cleared (510(k))

Authorized purpose: UNiD Spine Analyzer assists healthcare professionals in viewing and measuring images and planning orthopedic spine surgery, including preoperative and postoperative measurements, surgical-strategy simulation, and patient-specific or standard implant planning; clinical judgment and surgeon validation remain required.

Clinical role
Measures spine images, simulates surgical strategy, estimates compensatory effects, and supports surgeon review before implant manufacture.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Spine
Key limitation
Keep in mind: The exact FDA material requires clinical judgment and surgeon validation before implant manufacture; the AI models and web workflow are version-specific, and the FDA submission used separate training and testing cases without clinical testing for the submission.

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: UNiD Spine Analyzer assists healthcare professionals in viewing and measuring images and planning orthopedic spine surgery, including preoperative and postoperative measurements, surgical-strategy simulation, and patient-specific or standard implant planning; clinical judgment and surgeon validation remain required.
  • Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Spine Input: Patient images uploaded to the web application in JPEG, PNG, or GIF format, with user-entered or selected planning information as described in the FDA comparison table.
  • Who uses it?Intended users: Orthopedic spine surgeons and other trained healthcare professionals involved in spine-surgery planning.
  • What does the software produce?Output: Spine measurements, simulated surgical plans, patient-specific rod or standard-implant planning information, compensatory-effect estimates, and image or ZIP exports to the Medtronic HUB.
  • What is its most important limitation?Key limitation: The exact FDA material requires clinical judgment and surgeon validation before implant manufacture; the AI models and web workflow are version-specific, and the FDA submission used separate training and testing cases without clinical testing for the submission.

Clinical takeaway. Clinical role: UNiD Spine Analyzer assists healthcare professionals in viewing and measuring images and planning orthopedic spine surgery, including preoperative and postoperative measurements, surgical-strategy simulation, and patient-specific or standard implant planning; clinical judgment and surgeon validation remain required.

Evidence takeaway. Evidence from the reviewed source record: K251629 FDA material describes a version 5.0.0 performance evaluation using 1,050 patient surgery cases from U.S. sites, with 776 training and 274 testing cases, and a non-inferiority design; it states that no clinical testing was used for the submission.

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
UNiD Spine Analyzer assists healthcare professionals in viewing and measuring images and planning orthopedic spine surgery, including preoperative and postoperative measurements, surgical-strategy simulation, and patient-specific or standard implant planning; clinical judgment and surgeon validation remain required.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Measures spine images, simulates surgical strategy, estimates compensatory effects, and supports surgeon review before implant manufacture.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Patient images uploaded to the web application in JPEG, PNG, or GIF format, with user-entered or selected planning information as described in the FDA comparison table.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Spine measurements, simulated surgical plans, patient-specific rod or standard-implant planning information, compensatory-effect estimates, and image or ZIP exports to the Medtronic HUB.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Preoperative and postoperative spine-planning workflows in orthopedic healthcare settings.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Orthopedic spine surgeons and other trained healthcare professionals involved in spine-surgery planning.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
The exact FDA material requires clinical judgment and surgeon validation before implant manufacture; the AI models and web workflow are version-specific, and the FDA submission used separate training and testing cases without clinical testing for the submission.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
K251629 FDA material describes a version 5.0.0 performance evaluation using 1,050 patient surgery cases from U.S. sites, with 776 training and 274 testing cases, and a non-inferiority design; it states that no clinical testing was used for the submission.
  • Exact FDA submission
  • Checked 2026-09-04

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
K251629 FDA material describes a version 5.0.0 performance evaluation using 1,050 patient surgery cases from U.S. sites, with 776 training and 274 testing cases, and a non-inferiority design; it states that no clinical testing was used for the submission.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Sensitivity is not promoted as a product-wide endpoint. 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 promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.

Performance-evaluation case count

1050 patient surgery cases

  • EndpointTotal cases in FDA evaluation
  • PopulationSpine-surgery cases from U.S. sites
  • Tested versionUNiD Spine Analyzer version 5.0.0 configuration described in K251629

Training partition

776 cases

  • EndpointTraining partition size
  • PopulationSpine-surgery cases used in development
  • Tested versionUNiD Spine Analyzer version 5.0.0 configuration described in K251629

Testing partition

274 cases

  • EndpointTesting partition size
  • PopulationSpine-surgery cases held out for evaluation
  • Tested versionUNiD Spine Analyzer version 5.0.0 configuration described in K251629

K251629 FDA evidence package for UNiD™ Spine Analyzer

  • DesignFDA 510(k) non-inferiority performance evaluation with separate training and testing cases and ground truth from trained Medtronic measurement technicians.
  • Population1,050 patient spine-surgery cases from U.S. sites; 776 training cases and 274 testing cases.
  • Scopeexact submission
  • Tested versionUNiD Spine Analyzer version 5.0.0 configuration described in K251629
  • Samplen=1050
  • IndependenceSponsor or vendor study

K251629

The FDA summary describes cybersecurity testing and non-inferiority planning but no clinical testing for the submission.

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
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K251629 by exact native submission identifier. This does not exclude product-family, later-version, 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.

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

Reimbursement
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
  • Service-level, not product-specific
  • Checked 2026-09-04

No product-specific code

No separate named-product payment identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

This is not a product-specific reimbursement determination. Verify payer, site-of-service, coding, and coverage assumptions independently.

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: Patient images uploaded to the web application in JPEG, PNG, or GIF format, with user-entered or selected planning information as described in the FDA comparison table.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K251629: UNiD™ Spine Analyzer

  2. Routing

    Source context, not route validation: The FDA material describes a standalone or connected web application with image upload and export of images or ZIP files to the Medtronic HUB.

    Scope: Exact FDA submission. This is the interface boundary described in the exact FDA decision material; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

    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 K251629: UNiD™ Spine Analyzer

  3. AI processing

    Source context, not route validation: The FDA comparison table describes a cloud-based application hosted on AWS and a standalone or connected mode; current hosting, contracts, security, retention, availability, and local configuration remain unverified.

    Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA decision material; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-04 · FDA 510(k) decision material K251629: UNiD™ Spine Analyzer

  4. Returned objects

    Source context, not route validation: Spine measurements, simulated surgical plans, patient-specific rod or standard-implant planning information, compensatory-effect estimates, and image or ZIP exports to the Medtronic HUB.

    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 K251629: UNiD™ Spine Analyzer

  5. Viewer/worklist/report

    Unresolved route: Spine measurements, simulated surgical plans, patient-specific rod or standard-implant planning information, compensatory-effect estimates, and image or ZIP exports to the Medtronic HUB.

    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 K251629: UNiD™ Spine Analyzer

  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 FDA comparison table describes a cloud-based application hosted on AWS and a standalone or connected mode; current hosting, contracts, security, retention, availability, and local configuration remain unverified.
  • Exact FDA submission
  • Checked 2026-09-04

This is the release-level boundary described in the exact FDA decision material; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.

Integration
The FDA material describes a standalone or connected web application with image upload and export of images or ZIP files to the Medtronic HUB.
  • Exact FDA submission
  • Checked 2026-09-04

This is the interface boundary described in the exact FDA decision material; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

Training
Only Orthopedic spine surgeons and other trained healthcare professionals involved in spine-surgery planning should operate or interpret the product; local onboarding must cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K251629 by exact hardware, software, model, algorithm 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 exact FDA material requires clinical judgment and surgeon validation before implant manufacture; the AI models and web workflow are version-specific, and the FDA submission used separate training and testing cases without clinical testing for the submission.
  • Exact FDA submission
  • Checked 2026-09-04

Buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K251629 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared release includes them.

Deployment boundary

The FDA comparison table describes a cloud-based application hosted on AWS and a standalone or connected mode; current hosting, contracts, security, retention, availability, and local configuration remain unverified.

exact submission · checked 2026-09-04

FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.

Interoperability acceptance

The FDA material describes a standalone or connected web application with image upload and export of images or ZIP files to the Medtronic HUB.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

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 exact FDA material requires clinical judgment and surgeon validation before implant manufacture; the AI models and web workflow are version-specific, and the FDA submission used separate training and testing cases without clinical testing for the submission.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

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.

product family · checked 2026-09-04

No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.

Lifecycle monitoring

Monitor K251629 by exact hardware, software, model, algorithm 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.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.

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
K251629
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Radiological images; modality varies or is not specified in FDA list
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Spine
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-08-07
  • 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.

Human reviewedStatus
2026-09-04Last searched
32Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The discovery snapshot contains no PubMed or ClinicalTrials.gov candidates for K251629; 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, 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 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
  • 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.

  • Installation timeline: Not yet reviewed

6 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K251629: UNiD™ Spine Analyzer

    U.S. Food and Drug Administration - Published 2025-08-07 - 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

Research history

  1. K251629 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K261289

UNiD™ Spine Analyzer (SW3002)

Medicrea International S.A.S. (Medtronic)

Authorized purpose: UNiD Spine Analyzer SW3002 v5.1.0 enables healthcare professionals to view and measure images and plan orthopedic spine surgeries, including preoperative and postoperative measurements and patient-specific rod or implant planning.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Spine
Decision
2026-05-15
FDA-cleared K251059

Syngo Carbon Clinicals (VA41)

Siemens Healthineers AG

Authorized purpose: Syngo Carbon Clinicals VA41 provides advanced visualization and analysis for clinical images, including OrthoMatic Spine whole-spine curve-angle measurements and TimeLens comparison of regions of interest across time points.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Whole spine and other clinical image regions represented in supported CT and MR workflows
Decision
2025-10-24
FDA-cleared K243647

Synapse PACS (7.5)

FUJIFILM Healthcare Americas Corporation

Authorized purpose: Synapse PACS version 7.5 provides primary processing and presentation of DICOM and supported non-DICOM images with measurement, segmentation, fusion, volume rendering, reporting, integrated 3D, two-point VOI, and AI-assisted bone removal.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Multi-region
Decision
2025-06-30
FDA-cleared K231955

aprevo® Digital Segmentation

Carlsmed, Inc.

Authorized purpose: aprevo Digital Segmentation is software for trained, medically knowledgeable design personnel to perform digital image segmentation of the spine, primarily lumbar anatomy; it inputs DICOM images and outputs a three-dimensional spine model.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Spine, primarily lumbar anatomy
Decision
2023-11-03

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