Calculated fields/auto variables: useful, responsible for calculating chronotype for sleep study
Setting RecordID: unsure, pugID (synonymous to lunaID) was inputted into RedCap by San Diego team. Specific # of IDs were generated (set #, no adding)
Change question on an old instrument: has done this before, if the decision was made to no longer use a question, it was deleted. That data is found in past releses, but not used in future ones. (unsure if it deletes the old Q responses retroactively, asked but not entirely answered)
Saving partially completed + redoing: Create space for repeat forms when it's anticipated… if you expect it to happen make one or two extra. [never has experienced this before]
start/stop middawy through event? attrition? replacements?: label it as “incomplete” for attrition. doesnt use replacements so no insight. original cohort studied is only data sets used, if they drop out their events are simply incomplete.
FIONA server?
they don't store any PIH (email/phone/anything..) it's in a separate system held by SD not pitt(still accessible by ABCD but not their own?)
UPLOAD SURVEYS FROM CSV EXCEL FILE (horribly specific formatting)
brnaching logic is probably the must usefuul thing (similar to SQIS(?) syntex)
drawbacks/vulnerabilities: reports are clunky..
DF *thinks* qualtrics interfaces w/ redcap.. cannot say for certain but nonetheless
VL recap/takeaway: they basically supplied SD with the information they wanted, and then SD inputs (and continues to) the instruments/structural sides of it all. their RA's might know more about the RecordID/repeat visits.. might reach out to Andrew. i have more thoughts i just dont know them yet.