Authorized purpose: Automatic standard-view detection and frame extraction to support acquisition and interpretation of second- or third-trimester fetal heart ultrasound.
Clinical role
Adjunct to fetal ultrasound acquisition and interpretation; it classifies standard views and is not a replacement for the interpreting clinician.
Images and patients
Ultrasound · Obstetric/Fetal
Key limitation
Keep in mind: The exact FDA validation used GE, Philips, Samsung and Siemens ultrasound devices and pregnancies at 18 weeks or later recorded with transabdominal probes; performance was lower or less certain in some small demographic subgroups.
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: Automatic standard-view detection and frame extraction to support acquisition and interpretation of second- or third-trimester fetal heart ultrasound.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Obstetric/Fetal Input: Fetal 2D ultrasound images and video clips from transabdominal examinations at 18 weeks of gestation or later.
Who uses it?Intended users: Qualified and trained sonographers, maternal-fetal medicine specialists, obstetricians, gynecologists and fetal surgeons.
What does the software produce?Output: Automatic classification of fetal cardiac standard views and automatically extracted example frames for review and documentation.
What is its most important limitation?Key limitation: The exact FDA validation used GE, Philips, Samsung and Siemens ultrasound devices and pregnancies at 18 weeks or later recorded with transabdominal probes; performance was lower or less certain in some small demographic subgroups.
Clinical takeaway. Clinical role: Automatic standard-view detection and frame extraction to support acquisition and interpretation of second- or third-trimester fetal heart ultrasound.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA performance set contained 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 8 centers; mean standard-view recognition sensitivity was 0.939 and specificity was 0.984.
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
Automatic standard-view detection and frame extraction to support acquisition and interpretation of second- or third-trimester fetal heart ultrasound.
The exact FDA validation used GE, Philips, Samsung and Siemens ultrasound devices and pregnancies at 18 weeks or later recorded with transabdominal probes; performance was lower or less certain in some small demographic subgroups.
The exact FDA performance set contained 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 8 centers; mean standard-view recognition sensitivity was 0.939 and specificity was 0.984.
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 performance set contained 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 8 centers; mean standard-view recognition sensitivity was 0.939 and specificity was 0.984.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
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 2D ultrasound images and video clips from transabdominal examinations at 18 weeks of gestation or later.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The current BrightHeart family platform describes a standalone fetal-heart workflow with support for major ultrasound manufacturers, a cart-side tablet option, and results linked into reporting and a web view; exact K243684 interfaces are not established.
Scope: Product family.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA materials describe a cloud-based, software-only workflow with qualified users reviewing fetal ultrasound images or clips.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Automatic classification of fetal cardiac standard views and automatically extracted example frames for review and documentation.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Automatic classification of fetal cardiac standard views and automatically extracted example frames for review and documentation.
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 current BrightHeart family platform describes a standalone fetal-heart workflow with support for major ultrasound manufacturers, a cart-side tablet option, and results linked into reporting and a web view; exact K243684 interfaces 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.
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.
The exact validation covered GE, Philips, Samsung and Siemens devices; current family material separately describes integration with major manufacturers.
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-07Last searched
25Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The stored candidate metadata contained empty PubMed and clinical-trial ID arrays; metadata was screened, not full-text or registry-reviewed. The stored recall candidate record was empty and no event 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 product page, vendor manual, peer reviewed publication, clinical trial registry, recall database, 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-07 - Exact FDA submission
No numeric price was published in the reviewed sources.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "BrightHeart reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. No result was a vendor or payer page naming this product with coding or payment; any results were general billing guidance. This records what was found, not that none exists.
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-10-27 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
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.
Authorized purpose: Concurrent physician reading aid for specified abnormal fetal ultrasound findings; patient management must not rely solely on the analysis.
Authorized purpose: Butterfly Gestational Age Tool estimates gestational age for a singleton intrauterine pregnancy presumed to be 16 to 37 weeks within the labeled Butterfly ultrasound workflow; qualified professionals must review the output.
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.