The in-service event
Every sick call, profile and treatment note for the condition, quoted and dated. Often the page the C&P examiner missed.
in-service eventThe nexus is in the service records. Put it in front of the examiner.
Service treatment records and private history on 1 timeline against separation, every visit in between.
Yes. Medrecords AI merges both into 1 cited timeline.
| Date | Source | Finding | Page | Flag |
|---|---|---|---|---|
| 14 Aug 2009 | Entrance exam | Lower extremities normal. No knee complaints. | p. 4 | baseline |
| 3 May 2011 | Sick call | Left knee pain after a ruck march. Profile for 14 days. | p. 38 | in-service event |
| 22 Sep 2012 | Sick call | Knee pain recurring. Referred to orthopedics. No orthopedic note in the file. | p. 61 | missing record |
| 19 Jun 2013 | Separation exam | Knee pain marked Yes on the self-report. | p. 77 | cited |
| Date | Source | Finding | Page | Flag |
|---|---|---|---|---|
| 12 Feb 2014 | Private orthopedics | Left knee pain "since the Army". Early degenerative changes on X-ray. | p. 102 | within 1 year |
| 1 Mar 2016 to 30 Nov 2018 | No provider | No knee visits for 33 months. | none | gap, 33 months |
| 4 Dec 2018 | VA primary care | Left knee pain. Wears a brace daily. | p. 140 | cited |
| 10 Jan 2021 | Imaging center | MRI: moderate osteoarthritis, left knee. | p. 171 | cited |
| 5 Apr 2023 | C&P exam | Examiner notes no in-service treatment for the knee. | p. 198 | conflicts with p. 38 |
Examiner notes no in-service treatment for the knee.
A current disability, an in-service event and a link between them: the test for service connection.
Shedden v. Principi, 381 F.3d 1163 (Fed. Cir. 2004)Arthritis that reaches a 10% rating within a year of separation is presumed service connected.
38 CFR §3.307(a)(3)File within a year of separation and the effective date can reach back to the day after discharge.
38 CFR §3.400(b)(2)How long a typical case takes after upload.
Medrecords AIA VA claim is built on 3 elements spread across 2 record sets and often a decade or more. These are the points where they meet, each flagged with its page.
Every sick call, profile and treatment note for the condition, quoted and dated. Often the page the C&P examiner missed.
in-service eventWhat the exams recorded on the way in and the way out, set side by side.
baselineThe earliest post-service record of the condition, with its date against separation, so presumptive windows are easy to check.
38 CFR §3.307Every visit for the condition from separation to today, and every gap with both dates.
flaggedStatements in C&P exams and decisions set against the records they describe. A conflict is flagged with both pages.
conflictsThe orthopedic consult a sick call ordered, the private records a VA note mentions. Listed with the page that points to each one.
missing-records listWe assemble and cite what the service, VA and private records say. We do not decide service connection, assign a rating or write a nexus opinion. Those belong to you, the medical examiner and the VA.
No. Medrecords AI organizes and cites the service and private treatment history; it never calculates a percentage rating or predicts an outcome. Rating decisions belong to the VA.
No. It surfaces the condition-relevant entries in the record with citations, so the veteran or advocate can build the nexus argument. It never asserts that a condition is service-connected; that determination is the adjudicator's.
No. Medrecords AI does not retrieve service treatment records from the VA or DoD. You bring the STRs and private records you already have; review starts in minutes from upload.
Yes. STRs and private treatment records, in any format, are read together and merged into a single dated chronology; no manual reconciliation between the 2 sources.
From 10¢ to as low as 5¢ a page, duplicate pages free. A 1,800-page file is priced the same way as a 50-page one: by the page, with every line cited.
No. Medrecords AI organizes, cites and flags what is in the C-file you upload. It locates the in-service event, the current diagnosis and the evidence that connects them, and it lists what is missing. The nexus opinion comes from a clinician you choose, and the argument is yours. You review, you revise, you file.
Every entry on the chronology carries its source: service treatment record, VA treatment record, private record or prior rating decision. The C-file index groups the pages by source with date ranges and page spans, so the in-service history and the post-service history can be read separately or side by side.
The in-service event or exposure with its page, the current diagnosis with its page, every entry that links the 2 in time or in a clinician's own words, and the gaps: a diagnosis with no in-service entry, an in-service entry with no later follow-up, or a referenced record that is not in the file. The missing-records list is written so you can hand it to the treating provider with the request.
Yes. Range of motion, flare frequency, severity language, hospitalization counts and treatment course are grouped by condition and cited to the page, in a form you can check against the rating criteria and the DBQ questions. Medrecords AI does not assign a diagnostic code or a percentage.
Yes. Medrecords AI is SOC 2 audited and HIPAA compliant, and every file is handled under a signed Business Associate Agreement. Your records never train a model. Retention is configurable and deletion is on request, with an audit log of every access. Details on security and HIPAA.
No. It pulls out the findings each diagnostic code calls for and cites them, so you can see what the record supports and what is missing. The rating decision is the VA’s.
Yes, and that is the normal size here rather than the exception. Pricing is per page with duplicates free, and a C-file is mostly duplicates.
Yes. A supplemental claim or Board appeal turns on what the prior decision did not address, and the cited index shows which documents were in the file when the rater decided.
Book a short demo. After it we open trial access on one of your own cases, the first one free on us, with the timeline back page-cited.
Every rule, regulation, statute and published standard named on this page is linked below to the text the body that issues it puts out, read on the date shown. Where a standard is sold rather than published, the link goes to its publisher's page for it. A few rules are named without a link, because no source we could read and confirm publishes them.