Authorized purpose: HYPER AiR provides the cleared nuclear-medicine image-processing support described in K210001 for supported PET/CT studies; outputs require review by qualified professionals and do not establish product-wide clinical performance.
Clinical role
PET or nuclear-medicine acquisition, reconstruction, visualization, quantitative review, and release-specific processing support.
Images and patients
PET/SPECT/Nuclear Medicine · Whole body and organs represented in supported PET/CT studies
Key limitation
Keep in mind: Radiopharmaceutical, scan range, patient-size, acquisition, reconstruction, dose, and quantitative limits are configuration-specific; 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 AiR provides the cleared nuclear-medicine image-processing support described in K210001 for supported PET/CT studies; outputs require review by qualified professionals and do not establish product-wide clinical performance.
Which images or clinical context are in scope?Modality: PET/SPECT/Nuclear Medicine Anatomy or clinical context: Whole body and organs represented in supported PET/CT studies Input: Positron-emission or radioisotope-tracer data, CT transmission data, patient information, and supported studies.
Who uses it?Intended users: Qualified nuclear-medicine physicians, radiologists, technologists, and other trained PET/CT professionals.
What does the software produce?Output: Processed PET, SPECT, CT, fused, quantitative, or planning images for professional interpretation.
What is its most important limitation?Key limitation: Radiopharmaceutical, scan range, patient-size, acquisition, reconstruction, dose, and quantitative limits are configuration-specific; decisions remain with qualified clinicians.
Clinical takeaway. Clinical role: HYPER AiR provides the cleared nuclear-medicine image-processing support described in K210001 for supported PET/CT studies; outputs require review by qualified professionals and do not establish product-wide clinical performance.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports engineering bench testing that reconstructed identical raw datasets from uMI 780 and uMI 550 systems with HYPER AiR and OSEM and compared noise, contrast and contrast to noise ratio, and a clinical image evaluation in which three board-certified nuclear medicine physicians assessed image contrast, noise and quality, reporting better contrast and lower noise than OSEM with image quality sufficient for clinical diagnosis; software verification and validation is also reported. 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 AiR provides the cleared nuclear-medicine image-processing support described in K210001 for supported PET/CT studies; outputs require review by qualified professionals and do not establish product-wide clinical performance.
The exact FDA document reports engineering bench testing that reconstructed identical raw datasets from uMI 780 and uMI 550 systems with HYPER AiR and OSEM and compared noise, contrast and contrast to noise ratio, and a clinical image evaluation in which three board-certified nuclear medicine physicians assessed image contrast, noise and quality, reporting better contrast and lower noise than OSEM with image quality sufficient for clinical diagnosis; software verification and validation is also reported. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Engineering bench testing was performed to support substantial equivalence and the product performance claims. The evaluation and analysis used the identical raw datasets obtained on UIH's uMI 780 and uMI 550, and then applies both HYPER AiR and OSEM to do image reconstruction." … "Performance on contrast to noise ratio". 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 engineering bench testing that reconstructed identical raw datasets from uMI 780 and uMI 550 systems with HYPER AiR and OSEM and compared noise, contrast and contrast to noise ratio, and a clinical image evaluation in which three board-certified nuclear medicine physicians assessed image contrast, noise and quality, reporting better contrast and lower noise than OSEM with image quality sufficient for clinical diagnosis; software verification and validation is also reported. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Engineering bench testing was performed to support substantial equivalence and the product performance claims. The evaluation and analysis used the identical raw datasets obtained on UIH's uMI 780 and uMI 550, and then applies both HYPER AiR and OSEM to do image reconstruction." … "Performance on contrast to noise ratio". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint for this device 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 promoted as a product-wide endpoint for this device 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.
K210001 FDA evidence package for HYPER AiR
DesignFDA 510(k) substantial-equivalence decision evidence and product verification described in the exact submission.
PopulationWhole body and organs represented in supported PET/CT studies
Scopeexact submission
Tested versionHYPER AiR configuration described in K210001
IndependenceSponsor or vendor study
K210001
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 K210001 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, or surgical service line and verify payer, site-of-service, and coding 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: Positron-emission or radioisotope-tracer data, CT transmission data, patient information, and supported studies.
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 public FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, 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 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: Processed PET, SPECT, CT, fused, quantitative, or planning images for professional interpretation.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Processed PET, SPECT, CT, fused, quantitative, or planning images for professional interpretation.
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 nuclear-medicine physicians, radiologists, technologists, and other trained pet/ct 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 K210001 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 range, patient-size, acquisition, reconstruction, dose, and quantitative limits are configuration-specific; decisions remain with qualified 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 exact public integration contract remains incomplete; establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
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 range, patient-size, acquisition, reconstruction, dose, and quantitative limits are configuration-specific; 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.
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 K210001 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 range, patient-size, acquisition, reconstruction, dose, and quantitative limits are configuration-specific; decisions remain with qualified clinicians.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. PET/CT or nuclear-medicine imaging system or processing function 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
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 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.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact public FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
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.