Accessing and Using the TrialKit CTMS Tool
TrialKit has always provided a solution for collecting data at various levels (User, Site, Study, and Subject). The new CTMS Center, currently found only on the iOS mobile app, joins all that data collection into one central area for viewing and tracking.
Many features will be added to this in coming months, so stay tuned for more features!
NOTE: The CTMS Center is currently found only on the iOS mobile app
The CTMS Center is also where the current study's Dashboard or the host's Trial Master File can be accessed.
Accessing the CTMS Center
Prerequisite: The user's host-level role has Access to CTMS
The CTMS option can be found in the bottom navigation bar on the iOS mobile app
There are three possible sections, depending on the viewing user's form rights:
- User level information
- Site level information
- Study level information
Additionally at the Site and Study levels, they are further broken down into Host level and Study level. For example, a study level site form might be something like IRB Approval information. A Host level Site form might be something like Site Contact information - because it's information that is not specific for any one study that the site is being used in.
That level of granularity requires a user to select which study they are currently viewing information for:
If the study selection is changed, that will change the location of the user. In other words, if you exit the CTMS and open the Subject Manager, the subjects will be displayed for the study that was selected in the CTMS.
Navigating the Tables
The columns and details displayed in the tables are based on what has been configured by an Administrator. That is discussed in the next section below.
There is potential for a large amount of information in a small view, so each table can be adjusted as needed with the notch at the bottom of each table:
Tapping any record will open the form to see the full details or add/edit, depending on permissions.
Configuring the CTMS
The tables and information displayed in the tables must be pre-defined within the form builder, via the field property shown here:
