Skip to content
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

Collaboration Cycle for [MHV Medical Records, Settings] #95082

Open
28 of 71 tasks
bryan-riley-va opened this issue Oct 16, 2024 · 7 comments
Open
28 of 71 tasks

Collaboration Cycle for [MHV Medical Records, Settings] #95082

bryan-riley-va opened this issue Oct 16, 2024 · 7 comments
Assignees
Labels
CAIA-Collab Collaboration Cycle intakes that require CAIA involvement cc-kickoff CC-Request Consolidated GitHub issue for Collaboration Cycle touchpoints collaboration-cycle For VSP Collaboration Cycle requests and improvements mhv-medical-records mhv-va.gov-medical-records midpoint-review Collaboration Cycle Midpoint Review PO-Sync-approved Collab Cycle PO Syn was approved by OCTO leads sitewide CAIA

Comments

@bryan-riley-va
Copy link
Contributor

bryan-riley-va commented Oct 16, 2024

Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.

VFS product information

VFS team name

vfs-mhv-medical-records

Product name

MHV Medical Records

Feature name

Settings

GitHub label for team

mhv-va.gov-medical-records

GitHub label for product

mhv-medical-records

GitHub label for feature

No response

Public DSVA Slack channel for VFS team

mhv-medical-records

Kickoff questions

Toggle kickoff questions

When did/will you start working on this product/feature?

Oct 2024

Will your work result in visible changes to the user experience?

Yes

Are you doing research with VA.gov users?

Yes

Will your work involve changes to...

Both

Does your work require non-trivial code changes or involve PII/PHI?

No

Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo?

No

Do you need to capture any additional analytics or metrics?

No

Will a VA editor (Drupal) notice this change?

Unsure

Product outline

TBD

Verify all relevant materials provided to Governance Team

  • I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product

Add the GitHub labels for your team, product, and feature to this ticket.

  • I acknowledge that I must add the GitHub labels for my team, product, and feature to this ticket.
    Kickoff Slack Thread with VFS team: Kickoff thread

Collaboration Cycle touchpoints

PO Sync

Toggle PO Sync instructions

Note: The PO Sync touchpoint is for OCTO teams only. Non-OCTO teams are welcome to participate if they choose.

Before the meeting

OCTO Product Owner
  • Review PO Sync Guidance to understand what this sync involves.
  • Schedule your PO Sync (with at least 2 business days lead time from now):
    • Open the Calendly PO Sync calendar
    • Select a date and time and click "Confirm"
    • Add your name and email
    • Click "Schedule Event"
  • Link all artifacts in the PO Sync artifacts for review section below at least two business days before the scheduled PO Sync. Please don't add artifacts in the comments section.

PO Sync artifacts for review
See guidance on PO Sync artifacts. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

Optional:

  • Any other artifacts you have so far
Governance Team actions
  • Meeting date/time: 11:00am ET - Tuesday, October 22, 2024

After the meeting

OCTO Design Leads
  • If the initiative receives OCTO alignment to proceed, add the PO-Sync-approved label to this ticket.
  • If the initiative does not receive OCTO alignment to proceed, comment and close this ticket.

Design Intent

Toggle Design Intent instructions

Before the meeting

VFS team actions
  • Review Design Intent Guidance to understand what this touchpoint involves.
  • Schedule your Design Intent (with at least 2 business days lead time from now):
    • Open the Calendly design intent calendar
    • Select a date and time and click "Confirm"
    • Add your name and email
    • Click "Add Guests" and enter the email addresses for VFS team attendees
    • Click "Schedule Event"
  • Link all artifacts in the Design Intent artifacts for review section below at least two business days before the scheduled Design Intent. Please don't add artifacts in the comments section.

Design Intent artifacts for review

See guidance on Design Intent artifacts. Governance Team feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

  • User flow

Not required, but nice to have:

  • Wireframes (if provided, must include mobile wireframes)

Optional:

  • Research plan
  • Any other artifacts you have so far
Governance Team actions
  • Design Intent Slack thread with VFS team
  • Meeting date/time:

After the meeting

Governance Team actions
  • Update this ticket with the Zoom recording
    • Recording link
    • Passcode:
  • Accessibility
    • Feedback added to milestone
    • No feedback
  • Design
    • Feedback added to milestone
    • No feedback
  • IA
    • Feedback added to milestone
    • No feedback
VFS team actions
  • Review feedback tickets. Comment on the ticket if there are any questions or concerns.

Architecture Intent

Toggle Architecture Intent instructions

Before the meeting

VFS team actions
  • Review Architecture Intent Guidance to understand what this touchpoint involves.
  • Schedule your Architecture Intent (with at least 2 business days lead time from now):
    • Open the Calendly Architecture intent calendar
    • Select a date and time and click "Confirm"
    • Add your name and email
    • Click "Add Guests" and enter the email addresses for VFS team attendees
    • Click "Schedule Event"
  • Link all artifacts in the Architecture Intent artifacts for review section below at least two business days before the scheduled Architecture Intent. Please don't add artifacts in the comments section.

Architecture Intent artifacts for review

See guidance on Architecture Intent artifacts. Feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

Platform Team actions
  • Meeting date/time: Thursday Nov. 7 at 2:30 pm ET

After the meeting

Platform Team actions
  • Update this ticket with the Zoom recording
    • Recording link
    • Passcode:
  • Engineering feedback
    • Feedback ticket attached to milestone
    • No feedback
  • Mobile Engineering feedback
    • Feedback ticket attached to milestone
    • No feedback
  • Security feedback
    • Feedback ticket attached to milestone
    • No feedback
VFS team actions
  • Review feedback tickets. Comment on the ticket if there are any questions or concerns.

Research Review

Toggle Research Review

VFS actions

Midpoint Review

Toggle Midpoint Review

Before meeting

VFS actions

Navigate to reference link: Midpoint Review Guidance

  • Schedule your Midpoint Review when ready:
    • Open the Calendly midpoint review calendar
    • Select a date and time and click “Confirm”
    • Add your name and email
    • Click "Add Guests" and enter the VFS meeting attendees email addresses
      • Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders
    • Click "Schedule Event"
  • Check this box if you'd like this review to be asynchronous (Please refer to the Midpoint Review guidance for the difference between a synchronous meeting and an asynchronous review)
  • Link all artifacts ONLY in the Midpoint Review artifacts section below at least two days before the scheduled Midpoint Review. Do NOT add artifacts to Comments section

Midpoint Review artifacts

See Platform guidance on Midpoint Review artifacts. Platform feedback is based solely on the artifacts provided, as reviewed during the two days before the Midpoint Review meeting. Any work not included in the artifacts below or any ongoing work taking place during the review period may not be reflected in that feedback.

Required artifacts

Not required, but nice to have artifacts

  • Accessibility annotations included as part of your design
  • Research plan
  • Links to specific CAIA artifacts:
  • Any other artifacts you have so far
Platform actions

After meeting

Platform actions
  • Accessibility
    • Feedback added to milestone
    • No feedback
  • Content
    • Feedback added to milestone
    • No feedback
  • Design
    • Feedback added to milestone
    • No feedback
  • IA
    • Feedback added to milestone
    • No feedback
  • Update this ticket with the Zoom recording
VFS actions
  • Review feedback tickets and comment on the ticket if there are any questions or concerns

Analytics Request

Toggle Analytics Request

VFS actions

Contact Center Review

Toggle Contact Center Review

VFS actions

Staging Review

Toggle Staging Review

The staging review for this ticket is consolidated and includes MR Download Records, View Radiology Images, and Settings. The review information can be found within the Download Records ticket which is: #92340

Privacy, Security, Infrastructure Readiness Review

Toggle Privacy, Security, Infrastructure Readiness Review

VFS actions

This product (MHV Medical Records) went through a prior Privacy/Security/Infrastructure readiness review as part of our original Phase 0 ticket. The application is now just progressing toward Phase 1 and this is a feature that is required for Phase 1. That ticket is linked for reference: https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/issues/1041

Per this conversation the review is considered completed: https://dsva.slack.com/archives/C01CJV0L9PS/p1731614506846179

Platform actions

  • Privacy, security, infrastructure readiness review is complete
@bryan-riley-va bryan-riley-va added CC-Request Consolidated GitHub issue for Collaboration Cycle touchpoints collaboration-cycle For VSP Collaboration Cycle requests and improvements sitewide CAIA mhv-va.gov-medical-records mhv-medical-records labels Oct 16, 2024
@humancompanion-usds
Copy link
Contributor

These changes are related to settings including controlling notifications. Medications and Secure messaging have some settings as they are already in phase 1. This work is growing the settings section. Profile team is doing the work.

Settings control:

  • Sharing medical information
  • How they want to receive notifications

Currently a private beta with trusted users only (phase 0).

@MarciMcGuire MarciMcGuire self-assigned this Oct 22, 2024
@humancompanion-usds humancompanion-usds added the PO-Sync-approved Collab Cycle PO Syn was approved by OCTO leads label Oct 22, 2024
@JonathanKamensDVA
Copy link
Contributor

I don't see the arch intent documentation linked above. If I'm not missing it, then just a reminder that it needs to be linked here by 2:30 tomorrow US/Eastern or we will need to reschedule the A/I meeting. Thanks!

@DonMcCaugheyUSDS
Copy link
Contributor

Arch Intent meeting document is here.

Feedback from the arch intent meeting:

  • please complete API documentation for your new API endpoints
  • please make sure to set up necessary monitoring for new API endpoints

Thank you!

@NaomiPMC
Copy link

@aprocik1 to confirm with @laurwill content involvement in this ticket.

@aprocik1
Copy link
Contributor

Note re. CAIA content involvement: Laura is involved in drafting and reviewing most of the content within the health portal on VA.gov. She regularly collaborates with the MHV and other health portal teams on an ongoing basis. She can help answer content questions and incorporate content feedback from governance.

@bryan-riley-va
Copy link
Contributor Author

Checked off the contact center review as they have completed reviewing the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CAIA-Collab Collaboration Cycle intakes that require CAIA involvement cc-kickoff CC-Request Consolidated GitHub issue for Collaboration Cycle touchpoints collaboration-cycle For VSP Collaboration Cycle requests and improvements mhv-medical-records mhv-va.gov-medical-records midpoint-review Collaboration Cycle Midpoint Review PO-Sync-approved Collab Cycle PO Syn was approved by OCTO leads sitewide CAIA
Projects
None yet
Development

No branches or pull requests

9 participants