As we discussed last week, over the next few weeks we’ll be looking at how Patient Engagement can effect clinical trials. In order to move on to architecture (next week – February 4th) and the business value (February 11th), we need to discuss the required features.
There are core features (architectural components?) of Patient Engagement in Clinical Trials:
Ok, so one could argue that both of those are architectural components. But if we detail out the features of each, they simply become containers by which we can understand the full feature set. Let’s look at them individually.
These have been around for quite awhile – so we’ll deal with them briefly. Many consider an Investigator Portal to be merely a component of CTMS (clinical trial management system). There are others who feel that they can be (and are) stand-alone applications. When thinking about this use for Patient Engagement there are some additional features in an investigator portal that need to be supported.
These are relatively new in the clinical trials realm. They have a broad range of features, primarily focused on keeping patients engaged with the study, but also driving down the cost of clinical trials by capturing more data directly from the patient (through Connected Devices) which lowers the number of visits are required to the investigational site.
Below is a table of just some of the features:
Investigator Portal Features:
Clinical Trial Patient Portal Features
Again, these are just some of the features and requirements for patient engagement in clinical trials. If you think I’m missing some, please feel free to send me an e-mail at firstname.lastname@example.org
Until next week!