Authorized purpose: uWS-MR provides MR image viewing, manipulation, communication, storage, stitching, fusion, spectroscopy, parameter maps, breast evaluation, brain perfusion, and related processing for interpretation and evaluation within healthcare institutions.
Clinical role
MR viewing, manipulation, fusion, quantitative processing, and reporting support.
Images and patients
MRI · Head, body, breast, brain, and other anatomy represented in supported MR examinations
Key limitation
Keep in mind: The available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
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: uWS-MR provides MR image viewing, manipulation, communication, storage, stitching, fusion, spectroscopy, parameter maps, breast evaluation, brain perfusion, and related processing for interpretation and evaluation within healthcare institutions.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Head, body, breast, brain, and other anatomy represented in supported MR examinations Input: Supported MR DICOM studies and release-specific user inputs.
Who uses it?Intended users: Trained physicians and qualified MR imaging professionals.
What does the software produce?Output: Cross-sectional or derived MR images, maps, spectra, measurements, and reports.
What is its most important limitation?Key limitation: The available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
Clinical takeaway. Clinical role: uWS-MR provides MR image viewing, manipulation, communication, storage, stitching, fusion, spectroscopy, parameter maps, breast evaluation, brain perfusion, and related processing for interpretation and evaluation within healthcare institutions.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation testing, including a hazard analysis with potential hazards classified as a moderate level of concern, and lists a Performance Evaluation Report for MR Cardiac Analysis without reporting its results. Biocompatibility and electrical safety/EMC testing were not applicable because the device is stand-alone software, and the document states no animal study and no clinical study was required. Results are as reported in the FDA submission, not independent validation.
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
uWS-MR provides MR image viewing, manipulation, communication, storage, stitching, fusion, spectroscopy, parameter maps, breast evaluation, brain perfusion, and related processing for interpretation and evaluation within healthcare institutions.
The available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
The exact FDA document reports software verification and validation testing, including a hazard analysis with potential hazards classified as a moderate level of concern, and lists a Performance Evaluation Report for MR Cardiac Analysis without reporting its results. Biocompatibility and electrical safety/EMC testing were not applicable because the device is stand-alone software, and the document states no animal study and no clinical study was required. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Software verification and validation testing was provided to demonstrate safety and efficacy of the proposed device. This includes a hazard analysis, and the potential hazards have been classified as a moderate level of concern (LOC)." … "Performance Verification Performance Evaluation Report for MR Cardiac Analysis". 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, including a hazard analysis with potential hazards classified as a moderate level of concern, and lists a Performance Evaluation Report for MR Cardiac Analysis without reporting its results. Biocompatibility and electrical safety/EMC testing were not applicable because the device is stand-alone software, and the document states no animal study and no clinical study was required. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Software verification and validation testing was provided to demonstrate safety and efficacy of the proposed device. This includes a hazard analysis, and the potential hazards have been classified as a moderate level of concern (LOC)." … "Performance Verification Performance Evaluation Report for MR Cardiac Analysis". 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.
K192601 FDA evidence package for uWS-MR
DesignFDA 510(k) or PMA decision evidence and product verification described in the exact submission.
PopulationHead, body, breast, brain, and other anatomy represented in supported MR examinations
Scopeexact submission
Tested versionuWS-MR configuration described in K192601
IndependenceSponsor or vendor study
K192601
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 K192601 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.
Acquisition/source
Source context, not route validation: Supported MR DICOM studies and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes MR image storage, communication, and processing within healthcare institutions; exact interface and archive behavior remain unverified.
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.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact public 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: Cross-sectional or derived MR images, maps, spectra, measurements, and reports.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cross-sectional or derived MR images, maps, spectra, measurements, and reports.
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 MR image storage, communication, and processing within healthcare institutions; exact interface and archive behavior remain unverified.
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.
United Imaging Healthcare's cybersecurity page lists a secure development lifecycle and controls: firewall, encrypted connections, OS hardening, antivirus, patches, authentication, audit log, disk and transmission encryption. Company-level, not release-specific.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; exact-release scope is not established.
Only trained physicians and qualified mr 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 K192601 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 available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
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.
The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes MR image storage, communication, and processing within healthcare institutions; exact interface and archive behavior remain unverified.
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 supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
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 K192601 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 available MR applications, maps, fusion, spectroscopy, and measurement functions depend on the exact installed release and supported input data; interpretation remains with clinicians.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. MR image viewing and processing 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-20Last searched
27Fields reviewed
14Source 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, vendor documentation, 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 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact public FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Authorized purpose: SIGNA Bolt is a whole-body MRI system for high-resolution diagnostic imaging of the labeled body regions, with supported AI-assisted reconstruction, positioning, and protocol functions.
Authorized purpose: SIGNA Sprint Select is a whole-body MRI system for diagnostic imaging of the labeled body regions, with supported AI-assisted reconstruction, positioning, and protocol functions.
Authorized purpose: SIGNA Sprint is a 1.5T whole-body MRI system for diagnostic imaging of the labeled head, neck, TMJ, spine, breast, heart, abdomen, pelvis, joints, prostate, vessels, and musculoskeletal regions.
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.