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

Adaptation and validation of simple tools to screen and monitor for oral PrEP adherence #628

Closed
ben-domingue opened this issue Oct 16, 2024 · 13 comments
Assignees

Comments

@ben-domingue
Copy link
Owner

Data Availability: The data can be found on the Harvard Dataverse Repository at https://doi.org/10.7910/DVN/NI4ZQA.

https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0251823

@saviranadela
Copy link
Collaborator

the first section included 54 items in random order making up the six subscales of the screening tool. The same items were administered uniformly to all women. The second section comprised of 45 monitoring items in random order adapted for oral PrEP. There were two versions of this section; one focused on oral PrEP and administered only to women who had or were participating in oral PrEP trials, the other version adapted oral PrEP-specific items to other types of oral pill use to better fit the experiences of trial-naïve women.

based on that, I split them this way:
a. items from screening tool
b. items from monitoring tool with all participants combined
c. items from monitoring tool with former trial participants (FTP) only --> subset of b
d. items from monitoring tool with trial-naïve participants (TNP) only --> subset of b

@KingArthur0205 @ben-domingue please let me know if you guys have any input on the splitting! :)

@saviranadela saviranadela self-assigned this Nov 8, 2024
@ben-domingue
Copy link
Owner Author

wait i don't think we need to split here. we could maybe have a column that captures this set of distinctions but if the items are the same across a-d no need to split i don't think

@saviranadela
Copy link
Collaborator

got it!

@saviranadela
Copy link
Collaborator

saviranadela commented Nov 8, 2024

file:
PrEPAdherence_Zissette_2021.csv

code:

library(tidyr)
library(dplyr)

df <- read.table("Screening and adherence monitoring for oral PrEP.tab", header=TRUE, sep="\t")

df$id <- seq(1, nrow(df))

df_final <- df %>%
  select(id, starts_with("q_s_"), matches("^q_m_.*all")) %>%
  pivot_longer(-id,
               names_to = 'item',
               values_to = 'resp') %>%
  filter(!is.na(resp) & item != "q_s_048_reverse")

df_final$item[df_final$item == "q_s_048_original"] <- "q_s_048"


write.csv(df_final, "PrEPAdherence_Zissette_2021.csv", row.names=FALSE)

@saviranadela
Copy link
Collaborator

PR: #688

@saviranadela
Copy link
Collaborator

or actually I can also compile it like

id, item, resp, former_participant (N/A for screening items, 0 for no in monitoring items, 1 for yes in monitoring items)

@ben-domingue
Copy link
Owner Author

hm. i'm inclined at this point to simplify this data and maybe just take a single set of responses for each person? seems like kind of a mess otherwise? @saviranadela what do you think would be the right way of going if our goal is to get something a little simpler?

@saviranadela
Copy link
Collaborator

oh yes, if we want to keep it simple, we could just record the screening and monitoring items (they are different) without distinguishing between TNP and FTP (so basically just point a and b i listed above). let me know what you think :)

@ben-domingue
Copy link
Owner Author

@saviranadela yes let's keep it simple :)

@saviranadela
Copy link
Collaborator

thanks for the input! i have updated the file, code, and PR :)

@ben-domingue
Copy link
Owner Author

one comment: should one of these be dropped: q_s_048_original q_s_048_reverse

@saviranadela
Copy link
Collaborator

oh yeah right. updated!

@ben-domingue
Copy link
Owner Author

added, thanks @saviranadela

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants