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.
Clinical role
Anatomy visualization and segmentation assistance within the ultrasound viewing workflow; not diagnostic and not acquisition guidance.
Images and patients
Ultrasound · Musculoskeletal joints: shoulder, elbow, wrist/hand, knee, and ankle/foot.
Key limitation
Keep in mind: Adults 18+ only; not intended for diagnosis or to replace clinical decision-making; compatible ultrasound systems and listed joint regions are required; it does not guide image acquisition.
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: Assist qualified MSK-ultrasound professionals by highlighting supported joint anatomy and detection completeness on compatible adult ultrasound images; it is not a diagnostic device.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Musculoskeletal joints: shoulder, elbow, wrist/hand, knee, and ankle/foot. Input: B-mode MSK ultrasound image stream from compatible GE HealthCare Venue Go and Venue Sprint systems; adult patients 18+; five supported joint regions.
Who uses it?Intended users: Healthcare professionals trained and qualified in musculoskeletal ultrasound.
What does the software produce?Output: Anatomical name labels, color overlays/highlighting, and a detection indicator reflecting completeness of supported structures in the current image.
What is its most important limitation?Key limitation: Adults 18+ only; not intended for diagnosis or to replace clinical decision-making; compatible ultrasound systems and listed joint regions are required; it does not guide image acquisition.
Clinical takeaway. Clinical role: Assist qualified MSK-ultrasound professionals by highlighting supported joint anatomy and detection completeness on compatible adult ultrasound images; it is not a diagnostic device.
Evidence takeaway. Evidence from the reviewed source record: FDA K260234 packet reports AI/ML verification on 17,746 images from 40 subjects and clinical validation on 15,600 images from 3,017 scans of 79 subjects at three US clinical sites. Endpoints were joint-view detection, anatomical-structure detection, segmentation/highlighting, and detection indicator. Reported ranges include joint-view PPA 0.95-1.00/NPA 0.98-1.00, structure PPA 0.93-0.95/NPA 0.98-0.99, indicator PPA 0.90-1.00/NPA 0.97-1.00, and mean Dice 0.80-0.84 with no individual structure below 0.70.
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
Assist qualified MSK-ultrasound professionals by highlighting supported joint anatomy and detection completeness on compatible adult ultrasound images; it is not a diagnostic device.
Adults 18+ only; not intended for diagnosis or to replace clinical decision-making; compatible ultrasound systems and listed joint regions are required; it does not guide image acquisition.
FDA K260234 packet reports AI/ML verification on 17,746 images from 40 subjects and clinical validation on 15,600 images from 3,017 scans of 79 subjects at three US clinical sites. Endpoints were joint-view detection, anatomical-structure detection, segmentation/highlighting, and detection indicator. Reported ranges include joint-view PPA 0.95-1.00/NPA 0.98-1.00, structure PPA 0.93-0.95/NPA 0.98-0.99, indicator PPA 0.90-1.00/NPA 0.97-1.00, and mean Dice 0.80-0.84 with no individual structure below 0.70.
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
FDA K260234 packet reports AI/ML verification on 17,746 images from 40 subjects and clinical validation on 15,600 images from 3,017 scans of 79 subjects at three US clinical sites. Endpoints were joint-view detection, anatomical-structure detection, segmentation/highlighting, and detection indicator. Reported ranges include joint-view PPA 0.95-1.00/NPA 0.98-1.00, structure PPA 0.93-0.95/NPA 0.98-0.99, indicator PPA 0.90-1.00/NPA 0.97-1.00, and mean Dice 0.80-0.84 with no individual structure below 0.70.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
MSK Go regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K260234
Samplen=79
Sites3
IndependenceIndependence not established
K260234
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K260234. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: B-mode MSK ultrasound image stream from compatible GE HealthCare Venue Go and Venue Sprint systems; adult patients 18+; five supported joint regions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Runs within compatible diagnostic ultrasound systems, receives the host-system image stream, and displays feedback in the ultrasound system user interface; no standalone PACS routing is established.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-08 ·
Returned objects
Source context, not route validation: Anatomical name labels, color overlays/highlighting, and a detection indicator reflecting completeness of supported structures in the current image.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Anatomical name labels, color overlays/highlighting, and a detection indicator reflecting completeness of supported structures in the current image.
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.
Runs within compatible diagnostic ultrasound systems, receives the host-system image stream, and displays feedback in the ultrasound system user interface; no standalone PACS routing is established.
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
21Fields reviewed
9Source classes checked
0Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 0 PubMed and 1 ClinicalTrials.gov candidate record. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 0 PubMed and 1 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, acr ai central product, fda decision summary, 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 verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K260234 configuration was established in this review.
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-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Deployment: Not verified - checked 2026-09-08 - Exact FDA submission
The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
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-08 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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.