Midpoint Review - IA Feedback - OCTO Health Apps, MHV Medical Records, After Visit Summary

[sterkenburgsara]

VFS actions

• [x] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • [x] If the Platform reviewer has any Thoughts/Questions that require responses.
  • [x] When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • [ ] When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• This is looking really great! I love the use of accordions here - they help tremendously to reduce cognitive load & cut down on the length of content upfront.
• I can't see URL determinations from Sketch files, so I am curious how we are handling the phased approach for this. Tagging @mnorthuis for input. Are we basing navigational components on Appointments page now, and issuing redirects/updating to MHV once that tool launches? // cc @kristinoletmuskat
• I'm curious to see how Veterans prefer the ordering of data within the AVS based on need. Do they want a digest of today's appointment first? Or is it more important to see information on next steps (new medications, where to get imaging done that was assigned during this appointment)? I think the questions in your Conversation Guide (Task 1) will get at this pretty well.

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• Should: Continue working with Sitewide CAIA and make sure sure you using the same field labels and language as the other MHV tools, particularly medical records.

• Consider: Within the "Your appointment on [date]" section there is an H2 called "procedures" that appears to contain historical (past) data about procedures. This is confusing. Consider moving any information that is not a direct output of the appointment out of this section to reduce user confusion, or update heading language to clearly indicate the timeframe the data represents (e.g. "today's vitals"; "past procedures"; etc.)

  • I'm not sure what the data limitations or constraints are for making changes in the content grouping this round, so this is just a points for consideration:

[kristenmcconnell]

We will definitely continue to work with CAIA. Our study should help answer some of our IA questions.

Good point about procedures. I'll look into the current system. @acrollet