Authorized purpose: Prenuvo Body Composition is software that non-invasively quantifies fat, muscle, and organs from compatible MR DICOM datasets and displays internal body information, including liver and body-composition measurements, for adults age 18 and older.
Clinical role
Quantification and visualization support for the labeled imaging datasets under professional review.
Images and patients
MRI · Whole-body anatomy, liver, organs, fat, and muscle
Key limitation
Keep in mind: Quantification is limited by the cleared dataset, scanner, acquisition, population, and metric definitions; clinical interpretation remains with qualified professionals.
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: Prenuvo Body Composition is software that non-invasively quantifies fat, muscle, and organs from compatible MR DICOM datasets and displays internal body information, including liver and body-composition measurements, for adults age 18 and older.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Whole-body anatomy, liver, organs, fat, and muscle Input: Compatible DICOM imaging datasets and release-specific demographic or study metadata.
Who uses it?Intended users: Qualified physicians and trained healthcare professionals responsible for the labeled imaging or analysis workflow.
What does the software produce?Output: Measurements, quantified tissue or organ values, visualizations, and derived objects for professional review.
What is its most important limitation?Key limitation: Quantification is limited by the cleared dataset, scanner, acquisition, population, and metric definitions; clinical interpretation remains with qualified professionals.
Clinical takeaway. Clinical role: Prenuvo Body Composition is software that non-invasively quantifies fat, muscle, and organs from compatible MR DICOM datasets and displays internal body information, including liver and body-composition measurements, for adults age 18 and older.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA 510(k) decision material establishes the submission identity, labeled use, inputs, population, and configuration boundary summarized here. No product-wide clinical-performance or outcome claim is promoted without an exact endpoint and version linkage.
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
Prenuvo Body Composition is software that non-invasively quantifies fat, muscle, and organs from compatible MR DICOM datasets and displays internal body information, including liver and body-composition measurements, for adults age 18 and older.
Quantification is limited by the cleared dataset, scanner, acquisition, population, and metric definitions; clinical interpretation remains with qualified professionals.
The exact FDA 510(k) decision material establishes the submission identity, labeled use, inputs, population, and configuration boundary summarized here. No product-wide clinical-performance or outcome claim is promoted without an exact endpoint and version linkage.
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 510(k) decision material establishes the submission identity, labeled use, inputs, population, and configuration boundary summarized here. No product-wide clinical-performance or outcome claim is promoted without an exact endpoint and version linkage.
No exact submission-linked sensitivity endpoint with a verified population, threshold, tested version, and source was promoted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact submission-linked specificity endpoint with a verified population, threshold, tested version, and source was promoted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K242825 FDA evidence package for Prenuvo Body Composition
DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
PopulationLabeled population and configuration described in the K242825 FDA decision material
Scopeexact submission
Tested versionPrenuvo Body Composition configuration described in K242825
IndependenceSponsor or vendor study
K242825
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 K242825 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, procedural, or surgical service line and verify payer, site-of-service, and coding 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.
Acquisition/source
Source context, not route validation: Compatible DICOM imaging datasets and release-specific demographic or study metadata.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes Prenuvo Body Composition as designed to utilize DICOM-compliant magnetic resonance image datasets acquired from compatible MR systems. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "Designed to utilize DICOM-compliant magnetic-resonance image datasets acquired from compatible MR Systems, it displays the internal structure of the body, including the liver.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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 material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Measurements, quantified tissue or organ values, visualizations, and derived objects for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Measurements, quantified tissue or organ values, visualizations, and derived objects for professional 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 exact FDA package describes Prenuvo Body Composition as designed to utilize DICOM-compliant magnetic resonance image datasets acquired from compatible MR systems. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Designed to utilize DICOM-compliant magnetic-resonance image datasets acquired from compatible MR Systems, it displays the internal structure of the body, including the liver.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Only qualified physicians and trained healthcare professionals responsible for the labeled imaging or analysis workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
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 exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Quantification is limited by the cleared dataset, scanner, acquisition, population, and metric definitions; clinical interpretation remains with qualified professionals.
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 reviewed public material; productivity or value claims require local evidence.
Monitor 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.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.
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
12Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
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.
Installation timeline: Not yet reviewed
Monitoring: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision and checked recall snapshot do not establish a complete local postmarket monitoring protocol. Track version, population, anatomy, protocol, input quality, edits, failures, repeats, downstream effects, downtime, incidents, recalls, and updates locally.
Authorized purpose: LiverMultiScan v6.0 is MR diagnostic software for non-invasive liver-health assessment that generates, displays, and supports review of MR data and quantitative cT1, PDFF, and LIC metrics or composite images for trained healthcare-professional interpretation.
Authorized purpose: TumorSight Viz processes dynamic contrast-enhanced breast MRI for patients with biopsy-proven early-stage or locally advanced breast cancer, providing registration, subtraction, segmentation, 3D renderings, measurements, kinetic curves, parametric maps, MIPs, and reformats for physician visualization and analysis; results are not the sole basis for patient management.
Authorized purpose: Visualize and analyze DCE breast MRI studies for patients with biopsy-proven early-stage or locally advanced breast cancer, including processing, measurements, and configurable finding visualization; results are not a sole basis for patient management.
Modality
MRI
Anatomy
Breast, including biopsy-proven breast tumors/findings.
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.