Caseflow: Case details | Add POA address

[laurjpeterson]

We want to show the Power of Attorney address in Case details to help BVA dispatchers (and likely other BVA staff) complete tasks that require mailing to an appellant's POA.

Mocks

• https://github.com/department-of-veterans-affairs/caseflow/issues/6812#issuecomment-419995260

AC

• POA address from BGS exists in the POA section of Case details

[allyceh]

Adding what we've learned about POA to date. @laurjpeterson @amprokop , please confirm. cc: @sneha-pai @mkhandekar for design feedback.

What we know about POA:

• POA name and address for private attorneys: Lives in BGS
• POA name and address for VSOs: POA name lives in BGS, address pulled into the IDT and populated on decision letters lives in VACOLS
• POA info that lives in BGS must be edited in Share by someone who has admin access.

Below are some mocks of how POA could look in Case Details.

1) POA fields for private attorneys:

2) POA fields for VSOs:

[mkhandekar]

Just a quick question, why is the first part of these sentences different?

To update POA name and address

If the POA is incorrect?

[amprokop]

What about cases with multiple POAs, or cases with more than one claimant with different POA? Are we going to wait on designing that?

Eventually we'll have to transition to some model where POA is noted along with the person if there is more than one claimant— ok if we're saving that for later.

[laurjpeterson]

@amprokop - tracking showing multiple POA in this github issue - https://github.com/department-of-veterans-affairs/caseflow/issues/5589. We have early sketches, but we did deprioritize incorporating the POA exceptions after we chatted with Shane about how Caseflow Intake might be the source of these POA exceptions, so we don't have data as we'd use it just yet

[allyceh]

@mkhandekar I updated the verbiage to be more consistent and made it more concise (see below).

@laurjpeterson , if there is no additional feedback and given our October scope, these feel ready for development.

[laurjpeterson]

Looks good to me!

[mdbenjam]

Do we want to show the representative type? We currently do this (Attorney, VSO, etc.) or is that not needed.

[allyceh]

@mdbenjam I feel like that would be helpful. I am assuming we are able to clearly distinguish between private attorneys and VSOs. How about this, below:

I removed the word "representative". I don't think we are losing anything by not having this since we have the Power of Attorney label above.

cc design team : @sneha-pai and @mkhandekar

[mdbenjam]

@allyceh Cool, I think we should also distinguish between attorney and agent. So how about these options:

Private Attorney
Private Agent
Veteran Service Organization <- also we could split these into Local/Regional Organization, State Organization, and National Organization if that's useful.

[mdbenjam]

Actually it looks like we already have this mapping in the code:

"POA Attorney" => "Attorney",
"POA Agent" => "Agent",
"POA Local/Regional Organization" => "Service Organization",
"POA State Organization" => "Service Organization",
"POA National Organization" => "Service Organization"

I'm going to keep using these on the right hand side. Omitting Private and Veteran for now for consistency. We can change this mapping if we want to make the change application wide.

[allyceh]

@mdbenjam For legacy and AMA appeals in Caseflow, is the POA data source BGS? Or, does the legacy POA come from VACOLS?

@laurjpeterson and I are looking to clarify.

[mdbenjam]

POA comes from BGS for AMA and VACOLS for legacy. At least for now. I'd like to eventually pull everything from BGS.

[laurjpeterson]

Ticket to add POA from BGS for legacy appeals - https://github.com/department-of-veterans-affairs/caseflow/issues/5601