Authorized purpose: Delivery Date AI analyzes obstetric ultrasound images to provide a predicted delivery date for singleton pregnancies in women age 18 or older at 14 0/7 through 36 6/7 weeks when the last-menstrual-period date or first-trimester ultrasound is unreliable or unavailable; the output is an aid to clinical judgment.
Clinical role
Obstetric-image analysis that provides a predicted delivery date as an aid to clinical judgment.
Images and patients
Ultrasound · Pregnancy and obstetric anatomy
Key limitation
Keep in mind: The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
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: Delivery Date AI analyzes obstetric ultrasound images to provide a predicted delivery date for singleton pregnancies in women age 18 or older at 14 0/7 through 36 6/7 weeks when the last-menstrual-period date or first-trimester ultrasound is unreliable or unavailable; the output is an aid to clinical judgment.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Pregnancy and obstetric anatomy Input: Supported obstetric ultrasound images from singleton pregnancies within the labeled gestational-age and dating-history conditions.
Who uses it?Intended users: Qualified obstetricians, maternal-fetal-medicine specialists, sonographers, and other trained healthcare professionals.
What does the software produce?Output: A predicted delivery date and associated workflow display for clinician review.
What is its most important limitation?Key limitation: The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
Clinical takeaway. Clinical role: Delivery Date AI analyzes obstetric ultrasound images to provide a predicted delivery date for singleton pregnancies in women age 18 or older at 14 0/7 through 36 6/7 weeks when the last-menstrual-period date or first-trimester ultrasound is unreliable or unavailable; the output is an aid to clinical judgment.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA De Novo decision material describes the software-only radiological system, labeled pregnancy and dating-history criteria, the risk of inappropriate management from inaccurate prediction, and special controls. No generic obstetric outcome or universal accuracy claim is inferred.
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
Delivery Date AI analyzes obstetric ultrasound images to provide a predicted delivery date for singleton pregnancies in women age 18 or older at 14 0/7 through 36 6/7 weeks when the last-menstrual-period date or first-trimester ultrasound is unreliable or unavailable; the output is an aid to clinical judgment.
The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
The exact FDA De Novo decision material describes the software-only radiological system, labeled pregnancy and dating-history criteria, the risk of inappropriate management from inaccurate prediction, and special controls. No generic obstetric outcome or universal accuracy claim is inferred.
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 De Novo decision material describes the software-only radiological system, labeled pregnancy and dating-history criteria, the risk of inappropriate management from inaccurate prediction, and special controls. No generic obstetric outcome or universal accuracy claim is inferred.
Sensitivity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if one is later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if one is later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
DEN250007 FDA evidence package for Delivery Date AI
DesignFDA De Novo decision with machine-learning software, risk-control, analytical, clinical-image, and usability evidence described in the exact submission
PopulationSingleton pregnancies in women age 18 or older at 14 0/7 through 36 6/7 weeks without a reliable estimated due date from the labeled standard methods
Scopeexact submission
Tested versionDelivery Date AI configuration described in DEN250007
IndependenceSponsor or vendor study
DEN250007
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to DEN250007 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
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: Supported obstetric ultrasound images from singleton pregnancies within the labeled gestational-age and dating-history conditions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The public exact-submission material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The public exact-submission material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: A predicted delivery date and associated workflow display for clinician review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A predicted delivery date and associated workflow display for clinician review.
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.
Only qualified obstetricians, maternal-fetal-medicine specialists, sonographers, and other trained healthcare professionals should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
Product family
Checked 2026-09-04
Current vendor material is product-family context for DEN250007; confirm exact cleared version, enabled options, deployment, and local compatibility.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, and downtime contract locally.
product family · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally. Current vendor material is product-family context; confirm exact release, enabled options, deployment, and local compatibility.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The output is an aid and not a replacement for standard gestational-age methods or clinical judgment; the labeled singleton, age, gestational-age, dating-history, image-quality, and clinical-use limits apply.
product family · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. Current vendor material is product-family context; confirm exact release, enabled options, deployment, and local compatibility.
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-20Last searched
27Fields reviewed
12Source 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 material, vendor product page, peer reviewed literature, clinical trial registry, reimbursement policy, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The public exact-submission material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The public exact-submission material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
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
Security: Not verified - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Ligence Heart is a fully automated software platform that processes, analyses and makes measurements on acquired transthoracic cardiac ultrasound images, automatically producing a full report with measurements of several key cardiac structural and functional parameters. The data produced by this software is intended to be used to support qualified cardiologists or sonographers for clinical decision making. Ligence Heart is indicated for use in adult patients. Ligence Heart has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g., tumors, thrombi). Limitations: Poor image capture will lead to poor annotations and subsequent measurements. Multiple image quality algorithms are used to filter out images of poor quality. Our software complements good patient care and does not exempt the user from the responsibility to provide supervision, clinically review the patient, and make appropriate clinical decisions. If no gender is present, female referenced guideline values will be used for conclusions. If Body Surface Area (BSA) is not present, indexed values cannot be provided. During image acquisition, inappropriate use of the echo machine, use of non-cardiac ultrasound probes, or use of suboptimal settings (e.g., gain, contrast, depth) may lead to lower accuracy of the software. Ligence Heart has not been validated in patients with prosthetic or surgically altered cardiac valves, implantable intracardiac devices, or irregular (non-sinus) rhythm; these conditions may affect automated measurement accuracy.
Authorized purpose: Velacur Sonic measures liver tissue stiffness, ultrasound attenuation, and volume density fat fraction with shear-wave and ultrasound measurements to aid clinical management of liver disease, including steatosis, within the labeled workflow.
Authorized purpose: The ACUSON Sequoia and Sequoia Select systems provide ultrasound images or signals for the labeled fetal, abdominal, pediatric, neonatal cephalic, small-parts, OB/GYN, cardiac, pelvic, vascular, adult-cephalic, musculoskeletal, and peripheral-vascular applications; the system also supports UDFF liver-fat-fraction measurement and the ACUSON Origin includes intracardiac and intraluminal imaging guidance during adult and pediatric cardiac procedures.
Modality
Ultrasound
Anatomy
Fetal, abdominal, pediatric, neonatal cephalic, small parts, OB/GYN, cardiac, pelvic, vascular, adult cephalic, musculoskeletal, peripheral vascular, intracardiac, and intraluminal cardiac or great-vessel anatomy
Authorized purpose: Velacur Sonic measures liver tissue stiffness and ultrasound attenuation to aid clinical management of liver disease within the labeled workflow.
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.