Secondary Service Connection: How One Condition Leads to More VA Benefits

What Secondary Service Connection Is

Secondary service connection is a legal and medical framework under VA law that allows veterans to receive compensation for conditions that were caused or made significantly worse by an already service-connected condition. In other words, your first battlefield injury doesn't just affect one system in your body — its downstream effects on your health are also compensable.

This framework exists because the body does not isolate injuries neatly. A knee injury changes your gait and puts strain on your hips and spine. Chronic PTSD disrupts sleep, elevates cortisol, and damages cardiovascular health. Diabetes attacks peripheral nerves, kidneys, and eyes. The VA recognizes this physiological reality and allows veterans to claim ratings for each condition that flows from the service-connected original.

The result is that a veteran who entered the VA system with a single 40% rating for a knee injury might legitimately be entitled to additional separate ratings for hip osteoarthritis, lumbar radiculopathy, and depression — all flowing from the original knee claim — potentially pushing the combined rating to 70%, 80%, or even 100%.

The Legal Basis: 38 CFR § 3.310

38 CFR § 3.310 is the regulatory foundation for secondary service connection. The relevant language states:

"Disability which is proximately due to or the result of a service-connected disease or injury shall be service connected. When service connection is thus established for a secondary condition, the secondary condition shall be considered a part of the original condition."

The regulation further addresses aggravation — a critical concept discussed in the next section. The phrase "proximately due to" means the service-connected condition must be a proximate (direct) cause of the secondary condition, not merely a tangential contributing factor. However, "proximate cause" in the VA context is interpreted broadly — and the benefit of the doubt standard works in the veteran's favor.

Critically, once a secondary condition is service-connected, it is treated under the law as if it were the original service-connected condition itself. This means it receives its own rating, contributes to the combined rating, and is subject to the same protections (including TDIU consideration and P&T eligibility) as any primary service-connected condition.

Two Types: Caused By vs. Aggravated By

Section 3.310 recognizes two distinct theories of secondary service connection, each with different evidentiary requirements:

Type 1: Caused By (Direct Secondary Causation)

A condition is caused by a service-connected condition when the primary condition is a proximate cause — the condition would not have developed (or would not have developed when it did) but for the existence of the service-connected condition. The causal chain must be reasonably direct and supported by medical evidence.

Classic examples include: PTSD causing sleep apnea through hyperarousal and disrupted sleep architecture; service-connected diabetes causing peripheral neuropathy through chronic hyperglycemia; or a service-connected knee injury causing contralateral hip arthritis through abnormal gait compensation. In each case, the secondary condition flows directly from the primary as a recognized medical consequence.

Type 2: Aggravated By (Aggravation Theory)

A condition is aggravated by a service-connected condition when the secondary condition existed before it was caused by the primary — perhaps it was a pre-existing condition that predated military service or developed independently — but the service-connected condition has made it permanently worse beyond its natural progression.

Under the aggravation framework established in 38 CFR § 3.310(b), if a service-connected condition aggravates a pre-existing non-service-connected condition, the VA will compensate the veteran for the additional disability caused by the aggravation — that is, the degree to which the condition is worse than it would have been without the service-connected aggravator.

This is a critical distinction: if a veteran had mild arthritis before developing a service-connected knee injury, and the knee injury's compensatory gait changes accelerated and worsened that arthritis beyond its normal progression, the veteran is entitled to compensation for the excess disability attributable to the aggravation.

The "At Least As Likely As Not" Standard

The VA applies the same evidentiary standard to secondary claims as it does to primary claims: the causal relationship must be shown to be "at least as likely as not" — meaning a probability of 50% or greater that the service-connected condition caused or aggravated the secondary condition. This standard comes from 38 CFR § 3.102, which requires the VA to give the benefit of the doubt to the veteran when evidence is in approximate balance.

What makes secondary claims often easier to win than primary claims is that the causal chain is frequently shorter and more medically direct. You don't have to prove that your hip arthritis was caused by military service. You only have to prove that your service-connected knee injury — which the VA has already accepted — caused the hip arthritis. A rheumatologist or orthopedist can often provide this nexus far more readily than proving a direct in-service connection.

Under the benefit-of-the-doubt doctrine, when medical evidence is genuinely in equipoise — equally supporting and opposing the causal connection — the VA must resolve that doubt in the veteran's favor. This means that even without a definitive causal statement, a well-reasoned medical opinion that the causal connection is "plausible and as likely as not" can be sufficient.

The Most Common Secondary Connection Chains

Certain secondary connection chains are so well-documented in medical literature and VA case law that they have become near-standard approvals with proper documentation:

PTSD → Sleep Apnea: A Well-Established Chain

The PTSD–sleep apnea connection has become one of the most commonly approved secondary claims in the VA system, supported by extensive clinical research. PTSD causes chronic hyperarousal of the sympathetic nervous system — veterans remain in a state of heightened alertness that disrupts normal sleep architecture, suppresses REM sleep, and triggers the muscular and respiratory patterns associated with obstructive sleep apnea.

The VA's own training letters and BVA (Board of Veterans Appeals) decisions have consistently upheld this connection when supported by a medical nexus letter from a sleep medicine specialist or psychiatrist linking the sleep disturbance to PTSD symptomatology. Veterans with PTSD ratings of 50%, 70%, or 100% who also have sleep apnea diagnoses should almost certainly be pursuing secondary connection.

Back Pain → Radiculopathy and Hip Problems

Lumbar spine conditions rated under 38 CFR Part 4, Diagnostic Codes 5235–5243, are among the most common service-connected conditions. What many veterans don't realize is that the same spinal pathology producing back pain often simultaneously compresses or irritates lumbar nerve roots — producing radiculopathy (sciatica) that travels down one or both legs.

Radiculopathy is separately ratable under Diagnostic Codes 8510–8730, and the ratings can be significant: 10%–40% depending on the severity of neurological symptoms. A veteran rated at 20% for lumbar strain might add 20% for left leg radiculopathy and 10% for right leg radiculopathy — substantially changing the combined rating and monthly compensation.

Diabetes → Peripheral Neuropathy and Beyond

Service-connected diabetes (typically rated under DC 7913) is a gateway condition for a wide array of secondary claims. Diabetic peripheral neuropathy affects the nerves of the extremities and is separately ratable under Diagnostic Code 8620 (sciatic nerve) or similar codes — typically at 10%–20% per extremity. A veteran with bilateral peripheral neuropathy secondary to diabetes can add 10%–20% for each affected limb.

Diabetic retinopathy (eye damage), nephropathy (kidney damage), and erectile dysfunction are also well-recognized secondary conditions that flow from service-connected diabetes and each carry their own separate ratings under 38 CFR Part 4.

Medication Side Effects: An Underused Pathway

One of the most overlooked categories of secondary service connection involves conditions caused by medications prescribed to treat service-connected conditions. Under 38 CFR § 3.310(a), if a medication prescribed for a service-connected condition causes a new medical condition, that new condition is service connected as secondary.

Common examples:

• NSAIDs (ibuprofen, naproxen) for service-connected pain → GERD, gastric ulcers, kidney damage: Long-term NSAID use is a recognized cause of gastrointestinal disorders and nephrotoxicity. Veterans on long-term NSAIDs for service-connected orthopedic or musculoskeletal pain frequently develop GERD or gastric conditions that are secondarily ratable.
• Antidepressants (SSRIs, SNRIs) for PTSD → Weight gain, Type 2 diabetes: Certain antidepressants are associated with significant weight gain and metabolic changes that can predispose to or precipitate Type 2 diabetes. If a veteran developed diabetes after years on psychiatric medications prescribed for service-connected PTSD, a secondary claim may be supportable.
• Corticosteroids for service-connected inflammatory conditions → Osteoporosis, avascular necrosis, adrenal insufficiency: Long-term steroid use causes significant bone density loss and can cause avascular necrosis of the hip or shoulder joint — conditions that are separately ratable.
• Antipsychotics for PTSD or TBI → Metabolic syndrome, tardive dyskinesia: Atypical antipsychotics prescribed for PTSD-related psychosis or sleep carry metabolic risks including weight gain, hyperlipidemia, and type 2 diabetes.

How to Build a Winning Nexus Letter

The medical nexus letter is the cornerstone of any secondary service connection claim. It is the document that bridges the gap between what the VA has already accepted (your primary service-connected condition) and the new condition you are claiming as secondary. A weak or vague nexus letter is the primary reason secondary claims are denied; a strong, specific letter is the primary reason they are approved.

A winning secondary nexus letter must:

1. Identify the author's qualifications: The physician should state their specialty and treating relationship with the veteran. A sleep specialist opining on sleep apnea carries more weight than a primary care physician.
2. State the primary service-connected condition: Reference the VA-recognized diagnosis and rating explicitly.
3. Diagnose the secondary condition: Provide the current DSM or ICD diagnosis for the secondary condition, with clinical findings supporting it.
4. State the causal opinion explicitly: Use the "at least as likely as not" language: "It is my medical opinion that [secondary condition] is at least as likely as not caused by [service-connected condition]."
5. Explain the medical rationale: Describe the biological mechanism linking the two conditions. This is where medical specificity wins claims. A nexus letter that says "PTSD can cause sleep apnea because..." and then cites the physiological mechanism is dramatically more persuasive than one that merely asserts the connection.
6. Address contrary evidence: If there are other possible causes for the secondary condition, the letter should acknowledge them and explain why the service-connected condition is nonetheless the proximate cause or a significant aggravating factor.

How to File a Secondary Service Connection Claim

Filing a secondary service connection claim uses the same form as any disability compensation claim: VA Form 21-526EZ (Application for Disability Compensation and Related Compensation Benefits). Key steps:

1. On the conditions page of 21-526EZ, list the secondary condition by its medical name. In the description field, clearly state: "This condition is claimed as secondary to my service-connected [primary condition], per 38 CFR § 3.310."
2. Upload your nexus letter as supporting evidence in the evidence upload section of the form.
3. Upload medical records confirming the diagnosis of the secondary condition, including any treatment records, imaging, labs, or specialist notes.
4. Reference the primary service-connected condition by VA claim number if known. This helps the VA rater connect the dots immediately without needing to dig through records.
5. File an Intent to File first (VA Form 21-0966) if you haven't already. This preserves your start date — the date from which back pay is calculated — while you gather your evidence.

If you are a veteran who already has an active claim in progress, you can add secondary conditions to the existing claim rather than starting a new one — consult your VSO or VA representative about the best approach given your claim's current stage.

2025 Strategic Tip: Map Your Conditions First

Before filing any claim — whether primary or supplemental — do a systematic inventory of all your service-connected conditions and ask: what else has this condition caused or made worse?

This mapping exercise is best done with a medical provider who knows your history. Ask your physician or specialist to review your current diagnoses and identify which conditions are potentially secondary to service-connected ones. Have them note the medical relationships. Then build your claims strategy around the complete picture before filing — because once you file, the start date for back pay is locked to the Intent to File or filing date, and conditions not claimed must be filed separately with potentially later start dates.

The strategic value of this approach cannot be overstated. A veteran who identifies PTSD (70%), sleep apnea secondary to PTSD (50%), hypertension secondary to PTSD (10%), and radiculopathy secondary to a 20% back rating — and files all of them together — may reach a combined rating of 90%–100% and qualify for TDIU or even schedular 100%. Use the claim.vet rating estimator to model your potential combined rating before filing.

Common Mistakes Veterans Make