Define and enforce status for each study

A research study often is in one of the following states:

  • Study design and implementation
  • Field deployment and data collection
  • Data analysis

In each face, certain features are more important. For example, ability to debug the study, and see each step the platform takes during the “Study Design” is very important. As participants are testers in this phase, they may also want to see some additional details about the study progress.

In contrast, during the field deployment, tracking the progress is very important, and any changes to the study should be done very cautiously. The system should ensure the researcher understand the consequence of some of these changes.

As part of this feature, each study should have a status, chosen from one of the above options. For the first implementation, only the status definition is sufficient. no further changes needed.


Category: Study - Enrollment

Internal IDs:

  • Ticket # Z-25936: In this ticket, researcher created a test study, enrolled all participants, and then set the license, and because of this all his participants are Test!
  • Ticket # Z-30555: Researcher enrolled all participants and then started verifying her protocol.
  • Epic # ET-7122