Description
Product Outline
18F Hypertension Fast track team needs advice from vets-api to add on their new hypertension fast track expedited claim processing into the existing 526 claim submission backend workflow
High Level User Story/ies
As a 18f hypertension fast track developer, I need to understand the current 526 claim submission process so I can intercept incoming 526 claim submissions and assign the new "RDD" special issue to the claim if the claim is a single issue increase only hypertension(7101) with appropriate medical reports available. Also, since I have limited access to VA backend systems, I will need help testing in staging.
Hypothesis or Bet
If we intercept incoming claims and assign the new RDD special issue to the claim then we expect these claim to be processed faster.
OKR
Which Objective / Key Result does this epic push forward?
Getting the Hypertension fast track code into master and tested in staging with a staging user that create a single issue increase only claim. Confirm the hypertension code works as expected, does not impact the current 526 submission adversely and evss accepts claims with RRD special issue.
Definition of done
What must be true in order for you to consider this epic complete?
An incoming single issue hypertension claim submission has the RRD special issue assigned and EVSS accepts the claim as valid. The new code should ignore 526 claims that don't meet the FastTrack requirements.
How to configure this issue
- Labeled with Team (
product support,analytics-insights,operations,tools-be,tools-fe,content-ia,service-design,vsa-*) - Labeled with Practice Area (
backend,frontend,devops,design,research,product,ia,qa,analytics,contact center,research,accessibility,content)
Activity