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.
Clinical role
Radiographic image acquisition support, image processing, measurement, planning, or concurrent review under professional control.
Images and patients
X-ray/Radiography · Spine and lower-limb alignment; frontal and lateral EOS images and associated 3D datasets
Key limitation
Keep in mind: Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
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: 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.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Spine and lower-limb alignment; frontal and lateral EOS images and associated 3D datasets Input: Supported X-ray, radiographic, EOS, dental, or other labeled image inputs and associated study data.
Who uses it?Intended users: Radiologists, dentists, orthopedic clinicians, and other trained radiographic professionals within the labeled use.
What does the software produce?Output: Processed radiographs, measurements, landmarks, annotations, planning views, and review information for professional use.
What is its most important limitation?Key limitation: Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
Clinical takeaway. Clinical role: 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.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports a standalone validation of the VEA Align AI algorithm on a dedicated test data set of 361 patients, separate from the training data, with ground-truth EOS 3DServices reconstructions from sterEOS. Acceptance criteria were Median error ≤ 3 mm and 3rd Quartile ≤ 5 mm; the document states that direct comparison of skeletal landmark locations between the subject and predicate devices met these criteria. 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
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.
Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
The exact FDA document reports a standalone validation of the VEA Align AI algorithm on a dedicated test data set of 361 patients, separate from the training data, with ground-truth EOS 3DServices reconstructions from sterEOS. Acceptance criteria were Median error ≤ 3 mm and 3rd Quartile ≤ 5 mm; the document states that direct comparison of skeletal landmark locations between the subject and predicate devices met these criteria. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "To assess the standalone performance of the AI algorithm of the VEA Align, the test was performed with:" … "A dedicated test data set containing different data from the training data set.". Read from the exact FDA decision document on 2026-11-14.
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 a standalone validation of the VEA Align AI algorithm on a dedicated test data set of 361 patients, separate from the training data, with ground-truth EOS 3DServices reconstructions from sterEOS. Acceptance criteria were Median error ≤ 3 mm and 3rd Quartile ≤ 5 mm; the document states that direct comparison of skeletal landmark locations between the subject and predicate devices met these criteria. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "To assess the standalone performance of the AI algorithm of the VEA Align, the test was performed with:" … "A dedicated test data set containing different data from the training data set.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately 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, study design, and source if separately verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K251747 FDA decision evidence package for VEA Align; spineEOS
DesignFDA decision evidence and product verification described in the exact submission or PMA decision record.
PopulationSpine and lower-limb alignment; frontal and lateral EOS images and associated 3D datasets
Scopeexact submission
Tested versionVEA Align; spineEOS configuration described in K251747
IndependenceSponsor or vendor study
K251747
FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; local technical, clinical, privacy, security, and workflow acceptance remains necessary.
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 K251747 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.
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: Supported X-ray, radiographic, EOS, dental, or other labeled image inputs and associated study data.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes EOS 2D X-ray images, associated 3D datasets, landmarks, measurements, and spine-planning outputs; verify image identity, routing, dataset compatibility, and local archive behavior.
Scope: Exact FDA submission. This is a partial interface boundary described in the exact FDA package; 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.
Source context, not route validation: The exact FDA indication identifies VEA Align as cloud-based; current hosting, contracts, security, availability, and site configuration remain unknown.
Scope: Exact FDA submission. This is a partial release-level topology fact from the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Processed radiographs, measurements, landmarks, annotations, planning views, and review information for professional use.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Processed radiographs, measurements, landmarks, annotations, planning views, and review information for professional use.
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.
The exact FDA indication identifies VEA Align as cloud-based; current hosting, contracts, security, availability, and site configuration remain unknown.
Exact FDA submission
Checked 2026-09-04
This is a partial release-level topology fact from the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
The exact FDA package describes EOS 2D X-ray images, associated 3D datasets, landmarks, measurements, and spine-planning outputs; verify image identity, routing, dataset compatibility, and local archive behavior.
Exact FDA submission
Checked 2026-09-04
This is a partial interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only radiologists, dentists, orthopedic clinicians, and other trained radiographic professionals within the labeled use should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K251747 by exact hardware, software, model, and 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: Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The exact FDA indication identifies VEA Align as cloud-based; current hosting, contracts, security, availability, and site configuration remain unknown.
exact submission · checked 2026-09-04
FDA-described topology does not establish current hosting contracts, security controls, uptime, or local qualification.
The exact FDA package describes EOS 2D X-ray images, associated 3D datasets, landmarks, measurements, and spine-planning outputs; verify image identity, routing, dataset compatibility, and local archive behavior.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
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. Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
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.
exact submission · checked 2026-09-04
No exact-product price or reimbursement determination was promoted.
Monitor K251747 by exact hardware, software, model, and 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: Use is limited to orthopedic alignment and spine-planning workflows for patients aged 7 years and older, and clinical judgment and experience are required.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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
27Fields reviewed
9Source classes checked
1Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 1 PubMed and 1 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 1 PubMed and 1 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, 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 list price for the exact cleared or authorized configuration was found. Obtain a written quote separating license or hardware 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
Reimbursement: Not publicly available - checked 2026-09-04 - Exact FDA submission
No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.
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.
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: Post-processing segmentation, measurement, threshold labeling, and export of quantitative lumbar-spine measurements to support clinical review; not diagnosis.
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.