Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saipan Benefits offices have no representation in Facility Locator #12112

Closed
1 of 11 tasks
davidmpickett opened this issue Dec 23, 2022 · 11 comments
Closed
1 of 11 tasks

Saipan Benefits offices have no representation in Facility Locator #12112

davidmpickett opened this issue Dec 23, 2022 · 11 comments
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team sitewide VBA for VBA facilities that are not Regional Offices

Comments

@davidmpickett
Copy link
Contributor

Description

As a VA beneficiary in the Northern Mariana Islands, I want to find information about VA benefits offices located in Saipan by using the Facility Locator on VA.gov.

Searching for VA Benefit offices in this area yields no results:
saipan.png

Currently the information about the Saipan benefit offices is only listed on the front page of the Honolulu Region Office teamsite

honolulu.png

Acceptance Criteria

  • Testable_Outcome_X
  • Testable_Outcome_Y
  • Testable_Outcome_Z
  • Requires design review

CMS Team

Please check the team(s) that will do this work.

  • Program
  • Platform CMS Team
  • Sitewide Crew
  • ⭐️ Sitewide CMS
  • ⭐️ Public Websites
  • ⭐️ Facilities
  • ⭐️ User support
@davidmpickett davidmpickett added Facility Locator product owned by Facilities team Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team VBA for VBA facilities that are not Regional Offices Facilities Facilities products (VAMC, Vet Center, etc) labels Dec 23, 2022
@davidmpickett
Copy link
Contributor Author

The narrow issue here is resolving this for Saipan.

The broader issue here is understanding the scope of the use case for representing locations where VA benefit services are offered that are not official VA facilities

@swirtSJW
Copy link
Contributor

swirtSJW commented Dec 23, 2022

This looks like the case of having a VBA representative/provider assigned to a VHA facility, but no VBA facility reference in VAST (even as a co located facility).

@swirtSJW
Copy link
Contributor

Since this is all coming from "Sandy's Database that @davidconlon is maintaining it may just be that it was never added and needs to be.

@JQuaggles
Copy link

I don't think this is a FL locator issue though, but rather that this location is not a permanent facility and just what seems like 1 person? If you look at say Newington Regional Office, they have a benefits office located at the Medical Center (according to their current website) (West Haven VA Medical Center, 950 Campbell Ave. (BLDG 1, RM G197) West Haven, CT 06516) - but it is not considered a satellite office where it would appear within Facility Locator. Whereas Providence actually has a listing for the Benefits Satellite Office at the Providence VAMC.

So it's not just unofficial VA locations, but also other VA locations where they potentially have a benefits office there that might be missing from FL?

Seems like as we look at VBA Facilities pages, it might be good to discuss these types of things too. We want to make sure there is consistency.

@davidconlon
Copy link
Contributor

@JQuaggles - @swirtSJW is correct.
There is going to misalignment between what is on the teamsite pages and what is in 'Sandy's' database until we replace the DB with Drupal.
We performed a data call last year but that does not mean that the data is current in either the database or the website.
I also note that the website Last updated: December 16, 2022 so the request to add this content to Sandy's DB may not have occurred yet.

Regardless, the path forward on this is to escalate this content to Tanekwa in VBA and possibly OFO so that we can validate that this is a facility and get the appropriate data into Sandy's DB so that it populates correctly into Facilities API.

@JQuaggles
Copy link

Thanks @davidconlon - so we will want to ensure:

  • Regional Office facility locations
  • Confirmed VA Satellite locations
  • Other potential non-VA office located Satellite locations

What I was asking not very concisely is wanting to make sure that we understand what would be considered a satellite location that requires a facility within FL vs a location that a Regional Office sends someone to on a consistent basis (VA or not) but is not considered a satellite/full time location. (Similar to how we look at the other location types for VCs)

But definitely agree to the escalation as well.

@davidconlon
Copy link
Contributor

VBA Facilities Data Call Instructions 1.0.pdf
This may provide additional insight.
"Satellite" is all of the above. There is currently no sub-definition per OFO.

@kmariepat-cityfriends
Copy link

Next Steps:

  • this is a data quality issue, @davidconlon to reach out to Hawaii to prompt them to review their data

@davidconlon
Copy link
Contributor

Email sent to Eileen Asing for data update call.

@davidmpickett davidmpickett added Blocked Issues that are blocked on factors other than blocking issues. and removed Needs refining Issue status labels Apr 18, 2023
@davidconlon davidconlon removed the Blocked Issues that are blocked on factors other than blocking issues. label Apr 20, 2023
@davidconlon
Copy link
Contributor

Facilities added to VBA_facilities DB on 4/19. Populated in Drupal via nightly migration on 4/20. COVID facility statuses added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team sitewide VBA for VBA facilities that are not Regional Offices
Projects
None yet
Development

No branches or pull requests

6 participants