-
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
Review of new or updated KB article : VAMC and VBA Service Locations and appointment information #16156
Comments
This is the main article that will need to be updated. This is where there will be the most obvious changes. In addition, these three pages should be reviewed for edits. They all reference the process of creating a VAMC Facility non-clinical service. The non-clinical services will now have some new options that didn't exist previously. It also might be worth considering breaking off "how to add or edit a VAMC Facility non-clinical service" into a new article that all three of these article reference, rather than having all the steps related to non-clinical services repeated in three separate articles. |
@jilladams For your reporting, Dave's 2 points on this ticket can be considered done. The rest is my work and then sending it to CMS Team for review. |
@xiongjaneg Perfect, thx - I revised the ACs area in such a way that I'll remember this in reporting, but feel free to modify that if you have any concerns about how that's now framed. |
edits made to health service and submitted to VHA DM for review, once approved will copy to other articles |
approved by VHA DM with addition of images |
@xiongjaneg can this one be closed out? Or the copying to other articles is still outstanding? |
@jilladams Yes, I added an AC, they need copying and publishing timed along with launch. |
@xiongjaneg sorry to be obtuse, just making sure I know which launch -- is that with Service Location launch, yes? |
Not obtuse at all, I updated the title and description to be more clear that this is related to Service Locations |
Moving this to Complete Pending Integration to reflect that there will be steps for this during the VAMC/VBA service location launch but otherwise is done |
Hey @xiongjaneg I was able to pretty easily find the draft revisions that will need to be published for three of the four articles
But I'm having trouble finding a straightforward draft revision for How to add or edit a VAMC facility health service that's ready to publish. Looks like you had one ready to go, but then the Mental Health phone number changes came in and knocked it out. Can you identify/create a draft revision that's ready to launch? |
@davidmpickett Yeah, the timing was tough on that one. The last draft before mental health number updates is this one: https://prod.cms.va.gov/node/23473/revisions/846911/view The one line about mental health number logic will need to be added to line 18: Mental health service contact information: When the Use the general facility phone number checkbox is selected, the number displayed to Veterans will be the mental health number specified for your facility, rather than the main facility number. |
Okay I think I got it :) There was one other minor change in an early paragraph I needed to add as well to get a new draft revision lined up with the current state + your earlier draft. Now is ready for launch again |
I had to update one image in one KB |
Which article(s) need review?
Any article related to Service Locations and appointment information that will be affected by #14837
Working document of appointment changes
Provide the link to latest revision of each article that requires review.
Priority or deadline for request
Choose either Deadline or a priority:
Can article(s) be published?
Once the article has been fully reviewed, can the article(s) be published? For example, is anything tied directly to an upcoming feature and this information should not be published until the feature is on production?
Acceptance Criteria - Sprint 98 (2 points)
Product tasks
The text was updated successfully, but these errors were encountered: