b. Verifying Contentions All contentions must be verified in order for them to be available via eBenefits. Contentions automatically entered by the system will not be verified until an employee reviews the contention and checks the verified box. All employees reviewing a claim are responsible for ensuring all contentions are correct and verified. c. Classifying Contentions The CLASSIFICATION is a required component when entering a contention. When selecting a classification, use appropriate medical verbiage that corresponds to the claimed medical condition, instead of the claimant’s original language. Note: Classifying a contention is required if the MEDICAL field is set to Yes. If the MEDICAL field is set to No, adding a classification is optional. Exception: Unemployability is a classification that must be applied to an individual unemployability contention in to complete necessary specific development actions in VBMS. d. Associating Claims Types to Contentions Each contention must have the correct claim type associated with it. The contention claim types are New Increase Secondary, and Reopen. Example: A Veteran claims an increase in her service-connected (SC) peripheral neuropathy of the left lower extremity. The condition was previously granted on a secondary basis associated with the Veteran’s SC diabetes mellitus, type II. Although the condition was originally granted on a secondary basis, the current claim is for an increased evaluation. Therefore, the correct contention claim type is Increase. e. Entering a Claim-Specific Special Issue The RO has a responsibility to identify any contention that may have a special issue associated to it. Once the RO identifies the contention as having a special issue, the RO must enter a claim-specific special issue indicator that provides additional details about the contention and claim. Use of special issues is mandatory with every claim. ROs are responsible for identifying and inputting special issues where required. If a special issue exists and applies to the claim, it is required.
Example: The claimant files a claim for diabetes mellitus due to Agent Orange exposure while serving in Vietnam. Since Agent Orange is identified as a special issue, the diabetes mellitus contention must contain an Agent Orange-Vietnam special issue flash. Special issues may need to be updated throughout the life of a claim. It is important that field users are vigilant in identifying when the circumstances of the claim result in addition, removal, or editing of special issue indicators. Example: The claimant submits a Fully Developed Claim (FDC), and the user properly applies the FDC special issue indicator to one of the contentions associated with the claim. The claim is later excluded from the FDC Program based on evidence received after claims establishment, so the user edits FDC special issue from Fully Developed Claim to FDC Excluded – Evidence Received After FDC CEST. Follow the steps in the table shown below when entering a claim-specific special issue flash to a contention in VBMS. Step Action 1 Under the CONTENTION tab, select the SPECIAL ISSUES down arrow. 2 Select the appropriate special to be associated to the contention. 3 Select the SAVE button to save the special issue or the CANCEL button to discard the changes. Note: If you finish adding special issues and want to add another contention select the SAVE and ADD button. Note: To delete a special issue flash from a contention, click on the CLAIM DETAILS screen and then select the TRASH CAN icon next to the special issue to be deleted. Reference: For more information on how to apply a special issues flash to a contention in VBMS, see the . f. Properly Applying Special Issues Special issues must be applied or updated once they are identified. Use the below to determine how special issues should be applied to contentions. If the special issue applies to ... Then apply the special issue to ... the claim one contention. Examples:
Special Ops Claim Fully Developed Claim FDC Excluded – Needs Non-Fed Evidence Development a contention each applicable contention. Examples: Agent Orange – Vietnam Asbestos Burn Pit Exposure References: For more information about inputting special issues into VBMS, see the , and Modern Award Processing-Development (MAP-D), see the . 3. Utilizing Tracked Items to Document Development Introduction This topic contains general information on utilizing tracked items to document development, including purpose of tracked items creation of tracked tracked item dispositions tracked item automation accuracy of tracked and determining that a claim is ready for a decision. Change Date October 30, 2015 a. Purpose of Tracked Items The purpose of tracked items is to control receipt or non-receipt of information requested from the claimant, beneficiary, or other information provider. Status of individual tracked items will be visible through eBenefits. b. Creation of Tracked Items Tracked items are established automatically for corresponding development actions when creating and finalizing development letters in VBMS or Custom tracked items can also be established manually by the claims processor. References: For more information on creating tracked items in VBMS, see the , and MAP-D, see the .