MRI image-enhancement software that increases bone contrast in dedicated pelvic and lower-spine examinations for professional review.
Clinical role
MRI bone-contrast enhancement for professional image review.
Images and patients
MRI · Pelvic sacrum, hip bones, femoral heads, and lumbar spine L3-S1
Key limitation
Use is limited to the labeled anatomy and supported dedicated protocol; the enhanced image is not for primary or metastatic tumor diagnosis or monitoring and is not a CT replacement.
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?It enhances bone contrast in dedicated MRI examinations of the pelvic sacrum, hip bones, femoral heads, and lumbar spine from L3 through S1.
Which scans is it intended for?It accepts supported dedicated three-dimensional gradient-echo MRI studies within the labeled clinical MRI workflow.
Who uses it?Radiologists, orthopedic surgeons, and other trained imaging professionals use the enhanced images for review.
What does the software produce?It produces an enhanced MR series with increased bone contrast. The FDA package describes DICOM input and enhanced DICOM output in a clinic or hospital network.
What is its most important limitation?The enhanced image is not intended to diagnose or monitor primary or metastatic tumors, and it does not replace CT.
Clinical takeaway. BoneMRI enhances bone contrast for professional review in its labeled MRI scope; it does not replace CT or establish a tumor-diagnosis or monitoring use.
Evidence takeaway. The FDA decision material establishes the cleared software configuration, labeled use, and submission-specific verification. It does not establish product-wide sensitivity, specificity, clinical outcomes, or independent clinical validation.
Additional limitations
The FDA package describes the interface boundary, not current local compatibility, routing, identity, archive, downtime, hosting, security, or availability. Those require site acceptance testing and vendor evidence.
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
BoneMRI enhances bone contrast in dedicated MRI examinations of the pelvic sacrum, hip bones, femoral heads, and lumbar spine from L3 through S1; it is not intended to diagnose or monitor primary or metastatic tumors and does not replace CT.
The enhanced image is not intended for primary or metastatic tumor diagnosis or monitoring and is not a replacement for CT; dedicated anatomy and protocol limits apply.
The exact FDA document reports software verification and validation testing and a retrospective quantitative voxel-by-voxel validation for the lumbar spine region on imaging data from 73 patients, with co-registered CT scans as the reference standard. It reports a mean absolute cortical delineation error below 1.0 mm on average, a mean radiodensity deviation below 25 HU on average and below 55 HU for bone, and a mean HU correlation coefficient above 0.75 for bone. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "BoneMRI conducted the following performance testing: 1. Software verification and validation testing 2. Studies that utilized retrospective clinical data" … "A quantitative voxel-by-voxel validation of BoneMRI was performed on imaging data from 73 patients.". 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 software verification and validation testing and a retrospective quantitative voxel-by-voxel validation for the lumbar spine region on imaging data from 73 patients, with co-registered CT scans as the reference standard. It reports a mean absolute cortical delineation error below 1.0 mm on average, a mean radiodensity deviation below 25 HU on average and below 55 HU for bone, and a mean HU correlation coefficient above 0.75 for bone. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "BoneMRI conducted the following performance testing: 1. Software verification and validation testing 2. Studies that utilized retrospective clinical data" … "A quantitative voxel-by-voxel validation of BoneMRI was performed on imaging data from 73 patients.". 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, 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.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K221762 FDA evidence package for BoneMRI v1.4
DesignFDA 510(k) or PMA decision evidence and product verification described in the exact submission.
PopulationPelvic sacrum, hip bones, femoral heads, and lumbar spine L3-S1
Scopeexact submission
Tested versionBoneMRI v1.4 configuration described in K221762
IndependenceSponsor or vendor study
K221762
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and 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 K221762 by exact native submission identifier. This does not exclude product-family, later, 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.
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.
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. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.
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.
Source context, not route validation: The FDA package describes DICOM input and enhanced DICOM output for a server in a clinic or hospital network.
Scope: Exact FDA submission. This is the 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 FDA package describes a server in the clinic or hospital network; current hosting, service, security, and availability remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Enhanced MR series with increased bone contrast for review.
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 FDA package describes a server in the clinic or hospital network; current hosting, service, security, and availability remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA package describes DICOM input and enhanced DICOM output for a server in a clinic or hospital network.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only radiologists, orthopedic surgeons, and other trained imaging professionals should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K221762 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: The enhanced image is not intended for primary or metastatic tumor diagnosis or monitoring and is not a replacement for CT; dedicated anatomy and protocol limits apply.
Exact FDA submission
Checked 2026-09-04
Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
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 enhanced image is not intended for primary or metastatic tumor diagnosis or monitoring and is not a replacement for CT; dedicated anatomy and protocol limits apply.
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.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor K221762 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: The enhanced image is not intended for primary or metastatic tumor diagnosis or monitoring and is not a replacement for CT; dedicated anatomy and protocol limits apply.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. MRI image-enhancement software limits remain submission-specific.
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-04Last searched
26Fields reviewed
11Source classes checked
18Awaiting review PubMed leads
2Awaiting review trial leads
0Unreviewed FDA recall leads
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact-name and exact-submission searches in the checked 2026-09-01 indexes returned 18 PubMed candidate records and 2 ClinicalTrials.gov candidate records for K221762; review status is candidate_review_pending. Literature and registry candidates remain quarantined unless exact submission and tested-version linkage is established. The checked recall disposition is no exact-submission recall record was promoted; ambiguous or family-only candidates are not published. Pricing, complete security architecture, contracted deployment, exact reimbursement, and local interoperability remain unverified. Automated exact-name discovery found 18 PubMed and 2 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, acr ai central product, 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.
Authorized purpose: MRI-based BoneMRI v1.6 image enhancement for visualizing pelvic and L3-S1 lumbar bone structures with enhanced contrast; not for tumor diagnosis or monitoring and not a CT replacement.
Authorized purpose: CoLumbo is an image post-processing and measurement software tool that provides quantitative spine measurements from previously-acquired DICOM lumbar spine Magnetic Resonance (MR) images for users' review, analysis, and interpretation. It provides the following functionality to assist users in visualizing, measuring and documenting out-of range measurements:- Feature segmentation;- Feature measurement;- Threshold-based labeling of out-of-range measurement; and- Export of measurement results to a written report for user's review, revise and approval. Columbo does not produce or recommend any type of medical diagnosis or treatment. Instead, it simply helps users to more easily identify and classify features in lumbar MR images and compile a report. The user is responsible forconfirming/modifying settings, reviewing and verifying the software-generated measurements, inspecting out-of-range measurements, and approving draft report content using their medical judgment and discretion. The device is intended to be used only by hospitals and other medical institutions. Only DICOM images of MRI acquired from lumbar spine exams of patients aged 18 and above are considered to be valid input. CoLumbo does not support DICOM images of patients that are pregnant, undergo MRI scan with contrast media, or have post-operational complications, scoliosis, tumors, infections, fractures.
Authorized purpose: BoneMRI enhances bone contrast in pelvic MRI examinations of the sacrum, hip bones, and femoral heads; it is not intended to diagnose or monitor primary or metastatic tumors and does not replace CT.
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.