What service connection requires: the three elements

Every service-connected claim gets decided against the same three-part test, whether the rater ever spells it out or not. Most denial letters that feel arbitrary or unfair trace back to one specific element that never made it into the file — not because the condition isn't real, but because the file never proved the thing the VA is legally required to see.

What does "service connection" actually mean?

Service connection is the VA's determination that a current condition is connected to military service, and it's the gateway to every other question in a claim — the rating percentage, the effective date, back pay, none of it matters until this threshold is met. Under 38 CFR § 3.303, establishing it requires three separate elements, and the VA evaluates each one independently. A claim doesn't get partial credit for two out of three.

What is the first element — a current diagnosis?

The condition has to exist now, not just at some point in the past. A diagnosis from years ago, with no treatment or documented symptoms since, reads to a rater as a condition that may have resolved — even if it hasn't. This is a common trap: veterans assume an old record settles the question, when what the VA needs is evidence the condition is still present. The current diagnosis guide covers this element in full, including why the widely repeated "12-month rule" isn't a real regulation.

What is the second element — an in-service event, injury, or exposure?

Something has to have happened during your service that could plausibly connect to the condition — an injury, a diagnosed illness, a documented exposure, or a stressor. This element leans hardest on paperwork most veterans never think to look for: Service Treatment Records (STRs), your DD-214, deployment orders, and unit records.

It also leans on the least glamorous kind of evidence there is. One line scrawled by a medic decades ago — "complained of back pain after lifting" — can be exactly what carries this element, because it proves something was documented in real time, not reconstructed years later from memory. That's the entire reason the records hunt at the start of a claim matters as much as it does.

Not every in-service event makes it into the official record, though. If yours didn't, buddy statements from people who served with you can establish that it happened — lay evidence can't diagnose a condition, but it's strong evidence of an undocumented incident or of symptoms that started in service and never fully went away. And for a defined list of conditions tied to specific exposures — many PACT Act, Agent Orange, and Gulf War conditions — the VA presumes this element automatically. Check the presumptive conditions list before assuming you have to prove an exposure from scratch.

What is the third element — a nexus connecting the two?

A current diagnosis and a documented in-service injury can both be true and still not add up to a claim, because nothing yet explains why one caused the other. That link is the nexus, and for most non-presumptive conditions it's a written medical opinion stating the connection is "at least as likely as not" — a 50% or greater probability. Without it, the VA is looking at two facts with nothing tying them together. The nexus letter guide covers what a strong one has to say and the two paths to getting one written.

What happens if one element is missing?

The claim gets denied on that specific element, regardless of how strong the other two are. A diagnosis with no documented in-service event reads as a condition with no service connection to evaluate. An in-service injury with no current diagnosis reads as something that may have resolved. And a diagnosis plus an in-service event with no nexus reads as two facts the VA has no basis to connect — which is the single most common reason legitimate claims get denied even when the underlying condition is real and well-documented on both ends.

Filing an incomplete packet doesn't just risk a denial, either — it usually means slower processing too, since a Fully Developed Claim depends on having all three elements in hand before you certify there's nothing more to submit.

Does secondary service connection use the same test?

A variation of it. Secondary conditions — sleep apnea from PTSD, radiculopathy from a back condition — don't connect to your service directly. Under 38 CFR § 3.310, they connect to a condition that's already service-connected, either because it caused the new condition or made a pre-existing one permanently worse. You still need a current diagnosis of the secondary condition and a nexus opinion — the difference is what the nexus is linking. Instead of tracing back to something that happened in service, it traces back to a condition already sitting in your file with a rating attached.

Bottom line

Three elements, all three required, no partial credit: a current diagnosis, an in-service event or exposure, and a nexus connecting them. Most denials that feel like the VA "didn't believe" a veteran are actually a missing piece of paper on one specific element, not a rejection of the underlying condition. Plain language is the whole advantage here — a veteran who understands what "nexus" and "current diagnosis" mean in VA terms stops being at the mercy of a denial letter that never explains itself. Lima Charlie's A-to-Z Checklist walks through gathering evidence for all three elements in order, from Intent to File through the nexus letter, so nothing gets submitted with a gap in it. Free, accredited help building any of these three elements is also available anytime from a Veterans Service Organization at VA.gov.

Sources: 38 CFR § 3.303 (service connection), 38 CFR § 3.310 (secondary service connection), VA.gov — evidence needed for your disability claim.