Informed Consent and FERPA Release
Terracotta’s Consent/Release Process
Students' electronic consent responses in Terracotta meet the US Department of Education's requirements for e-signature when providing a FERPA release.
Students' responses in Terracotta are legally verifiable — students are authenticated in the learning management system when they respond, and Terracotta stores the responses, along with their timestamp and context, in a database with routine back ups and extensive security certifications.
There are requirements regarding what is presented to students when they provide FERPA release. When consent in Terracotta is collected, it appears on the same page as the consent statement that a researcher’s Institutional Review Board (IRB) approves, and Terracotta expects that your consent statement will "specify the records that may be disclosed, state the purpose of the disclosure, and identify the party or class of parties to whom the disclosure may be made" (34 CFR § 99.30).
Once students respond to the Informed Consent assignment, it is impossible in Terracotta, by design, to change the consent statement. Thus, Terracotta not only has timestamped response records from authenticated students; it can also construct a record of what students saw in their browsers when they responded.
Advantages to Terracotta’s Consent/Release Process
Beyond merely meeting the requirements for e-signature for a FERPA release, Terracotta’s consent process has several of advantages over paper consent/release:
Paper consent/release creates an identifiable physical record of a student's response, which introduces the possibility of loss of confidentiality, as the student's identity, consent response, and FERPA release are visible to whomever collects and stores these documents (and potentially to nearby classmates). Further, for many studies, these physical documents will need to be read by someone one at a time, and students' names (or other identifiers) manually added to an electronic document to begin the process of data collection from Canvas, introducing further potential error and loss of confidentiality.
In Terracotta, consent and FERPA release responses are private. While the consent process is administered in a Canvas assignment, the teacher is never able to see students' responses — the teacher can only see whether and when a student responded, but not how. Terracotta’s research data exports filter out non-consenting participants, and replace consenting students' identities with anonymous pseudonyms (Terracotta-internal identifiers). To be clear, Terracotta does maintain identifiable records of who provided consent in its internal database, but these are never provided to the teacher.
A key advantage of electronic consent in Terracotta is that students not only have a secure, private means of registering their legally-verifiable consent response; they also have a secure and private means of changing their consent response. In principle, students should have the right to withdraw from a study, but when using paper consent, once consent is provided, significant barriers prevent students from withdrawing their FERPA release. With paper consent, a student would need to keep a copy of the consent statement, contact the researcher, and request to be removed from the study, all of which would be identifiable and likely on vulnerable systems (e.g., email). In Terracotta, consent is implemented as an assignment in the LMS, and if a student wants to change their response, they simply return to the assignment and submit a new response.
Administering consent + FERPA release in Terracotta gives students longer to read the consent document, and more time to respond. Further, Terracotta registers their responses and immediately differentiates the students' future learning activities according to their responses — if a student does not provide consent, they immediately receive default/business-as-usual assignment versions. In other words, consent in Terracotta is not only a data collection vehicle, it also allows students who opt out to avoid random assignment, and to avoid having their data included in research data exports without the need for manual entry from paper records.