Authorized purpose: Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.
Clinical role
AI pipeline estimates femoral-neck BMD; when below a pre-specified threshold, it delivers a report to the interpreting physician flagging possible low BMD to prompt a clinical bone-health assessment; it should not be used to rule out low BMD.
Images and patients
X-ray/Radiography · MSK
Key limitation
Keep in mind: A missing or above-threshold report does not rule out low BMD; clinicians should follow recommended screening and assessment regardless of the report, and the FDA packet does not establish current commercial hosting or support terms.
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: Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: MSK Input: Standard anteroposterior (AP) radiographs of the hip or pelvis from patients aged 50 years and older, received as DICOM images with associated metadata from clinical imaging systems via a host integration platform.
Who uses it?Intended users: Radiologists and/or physician interpreters
What does the software produce?Output: OsteoSight applies an AI-enabled algorithm pipeline to estimate bone mineral density (BMD) at the femoral neck. The algorithm presents a binary output to indicate whether the patient likely has low BMD at the femoral neck. If an estimated BMD is below the pre-specified threshold, OsteoSight generates a report (Results Report) indicating that the patient is at risk of having low BMD, which is delivered to the interpreting physician via the host integration platform. If the estimated BMD is above or equal to the pre-specified threshold, no report is generated.
What is its most important limitation?Key limitation: A missing or above-threshold report does not rule out low BMD; clinicians should follow recommended screening and assessment regardless of the report, and the FDA packet does not establish current commercial hosting or support terms.
Clinical takeaway. Clinical role: Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.
Evidence takeaway. Evidence from the reviewed source record: Study type: Stand-Alone Performance. Cases: 3082. Sites: 6. Reported sensitivity: 37% (95% CI: 34.9%, 39.1%). Reported specificity: 95.1% (95% CI: 93.6%, 96.3%)
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
Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.
Exact FDA submission
Checked 2026-09-06
Exact clinical-use normalization from the FDA packet; this text is also the locked corrections value.
AI pipeline estimates femoral-neck BMD; when below a pre-specified threshold, it delivers a report to the interpreting physician flagging possible low BMD to prompt a clinical bone-health assessment; it should not be used to rule out low BMD.
Exact FDA submission
Checked 2026-11-14
Packet wording: "OsteoSight applies an AI-enabled algorithm pipeline to estimate bone mineral density (BMD) at the femoral neck. If an estimated BMD is below the pre-specified threshold, OsteoSight generates a report indicating that the patient is at risk of having low BMD." … "This report is delivered to the interpreting physician via the host integration platform.". Read from the exact FDA decision document on 2026-11-14.
Standard anteroposterior (AP) radiographs of the hip or pelvis from patients aged 50 years and older, received as DICOM images with associated metadata from clinical imaging systems via a host integration platform.
Exact FDA submission
Checked 2026-11-14
Packet wording: "processes standard anteroposterior (AP) radiographs of the hip or pelvis in patients aged 50 years and older." … "The device operates via integration with a host integration platform that facilitates the secure transfer of DICOM images and associated metadata from clinical imaging systems.". Read from the exact FDA decision document on 2026-11-14.
OsteoSight applies an AI-enabled algorithm pipeline to estimate bone mineral density (BMD) at the femoral neck. The algorithm presents a binary output to indicate whether the patient likely has low BMD at the femoral neck. If an estimated BMD is below the pre-specified threshold, OsteoSight generates a report (Results Report) indicating that the patient is at risk of having low BMD, which is delivered to the interpreting physician via the host integration platform. If the estimated BMD is above or equal to the pre-specified threshold, no report is generated.
Exact FDA submission
Checked 2026-09-01
Clinical output reported in the exact-submission ACR model card.
A missing or above-threshold report does not rule out low BMD; clinicians should follow recommended screening and assessment regardless of the report, and the FDA packet does not establish current commercial hosting or support terms.
Exact FDA submission
Checked 2026-09-06
Exact-product limitations and clinician-review boundary from the FDA packet.
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.
Opportunistic assessment of osteoporosis using hip and pelvic X-rays with OsteoSight: validation of an AI-based tool in a US population
DesignPeer-reviewed diagnostic validation study
PopulationUS population with hip or pelvic X-rays compared with DXA; robustness and reproducibility were evaluated across demographic groups and scanner hardware
Scopeproduct family
Tested versionOsteoSight product family; exact commercial release not reported
Authors include Naitive employees/shareholders; treat as vendor-sponsored family evidence, not independent exact-release performance. The abstract reports preprocessing exclusions for wrong body parts, metalwork, and unacceptable femur positioning.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
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: Standard anteroposterior (AP) radiographs of the hip or pelvis from patients aged 50 years and older, received as DICOM images with associated metadata from clinical imaging systems via a host integration platform.
Scope: Exact FDA submission. Packet wording: "processes standard anteroposterior (AP) radiographs of the hip or pelvis in patients aged 50 years and older." … "The device operates via integration with a host integration platform that facilitates the secure transfer of DICOM images and associated metadata from clinical imaging systems.". Read from the exact FDA decision document on 2026-11-14.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes OsteoSight as able to be installed in the cloud via a host integration platform, which may be within the existing secured network of a clinical site. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "be installed in the cloud, via a host integration" … "platform, which may be within the existing". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: OsteoSight applies an AI-enabled algorithm pipeline to estimate bone mineral density (BMD) at the femoral neck. The algorithm presents a binary output to indicate whether the patient likely has low BMD at the femoral neck. If an estimated BMD is below the pre-specified threshold, OsteoSight generates a report (Results Report) indicating that the patient is at risk of having low BMD, which is delivered to the interpreting physician via the host integration platform. If the estimated BMD is above or equal to the pre-specified threshold, no report is generated.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: OsteoSight applies an AI-enabled algorithm pipeline to estimate bone mineral density (BMD) at the femoral neck. The algorithm presents a binary output to indicate whether the patient likely has low BMD at the femoral neck. If an estimated BMD is below the pre-specified threshold, OsteoSight generates a report (Results Report) indicating that the patient is at risk of having low BMD, which is delivered to the interpreting physician via the host integration platform. If the estimated BMD is above or equal to the pre-specified threshold, no report is generated.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
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 package describes OsteoSight as able to be installed in the cloud via a host integration platform, which may be within the existing secured network of a clinical site. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "be installed in the cloud, via a host integration" … "platform, which may be within the existing". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
The peer-reviewed family study reports exclusion of unsuitable cases such as wrong body parts, metalwork, or unacceptable femur positioning before analysis.
product family · checked 2026-09-06
Product-family study; it does not establish exact K251408 commercial release behavior.
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.
Human reviewedStatus
2026-09-07Last searched
28Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
Stored exact-submission candidate metadata had zero PubMed and ClinicalTrials.gov identifiers; this metadata screening is not a full paper or registry-record review. 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, vendor product page, peer reviewed publication, 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-06 - Exact FDA submission
Official non-FDA product sources were reviewed for buyer and workflow context, but no exact-submission amount, currency, unit, term, or implementation fee was displayed. A vendor quote remains required.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "Naitive Technologies reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. No result was a vendor or payer page naming this product with coding or payment; any results were general billing guidance. This records what was found, not that none exists.
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-08-13 - Exact FDA submission
FDA authorization does not establish the current commercial security posture. Request data-flow diagrams, hosting and retention details, access controls, audit logging, attestations, and incident-response documentation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-08-13 - Exact FDA submission
Training, onboarding, competency, and support commitments are commercial implementation details that require current vendor documentation.
Monitoring: Not verified - checked 2026-08-13 - Exact FDA submission
Local acceptance testing, production monitoring, drift review, update control, and incident escalation require a current vendor and site-specific governance plan.
Authorized purpose: Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.
Authorized purpose: Assists radiologists and emergency physicians in detecting fractures on DICOM musculoskeletal radiographs for adults and children aged 2 years or older, limited to the FDA-listed anatomic areas and standard views (ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot); it is an aided-diagnosis device and does not operate autonomously.
Authorized purpose: The Knee OsteoArthritis Labeling Assistant (KOALA) software provides metric measurements of the joint space width and indicators for presence or absence of radiographic features of osteoarthritis (OA) on PA/AP knee X-ray images.
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.