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

[ADD] VA police to VA Service Taxonomy #16811

Open
6 tasks
davidmpickett opened this issue Jan 10, 2024 · 4 comments
Open
6 tasks

[ADD] VA police to VA Service Taxonomy #16811

davidmpickett opened this issue Jan 10, 2024 · 4 comments
Labels
Content CMS team practice area Drupal Site Building For tasks that require Drupal Admin access, but don't require updating code or making a PR product VA services taxonomy CMS-managed product owned by the Facilities team VAMC police transparency Sub-product of VAMC

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Jan 10, 2024

Which Taxonomy is this term for?

VA services taxonomy

Proposed term name/label

VA police

Proposed machine name/ API ID

va_police / VApolice

Does this overlap with any existing term in the taxonomy?

No

Rationale for adding this term

Based on content model in #16415

Which products will this term impact?

VAMCs

Have stakeholders from impacted products been consulted?

No

Have you drafted content for all the relevant subfields?

  • Show for VAMC Facilities:
  • Type of Care: Non-clinical services

Acceptance Criteria

  • Term is reviewed by relevant taxonomy governance body
  • Term is either approved for addition, or denied with an explanation
  • If approved, a Drupal admin from Product team may add the term to the taxonomy
  • Content for subfields is drafted in Drupal by Product team
  • (List any necessary review and approval steps here)
  • Term is published
@xiongjaneg
Copy link
Contributor

From Michelle: Will editors be prevented from adding this term to their health services?

From Dave: There are filtered lists and a check box that says which type of service this can be added to. Depending on how we implement this non-clinical service, there could be other fields. Currently, like for billing, we don't show Description but we could, it is an option. Dave is working in this sprint on a content spec model.

@davidmpickett davidmpickett removed the Content governance [CMS feature] Content ownership label Jan 29, 2024
@davidmpickett davidmpickett added the Drupal Site Building For tasks that require Drupal Admin access, but don't require updating code or making a PR label Feb 9, 2024
@davidmpickett
Copy link
Contributor Author

@xiongjaneg Likely candidate for a future sprint as it blocks #16813, but is pretty straightforward itself

@mmiddaugh
Copy link
Contributor

@davidmpickett is any work remaining on this one?

@davidmpickett
Copy link
Contributor Author

@davidmpickett is any work remaining on this one?

I just downgraded this to a 1 pointer since it's just adding a single term to the Taxonomy. We have not done this yet because the expanded contact information model for VA Police stalled.

If there was any centralized information that we wanted to inject, then this could be a little bit more of a lift, but otherwise this will just be identical to Billing and Insurance/ Medical Records/ Register for Care and could be a 0-pointer that you do in a few minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content CMS team practice area Drupal Site Building For tasks that require Drupal Admin access, but don't require updating code or making a PR product VA services taxonomy CMS-managed product owned by the Facilities team VAMC police transparency Sub-product of VAMC
Projects
None yet
Development

No branches or pull requests

3 participants