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

Service Options / Modalities MVP #14683

Closed
davidmpickett opened this issue Aug 7, 2023 · 2 comments
Closed

Service Options / Modalities MVP #14683

davidmpickett opened this issue Aug 7, 2023 · 2 comments
Labels
Content model [CMS feature] The bones of the CMS Content CMS team practice area Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Lighthouse Facility API Data source/destination for many Facilities team products Regional office CMS managed VBA product owned by the Facilities team UX VAMC CMS managed product owned by Facilities team

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Aug 7, 2023

Background

One of the new features we are planning to explore in the VBA Regional Office MVP is adding the concept of service modalities / delivery methods to the existing service location pattern.

When we built the service location model for VAMCs, it was mostly meant to support multiple physical locations for a given service within that facility.

However, from VBA research we know that there are few (if any) tasks that require a Veteran to be physically present.

We also know from our partners at VAMCs that the current model doesn't align perfectly with the reality of their services.

  • Currently, Telehealth is listed as its own service in the service taxonomy.
  • Home-based care is another service modality that exists

Other possible service modalities / options

  • Submit by mail
  • Submit by Fax (for NCA)
@davidmpickett davidmpickett added VAMC CMS managed product owned by Facilities team Epic Issue type Content model [CMS feature] The bones of the CMS Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team Content CMS team practice area Vet Center CMS managed product owned by Facilities team Lighthouse Facility API Data source/destination for many Facilities team products Facility Locator product owned by Facilities team VA services taxonomy CMS-managed product owned by the Facilities team labels Aug 7, 2023
@davidmpickett
Copy link
Contributor Author

Adding this slice of the VBA Services doc source of truth for future reference
Service Delivery Options.xlsx

@davidmpickett davidmpickett changed the title Supporting Service Modalities / Delivery Methods across Facilities products Supporting Service Delivery Options across Facilities products Nov 3, 2023
@davidmpickett davidmpickett changed the title Supporting Service Delivery Options across Facilities products Service Delivery Options MVP May 1, 2024
@davidmpickett davidmpickett removed Needs refining Issue status Vet Center CMS managed product owned by Facilities team VA services taxonomy CMS-managed product owned by the Facilities team labels May 1, 2024
@davidmpickett davidmpickett changed the title Service Delivery Options MVP Service Options / Modalities MVP May 1, 2024
@davidmpickett
Copy link
Contributor Author

Service Options MVP is in PROD!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content model [CMS feature] The bones of the CMS Content CMS team practice area Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Lighthouse Facility API Data source/destination for many Facilities team products Regional office CMS managed VBA product owned by the Facilities team UX VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

1 participant