Authorized purpose: Qualitative and quantitative spine analysis from CT images to support clinician evaluation of musculoskeletal spinal disease, including vertebral labeling, vertebral height-loss measurement, and mean vertebral Hounsfield-unit measurement in patients aged 50 and over.
Clinical role
Post-acquisition DICOM CT validation and analysis in parallel with standard image storage and clinician availability, with automated vertebral labeling, segmentation, height and HU measurements, configurable flags, and clinician review.
Images and patients
CT/CTA · Spine, including T1-L4 vertebrae and T11-L4 trabecular bone regions
Key limitation
Keep in mind: Use is limited to patients aged 50 and over, FBP-reconstructed CT, and the required vertebral coverage. Height-loss and bone-attenuation display thresholds are configurable from predefined lists. Axial analysis is a backup when sagittal data are unavailable, and the device is not intended as a standalone diagnostic tool.
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: Qualitative and quantitative spine analysis from CT images to support clinician evaluation of musculoskeletal spinal disease, including vertebral labeling, vertebral height-loss measurement, and mean vertebral Hounsfield-unit measurement in patients aged 50 and over.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Spine, including T1-L4 vertebrae and T11-L4 trabecular bone regions Input: DICOM CT scans of patients aged 50 and over undergoing any clinical indication, with at least four vertebrae in the T1-L4 portion for height-loss analysis and the T11-L4 portion for bone attenuation; FBP-reconstructed images only. Sagittal scans are intended, with axial scans as backup when sagittal scans are unavailable.
Who uses it?Intended users: Clinicians, including radiologists and physicians in emergency medicine, specialty care, urgent care, and general practice.
What does the software produce?Output: For each analyzed vertebra, a vertebral name, percentage height loss based on anterior/middle/posterior measurements, an indication when height loss exceeds a configurable threshold defaulting to >20%, mean trabecular-bone HU for T11-L4 with a configurable low-attenuation indication, and flags for significant height deviation from neighboring vertebrae.
What is its most important limitation?Key limitation: Use is limited to patients aged 50 and over, FBP-reconstructed CT, and the required vertebral coverage. Height-loss and bone-attenuation display thresholds are configurable from predefined lists. Axial analysis is a backup when sagittal data are unavailable, and the device is not intended as a standalone diagnostic tool.
Clinical takeaway. Clinical role: Qualitative and quantitative spine analysis from CT images to support clinician evaluation of musculoskeletal spinal disease, including vertebral labeling, vertebral height-loss measurement, and mean vertebral Hounsfield-unit measurement in patients aged 50 and over.
Evidence takeaway. Evidence from the reviewed source record: FDA stand-alone retrospective testing used 150 anonymized CT cases containing 1,425 vertebrae from two healthcare institutions with multiple US and OUS clinical sites; ground truth was determined by three US board-certified radiologists. Overall vertebral-naming agreement was 91.49% (95% CI [89.91%, 92.89%]); height-loss 95% limits of agreement were [-7.98, 7.36], with 91.86% of differences within the ground-truth readers' limits; agreement for classifying height loss above or below 20% was 91.28%; bone-attenuation 95% limits of agreement were [-20.83, 18.29], with 96.06% of differences within ground-truth readers' limits. These are agreement and limits-of-agreement endpoints, not sensitivity or specificity.
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
Qualitative and quantitative spine analysis from CT images to support clinician evaluation of musculoskeletal spinal disease, including vertebral labeling, vertebral height-loss measurement, and mean vertebral Hounsfield-unit measurement in patients aged 50 and over.
Post-acquisition DICOM CT validation and analysis in parallel with standard image storage and clinician availability, with automated vertebral labeling, segmentation, height and HU measurements, configurable flags, and clinician review.
DICOM CT scans of patients aged 50 and over undergoing any clinical indication, with at least four vertebrae in the T1-L4 portion for height-loss analysis and the T11-L4 portion for bone attenuation; FBP-reconstructed images only. Sagittal scans are intended, with axial scans as backup when sagittal scans are unavailable.
For each analyzed vertebra, a vertebral name, percentage height loss based on anterior/middle/posterior measurements, an indication when height loss exceeds a configurable threshold defaulting to >20%, mean trabecular-bone HU for T11-L4 with a configurable low-attenuation indication, and flags for significant height deviation from neighboring vertebrae.
Use is limited to patients aged 50 and over, FBP-reconstructed CT, and the required vertebral coverage. Height-loss and bone-attenuation display thresholds are configurable from predefined lists. Axial analysis is a backup when sagittal data are unavailable, and the device is not intended as a standalone diagnostic tool.
FDA stand-alone retrospective testing used 150 anonymized CT cases containing 1,425 vertebrae from two healthcare institutions with multiple US and OUS clinical sites; ground truth was determined by three US board-certified radiologists. Overall vertebral-naming agreement was 91.49% (95% CI [89.91%, 92.89%]); height-loss 95% limits of agreement were [-7.98, 7.36], with 91.86% of differences within the ground-truth readers' limits; agreement for classifying height loss above or below 20% was 91.28%; bone-attenuation 95% limits of agreement were [-20.83, 18.29], with 96.06% of differences within ground-truth readers' limits. These are agreement and limits-of-agreement endpoints, not sensitivity or specificity.
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 stand-alone retrospective testing used 150 anonymized CT cases containing 1,425 vertebrae from two healthcare institutions with multiple US and OUS clinical sites; ground truth was determined by three US board-certified radiologists. Overall vertebral-naming agreement was 91.49% (95% CI [89.91%, 92.89%]); height-loss 95% limits of agreement were [-7.98, 7.36], with 91.86% of differences within the ground-truth readers' limits; agreement for classifying height loss above or below 20% was 91.28%; bone-attenuation 95% limits of agreement were [-20.83, 18.29], with 96.06% of differences within ground-truth readers' limits. These are agreement and limits-of-agreement endpoints, not sensitivity or specificity.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
HealthOST regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K213944
Samplen=150
IndependenceIndependence not established
K213944
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 K213944. 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: DICOM CT scans of patients aged 50 and over undergoing any clinical indication, with at least four vertebrae in the T1-L4 portion for height-loss analysis and the T11-L4 portion for bone attenuation; FBP-reconstructed images only. Sagittal scans are intended, with axial scans as backup when sagittal scans are unavailable.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The packet describes DICOM-compliant clinical-center infrastructure, IMA integration for study results, and error codes for validation or analysis failure; it does not establish a specific PACS, RIS, EHR, interface version, or hosting model.
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: For each analyzed vertebra, a vertebral name, percentage height loss based on anterior/middle/posterior measurements, an indication when height loss exceeds a configurable threshold defaulting to >20%, mean trabecular-bone HU for T11-L4 with a configurable low-attenuation indication, and flags for significant height deviation from neighboring vertebrae.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: For each analyzed vertebra, a vertebral name, percentage height loss based on anterior/middle/posterior measurements, an indication when height loss exceeds a configurable threshold defaulting to >20%, mean trabecular-bone HU for T11-L4 with a configurable low-attenuation indication, and flags for significant height deviation from neighboring vertebrae.
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 packet describes DICOM-compliant clinical-center infrastructure, IMA integration for study results, and error codes for validation or analysis failure; it does not establish a specific PACS, RIS, EHR, interface version, or hosting model.
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
2Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 2 PubMed and 0 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 2 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-09 - Exact FDA submission
No public price or quote for the exact K213944 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-09 - 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
Security: Not verified - checked 2026-09-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Auto-Seg and Spine Auto-Seg accept spine and pelvis CT images and provide three-dimensional segmentation and labels to support spine-surgery planning and assessment by spine surgeons.
Authorized purpose: Acorn 3D Software and Acorn 3DP Model process CT, synthetic CT, and CT angiography for segmentation, visualization, measurement, treatment planning, and three-dimensional printing, including adult and pediatric spine trajectory planning.
Modality
CT/CTA
Anatomy
Spine; craniomaxillofacial; musculoskeletal anatomy; and patient-specific printed models
Authorized purpose: AI-CVD provides automated quantitative CT-derived anatomical and density measurements for clinician review, including calcium scores, cardiac and vascular measurements, lung and liver density, bone mineral density, and muscle/fat composition; it is opportunistic decision support, not diagnostic interpretation or risk prediction.
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.