Authorized purpose: Concurrent aid during acquisition and interpretation of fetal ultrasound examinations across gestational ages 11-37 weeks to detect supported views and structures and verify view quality criteria and characteristics.
Clinical role
Real-time concurrent acquisition and interpretation aid for exam completeness and protocol checking; the healthcare professional can reassign or unassign views and override quality or characteristic outputs.
Images and patients
Ultrasound · Fetus/obstetric anatomy, including fetal brain, heart/thorax, abdomen, placenta, and genitalia
Key limitation
Keep in mind: The packet states that Sonio Detect was validated only with GE, Canon, Philips, and Samsung ultrasound devices and is intended only for those vendors. Outputs are concurrent reading aids that can be overridden by the user; the packet does not establish a diagnostic conclusion or a clinical-outcome claim. No clinical study was required for substantial equivalence.
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: Concurrent aid during acquisition and interpretation of fetal ultrasound examinations across gestational ages 11-37 weeks to detect supported views and structures and verify view quality criteria and characteristics.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Fetus/obstetric anatomy, including fetal brain, heart/thorax, abdomen, placenta, and genitalia Input: Fetal ultrasound images and clips from GE Medical, Samsung, Canon, or Philips ultrasound machines, covering trimester 1, 2, or 3 and gestational age 11-37 weeks; DICOM instances are received by edge software on a server connected to the ultrasound-machine network.
Who uses it?Intended users: Sonographers, OB/GYN maternal-fetal medicine specialists, and fetal surgeons as healthcare professionals
What does the software produce?Output: Automatic detection of 7 first-trimester or 18 second/third-trimester views, supported fetal anatomical structures, presence or absence quality criteria, placenta location (anterior/posterior), and fetal sex (male/female), with yellow highlighting for unverified items and user-editable assignments.
What is its most important limitation?Key limitation: The packet states that Sonio Detect was validated only with GE, Canon, Philips, and Samsung ultrasound devices and is intended only for those vendors. Outputs are concurrent reading aids that can be overridden by the user; the packet does not establish a diagnostic conclusion or a clinical-outcome claim. No clinical study was required for substantial equivalence.
Clinical takeaway. Clinical role: Concurrent aid during acquisition and interpretation of fetal ultrasound examinations across gestational ages 11-37 weeks to detect supported views and structures and verify view quality criteria and characteristics.
Evidence takeaway. Evidence from the reviewed source record: FDA K240406 reports standalone performance testing on 36,769 fetal ultrasound images using a global validation dataset independent of development and operating-point data. The table reports endpoint-specific sensitivity and specificity: view sensitivity was 0.914 for 7 first-trimester views and 0.937 for 18 second/third-trimester views; paired structure or characteristic results included brain 0.934/0.949, thorax and heart 0.861/0.938 for trimester 1 and 0.919/0.976 for trimesters 2/3, placenta structures 0.967/0.856, CRL/NT/profile 0.898/0.862 for trimester 1 and 0.893/0.956 for trimesters 2/3, anterior placenta location 0.959/0.966, posterior location 0.966/0.959, female sex 0.977/0.987, and male sex 0.987/0.977. The table also reports sensitivity-only values of 0.892 for 3D-image detection, 0.973 for Doppler-image detection, and 0.913 for view detection from image annotations.
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
Concurrent aid during acquisition and interpretation of fetal ultrasound examinations across gestational ages 11-37 weeks to detect supported views and structures and verify view quality criteria and characteristics.
Real-time concurrent acquisition and interpretation aid for exam completeness and protocol checking; the healthcare professional can reassign or unassign views and override quality or characteristic outputs.
Fetal ultrasound images and clips from GE Medical, Samsung, Canon, or Philips ultrasound machines, covering trimester 1, 2, or 3 and gestational age 11-37 weeks; DICOM instances are received by edge software on a server connected to the ultrasound-machine network.
Automatic detection of 7 first-trimester or 18 second/third-trimester views, supported fetal anatomical structures, presence or absence quality criteria, placenta location (anterior/posterior), and fetal sex (male/female), with yellow highlighting for unverified items and user-editable assignments.
The packet states that Sonio Detect was validated only with GE, Canon, Philips, and Samsung ultrasound devices and is intended only for those vendors. Outputs are concurrent reading aids that can be overridden by the user; the packet does not establish a diagnostic conclusion or a clinical-outcome claim. No clinical study was required for substantial equivalence.
FDA K240406 reports standalone performance testing on 36,769 fetal ultrasound images using a global validation dataset independent of development and operating-point data. The table reports endpoint-specific sensitivity and specificity: view sensitivity was 0.914 for 7 first-trimester views and 0.937 for 18 second/third-trimester views; paired structure or characteristic results included brain 0.934/0.949, thorax and heart 0.861/0.938 for trimester 1 and 0.919/0.976 for trimesters 2/3, placenta structures 0.967/0.856, CRL/NT/profile 0.898/0.862 for trimester 1 and 0.893/0.956 for trimesters 2/3, anterior placenta location 0.959/0.966, posterior location 0.966/0.959, female sex 0.977/0.987, and male sex 0.987/0.977. The table also reports sensitivity-only values of 0.892 for 3D-image detection, 0.973 for Doppler-image detection, and 0.913 for view detection from image annotations.
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 K240406 reports standalone performance testing on 36,769 fetal ultrasound images using a global validation dataset independent of development and operating-point data. The table reports endpoint-specific sensitivity and specificity: view sensitivity was 0.914 for 7 first-trimester views and 0.937 for 18 second/third-trimester views; paired structure or characteristic results included brain 0.934/0.949, thorax and heart 0.861/0.938 for trimester 1 and 0.919/0.976 for trimesters 2/3, placenta structures 0.967/0.856, CRL/NT/profile 0.898/0.862 for trimester 1 and 0.893/0.956 for trimesters 2/3, anterior placenta location 0.959/0.966, posterior location 0.966/0.959, female sex 0.977/0.987, and male sex 0.987/0.977. The table also reports sensitivity-only values of 0.892 for 3D-image detection, 0.973 for Doppler-image detection, and 0.913 for view detection from image annotations.
Endpoint-specific, not device-level: fetal brain 93.4%; fetal thorax/heart 86.1% at T1 and 91.9% at T2/T3; additional view and characteristic rows are reported in the FDA table.
FDA source
Exact FDA submission
Checked 2026-09-08
FDA K240406 reports separate trimester-, view-, structure-, and characteristic-specific endpoints; the prior 95%/95% pair was not an observed overall result.
Endpoint-specific, not device-level: fetal brain 94.9%; fetal thorax/heart 93.8% at T1 and 97.6% at T2/T3; specificity is not reported for some image-type endpoints.
FDA source
Exact FDA submission
Checked 2026-09-08
FDA K240406 reports separate trimester-, view-, structure-, and characteristic-specific endpoints; the prior 95%/95% pair was not an observed overall result.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Sonio Detect regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K240406
Samplen=36769
IndependenceIndependence not established
K240406
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 K240406. 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: Fetal ultrasound images and clips from GE Medical, Samsung, Canon, or Philips ultrasound machines, covering trimester 1, 2, or 3 and gestational age 11-37 weeks; DICOM instances are received by edge software on a server connected to the ultrasound-machine network.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The packet describes edge software on a local server receiving DICOM instances from the ultrasound machine, uploading them to Sonio Cloud, and SaaS access through an internet browser, with Chrome recommended. It does not establish a specific PACS, RIS, EHR, interface version, or pure cloud-only deployment.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes Sonio Detect as a Software as a Service solution accessible from an internet browser, with Edge Software installed on the HCP server and network to receive DICOM instances from the ultrasound machine and upload them to Sonio's Cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Sonio Detect is a Software as a Service SaaS solution that aims at helping sonographers," … "SaaS accessibility from any internet browser (recommended browser: Google Chrome).". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Automatic detection of 7 first-trimester or 18 second/third-trimester views, supported fetal anatomical structures, presence or absence quality criteria, placenta location (anterior/posterior), and fetal sex (male/female), with yellow highlighting for unverified items and user-editable assignments.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Automatic detection of 7 first-trimester or 18 second/third-trimester views, supported fetal anatomical structures, presence or absence quality criteria, placenta location (anterior/posterior), and fetal sex (male/female), with yellow highlighting for unverified items and user-editable assignments.
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 exact FDA package describes Sonio Detect as a Software as a Service solution accessible from an internet browser, with Edge Software installed on the HCP server and network to receive DICOM instances from the ultrasound machine and upload them to Sonio's Cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Sonio Detect is a Software as a Service SaaS solution that aims at helping sonographers," … "SaaS accessibility from any internet browser (recommended browser: Google Chrome).". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The packet describes edge software on a local server receiving DICOM instances from the ultrasound machine, uploading them to Sonio Cloud, and SaaS access through an internet browser, with Chrome recommended. It does not establish a specific PACS, RIS, EHR, interface version, or pure cloud-only deployment.
Sonio's security page states HIPAA and GDPR compliance, HDS-certified cloud providers, SOC 2 Type 2 compliance, encryption at rest and in transit, a web application firewall with intrusion detection, and isolated regional deployments. Vendor-wide.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; exact-release scope is not established.
ACR AI Central provides an exact-submission model card for Sonio Detect; FDA labeling remains controlling for clinical use, limitations, and performance.
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
24Fields reviewed
10Source 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, acr ai central product, vendor documentation, 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 K240406 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.
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
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: FETOLY analyzes fetal ultrasound images and sequences to detect labeled fetal brain and heart views, assess image completeness or quality, and provide fetal biometric measurements during the second and third trimesters.
Authorized purpose: Automatic standard-view detection and frame extraction to support acquisition and interpretation of second- or third-trimester fetal heart ultrasound.
Authorized purpose: Adjunctive detection of suspicious fetal cardiac findings during second-trimester ultrasound to aid concurrent OB-GYN or maternal-fetal-medicine interpretation.
Modality
Ultrasound
Anatomy
Fetal heart, including four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract views and the specified suspicious cardiac findings
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.