Authorized purpose: AmCAD-UV classifies ultrasonic color-intensity data and lets users view primary pulsatile, secondary pulsatile, and unidentified signals in flow-Doppler ultrasound images. It is a general-purpose medical-image-processing tool for vascular pulsatility analysis and must not be used alone for primary diagnostic interpretation.
Clinical role
Classification, visualization, quantification, and trend review of color or power Doppler flow signals.
Keep in mind: The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
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: AmCAD-UV classifies ultrasonic color-intensity data and lets users view primary pulsatile, secondary pulsatile, and unidentified signals in flow-Doppler ultrasound images. It is a general-purpose medical-image-processing tool for vascular pulsatility analysis and must not be used alone for primary diagnostic interpretation.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Vascular structures; pulsatile flow signals Input: Color and power Doppler ultrasound images acquired from FDA-cleared ultrasound systems or another DICOM source.
Who uses it?Intended users: Qualified physicians, sonographers, and trained ultrasound professionals.
What does the software produce?Output: Color-coded primary, secondary, and unidentified pulsatile signals, ROI statistics, trend charts, and exported text or image files.
What is its most important limitation?Key limitation: The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
Clinical takeaway. Clinical role: AmCAD-UV classifies ultrasonic color-intensity data and lets users view primary pulsatile, secondary pulsatile, and unidentified signals in flow-Doppler ultrasound images. It is a general-purpose medical-image-processing tool for vascular pulsatility analysis and must not be used alone for primary diagnostic interpretation.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification testing (software unit, integration and system tests) to ensure the device meets its functional specifications, and performance validation testing, described as a human validation study, which it states demonstrated that the device can be used to visualize and quantify primary pulsatile, secondary pulsatile, and unidentified signals of flow Doppler ultrasound images. 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
AmCAD-UV classifies ultrasonic color-intensity data and lets users view primary pulsatile, secondary pulsatile, and unidentified signals in flow-Doppler ultrasound images. It is a general-purpose medical-image-processing tool for vascular pulsatility analysis and must not be used alone for primary diagnostic interpretation.
The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
The exact FDA document reports software verification testing (software unit, integration and system tests) to ensure the device meets its functional specifications, and performance validation testing, described as a human validation study, which it states demonstrated that the device can be used to visualize and quantify primary pulsatile, secondary pulsatile, and unidentified signals of flow Doppler ultrasound images. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software verification testing, including software unit test, software integration test, and software system test, was performed to ensure that AmCAD-UV meets all functional and specifications for its indications for use." … "The results of performance validation testing (i.e. human validation study) demonstrated that AmCAD-UV can be used to visualize and quantify the primary pulsatile, secondary pulsatile, and unidentified signals of flow Doppler ultrasound images.". 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 testing (software unit, integration and system tests) to ensure the device meets its functional specifications, and performance validation testing, described as a human validation study, which it states demonstrated that the device can be used to visualize and quantify primary pulsatile, secondary pulsatile, and unidentified signals of flow Doppler ultrasound images. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software verification testing, including software unit test, software integration test, and software system test, was performed to ensure that AmCAD-UV meets all functional and specifications for its indications for use." … "The results of performance validation testing (i.e. human validation study) demonstrated that AmCAD-UV can be used to visualize and quantify the primary pulsatile, secondary pulsatile, and unidentified signals of flow Doppler ultrasound images.". 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.
K170069 FDA evidence package for AmCAD-UV
DesignFDA 510(k) software verification, performance validation, and human-validation evidence for visualizing and quantifying classified Doppler pulsatility signals.
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 K170069 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.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage 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: Color and power Doppler ultrasound images acquired from FDA-cleared ultrasound systems or another DICOM source.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes color and power Doppler images from FDA-cleared ultrasound systems or another DICOM source, ROI selection, trend charts, and export of quantified values and color-coded images in text, BMP, or JPEG formats.
Scope: Exact FDA submission. This is the 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 FDA package describes operation on a standard PC, workstation, or on-board FDA-cleared ultrasound system; current hosting, service, security, availability, and site configuration remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Color-coded primary, secondary, and unidentified pulsatile signals, ROI statistics, trend charts, and exported text or image files.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Color-coded primary, secondary, and unidentified pulsatile signals, ROI statistics, trend charts, and exported text or image files.
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 FDA package describes operation on a standard PC, workstation, or on-board FDA-cleared ultrasound system; current hosting, service, security, availability, and site configuration remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA package describes color and power Doppler images from FDA-cleared ultrasound systems or another DICOM source, ROI selection, trend charts, and export of quantified values and color-coded images in text, BMP, or JPEG formats.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only qualified physicians, sonographers, and trained ultrasound 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 K170069 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: The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared or authorized scope; it is not a claim that the FDA package provides a live monitoring service.
The FDA package describes operation on a standard PC, workstation, or on-board FDA-cleared ultrasound system; current hosting, service, security, availability, and site configuration remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes color and power Doppler images from FDA-cleared ultrasound systems or another DICOM source, ROI selection, trend charts, and export of quantified values and color-coded images in text, BMP, or JPEG formats.
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. The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
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 K170069 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: The tool is general-purpose and must not be used alone for primary diagnostic interpretation; quantified values represent information from the source Doppler images.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. flow-Doppler ultrasound image-processing software 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-04Last searched
26Fields reviewed
11Source classes checked
1Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
One PubMed record was screened. It uses a proprietary AmCAD-UV program but predates K170069 and does not identify the tested software as AmCAD-UV model 1.0 from that submission; the record is quarantined. The current discovery snapshot contains 1 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, fda decision material, fda pma record, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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 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
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 publicly available - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: Assist qualified MSK-ultrasound professionals by highlighting supported joint anatomy and detection completeness on compatible adult ultrasound images; it is not a diagnostic device.
Modality
Ultrasound
Anatomy
Musculoskeletal joints: shoulder, elbow, wrist/hand, knee, and ankle/foot.
Authorized purpose: Sonio Detect v3 analyzes fetal ultrasound images and clips to detect views and anatomical structures and to check labeled image-quality characteristics during acquisition or interpretation.
Authorized purpose: BioticsAI assists healthcare professionals during and after fetal ultrasound acquisition and interpretation by detecting views and anatomical structures and facilitating quality-criteria verification on DICOM images and frames; it is a concurrent reading aid for the labeled GE ultrasound and prenatal population.
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.