Authorized purpose: uOmnispace is software for viewing, manipulating, communicating, storing, processing, and filming multimodality DICOM images, usable stand-alone or with cleared software options and multi-vendor applications meeting interface requirements; it is not intended to display digital mammography images for diagnosis in the United States.
Clinical role
Medical-image viewing, processing, segmentation, measurement, registration, communication, or planning support within the exact labeled scope.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Multi-region medical images, excluding U.S. digital mammography diagnosis
Key limitation
Keep in mind: Supported modalities, modules, anatomy, patient population, and output use are submission-specific; source images and generated results require expert review.
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 is software for viewing, manipulating, communicating, storing, processing, and filming multimodality DICOM images, usable stand-alone or with cleared software options and multi-vendor applications meeting interface requirements; it is not intended to display digital mammography images for diagnosis in the United States.
Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Multi-region medical images, excluding U.S. digital mammography diagnosis Input: DICOM or other medical-image data from the exact labeled modalities, scanners, and user workflow.
Who uses it?Intended users: Trained healthcare professionals, physicians, technicians, surgeons, or other users specified by the exact submission.
What does the software produce?Output: Images, measurements, segmentations, models, reports, or planning information for professional review.
What is its most important limitation?Key limitation: Supported modalities, modules, anatomy, patient population, and output use are submission-specific; source images and generated results require expert review.
Clinical takeaway. Clinical role: uOmnispace is software for viewing, manipulating, communicating, storing, processing, and filming multimodality DICOM images, usable stand-alone or with cleared software options and multi-vendor applications meeting interface requirements; it is not intended to display digital mammography images for diagnosis in the United States.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation and performance testing of the ML-based rib segmentation algorithm on 60 subjects, with ground truth checked and modified by a senior clinical specialist; the average Dice was 0.855 against an acceptance criterion of higher than 0.8, and subgroup performance was consistent. 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
uOmnispace is software for viewing, manipulating, communicating, storing, processing, and filming multimodality DICOM images, usable stand-alone or with cleared software options and multi-vendor applications meeting interface requirements; it is not intended to display digital mammography images for diagnosis in the United States.
Supported modalities, modules, anatomy, patient population, and output use are submission-specific; source images and generated results require expert review.
The exact FDA document reports software verification and validation and performance testing of the ML-based rib segmentation algorithm on 60 subjects, with ground truth checked and modified by a senior clinical specialist; the average Dice was 0.855 against an acceptance criterion of higher than 0.8, and subgroup performance was consistent. 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." … "The performance testing for ML-based rib segmentation algorithm was performed on 60 subjects (data shown in Table 8-2) during the product development.". 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 performance testing of the ML-based rib segmentation algorithm on 60 subjects, with ground truth checked and modified by a senior clinical specialist; the average Dice was 0.855 against an acceptance criterion of higher than 0.8, and subgroup performance was consistent. 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." … "The performance testing for ML-based rib segmentation algorithm was performed on 60 subjects (data shown in Table 8-2) during the product development.". Read from the exact FDA decision document on 2026-11-14.
No exact-submission and version-linked sensitivity endpoint is promoted; candidate or product-family values were not substituted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact-submission and version-linked specificity endpoint is promoted; candidate or product-family values were not substituted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
FDA submission-specific verification and validation evidence for K230039
DesignFDA 510(k) regulatory decision material and submission-specific verification or validation evidence for K230039; this is regulatory evidence, not an independent clinical effectiveness study.
PopulationThe labeled population, anatomy, images, and test materials described in the exact FDA decision material for K230039; a broader clinical population is not established here.
Scopeexact submission
Tested versionuOmnispace (K230039)
IndependenceSponsor or vendor study
K230039
The exact FDA material is submission-specific and should not be generalized to other versions, enabled options, sites, protocols, or clinical outcomes.
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
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 or other medical-image data from the exact labeled modalities, scanners, and user workflow.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA indication describes plug-in multi-vendor applications that meet interface requirements; local PACS, identity, routing, storage, and application compatibility require confirmation.
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 indication describes stand-alone use or use with cleared software options and compatible multi-vendor applications; hosting, server topology, retention, and local operational requirements are not established.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Images, measurements, segmentations, models, reports, or planning information 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 indication describes stand-alone use or use with cleared software options and compatible multi-vendor applications; hosting, server topology, retention, and local operational requirements are not established.
The exact FDA indication describes plug-in multi-vendor applications that meet interface requirements; local PACS, identity, routing, storage, and application compatibility require confirmation.
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.
The exact FDA indication describes stand-alone use or use with cleared software options and compatible multi-vendor applications; hosting, server topology, retention, and local operational requirements are not established.
exact submission · checked 2026-09-04
Confirm hosting, PHI flow, retention, access, updates, downtime, and support obligations before procurement or clinical use.
The exact FDA indication describes plug-in multi-vendor applications that meet interface requirements; local PACS, identity, routing, storage, and application compatibility require confirmation.
exact submission · checked 2026-09-04
Validate the local workflow against the exact release and enabled options.
Current vendor material is product-family context for K230039 only; exact release, enabled options, deployment, security, interoperability, pricing, and local workflow require confirmation.
product family · checked 2026-09-04
Vendor material is not exact-release evidence unless that linkage is separately proven.
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
31Fields 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, vendor documentation, vendor product page, implementation documentation, reimbursement policy, peer reviewed literature, clinical trial registry, 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 exact-release price, license fee, subscription, contract, or implementation cost 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 applicable - checked 2026-09-04 - Not applicable
CMS coverage-index context was checked, but no product-specific coverage or reimbursement determination is inferred.
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: Synapse 3D Base Tools assists trained professionals with reading, interpreting, reporting, and treatment planning from DICOM data from CT, MR, CR, US, NM, PT, XA, and other supported modalities; the base tools are not primary mammography interpretation.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Multi-region anatomy represented in CT, MR, CR, US, NM, PT, and XA studies
Authorized purpose: VersaViewer supports two-dimensional, three-dimensional, and four-dimensional medical-image series processing and analysis through customizable layouts, multimodality review, and measurements for trained healthcare professionals; it is not for displaying digital mammography for diagnosis.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Multi-region anatomy represented in CT, MR, PET, NM, XA, and other supported studies
Authorized purpose: RadioLens v1.0 is a medical diagnostic application for displaying, processing, storing, and transferring DICOM data other than mammography, with filtering, digital manipulation, and quantitative measurements; its optional SpindleX module analyzes potential vertebral displacement in adult cervical or lumbar spine stress X-rays and calculates measurements related to spinal-ligament injury leading to subluxation.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Spine, including cervical and lumbar vertebrae; general DICOM images excluding mammography
Authorized purpose: Syngo Dynamics VA40F is a multimodality, vendor-agnostic cardiology image and information system for medical-image management and processing, with post-processing functions for image manipulation and quantification supporting interpretation and analysis for disease detection, diagnosis, and patient management within a healthcare institution's network.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Anatomy represented in multimodality cardiology medical images, excluding U.S. digital mammography diagnosis
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.