Service Treatment Record Review for VA Disability Claims

What STRs Contain and Why the Record Structure Matters

Service treatment records are the foundation of every direct service connection claim. They document what happened to a veteran's body during military service: sick call visits, hospitalizations, line-of-duty investigations, separation physicals, and treatment notes generated by military medical personnel. Under 38 CFR § 3.303^[1], each disabling condition must be considered on the basis of the places, types, and circumstances of service as shown by service records. That language is structural. It means the STR review is not optional background reading. It is the evidentiary predicate for every theory of service connection the firm wants to build.

STRs arrive in the C-file in varying states of organization. Some files separate STRs into a dedicated section. Others have STR documents scattered across a larger claims file, interleaved with rating decisions and correspondence. Before any substantive review begins, staff should confirm the STR section is complete and segregated. The location of a document in the C-file does not change its evidentiary value, but scattered records create review gaps and slow attorney analysis. Pete attaches STR documents to the case and segments them as a discrete evidence category so the file structure doesn't obstruct the review.

The main document types to expect in an STR section:

• Induction and entrance physical exam (SF-88, DD-2808, or equivalent)
• Annual periodic health assessments
• Sick call encounter records and outpatient treatment records
• Hospitalization and inpatient records
• Dental records
• Separation physical (SF-88 or DD-2808)
• Report of Medical History completed by the veteran at separation (SF-93 or DD-2807-1)
• Line-of-duty determinations
• Physical profile records (DA Form 3349 or equivalent)

Each document type serves a different evidentiary function. The entrance physical establishes baseline health. The separation physical, and the veteran's own report of medical history at separation, often contain the most candid self-report of symptoms. Sick call records document frequency and nature of treatment. Staff reviewing an STR section should know what each document type is supposed to show before evaluating what it actually shows.

Mapping In-Service Events to Claimed Conditions

For direct service connection, the firm needs to trace each claimed condition to something in the STR: an event, an injury, an exposure, a diagnosis, or a pattern of treatment. 38 CFR § 3.303^[1] requires that each condition be evaluated against the places, types, and circumstances of service. That framing matters because the evidentiary question is not just whether something appears in the record. It is whether what appears in the record, combined with the veteran's service context, supports the claimed nexus.

For each claimed condition, the case record should reflect answers to these questions:

• Does the STR contain a contemporaneous diagnosis of the condition?
• Does the STR document an event, injury, or exposure that could cause or aggravate the condition?
• Does the STR show treatment for symptoms consistent with the claimed condition, even without a formal diagnosis?
• Do the places and types of service shown in military personnel records align with exposure or injury consistent with the claim?

A formal in-service diagnosis is strong evidence but not required. Treatment notes describing musculoskeletal pain, hearing difficulty, psychological symptoms, or other relevant complaints can support the nexus argument even when a diagnosis was not assigned. The absence of a diagnosis does not mean the condition wasn't present. Military medicine is episodic and often focused on duty fitness rather than complete diagnostic workup.

Staff should annotate each in-service event in the case record with the document source, date, condition or symptom described, and relevance to a specific claim. That annotation becomes the input for attorney review of nexus theory. The attorney decides how to use the evidence, not staff.

Identifying Chronicity and Continuity of Symptomatology

Chronicity is one of the most underutilized arguments in VA disability practice, and one of the most dependent on careful STR reading. Under 38 CFR § 3.303(b)^[2], a chronic disease shown in service can be presumed to have continued after service if there is a showing of continuity of symptomatology. The regulatory language is narrower than it sounds, but the principle applies broadly to service connection arguments built on symptom timelines rather than single in-service events.

Chronicity markers in STRs appear in predictable places:

• Repeated sick call visits for the same complaint across multiple dates
• Progressive worsening documented across successive physical exams
• Physical profile restrictions that reflect an ongoing limitation
• Separation physical findings that deviate from the entrance physical baseline
• The veteran's own separation report of medical history, which often discloses chronic complaints the record otherwise understates

The symptom timeline for each condition should run from the entrance physical through the separation date and into the post-service record. A single sick call visit for back pain is a data point. Three visits in one year, a physical profile restricting lifting, and a separation physical noting lumbar tenderness are a timeline. The difference between those two pictures is the difference between a weak nexus argument and a strong one.

38 CFR § 4.1^[3] states that each disability must be viewed in relation to its history. That principle applies not just to rating but to service connection development. The STR review should produce a documented symptom history, not just a list of found records.

Staff should build a condition-specific chronology within the case record: date, source document, symptom or finding, and how it relates to the claimed condition. Gaps in the timeline are as important as entries. A two-year period with no sick call visits during the same years the veteran reports worsening symptoms is worth flagging for attorney review.

Auditing STRs for Missing Records and Development Gaps

An STR section that looks complete may not be. The audit step is distinct from the review step, and it requires knowing what the record should contain before evaluating what it does.

Start with the veteran's service history: branches, periods, duty stations, and deployments. That information comes from the DD-214 and any military personnel file documents in the C-file. Cross-reference the service history against the STR documents. A veteran with three overseas deployments should have medical records associated with each. A veteran treated at a specific military hospital should have those records in the file. If the dates or locations don't match up, the gap is a development issue.

Common causes of missing STRs:

• The 1973 NPRC fire in St. Louis destroyed an estimated 16 to 18 million Army and Air Force personnel records from roughly 1912 to 1964. Records for veterans who separated before 1973 may be partially or fully destroyed.
• Records held by the National Personnel Records Center (NPRC) that were not requested or were requested but not transferred to VA.
• Records held at a Veterans Integrated Service Network (VISN) or military facility that were never forwarded.
• Reserve and National Guard records maintained separately from active duty records, often requiring requests to the state adjutant general.

Each gap should be documented in the case record: what is missing, what the expected source is, and whether a request has been made. This documentation protects the case at adjudication and on appeal. If VA denies a claim and the basis for denial was a missing in-service event that the firm had already flagged as an outstanding development item, the record supports a duty-to-assist argument.

Staff should not treat a missing record as a closed question. The annotation in the case record should read as an open development item until the request is resolved or the firm concludes the record does not exist.

VA's Duty to Assist and the Firm's Independent Obligations

VA is required to make reasonable efforts to obtain STRs when they are relevant to a pending claim. Under 38 CFR § 3.159(c)^[4], VA will make efforts to obtain service medical records and other relevant records held by a governmental entity. For federal records, VA continues to make requests until it is reasonably certain the records do not exist. VA.gov – VA's Duty to Assist^[5]

The duty to assist is real, but waiting on it is a risk. VA's development timeline does not match a firm's case-readiness timeline. Records requests get stuck. Follow-up doesn't happen. The case gets rated before records arrive. By the time the firm discovers the gap, the rating decision is final and the appeal window is running.

Firms should run parallel development. The M21-1, Part III, Subpart ii, Chapter 2, Section B^[6] procedures that govern VA adjudicators also tell firms where records should come from and who holds them. Firms can request STRs directly from NPRC using a Standard Form 180 or the veteran's signed authorization. For records held at military treatment facilities, the request goes to the relevant facility records department.

The claimant must provide enough information for VA to request relevant records: the custodian, approximate time frame, and condition for which treatment was provided. Federal Register – Duty to Assist Final Rule^[7] That information should be collected during case intake and documented in the case record as part of the development checklist.

Track every outstanding request in the case record. Date sent, expected source, and current status. When records arrive, staff confirms they were added to the file and cross-references them against the known gaps from the audit step.

Substitute and Supplemental Evidence When STRs Are Incomplete

Missing STRs do not end the claim. They shift the evidentiary strategy.

The M21-1 addresses fire-related and substitute records directly. M21-1, Part III, Subpart ii, Chapter 2, Section F^[8] covers the procedures for handling situations where STRs were destroyed or are unavailable, including alternative record sources and substitute evidence. When fire-related destruction is confirmed or likely, the case record should note that explicitly. VA adjudicators are required to give extra consideration to lay and secondary evidence in those situations.

Substitute and supplemental evidence options include:

• Buddy statements. Statements from fellow service members who witnessed an event, injury, or symptom pattern. These are lay evidence under 38 CFR § 3.303 and can corroborate claimed in-service events when records are missing.
• Private treatment records from the post-service period. A physician who treated the veteran shortly after discharge and documented symptoms consistent with the claimed condition can support continuity arguments.
• Photographs, personal logs, or unit histories. Less common but occasionally useful for establishing the circumstances of service.
• VA examination findings. A C&P examiner who reviews the veteran's lay account of service and finds it credible can provide nexus rationale even without contemporaneous STR documentation.

The decision about how to use substitute evidence is an attorney judgment call. Staff identifies what is missing, documents what substitute evidence exists or could be developed, and flags the gap as an attorney review item. The attorney decides whether the substitute evidence is sufficient to support the claim theory or whether additional development is needed.

Structuring STR Findings for Attorney Review

Attorney review of STRs should be focused on nexus theory and claim strategy. It should not require the attorney to sort documents, build timelines from scratch, or identify gaps that staff should have caught.

The STR section of the case record gives the attorney a file that already reflects the work. STR documents are attached to the case as a discrete evidence category. Key entries include condition tags, date references, and relevance notes. Chronicity markers are compiled into a symptom timeline by condition. Identified gaps appear as open development items with source, request status, and whether substitute evidence has been evaluated.

What the attorney sees at review:

• Per-condition summaries: what the STR shows, what it does not show, and where the record supports or undermines the claimed nexus
• Open development items requiring attorney direction, such as gaps where the duty-to-assist argument may be needed or where substitute evidence strategy requires a judgment call
• Drafted outputs that reflect the current case state, updated as new records arrive

That structure keeps attorney review on the decisions that require legal judgment. Whether the evidence supports direct service connection, how to frame the nexus theory for a C&P examiner, and whether the record is ready for submission are attorney calls. The STR workup is what makes those calls possible.

Related guides

Building a Chronological Timeline from a VA C-fileA structured C-file timeline anchors service connection theory, exposes effective date arguments, and keeps attorney review focused on the decisions that matter.VA C-file Workup ChecklistA structured C-file workup turns a raw claims file into a cited case record. This checklist covers document segmentation, chronology, conditions, exams, and evidence gaps.