Change management / launch for Register for Care, Medical records, and Billing and Insurance

[kevwalsh]

The change represented by epic #3151 will standardize the following pages to ensure consistency, quality, and semantic content across VAMCs:

• Billing and insurance
• Medical records
• Register for care

1. Describe the change from the perspective of VA employees, in plain language. What is the employee going to experience with this change? To create the new top task pages, editors will need to add information about these services (like locations and hours) to the new pages in the CMS.

2. Explain why the change is necessary from a CMS/platform and project goal perspective. Link to screenshots if that helps tell the story. Three new content types for what we call "Top task" pages in the VAMC product: Billing and insurance, Medical records, and Register for care. Previously, this content was housed in general-purpose Benefit Detail Pages. The new pages use a mix of structured local content and nationally standardized content to give Veterans a consistent experience across all VAMCs.

3. Select the role(s) impacted by the change.

• [ ] All CMS users
• [ ] All CMS editors
• [ ] Vet Center editor
• [x] VA Medical Center editor
• [ ] VA Outreach Hub editor
• [ ] VA Benefits Hub editor
• [ ] Campaign landing page editor
• [ ] VA Resources and Support editor
• [ ] Offices editor
• [ ] Supporting roles such as CMS account admin, Facilities or Public websites team member

4. How will success be defined for this change? All 140 VAMCs have adopted the new top task pages.

5. How will success be measured for this change (audit, survey, other types of research, etc.)? VHA will have a dashboard to monitor which VAMCs have adopted the new pages.

6. Does the change require new or updated:

• [x] Knowledge Base article(s) If existing articles, list URLs:
• [ ] Training video(s) If existing videos, list URLs:
• [x] CMS UI support

7. Will the change be tested with users before release?

• [x] Yes
• [ ] No

8. Are there any known dependencies? Front-end

Question for discussion: Do we autogenerate non-clinical service nodes?

• Pros: Experience is more complete from the beginning
• Cons: Editors are not forced to think through the content creation.
• Decision: Don't create them

Sprint 50

• [x] Finish UX for Top tasks

Sprint 51

• [x] #6882
• [x] #6883 (jane)
• [x] Further Develop change management approach (Airtable)
• [x] First on a Tugboat environment (feature branch?)
  • [x] Merge PR for #7551 which will grant permissions
  • [x] Merge PR #7421 which will generate 420 nodes and menu items
  • [ ] Merge #6272, #6273, #6274
  • [ ] Smoke test with
  • [ ] Run through chanagement script

Sprint 53

Beta test

• [x] Plan beta test with a small group of editors with different skill levels and familiarity with CMS

Sprint 54

Beta test

• [x] Launch beta test

Sprint 55

Beta test

• [x] Collect and analyze results

Launch!

From the editor's perspective

• Find out
  • about these new pages
  • what to do there
  • WHY, tell and teach
  • how long this task will take
  • (links to training, Knowledge Base articles) (from whom, VHA DM)
• Find the content (go to your section and filter for each content type)
• Review and edit top task and add service locations
• Publish the new content (which will automatically archive old content)

[cmaeng]

@ContentBrewmaster , not a huge deal but standard practice is to keep epics that are in progress in the "Epics in progress" column/pipeline. if putting in "In progress" instead helps you organize your work, let's discuss.

[ContentBrewmaster]

NP, moved back to Epics in progress.

On Fri, May 6, 2022 at 10:01 AM Clarence Maeng @.***> wrote:

@ContentBrewmaster https://github.com/ContentBrewmaster , not a huge deal but standard practice is to keep epics that are in progress in the "Epics in progress" column/pipeline. if putting in "In progress" instead helps you organize your work, let's discuss.

— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-cms/issues/6881#issuecomment-1119655996, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV6HVTWA4UELQU26RAK22L3VIUQ4FANCNFSM5HI7JLTA . You are receiving this because you were mentioned.Message ID: @.*** com>

-- Denise Eisner

she / her

Content Strategist

civicactions.com http://www.civicactions.com/ | @civicactions https://twitter.com/civicactions