-
Notifications
You must be signed in to change notification settings - Fork 209
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
Comments
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:
Currently a private beta with trusted users only (phase 0). |
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! |
Arch Intent meeting document is here. Feedback from the arch intent meeting:
Thank you! |
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. |
Checked off the contact center review as they have completed reviewing the ticket. |
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
Add the GitHub labels for your 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
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:
Governance Team actions
After the meeting
OCTO Design Leads
Design Intent
Toggle Design Intent instructions
Before the meeting
VFS team actions
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:
Not required, but nice to have:
Optional:
Governance Team actions
After the meeting
Governance Team actions
VFS team actions
Architecture Intent
Toggle Architecture Intent instructions
Before the meeting
VFS team actions
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:
https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/platform/engineering/collaboration-cycle/architecture-intent/checklist/mhv-medical-records-settings-11072024.md
Platform Team actions
After the meeting
Platform Team actions
VFS team actions
Research Review
Toggle Research Review
VFS actions
Midpoint Review
Toggle Midpoint Review
Before meeting
VFS actions
Navigate to reference link: Midpoint Review Guidance
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
Platform actions
After meeting
Platform actions
#qTwj2L6
VFS actions
Analytics Request
Toggle Analytics Request
VFS actions
Contact Center Review
Toggle Contact Center Review
VFS actions
Contact Center Review for [MHV Medical Records Phase 1 Launch (Download All, Radiology Images, Settings)] #97364
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
The text was updated successfully, but these errors were encountered: