The Luria report templates are scaffolded Markdown files that mirror the section structure of a polished neuropsychological evaluation. Each context — adult, pediatric, geriatric, forensic, and screening — has its own template. You start with the right headings, the right placeholders, and the right tone for the audience that will read the report.
These templates ship as plain Markdown under agents/visit2_nt/templates/. They are the input that the agent pipeline fills in during Phases B–D, and they are also useful as standalone starting points when you are writing a report by hand.
Choosing a template
| Template | When to use it |
|---|
full_neuropsych_report_template.md | Standard adult comprehensive evaluation with full battery and SIRF synthesis |
pediatric_neuropsych_template.md | School-age and adolescent evaluations where school, grade, and parent rater data matter |
geriatric_dementia_template.md | Older-adult evaluations focused on cognitive decline, capacity, or dementia differential |
forensic_neuropsych_template.md | Court-, IME-, or attorney-retained evaluations with explicit notification language |
forensic_neuropsych_addendum_template.md | Add-on sections (retention, materials reviewed, opinions to a reasonable degree) to layer on top of a clinical report when the case becomes forensic |
brief_cognitive_assessment_template.md | Screening or capacity questions where a full battery is not indicated |
neuropsych_evaluation_template.md | Generic scaffold when none of the context-specific templates fit |
nse_summary_template.md | Standalone Neurobehavioral Status Exam summary (Visit 1 output) |
score_table_template.md | Reusable score table block to include in any of the above |
full_neuropsych_report_template.md and switch to a context-specific template once the referral question is clear.
What each template gives you
Every template ships with the same backbone so the resulting reports are interchangeable across clinicians:
- A CONFIDENTIAL header block and patient identifiers
- Reason for Referral and Sources of Information sections with placeholder prose
- Background sections organized by domain (medical, psychiatric, developmental, educational, social)
- Behavioral Observations and Validity sections
- Test Results by Domain scaffolding compatible with the
score_table_template.md block
- Summary, Diagnostic Impression, and Recommendations — the SIRF half of the report
- A Signature block
Context-specific templates add their own sections on top of this backbone. The pediatric template adds developmental and school history; the geriatric template adds capacity and IADL fields; the forensic template adds notification of purpose, limits of confidentiality, and an opinions-to-a-reasonable-degree-of-certainty block.
Using a template by hand
The templates are plain Markdown. Copy one into your case folder, fill in the placeholders, and convert to PDF however you normally would.
cp agents/visit2_nt/templates/pediatric_neuropsych_template.md \
cases/doe-jane-2026/report.md
[bracketed placeholder] with the corresponding patient data, then render through your normal pipeline.
Using a template through the pipeline
Inside the pipeline, the assembly agent (report_assemble, Phase D) selects the template based on the report_type field in config.patient.yml:
patient:
first_name: Jane
last_name: Doe
dob: 2012-08-04
report:
type: pediatric # one of: adult | pediatric | geriatric | forensic | brief
.qmd to data/reports/. You then review, revise, and render to PDF.
When to extend the templates
Does your clinic see a recurring evaluation type that none of the shipped templates fit — say, a return-to-play concussion evaluation or a pre-surgical capacity screen? Copy the closest existing template, adjust the section headings, and save it next to the others under agents/visit2_nt/templates/. The assembly agent picks it up as soon as you reference it by name in config.patient.yml.
Keep the patient identifier block, the validity section, and the signature block — those are the parts that make the document defensible regardless of context. Last modified on June 3, 2026
