Business intake form for [10-10 Health Apps]

[coope93]

VA Notify: Important Scheduling Information

As we approach the end of the year, please note that VA Notify will not be starting any new notification intakes after November 15th. Our focus will be on supporting in-progress notifications, urgent zero silent failure use cases, and completing 2024 initiatives. Kick-off meetings for new intake forms submitted after November 15th will be scheduled in January.

Important Reminder: Please be mindful of launching new notifications before the holidays unless there is a business-critical deadline. There will be a VA platform code freeze 12/23/2024 - 1/3/2025, with limited support during this time.

If you have any other urgent needs that require attention before the end of the year, please reach out as soon as possible for review.

Your Details

1. Your Name

   • Brandon Cooper
     ​

2. Business Line
   (ex., claims, health, etc.)

   • Health Tools

3. VA Product/Business Owner Contact Information

   • Patrick Bateman
     ​

Notification Details

1. Notification type
   (email, text/SMS, or both)

   • email
     ​

2. Please describe your use case.
   (This is your chance to tell us an overview of your plans.)

   • We use sidekiq to submit the 10-10CG form to the Mulesoft API where it is processed to CARMA. Very rarely there will be some issue where the sidekiq job will fail and run out of retries. Right now, we get a notification about the failure and reach out to the CARMA team with the Veteran information for them to contact the Veteran directly. We would like to send an email to the Veteran(if it was provided as part of the form; it is an optional field) when the failure occurs informing them of the submission failure and who to contact for assistance. We already send a similar email for the 10-10EZ and 10-10EZR forms.
     ​

3. What actions can the user take based on the notification they receive?
   (ex., view secure messages, fill out a survey, schedule an appt, etc.)

   • The Veteran is provided a link to go back to the 10-10CG and a phone number to call for assistance.
     ​

4. What is the desired business outcome?
   (ex., fewer skipped appointments, less call center volume, etc.)

   • Allowing the Veteran to know about the failure sooner, and providing the necessary information on who to contact to get the form processed faster.
     ​

5. What system will kick off the notification? Please note the system should be inside the VA or have an ATO.
   (ex., BVA hearing reminders are kicked off from Caseflow)

   • vets-api
     ​

6. What is the primary software language your system is built on?
   (ex., Python, Java, etc)

   • Ruby on Rails

7. What will trigger the notification?
   (ex., clicking submit, status updates for claims, appointment reminders, new services available)

   • Sidekiq job running out of retries

8. Provide sample content per notification type, if you have it.
   Please note we collaborate with all of our users on their content to ensure it meets standards.

   • It will be very similar to our 10-10EZ and 10-10EZR submission failure emails.
     ​

9. Has a Privacy Officer (PO) seen and approved the content? If not, do you know who your PO is? Privacy Officer Locator - must be on VA network to access.
   (ex., PO has seen the content but it is not approved)

   • Not yet. We have similar emails for 10-10EZ and 10-10EZR.
   • We have reached out to our Privacy Officer on 11/6 and they will be reviewing the template email.
     ​

10. Would you prefer to provide contact information for the recipients or would you rather VA Notify look this up for you by Veteran ID? If by ID, please let us know what identifier is used in your system.
    (ex., VAPROFILEID, PID, BIRLS, ICN, etc.)

• We will provide the email address that was entered for the Veteran when filling out the 10-10CG form
  ​

11. Do you currently capture communication preferences related to this notification? If so, please describe.
    (ex., opt in for claim status updates via email or text)

• No
  ​

12. What is the anticipated volume of notifications per day, week, month?

• These are very rare. Rarely more than a few a month, often none.
  ​

13. When does this notification need to be in production?

• Whenever possible. This is not urgent, but it is something that we've been wanting to have done for quite some time.

[kbelikova-oddball]

@hdjustice and @coope93 - intake review (aka kick-off meeting) scheduled for 12/03 at 3pm ET.

[hdjustice]

Great, thank you @kbelikova-oddball !

[kbelikova-oddball]

Service exists on the postal and users have been added to it.
10-10 Health apps team will work on the trigger for the notification and update Va notify with the proposed launch date.
Moving to In Progress.