MRI Assessment of the Multifidus Muscle in Patients Undergoing Microdiscectomy or Physiotherapy: A Retrospective Analysis

The Body's Invisible Seatbelt

Imagine your spine as a tall, wobbly tower of blocks. To keep it from toppling over when you twist, bend, or carry groceries, nature installed a complex system of internal cables and shock absorbers: your back muscles. Deep inside your lower back, tucked right against the spine, sits a specific set of cables called the multifidus muscle. Think of these as the "seatbelts" for your vertebrae. They are the unsung heroes that stop your spine from sliding around too much.

Sometimes, the soft cushions between the spinal blocks (called discs) get squished and bulge out, poking a nearby nerve. This is a disc herniation, and it causes the kind of back pain that makes you want to stay in bed forever. When this happens, doctors have two main ways to fix it: they can try to calm the pain with exercises and rest (physiotherapy), or they can perform a tiny surgery called a microdiscectomy to remove the part of the disc that is poking the nerve.

For a long time, people worried that cutting into the back muscles to get to the spine might damage the very "seatbelts" needed to hold the spine together. Would the surgery make the muscles shrink or turn into useless fat? Or would the muscles bounce back? This question is the heart of the story we are about to tell.

---

The Great Muscle Mystery: Surgery vs. The Gym

A team of researchers from Poland decided to play detective with a group of 50 young adults (ages 18 to 40) who had a bulging disc in their lower back. They wanted to see what happened to the "seatbelt" muscles (the multifidus) after the patients either got surgery or stuck to a strict exercise plan.

To get the answers, they used a giant, super-powerful camera called an MRI. This camera doesn't just take a picture of the back; it can count the pixels of muscle and fat inside the muscle itself. The researchers looked at three groups:

1. The Surgery Group: 31 people who had the disc removed.
2. The Exercise Group: 10 people who treated their pain without surgery.
3. The "Super Healthy" Group: 10 people with no back pain at all, used as a perfect reference.

The Surgery Group was special. They didn't just get the operation and go home. Starting just 48 hours after surgery, they began a very specific, step-by-step exercise program. It started with simple breathing and tiny muscle twitches, then moved to lifting legs while lying down, and eventually to standing and moving. It was like a "muscle boot camp" designed to wake up the deep muscles without straining them.

The researchers took MRI snapshots at three times: before the surgery, 3 months after, and a full year after. They measured three things:

• TCSA: The total size of the muscle (including everything inside it).
• MCSA: The size of the actual, healthy muscle fibers.
• FCSA: The amount of fatty tissue hiding inside the muscle (which is bad news for strength).

What They Found: The Muscle Didn't Give Up

Here is the big surprise: The surgery did not destroy the muscles.

Many people feared that cutting into the back would leave the muscles weak and shriveled. But the MRI scans told a different story. After one year, the muscles in the surgery group were actually slightly bigger than they were before the operation. Specifically, the healthy muscle tissue (MCSA) grew by an average of 0.6 cm².

Think of it like a garden. Before the surgery, the garden (the muscle) was a bit overgrown with weeds (fat) and the flowers (muscle fibers) were small. After the surgery and the special exercises, the garden didn't just survive; the flowers grew a little bigger, and the weeds didn't take over.

The researchers also looked at the "fat percentage" inside the muscle. In the surgery group, the amount of fat inside the muscle at the L4-L5 level actually decreased significantly after just 3 months. This is a great sign because it means the muscle was getting cleaner and healthier, not fatter.

When they compared the surgery group to the exercise-only group and the healthy group, the results were interesting. The surgery group didn't end up with bigger muscles than the healthy people, but they didn't end up with worse muscles either. They caught up. The surgery didn't cause the muscle atrophy (shrinking) that some feared.

The Pain Vanished

While the muscle measurements were the main focus, the researchers also asked the patients how they felt. The results here were dramatic.

• Before surgery: The pain was a 8.4 out of 10 (on a scale where 10 is the worst pain imaginable).
• 3 months later: The pain dropped to 0.67.
• 1 year later: The pain was down to 0.45.

Disability (how hard it was to do daily tasks) also crashed from 0.71 to 0.04. Essentially, the patients went from being unable to move to feeling almost completely normal.

The Verdict: Surgery + Boot Camp Works

The paper concludes that getting a microdiscectomy (the surgery) does not cause the multifidus muscles to waste away. In fact, when combined with a quick start on rehabilitation (starting just two days after the operation), the muscles actually improved. They got a tiny bit bigger, and the fat inside them went down.

The authors suggest that this success might be because the surgery removed the pain, allowing the muscles to finally "wake up" and work again, or because the early exercises helped the nerves reconnect with the muscles.

Of course, the researchers admit their study had some limits. It was a "pilot study," meaning it was relatively small (only 50 people total), and they looked at two different levels of the spine (L4-L5 and L5-S1) together, which might have mixed up some details. They also only had one person measure the MRI pictures, which could introduce a tiny bit of bias.

But the main message is clear and hopeful: If you need surgery for a bad back, it doesn't mean your muscles are doomed. With the right mix of a precise operation and a dedicated, early exercise plan, your body's internal seatbelts can not only survive the cut but actually get stronger and healthier again.