-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
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: @KingArthur0205 @ben-domingue please let me know if you guys have any input on the splitting! :) |
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 |
got it! |
file: code:
|
PR: #688 |
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) |
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? |
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 :) |
@saviranadela yes let's keep it simple :) |
thanks for the input! i have updated the file, code, and PR :) |
one comment: should one of these be dropped: q_s_048_original q_s_048_reverse |
oh yeah right. updated! |
added, thanks @saviranadela |
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
The text was updated successfully, but these errors were encountered: