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

New CIDs for Re-invitation Campaign Type and Re-invitation Date (April Release) #1208

Open
4 tasks
robertsamm opened this issue Jan 31, 2025 · 1 comment
Open
4 tasks
Labels
API CCC Priority 2 Issues will be prioritized in the upcoming/next release

Comments

@robertsamm
Copy link
Collaborator

KPCO and KPNW are going to run through their 1st round of invitations in their catchment populations soon. They are preparing for a second round of contact attempts to re-invite patients they invited before that did not initially respond to the invitation. We would like KPCO/KPNW (and eventually all sites in the future) to share data about re-invitations with our system so we can track progress and response rates. Aiming to have the following items below finalized for an April Release.

To track re-invitations in our system, we will need the following 2 new CIDs:

  • Re-Invitation Campaign Type: will have the same format and response codes as the current ‘Campaign Type’ variable. KP will push this to us when they initiate a batch of re-invitations.
  • Re-Invitation Date: will be autogenerated by our system upon receiving the Re-invitation Campaign Type.

Tasks:

  • Add the new variables and their descriptions to the Data Dictionary (@hullingsag)
  • DevOps add the new variables to the API (DevOps - @sonyekere please assign)
  • Test sending of the new variables w/ KPCO + KPNW (@mnataraj92)
  • Add to QC and Metrics Report - (@robertsamm to add in a separate github issue in the Analytics Repo)

Additional details:

  • Sites will use the same token/PIN and Study ID for each re-invitation to to a recruit. They will not push a new record for the same person in the system.
  • Sites will not need to push us the de-identified data again
@robertsamm
Copy link
Collaborator Author

Related Issues for QC and Metrics Requests:
QC: Analyticsphere/metricsReportsRequests#207
Metrics: Analyticsphere/metricsReportsRequests#208

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API CCC Priority 2 Issues will be prioritized in the upcoming/next release
Projects
Development

No branches or pull requests

7 participants