Updated Nov 21, 2024
In This Section |
This section contains the following topics:
|
1. Maintenance for eFolders
Introduction
|
This topic contains information to assist Veterans Benefits Management System (VBMS) end users with maintaining an eFolder in VBMS, including
|
Change Date |
July 17, 2019 |
II.ii.2.A.1.b. Converting Documents to PDF and Uploading to the eFolder |
When a document is generated or received outside of VBMS it must be converted into a portable document format (PDF), if it is not already in this format, and uploaded into the eFolder.
Use the table below to convert and upload a PDF.
Important:
Example: A Hypertension Disability Benefits Questionnaire (DBQ) for Jamie Veteran, uploaded on October 7, 2017, could be named jvHTN100717.pdf.
Notes:
References: For more information on
|
II.ii.2.A.1.d. Indexing a Document in VBMS |
When uploading a document into an eFolder, index the document in accordance with the Document Identification and Date of Receipt Guide.
Important:
Note: Documents of an Unknown type must be relabeled. If a category and type cannot be determined, use the subject line to briefly describe the document.
References: For more information on how to
|
II.ii.2.A.1.e. Using the Document’s Subject as a Note |
To aid in easy identification of document(s) commonly used when processing a claim, use the document’s subject line as a note field. This allows for easy identification of important documents when viewing the entire eFolder under the DOCUMENTS tab in VBMS.
The table below provides the subject lines for several common documents.
Reference: For more information on changing the subject line for a VBMS document, see the VBMS Core User Guide.
|
II.ii.2.A.1.g. Redacting eFolder Documents Containing Criminal Investigation Reports |
Documents in the eFolder containing criminal investigation reports must be replaced with a redacted copy. To properly redact eFolder documents,
The claims processor must leave a note explaining the action taken. Use the table below to determine the content of the note and who is responsible for leaving it.
Note: If the subject line of the document must contain other required language, use annotations to identify the uploaded document as a redacted copy of the original.
References: For more information on
|
II.ii.2.A.1.h. Other VBMS Functionality Available to Maintain the eFolder |
VBMS-Core contains a variety of tools and functionality that allow a claims processor to organize and maintain the eFolder. Use of these features are strongly recommended, but may also be required by individual manual references and other guidance.
The VBMS Core User Guide contains instructions on how to use features such as
Note: When annotating an award for record-keeping purposes, enter information into the remarks section of the document that briefly provides the reasons for the required action.
References: For more information on
|
2. Handling Documents That Are Misfiled or Require Amendment and/or Deletion
Introduction |
This topic contains information to assist VBMS end users with maintaining an eFolder in VBMS, including
|
Change Date |
July 26, 2024
|
II.ii.2.A.2.a. Handling a Misfiled Electronic Document Identified in VBMS |
Upon identification of a misfiled document in VBMS, take action to relocate the document to the correct claims folder.
Use the table below when handling a misfiled electronic document identified in VBMS.
Note: The RO must notify the Privacy Officer when misfiled documents are released during a FOIA request.
References: For more information on how to
|
II.ii.2.A.2.b. Requesting a Document Deletion in VBMS |
Once a document is finalized in VBMS it cannot be deleted without requesting assistance from the VBMS Office of Information Technology (OIT). There are several reasons a document may need to be removed from the eFolder. This includes when a document was
Follow the steps in the table below when requesting deletion of a document from an eFolder in VBMS.
Note: Duplicate copies of medical records, exam worksheets, and VA Form 27-0820, Report of General Information, should not be deleted from an eFolder.
Exception: When the document requiring deletion contains Federal tax information, follow the guidance in M21-1, Part XIV, 4.B.2.d. Reference: For more information on managing a duplicate document, see
|
II.ii.2.A.2.c. Validating the Request for Document Deletion |
To validate the request for document deletion, an approving official must authorize the deletion of any document that is associated with an eFolder in VBMS.
The approving official must follow the steps in the table below when a VBMS Request for Document Deletion Form is received.
|
II.ii.2.A.2.d. Preparing a Document for Deletion by VBMS OIT |
The supervisor who approves the document deletion request from a claims processor must
Important: VBMS OIT will periodically run a report on the Unassociated Documents queue to locate and remove the documents that have been identified for deletion. For this reason, supervisors must use the specific subject line identified in this block.
Notes:
Reference: For more information on editing a document’s subject line, see the VBMS Core User Guide.
|
II.ii.2.A.2.f. eFolder Document Amendment |
VBMS end users must follow the steps in the table below after discovering an eFolder maintenance issue that requires the
Important: At the discretion of RO management, claims processors with Adobe Pro may be authorized to take the necessary corrective actions without requiring the submission of a Document Error Report to the local RO mailbox.
|
II.ii.2.A.2.g. Removing an Incorrectly Scanned Document |
PDF editors, or claims processors given the authority to perform the corrective actions, will determine if an incorrectly scanned document needs to be removed from the eFolder. This action will be taken once the claim processor has completed the VBMS Request for Document Deletion Form and e-mailed the form to the specified mailbox.
Notes:
Reference: For more information on working with unassociated documents, see the VBMS Core User Guide.
|
II.ii.2.A.2.h. Merging Documents in VBMS |
PDF editors, or users with Adobe Pro who have been given permission by RO management to make the required changes, must follow the steps in the table below when merging multiple eFolder documents into a single merged document.
Reference: For more information on the responsibilities of PDF editors, see M21-1, Part II, Subpart ii, 2.A
.2.g. |
II.ii.2.A.2.i. Splitting Documents in VBMS |
PDF editors, or users with Adobe Pro who have been given permission by RO management to make the required changes, must follow the steps in the table below when splitting a document into multiple eFolder documents.
Reference: For more information on the responsibilities of PDF editors, see M21-1, Part II, Subpart ii, 2.A.2.g.
|
3. Missing Claims Materials That Were Previously of Record
Introduction |
This topic describes the actions to take when claims materials that were previously of record go missing, including |
Change Date |
November 21, 2024 |
II.ii.2.A.3.a. Identifying Missing Claims Materials That Were Previously of Record |
In some situations, there may be indications that claims materials were previously of record and viewed by RO personnel. Identify lost claims of this type through review of claim notes and other identifiers in the corporate record.
Consider a claim lost if there is an electronic record of a pending claim but the claims folder contains no documents related to the claim.
References: For more information on
|
II.ii.2.A.3.b. Replacing Missing Claims Materials That Were Previously of Record |
Follow the steps in the table below upon identification of missing claims materials that RO personnel may have previously viewed.
Note: If, within one year of the date of the letter referenced in Step 4, a claimant resubmits a claim that VA lost, use the date of receipt of the initial (lost) claim as the DOC when reestablishing EP control. Otherwise, use the date of receipt of the resubmitted claim.
|
4. Claims Materials That Are Misplaced in the CM System
Introduction |
This topic contains information on allegations from claimants or their representatives of lost claims associated with the CM system, including |
Change Date |
November 30, 2020 |
II.ii.2.A.4.a. Fax Confirmation Page the CM Scanning Vendor Provided to Claimants |
The scanning vendor provided a single confirmation page to claimants when the vendor received documents via the designated intake fax number.
The confirmation page
Note: The first page of a claimant’s fax transmission was generally, but not necessarily, a cover sheet.
Reference: For more information on the intake fax number for the CM scanning vendor, see the VA Mailing Address for Disability Compensation Claims webpage.
|
II.ii.2.A.4.b. Resubmission of a Lost Claim With Copy of the Fax Confirmation Page |
Claimants may resubmit a lost claim, but the claim must be accompanied by a copy of the original fax confirmation page referenced in M21-1, Part II, Subpart ii, 2.A.4.a.
To retain the original DOC, the following must be provided in addition to a copy of the original fax confirmation page:
Example: If the confirmation page shows 10 pages received, including the cover sheet, more than 9 pages of resubmitted documents will not be accepted as eligible to receive the original VA date stamp provided by the CM vendor.
Reference: For more information on the confirmation page provided to claimants by CM vendors, see M21-1, Part II, Subpart ii, 2.A.4.a.
|
II.ii.2.A.4.c. Resubmission of Alleged Lost Claims Absent the VA Date- Stamped Fax Confirmation Page |
If a CM vendor fax confirmation page with a VA date stamp is not provided by the claimant alleging a lost claim, then the original DOC associated with the alleged lost claim cannot be accepted.
References: For more information on the
|
5. Claims Materials Submitted Using a VA Electronic Application Process That Fails to Upload to the eFolder
Introduction |
This topic contains information on locating missing claims documents submitted using a VA electronic application process, including
|
Change Date |
February 5, 2021 |
II.ii.2.A.5.a. Identifying Claims Submitted Using a VA Electronic Application Process That Failed to Upload to the eFolder |
In rare situations, a technical error in the Enterprise Veterans Self Service (EVSS) system, which supports electronic transmission of claims material through VA claims submission service websites, results in the failure of a claims document to upload to the eFolder. These cases can be identified by
Notes:
|
II.ii.2.A.5.b. Allowing Time for Automatic Retransmission of Documents That Failed to Upload |
In most situations, if claims documents failed to upload through EVSS to the eFolder, the documents will be retransmitted within two weeks without any RO action.
Follow the steps in the table below when a claim is received without supporting claims documents.
Important: Ensure the claim goes to Ready to Recall – Yes status.
References: For more information on
|
II.ii.2.A.5.c. Requesting Retransmission of Claims Documents That Failed to Upload |
Follow the steps in the table below if claims documents fail to upload after the 15-day period referenced in Step 2 of the procedure outlined in M21-1, Part II, Subpart ii, 2.A.5.b, ends.
|
II.ii.2.A.5.d. Notifying a VSO That Claims Documents Submitted Through D2D Failed to Upload |
The D2D application submission process does not have functionality to re-transmit documents that have failed to upload. Follow the instructions in the table below when claims documents submitted through D2D fail to upload.
Notes:
References: For more information on
|