510(k) Report

510(k) · Cleared

Cleared

Liaison Anti-Hav Assay, Liaison Control Anti-Hav

K082049510(k) TraditionalCleared Dec 5, 2008140-day reviewClass II21 CFR 866.3310

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

DiaSorin, Inc. · LOL Hepatitis A Test (Antibody And Igm Antibody)

Cleared on Dec 5, 2008 as substantially equivalent to P890019 (Diasorin, 1990) after a 140-day review. Its family tree reaches back 1 generation to 1990.

Decided
Dec 5, 2008
Review
140 days
Class
Class II
Product code
LOL
Recalls
None
Predicates
1

Its longest line of descent runs back 1 generation to P890019 (1990). No later device cites it as a predicate yet.

P890019 · AB -Havk · Diasorin · 199019901995200020052010
P890019 · AB -Havk · Diasorin · 19900
  1. Root · 1 generation backP890019 AB -HavkDiasorin · 1990
  2. This deviceK082049 Liaison Anti-Hav Assay, Liaison Control Anti-HavDiaSorin, Inc. · 2008
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1P890019AB -HavkDiasorin1990—
0 (this device)K082049Liaison Anti-Hav Assay, Liaison Control Anti-HavDiaSorin, Inc.2008—
FIG. 1 — Lineage of K082049, 1990–2008Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in LOL? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

Top candidate predicates for a new LOL device

  1. #1 K251995 Access anti-HAV IgMscore 13.7 · 1 generation · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) Report

What was it cleared against? (1)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*P890019AB -Havk
Summary page 1
…LOL, JJX PREDICATE DEVICES DiaSorin Inc. ETI-AB-HAVK Plus assay (PMA #P890019/S05) DEVICE DESCRIPTION: INTENDED USE: The LIAISONeAnti-HAV assay is an in vitro chemiluminescent immunoassay intended for…
Diasorin1990—

Also cleared against P890019: 1 other device →

What descends from it?

No later submission names this one as a predicate yet.

Has anything in its family been recalled? (0 Class I)

No FDA recall names this device.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • Its one ancestor has no recall.
  • 1 other device also cites its predicate P890019.

How does its category compare?

All LOL devices

LOL Hepatitis A Test (Antibody And Igm Antibody): FDA decisions, review times, recalls and adverse event reports over 20 years. 2008, this device’s year, is highlighted.

FDA decisions per year · LOL

1in 2025

2007: 32008: 32009: 22010: 22011: 12012: 12014: 22016: 22019: 12020: 12021: 12022: 12023: 12025: 12026 (partial year): 2
2007high 3 (2007) · low 0 (2013)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · LOL

108in 2008

2007: 182 days median2008: 108 days median
2007high 182 (2007) · low 108 (2008)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · LOL

2in 2019

2007: 22008: 12009: 12011: 12018: 12019: 2
2007high 2 (2007) · low 0 (2010)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · LOL

19in 2025

2007: 22008: 132009: 242010: 532011: 3532012: 422013: 492014: 192015: 292016: 362017: 262018: 612019: 512020: 1042021: 122022: 172023: 362024: 212025: 19
2007high 353 (2011) · low 2 (2007)2025

MAUDE reports naming product code LOL, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
2007318222
20083108113
20092—124
20102—053
20111—1353
20121—042
20130—049
20142—019
20150—029
20162—036
20170—026
20180—161
20191—251
20201—0104
20211—012
20221—017
20231—036
20240—021
20251—019
20262—0—

What is it indicated for?

The LIAISON® Anti-HAV assay is an in vitro chemiluminescent immunoassay intended for the qualitative detection of total antibodies to hepatitis A (anti-HAV) in human serum and sodium heparinized plasma samples using the automated LIAISON® Analyzer. The assay is indicated as an aid in the laboratory diagnosis of current or previous HAV infections in conjunction with other serological and clinical information and to determine the presence of an antibody…

Read the full statement (139 words)

The LIAISON® Anti-HAV assay is an in vitro chemiluminescent immunoassay intended for the qualitative detection of total antibodies to hepatitis A (anti-HAV) in human serum and sodium heparinized plasma samples using the automated LIAISON® Analyzer.

The assay is indicated as an aid in the laboratory diagnosis of current or previous HAV infections in conjunction with other serological and clinical information and to determine the presence of an antibody response to HAV in vaccine recipients.

This assay is not intended for screening blood or solid or soft tissue donors. Assay performance characteristics have not been established for immunocompromised or immunosuppressed patients. The user is responsible for establishing their own assay performance characteristics in these populations.

The LIAISON® Control Anti-HAV (negative and positive) is intended for use as assayed quality control samples to monitor the performance of the LIAISON® Anti-HAV assay.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K082049: Liaison Anti-Hav Assay, Liaison Control Anti-Hav.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 5, 2026. https://510kreport.com/device/K082049

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026