Skip to content

Section 6 : Weekly Operations Metrics Analytics/Operations Review #1591

@KELSEYDOWLING7

Description

@KELSEYDOWLING7
  1. Suggestion to update all report figures to have 6-week tic marks instead of 4-week tic marks for readability on the x axis OR we can do the M-YY abbreviation we were considering for the biospecimen report (ex A-24 for August 2024). HOWEVER, we look at weeks as Monday-Sunday, so the 1st of the month will likely not land on a Monday and because months may have 5 weeks we could have tic labels that repeat.
  • Operations decided/approved
  • Code updated in production
  1. Suggestion to update y axis tics in this whole section: If <10, increments of 2. If >=10, increments of 5
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.8 - Suggest adding a footnote explaining the sudden spike (doesn’t match the UC date of 9/16/25)
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.12 - Suggest revising title to: "Cumulative Number of Withdrawals and Data Destruction Requests per 1k Verified Participants through 2026-02-08 All Sites”. Data destruction is displayed here as count and date requested not count and date completed, as described in the figures before this one.
  • Operations decided/approved
  • Code updated in production
  1. Table 6.2 - Suggest adding a footnote for when each new reason was added (reasons were added over the course of 2-3 years)
  • Operations decided/approved
  • Code updated in production
  1. Table 6.2 - (If needed) have a footnote explaining that the CIDs were mistakenly swapped for technical vs. no reason selected before the report on 2/16/2026, which is why the reasons for refusal may look off compared to previous weeks
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.13 - Suggest revising Y-axis title as: "Number of Refusals or Withdrawals"
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.13 - Suggest adding a footnote for when each new reason was added (reasons were added over the course of 2-3 years)
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.13 - (If needed) have a footnote explaining that the CIDs were mistakenly swapped for technical vs. no reason selected before the report on 2/16/2026, which is why the reasons for refusal may look off compared to previous weeks
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.15 - Suggest revising Y-axis title to "per week" for consistency with Fig 6.14
  • Operations decided/approved
  • Code updated in production
  1. Figure 6.15 - Should the X-axis be 'Date of Data Destruction Request’?
  • Operations decided/approved
  • Code updated in production
  1. Table 6.4 - Would be more informative to make Total Withdrawals column into column % for each site (similar to Table 6.2)?
  • Operations decided/approved
  • Code updated in production

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions