510(k) Report

510(k) · Cleared

Recalled · Class II · 2017

Maximis Spinal Fixation System

K140359510(k) TraditionalCleared Jan 7, 2015329-day reviewClass II21 CFR 888.3070Recalls 144

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

Valorem Surgical · MNH Orthosis, Spondylolisthesis Spinal Fixation

Cleared on Jan 7, 2015 as substantially equivalent to K120538 (Korea Bone Bank Co., Ltd., 2012) after a 329-day review. Its family tree reaches back 7 generations to 2000. It has been recalled 144 times.

Decided
Jan 7, 2015
Review
329 days
Class
Class II
Product code
MNH
Recalls
144
Predicates
1

Its longest line of descent runs back 7 generations to K000319 (2000). 12 ancestors in all. No later device cites it as a predicate yet.

  1. Root · 7 generations backK000319 Ebi Xfix DFS SystemEbi, L.P. · 2000
  2. 6 generations backK020279 Forex Corporation, Optima, Spinal SystemForex Corp. · 2002 · Recalled
  3. 5 generations backK031585 U&I, Optima, Spinal SystemU&I Corp., America · 2003 · Recalled
  4. 4 generations backK053573 GSS Pedicle Screw SystemGS Medical Co., Ltd. · 2006
  5. 3 generations backK082509 Eos Spinal SystemKorea Bone Bank Co., Ltd. · 2008
  6. 2 generations backK102574 Palla M Spinal SystemKorea Bone Bank Co., Ltd. · 2011
  7. 1 generation backK120538 Palls M Spinal SystemKorea Bone Bank Co., Ltd. · 2012
  8. This deviceK140359 Maximis Spinal Fixation SystemValorem Surgical · 2015
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−7K000319Ebi Xfix DFS SystemEbi, L.P.2000—
−6K020279Forex Corporation, Optima, Spinal SystemForex Corp.20024
−5K031585U&I, Optima, Spinal SystemU&I Corp., America20035
−4K053573GSS Pedicle Screw SystemGS Medical Co., Ltd.2006—
−3K082509Eos Spinal SystemKorea Bone Bank Co., Ltd.2008—
−2K102574Palla M Spinal SystemKorea Bone Bank Co., Ltd.2011—
−1K120538Palls M Spinal SystemKorea Bone Bank Co., Ltd.2012—
0 (this device)K140359Maximis Spinal Fixation SystemValorem Surgical2015—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
200040
200610
FIG. 1 — Lineage of K140359, 2000–2015Source: 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 MNH? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

  • Candidate predicates for a device like this, rankedin the report
  • Recall history across each candidate’s familyin 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
*K120538Palls M Spinal System
Summary page 5
…used with autograft of allograft. 7. Comparison with predicate device: The MAXIMIS TM Spinal Fixation System is substantially equivalent to the Pallas M Spinal System (K120538), a currently marketed Spinal System. When considered for posterior applications, both the MAXIMIS TM Spinal Fixation System and…
Korea Bone Bank Co., Ltd.2012—

What descends from it?

No later submission names this one as a predicate yet.

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

Recalls of this device

DateClassRecallRoot causeReason
Jun 21, 2017Class IIZ-2879-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2875-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2936-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2978-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2998-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2926-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2944-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3016-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2973-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2933-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3002-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2951-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3006-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2918-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2891-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2939-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2979-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2925-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2894-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2982-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2952-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2930-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2915-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2886-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3005-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2941-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2956-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2962-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2999-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2901-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2893-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3014-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2917-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2977-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2885-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2994-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2935-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3015-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2928-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2959-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2971-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2989-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2889-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2987-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2995-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2927-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-3008-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2934-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2880-2017Device DesignDevices are not consistent with Quality System Requirements.
Jun 21, 2017Class IIZ-2984-2017Device DesignDevices are not consistent with Quality System Requirements.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 15 years and passes through 6 companies; a new generation was cleared every 2.3 years on median.
  • 2 of the 12 ancestors have a recall of any class.

How does its category compare?

All MNH devices

MNH Orthosis, Spondylolisthesis Spinal Fixation: FDA decisions, review times, recalls and adverse event reports over 20 years. 2015, this device’s year, is highlighted.

FDA decisions per year · MNH

8in 2016

2007: 52008: 132009: 132010: 102011: 172012: 72013: 102014: 122015: 102016: 8
2007high 17 (2011) · low 0 (2017)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MNH

93in 2016

2007: 123 days median2008: 65 days median2009: 151 days median2010: 106 days median2011: 171 days median2012: 93 days median2013: 124 days median2014: 140 days median2015: 99 days median2016: 93 days median
2007high 171 (2011) · low 65 (2008)2026

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

Recalls per year · MNH

1in 2016

2009: 72012: 12013: 12016: 1
2007high 7 (2009) · low 0 (2007)2026

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

Adverse event reports per year · MNH

89in 2025

2007: 182008: 302009: 452010: 592011: 1072012: 4332013: 4642014: 2862015: 1522016: 2162017: 1742018: 1292019: 4032020: 4322021: 5312022: 2652023: 1212024: 3022025: 89
2007high 531 (2021) · low 18 (2007)2025

MAUDE reports naming product code MNH, 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
20075123018
20081365030
200913151745
201010106059
2011171710107
20127931433
2013101241464
2014121400286
201510990152
20168931216
20170—0174
20180—0129
20190—0403
20200—0432
20210—0531
20220—0265
20230—0121
20240—0302
20250—089
20260—0—

What is it indicated for?

The Valorem Surgical MAXIMIS™ Pedicle Screw Fixation System is intended for posterior pedicle screw fixation of the non-cervical posterior spine in skeletally mature patients. It provides stabilization and immobilization of spinal segments as an adjunct to fusion in the treatment of the following acute and chronic instabilities or deformities: 1) trauma (i.e. fracture or dislocation), 2) curvatures (scoliosis, kyphosis, and/or lordosis) 3) spinal tumor, 4) failed previous fusion, 5) pseudoarthrosis, 6) spinal stenosis. It is not intended for pedicle screw fixation above T8. This device may be used with autograft of allograft.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K140359: Maximis Spinal Fixation System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 3, 2026. https://510kreport.com/device/K140359

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