Overview
In This Section |
This section contains the following topics:
|
1. System-Generated Data Table Entries and the Jurisdiction of the Codesheet
Introduction |
This topic contains information about the system-generated data table entries and the Jurisdiction of the Codesheet, including
|
Change Date |
June 27, 2016
|
III.iv.6.D.1.a. System-Generated Data Table Entries Organized by Field |
Use the table below to determine when entries are generated by the system in the fields of the data tables on the Codesheet based on user-entered data on the MASTER RECORD tab and/or DISABILITY DECISION INFORMATION screens.
Note: Each page of the rating decision contains a header with information identifying the claimant and rating.
Reference: For more information on preparing a rating decision using the Veterans Benefits Management System – Rating (VBMS-R), see the VBMS-R User Guide.
|
2. Additional Service Codes
Introduction |
This topic contains information about additional service codes, including
|
Change Date |
October 19, 2018 |
III.iv.6.D.2.a. Generating Additional Service Codes |
The additional service code is automatically generated when, for example, the decision maker selects combat related.
|
III.iv.6.D.2.b. Description of the Codes |
Use the table below for a description of additional service codes.
|
3. Combat Status Codes
Introduction |
This topic contains information about combat codes, including
|
Change Date |
December 13, 2005
|
III.iv.6.D.3.a. Definition: Combat Disability |
The term combat disability applies to any injury incurred in action against an enemy of the United States or as a result of an act of such an enemy. These injuries include
Reference: For more information on combat-related disabilities, see M21-1, Part IV, Subpart ii, 2.B.3.d. |
4. Special Provision Codes
Introduction |
This topic contains information on special provision codes, including
|
Change Date |
March 13, 2017
|
III.iv.6.D.4.a. Definition: Special Provision Codes |
Special provision codes are used to identify those rating cases that contain an evaluation or combined degree that would not ordinarily be acceptable but for a special provision of the rating schedule or other Department of Veterans Affairs (VA) regulation.
|
III.iv.6.D.4.b. Data Capture of Special Provision Codes |
VBMS-R captures the required special provision code data for Codesheet entry based on selection(s) made from the OTHER – SPECIAL PROVISION DETERMINATIONS drop-down on the ISSUE MANAGEMENT tab.
Reference: For further information on selection of special provisions, see theVBMS-R User Guide.
|
III.iv.6.D.4.c. Descriptions of Individual Special Provision Codes |
The table below contains descriptions for each of the seven special provision codes.
|
III.iv.6.D.4.d. Examples of Special Provision Code 6 Indicating Computer Audit Acceptance |
The following are examples of the use of special provision code 6 when a combined evaluation is not justified by the individual evaluations in cases:
|
5. SMC Codes
Change Date |
April 3, 2015
|
III.iv.6.D.5.a. SMC Codes |
VBMS-R captures the required SMC coding for Codesheet entry based on data entered on the SMC CODES tab.
Reference: For more information on entering SMC codes, see
|
6. Special Notations and Notification Templates
Introduction |
This topic contains information on use of the SPECIAL NOTATION field and notification template, including
|
Change Date |
October 19, 2018
|
III.iv.6.D.6.a. Purpose of Special Notations and Notification Templates |
The primary purposes of notations made in the SPECIAL NOTATION field and the notification template fields on the Codesheet are to
Note: All special notations and templates are generated through input in the PROFILE tab of VBMS-R.
Reference: For more information on the PROFILE tab, see the VBMS-R User Guide.
|
III.iv.6.D.6.b. Special Notation Field |
Use the SPECIAL NOTATION field, accessible from VBMS-R’s PROFILE tab, to communicate an instruction or administrative message to the authorization activity. Clarify if the message is solely administrative (for example, Cancel the erroneously established EP 930) or to be shared with the Veteran (for example, Tell the Veteran that the evaluation of his nephrolithiasis is currently awaiting higher-level review and will be addressed in a future decision).
Note: The special notation text appears at the bottom of the Codesheet above the signature(s).
Reference: For more information on the SPECIAL NOTATION field, see theVBMS-R User Guide.
|
III.iv.6.D.6.c. Amputation Rule Template |
Use the amputation rule template, accessible from VBMS-R’s PROFILE tab, to list the disabilities and evaluations included in the application of the amputation rule.
Show the actual combined evaluation of all disabilities of the affected extremity, as well as the schedular evaluation associated with amputation of the extremity at the elective level.
Note: The amputation rule text appears at the bottom of the Codesheet above the signature(s).
References: For more information on
|
III.iv.6.D.6.d.
|
Use the 38 CFR 3.105(a) grant template, accessible from VBMS-R’s PROFILE tab, when granting benefits on the basis of clear and unmistakable error (CUE).
Note: The 38 CFR 3.105(a) template is comprised of both automated text and free text. It appears at the top of the first page of the Codesheet below the data tables.
Reference: For more information on the CUE template in VBMS-R, see
|
III.iv.6.D.6.e.Accrued Grant Template |
When granting an accrued benefit claim, use the language generated by enabling the accrued grant template accessible from VBMS-R’s PROFILE tab.
Note: The accrued template is only available for selection if the Veteran is deceased. When generated, the accrued grant template will appear at the top of the first page of the Codesheet below the data tables.
Reference: For more information on the accrued grant template, see the VBMS-R User Guide.
|
7. Signature
Introduction |
This topic contains information on the signature line on rating decisions, including
|
Change Date |
November 8, 2018
|
III.iv.6.D.7.a.
|
Rating decisions must contain the decision maker’s digital signature on the bottom of the last page of the Codesheet.
A rating decision signature is defined as
Exception: If a rating decision requires more than one signature, the rating decision Codesheet must display the required additional signature fields, but the digital signatures of the additional reviewers must be documented on VA Form 21-0961, Electronic Signatures.
Important: The signature of the decision maker(s) certifies that the claims folder was reviewed and all phases of the claims process leading to the decision were correctly handled.
References: For more information on
|
III.iv.6.D.7.b.Procedure for Completing a Digital Signature on the Rating Decision Codesheet |
The rating decision Codesheet must contain the standardized digital signature of the decision maker as described in M21-1, Part III, Subpart iv, 6.D.7.a. “Wet signatures” are no longer required.
To establish the standardized digital signature, users should navigate to the SIGNATURE/DOCUMENT TITLE tab in VBMS-R’s options configurations, and populate the AUTHOR SIGNATURE LINE field as follows:
eSign: certified by [decision maker’s LAN ID, job title]
Example: eSign: certified by VSCJSMIT, RVSR
References: For more information on
|
III.iv.6.D.7.c.Single-Signature Ratings |
Single-signature authority is restricted to decision makers whose ability to produce quality work independently without additional oversight has been demonstrated by review.
Note: Authority for single signature may
|
III.iv.6.D.7.d.Two-Signature Ratings |
All rating decisions require the signatures of two decision makers, unless approved as single-signature ratings by the Veterans Service Center Manager (VSCM) or Pension Maintenance Center Manager (PMCM).
Exception: The VSCM/PMCM does not have authority to grant single-signature authority in all cases. The table below lists specific types of rating issues that always require a second signature.
Note: Follow locally established policies to obtain a third signature, when required.
References: For more information on
|
III.iv.6.D.7.e.
|
The table below describes the steps involved in obtaining second/third signatures for rating decisions in VBMS.
Important:
|
III.iv.6.D.7.f.Exhibit: Rating Decision Codesheet Signature Field |
The exhibit below contains a sample rating decision Codesheet with the signature field containing the electronic signature certification statement and the user’s LAN ID.
![]() |
8. Exhibit 1: Sample Draft Codesheet for a CUE Rating Decision
Change Date |
March 13, 2017
|
III.iv.6.D.8.a.Sample Draft Codesheet, CUE Rating Decision |
The exhibit below contains a sample draft Codesheet for a CUE rating decision prepared under the authority of 38 CFR 3.105(a).
![]() |
9. Exhibit 2: Sample Draft Codesheet for Application of the Amputation Rule
Change Date |
June 27, 2016
|
III.iv.6.D.9.a.Sample Draft Codesheet, Amputation Rule |
The exhibit below contains a sample draft Codesheet demonstrating proper application of the amputation rule under 38 CFR 4.68.
![]() |
6-9-17_Key-Changes_M21-1III_iv_6_SecD.docx | May 15, 2019 | 404 KB |
6-5-17_Key-Changes_M21-1III_iv_6_SecD.docx | May 15, 2019 | 411 KB |
Change-April-3-2015-Transmittal-Sheet-M21-1III_iv_6_SecD_TS.docx | May 15, 2019 | 37 KB |
Transmittal-M21-1MRIII_iv_6_SecD_TS.docx | May 15, 2019 | 38 KB |
Transmittal-12_13_05.doc | May 15, 2019 | 52 KB |
in Chapter 6 The Rating Decision, Part III General Claims Process, Subpart iv General Rating Process
Related Articles