Authorized purpose: HYPER DLR is an image-processing function intended for radiologists and nuclear-medicine physicians to reduce noise in fluorodeoxyglucose PET images. The software is intended to be implemented on the previously cleared uMI 550 and uMI 780 PET/CT devices.
Clinical role
Nuclear-medicine image acquisition support, reconstruction, display, quantification, analysis, or comparison under professional review.
Images and patients
PET/SPECT/Nuclear Medicine · Whole-body FDG PET images
Key limitation
Keep in mind: Radiopharmaceutical, scan, reconstruction, quantitative, anatomy, and patient limits are exact-configuration dependent; clinical decisions remain with qualified 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: HYPER DLR is an image-processing function intended for radiologists and nuclear-medicine physicians to reduce noise in fluorodeoxyglucose PET images. The software is intended to be implemented on the previously cleared uMI 550 and uMI 780 PET/CT devices.
Which images or clinical context are in scope?Modality: PET/SPECT/Nuclear Medicine Anatomy or clinical context: Whole-body FDG PET images Input: Supported PET, SPECT, nuclear-medicine, CT, MR, tracer, physiologic-signal, and study inputs described in the labeling.
Who uses it?Intended users: Qualified radiologists, nuclear-medicine physicians, and trained imaging professionals.
What does the software produce?Output: Processed, fused, quantitative, comparative, and report-ready molecular-imaging views for professional review.
What is its most important limitation?Key limitation: Radiopharmaceutical, scan, reconstruction, quantitative, anatomy, and patient limits are exact-configuration dependent; clinical decisions remain with qualified clinicians.
Clinical takeaway. Clinical role: HYPER DLR is an image-processing function intended for radiologists and nuclear-medicine physicians to reduce noise in fluorodeoxyglucose PET images. The software is intended to be implemented on the previously cleared uMI 550 and uMI 780 PET/CT devices.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing comparing HYPER DLR with Gaussian filtering on identical raw datasets from uMI 780 and uMI 550, stating HYPER DLR can significantly improve SNR and CNR while preserving image consistency; and a clinical image evaluation in which board-certified nuclear medicine physicians assessed image noise and overall image quality, finding lower image noise than Gaussian filtering with image quality sufficient for clinical diagnosis. No clinical study is included. 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
HYPER DLR is an image-processing function intended for radiologists and nuclear-medicine physicians to reduce noise in fluorodeoxyglucose PET images. The software is intended to be implemented on the previously cleared uMI 550 and uMI 780 PET/CT devices.
The exact FDA document reports bench testing comparing HYPER DLR with Gaussian filtering on identical raw datasets from uMI 780 and uMI 550, stating HYPER DLR can significantly improve SNR and CNR while preserving image consistency; and a clinical image evaluation in which board-certified nuclear medicine physicians assessed image noise and overall image quality, finding lower image noise than Gaussian filtering with image quality sufficient for clinical diagnosis. No clinical study is included. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The evaluation and analysis used the identical raw datasets obtained on UIH’s uMI 780 and uMI 550, and then applies both HYPER DLR and Gaussian filtering to do image de-noising." … "Bench test showed overall image quality improvement based on the commonly used quantitative metrics. HYPER DLR can significantly improve SNR and CNR while preserving image consistency.". 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 bench testing comparing HYPER DLR with Gaussian filtering on identical raw datasets from uMI 780 and uMI 550, stating HYPER DLR can significantly improve SNR and CNR while preserving image consistency; and a clinical image evaluation in which board-certified nuclear medicine physicians assessed image noise and overall image quality, finding lower image noise than Gaussian filtering with image quality sufficient for clinical diagnosis. No clinical study is included. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "The evaluation and analysis used the identical raw datasets obtained on UIH’s uMI 780 and uMI 550, and then applies both HYPER DLR and Gaussian filtering to do image de-noising." … "Bench test showed overall image quality improvement based on the commonly used quantitative metrics. HYPER DLR can significantly improve SNR and CNR while preserving image consistency.". 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, study design, and source if separately 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, study design, and source if separately verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K193210 FDA decision evidence package for HYPER DLR
DesignFDA decision evidence and product verification described in the exact submission or PMA decision record.
PopulationWhole-body FDG PET images
Scopeexact submission
Tested versionHYPER DLR configuration described in K193210
IndependenceSponsor or vendor study
K193210
FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; 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 K193210 by exact native submission identifier. This does not exclude product-family, later-version, 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.
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 PET, SPECT, nuclear-medicine, CT, MR, tracer, physiologic-signal, and study inputs described in the labeling.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes HYPER DLR as a post-processing function on supported uMI 550 or uMI 780 PET/CT reconstruction systems; verify the installed device, reconstruction path, and archive behavior.
Scope: Exact FDA submission. This is a partial 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.
Source context, not route validation: The exact FDA package describes implementation on the facility PET/CT reconstruction computer, with Windows and online or offline workflow support; current hosting, service, version, and site qualification remain unknown.
Scope: Exact FDA submission. This is a partial release-level topology fact from the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Processed, fused, quantitative, comparative, and report-ready molecular-imaging views 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 implementation on the facility PET/CT reconstruction computer, with Windows and online or offline workflow support; current hosting, service, version, and site qualification remain unknown.
Exact FDA submission
Checked 2026-09-04
This is a partial release-level topology fact from the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
The exact FDA package describes HYPER DLR as a post-processing function on supported uMI 550 or uMI 780 PET/CT reconstruction systems; verify the installed device, reconstruction path, and archive behavior.
Exact FDA submission
Checked 2026-09-04
This is a partial 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 qualified radiologists, nuclear-medicine physicians, and trained 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 K193210 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: Radiopharmaceutical, scan, reconstruction, quantitative, anatomy, and patient limits are exact-configuration dependent; clinical decisions remain with qualified clinicians.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The exact FDA package describes implementation on the facility PET/CT reconstruction computer, with Windows and online or offline workflow support; current hosting, service, version, and site qualification remain unknown.
exact submission · checked 2026-09-04
FDA-described topology does not establish current hosting contracts, security controls, uptime, or local qualification.
The exact FDA package describes HYPER DLR as a post-processing function on supported uMI 550 or uMI 780 PET/CT reconstruction systems; verify the installed device, reconstruction path, and archive behavior.
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. Radiopharmaceutical, scan, reconstruction, quantitative, anatomy, and patient limits are exact-configuration dependent; clinical decisions remain with qualified 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.
exact submission · checked 2026-09-04
No exact-product price or reimbursement determination was promoted.
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
10Source 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, 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 authorized 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
Reimbursement: Not publicly available - checked 2026-09-04 - Exact FDA submission
No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.
Authorized purpose: uMI Panvivo variants acquire and display PET and CT information for anatomical and functional imaging, radiopharmaceutical distribution, attenuation correction, and the labeled body-region workflows.
Modality
PET/SPECT/Nuclear Medicine
Anatomy
Whole body; brain; head and neck; heart; lung; breast; gastrointestinal; urinary; genital; and musculoskeletal anatomy
Authorized purpose: uMI Panvivo PET/CT acquires anatomical CT and functional PET images of radiopharmaceutical distribution for qualified diagnostic and treatment-planning workflows, including labeled lung-cancer-screening use.
Modality
PET/SPECT/Nuclear Medicine
Anatomy
Whole body, head and neck, cardiac, and other labeled PET/CT regions
Authorized purpose: BIOGRAPH One with syngo MR XB10 combines metabolic or physiologic PET information with MR anatomy, MR-based attenuation correction, fused alignment, and support for treatment planning and interventions.
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.