Authorized purpose: Automatically segment lower-extremity muscle and bone structures from MRI in patients aged 18 years and older and provide derived muscle volume, bone volume, intramuscular fat percentage, and left/right asymmetry metrics; the output is not direct disease diagnosis.
Clinical role
Post-acquisition MRI preprocessing and 3D volume segmentation followed by interactive visualization and metric review; segmentation results must be reviewed and edited using appropriate software.
Images and patients
MRI · Lower extremities; 72 muscles and 8 bones including pelvis, femur, tibia, and fibula, bilaterally
Key limitation
Keep in mind: The labeled scope is patients aged 18 years and older and excludes patients with tumors in the lower limb. Outputs are only segmentation and derived metrics, cannot directly guide disease diagnosis, and require physician review and editing with appropriate software. The FDA summary does not establish PACS, RIS, EHR, or cloud deployment.
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: Automatically segment lower-extremity muscle and bone structures from MRI in patients aged 18 years and older and provide derived muscle volume, bone volume, intramuscular fat percentage, and left/right asymmetry metrics; the output is not direct disease diagnosis.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Lower extremities; 72 muscles and 8 bones including pelvis, femur, tibia, and fibula, bilaterally Input: MRI DICOM data from one or more study series, preprocessed into continuous 3D volumes for lower-extremity musculoskeletal segmentation; validation covered multiple manufacturers, field strengths, series settings, and resolutions.
Who uses it?Intended users: Physicians trained to interpret MRI images.
What does the software produce?Output: Automatic segmentations and an interactive 3D model viewer for the supported muscles and bones, with segmentation volume, muscle volume, bone volume, intramuscular fat infiltration or percentage, limb-side asymmetry, and other derived metrics.
What is its most important limitation?Key limitation: The labeled scope is patients aged 18 years and older and excludes patients with tumors in the lower limb. Outputs are only segmentation and derived metrics, cannot directly guide disease diagnosis, and require physician review and editing with appropriate software. The FDA summary does not establish PACS, RIS, EHR, or cloud deployment.
Clinical takeaway. Clinical role: Automatically segment lower-extremity muscle and bone structures from MRI in patients aged 18 years and older and provide derived muscle volume, bone volume, intramuscular fat percentage, and left/right asymmetry metrics; the output is not direct disease diagnosis.
Evidence takeaway. Evidence from the reviewed source record: FDA AI validation used 1,658 training scans from 1,294 subjects and 148 validation scans from 148 subjects; 70% of validation data came from 19 new sites and the validation set covered Siemens, GE, Philips, Canon, and other or unknown MRI systems. Expert manual segmentations were the reference standard. Each of the 80 supported structures and reported healthy, patient, manufacturer, age, and biologic-sex subgroups passed prespecified acceptance criteria using either Dice similarity coefficient or volume difference relative to interobserver variability. The reviewed text does not provide a single overall sensitivity, specificity, AUC, or one pooled numeric result.
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
Automatically segment lower-extremity muscle and bone structures from MRI in patients aged 18 years and older and provide derived muscle volume, bone volume, intramuscular fat percentage, and left/right asymmetry metrics; the output is not direct disease diagnosis.
Post-acquisition MRI preprocessing and 3D volume segmentation followed by interactive visualization and metric review; segmentation results must be reviewed and edited using appropriate software.
MRI DICOM data from one or more study series, preprocessed into continuous 3D volumes for lower-extremity musculoskeletal segmentation; validation covered multiple manufacturers, field strengths, series settings, and resolutions.
Automatic segmentations and an interactive 3D model viewer for the supported muscles and bones, with segmentation volume, muscle volume, bone volume, intramuscular fat infiltration or percentage, limb-side asymmetry, and other derived metrics.
The labeled scope is patients aged 18 years and older and excludes patients with tumors in the lower limb. Outputs are only segmentation and derived metrics, cannot directly guide disease diagnosis, and require physician review and editing with appropriate software. The FDA summary does not establish PACS, RIS, EHR, or cloud deployment.
FDA AI validation used 1,658 training scans from 1,294 subjects and 148 validation scans from 148 subjects; 70% of validation data came from 19 new sites and the validation set covered Siemens, GE, Philips, Canon, and other or unknown MRI systems. Expert manual segmentations were the reference standard. Each of the 80 supported structures and reported healthy, patient, manufacturer, age, and biologic-sex subgroups passed prespecified acceptance criteria using either Dice similarity coefficient or volume difference relative to interobserver variability. The reviewed text does not provide a single overall sensitivity, specificity, AUC, or one pooled numeric result.
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 AI validation used 1,658 training scans from 1,294 subjects and 148 validation scans from 148 subjects; 70% of validation data came from 19 new sites and the validation set covered Siemens, GE, Philips, Canon, and other or unknown MRI systems. Expert manual segmentations were the reference standard. Each of the 80 supported structures and reported healthy, patient, manufacturer, age, and biologic-sex subgroups passed prespecified acceptance criteria using either Dice similarity coefficient or volume difference relative to interobserver variability. The reviewed text does not provide a single overall sensitivity, specificity, AUC, or one pooled numeric result.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
MuscleView regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K241331
Samplen=148
IndependenceIndependence not established
K241331
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 K241331. 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: MRI DICOM data from one or more study series, preprocessed into continuous 3D volumes for lower-extremity musculoskeletal segmentation; validation covered multiple manufacturers, field strengths, series settings, and resolutions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Processes DICOM data on a private-network GPU workstation as a service and uses a web-based interface for data transfer, automated segmentation, and visualization. Specific hospital-system interfaces and local compatibility are not established.
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: The exact FDA package describes MuscleView as deployed within a private network on a workstation with an advanced graphic processing unit (GPU), running as a service accessed through a web-based interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The software is deployed within a private network on a workstation with an advanced graphic processing unit (GPU) and runs as a service." … "A web-based interface is used to access the service and manage the data transfer, automatic segmentation, and visualization.". 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: Automatic segmentations and an interactive 3D model viewer for the supported muscles and bones, with segmentation volume, muscle volume, bone volume, intramuscular fat infiltration or percentage, limb-side asymmetry, and other derived metrics.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Automatic segmentations and an interactive 3D model viewer for the supported muscles and bones, with segmentation volume, muscle volume, bone volume, intramuscular fat infiltration or percentage, limb-side asymmetry, and other derived metrics.
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 MuscleView as deployed within a private network on a workstation with an advanced graphic processing unit (GPU), running as a service accessed through a web-based interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software is deployed within a private network on a workstation with an advanced graphic processing unit (GPU) and runs as a service." … "A web-based interface is used to access the service and manage the data transfer, automatic segmentation, and visualization.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Processes DICOM data on a private-network GPU workstation as a service and uses a web-based interface for data transfer, automated segmentation, and visualization. Specific hospital-system interfaces and local compatibility are not established.
ACR AI Central provides an exact-submission model card for MuscleView; FDA labeling remains controlling for clinical use, limitations, and performance.
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
22Fields reviewed
9Source 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, 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-08 - Exact FDA submission
No public price or quote for the exact K241331 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-08 - 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.
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-08 - 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-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Post-process previously acquired cervical-spine MR images to segment vertebrae and disks, calculate quantitative measurements, label out-of-range values, and export results for user review and interpretation.
Modality
MRI
Anatomy
Cervical spine: vertebrae C3-C7 and disks C2C3 through C7T1
Authorized purpose: Automatic MRI segmentation and quantitative analysis of muscle, bone, fat, and other anatomical structures to assist visualization and measurement; not direct disease diagnosis.
Modality
MRI
Anatomy
Muscles, bones, and adipose tissue across the lower extremities and upper body from neck to hips, plus other segmented structures
Authorized purpose: Semi-automatic lumbar MRI segmentation and area and distance measurements with radiologist-approved PDF report to PACS; adjunct only.
Authorized purpose: Assist physicians in reviewing previously acquired lumbar-spine MRI by providing user-confirmed anatomy identification, segmentation, labeling, measurements, and reporting; it is not a diagnostic device.
Modality
MRI
Anatomy
Lumbar spine, including vertebral bodies L1-S1, intervertebral discs, cord canal, dural sac, nerve roots, and posterior arch.
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.