-
Notifications
You must be signed in to change notification settings - Fork 70
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] VBA services (batch 2) to Service Taxonomy #16269
Comments
Capturing VBA and Taxonomy Council input to date
|
Moved Medical records to #16463 because it is an update of existing term not an addition |
@mmiddaugh @aklausmeier @xiongjaneg Potential ticket for me to take on in sprint 100 /101 depending on priority. I separated out the list in the main description to focus on the 8 terms that seem to have consensus (though I will need to wordsmith some of them.) Shifted a couple terms to other tickets based on feedback here and in Sharepoint doc. |
@mmiddaugh Want to clarify this comment. Is this saying that Grief and bereavement should not be listed as a VBA service, or simply pointing out that it would be an UPDATE to an existing term rather than a net ADDition? |
@davidmpickett good question about Grief and bereavement - apologies for not being more clear.
|
@mmiddaugh Awesome, thanks for clarification. I'm splitting that off into a separate issue: #16503 I also just created a new issue template to GitHub to handle this type of Taxonomy work. Also covers Medical Records |
Health Service API IDs - unmatched
Health Service API IDs - Matched to a term in Drupal
|
@davidmpickett based on most recent RO conversations, here are the revised descriptions for the pending service taxons. I think they're ready to be added and reviewed by CAIA. Disability Compensation, Pre-discharge claims, and Appeals
Pre-discharge claims
Disability compensation
Returning service member care and Transition assistance
Returning service member care
Transition assistance
|
@mmiddaugh Just making some additional notes on this now for sake of thoroughness.
P12 - "There is only one person in our office that does that [IDES].... [Service Members might visit the RO] if they wanted to meet with that person [but would likely schedule that meeting directly]." P9 - "I supervise the Military Specialist Coordinators that do the IDES but that is separate from Public Contact... IDES is completely different, and not something that I, personally, think should be on the website." |
@xiongjaneg @jilladams - This ticket will likely roll over the sprint boundary but should be closed next week. I just remembered that Monday is a holiday. That plus my sick days and other tickets taking priority means it won't quite hit the sprint report. |
EASY PEASYThese labels were copy-edited and approved by CAIA in the summer round of feedback. VBA stakeholders have confirmed these as core services and agree on the names.
THINKY SLINKYThese names have changed since the last CAIA review. We may want to get their review before adding to Drupal. Some of these were changed based on VBA stakeholder feedback. Others were changed based on usability testing findings.
|
End of sprint 101 update
For sprint 102
|
Terms to add to the Service Taxonomy and save as Draft
|
Made good progress on sub fields today. Also messaged CAIA on slack to ask how they want to get notified when stuff is ready for more input. |
DRAFT request to CAIA department-of-veterans-affairs/va.gov-team#74390 |
My work on this is complete, pending final feedback and direction on what to send to CAIA from @mmiddaugh. This is on the agenda for UX sync tomorrow. FYI @jilladams @xiongjaneg I made the ACs more specific |
Follow on ticket: #17046 Slack thread: https://dsva.slack.com/archives/C0FQSS30V/p1706220664151049?thread_ts=1706219966.668729&cid=C0FQSS30V
@xiongjaneg @mmiddaugh we ok to close this, knowing the follow up on approvals will happen in the other ticket? |
There was one batch of terms that were partially drafted in this ticket (I gave them new labels), but aren't quite ready to send to VBA (they haven't been added to Drupal and had additional fields drafted). During this week's UX Sync, we clarified that these "Thinky Slinky" terms did not need sign off from CAIA on the updated labels before being adding to Drupal. I cut a new ticket to do the follow up work that would get them to VBA readiness: |
Now we should be good to close this ticket with follow up work & approvals both tracked |
Which Taxonomy is this term for?
VA services taxonomy
Proposed terms
Veteran profile informationFinancial servicesBurial in a VA cemetery*Suggesting this as best fit for mapping the legacy Facilities API ID, even though it isn't perfect
Rejected terms
Does this overlap with any existing term in the taxonomy?
No
Rationale for adding this term
Follow up from batch 1
Which products will this term impact?
VBA Regional Office
Have stakeholders from impacted products been consulted?
Yes
Have you drafted content for all the relevant subfields?
Acceptance Criteria
End of sprint 101 update - 2 points
Sprint 102 - 3 points
The text was updated successfully, but these errors were encountered: