HYPER DLR
Shanghai United Imaging Healthcare Co., Ltd. • Radiology • 08/04/2020
Device Purpose
HYPER DLR is a software-only medical device intended to enhance fluorodeoxyglucose (FDG) PET image quality by reducing noise through a pre-trained convolutional neural network, functioning as an image post-processing technique. This method aims to offer superior noise reduction and image detail preservation compared to traditional Gaussian filtering, thereby potentially improving diagnostic confidence for clinicians using compatible uMI 550 and uMI 780 PET/CT systems.
Summary
HYPER DLR is a software-only device designed for image post-processing on existing uMI 550 and uMI 780 PET/CT systems. Its primary purpose is to reduce noise in fluorodeoxyglucose (FDG) PET images, thereby aiding radiologists and nuclear medicine physicians in their diagnostic interpretations. The core technology involves a pre-trained convolutional neural network that processes high-noise PET images to predict and generate low-noise versions by specifically extracting the noise component, distinguishing it from useful image details, which offers an alternative to traditional image smoothing techniques like Gaussian filtering. The performance of HYPER DLR was assessed through non-clinical testing, including engineering bench tests and clinical image evaluations, without conducting new clinical studies. Bench testing compared HYPER DLR against Gaussian filtering using identical raw datasets from uMI 780 and uMI 550 systems, evaluating metrics such as peak signal-to-noise ratio, structural similarity index, SNR, and CNR. These tests demonstrated that HYPER DLR significantly improved SNR and CNR while preserving image consistency. Clinical image evaluations by board-certified nuclear medicine physicians indicated that HYPER DLR produced images with lower noise than Gaussian filtering and maintained sufficient diagnostic quality, an observation consistent across typical clinical scan times for the compatible PET/CT systems.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the performance of HYPER DLR vary with different levels of initial image noise and varying radiotracer uptake in FDG PET scans beyond the tested scenarios?; What are the specific architectural details and training dataset characteristics of the pre-trained convolutional neural network in HYPER DLR that ensure its robustness and generalizability across diverse patient demographics and acquisition protocols?; Beyond the reported qualitative improvements and standard image quality metrics (SNR, CNR), how does HYPER DLR quantitatively affect standardized uptake values (SUVs) and lesion detectability, particularly for small or low-contrast lesions, compared to Gaussian filtering?; Are there any specific types of image artifacts that HYPER DLR might introduce or be less effective at mitigating compared to traditional methods, and what is the learning curve for physicians to interpret HYPER DLR-processed images?; What is the computational overhead (processing time per study) of HYPER DLR when integrated into the existing workflow of uMI 550 and uMI 780 systems, and how does it compare to the processing time of Gaussian filtering?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, SaaSBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly