Authorized purpose: Automatic standard-view classification, frame extraction, and acquisition-protocol assessment during second- or third-trimester fetal ultrasound.
Clinical role
Acquisition and interpretation support: classifies standard views, extracts representative frames, and assesses whether documented views satisfy a center-defined acquisition protocol.
Images and patients
Ultrasound · Fetal heart and abdomen standard views during fetal anatomic ultrasound
Key limitation
Keep in mind: Not intended for multiple pregnancies. The packet limits intended/validated use to transabdominal examinations at 18 weeks of gestation or later and to General Electric, Philips, Samsung, and Siemens ultrasound devices; standard-view classification is not a disease-detection endpoint.
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 classification, frame extraction, and acquisition-protocol assessment during second- or third-trimester fetal ultrasound.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Fetal heart and abdomen standard views during fetal anatomic ultrasound Input: Fetal 2D ultrasound images and video clips from transabdominal probes during second- or third-trimester examinations, at 18 weeks of gestation or later, for pregnant women aged 18 or older and single pregnancies.
Who uses it?Intended users: Qualified, trained healthcare professionals in a professional prenatal ultrasound environment, including sonographers, MFMs, OB/GYNs, and fetal surgeons
What does the software produce?Output: Automatic classification of fetal heart and abdomen standard views, extracted example frames from video clips, acquisition-protocol assessment, and annotated DICOM files displayed in a DICOM viewer with optional web-interface display; generated annotated DICOM files cannot be modified by the user.
What is its most important limitation?Key limitation: Not intended for multiple pregnancies. The packet limits intended/validated use to transabdominal examinations at 18 weeks of gestation or later and to General Electric, Philips, Samsung, and Siemens ultrasound devices; standard-view classification is not a disease-detection endpoint.
Clinical takeaway. Clinical role: Automatic standard-view classification, frame extraction, and acquisition-protocol assessment during second- or third-trimester fetal ultrasound.
Evidence takeaway. Evidence from the reviewed source record: FDA bench validation used 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 18 weeks of gestation or later, from eight centers. A sonographer and an MFM specialist independently established the standard-view reference. Mean standard-view recognition sensitivity was 0.939 (95% CI 0.917-0.960) and specificity was 0.984 (95% CI 0.973-0.996). Validation used GE, Philips, Samsung, and Siemens ultrasound devices and separate training and testing 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
Automatic standard-view classification, frame extraction, and acquisition-protocol assessment during second- or third-trimester fetal ultrasound.
Acquisition and interpretation support: classifies standard views, extracts representative frames, and assesses whether documented views satisfy a center-defined acquisition protocol.
Fetal 2D ultrasound images and video clips from transabdominal probes during second- or third-trimester examinations, at 18 weeks of gestation or later, for pregnant women aged 18 or older and single pregnancies.
Automatic classification of fetal heart and abdomen standard views, extracted example frames from video clips, acquisition-protocol assessment, and annotated DICOM files displayed in a DICOM viewer with optional web-interface display; generated annotated DICOM files cannot be modified by the user.
Qualified, trained healthcare professionals in a professional prenatal ultrasound environment, including sonographers, MFMs, OB/GYNs, and fetal surgeons
Not intended for multiple pregnancies. The packet limits intended/validated use to transabdominal examinations at 18 weeks of gestation or later and to General Electric, Philips, Samsung, and Siemens ultrasound devices; standard-view classification is not a disease-detection endpoint.
FDA bench validation used 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 18 weeks of gestation or later, from eight centers. A sonographer and an MFM specialist independently established the standard-view reference. Mean standard-view recognition sensitivity was 0.939 (95% CI 0.917-0.960) and specificity was 0.984 (95% CI 0.973-0.996). Validation used GE, Philips, Samsung, and Siemens ultrasound devices and separate training and testing examinations.
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 bench validation used 2,290 clinically acquired images and video frames from 579 fetal ultrasound examinations at 18 weeks of gestation or later, from eight centers. A sonographer and an MFM specialist independently established the standard-view reference. Mean standard-view recognition sensitivity was 0.939 (95% CI 0.917-0.960) and specificity was 0.984 (95% CI 0.973-0.996). Validation used GE, Philips, Samsung, and Siemens ultrasound devices and separate training and testing examinations.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
BrightHeart View Classifier regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K251456
Samplen=2290
Sites8
IndependenceIndependence not established
K251456
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 K251456. 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 2D ultrasound images and video clips from transabdominal probes during second- or third-trimester examinations, at 18 weeks of gestation or later, for pregnant women aged 18 or older and single pregnancies.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Cloud-based, stand-alone software that operates on DICOM files, displays annotated DICOM outputs in a DICOM viewer, and may also display them in a device web interface. Specific PACS/RIS interfaces and local compatibility 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 BrightHeart View Classifier v1.1 as a cloud-based software-only device whose annotated DICOM outputs are displayed in a DICOM viewer and may optionally be displayed on a web interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "BrightHeart View Classifier is a cloud-based software-only device which uses artificial intelligence (AI)" … "the outputs of the subject device are annotated DICOM files displayed in a DICOM viewer and may optionally be displayed on a web interface.". 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 classification of fetal heart and abdomen standard views, extracted example frames from video clips, acquisition-protocol assessment, and annotated DICOM files displayed in a DICOM viewer with optional web-interface display; generated annotated DICOM files cannot be modified by the user.
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 heart and abdomen standard views, extracted example frames from video clips, acquisition-protocol assessment, and annotated DICOM files displayed in a DICOM viewer with optional web-interface display; generated annotated DICOM files cannot be modified by the user.
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 BrightHeart View Classifier v1.1 as a cloud-based software-only device whose annotated DICOM outputs are displayed in a DICOM viewer and may optionally be displayed on a web interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "BrightHeart View Classifier is a cloud-based software-only device which uses artificial intelligence (AI)" … "the outputs of the subject device are annotated DICOM files displayed in a DICOM viewer and may optionally be displayed on a web interface.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Cloud-based, stand-alone software that operates on DICOM files, displays annotated DICOM outputs in a DICOM viewer, and may also display them in a device web interface. Specific PACS/RIS interfaces and local compatibility 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.
ACR AI Central provides an exact-submission model card for BrightHeart View Classifier; 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
26Fields 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 K251456 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: Alturion Series diagnostic ultrasound systems acquire and display ultrasound images and fluid-flow information for the labeled fetal, abdominal, cardiac, cephalic, obstetric, musculoskeletal, ophthalmic, urologic, vascular, small-organ, and lung examinations.
Modality
Ultrasound
Anatomy
Fetus; abdomen; pelvis; small organs; head; heart; peripheral vessels; musculoskeletal anatomy; ophthalmic; urologic organs; and lung
Authorized purpose: WatchMate Software v1.2.0 processes transesophageal echocardiography data to reconstruct the left atrial appendage and assist preprocedural planning and device sizing during left-atrial-appendage closure.
Authorized purpose: Guides medical professionals acquiring ten standard 2D transthoracic echocardiographic views in adults requiring a cardiac ultrasound examination; acquired images require qualified clinical interpretation.
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.