Prompt engineering is the skill of asking AI systems precise, structured questions that get you accurate, usable answers about VA regulations and your claim strategy. Since AI tools can hallucinate or oversimplify, learning to frame your questions right—with specific dates, regulation numbers, and context—turns them from entertaining to genuinely useful.
Prompt engineering in the VA claims context means designing questions and instructions that force an AI system to do deep analytical work across multiple documents—not just summarize them. A weak prompt: "Analyze my VA claim." A strong prompt specifies exactly what analysis you need, in what format, with what level of detail.
The most effective VA prompts follow a pattern: context + task + constraints + output format. Example: "You are analyzing a VA disability claim for lower back pain. Review these four documents: [service records, medical records, VA rating schedule excerpt, prior decision letter]. For each VA diagnostic code potentially applicable to this condition, identify: (1) whether the medical evidence in the file supports rating at that code, (2) specific evidence gaps, (3) what additional evidence would strengthen the claim at that rating level. Format your response as a table with columns for each diagnostic code."
This structure works because it:
For multi-step claims analysis, use prompt chaining—multiple AI interactions where the output of one becomes the input of the next. First prompt: "Identify all medical diagnoses mentioned in these records." Second prompt: "For each diagnosis, list corresponding VA rating codes and rating percentages." Third prompt: "Based on the severity indicators in the medical records, estimate which rating level each diagnosis would likely receive." This sequential approach is more reliable than asking the AI to do all three steps simultaneously.
VA claims often contain contradictions—a medical exam saying "no functional impairment" alongside a VA&E report saying "significant limitations." A targeted prompt: "These documents contain conflicting assessments of functional status for [condition]. For each assessment method (VA exam, private medical provider, veteran self-report), describe what factors might explain the discrepancy. Which assessment aligns most closely with VA rating schedule criteria for functional impairment?" This prevents the AI from averaging conflicting evidence and instead pushes it to analyze why conflicts exist and which evidence is most relevant to VA standards.
VA claims analysis benefits from lower temperature settings (0.3–0.5 range). Lower temperature reduces the AI's creativity and makes it more consistent and rule-following—exactly what you need when matching evidence to VA schedules. Higher temperatures are useful for brainstorming service narratives but dangerous for claims analysis.
Claude tends to provide more detailed reasoning around evidence gaps; ChatGPT excels at structured table output. For claims analysis, Claude's reasoning transparency often outweighs formatting neatness.
Try this: Take a VA decision letter denying one of your claims and prompt an AI: "This VA decision denied my claim for [condition] citing insufficient evidence of service connection. The stated reason for denial was [paste exact reason]. Based on the medical records I'm providing, does the evidence actually support service connection under VA standards? For each required element (incurrence in service, current diagnosis, medical nexus), evaluate whether the provided records meet the standard." Review the AI's element-by-element analysis and use it to identify exactly which evidence gap is blocking your appeal.
Peri can explain this concept, give practical examples, help you decide whether it applies to your situation, or recommend a journey if appropriate.
Explore related journeys or tell Peri what you're working through.