MRI-processing software that creates an added bone-contrast image series for review beside the original scan.
Clinical role
Standalone MRI image-processing server that creates an adjunctive bone-visualization series while the original DICOM study remains available for standard interpretation.
Images and patients
MRI · Spine
Key limitation
BoneMRI images co-exist with the original MRI images and are not intended to replace CT images in general.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?It creates MRI-based images that make bone stand out more clearly from surrounding soft tissue.
Which scans and patients is it intended for?It is for people aged 12 and older who have dedicated 3D MRI of pelvic or spinal bone structures.
Who uses it?Imaging experts, such as radiologists or orthopedic surgeons, use the added image series during review.
What does the software produce, and what must the clinician do?It returns a standard image-file (DICOM) BoneMRI series that co-exists with the original MRI images. The clinician reads it in regular DICOM-compatible viewing software.
What is its most important limitation?It is not intended to replace CT images in general and is not for diagnosing or monitoring primary or metastatic tumors.
Clinical takeaway. BoneMRI is an added MRI image-processing series for bone visualization. It is reviewed alongside the original MRI, not as a general CT substitute.
Evidence takeaway. The FDA submission describes quantitative validation against paired CT in pelvic and spine patients, with stated acceptance bounds. This is a technical validation measure, not a reported patient-outcome measure.
Additional limitations
It is not intended for diagnosis or monitoring of primary or metastatic tumors.
Evidence context: questions, not a score
Agent transcription of regulatory evidence context, not independent validation, clinical acceptance or a product recommendation. Separate studies and outcomes are not a leaderboard.
Existing study anchor: K233030 BoneMRI quantitative voxel-by-voxel validation. Tested version label: BoneMRI release reviewed in FDA submission K233030.
What was tested?
Quantitative agreement of BoneMRI bone morphology, radiodensity and radiodensity contrast with paired CT.
Source section: 510(k) summary, section 9: Performance Data and Performance Validation
On which cases and versions?
76 patients contributed pelvic-region data and 117 contributed spine-region data. Test images were unseen during development; the source describes different sites, departments or studies from training. Cohorts are not assumed to be disjoint.
Source section: 510(k) summary, section 9: Performance Data and Performance Validation
What changed?
The regulatory package reports quantitative morphology/radiodensity endpoints against CT. This is image-reconstruction validation, not evidence of cancer detection or improved treatment outcomes.
Source section: 510(k) summary, section 9: Performance Data and Performance Validation
What does this not establish?
Agreement with CT on these measures does not establish a general CT replacement, tumor diagnosis/monitoring or treatment-planning authorization. Manufacturer validation is not independent-investigator validation.
Source section: 510(k) summary, section 9: Performance Data and Performance Validation
Study design, population and missing context
evidence Role
Retrospective technical validation of paired BoneMRI and CT images, not a disease-detection or treatment-outcome trial.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
design
Quantitative voxel-by-voxel validation using paired images from previously conducted clinical investigations; test data were unseen during development.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
setting
Test data acquired at different medical sites, departments or studies than training; exact site count not stated in the reviewed passage.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
training Population
Not established: The reviewed regulatory summary does not establish this field for this study context.
evaluation Population
76 patients with pelvic-region data and 117 with spine-region data. Cohort counts are retained separately; unique-patient overlap across cohorts is not established here.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
reference Standard
Paired CT of the same patient in the same anatomical region for morphology and radiodensity comparisons.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
comparator
BoneMRI outputs versus co-registered CT; endpoints describe morphology, radiodensity and radiodensity contrast.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
sites
Not established: The reviewed regulatory summary does not establish this field for this study context.
scanner Protocol
Input from a specified gradient-echo MRI sequence; paired CT acquired using standard-of-care bone imaging protocols.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
sample Composition
Pelvic cohort n=76 and spine cohort n=117, retained as distinct denominators rather than asserting 193 unique patients.
technical validation · 510(k) summary, section 9: Performance Data and Performance Validation
sponsor Involvement
Validation conducted by MRIguidance. Unseen test data do not establish independent investigators.
regulatory summary · 510(k) summary, section 9: Performance Data and Performance Validation
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.
Exact FDA submission K233030 · agent source review 2026-11-12 · BoneMRI release reviewed in FDA submission K233030
MRI-based BoneMRI image enhancement for visualizing pelvic and cervical, thoracic, lumbar and S1 spinal bone structures with CT-like radiodensity contrast; not for tumor diagnosis or monitoring and not a CT replacement.
Standalone MRI image-processing server that creates an adjunctive bone-visualization series while the original DICOM study remains available for standard interpretation.
DICOM BoneMRI images for viewing in a regular DICOM-compatible viewer, with 3D bone morphology, tissue radiodensity and tissue-radiodensity contrast visualized alongside the original images.
K233030 BoneMRI was validated with paired BoneMRI and CT images from 76 pelvic and 117 spine patients. The FDA summary reports bounds for morphology and radiodensity agreement, not exact aggregate point estimates.
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
K233030 BoneMRI was validated with paired BoneMRI and CT images from 76 pelvic and 117 spine patients. The FDA summary reports bounds for morphology and radiodensity agreement, not exact aggregate point estimates.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
DesignQuantitative validation using paired BoneMRI and CT images from previously conducted clinical investigations; test data were unseen during development.
Population76 patients with pelvic-region data and 117 patients with spine-region data.
Scopeexact submission
Tested versionBoneMRI release reviewed in FDA submission K233030
IndependenceIndependence not established
K233030
Validation was conducted by MRIguidance; independent-investigator status was not established. The FDA summary reports the pelvic (76) and spine (117) cohorts separately and states no combined unique-patient count.
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
Service-level context: CMS Transmittal 13135 (April 2025) establishes HCPCS G0566 under the hospital outpatient payment system, effective 2025-04-01, for 3D image generation used in surgical planning and navigation for placing implants and devices in the spine and pelvis. MRIguidance states BoneMRI was assigned G0566 (APC 5721) from 2025-04-01 and that it is a hospital outpatient billing pathway. CMS names no product. The vendor statement is not version-specific, and this entry's cleared use is bone visualization. This is not a determination that this exact release is covered or paid. No payment amount, status indicator or APC was read.
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 3D gradient-echo MRI images acquired using a dedicated MRI protocol.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Communicates with a DICOM-compatible imaging archive such as PACS to receive MRI input and return BoneMRI images; regular DICOM viewing software displays the result, while receipt and delivery depend on other software systems.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Server application on clinic or hospital networks, available fully on premises with specific GPU requirements or partly as a managed cloud service. The FDA summary states that on-premise PHI stays within the network and data sent to the managed cloud is de-identified before leaving it.
Scope: Exact FDA submission. Deployment language is from the exact FDA submission; it does not establish a current contracted hosting or security configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: DICOM BoneMRI images for viewing in a regular DICOM-compatible viewer, with 3D bone morphology, tissue radiodensity and tissue-radiodensity contrast visualized alongside the original images.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: DICOM BoneMRI images for viewing in a regular DICOM-compatible viewer, with 3D bone morphology, tissue radiodensity and tissue-radiodensity contrast visualized alongside the original images.
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.
Server application on clinic or hospital networks, available fully on premises with specific GPU requirements or partly as a managed cloud service. The FDA summary states that on-premise PHI stays within the network and data sent to the managed cloud is de-identified before leaving it.
Exact FDA submission
Checked 2026-09-07
Deployment language is from the exact FDA submission; it does not establish a current contracted hosting or security configuration.
Communicates with a DICOM-compatible imaging archive such as PACS to receive MRI input and return BoneMRI images; regular DICOM viewing software displays the result, while receipt and delivery depend on other software systems.
MRIguidance announced ISO 27001:2017 certification of its information security management system (certified 2022-04-22 by Brand Compliance), the certificate encompassing information security of the design and development, production, distribution, installation and servicing of the BoneMRI medical imaging processing software, both on premise and in cloud applications.
Product family
Checked 2026-10-27
Vendor statement; certificate not read. Scope explicitly names BoneMRI on-premise and cloud.
The FDA summary describes on-premise or partly managed-cloud server deployment and DICOM archive/PACS input and return, with output viewed in regular DICOM software.
MRIguidance's current BoneMRI family page describes 3D CT-like images reconstructed from MRI, forwarding reconstructed images to PACS, and compatibility with major MRI scanners.
product family · checked 2026-09-07
Current family material is buyer-relevant workflow context but does not establish feature parity or release identity for K233030.
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.
These links identify a sourced product-family relationship. They do not transfer evidence, metrics, clearance scope, compatibility, pricing, or availability between submissions.
This is a documented BoneMRI product-family relationship. Each linked FDA submission remains a separate record with its own intended use, evidence, implementation facts, and limitations.
MRIguidance's official BoneMRI page is a current product-family source. The individual FDA decision materials identify the named submissions below. The family source does not establish feature parity, supersession, or current commercial availability for either submission.
K233030 · 2024-03-01. This is the latest FDA decision date among the mapped records only. It is not a statement that K233030 supersedes K230197.
Latest documented release
No source reviewed for this mapping establishes a current commercial release chronology beyond the individual FDA records.
Current commercial availability
The reviewed materials do not establish current commercial availability or an installed version.
Research record
What has been checked
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-07Last searched
24Fields reviewed
13Source classes checked
18Screened PubMed leads
2Screened trial leads
0Unreviewed FDA recall leads
The stored PubMed and ClinicalTrials candidate metadata were screened in the exact stored order; this was metadata triage, not full-text paper or registry-record review, and no candidate was promoted. The stored recall query returned no records, so no event was promoted and no absence claim is made. The current discovery snapshot contains 18 PubMed and 2 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, literature index, trial registry, stored candidate metadata, stored recall candidates, payer policy, vendor documentation, 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-07 - Exact FDA submission
No public exact-submission price or procurement terms were reviewed.
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
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-10-27 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-10-27 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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: Semi-automatic lumbar MRI segmentation and area and distance measurements with radiologist-approved PDF report to PACS; adjunct only.
Authorized purpose: SubtleSYNTH is a software medical device consisting of a machine-learning algorithm that synthesizes a SynthSTIR contrast image from T1-weighted and T2-weighted spine MR 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.