Authorized purpose: uOmnispace.MR is a software solution for viewing, manipulating, evaluating, and analyzing medical images within healthcare institutions. The FDA indication lists MR stitching, dynamic studies, MR spectroscopy, maps and arithmetic functions, breast evaluation, brain perfusion, vessel analysis, dynamic contrast-enhanced analysis, neurological review, cardiac function, and flow analysis.
Clinical role
Medical-image processing, segmentation, enhancement, measurement, quantification, visualization, or reporting support under professional review.
Images and patients
MRI · Breast, brain, heart, vessels, and other labeled MR anatomy
Key limitation
Keep in mind: Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
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: uOmnispace.MR is a software solution for viewing, manipulating, evaluating, and analyzing medical images within healthcare institutions. The FDA indication lists MR stitching, dynamic studies, MR spectroscopy, maps and arithmetic functions, breast evaluation, brain perfusion, vessel analysis, dynamic contrast-enhanced analysis, neurological review, cardiac function, and flow analysis.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Breast, brain, heart, vessels, and other labeled MR anatomy Input: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Who uses it?Intended users: Qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow.
What does the software produce?Output: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
What is its most important limitation?Key limitation: Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
Clinical takeaway. Clinical role: uOmnispace.MR is a software solution for viewing, manipulating, evaluating, and analyzing medical images within healthcare institutions. The FDA indication lists MR stitching, dynamic studies, MR spectroscopy, maps and arithmetic functions, breast evaluation, brain perfusion, vessel analysis, dynamic contrast-enhanced analysis, neurological review, cardiac function, and flow analysis.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation and testing of new parameters and algorithms, including SER, T1rho and semi-automatic contour segmentation. The deep learning automatic ventricular segmentation algorithm was tested on 114 subjects by comparison with the predicate device's cardiac function application: Dice 1.00, against a consistency criterion of dice>0.95. No animal or 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
uOmnispace.MR is a software solution for viewing, manipulating, evaluating, and analyzing medical images within healthcare institutions. The FDA indication lists MR stitching, dynamic studies, MR spectroscopy, maps and arithmetic functions, breast evaluation, brain perfusion, vessel analysis, dynamic contrast-enhanced analysis, neurological review, cardiac function, and flow analysis.
Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
The exact FDA document reports software verification and validation and testing of new parameters and algorithms, including SER, T1rho and semi-automatic contour segmentation. The deep learning automatic ventricular segmentation algorithm was tested on 114 subjects by comparison with the predicate device's cardiac function application: Dice 1.00, against a consistency criterion of dice>0.95. No animal or 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." … "The performance functionality of new parameters or algorithms for uOmnispace.MR has been tested and validated, including SER (signal enhancement ratio) parameter in MR Breast Evaluation, T1rho parameter in MR MAPs, as well as semi-automatic contour segmentation for Contour Segmentation function,". 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 and testing of new parameters and algorithms, including SER, T1rho and semi-automatic contour segmentation. The deep learning automatic ventricular segmentation algorithm was tested on 114 subjects by comparison with the predicate device's cardiac function application: Dice 1.00, against a consistency criterion of dice>0.95. No animal or 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." … "The performance functionality of new parameters or algorithms for uOmnispace.MR has been tested and validated, including SER (signal enhancement ratio) parameter in MR Breast Evaluation, T1rho parameter in MR MAPs, as well as semi-automatic contour segmentation for Contour Segmentation function,". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not a product-wide endpoint for this system or software function. 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 a product-wide endpoint for this system or software function. 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.
K233186 FDA decision evidence for uOmnispace.MR
DesignFDA 510(k) substantial-equivalence review of the exact submission, device description, indications, and verification or validation documentation.
PopulationBreast, brain, heart, vessels, and other labeled MR anatomy
Scopeexact submission
Tested versionuOmnispace.MR
IndependenceSponsor or vendor study
K233186
The FDA decision material is manufacturer-submitted regulatory evidence. 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 K233186 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, surgical, or diagnostic 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: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, archive, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
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: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Images, segmentations, measurements, models, calculations, overlays, or reports that require 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.
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 qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow should operate or interpret this product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K233186 before acceptance. Later family features are not evidence for this exact submission.
The exact FDA material does not establish a complete interoperability contract. Establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
The exact FDA material does not establish hosting, deployment topology, availability, upgrade path, or service responsibility. Obtain site-specific evidence before procurement.
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. Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
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. No exact-product price was found.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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: Each named application has its own input, anatomy, protocol, and interpretation boundary. Product-family functionality, deployment, and current licenses must not be inferred beyond the exact submission.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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
33Fields reviewed
13Source 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, 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 or approved 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 FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, archive, and downtime locally.
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.