Authorized purpose: Concurrent AI reading aid for routine fetal heart ultrasound examinations in second- and third-trimester pregnancies from 17 to 40 weeks, detecting the five recommended fetal heart views and 52 within-view quality criteria.
Clinical role
Concurrent real-time acquisition and reading aid; displays examination completeness and an illustrative image subset while the healthcare professional acquires and interprets images, with clinician review, editing, or override.
Images and patients
Ultrasound · Obstetric fetal heart
Key limitation
Keep in mind: The device does not select the best or diagnostically highest-quality image; its illustration represents quantitative completeness, not diagnostic quality. Clinicians must verify the views and criteria. The FDA packet marks clinical performance data as not applicable and does not establish diagnostic use.
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 AI reading aid for routine fetal heart ultrasound examinations in second- and third-trimester pregnancies from 17 to 40 weeks, detecting the five recommended fetal heart views and 52 within-view quality criteria.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Obstetric fetal heart Input: Real-time fetal ultrasound images and image sequences or clips from a connected ultrasound machine for second- and third-trimester examinations; the packet names GE Medical, Samsung, Canon, and Philips ultrasound compatibility in its comparison and testing materials.
Who uses it?Intended users: Sonographers, obstetricians, radiologists, maternal-fetal medicine specialists, and pediatric cardiologists who are qualified healthcare professionals specialized in prenatal ultrasound imaging.
What does the software produce?Output: A real-time completeness overview identifying the abdomen, four-chamber, LVOT, RVOT, and three-vessel views and 52 quality criteria as verified or not verified, plus an illustrative image subset and optional quality-criterion localization boxes.
What is its most important limitation?Key limitation: The device does not select the best or diagnostically highest-quality image; its illustration represents quantitative completeness, not diagnostic quality. Clinicians must verify the views and criteria. The FDA packet marks clinical performance data as not applicable and does not establish diagnostic use.
Clinical takeaway. Clinical role: Concurrent AI reading aid for routine fetal heart ultrasound examinations in second- and third-trimester pregnancies from 17 to 40 weeks, detecting the five recommended fetal heart views and 52 within-view quality criteria.
Evidence takeaway. Evidence from the reviewed source record: FDA standalone performance testing used 2,288 fetal ultrasound images from 480 patient cases across 7 clinical sites in the United States and France, with test data distinct from model-development data. Acceptance criteria were sensitivity and specificity at least 85% for fetal heart views, sensitivity and specificity at least 90% for quality criteria within views, and mean bounding-box IoU at least 50% for quality-criteria localization. The packet describes paired annotators with adjudication as the reference process; clinical performance data are marked not applicable.
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 AI reading aid for routine fetal heart ultrasound examinations in second- and third-trimester pregnancies from 17 to 40 weeks, detecting the five recommended fetal heart views and 52 within-view quality criteria.
Concurrent real-time acquisition and reading aid; displays examination completeness and an illustrative image subset while the healthcare professional acquires and interprets images, with clinician review, editing, or override.
Real-time fetal ultrasound images and image sequences or clips from a connected ultrasound machine for second- and third-trimester examinations; the packet names GE Medical, Samsung, Canon, and Philips ultrasound compatibility in its comparison and testing materials.
A real-time completeness overview identifying the abdomen, four-chamber, LVOT, RVOT, and three-vessel views and 52 quality criteria as verified or not verified, plus an illustrative image subset and optional quality-criterion localization boxes.
Sonographers, obstetricians, radiologists, maternal-fetal medicine specialists, and pediatric cardiologists who are qualified healthcare professionals specialized in prenatal ultrasound imaging.
The device does not select the best or diagnostically highest-quality image; its illustration represents quantitative completeness, not diagnostic quality. Clinicians must verify the views and criteria. The FDA packet marks clinical performance data as not applicable and does not establish diagnostic use.
FDA standalone performance testing used 2,288 fetal ultrasound images from 480 patient cases across 7 clinical sites in the United States and France, with test data distinct from model-development data. Acceptance criteria were sensitivity and specificity at least 85% for fetal heart views, sensitivity and specificity at least 90% for quality criteria within views, and mean bounding-box IoU at least 50% for quality-criteria localization. The packet describes paired annotators with adjudication as the reference process; clinical performance data are marked not applicable.
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 performance testing used 2,288 fetal ultrasound images from 480 patient cases across 7 clinical sites in the United States and France, with test data distinct from model-development data. Acceptance criteria were sensitivity and specificity at least 85% for fetal heart views, sensitivity and specificity at least 90% for quality criteria within views, and mean bounding-box IoU at least 50% for quality-criteria localization. The packet describes paired annotators with adjudication as the reference process; clinical performance data are marked not applicable.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
FETOLY-HEART 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 K241380
Samplen=480
Sites7
IndependenceIndependence not established
K241380
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 K241380. 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: Real-time fetal ultrasound images and image sequences or clips from a connected ultrasound machine for second- and third-trimester examinations; the packet names GE Medical, Samsung, Canon, and Philips ultrasound compatibility in its comparison and testing materials.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Installed on hardware connected to the ultrasound machine through HDMI and receiving the ultrasound stream in real time; the FDA comparison describes local or edge operation independent of the ultrasound equipment and does not establish DICOM, PACS, RIS, or EHR interfaces.
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 FETOLY-HEART software installed on a hardware device connected to an ultrasound machine through an HDMI connection, receiving that machine's ultrasound images in real time. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "To utilize FETOLY-HEART, the software needs to be installed on a hardware device which is connected to an Ultrasound Machine through an HDMI connection." … "The software receives ultrasound images captured by the connected Ultrasound Machine in real-time.". 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: A real-time completeness overview identifying the abdomen, four-chamber, LVOT, RVOT, and three-vessel views and 52 quality criteria as verified or not verified, plus an illustrative image subset and optional quality-criterion localization boxes.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A real-time completeness overview identifying the abdomen, four-chamber, LVOT, RVOT, and three-vessel views and 52 quality criteria as verified or not verified, plus an illustrative image subset and optional quality-criterion localization boxes.
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 FETOLY-HEART software installed on a hardware device connected to an ultrasound machine through an HDMI connection, receiving that machine's ultrasound images in real time. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "To utilize FETOLY-HEART, the software needs to be installed on a hardware device which is connected to an Ultrasound Machine through an HDMI connection." … "The software receives ultrasound images captured by the connected Ultrasound Machine in real-time.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Installed on hardware connected to the ultrasound machine through HDMI and receiving the ultrasound stream in real time; the FDA comparison describes local or edge operation independent of the ultrasound equipment and does not establish DICOM, PACS, RIS, or EHR interfaces.
Diagnoly's security & regulatory page states that Fetoly operates without internet or cloud dependency, so that patient data never leaves the hospital and no external access exists.
Product family
Checked 2026-10-27
Vendor statement, not an attestation. The page names Fetoly and cites US certification K251368 (FETOLY); FETOLY-HEART (K241380) is within the same Fetoly product family; exact-release scope is not established.
ACR AI Central provides an exact-submission model card for FETOLY-HEART; 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
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 K241380 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.