# Nexus Letter Record Review > Nexus letter record review: a cited service-connection timeline from the C-file, so the opinion writer builds a rationale on evidence instead of memory. Canonical page: https://medrecords.ai/solutions/nexus-letter-record-review/ --- New — **Missing Records Detection:** flags every visit, provider, and date missing from the file. [See how →](https://medrecords.ai/product/missing-records-identification/) [Home](https://medrecords.ai/) ›[Solutions](https://medrecords.ai/solutions/) › — Nexus Letter Record Review NEXUS LETTER RECORD REVIEW ## The rating is decided on the rationale, not on the conclusion. Nexus letter record review services give the opinion writer a cited service-connection timeline: the in-service event or exposure, the continuity of symptoms after discharge, and the post-service diagnosis, each linked to its page in the C-file. The opinion and its rationale stay with the clinician. [Test a file ](https://medrecords.ai/test-a-file/?src=nexus-letter-record-review) [Book a demo](https://medrecords.ai/demo/) Click any row → the source page it cites Service-connection timeline · Case #IME-4812 documented Adams, Timothy · C-file 342 pp / 2 packets received logged 11 duplicate pages removed free p.140 — wrong patient quarantined Pages 342 Documents 27 Cited 100% ### VA tells raters exactly what makes a private opinion adequate. We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. For nexus opinions the standard is published in the regulations and the adjudication manual, and the referee is the rater who applies it. The standard and the referee The rulebook - 38 CFR §3.303(d) and §3.310, which define direct service connection for a disease diagnosed after discharge and secondary service connection for a condition caused or aggravated by a service-connected one - 38 CFR §3.102, the benefit of the doubt rule, under which an opinion that the link is at least as likely as not is enough, and under which a bare conclusion is not - The VA Adjudication Procedures Manual M21-1, which tells the rater what makes a private medical opinion adequate and what makes it inadequate - 38 CFR §4.1 and §4.2, which require the rating to rest on review of the entire recorded history rather than on the most recent examination alone The referee - The rating veterans service representative, who weighs the private opinion against the C&P examiner’s and can discount one that does not show the file was reviewed - The Board of Veterans’ Appeals, which remands for a new opinion when the rationale does not connect the evidence to the conclusion - The Court of Appeals for Veterans Claims, whose case law on adequate reasons and bases is what makes the rationale rather than the conclusion the operative part of the letter A nexus opinion discounted because it never showed the file was read From 10¢ to as low as 5¢/page here, duplicates free Service-connection timeline · Case #IME-4812 cited 100% Packet — 342 pp / 2 packets · 11 deduplicated — logged In-service events and exposures — Every entry in the service treatment records — cited Continuity of symptomatology — Every post-discharge contact on the same complaint — cited Evidence against the claim — Including the C&P examiner’s stated rationale — flagged Timeline delivered · cited 100% · no medical opinion How it works ### 3 steps between the C-file and the timeline. 01 #### Send the C-file Service treatment records, the claims file, VA and private treatment records, and any prior C&P examination reports, in any format. 02 #### We return the timeline, page-cited The in-service event or exposure, every documented symptom contact from discharge forward, the diagnosis and its date, and the evidence that cuts the other way. 03 #### The clinician writes the opinion The likelihood statement and the rationale behind it are the clinician’s, made on their own judgment. The timeline is what shows the file was actually reviewed. The boundary, in writing ### A timeline of the file, not a nexus opinion. We assemble and cite the record the opinion will rest on. We do not state that a condition is at least as likely as not related to service, write the rationale, or sign anything. A nexus opinion is a medical opinion, made and signed by a qualified clinician. In the demo case, page 140 turned out to belong to a different patient. In a C-file that error puts another veteran’s finding into a service-connection argument, so it is quarantined rather than folded quietly into the history. Audit trail · Case #IME-4812 exportable 08:12 — Packet received · 342 pp / 2 packets — system 08:31 — 11 pages deduplicated — system 08:44 — p.140 flagged — wrong patient — system 08:54 — Service-connection timeline complete · timeline delivered · cited 100% — system 09:20 — Service-connection timeline reviewed · citations verified — reviewer 09:26 — Service-connection timeline exported · opinion letter written by the clinician — reviewer Every access logged · file deleted 30 days after delivery Why Medrecords AI ### The rules the platform never breaks. EVERY LINE CITED CASE #IME-4812 · ADAMS, T. 342 pp 2/14 — ER visit, right knee p.4 4/18 — arthroscopic surgery p.61 p.140 — wrong patient quarantined Medrecords AI Read every page · cite every line #### HIPAA, under a signed BAA Every file is handled under our Business Associate Agreement, from the first byte. #### Never trains a model Your records are never used to train any AI model — ours or anyone else's. #### Every line cited If we can't cite it, we don't say it. Every sentence links to its source page. #### Deleted after delivery Files are deleted 30 days after delivery, with a full audit log of every access. Powered by the platform ### 7 capabilities behind every service-connection timeline. The service-connection timeline is one deliverable of the same platform that reads, sorts, and cites the whole record. [ #### Medical Records OCR Every page read in full, including the service treatment records where the in-service entry usually sits. IN ACTION · 342 pp / 2 packets → 27 documents, read in full ](https://medrecords.ai/product/ocr/) [ #### Medical Chronology The timeline assembles itself from dates across service and civilian care, so continuity reads as a sequence rather than as a claim. IN ACTION · in-service event → current diagnosis, one continuous timeline ](https://medrecords.ai/product/chronology/) [ #### Verifiable AI Citations Every entry links back to its page, including the ones the rater will use against the claim. IN ACTION · timeline → cited 100% ](https://medrecords.ai/product/citations/) [ #### Medical Summary Reports It exports into the clinician’s opinion letter in their format. IN ACTION · timeline → opinion-ready ](https://medrecords.ai/product/summaries/) [ #### Medical Record Deduplication Forty charts pulled from multiple practices and EHR migrations carry their share of duplicate visit notes. Each is matched and collapsed to one canonical record, so the prescribing pattern is read once per real encounter. IN ACTION · 40 charts → duplicate visit notes collapsed to 1 record each ](https://medrecords.ai/product/medical-record-deduplication/) [ #### Missing Records Identification A prescribing pattern read across 40 charts is only as sound as the file behind it. When a chart references a visit, refill, or referral that never made it into the production, the gap is flagged before the pattern goes to the board. IN ACTION · prescribing pattern cross-checked → gaps flagged before submission ](https://medrecords.ai/product/missing-records-identification/) [ #### Cross-Exam Simulator (beta) A board investigator or defense counsel builds a case from the chart abstraction. This beta tool maps the questioning a physician facing that hearing is likely to face on the gaps and pattern in their own record. A rehearsal tool, not legal advice. IN ACTION · prescribing pattern → likely hearing questions mapped (beta) ](https://medrecords.ai/product/cross-exam-simulator/) FAQ ### Nexus letter record review, answered. No. The likelihood statement and the rationale are a medical opinion under 38 CFR §3.303(d), made and signed by a qualified clinician. We build the cited timeline the clinician reads before forming it. Because M21-1 and the Board both discount an opinion that does not show the file was reviewed. A conclusion with no visible evidence chain behind it gets weighed against the C&P examiner’s and loses, however well the conclusion is worded. Yes, flagged in its own state. The rater is going to read it either way, and an opinion that addresses the contrary evidence is the one that survives review. Leaving it out is how a letter gets remanded. No. Medrecords AI does not retrieve records from providers or facilities. You bring the records you already have — review starts in minutes from upload. Retrieval vendors take days; you can keep yours and still cut the review to minutes. ### Send one file. We'll tell you what we can read. No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so. [Test a file ](https://medrecords.ai/test-a-file/?src=nexus-letter-record-review) [Book a demo](https://medrecords.ai/demo/) [See every case type we process →](https://medrecords.ai/solutions/case-types/) ### More solutions - [**The registrar is the bottleneck, and the backlog never clears.** — NTDB and TQIP abstraction support — data-standard elements, injury coding evidence and outcome fields located…](https://medrecords.ai/solutions/trauma-registry-abstraction/) - [**The routine certifications are fine. It's the escalated ones that cost.** — Medical certification review for escalated FMLA and ADA cases — second and third opinions, intermittent-leave…](https://medrecords.ai/solutions/fmla-ada-certification-review/) - [**The same injury story turns up in 40 unrelated files. Reading one at a time, no one connects them.** — SIU fraud review, No Surprises Act IDR, and Medicare audit response — clinical documentation read and cited…](https://medrecords.ai/solutions/claims-integrity/) - [**The same narrative, in 40 unrelated patients' charts.** — Cross-claim medical record analysis for SIU units — cloned notes, protocol uniformity, billed-vs-documented…](https://medrecords.ai/solutions/provider-fraud-record-review/) - [**The SOAF a referee opinion can actually stand on.** — SOAF preparation for federal injury compensation programs. Accepted conditions, dates of injury and job factors…](https://medrecords.ai/solutions/statement-of-accepted-facts/) - [**The therapy notes are the file. Read all of them, in your report format.** — Years of therapy notes, hospitalization records, and medication histories organized and cited — drafted…](https://medrecords.ai/solutions/forensic-psychological-evaluators/)