FDA-cleared profile

Folliscan

Mim Fertility · Ultrasound · FDA-cleared (510(k))

Authorized purpose: Semi-automatic ovarian follicle count and size assessment from transvaginal ultrasound, with clinician verification before clinical use.

Clinical role
Follicle segmentation, measurement and counting
Images and patients
Ultrasound · Pelvis/Ovaries
Key limitation
Keep in mind: Results must be manually verified in a DICOM viewer before clinical use. The submitted algorithms are fixed; the software does not replace clinician assessment.

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: Semi-automatic ovarian follicle count and size assessment from transvaginal ultrasound, with clinician verification before clinical use.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Pelvis/Ovaries Input: DICOM 2D+t cine loops or 3D transvaginal ultrasound scans capturing an ovarian sweep.
  • Who uses it?Intended users: Clinicians interpreting transvaginal ovarian ultrasound examinations.
  • What does the software produce?Output: Follicle contours, two orthogonal diameters and volume, and counts per ovary in size groups below 10 mm, at least 10 but below 17 mm, and at least 17 mm.
  • What is its most important limitation?Key limitation: Results must be manually verified in a DICOM viewer before clinical use. The submitted algorithms are fixed; the software does not replace clinician assessment.

Clinical takeaway. Clinical role: Semi-automatic ovarian follicle count and size assessment from transvaginal ultrasound, with clinician verification before clinical use.

Evidence takeaway. Evidence from the reviewed source record: The FDA summary describes a held-out test set of 138 scans from 64 patients at five clinics, including 45 US scans, with expert-reviewed reference contours and patient-separated development/test data.

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
Semi-automatic ovarian follicle count and size assessment from transvaginal ultrasound, with clinician verification before clinical use.
  • Exact FDA submission
  • Checked 2026-09-05
Workflow role
Follicle segmentation, measurement and counting
  • Exact FDA submission
  • Checked 2026-09-05
Required input
DICOM 2D+t cine loops or 3D transvaginal ultrasound scans capturing an ovarian sweep.
  • Exact FDA submission
  • Checked 2026-09-05
Output and clinician action
Follicle contours, two orthogonal diameters and volume, and counts per ovary in size groups below 10 mm, at least 10 but below 17 mm, and at least 17 mm.
  • Exact FDA submission
  • Checked 2026-09-05

Restores the comparison operators missing from the baseline size-bin text.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Source-backed baseline patient-population label retained.

Intended users
Clinicians interpreting transvaginal ovarian ultrasound examinations.
  • Exact FDA submission
  • Checked 2026-09-05
Limitations
Results must be manually verified in a DICOM viewer before clinical use. The submitted algorithms are fixed; the software does not replace clinician assessment.
  • Exact FDA submission
  • Checked 2026-09-05
Evidence summary
The FDA summary describes a held-out test set of 138 scans from 64 patients at five clinics, including 45 US scans, with expert-reviewed reference contours and patient-separated development/test data.
  • Exact FDA submission
  • Checked 2026-09-05

Development involved 2132 patients at seven centers and 6404 DICOM datasets; those are not the test denominator. No IVF outcome benefit is inferred.

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
The FDA summary describes a held-out test set of 138 scans from 64 patients at five clinics, including 45 US scans, with expert-reviewed reference contours and patient-separated development/test data.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-05

Development involved 2132 patients at seven centers and 6404 DICOM datasets; those are not the test denominator. No IVF outcome benefit is inferred.

Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-05

No product-wide sensitivity with a verified exact-release endpoint/threshold is promoted; follicle measurement and count errors are distinct endpoints.

Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-05

No product-wide specificity with a verified exact-release endpoint/threshold is promoted.

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

K252332 held-out follicle measurement and counting validation

  • DesignMulticenter held-out standalone evaluation against expert-reviewed follicle reference contours
  • Population138 transvaginal ultrasound scans from 64 patients at five clinics; 45 scans from the United States
  • Scopeexact submission
  • Tested versionFolliscan configuration submitted in K252332
  • Samplen=64
  • Sites5
  • IndependenceSponsor or vendor study

K252332

Sample size is patients, not scans or follicles. Patient-level split avoids development/test overlap. The summary's volume error/unit presentation is not promoted as a normalized numeric metric.

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
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-06

Downloaded exact-ID recall packet contained zero records; this limited result does not establish absence of recall or safety information.

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: DICOM 2D+t cine loops or 3D transvaginal ultrasound scans capturing an ovarian sweep.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-05 · Folliscan: K252332 clearance and 510(k) summary

  2. Routing

    Source context, not route validation: DICOM image submission and review workflow, with API use dependent on a validated connector and manual verification of results.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-05 · Folliscan: K252332 clearance and 510(k) summary

  3. AI processing

    Source context, not route validation: Web application or API access through a validated connector.

    Scope: Exact FDA submission.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-05 · Folliscan: K252332 clearance and 510(k) summary

  4. Returned objects

    Source context, not route validation: Follicle contours, two orthogonal diameters and volume, and counts per ovary in size groups below 10 mm, at least 10 but below 17 mm, and at least 17 mm.

    Scope: Exact FDA submission. Restores the comparison operators missing from the baseline size-bin text.

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

    Field checked 2026-09-05 · Folliscan: K252332 clearance and 510(k) summary

  5. Viewer/worklist/report

    Unresolved route: Follicle contours, two orthogonal diameters and volume, and counts per ovary in size groups below 10 mm, at least 10 but below 17 mm, and at least 17 mm.

    Scope: Exact FDA submission. Restores the comparison operators missing from the baseline size-bin text.

    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-05 · Folliscan: K252332 clearance and 510(k) summary

  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
Web application or API access through a validated connector.
  • Exact FDA submission
  • Checked 2026-09-05
Integration
DICOM image submission and review workflow, with API use dependent on a validated connector and manual verification of results.
  • Exact FDA submission
  • Checked 2026-09-05

Web/API workflow

Web application or API through a validated connector, with manual result verification in a DICOM viewer.

exact submission · checked 2026-09-05

Family integration choices

Vendor describes edge-device, EMR and manual-upload routes with browser access.

product family · checked 2026-09-06
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
K252332
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-05
Anatomy
Pelvis/Ovaries
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-05

Narrows the baseline Abdomen;Pelvis classification to the explicitly described ovarian target.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2026-04-20
  • 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.

Human reviewedStatus
2026-09-06Last searched
20Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

Stored literature-index and trial-registry candidate arrays were empty and screened. This does not establish absence of literature; current vendor page links newer papers/posters that were not fully reviewed or promoted here. 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, acr ai central product, fda decision summary, vendor product page, literature index, trial registry, stored candidate metadata, 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-06 - Exact FDA submission

    Reviewed product page offers contact/demo access, not a verified license, connector, edge-device or implementation price.

  • Pricing model: Not verified - checked 2026-09-06 - Exact FDA submission

    Per-cycle, per-exam and site licensing terms remain unresolved.

  • 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: "Mim Fertility 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
  • Security: Not verified - checked 2026-09-06 - Exact FDA submission

    Family FAQ makes hosting/encryption statements, but scoped dated security evidence and exact-US-configuration data-processing terms were not established.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-06 - Exact FDA submission

    Exact connector/operator training curriculum, competency assessment and costs require confirmation.

  • Monitoring: Not verified - checked 2026-09-06 - Exact FDA submission

    Contracted post-installation quality monitoring and incident-handling responsibilities were not established.

7 sources - 3 history items

Source ledger

  1. Folliscan: K252332 clearance and 510(k) summary

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

    Scope: purpose, clinicalUse, modality, anatomy, input, output, limitations, deployment, integration, evidenceStudies

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Folliscan model card (K252332)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: purpose, modality, intendedUsers, careSetting, output, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  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. Folliscan product and integration FAQ

    MIM Fertility - Accessed 2026-09-06

    Scope: productFamilyContext, deployment, implementationCapabilities

Research history

  1. K252332 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K260667

Alturion Series Diagnostic Ultrasound System

Philips Ultrasound, LLC

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
Decision
2026-06-29
FDA-cleared K260190

ARTHUR

ROPCA ApS

Authorized purpose: Supervised automatic ultrasound image acquisition of hand and wrist joints in adults being investigated or monitored for musculoskeletal disease.

Modality
Ultrasound
Anatomy
Hand/Wrist
Decision
2026-06-18
FDA-cleared K260844

ACUSON Sequoia Diagnostic Ultrasound System;ACUSON Sequoia Select Diagnostic Ultrasound System;ACUSON Origin Diagnostic Ultrasound System;ACUSON Origin ICE Diagnostic Ultrasound System

Siemens Medical Solutions USA, Inc.

Authorized purpose: ACUSON Sequoia, Select, Origin, and Origin ICE diagnostic ultrasound systems acquire and display the labeled fetal, abdominal, pediatric, neonatal, cephalic, small-part, obstetric, cardiac, transesophageal, intracardiac, vascular, and musculoskeletal examinations.

Modality
Ultrasound
Anatomy
Fetus; abdomen; pelvis; small organs; head; heart; peripheral vessels; musculoskeletal anatomy; transesophageal and intracardiac applications
Decision
2026-06-16
FDA-cleared K260300

WatchMate Software

Anumana, Inc.

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.

Modality
Ultrasound
Anatomy
Heart and left atrial appendage
Decision
2026-06-15

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