Device type · LNX
Product code LNX
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
LNX
Not in our classification list
Device class
n/a
FDA decisions since 2015
0
510(k), De Novo and PMA
Adverse event reports
0
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Product code
- LNX
- FDA record
- Classification database entry for LNX
Latest FDA decisions
No 510(k), De Novo or PMA decisions for this product code since 2015.
Reports received
0
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
0
Injury reports
0
Death reports
0
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 2 | 0 | 0 | 0 |
| Jan 24 | 0 | 0 | 0 | 0 |
| Feb 24 | 0 | 0 | 0 | 0 |
| Mar 24 | 0 | 0 | 0 | 0 |
| Apr 24 | 0 | 0 | 0 | 0 |
| May 24 | 0 | 0 | 0 | 0 |
| Jun 24 | 0 | 0 | 0 | 0 |
| Jul 24 | 0 | 0 | 0 | 0 |
| Aug 24 | 0 | 0 | 0 | 0 |
| Sep 24 | 0 | 0 | 0 | 0 |
| Oct 24 | 0 | 0 | 0 | 0 |
| Nov 24 | 0 | 0 | 0 | 0 |
| Dec 24 | 0 | 0 | 0 | 0 |
| Jan 25 | 0 | 0 | 0 | 0 |
| Feb 25 | 0 | 0 | 0 | 0 |
| Mar 25 | 0 | 0 | 0 | 0 |
| Apr 25 | 0 | 0 | 0 | 0 |
| May 25 | 0 | 0 | 0 | 0 |
| Jun 25 | 0 | 0 | 0 | 0 |
| Jul 25 | 0 | 0 | 0 | 0 |
| Aug 25 | 0 | 0 | 0 | 0 |
| Sep 25 | 0 | 0 | 0 | 0 |
| Oct 25 | 0 | 0 | 0 | 0 |
| Nov 25 | 0 | 0 | 0 | 0 |
| Dec 25 | 0 | 0 | 0 | 0 |
| Jan 26 | 0 | 0 | 0 | 0 |
| Feb 26 | 0 | 0 | 0 | 0 |
| Mar 26 | 0 | 0 | 0 | 0 |
| Apr 26 | 0 | 0 | 0 | 0 |
| May 26 | 0 | 0 | 0 | 0 |
| Jun 26 | 0 | 0 | 0 | 0 |
| Jul 26 | 0 | 0 | 0 | 0 |
| Aug 26 | 0 | 0 | 0 | 0 |
| Sep 26 | 0 | 0 | 0 | 0 |
| Oct 26 | 0 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
No manufacturers to rank.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
No device problems coded.
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
No patient problems coded.
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
Z-0539-2014 · Started Dec 3, 2013 · Posted by FDA Dec 18, 2013
Reason given: Baxter Healthcare Corporation is issuing a voluntary correction for ABACUS Total parenteral Nutrition (TPN) Calculation Software versions 2.0 through 3.0 due to the possibility that a patient could receive another patient's TPN order as a result of data corruption.
Cause as FDA categorized it: Unknown/Undetermined by firm
- ORCHESTRA/ORCHESTRA PLUS ProgrammerTerminated
Z-0805-2014 · Started Nov 20, 2013 · Posted by FDA Jan 22, 2014
Reason given: Sorin has voluntarily issued a notification to physicians related to the overestimation of the residual longevity displayed by its programmer (ORCHESTRA or ORCHESTRA PLUS) during a follow-up exam of patients implanted with a REPLY or ESPRIT pacemaker.
Cause as FDA categorized it: Software design
Z-0362-2012 · Started Oct 25, 2011 · Posted by FDA Dec 2, 2011
Reason given: On 10/25/2011 SCC Soft Computer, Clearwater, FL initiated a correction on the SoftReports version 1.1.8.2.4 with Hot Fixes 1.7199.7 or 1.7200.7. When SoftReports Designer opened a layout, the system did not load the layout with the previously saved value in the NewPage property. This caused multiple patient records to...
Cause as FDA categorized it: Software design
18 more recall records with a free account
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.