Authorized purpose: Aid to interpreting clinicians for calculating the number and size of ovarian follicles in a transvaginal ultrasound volume sweep of the ovaries.
Clinical role
Measurement and quantification aid during transvaginal ovarian ultrasound review, with clinician ability to verify images and add or delete measurements.
Images and patients
Ultrasound · Ovaries; ovarian follicles
Key limitation
Keep in mind: The packet establishes follicle count and size quantification against manual and SonoAVC comparisons but does not establish a diagnostic claim, a numeric sensitivity/specificity endpoint, or a particular care setting or current interface version.
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: Aid to interpreting clinicians for calculating the number and size of ovarian follicles in a transvaginal ultrasound volume sweep of the ovaries.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Ovaries; ovarian follicles Input: DICOM transvaginal ultrasound volume-sweep images of the ovaries from compatible ultrasound systems.
Who uses it?Intended users: Interpreting clinicians.
What does the software produce?Output: Automatically calculated ovarian follicle count and size in graphical and tabular displays, with the received images and clinician measurements available for review and adjustment.
What is its most important limitation?Key limitation: The packet establishes follicle count and size quantification against manual and SonoAVC comparisons but does not establish a diagnostic claim, a numeric sensitivity/specificity endpoint, or a particular care setting or current interface version.
Clinical takeaway. Clinical role: Aid to interpreting clinicians for calculating the number and size of ovarian follicles in a transvaginal ultrasound volume sweep of the ovaries.
Evidence takeaway. Evidence from the reviewed source record: Non-clinical validation included a phantom trial and two ovarian validation trials covering ovaries with three or fewer and ten or more follicles; one-to-one tracking and measurement accuracy was within the margin of error for human measurements. Prospective clinical validation compared follicle size and count with manual ultrasonographer and SonoAVC measurements and met the predetermined endpoints. The packet reports accuracy, precision, and agreement objectives but no numeric sensitivity or specificity.
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
Aid to interpreting clinicians for calculating the number and size of ovarian follicles in a transvaginal ultrasound volume sweep of the ovaries.
Measurement and quantification aid during transvaginal ovarian ultrasound review, with clinician ability to verify images and add or delete measurements.
Automatically calculated ovarian follicle count and size in graphical and tabular displays, with the received images and clinician measurements available for review and adjustment.
The packet establishes follicle count and size quantification against manual and SonoAVC comparisons but does not establish a diagnostic claim, a numeric sensitivity/specificity endpoint, or a particular care setting or current interface version.
Non-clinical validation included a phantom trial and two ovarian validation trials covering ovaries with three or fewer and ten or more follicles; one-to-one tracking and measurement accuracy was within the margin of error for human measurements. Prospective clinical validation compared follicle size and count with manual ultrasonographer and SonoAVC measurements and met the predetermined endpoints. The packet reports accuracy, precision, and agreement objectives but no numeric sensitivity or specificity.
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
Non-clinical validation included a phantom trial and two ovarian validation trials covering ovaries with three or fewer and ten or more follicles; one-to-one tracking and measurement accuracy was within the margin of error for human measurements. Prospective clinical validation compared follicle size and count with manual ultrasonographer and SonoAVC measurements and met the predetermined endpoints. The packet reports accuracy, precision, and agreement objectives but no numeric sensitivity or specificity.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Follicle Clarity Software 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 K212012
IndependenceIndependence not established
K212012
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 K212012. 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: DICOM transvaginal ultrasound volume-sweep images of the ovaries from compatible ultrasound systems.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The application is cloud-based and uses DICOM patient clinical data from compatible ultrasound systems; the packet does not establish specific PACS, RIS, EHR, or transfer 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 Follicle Clarity as a cloud-based software application package (software as a medical device), without detailing the hosting environment. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Follicle Clarity is a cloud-based software application package (software as a medical device, SaMD).". 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: Automatically calculated ovarian follicle count and size in graphical and tabular displays, with the received images and clinician measurements available for review and adjustment.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Automatically calculated ovarian follicle count and size in graphical and tabular displays, with the received images and clinician measurements available for review and adjustment.
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 Follicle Clarity as a cloud-based software application package (software as a medical device), without detailing the hosting environment. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Follicle Clarity is a cloud-based software application package (software as a medical device, SaMD).". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The application is cloud-based and uses DICOM patient clinical data from compatible ultrasound systems; the packet does not establish specific PACS, RIS, EHR, or transfer interfaces.
Cycle Clarity's trust center reports HIPAA and SOC 2 Type 2 'Compliant' status and publishes a controls overview including MFA for critical services, access granting and revocation processes, account inventory, dormant-account disabling, regular access reviews, and password management.
Vendor-wide
Checked 2026-10-27
Vendor statements, not attestations. Audit reports are request-gated and were not read; the trust center names Cycle Clarity generally and does not scope the claims to Follicle Clarity or any specific release; exact-release scope is not established.
ACR AI Central provides an exact-submission model card for Follicle Clarity; 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
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 0 PubMed and 1 ClinicalTrials.gov candidate record. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 0 PubMed and 1 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.
Care setting: Not publicly available - checked 2026-11-14 - Exact FDA submission
The exact FDA decision document was reviewed on 2026-11-14 and does not state a care setting or patient population for the subject device. Confirm intended sites and patients with the vendor and local policy.
Public pricing: Not verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K212012 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-09 - 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-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response 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: Supervised automatic ultrasound image acquisition of hand and wrist joints in adults being investigated or monitored for musculoskeletal disease.
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.
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.