xiongjaneg
commented
10 months ago Problem to solve
Legislation passed in 2022 requires VAMC websites to include data about VA police activity. Deadline: One year after the enactment (December 29, 2022), the Secretary shall report to Congress on the implementation of all provisions of amendments to 38 USC 902, which includes the publishing of arrest and ticketing data.
Initiative Brief: VA police transparency (WIP)
Background
Cleland Dole Act Sec 405 legislation passed in 2022
“(e) (1) The Secretary shall publish on the internet website of each facility of the Department the following information with respect to the facility: “(A) Summaries and statistics covering the previous five-year period regarding— “(i) arrests made by and tickets issued by Department police officers; “(ii) prosecutions, ticketing, and other actions relating to such arrests; “(iii) the use of force and weapons discharge by Department police officers; and “(iv) complaints, investigations, and disciplinary actions regarding Department police officers. “(B) Contact information for employees of the Department and the public to directly contact the police force of the facility, including for an individual (or the representative, attorney, or authorized agent of the individual) to request information regarding the arrest, ticketing, detainment, use of force, or other police matters pertaining to that individual. “(2) The Secretary shall ensure that each police force of a facility of the Department is able to provide to an individual who contacts the police force pursuant to paragraph (1)(B) the information described in such paragraph.”.
Information on data source (from Jeffrey Steidler, 7/26)
- The current system is Report Exec, from Omnigo Inc which will be replaced by a newly procured system to be implemented ~October 1, 2023. The new system will have advanced capabilities to track and trend data, with easy data exporting in a Power BI Dashboard format. VA will have the ability to analyze data in a ways we previously could not, including improved demographic data collection, and location mapping. It includes automatic exporting of required data points to the FBI (National Incident Based Reporting) which is legislatively mandated and will allow us to publish data in compliance with the Cleland Dole Act.
- Existing data will need to be scrubbed for quality so we should not expect to have access to historical data. 5 year data request can be fulfilled going forward.
- Phase 1 - Oct 1, 2023 - March 30, 2024 - VA police use new system as reporting tool of record and data from legacy system is scrubbed and migrated
- Phase 2 - begins April 1, 2024 - API to be available
Meeting with vendor for questions and insight into data export options to be scheduled.
Web presence on VA.gov Departments: VA police
jilladams
it-harrison
VFS product information
VFS team name
Sitewide - Facilities
Product name
VA Medical Centers
Feature name
Police Transparency
GitHub label for product
VAMC
GitHub label for feature
No response
Public DSVA Slack channel for VFS team
sitewide-facilities
Kickoff questions
Toggle kickoff questions
### When did/will you start working on this product/feature? July 12, 2023 ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? Unsure ### Will your work involve changes to... Tools, applications and dynamic pages -> will be added to existing VAMC modernized pages ### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo? Yes -> Content KPI ### Do you need to capture any additional analytics or metrics? Yes ### Product outline - [Initiative Brief: VA police transparency](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/facilities/medical-centers/police/readme.md#initiative-brief-va-police-transparency-wip) - [Epic VA Police Transparency MVP #14327](https://app.zenhub.com/workspaces/sitewide-facilities-639f5253e4b702a32376339e/issues/gh/department-of-veterans-affairs/va.gov-cms/14327) ### Verify all relevant materials provided to Governance Team - [X] I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product ### Notify the Collaboration Cycle team of this ticket in your team's public Slack channel. - [X] I acknowledge that I must notify the Governance team by completing the collab cycle kicckoff workflow in my team's Slack channel after submitting this issue. This can be completed by typing "/collab cycle" and selecting the appropriate workflow. Kickoff Slack Thread with VFS team:: https://dsva.slack.com/archives/C0FQSS30V/p1694034763751069Design Intent
Toggle Design Intent
#### Before meeting ##### VFS actions - Navigate to reference link: [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) - [x] Schedule your Design Intent when ready: - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - 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 - The Governance team is responsible for inviting our team members, including our Product Owner, Product Manager, and practice area specialists. We also notify OCTO-DE practice area leads when we finalize meeting scheduling. - Click "Schedule Event" - [x] Notify the Collaboration Cycle team of this event by using the `/Collab Cycle Design Intent` "slash-command" in your team channel. Provide information as prompted by the Slack workflow. - [x] Link all artifacts **ONLY** in the Design Intent artifacts section below at least two days before the scheduled Design Intent. **Do NOT add artifacts to Comments section** **Design Intent artifacts** See Platform guidance on [Design Intent artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent#Designintent-Artifacts). Platform feedback is based solely on the artifacts provided, as reviewed during the two days before the Design Intent 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. - [x] User flow ([Sketch file](https://sketch.com/s/b48c905c-7c7f-46fb-9ae5-6020ff0e5174)) (required) - [x] Whiteboard sketch or other lo-fi prototypes or wireframes ([Sketch file](https://sketch.com/s/b48c905c-7c7f-46fb-9ae5-6020ff0e5174)) - [ ] Research plan - [ ] Any other artifacts you have so far ##### Platform actions - [ ] Slack thread with VFS team: https://dsva.slack.com/archives/CBU0KDSB1/p1696603768730639?thread_ts=1696603765.586109&cid=CBU0KDSB1 - [ ] Meeting date/time: October 24, 2023 at 3.30 ET #### After meeting ##### Platform actions * Accessibility * [ ] Feedback ticket attached * [x] No feedback * Design * [ ] Feedback ticket attached * [x] No feedback * IA * [x] Feedback ticket attached * [ ] No feedback * [ ] Update this ticket with the Zoom recording - Recording link: https://oddball-io.zoom.us/rec/share/NPVhlQ18XA4A93qiwd37RpuIX-q1KeYXNwrfPQHeatfClTrKn4SpvFhXlgEcSKrb.AK0ZUxIBkm-9R3wY - Passcode: 54a%ae+J ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concernsSitewide CAIA Intake Request
Toggle Sitewide CAIA Intake Request
##### VFS actions - [x] Complete the [Sitewide CAIA intake request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Sitewide-CAIA-intake-request.2124906551.html) - [x] Link to the Sitewide CAIA Intake Request ticket below #67055Research Review
Toggle Research Review
#### VFS actions - [ ] Complete the [research review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Research-plan-review.1781891143.html)Midpoint Review
Toggle Midpoint Review
#### Before meeting ##### VFS actions Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [x] Schedule your Midpoint Review when ready: - Open the [Calendly midpoint review calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - 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" - [X] Check this box if you'd like this review to be asynchronous (Please refer to the [Midpoint Review guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Midpoint-review.1781039167.html) for the difference between a synchronous meeting and an asynchronous review) - [x] Notify the Collaboration Cycle team of this event by using the `/Collab Cycle Midpoint Review` "slash-command" in your team channel. Provide information as prompted by the Slack workflow. - [x] 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review#Midpointreview-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. Provide links or documents for the following: - [X] Finalized design prototype or mockup: [Sketch file](https://www.sketch.com/s/b48c905c-7c7f-46fb-9ae5-6020ff0e5174) - [X] Specify which pages are included in the review: Current, Unhappy Paths - [ ] Research plan - N/A - [ ] Conversation guide - N/A **Content artifacts** - [X] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. [CAIA intake](https://github.com/department-of-veterans-affairs/va.gov-team/issues/67055) - [X] [Content source of truth on Sharepoint](https://dvagov.sharepoint.com/:w:/s/SitewideCAIA/ESKYtD-cnh9Pg8rBf_kgYaoBmr8Mg7eMTrtKtKoGrXCDiA?e=IQyeOD) - [X] [Centralized content feedback and response](- https://github.com/department-of-veterans-affairs/va.gov-team/issues/68949#issuecomment-1874275167) **IA artifacts** - [X] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. [CAIA intake](https://github.com/department-of-veterans-affairs/va.gov-team/issues/67055) - [X] [CAIA IA design doc](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/information-architecture/ia-design-docs/va-police-facilities-page.md) - [X] [CAIA IA tracker ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/69003) - Our tickets to implement this feedback: - https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16233 - https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16234 ##### Platform actions - [x ] [Slack thread with VFS team](https://dsva.slack.com/archives/C0FQSS30V/p1704219948268439) - [x] Meeting date/time: 11:30 a.m. on January 9, 2024 (Async) #### After meeting ##### Platform actions * Accessibility * [x] Feedback ticket attached * [ ] No feedback * Content * [x] Feedback ticket attached * [ ] No feedback * Design * [x] Feedback ticket attached * [ ] No feedback * IA * [ ] Feedback ticket attached * [x] No feedback * [X] Update this ticket with the Zoom recording - Async review. ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concernsAnalytics Request
Toggle Analytics Request
#### VFS actions - [ ] Complete the [analytics request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Analytics-request.1782120453.html) - [ ] Link to the Analytics Implementation and QA Request ticket belowContact Center Review
Toggle Contact Center Review
#### VFS actions - [ ] Complete the [Contact Center review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] Link to the Contact Center review request ticket belowStaging Review
Toggle Staging Review
#### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [x] Schedule your Staging Review when ready: - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - 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" - [x] Notify the Collaboration Cycle team of this event by using the `/Collab Cycle Staging Review` "slash-command" in your team channel. Provide information as prompted by the Slack workflow. - [ ] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings. - [ ] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section** - [ ] I confirm the environment is available and test users have been provided. - [ ] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** See Platform guidance on [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts). Platform findings are based solely on the staging URL and test users provided, as reviewed during the four days before the Staging Review meeting. Any test cases not covered or any ongoing work taking place during the review period may not be reflected in those findings. **Product artifacts** - [ ] Staging URL - [ ] Specify which pages are included in the review - [ ] Staging test user information **Note:** Please double-check that you've provided staging access information appropriate for testing the tool or feature. Don't put staging credentials in your va.gov-team ticket; store [test user information, passwords, and tasks](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md) in a .md file in the va.gov-team-sensitive repository. **Content artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. **IA artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. **QA artifacts** An artifact that corresponds to each standard in the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [ ] [Regression test plan](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-regression-test-planRegressionTestPlan) - [ ] [Test plan](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-test-planTestPlan) - [ ] [Coverage for References](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-traceability-reportsTraceabilityReports) - [ ] [Summary(Defects) reports](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-traceability-reportsTraceabilityReports) - [ ] [E2E tests](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-e2e-test-participationE2ETestParticipation) (provide a link to the product’s code) - [ ] [Code coverage](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-unit-test-coverageUnitTestCoverage) (provide a link to the product’s code) **Accessibility artifacts** - [ ] [Completed accessibility testing artifact](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=briandeconinck&labels=a11y-testing&template=a11y-testing.yaml&title=Accessibility+Testing+for+%5BTeam+Name%2C+Product+Name%2C+Feature+Name%5D). For details, see [Prepare for an accessibility staging review](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review). ##### Platform actions - [x ] [Slack thread with VFS team](https://dsva.slack.com/archives/C0FQSS30V/p1701199378559799) - [ ] Meeting date/time: Thursday, December 14 at 3:30 p.m. ET #### After meeting ##### Platform actions - [ ] Update this ticket with the Zoom recording - Recording link - Password: ##### VFS actions - [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns - [ ] Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket. - [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review. - [ ] Share ServiceNow ticket number here: ______ - [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are completePrivacy, Security, Infrastructure Readiness Review
Toggle Privacy, Security, Infrastructure Readiness Review
#### VFS actions - [ ] Complete the [Privacy, security, infrastructure readiness review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Privacy-and-security-review.1782317101.html) - [ ] Link to the Readiness Review ticket below #### Platform actions - [ ] Privacy, security, infrastructure readiness review is complete