FDA record research

Automatic Event Detection Software For Full-Montage Electroencephalograph (OMB) — FDA decisions, comparisons and evidence

The 2021–2025 analysis contains 14 selected substantially-equivalent FDA decisions under primary product code OMB. Use it to compare documented submissions and evidence with your product. A separate 2026 update contains 1 decisions through 2026-09-27. The latest selected decision across the acquired endpoint is dated 2026-06-24. Neither set establishes a suitable predicate or the route for your device. The complete-year window has 14 decisions; the separate all-observed-date count is 42. These denominators describe different date ranges.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Recorded scope and its declared regulatory reference

An exact FDA-record regulation_number match to one acquired Title 21 section. Records with the same normalized scope definition, class, regulation and recorded submission/GMP flags are grouped. Sparse definitions and generic exemption boilerplate do not qualify. No text-similarity equivalence or legal applicability is inferred.

What scope does the FDA record describe?

Automatically mark or identify electroencephalograph waveforms for spikes, electrographic seizures, seizure-like events in order to aid in identification of such events and help review and annotation of prolonged EEG traces; All output subject to verification by qualified user

Compare the proposed indication, user, anatomy, technology and operating principle with this actual scope; record differences and unresolved facts.

Cited source

Which current section does the record cite?

§ 882.1400 Electroencephalograph. (a) Identification. An electroencephalograph is a device used to measure and record the electrical activity of the patient's brain obtained by placing two or more electrodes on the head. (b) Classification. Class II (performance standards).

Read the identification, classification, conditions and referenced limitations in the cited section. A numeric reference match is not a buyer classification or exemption determination.

Cited source

Historical FDA comparison

2021–2025: five complete calendar years

Primary code OMB

All statistics in this section use decisions dated 2021-01-01 to 2025-12-31. The partial 2026 update below is excluded from these distributions.

14Selected decisions in these five years
WithheldMedian receipt-to-decision calendar days
14Valid date pairs in the distribution

There are 14 valid recent date pairs. Distribution summaries require at least 20; older records are not substituted for a current benchmark.

20211
20221
20232
20245
20255

Statistical source: FDA openFDA 510(k) decision dataset. Partition 1 Download the identified records and dates (CSV).

Filters, exclusions and reproducible calculation

Deduplicate by official submission ID across the complete current manifest partitions. Select exact primary product code, K-number format and the stated SE decision codes with valid dates. Recent distributions use the five complete calendar years preceding the latest valid endpoint decision year. Partial-year counts compare equal January-to-cutoff periods. Quartiles use linear interpolation at (n-1)*p and are withheld below 20 valid date pairs. The analysis n describes only its declared complete-year window; selected_se_n separately counts all selected recorded dates through the cutoff.

42 selected records across all observed dates; 0 other/invalid identifier or decision-date records excluded. 0 missing or invalid date pairs in the five-year window.

Date fields: date_received → decision_date. Quantiles: Hyndman–Fan type 7: linear interpolation at (n − 1) × p; displayed to one decimal; n ≥ 20 valid pairs.

Receipt-to-decision calendar elapsed time includes time outside active FDA review; it is not FDA review time, a promised project timeline or an estimate of future clearance. This selected recorded cohort does not include all applications or establish a success probability, predicate suitability, market size, current market availability or legal authorization for another product.

Calculation fda-buyer-research-3 · database cutoff 2026-09-27. CSV rows identify each official K-number, cohort, date pair, exclusion reason and source version.

Separate partial-year update

2026 decisions through 2026-09-27

1 selected decisions from 2026-01-01 to 2026-09-27. The equivalent previous-year period contains 3 decisions through 2025-09-27. These counts describe the records; they are not market growth or submission success rates.

Named records to investigate

Latest decisions across the database

These dated records may come from 2026 or earlier years. They are a separate investigation list, not the five-year statistical cohort. Compare the actual indications and technology before considering a record as a comparator.

Official record / deviceRecorded applicantDecisionRecorded typeCalendar days
K260998 ↗Ceribell Neurology Review SoftwareCeribell, Inc.2026-06-24Traditional90
K252070 ↗Ceribell Infant Seizure Detection SoftwareCeribell, Inc.2025-11-21Traditional143
K252160 ↗Persyst 15 EEG Review and Analysis Software (Persyst 15 (P15))Persyst Development, LLC2025-10-31Traditional113
K243743 ↗autoSCORE (V 2.0.0)Holberg Eeg AS2025-04-09Traditional126
K241589 ↗Ceribell Seizure Detection SoftwareCeribell, Inc.2025-04-09Traditional310
K242446 ↗Persyst 15 EEG Review and Analysis Software (Persyst 15 (P15))Persyst Development Corporation2025-01-22Traditional159
K241390 ↗NeuroMatchLVIS Corporation2024-11-26Traditional195
K240408 ↗REMI-AI Rapid Detection Module (REMI-AI RDM)Epitel, Inc.2024-10-17Traditional251

Supporting documents actually acquired

Go beyond the database row

Read the source context, then compare the evidence with your design. Topic locations below are text matches, including possible limitations or negative statements; they are not a mandatory test list.

The documents are a bounded sample of acquired summaries, not complete evidence coverage of the cohort.

Recorded classification context

Known context: US. Match the intended use and design with the recorded category before treating it as applicable.

Source factRecorded value
FDA product codeOMB [1]
Generic device categoryAutomatic Event Detection Software For Full-Montage Electroencephalograph [1]
Recorded scopeAutomatically mark or identify electroencephalograph waveforms for spikes, electrographic seizures, seizure-like events in order to aid in identification of such events and help review and annotation of prolonged EEG traces; All output subject to verification by qualified user [1]
Recorded class2 [1]
Regulation882.1400 [1]
Medical specialtyNeurology [1]

Build a comparison that explains the differences

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which specific part of the recorded scope fits or differs?

    Put your proposed label and design beside the quoted definition. Record matching facts, differences and missing facts separately; naming the category alone cannot resolve scope.

    Useful evidence: Proposed indication/design and a definition-to-product comparison with source locators.

  2. Have the cited section and its limitations been reviewed?

    Record the applicable paragraph, conditions and cross-referenced limitations after specialist review. Keep a claimed exemption separate from actual establishment, listing and quality-system responsibilities.

    Useful evidence: Dated classification/route rationale and the current provisions relied on, with unresolved conditions.

  3. Compare your intended use with a named decision

    Choose a named record above. Put your proposed claim beside its actual indications-for-use statement. Record different patients, users, anatomy, settings and output claims; do not treat a shared code as proof of equivalence.

    Useful evidence: Your draft indications for use + the selected official summary and its exact page.

  4. Explain the technology and evidence differences

    For each comparison, record the different materials, hardware, software functions and operating conditions. Link each difference to existing evidence or an unresolved evaluation task.

    Useful evidence: A three-column matrix: comparator fact / your design fact / evidence or unresolved gap.

  5. Prepare a scope-based schedule without a sparse timing benchmark

    This recent cohort has fewer than 20 valid date pairs, so it supplies no median or percentile benchmark. Ask for a schedule based on actual preparation, evidence gaps, interactions and response assumptions; keep any historical decision context separately dated.

    Useful evidence: Document/test readiness, unresolved route/evidence tasks and the assumptions behind the specialist’s proposed sequence.

Work packages and dependencies

What needs to happen first

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA openFDA — device classification records ↗

2026-10-05 · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D01 · snapshot 936de5f5d47b9293b702fc32512a79173969fb788c74a63d9b91abe73f3b86a5

  • [1] device-classification-0001-of-0001.json:results[1961] · record 3483f0c0262b96e7ddb1ebdef28c773a1f57dca7181ce7378e71217f001fe4d3

FDA 510(k) summary — K260998 ↗

Mon, 06 Jul 2026 18:51:26 GMT · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot cbf07b16e14ae497bc5179512ab2df4ca66023a050fe3a1fa828baf6e4fee790

  • [2] PDF page 7 · record e07835f2f8ed20c8ab736d90989868d6361c5e61dbe46f5b032ab3af7a78dbe5
  • [3] PDF page 8 · record 3be593d535718c8b7d23efd1832edb1a5b3668b9a06238cc26b6aad4193bc557
  • [4] PDF page 12 · record 84307fc1a060b6dd1883be2ed55fae44524762bd8cba2299fea429ea48b6de3f

FDA 510(k) summary — K252070 ↗

Fri, 05 Dec 2025 20:59:38 GMT · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 029f9142f218e8c6564bd37b7eca1331b183ad20f3aa7ce8f9aead8d2fd59530

  • [6] PDF page 7 · record b3a307ace774de0e8cf82f94ea454b1d99b2cfb1dde0c4a02c114946f8156d05
  • [7] PDF page 8 · record e5c9403b8048f8b1d5ff2b0eab60aa9466e7945a18711a20f3ad59a7711d6dfb
  • [8] PDF page 11 · record 46398a2ba89d7e015c587abfa335848cafdcba153c14655a1fbf9461f8cb43cd

FDA 510(k) summary — K241589 ↗

Mon, 05 May 2025 10:18:56 GMT · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 71f04f7b8d21999064a6803b7ae1789cfceff2c70201c087b7400688fc4ce8c2

  • [9] PDF page 7 · record b8f12f917a26a92e4412e76747610231f522dd3ad74aa7688f0127d074c3e714
  • [10] PDF page 8 · record 42d8e49f2bc5fc5abfa30d7a3ba102a5d255a018f4fb893bf6e0accb1ec23f44
  • [11] PDF page 10 · record a1e2d7ca79fe4e4ca7daf83f6cd1893fe32560ac939495bce8cad40932c5d972

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services

Find FDA US Agent Services | Compare & Get Quotes · FDA QMSR Transition & Inspection Readiness (ISO 13485 Alignment)