FDA-cleared profile

PIUR tUS inside

PIUR Imaging GmbH · Ultrasound · FDA-cleared (510(k))

Authorized purpose: 3D ultrasound reconstruction with physician-reviewed thyroid and nodule quantification and sonographic feature visualization.

Clinical role
Adjunct 3D reconstruction and quantitative visualization tool; the user reviews the reconstructed volume, annotations and report.
Images and patients
Ultrasound · Neck
Key limitation
Keep in mind: The reviewed labeling requires compatible GE ultrasound equipment and trained use; manual ACR TI-RADS assessment and clinician review remain part of the workflow.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: 3D ultrasound reconstruction with physician-reviewed thyroid and nodule quantification and sonographic feature visualization.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Neck Input: 2D ultrasound images plus PIUR sensor position data captured while the transducer is moved perpendicular to the thyroid structure.
  • Who uses it?Intended users: Trained healthcare professionals performing or interpreting thyroid ultrasound examinations.
  • What does the software produce?Output: An unlimited-length 3D volume intended to cover a thyroid lobe, user-selected or algorithm-suggested lobe and nodule volumes, sonographic feature views, annotated screenshots, reports and DICOM Secondary Capture objects.
  • What is its most important limitation?Key limitation: The reviewed labeling requires compatible GE ultrasound equipment and trained use; manual ACR TI-RADS assessment and clinician review remain part of the workflow.

Clinical takeaway. Clinical role: 3D ultrasound reconstruction with physician-reviewed thyroid and nodule quantification and sonographic feature visualization.

Evidence takeaway. Evidence from the reviewed source record: The FDA summary establishes the reconstruction workflow and DICOM/report outputs; it does not provide a numeric clinical performance endpoint in the reviewed summary.

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
3D ultrasound reconstruction with physician-reviewed thyroid and nodule quantification and sonographic feature visualization.
  • Exact FDA submission
  • Checked 2026-09-06
Workflow role
Adjunct 3D reconstruction and quantitative visualization tool; the user reviews the reconstructed volume, annotations and report.
  • Exact FDA submission
  • Checked 2026-09-06
Required input
2D ultrasound images plus PIUR sensor position data captured while the transducer is moved perpendicular to the thyroid structure.
  • Exact FDA submission
  • Checked 2026-09-06
Output and clinician action
An unlimited-length 3D volume intended to cover a thyroid lobe, user-selected or algorithm-suggested lobe and nodule volumes, sonographic feature views, annotated screenshots, reports and DICOM Secondary Capture objects.
  • Exact FDA submission
  • Checked 2026-09-06
Care setting
Ultrasound examination settings using a compatible GE Healthcare ultrasound system.
  • Exact FDA submission
  • Checked 2026-09-06
Intended users
Trained healthcare professionals performing or interpreting thyroid ultrasound examinations.
  • Exact FDA submission
  • Checked 2026-09-06
Limitations
The reviewed labeling requires compatible GE ultrasound equipment and trained use; manual ACR TI-RADS assessment and clinician review remain part of the workflow.
  • Exact FDA submission
  • Checked 2026-09-06
Evidence summary
The FDA summary establishes the reconstruction workflow and DICOM/report outputs; it does not provide a numeric clinical performance endpoint in the reviewed summary.
  • Exact FDA submission
  • Checked 2026-09-06

Evidence

Performance evidence

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 FDA summary establishes the reconstruction workflow and DICOM/report outputs; it does not provide a numeric clinical performance endpoint in the reviewed summary.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

PIUR tUS inside reconstruction and DICOM performance validation

  • DesignBench and workflow validation
  • PopulationThyroid ultrasound acquisitions using the reviewed compatible equipment and sensor workflow
  • Scopeexact submission
  • Tested versionPIUR tUS inside release reviewed in K250484
  • IndependenceSponsor or vendor study

K250484 FDA 510(k) summary

The reviewed FDA summary describes DICOM compliance and performance validation without a public numeric endpoint.

Safety and lifecycle

Postmarket record

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 & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
Service-level context only: the PIUR page discusses CPT 76376 and 76377 (3D ultrasound reconstruction) as commonly discussed Category I codes, and says code selection depends on where reconstruction runs and on the record produced. It names PIUR tUS inside (on GE LOGIQ E10, E10s and Fortis) but states PIUR gives no code advice, billing support or payment assurance. This is not product coverage and no payment amount is stated.
  • Service-level, not product-specific
  • Checked 2026-10-26

Vendor page read 2026-10-26 (last updated 2026-10-15). Service-level context; whether a payer covers or pays for this product depends on payer, site of service and documentation.

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: 2D ultrasound images plus PIUR sensor position data captured while the transducer is moved perpendicular to the thyroid structure.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-06 · FDA 510(k) decision record and summary reviewed for PIUR tUS inside, K250484

  2. Routing

    Source context, not route validation: The exact submission describes DICOM Secondary Capture storage objects and report outputs; the current PIUR resource set publishes DICOM and user-manual resources, but current site-specific integration was not established.

    Scope: Product family.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-07 · PIUR Imaging resources

  3. AI processing

    Source context, not route validation: FDA materials describe a Windows-based application running directly on compatible GE LOGIQ E10, E10s and Fortis systems.

    Scope: Exact FDA submission.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-06 · FDA 510(k) decision record and summary reviewed for PIUR tUS inside, K250484

  4. Returned objects

    Source context, not route validation: An unlimited-length 3D volume intended to cover a thyroid lobe, user-selected or algorithm-suggested lobe and nodule volumes, sonographic feature views, annotated screenshots, reports and DICOM Secondary Capture objects.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-06 · FDA 510(k) decision record and summary reviewed for PIUR tUS inside, K250484

  5. Viewer/worklist/report

    Unresolved route: An unlimited-length 3D volume intended to cover a thyroid lobe, user-selected or algorithm-suggested lobe and nodule volumes, sonographic feature views, annotated screenshots, reports and DICOM Secondary Capture objects.

    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.

    Field checked 2026-09-06 · FDA 510(k) decision record and summary reviewed for PIUR tUS inside, K250484

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
FDA materials describe a Windows-based application running directly on compatible GE LOGIQ E10, E10s and Fortis systems.
  • Exact FDA submission
  • Checked 2026-09-06
Integration
The exact submission describes DICOM Secondary Capture storage objects and report outputs; the current PIUR resource set publishes DICOM and user-manual resources, but current site-specific integration was not established.
  • Product family
  • Checked 2026-09-07
Training
PIUR publishes user manuals and training resources for the inside family; the exact K250484 onboarding or competency package was not established.
  • Product family
  • Checked 2026-09-07

Ultrasound hardware coupling

The exact labeling describes a PIUR sensor clipped to a transducer with a bracket and position data transferred by Bluetooth.

exact submission · checked 2026-09-06

GE system installation

The current family manual describes installation on compatible GE ultrasound systems and use of official brackets; exact K250484 installation steps are not established from that family manual.

product family · checked 2026-09-07

DICOM and report resources

PIUR publishes DICOM files, user manuals and training materials for its product family.

product family · checked 2026-09-07
Sources & review details FDA 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.

FDA submission
K250484
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Anatomy
Neck
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-06-30
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Human reviewedStatus
2026-09-07Last searched
22Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The stored candidate metadata contained empty PubMed and clinical-trial ID arrays; metadata was screened, not full-text or registry-reviewed. The stored recall candidate record was empty and no event 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, acr ai central product, vendor product page, vendor manual, peer reviewed publication, clinical trial registry, recall database, 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-07 - Exact FDA submission

    No numeric price was published in the reviewed sources.

  • 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
  • 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
  • Security: Not verified - checked 2026-09-07 - Exact FDA submission

    No current exact-release security attestation was established.

  • Installation timeline: Not yet reviewed
  • 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.

10 sources - 3 history items

Source ledger

  1. K250484 FDA decision source

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, purpose, modality, anatomy

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PIUR tUS inside model card (K250484)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, evidenceSummary, anatomy, evidenceStudies

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. FDA 510(k) decision record and summary reviewed for PIUR tUS inside, K250484

    U.S. Food and Drug Administration - Published 2025-06-30 - Accessed 2026-09-06

    Scope: identity, intended_use, performance, limitations, implementation

  8. PIUR tUS inside User Manual, English revision 15.0

    PIUR Imaging - Published 2025-10-10 - Accessed 2026-09-07

    Scope: product_family, clinical_workflow, outputs, limitations, installation

  9. PIUR Imaging resources

    PIUR Imaging - Accessed 2026-09-07

    Scope: product_family, manuals, training_resources, DICOM_resources

  10. PIUR IMAGING: CPT 76376 and 76377 in 3D Ultrasound: Workflow Guide

    PIUR IMAGING - Published 2026-10-15 - Accessed 2026-10-26

    Scope: reimbursement

Research history

  1. K250484 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K252237

EdgeFlow UW20

Edgecare, Inc.

Authorized purpose: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.

Modality
Ultrasound
Anatomy
Urinary bladder
Decision
2026-04-17
FDA-cleared K253535

Ligence Heart

Ligence Uab

Ligence Heart is a fully automated software platform that processes, analyses and makes measurements on acquired transthoracic cardiac ultrasound images, automatically producing a full report with measurements of several key cardiac structural and functional parameters. The data produced by this software is intended to be used to support qualified cardiologists or sonographers for clinical decision making. Ligence Heart is indicated for use in adult patients. Ligence Heart has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g., tumors, thrombi). Limitations: Poor image capture will lead to poor annotations and subsequent measurements. Multiple image quality algorithms are used to filter out images of poor quality. Our software complements good patient care and does not exempt the user from the responsibility to provide supervision, clinically review the patient, and make appropriate clinical decisions. If no gender is present, female referenced guideline values will be used for conclusions. If Body Surface Area (BSA) is not present, indexed values cannot be provided. During image acquisition, inappropriate use of the echo machine, use of non-cardiac ultrasound probes, or use of suboptimal settings (e.g., gain, contrast, depth) may lead to lower accuracy of the software. Ligence Heart has not been validated in patients with prosthetic or surgically altered cardiac valves, implantable intracardiac devices, or irregular (non-sinus) rhythm; these conditions may affect automated measurement accuracy.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2026-02-27

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history