FDA-cleared profile

Fetal EchoScan (v1.1)

BrightHeart · Ultrasound · FDA-cleared (510(k))

Authorized purpose: Adjunctive detection of suspicious fetal cardiac findings during second-trimester ultrasound to aid concurrent OB-GYN or maternal-fetal-medicine interpretation.

Clinical role
Concurrent CADx reading aid for frame- and clip-level finding classification, with physician review and standard-of-care follow-up; not a stand-alone diagnostic decision maker
Images and patients
Ultrasound · Fetal heart, including four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract views and the specified suspicious cardiac findings
Key limitation
Keep in mind: Not intended for multiple pregnancies, heterotaxy, or postnatal ultrasound examinations. It is an adjunct and does not replace physician review or other diagnostic testing. The packet describes validation on Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices and on the stated second-trimester population; inconclusive outputs require interpretation.

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: Adjunctive detection of suspicious fetal cardiac findings during second-trimester ultrasound to aid concurrent OB-GYN or maternal-fetal-medicine interpretation.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Fetal heart, including four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract views and the specified suspicious cardiac findings Input: Fetal cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views from second-trimester examinations at 18-24 weeks of gestation.
  • Who uses it?Intended users: Interpreting physicians, specifically OB-GYNs and maternal-fetal medicine physicians
  • What does the software produce?Output: For each frame, present, absent, or inconclusive classification for the eight suspicious findings; a record summary for each video clip; an exam summary for the overall study; and annotated DICOM outputs displayed in the user PACS viewer, with an optional web-interface display.
  • What is its most important limitation?Key limitation: Not intended for multiple pregnancies, heterotaxy, or postnatal ultrasound examinations. It is an adjunct and does not replace physician review or other diagnostic testing. The packet describes validation on Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices and on the stated second-trimester population; inconclusive outputs require interpretation.

Clinical takeaway. Clinical role: Adjunctive detection of suspicious fetal cardiac findings during second-trimester ultrasound to aid concurrent OB-GYN or maternal-fetal-medicine interpretation.

Evidence takeaway. Evidence from the reviewed source record: FDA packet: standalone testing used 877 clinically acquired fetal ultrasound examinations from 11 centers, with three pediatric cardiologists establishing majority-vote reference standards; 98.8% of exams had a conclusive output for any finding. A fully crossed reader study used 14 readers and 200 exams in aided and unaided conditions, with training and validation examinations distinct from standalone test examinations.

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
Adjunctive detection of suspicious fetal cardiac findings during second-trimester ultrasound to aid concurrent OB-GYN or maternal-fetal-medicine interpretation.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Concurrent CADx reading aid for frame- and clip-level finding classification, with physician review and standard-of-care follow-up; not a stand-alone diagnostic decision maker
  • Exact FDA submission
  • Checked 2026-09-08
Required input
Fetal cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views from second-trimester examinations at 18-24 weeks of gestation.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
For each frame, present, absent, or inconclusive classification for the eight suspicious findings; a record summary for each video clip; an exam summary for the overall study; and annotated DICOM outputs displayed in the user PACS viewer, with an optional web-interface display.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Prenatal/obstetric ultrasound care during second-trimester anatomic examinations at 18-24 weeks of gestation for pregnant women aged 18 or older
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Interpreting physicians, specifically OB-GYNs and maternal-fetal medicine physicians
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
Not intended for multiple pregnancies, heterotaxy, or postnatal ultrasound examinations. It is an adjunct and does not replace physician review or other diagnostic testing. The packet describes validation on Fujifilm, GE, Philips, Samsung, and Toshiba ultrasound devices and on the stated second-trimester population; inconclusive outputs require interpretation.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
FDA packet: standalone testing used 877 clinically acquired fetal ultrasound examinations from 11 centers, with three pediatric cardiologists establishing majority-vote reference standards; 98.8% of exams had a conclusive output for any finding. A fully crossed reader study used 14 readers and 200 exams in aided and unaided conditions, with training and validation examinations distinct from standalone test examinations.
  • Exact FDA submission
  • Checked 2026-09-08

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
FDA packet: standalone testing used 877 clinically acquired fetal ultrasound examinations from 11 centers, with three pediatric cardiologists establishing majority-vote reference standards; 98.8% of exams had a conclusive output for any finding. A fully crossed reader study used 14 readers and 200 exams in aided and unaided conditions, with training and validation examinations distinct from standalone test examinations.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
Any suspicious finding: 97.7% worst-case and 98.7% best-case, depending on how inconclusive outputs are counted.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

Reader-study AUC, sensitivity, and specificity changes are separate percentage-point effects and are not standalone device values.

Reported specificity
Any suspicious finding: 97.7% best-case and 96.3% worst-case, depending on how inconclusive outputs are counted.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

Reader-study AUC, sensitivity, and specificity changes are separate percentage-point effects and are not standalone device values.

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

Fetal EchoScan v1.1 regulatory performance study summary

  • DesignStand-alone performance and reader study (ACR AI Central category)
  • PopulationAdult
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K251071
  • Samplen=877
  • Sites11
  • IndependenceIndependence not established

K251071

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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
The exact-identifier FDA recall query returned no native recall record for K251071. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

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: Fetal cardiac ultrasound video clips containing interpretable four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract standard views from second-trimester examinations at 18-24 weeks of gestation.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K251071: Fetal EchoScan (v1.1)

  2. Routing

    Source context, not route validation: Cloud-based software-only device with annotated DICOM output displayed in a user PACS viewer and optionally in a web interface; the FDA packet does not establish specific PACS/RIS/EHR interface versions or a local deployment topology.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K251071: Fetal EchoScan (v1.1)

  3. AI processing

    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 for review by trained and qualified physicians. 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 for further review by trained and qualified physicians.". 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.

    Field checked 2026-11-14 · FDA K251071: Fetal EchoScan (v1.1)

  4. Returned objects

    Source context, not route validation: For each frame, present, absent, or inconclusive classification for the eight suspicious findings; a record summary for each video clip; an exam summary for the overall study; and annotated DICOM outputs displayed in the user PACS viewer, with an optional web-interface display.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K251071: Fetal EchoScan (v1.1)

  5. Viewer/worklist/report

    Unresolved route: For each frame, present, absent, or inconclusive classification for the eight suspicious findings; a record summary for each video clip; an exam summary for the overall study; and annotated DICOM outputs displayed in the user PACS viewer, with an optional web-interface display.

    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-08 · FDA K251071: Fetal EchoScan (v1.1)

  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
The exact FDA package describes Fetal EchoScan as a cloud-based software-only device that uses neural networks to detect suspicious cardiac radiographic findings for review by trained and qualified physicians. 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 for further review by trained and qualified physicians.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
Cloud-based software-only device with annotated DICOM output displayed in a user PACS viewer and optionally in a web interface; the FDA packet does not establish specific PACS/RIS/EHR interface versions or a local deployment topology.
  • Exact FDA submission
  • Checked 2026-09-08
Security
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.

Monitoring
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 exact-submission catalog context

ACR AI Central provides an exact-submission model card for Fetal EchoScan (v1.1); FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K251071
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Fetal heart, including four-chamber, left-ventricular-outflow-tract, and right-ventricular-outflow-tract views and the specified suspicious cardiac findings
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-05-02
  • 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.

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 K251071 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.

8 sources - 3 history items

Source ledger

  1. FDA K251071: Fetal EchoScan (v1.1)

    U.S. Food and Drug Administration - Published 2025-05-02 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Fetal EchoScan v1.1 model card (K251071)

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

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, 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. openFDA exact recall query for K251071

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

    Scope: postmarketSafety

  8. BrightHeart: Security (Coordinated Vulnerability Disclosure)

    BrightHeart - Accessed 2026-10-27

    Scope: security

Research history

  1. K251071 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K251368

FETOLY

Diagnoly

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.

Modality
Ultrasound
Anatomy
Fetal heart and fetal brain
Decision
2025-09-12
FDA-cleared K242342

Fetal EchoScan

BrightHeart

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.
Decision
2024-11-14

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