Webinar · On demand

eConsent – The Enrollment Solution for Decentralized Trials

Castor Founder Derk Arts and Head of Products Rowan Milwid present eConsent regulations and demonstrate Castor's video-enabled remote enrollment workflow.

50 min · Recorded 22 September 2020

  • Dr. Derk Arts, MD PhDCEO, Castor
  • Rowan MilwidHead of Product, Castor
  • Dr. Derk Arts, MD PhDCEO, Castor
  • Rowan MilwidHead of Product, Castor

About this webinar

In this webinar, Castor Founder Derk Arts and Head of Products Rowan Milwid examine the operational and regulatory requirements for implementing electronic informed consent in decentralized and hybrid clinical trials. Designed for clinical trial teams, researchers, and study operators adapting to remote trial execution during COVID, the session outlines country-specific rules for digital consent and e-signatures in the US, UK, Germany, and the Netherlands. The speakers detail essential setup steps, including protocol design, IRB approval, participant identity verification, and compliant PDF documentation. They also deliver a live demonstration of Castor's web-based enrollment and eConsent workflow, showing how custom recruitment landing pages, automated ePRO screening questionnaires, encrypted peer-to-peer video calls, real-time countersignatures, and EDC integration operate together while separating personally identifiable information.

Key takeaways

  • While digital patient information is broadly accepted, valid e-signatures depend on local regulations, with full support in the US and UK, practical hurdles in Germany, and restrictions on interventional studies in the Netherlands.
  • Implementing eConsent requires specifying electronic consent in the study protocol, securing IRB approval beforehand, verifying participant identity, and providing a signed PDF copy to both the participant and the researcher.
  • Castor's web-based enrollment workflow connects custom recruitment landing pages with ePRO screening questionnaires to automate eligibility checks and reduce funnel attrition before the consent stage.
  • Integrated end-to-end encrypted peer-to-peer video calls allow researchers and participants to review the consent form together, verify identity visually, and complete real-time signatures and countersignatures in a single browser experience.
  • Keeping eConsent in a separate application integrated with the EDC restricts access to personally identifiable information while syncing subject identifiers, eligibility outcomes, and consent statuses across systems.
  • The platform supports protocol amendments by keeping prior participants on their original signed version while routing new participants or re-consenting active subjects to updated consent forms.
Full transcript

Derk: Hello, everyone. Welcome to our webinar on eConsent, where we will be speaking about eConsent and some of the technicalities around incorporating eConsent into your projects. But of course, the part that I'm most excited about is the presentation of our video-enabled eConsent solution. So we'll we'll get to that in a bit. And I'll see if I can maximize my screen share here, and I'm going to go to that window. So hopefully you see my slide advancing. Rowan, if anything is is wrong, please let me know because I'm now looking at the slides. So my name is Derk Arts. Originally trained as a medical doctor, also did a PhD in medicine and medical informatics.

And eight years ago, I founded this company because I see still a lot of room for improvement in the clinical trial process and in the evidence-based medicine process. And so every day, I'm still eager to go to work and address this problem. And with me, I have Rowan Milwid, who is our our head of products for for already over three years now. And he is here with me today to present our our new eConsent solution. We'll be doing a part presentation and then a full live demo with, you know, all the risks that come with that. So bear with us, but we wanted to give you, you know, the best sort of preview we could give you.

So, you know, before we get to that, we just quickly want to want to speak about, you know, why the need for eConsent is now so prominent and what are some of the challenges we now face. Well, obviously, ever since March, and even before that, February, January, people have been speaking about COVID, and it hasn't actually stopped, in the sense that it's still, I think, the topic that everyone, you know, speaks about when they when they meet each other, specifically in the clinical clinical trial space. Because COVID, of course, has a huge impact on clinical trials. It paused a lot of trials.

There's a lot of patients who weren't able to, you know, receive investigational therapies, and it basically made it, you know, practically impossible to to continue normal operations. And that it brings, you know, a lot of challenges for for almost all the players in this space. And therefore everyone is now looking for for solutions, because we need to find a way to continue research even when, you know, a potential second wave might be hitting. And I think the most important thing here is to to think about the patients that are enrolled in these trials. You know, they've already been enrolled. They've already been burdened.

You know, they might be receiving therapies that might potentially save their lives in these trials, and not being able to continue these projects will negatively impact them. And I think for now, the focus should really be on making sure we can continue those types of projects and make sure that those essential trials can can continue. And so what are some of the things we can do? Well, everyone's been speaking about digitizing clinical trials for a long time, but progress has been slow because ultimately, there wasn't a a strong, inherent need to make trials more digital than they already were. Second, you know, electronic reporting of patient outcomes was, of course, already there, but but not something that every trial was incorporating.

And with COVID and with this increased need for being able to run trials remotely, the increased need to run trials that don't rely on physical visits to a site, we need to really accelerate the adoption of those two, you know, those two items. So what can we do? How can we deal with patient recruitment? How can we deal with, you know, informed consent, with actual enrollment into a trial, and also retention? What are some of the techniques we can deploy to to make sure we continue to perform well on those on those key metrics when when COVID is still all around us?

And so looking a little bit at patient enrollment and enrollment of patients of patients in trials, of course, there is a a very strong educational component for when you when you enroll patients in trial, because they need to understand their own involvement in in the trial that they are planning to participate in. And then there's, of course, the document of the informed consent. And so those are two two key pieces. I would like to add a third, actually, now that we're talking, because I think screening for eligibility is is also a crucial part. Of course, not every trial has, you know, strict eligibility criteria, but typically what we see is that that's very common to have those.

But I think if you look at it from a regulatory standpoint, some of the things we just absolutely have to take care of properly are the fact that a patient really understands their their own involvement and what it means to participate in a particular trial, and that we then have a compliant manner of documenting the fact that they have given informed consent through a signature. And so if you look at eConsent specifically, there's a few challenges there, because, of course, informing patients through digital means is not something new. But capturing a compliant signature that the authorities across borders accept on an informed consent form, that's actually more of a challenge.

So what we see is that generally speaking, globally, informing patients, so having a a digital process for informing patients, that's, you know, that's all fine. The problem arises when they actually have to enter their signature, or when they have to sign for the fact that they've received the information. And maybe you've seen this, maybe you haven't, but we not too long ago published a a white paper on eConsent and e-signature status in various countries. And you see a little snippet of that here on the screen, but it's it's not very straightforward. That it's it's been a very complex white paper to put together.

It required a lot of research, and there's still actually quite a bit of debate on on certain countries, because we see that, you know, the actual eConsenting process is allowed in most countries, but then signing to to to indicate for a patient that they have understood exactly what the trial entails, that's something that's not not universally allowed. But I think there, you know, there's two very big, important countries that that do allow for full, you know, eConsent, which are the US and the UK. Germany does allow for both, but there's been a a lengthy discussion on the topic of how to obtain, you know, an actual valid e-signature in Germany.

And so this is still a a debatable topic because it's it might technically be possible, but in practice, it might actually be very hard for patients to obtain an e-signature that that the German authorities would accept. So this is definitely something to look out for when you are considering eConsent projects in in Germany. And then in the Netherlands currently, unfortunately, I would say, we do not allow for e-signatures for studies that have any type of intervention. So the majority of clinical trials would fall in that category and would not allow for e-signatures, although currently that is being revisited, because for obvious reasons, COVID has really pushed the need for e-signatures. So therefore, we are seeing some progress there.

And then, you know, we've listed other, you know, various countries. But as you can see, it's not it's not something that's clear-cut. So I think anytime you would consider switching to eConsent, the first step basically is looking at your project, you know, is this a project that would, you know, normally have to go through through IRB approval, and then making sure that, you know, local regulations allow for the eConsent workflow, because you don't want to be in a situation where you've put a lot of time and effort into your protocol, and you've made sure everything looks great, and that you've you've focused on the patient from the very beginning.

Maybe you've even involved patients in putting your protocol together, which would be, you know, an amazing thing to do, and then to only find out during the IRB submission process that it's not actually allowed in that country to to have eConsent, or e-signatures, more likely. So, you know, make sure you you focus on that. And then looking at sort of implementing eConsent, what are some of the steps you need to think about when you when you're considering an eConsent approach for a project? Well, first step is to make sure your protocol, you know, discusses obtaining eConsent electronically, so really being explicit about that.

And, of course, we have seen new guidance coming out from the FDA, the EMA, the MHRA, all stating that because of COVID, because of all the special regulations, or special circumstances, I should say, it is actually allowed to switch to, you know, a different way of consenting with the proper approvals. But technically speaking, you should always just incorporate the intent to to have electronic consent from the very beginning. And then, of course, the the IRB must approve the use of eConsent. So that's a very important step. That's why it's so important to think, you know, ahead of ahead of time. Consent forms must be easy to navigate. So, of course, it should be very straightforward to navigate a consent form.

It should include hyperlinks to external resources. You can even sort of add an maybe a video, maybe not to the consent form itself, but to the consent process, to to make it easier for for a participant to grasp the the information in that form. And then, of course, there's the e-signature piece. So you can't just have a check box saying, "I approve." There needs to be a valid e-signature element to the consent workflow. So just a simple boolean, or a simple check box, that won't suffice. You need to incorporate something that, you know, in under local regulations constitutes an e-signature. And there there's, of course, a lot of white papers that can be found on that topic.

But that's that's crucial to to add that, otherwise you still have to depend on signatures on on paper forms. And then the signature process must must include identity verification. So you must have some way of identifying who the patient is. And we've done extensive research on this topic. There's various ways you can do it. So you can you can potentially you can use, you know, an upload of a document and verify that, or you can also identify a patient during a video call, which, of course, is quite straightforward, because they can then show their driver's license or some some other form of ID.

And in the UK, we know it's also possible to when there's a a final face-to-face element to the study, you can also identify the patient there, as long as the identification happens before any intervention happens. So again, it's critically important to look at the local regulations and how things have been sort of put together for that for that country to make sure you meet all those requirements, but that you also use all those opportunities that that are there. Then, and by the way, I can't see the questions right now, so if if Rowan or Cameron, if there's anything pressing, please let me know so I am aware of of that.

Then of course, study participants must be able to receive a copy of the consent form. So that that's also something to think about, that they receive a a PDF with the signature of both the researcher and and themselves, of course, meeting all the requirements. So it can't just be a simple a simple Word document. It's It really needs to be a, you know, a valid copy of the signed consent form. And, of course, all the documentation must be accessible for the regulatory entities during an audit, for example.

So there's quite a few things to think about, but honestly, with the right technology, of course, the technology that we'll be presenting later, this this should all be doable assuming you know, assuming that you've actually considered local regulations and are not trying to implement e- eConsent and e-signatures in countries that that don't allow it. And so with that, I want to actually hand over to to Rowan, so he can start sharing his screen and talk a little bit about more about how we approach these things. So Rowan, I see your screen here. You can switch to your presentation and I will maximize it for you. Yes, we we see it here.

Rowan: Excellent, thank you. Because everybody, you can hear me okay now, Derk?

Derk: Yeah, absolutely.

Rowan: Okay, perfect. So then I'll continue from here. Thanks for for that, Derk. So as Derk has mentioned, we of course have an eConsent solution. And I'll walk you through, it's beyond eConsent, in fact. We've got a lot of integrated solutions that I'll walk you through right now related to enrollment and eConsent. And it starts with the piece that we play in recruitment, which are custom landing pages, and which can help you to streamline and make your recruitment efficient by bringing people in from a number of different online sources and and keep a consistent patient experience. So these are landing pages that can be customized to fit your brand and your messaging and your recruitment campaigns.

And also with this process, it's it can help you, I'll move on here, to minimize site burden, which with eConsent in general, but also with the recruitment landing pages specifically, because you can bring people in without the necessity for somebody at site to to take part in that process. And also can reduce operational overhead, in this case, it's self-service for the the patients for recruitment. And and it also helps to automate things because it's integrated with our our ePRO for, for example, screening questionnaires, that I'll get to in a moment, with our EDC to to automatically create subject IDs and things like that. It also gives you better funnel visibility.

So unlike a lot of the the traditional processes, it allows you to you could add, for example, analytics on your landing pages to to see the performance of your campaigns in in real numbers, and can figure out where your attrition rates are in the funnel. So moving along, I mentioned screening questionnaires, so we have our landing pages are integrated with our our ePRO, or questionnaire software and and the EDC. And that means that directly off the back of the the landing page, which we'll give you a live demo of later, you can have them land on the screening questionnaires, which is great for the patient experience and consistency. You've got your automated eligibility assessment.

And of course, having the questionnaires immediately after the landing page can also help to reduce attrition in the funnel, while people are waiting around typically between different stages. We've got configurable workflows so you can decide where and when the questionnaires can can be shown in the in the patient experience, whether, for example, they're required to be inside of a logged-in environment or not, depending on where you're running the study and what the the requirements are there. And, again, you can improve the the final conversion by having this seamless patient experience. Speaking of patient experience, everything we've done has been designed to be simple and intuitive and to reduce the burden on on patients for multiple clicks or for complicated systems.

So everything from the landing page through to the consent can be done with minimal interactions. It's also all of this are web applications, so there's no need to download and install applications, which sometimes can come with compatibility issues with older devices, for example. And it works across all different devices: smartphones, tablets, laptops, desktops, whatever operating system, or any modern operating system or browser. And, of course, can be accessed from anywhere in the world. So Then we'll be very happy to show you in a moment, as well, part of our system is the virtual visits through secure and compliant video calls, and this is done with end-to-end encrypted video calls. So the highest level of security, as you would expect for any medical application.

And what's nice about this is it helps to mimic the in-person experience that both the study team and perhaps patients are are used to and have confidence in. So that's easier to adapt operational procedures, and it can help to improve trust with your participants. So it also helps with comprehension. You've got the virtual face-to-face interaction, so you've got the reading of facial expressions and body language that can be lost on a phone call or if it's entirely a self-service process. And we also helps to strengthen remote identification. You've got somebody in on the other end of a video call.

So, for example, if you're using the upload of of an ID document, then you can you can visually identify them on the video call compared to the ID document. And now, moving along, actually, we're going to skip through that and we'll get to that at the end. But we've got a flexible ICF design. So once with our system, we can match virtually anything in your typical paper or or PDF design, and that's important for IRB approval and to keep consistency in formatting with what you have determined to be the most important to to to bring the information across properly.

It also helps with with comprehension and readability to have it as an online form where you can control font sizes and for people with issues, you know, eye issues, their sight isn't isn't what it used to be perhaps. And we also allows you to to sign and countersign in real time in our application, which allows you to be on the consent call at that moment in time. I also hear, Derk, let me know if there's anything. I hear a lot of the the questions coming in. Hopefully these are things that we will get to. If we don't answer your questions live here during the this part of the webinar, then stick around afterwards and during the Q&A we'll get to them or or after that.

You can always reach out to us afterwards as well. So one of the other great things about this the way that we've implemented this product is that it's integrated with our EDC, as I mentioned previously. And that means that you've got great oversight of the entire enrollment process, or at least the parts that that that you would use our our applications for. And that means that the landing pages, the questionnaires, eConsent, EDC, ePRO, it's all in connected or in the same platform, depending on which one we're talking about.

That means that you've got matching identifiers, statuses can be updated across the systems, customizable workflow, you can see the progress of your overview for the different stages, something we'll show you live as well in a moment. And you can have restricted access to PII while maintaining this integration. And what I mean by that is that in an EDC system, typically you would not want the personally identifiable information, and in eConsent, of course, you need it for identification purposes. And so we've got separate systems to maintain that that properly, but they're integrated to still allow for for the information that should flow to flow between them.

Now when it comes to privacy and compliance, we've we of course with all of our systems, that's that's key in all in our decisions. And so we make sure that we adhere to the regulate the important regulations using our quality management system, including 21 CFR Part 11, with things like an immutable audit trail, unique electronic signatures, a statement for the signature for the the researcher, or the study team, and everything password protected. We use of course GCP as well for things like data backups and long-term data storage. And we take the strictest interpretation of GDPR and HIPAA for privacy, and as an organization, we're also ISO 27001 and 9001 certified. So I'll talk you through just quickly.

This won't be part of the demo necessarily, because a lot of it is custom configuration with a little bit heavier workload or things that are coming soon on the roadmap. But, of course, we can add languages as needed for the ICF. So the interface as well for the for the patients at least, depending on where you'll be running your trials. Multi-center management is typically custom configuration and and something that, for example, with advanced user access management and workflows. Similarly with concurrent ICF versions, depending on what your needs are there. So, for example, if you've got delayed IRB approval in one of your sites or markets in a multi-center, multi-market study.

We will be adding a the ability to have both on-site and remote in a hybrid configuration, in the scenario where for perhaps you've started on-site and need to move over to remote, but want to retain everything within the same system from from before migrating over. We'll be implementing as well custom workflows for things like a witness and and legally authorized representative signature flows. More hybrid with paper and electronic, as we know that when you're running trials in in Europe, for example, some countries are fine with electronic and some are still requiring a wet signature. And so we want to make sure that you're able to use the system across all sites, regardless of whether you still need a wet signature in some locations.

And ultimately, down the road, we will be improving the patient engagement capabilities with custom workflows as well. So with that, I think I hand it back over to you, Derk, where you can then If we can get the screen share back over, let me know when that's

Derk: Yeah, I'm handling it. I'm handling it.

Rowan: You're there. Exactly. Welcome to live. And you can start the live demo that I think everybody is now very enthusiastic to see.

Derk: Yeah, so Rowan, you see you're seeing the customized enrollment portal?

Rowan: Absolutely.

Derk: Great. So I am now a, you know, a research participant, maybe even a patient, and I have been exposed to a new study that's of interest to me. So maybe I've seen a Facebook advertisement or I've seen something on Instagram that peaked my interest. And I clicked that link and it sends me to this page. And so the goal of this page is to really specifically for your project, inform potential participants about the study, why they would, you know, want to consider participating, and make sure that they already have some idea of an eligibility. So what we do when we work with you and your team is to make sure we create something that is, you know, fully responsive. So this page will will work well in any in any sort of configuration, on any device. So Rowan, are you seeing the resizing here, as well?

Rowan: Yeah, it's working perfectly.

Derk: So as you can see, this is basically what it would look like on a mobile phone. So we make sure we create a fully responsive, beautiful looking page for your project, and make sure that sort of all the information is conveyed correctly. And then as a patient, I can decide to to sign myself up for this project. Now in this case, as Rowan explained, I'm going to be sent to a screening questionnaire automatically. And this is a workflow we can configure for you. So we can decide to do this already, like just be just after signing up on the portal, like like you see here.

We can do this just before you you see the the eConsent form, so you've already sort of signed up for the eConsent platform. And this is really a decision that depends on how many patients you want to sort of already enroll themselves in the eConsent platform, that then maybe are not eligible. So there's pros and cons to each approach, but it can be customized and our team will happily discuss you the options with you. And so this is our our fully responsive ePRO functionality, so this also works great on mobile. And, you know, we already saw some questions around native apps, so we do have an app available for for patients that is native to iOS and and Android.

That's that's being launched, so that will provide a more native experience. But this workflow currently is web-based. And here I will go through some of the screening questions, and this will automatically validate my my eligibility. And in this case, I'm just going to quickly answer these questions here. Good thing I tried this beforehand, because I don't actually wear glasses, so I I wouldn't know the the right answers to these. And in this case, I'm not eligible, unfortunately. But let's pretend I am eligible. So when I do get through this entire survey, I will be invited through an email link to join the eConsent platform, and I go through a sign up workflow which is very basic, puts minimal burden on the patient.

Again, fully responsive, works on any device. And then I land on this on this page, where here I see the the research projects that I'm involved in. And as a patient, there's there's not a lot I can do here. I can, you know, fill in my, you know, my account details. I can expose my details to the researcher, so I I can choose to sort of add those to, and then I I have to agree to sharing those details with the researcher. But of course, the most important thing here is is starting a consent call. And now this is where it gets exciting and a little bit tricky.

So what I'm going to do is I'm going to disable my webcam here so that it should be available in in the app. And then Rowan, are you ready to start it on your end?

Rowan: Yeah, absolutely. So if you want to I think let me know when you're looking at my screen again now.

Derk: Yeah, I've just joined. I've just joined the call, so if you also can join?

Rowan: Yes, I can. Just a moment here, and I will be in there.

Derk: We're still looking at my screen, so you can you can disable your screen share for now.

Rowan: Okay. Just apologies for that. Well, we had have been kicked out, and so perhaps you want to talk through the ICF for just a moment there, Derk, and let me get back in.

Derk: Yeah, of course. So the key here is that we want to get as close to the normal consent process as possible. Especially for projects that were originally relying on, you know, a paper consent face-to-face process, we felt it would be best to to try to mimic that situation as closely as possible, because of course, and let me just mute this, the advantage of of video is that you can have an interaction with the patient. You can you can build a human relation, of course, and you can also answer any questions about the about the ICF directly. There we go.

Rowan: There we go. Yes, apologies for that. I this is what happens with two a couple of live tabs open there.

Derk: Can you mute yourself as well?

Rowan: I can. Is that echo gone?

Derk: I think so. Yeah, that's better. So because we we have now multiple video streams going on, it starts to echo for us. But but here we are. So Rowan is now the researcher, I am still the participant. So I can ask him any questions about this consent form, which we filled with some Latin just for the people who are into that type of thing. But the most important part here is, of course, the actual consenting process. So we've now talked through the entire process, all my questions have been answered, and I'm ready to to sign. So I'm going to be typing my name here and and Rowan is going to be doing the same thing on on his end. I'm going to confirm and sign.

So Rowan is going to provide the countersignature, so the document will be signed twice. And here I have now completed the digital signature process. And I believe that this is going to be sort of the most patient friendly way of doing this. Fully integrated, no external Zoom apps, no no DocuSign. It's all in one system, one single experience for a patient. And I think that's key, especially in this time that we really focus on on patient experience. With that, my work here as the participant is is done. The form is signed, and I can review it here if I if I want to.

I believe there's also a PDF that's being generated in the backend, so that will become available for me in the not in not too distant future. But we'll switch to to Rowan to see to his side of of this demo. And I'll stop my screen share, because it's a little bit confusing to look at. Okay Rowan, I'm going to maximize your screen now.

Rowan: You can see me here. All right. So as you can see here, we can, in the exact same manner that we saw it before, if I'm the researcher now, I'm looking at the patient, the subject record here. And I can go in and take a look at the form. We could have done that live on the call, as well, but of course you've seen it already. I can go in and type and sign it as well.

And what we end up with here is we end up with a fully executed form, and afterwards, as Derk has just mentioned, you've got the downloadable, in this case, ICF form in PDF format that is available to both the researchers and the participants, in this case, as required by FDA regulations. And and that's the overview there. Now all along with the countersignature, of course you've got an overview of the different records here and the status in them. But as we've mentioned previously, what's important is that these systems are also integrated, and so you've got an overview of everything.

So you've got the eligibility from the the screening questionnaires, you've got the consent status, this is back over in our EDC system now, as well as the the moving along after that with the rest of your study and the data collection. So Derk, I'll hand it back over to you now.

Derk: Yeah, I think that was it for the demo. There's a lot more, you know, moving pieces to show, and of course we've only shown you a relatively simple project. Projects are of course configured to your needs. As you may know, our entire platform is fully self-service, but for this new platform for now, we've opted to to support you with the setup, because we want to make sure we get everything right, and that of course also allows for more configuration and more sort of custom options. There's a lot of questions streaming in that I've tried to answer a few of. But before we do that, I would like to to thank Rowan for for all the hard work.

Great that we got everything set up in time for this for this demo. I'm very excited to to be showing this this amazing product to to our customers. And maybe we can start looking at a few questions. So, Rowan, maybe you want to, you know, pick one off the off the list. I've already answered a few, but I think it can't hurt to talk to talk through a few.

Rowan: Yes, absolutely. So I'll pick right from the top here. So I've got a question on withdrawing of consent, and so that has been considered in our platform. This is a there's a lot of functionality that you haven't seen that's it comes as custom configuration in terms of your workflow and your needs. And we didn't demonstrate how that can all be set up, but at a later date, we'll probably do this again on on demand. And in this case, patients can at any point in time come in and manage their consent. So they can come back in and they can withdraw from the study. Now, of course, depending on what your needs are for your particular study and what they've consented to, they wouldn't be withdrawing consent for data collected so far typically, but they can withdraw from future collection. So very possible within the in the application. Let's see what else we've got here.

Derk: I'll take one. So there there's two calls now two questions now on recording the consent call. I already provided one written answer, but I'll answer it again. Currently, to preserve privacy, we do not record anything. So we've specifically opted for a method where we have a peer-to-peer connection. So the only thing the back end basically does, it negotiates a connection between two browsers, basically, and then there's a direct video connection between two browsers, which means there's sort of no middle man, nothing in between that can snoop on on that, you know, encrypted video connection. However, we can configure the platform to have that man in the middle, which would be a server that can record those videos. So technically it's possible.

We don't have a a streamlined way of exposing these videos to the researcher yet, although that's relatively straightforward. But if you would like the recordings to be there safely on a secure server as sort of an audit trail of the conversation that can be retrieved through us, that is possible per project. But we would have to provide you the video recording if you if you need it. So it's really something you can you can choose, but we right now opt for no recordings to to to sort of maximize patient privacy. And we'd be happy to to change that for you for an individual project. Rowan, did you select the next one?

Rowan: Yeah, so I've got another question here around the the question about PII and whether or not it's blinded between the site and the patient. I did mention that in our in our in the overview before we got to the demo briefly. So it's not automatically blinded in the video call itself, which is I think is what the question is asking here, but it's one of the reasons that we opted to have eConsent as a separate application, is so you have completely separate user management between the the EDC, where you would typically have site staff that should not have access to the the the patient or the PII information, whereas those that are conducting the consent call would need to, because identification is typically a key component of that. Derk, did you find another one?

Derk: Let's see. Sorry, I was also typing an answer. "Does the platform allow for video remote interpreting?" That's a that's a great question. I would imagine there are plug-ins for that, but currently we do not. So currently the because it's all integrated, we've kept it relatively simple. I think it's a huge advantage of the platform that it's an integrated workflow for patients, but it does mean we don't have some of the fancy Zoom features, although I'm quite confident that those can be can be added. But right now, we don't have live translations. But it's an interesting point and I think I think our our product owner, Froukje, is also on the call, so it might be something to to look into.

Rowan: All right, well, I've got here as well. Yeah, so I've got a question here which is, are are consent comprehension tools, videos, quizzes, for example, available on the roadmap? And the answer to that is absolutely yes. On the very short-term roadmap are videos. So if you're talking about the the information leaflet, for example, available in video form, or other types of aids for comprehension of the content of the of the the consent form itself. And and quizzes as well, I would say medium-term for the quizzes.

But if you looking to a fully, fully self-service process, at the moment, most of the people we're talking to that have real use cases for that are for the lighter, you know, our studies that have much lighter regulatory requirements, and so even the requirement for for proving comprehension isn't there. But it's definitely something we're looking into, and will be added to the product.

Derk: Okay. Then another great question: "So there are a lot of countries that allow an eConsenting process, but they don't like they don't allow a digital signature, e-signature. How do we deal with that?" And so one thing we have heard from an IRB is that they would allow a wet signature, so a traditional written signature on a piece of paper that is then mailed in, and I think that would have to be supervised.

So we already know that a supervised wet signature would also be an option, which would basically mean when you schedule the call with the patient, you also mail them the paper consent form, and then you follow the exact same procedure, but except that you sign on the screen, you sign the piece of paper, and then they mail that back in. So that is another way to do it. But of course, confirm this with your with the local IRBs, because these things are tricky, they're very new, and they they typically also require quite a bit of explanation. So when you go to the IRB, be well prepared with with screenshots and information on how this platform works.

And we are actually putting together a package for you to make it easier to get that IRB approval. So what we're we're creating a a sort of a zip file full of documents that you can add to your, you know, submission, that will help you get approval, so because we then explained how this entire platform works for you. So that that would also be a relevant a thing to include there. Back to Rowan.

Rowan: Yeah, so I've got another question here. Oh, and the questions have just refreshed and it's moved down. Let me find it again. So it was a question about what the real benefits were considering Here it is. So if the consent is remote, the screening procedure and drug device supply will be another challenge in interventional trials. So what is the real benefit? So there's a number of them.

So I think we should look at this as as a hybrid scenario in in a lot of cases, so it's not always that you can do everything remote, but in every everything that you can add that reduces the the site burden on patients or on the trial team, that that improves operational efficiency is always a plus, of course.

And in this case, whether you still need to either deliver the the drug or the device directly to people's homes, which we know is happening in some cases, or whether there's still a site visit required for some of these things, then still reducing the requirement for for physical visits for other things, like the the like the the consent and the screening especially, because then you can you can have fewer people that need to come all the way to the site, even if you had a final step for a wet signature in the consent process, for example. Derk, did you want to add anything to that?

Derk: Well, we are forging partnerships with with players in this space that they can actually solve some of these logistics problems. So Castor's not going to handle the logistics for you, but we do plan to partner, integrate with with players that can actually bring things physically to a patient's home. So it's really also about considering all the options. So it's it is a lot of studies are doing this. A lot of studies are using third parties to ship devices and and sometimes even drugs, but it's highly dependent on what the drug is, to to the patient's home. So again, every study is different. It highly depends also on local regulations if you're allowed to do something like that.

But the logistics of it are it's solvable, but yes, it is an additional layer of complexity for your project, but I would argue that's still better than, you know, no project at all. Then that's that's unfortunately the age we're currently in. I got a question around scheduling, and so right now we don't handle scheduling, mostly because there's a lot of institutes that already have some kind of tool to to schedule things with patients, but we are thinking of adding, for example, a Calendly integration to to have some out-of-the-box scheduling solution that's available.

But for now, we would depend on normal scheduling scheduling practices, which could even be a phone call to to to set a date, but then you have this secure, video-enabled environment to go through the through the eConsent process.

Rowan: Okay, I've got another one here, which is, "If a protocol amendment requires an updated consent form, how would you handle that?" A great question, and obviously a common use case. So the way that that's handled is that you can update the the consent form, and the the previous the subjects that were consented on the first version remain consented on the first version with the availability of that consent form, and you have the new subjects coming in can go to the new version of the consent form, with the possibility of requesting, if necessary, to some of the prior subjects if they have not completed all of their visits, for example, to to re-consent to the second to the updated version. So depending on your needs, all of these things are also custom configurable so such that that we can make sure to meet exactly what your needs are.

Derk: Okay. Then there was a question on if it's if it can be integrated with other platforms. I'm not sure if Rowan answered that one already, but the platform has been built to to be to able to operate standalone. More importantly, it's been built with sort of an API-first strategy, so all the functionality has an API behind it, which does mean that custom integrations are are possible, and meaning that it could also be integrated with another EDC system. But obviously, that require would require a custom integration process, and the ease of that would highly depend on the, you know, the how do you say this in a polite way?

Sort of the state of the technology in the other EDC platform, as in, does this other EDC platform also have an API, for example? So those things need to be taken into consideration, but you don't have to buy our EDC platform to use this consent solution, although, obviously, we would highly recommend that. Back to Rowan.

Rowan: Yes, I can see you're already starting to type a reply, but maybe I'll go ahead anyway. This is for the the "Can you conduct UAT before go live of the eCOA or eConsent?" And the answer is absolutely yes. So in everything that we do, we expect that that's part of your process, so it's there's no no problem at all there. So you can always do thorough UAT before you go live.

Derk: And then a question on server locations or where the data are stored. So you can choose for your project where you want to run it: on the in the US, in the UK, in Australia, on our Dutch server in the Netherlands, or we can set up a private Castor Cloud for for your company or for your project in any of the Azure regions globally. Of course, this will have a certain implementation timeline and an additional cost involved, but if you are very specific about where the data needs to be stored, we can accommodate you as as long as there's an Azure region region there, or maybe as a fallback, AWS, so Amazon.

Rowan: All right, I've got a question here on, "How do you follow up with the participant if they don't respond? Also, do you provide a plan B if a participant realizes they have no good means to read it properly, etc.?" So I think this is a mix of technology and your own procedures, and depending on who your your audience is, so who your, you know, your your eligibility criteria, and whether you're expecting elderly or people with visual impairment and can't read it.

But I think we can cover most of these cases with the fact that if you're if they come in through the recruitment landing page, for example, and then there's no completion of the screening survey, you have visibility on that and you can send a reminder. And likewise, if they complete the screening survey, but they don't complete the registration on the consent, or they don't respond to your your request to to schedule a call, so you have visibility on on all of these things. Some of it can be automated, and some of it would be manual depending on what your needs are to reach out and and follow up with them.

But at in all in all cases, you would have at a minimum the information you've collected on the landing page, and so you've got that information to follow up with them.

Derk: I have a very interesting question here. If three browsers can participate in a consent call, so also the sponsor for technical support. I think it's a very interesting question. I do think the technology would allow for it. It's not something we've built right now, but it's my my only consideration is if that secure peer-to-peer connection is still possible with three people. I would have to check that, but it's a it's a great question. It's not enabled by default, but I I do expect it might be it might be possible, but that would definitely be something that we would, you know, configure for for a specific project.

Rowan: All right, I've got I've got two questions here. I'll answer them both because they're quite brief. The first one is, "Do you send email notifications to the investigator once the eConsent is provided by the participant?" And yes, absolutely. So there's configurable notifications for a number of these sort of milestones or events, and that's one that comes by default is there. And the other one is, "How much of the functionality is out of the box?" Quite a bit of it. What we what we demoed, most of it, but given the differences from one study to another, and one, you know, one protocol to the next, and how much it's needs to be integrated with other systems, there's quite often a little bit of custom configuration necessary to set it up to your needs.

Derk: Great. Let's see. I think we should be be wrapping up a little bit. There's a lot more questions that we'll try to get to after the after the webinar. Let's see. Yeah, there is a question on if the entire workflow can be mobile. So especially the patient workflow, should be, you know, fully possible on any device that has an internet connection. As I mentioned, we we we were also launching our our native ePRO app, but that doesn't have this consent workflow built in yet. But generally, the entire workflow that we've shown you is is usable on on any device. And as I said, everything we build that that is exposed to patients specifically is built to be responsive.

So they wouldn't technically need a a desktop computer, although I think we are still optimizing the the video call for for mobile, if I'm correct. So I'm not sure if that's already available on mobile, but it's something we we're working on. Maybe Rowan, you can comment on that.

Rowan: Yeah, so well, I think I think you've covered it to be honest, I think to the essentially. I was going to move on to another question first, which is that here we've got the a question from Doug, which is, "You mentioned eConsent is on a different server. How does this manifest if a patient that is involved in a cycle of recruitment, consent, ePRO, do they have a single UX?" So the question the answer to that is yes. So the the different the applications are on are different applications, but the user experience for the patient is quite consistent and and fluid. So the recruitment through to consent, at some point they have to create an account, of course, but they only have to create one. So there's no no requirement to to to have multiple accounts for the patients. So it's a it's a seamless experience.

Derk: I think we've gotten through most of the questions, so I'm I'm thinking we we can wrap it up here. I feel this was an amazing webinar, so many great questions. I'm all heated up from from the excitement and trying to answer as many questions as possible. This this webinar will, you know, will be has been recorded, so will be made available for anyone to to to watch again. Of course, you can reach out to us with any additional questions that you have, and if you're interested in the platform, interested in pricing, please reach out to us so we can connect you to the right people internally at at Castor. Rowan, anything you want to add before we before we close off?

Rowan: No, I'd just like to thank everybody for their time, and also to remind you that we will be providing more updates as we extend the product. So keep in touch. You can follow us on on on LinkedIn or or elsewhere, so keep an eye out for it. And if you have any questions that weren't answered, then feel free to follow up with us afterwards.

Derk: All right, thanks everyone for such an engaging webinar, and we look forward to to connecting with you in the future, and doing amazing research together.