FDA 510(k) Clearance & Decision Monitor avatar

FDA 510(k) Clearance & Decision Monitor

Pricing

from $1.20 / 1,000 saved observations

Go to Apify Store
FDA 510(k) Clearance & Decision Monitor

FDA 510(k) Clearance & Decision Monitor

Monitor FDA 510(k) decisions by K number, product code or applicant. Export company and device details, source update dates and saved changes from the monthly public dataset.

Pricing

from $1.20 / 1,000 saved observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Features

Limited permissions

Share

FDA 510(k) Clearance & Decision Monitor — illustrative workflow

FDA 510(k) Clearance & Decision Monitor

Turn the monthly public FDA 510(k) decision dataset into a small, traceable research window or an exact device-decision watchlist. Each saved observation includes the K number, device and applicant names, product code, decision date, source update date and official record link. Optional comparisons show the source fields that changed between complete observations.

Start with three records

Run the default input to retrieve three substantial-equivalence decisions, sorted by source decision date. No new API key, login, proxy or paid source subscription is required for the bounded queries tested here. The public API has shared IP quotas and may temporarily reject or limit requests.

{
"maxResults": 3,
"clearanceOnly": true,
"comparePrevious": false
}

This is monthly FDA data, not a real-time device launch, availability or sales feed. sourceDataLastUpdated comes directly from the source metadata; observedAt is when this Actor read it. sourceDataAgeDays and sourceFreshness make aged source data visible. The 45-day label is a transparent observation threshold, not an FDA service guarantee. Decision-date ties retain source ordering, so a small discovery window can change membership without a new decision.

Three useful recipes

Review three FDA clearance decisions

Inspect a bounded decision-date-sorted window of three SESE records and the monthly source update date.

{
"maxResults": 3,
"clearanceOnly": true,
"comparePrevious": false
}

Track two exact device decisions

Compare source fields for two exact K-number records without inferring current device availability.

{
"kNumbers": [
"K260648",
"K263232"
],
"maxResults": 3,
"comparePrevious": true,
"snapshotName": "device-decision-watchlist"
}

Find GWL product-code decisions

Review three substantial-equivalence records for FDA product code GWL, preserving applicant and source identity.

{
"productCodes": [
"GWL"
],
"maxResults": 3,
"clearanceOnly": true,
"comparePrevious": false
}

Use kNumbers for up to 20 exact decisions. Exact IDs override discovery filters; the source request includes every selected ID even if your output cap is smaller. Missing IDs appear in SUMMARY.notFoundKNumbers without billable placeholder rows. Discovery supports up to five three-letter productCodes, an optional applicantPhrase, and clearanceOnly. Applicant phrase matching uses the source search index and does not establish a corporate identity match. Turning off clearanceOnly includes other recorded 510(k) decision codes.

What the fields mean

FieldInterpretation
kNumber, recordId, sourceUrlExact FDA submission identity and official record link.
deviceName, applicantName, productCodePublished device, applicant and product-code labels.
decisionCode, decisionDescription, decisionDateThe recorded 510(k) decision and date, not current market status.
clearanceRecordedTrue for documented substantial-equivalence codes SEKD, SESD, SESE, SESK, SESP and SESU; null for other codes. This is not PMA approval.
deviceClass, regulationNumberOptional classification harmonization from openFDA; singular values only when unambiguous. All source values are retained in deviceClasses and regulationNumbers, not a unique manufacturer linkage.
receivedDate, clearanceType, statementOrSummarySource administrative fields; missing values remain null.
sourceDataLastUpdated, sourceCadence, observedAtSource update date, monthly cadence and separate retrieval time.
comparisonStatus, changedFields, previousNew, changed or unchanged observed source fields when comparison is requested.

Applicant city/state/country are business-location labels from the record. No personal contact names, street addresses, emails, FEI/registration arrays, GMDN terms or raw source document are exported. No clearance amount, revenue, efficacy endorsement, procurement demand or buying-intent score is invented. currentMarketAvailability always remains not_determined. Do not use openFDA data to make medical-care decisions.

Saved changes and honest coverage

Run the same selection and snapshotName sequentially with comparePrevious:true. The first run is a baseline. onlyChanges:true also enables comparison and can correctly save zero records on an unchanged repeat. Source-wide metadata refreshes and ordinary passage of time do not themselves generate changed records. Record corrections are observed differences, not necessarily newly issued decisions.

History uses the named fda-device-clearance-monitor-history key-value store and scope-specific keys. Only positive observed records are retained. Missing or no-longer-selected records are never classified as withdrawn, recalled or removed. A source failure, exhausted charge allowance, interrupted output or deadline prevents the entire run from advancing its baseline. Concurrent writers are detected; run each snapshot sequentially.

SUMMARY.selectedWindowComplete covers the requested selection; sourceUniverseComplete indicates whether the response reports more matches outside that window. A complete selected window can have incomplete:false and sourceUniverseComplete:false. An exact source NOT_FOUND response is an empty query result, not proof that a clearance never existed or was withdrawn. A failed or malformed response fails visibly instead of creating a paid diagnostic row. HTTP denials and rate limits are not bypassed or repeatedly retried.

Pricing and bounds

Standard event pricing is $0.002 per confirmed saved observation, plus $0.00005 Actor Start. Three observations total $0.00605 in Actor event charges; 100 total $0.20005. Plan discounts and applicable Apify platform charges are separate. Unchanged-only runs can have zero result charges while still incurring start/platform usage. Reports and source diagnostics are not billed as dataset observations. Set Run options' maximum total charge to bound spending.

Default output is three records, maximum 100. The one source request is capped at 20 seconds and 6 MiB with public-address validation and no redirects. The default whole-run budget is 60 seconds, allowed 30–120; the platform timeout may stop sooner. The unauthenticated public API's documented quotas are shared by IP; this Actor does not accept an API key or raise source limits.

Outputs and source

Download the dataset as JSON or CSV. SUMMARY records selected coverage, source age, errors and baseline status; RUN_REPORT provides a readable report without extra paid rows. Use your own Apify saved task or API client for repeated observations. This Actor does not schedule itself, contact applicants or make purchases.

Official 510(k) API · Searchable fields · API limits · openFDA terms.

Independent of the FDA and not endorsed by it. Source data may be delayed, corrected or incomplete. Review the official record before using an observation in a business or regulatory workflow. Report reproducible issues through this Actor's Issues tab with a non-sensitive input and run link.

Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

FDA Recalls Scraper - Drug, Device & Food

Review device recall records alongside a manually matched clearance or decision record.

  1. Verify the manufacturer and exact product identity before configuring a separate device-recall search.
  2. Preserve K numbers and recall IDs as different identifiers, along with their source dates and scope.

A clearance record does not establish safety, current sale status or recall absence. Name similarity alone is not a verified product match.

FDA Warning Letter Monitor - Supplier & Closeout Changes

Add official inspection and warning-letter context when researching a device applicant or manufacturer.

  1. Independently verify the legal organization, facilities and names relevant to a device record.
  2. Configure a separate warning-letter review and retain the original letter dates and cited activities.

A matching organization name does not establish that a letter concerns the device, and no letter result is not evidence of compliance. This is research context, not a medical or regulatory determination.