search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
97 stars 69 forks source link

Update content for Get Medical Records detail page (react widget) #9387

Closed wesrowe closed 2 years ago

wesrowe commented 2 years ago

Description

A lot of the content on this page is hard-coded inside a react widget. That content is being updated by the SW Content team and needs to be live by July 1.

Per @RLHecht, 6/29 (Slack):

We are going to hold off on publishing these Medical Records pages tomorrow. Our VA partners would like us to wait for people from DoD to weigh in on their page and we won't hear back from them in time for this to be completed tomorrow. Rather than making changes to these pages twice, we will publish all at once when we get the go-ahead next week. As soon as I hear from them and know whether we'll have changes you'll need to make in these files, I'll let you know. In the meantime, I'll keep commenting in the ticket for the work Allison is currently doing in this. Thanks so much for your flexibility with this. FYSA

Acceptance Criteria

CMS Team

Please check the team(s) that will do this work.

wesrowe commented 2 years ago

per @davidconlon this will be a sprint goal for sprint 61

allisonlu commented 2 years ago

@wesrowe @jilladams can you remind me where the new content is?

jilladams commented 2 years ago

@wesrowe I think the content we're talking about is the 'Main "Get your records" page' content mentioned here, https://github.com/department-of-veterans-affairs/va.gov-team/issues/41796#issuecomment-1152789350 , but I don't see that Danielle has signed off on it yet. Do you have notes somewhere about another source for final copy? (Added a note on that ticket for Danielle as well, to check, since you're OOO for a little this morning.)

jilladams commented 2 years ago

@RLHecht confirmed in Slack that she has the content and will add it here.

RLHecht commented 2 years ago

@jilladams Here is the non-Cerner content. Just note that there may be changes from stakeholders. We gave them 6/21 as a deadline and haven't heard back. I followed up today. The one section that you'll see still has a question for stakeholders could be published as is and we could always make changes afterward (though I know that's not ideal since we need to send this to you again).

Get your medical records_Non-Cerner version_for SME team.docx

I will post the Cerner version in a bit but waiting on a cleaned up version of it.

RLHecht commented 2 years ago

@jilladams Here is the Cerner version of content to use. We've now gotten some feedback from stakeholders for the page above as well, but I can't promise we won't have more. I'll let you know as soon as we do. There are few notes in the word doc for your team. The pages we are linking to in R&S aren't live yet. These will all be going live together. Get.your.medical.records_Cerner.version_for PW (1).docx

Here is a newer version of the non-Cerner version: Get.your.medical.records_Non-Cerner.version_for.SME.team.docx

jilladams commented 2 years ago

Thanks! Content is now final. I'm going to unassign Allison here, to make clear that whoever has capacity first on Front end can pick this up, until she's back from being sick, since it's a sprint goal.

jilladams commented 2 years ago

Code treats the distinctions as:

Copy does:

In this case: non-Cerner / unauthed are synonymous. That's not always true.

Our test users aren't working today. WOrking with Allison on a TUD user, and will ping Anthony if none work.

SHipping: R&S articles must be published before we ship, to prevent broken links. Randi will manage publishing, but we need to notify her when we're ready to merge, so she can publish. Should target merge after 29th daily deploy, for deploy on the 30th.

allisonlu commented 2 years ago

PR opened: https://github.com/department-of-veterans-affairs/vets-website/pull/21510

I've added the DO NOT MERGE label so we can make sure it gets deployed on the 30th (and not before)

allisonlu commented 2 years ago

Caveats:

jilladams commented 2 years ago

Nice! And we still don't have a means of getting eyes on the Cerner version in staging, without a test user, correct?

jilladams commented 2 years ago

Cerner testing was done - disabling CORS browser setting enabled using TUD users, and screenshots are added to the PR.

This ticket will cross sprint boundary due to publishing delay from Sitewide Content, signed off by Dave in Slack.

jilladams commented 2 years ago

@RLHecht do you have any info about the possible timeline for publishing these changes?

RLHecht commented 2 years ago

Unfortunately we're still in a holding pattern waiting for the go-ahead from stakeholders. We haven't gotten approval yet to publish one of the pages we are linking too from this medical records page. As soon as I hear something I will let you know. Is everything now set on your end for when we are ready? I know there was still an issue with one part of the dynamic content.

jilladams commented 2 years ago

Yes, content is ready to merge/deploy when we get the greenlight, with the exception of dynamic facility name. That requires a bigger technical lift because the content here is all hard-coded. We've ticketed discovery around whether / how to do this under https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9854.

jilladams commented 2 years ago

Ticket is unblocked, added to Sprint 65, notes on https://github.com/department-of-veterans-affairs/vets-website/pull/21510#issuecomment-1212364288.

allisonlu commented 2 years ago

Get Medical Records page is now live on prod!

https://www.va.gov/health-care/get-medical-records/