Authorized purpose: Concurrent CADx aid for suspicious fetal cardiac morphological findings during second-trimester fetal heart ultrasound.
Clinical role
Concurrent reading aid and adjunct to physician interpretation; it does not replace the physician or other standard-of-care testing.
Images and patients
Ultrasound · Fetal Heart / Obstetric
Key limitation
Keep in mind: Not for multiple pregnancies, fetal heterotaxy, or postnatal ultrasound. Inconclusive outputs require scenario-specific handling in performance analysis. The packet states validation only with Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices.
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 CADx aid for suspicious fetal cardiac morphological findings during second-trimester fetal heart ultrasound.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Fetal Heart / Obstetric Input: Fetal cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views.
Who uses it?Intended users: Interpreting physicians.
What does the software produce?Output: For each frame, present, absent, or inconclusive status for eight suspicious fetal cardiac findings, plus an overall exam summary; annotated DICOMs are displayed in the user PACS viewer and optionally in a validated third-party interface.
What is its most important limitation?Key limitation: Not for multiple pregnancies, fetal heterotaxy, or postnatal ultrasound. Inconclusive outputs require scenario-specific handling in performance analysis. The packet states validation only with Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices.
Clinical takeaway. Clinical role: Concurrent CADx aid for suspicious fetal cardiac morphological findings during second-trimester fetal heart ultrasound.
Evidence takeaway. Evidence from the reviewed source record: FDA standalone testing used 877 second-trimester fetal ultrasound exams from 11 centers, with three pediatric cardiologists providing majority-vote truthing and testing data separate from training. For any suspicious finding, when inconclusive exams were counted negative, sensitivity was 0.984 (CI .963-.993) and specificity 0.970 (.952-.981); when counted positive, sensitivity was 0.990 (.972-.997) and specificity 0.958 (.938-.971). The packet also summarizes a fully crossed reader study of 14 readers and 200 exams: aided AUC 0.974 versus unaided 0.825, aided mean sensitivity 0.935 versus 0.782, and aided mean specificity 0.970 versus 0.759.
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 CADx aid for suspicious fetal cardiac morphological findings during second-trimester fetal heart ultrasound.
Fetal cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views.
For each frame, present, absent, or inconclusive status for eight suspicious fetal cardiac findings, plus an overall exam summary; annotated DICOMs are displayed in the user PACS viewer and optionally in a validated third-party interface.
Not for multiple pregnancies, fetal heterotaxy, or postnatal ultrasound. Inconclusive outputs require scenario-specific handling in performance analysis. The packet states validation only with Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices.
FDA standalone testing used 877 second-trimester fetal ultrasound exams from 11 centers, with three pediatric cardiologists providing majority-vote truthing and testing data separate from training. For any suspicious finding, when inconclusive exams were counted negative, sensitivity was 0.984 (CI .963-.993) and specificity 0.970 (.952-.981); when counted positive, sensitivity was 0.990 (.972-.997) and specificity 0.958 (.938-.971). The packet also summarizes a fully crossed reader study of 14 readers and 200 exams: aided AUC 0.974 versus unaided 0.825, aided mean sensitivity 0.935 versus 0.782, and aided mean specificity 0.970 versus 0.759.
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 standalone testing used 877 second-trimester fetal ultrasound exams from 11 centers, with three pediatric cardiologists providing majority-vote truthing and testing data separate from training. For any suspicious finding, when inconclusive exams were counted negative, sensitivity was 0.984 (CI .963-.993) and specificity 0.970 (.952-.981); when counted positive, sensitivity was 0.990 (.972-.997) and specificity 0.958 (.938-.971). The packet also summarizes a fully crossed reader study of 14 readers and 200 exams: aided AUC 0.974 versus unaided 0.825, aided mean sensitivity 0.935 versus 0.782, and aided mean specificity 0.970 versus 0.759.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Fetal EchoScan (v1.2) regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationAdult
Scopeexact submission
Tested version1.2
Samplen=877
Sites11
IndependenceIndependence not established
K252294
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 K252294. 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 cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Cloud-based software outputs annotated DICOMs to the user PACS viewer and optionally a validated third-party user interface; exact products, versions, routing, and current commercial configuration are not established.
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 Fetal EchoScan as a cloud-based software-only device that uses neural networks to detect suspicious cardiac radiographic findings. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Fetal EchoScan is a cloud-based software-only device which uses neural networks to detect suspicious cardiac radiographic findings". 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: For each frame, present, absent, or inconclusive status for eight suspicious fetal cardiac findings, plus an overall exam summary; annotated DICOMs are displayed in the user PACS viewer and optionally in a validated third-party interface.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: For each frame, present, absent, or inconclusive status for eight suspicious fetal cardiac findings, plus an overall exam summary; annotated DICOMs are displayed in the user PACS viewer and optionally in a validated third-party interface.
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 Fetal EchoScan as a cloud-based software-only device that uses neural networks to detect suspicious cardiac radiographic findings. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Fetal EchoScan is a cloud-based software-only device which uses neural networks to detect suspicious cardiac radiographic findings". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Cloud-based software outputs annotated DICOMs to the user PACS viewer and optionally a validated third-party user interface; exact products, versions, routing, and current commercial configuration are not established.
BrightHeart's security page describes a coordinated vulnerability disclosure program: a cybersecurity team monitoring for vulnerabilities, vulnerability report submission to support@brightheart.ai in a defined format, confirmation of receipt within ten business days, investigation and risk analysis, and a findings summary returned to the reporter.
Vendor-wide
Checked 2026-10-27
Vendor statement. The page is a coordinated vulnerability disclosure program description (last updated 2025-06-19); no certification or audit report was read, and exact-release scope is not established. Applicant name variant 'Brightheart' is bridged to BrightHeart via the identical Fetal EchoScan product name on the vendor's cleared-product entries and site.
BrightHeart's security page (last updated 2025-06-19) states a cybersecurity team monitoring for vulnerabilities and a coordinated vulnerability disclosure program with receipt confirmation within ten business days, investigation and risk analysis, and a findings summary returned to the reporter.
Vendor-wide
Checked 2026-10-27
Vendor statement, not an attestation. The page names BrightHeart generally and does not scope these commitments to any specific product release; exact-release scope is not established.
ACR AI Central provides an exact-submission model card for Fetal EchoScan (v1.2); 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
25Fields reviewed
9Source 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, 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 K252294 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.
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
Authorized purpose: Adjunctive CADx aid for interpreting OB-GYN/MFM physicians to identify suspicious fetal-cardiac findings in second-trimester anatomic ultrasound that may suggest congenital heart defects and inform the need for additional exams.
Modality
Ultrasound
Anatomy
Fetal heart, including the cardiac crux, outflow tracts, cardiac axis, ventricles, and valve annular relationships.
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.