Q: How does D2D work?
A: The VSO will prepare Veteran claims in their CMS, press the submit button, and the claim will be submitted directly to VBMS.
Q: What is VBMS?
A: VBMS is a repository for Veteran compensation claims and evidence, including forms, birth and medical records, and correspondence. If the VSO POA has access to VBMS through D2D, the VSO POA will be able to check whether forms and supporting documentation submitted were received.
Q: What type of forms and claims does D2D support?
A: D2D currently supports the following VA Forms as computable data: 21-22 (Power Of Attorney), 21-996 (Intent to File (ITF)), and the 526EZ Compensation Claim.
Q: Can VSOs submit other forms, for example, a 686C, through D2D?
A: D2D can accept over 500 forms as a PDF; however, currently PDFs should be supporting documentation for pending compensation claims only. The VA Form 686C can be sent as a PDF attachment to the 526EZ. If the 686C is sent separately, the Claim ID returned from the 526EZ submission must be included.
Q: What are the state VSOs’ considerations when a state does not accredit all service officers within its organization to submit claims?
A: While the state determines how to set up their POA system, VSOs typically accredit several representatives to review and send claims to D2D.
Q: Does D2D have a restriction on how many representatives may send in claims?
A: D2D does not have a restriction on how many VSO representatives may send in claims. However, D2D recommends that the VSO confer with their vendor for any technical restrictions.
Q: What are the differences between D2D and SEP?
A: While D2D and SEP in tandem offers the VSO the full spectrum of VA services, they have distinct characteristics:
Q: Who can submit claims through D2D into the Veteran eFolder?
A: The VSO submitting the claim to VA needs to be the Veteran’s Power of Attorney (POA). The VSO who has more than one CMS system must use a CMS certified to submit claims through the D2D system to the Veteran eFolder.
Q: Will the VSO need to scan documents as part of D2D?
A: No, the VSO will input documents into their Claims Management System (CMS).
Q: Does an on-boarding VSO need to build claim forms into his/her Claims Management System (CMS) system?
A: The VSO’s vendor will build the claim forms into the VSO’s CMS system. The VSO’s vendor certifies with D2D to submit claim forms to D2D, and, upon successful form certification, the vendor enables the VSO to submit certified forms to D2D.
Q: Why does the VSO need to submit Veteran identifying information to D2D when the VA should already have this information?
A: The identifying Veteran information enables the D2D system to locate the Veteran record and to match that record to the Veteran’s POA (Power of Attorney).
Q: Is the date of the original claim protected when the VA requests more medical evidence in support of a claim?
A: The original claim file date will be protected by the VSO's submittal of the Intent to File (ITF). The functionality to protect the original claim file date in the ITF is part of the October 2015 Release 2.3.
Q: Does the VSO transmit forms individually?
A: While the VSO submits the 21-22 (POA) and 21-0996 Intent to File (ITF) forms individually, the VSO typically submits the 526EZ form with supporting documentation or attachments.
Q: Can a VSO submit the initial claim through other VA services (e.g., the SEP portal or Centralized Mail), and then submit evidence for the initial claim via D2D?
A: This is not a current capability. However, this capability is undergoing research for implementation in a future release.
Q: Will D2D communicate to the VSO that a claims submission has erred? What type of messages will the VSO receive in regards to the claims submission?
A: The VSO’s CMS system will provide either a success message stating all documents were successfully sent and received, or an error message stating that not all the documents were sent and received. The error messages will explain the errors found during submission.
Q: Has the D2D Pilot submissions been successful?
A: The D2D Pilot was established to provide a baseline for proof of concept. The information gathered from the proof of concept will be used to improve the D2D services and to determine the readiness for D2D’s National Rollout.
Q: Once the VSO is familiar with D2D services, how may the VSOs communicate to D2D improvements to features or services?
A: D2D currently uses a three tier support system to resolve issues and errors. Tier 1 Support is where the VSO works directly with the vendor to identify the issue. If the problem cannot be resolved with vendor support, the problem is referred to the Tier 2 Support who communicates with the VSO and their vendor until the issue is resolved. If Tier 2 cannot resolve the issue, the issue escalates to the Tier 3 Support where the VA internal technical team resolves the issue.
Q: Can a vendor send in claims without a VSO partner?
A: A vendor must first have a Claims Management System (CMS) and an agreement with a VSO partner before the vendor can send in claims and supporting documentation into D2D.
Q: How can the VSO submit additional evidence into D2D to support a claim?
A: The VSO must submit the supplemental claim in the same format as the VSO submitted the initial claim.
Q: Where can the Word Service Definition Language (WSDL) be found?
A: The WSDL can be found in the document "VLER DAS Gateway ICD" located under the folder "Technical – Current Production".
Q: How do VSOs send a batch submission of forms and attachments?
A: Effective November 2015, Release 2.3 will allow VSOs to submit a form and its attachments individually as long as each item has the same Submission ID. Note that each attachment submission, however, must have a unique Transmission ID.
Q: Where can the response messages that D2D returns to the VSO be found?
A: The vendor may find the response messages that D2D returns to the VSO under the tab “Error Codes” in the document “VSO Interface Dictionary”, located under the folder “Technical – Future Release”.
Q: When an attachment becomes corrupted during a claim submission, does D2D return an error message to the VSO and should the VSO resend the submission?
A: D2D is in the process of reviewing if and who returns an error to the VSO’s CMS when a file becomes corrupted during a VSO’s claim submission.
Q: How is the vendor informed when there is a discrepancy between the number of items that the VSO submitted and the number of items that D2D received?
A: The D2D system will return an appropriate error response. For detailed error responses, refer to the tab “Error Codes” in the document “VSO Interface Dictionary”, located under the folder “Technical – Future Release”.
Q: What happens when content on a VA form changes?
A: VA is going to future proof all electronic forms, so that the form stored in D2D or any other system is still viable until an update can be performed. Additionally, the D2D team will inform VSOs and their vendors of impending changes to a computable form and when computable forms are accessible through the VACI website.
Q: Does the VA require that the Veteran provide signed authorization on VA forms? If yes, what is the VA-accepted method(s) for a VSO to obtain the Veteran’s signed authorization?
A: Yes, VA requires that the Veteran provide signed authorization on the appointment of the VSO as the claimant’s representative on VA Forms 21-22 and 21-526EZ.
The intent to file (ITF) form 21-0966 requires only the signature of the Claimant/Authorized Representative, where the claimant may be the Veteran.
Under the D2D system, a VSO must obtain a Veteran’s wet or penned signature and submit a scanned signed form to the D2D system. Note that in the future, D2D will accept the receipt of a Veteran’s eSignature.
Veterans Relationship Management Project Management Office
Veterans Benefits Administration
Program Analyst (D2D Business Lead)
Send Mail to Stan Moran
Veterans Crisis Line:
1-800-273-8255 (Press 1)
U.S. Department of Veterans Affairs | 810 Vermont Avenue, NW Washington DC 20420
Last updated June 03, 2015.