Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

📲 Share or Open on Web

TrialKit can support any risk-based monitoring (RBM) models that are created outside the system in analytical or biostatistics reporting. This takes Field Source Verification to a more site/subject-specific level, rather than applying the same rules throughout an entire study. In other words, a study manager may want Monitors to verify specific data points that need review, but those requirements may vary by site, visit, or subject.

TrialKit allows for RBM models to be implemented in a couple different ways

  • Real-time through the TrialKit API from an external tool driving the RBM decisions

  • A built-in configuration tool to define the RBM rules

...

This article covers how to configure which fields require source-level verification under a known risk-based monitoring model.

Rules for what needs to be Monitored is monitored are easily defined directly from the CRFs in the study. This can be done on any CRF at any site depending on what rules are being defined. Multiple rules can be defined. The options per rule are as follows:

...

Starting date

...

Distribution: Single participant, single site, all sites

...

Access to configure these rules requires two unique permissions

...

Access to risk based monitoring on its own will only allow users to view the existing rules. Configuring those rules and saving new ones is a separate permission.

To define a new rule, open an applicable subject record that will need to be monitored. Tap the workflow settings icon indicated below.

The ability to see this icon depends on your role's permission settings (Enable Risk-Based Monitoring Function )access to configure risk-based monitoring from the study role security settings.

...


As shown in the image below:

  1. Tap the lock icons next to any of the fields on the form that need to be Monitored. 

Green = enabled (Monitor will review). 

Red = disabled (Monitor will not review)

...


To define and save the new rule, indicate a starting date and which forms the rule will apply to, and then define which subject and record(s) the rule is for. Note:

The starting date for the rule is compared to the visit/transaction date on the form, not the current date when Monitoring takes place.

The following are the rules that can be applied:

...

In the configuration above, monitoring will be required on the first three fields of the form for records with visit dates starting on March 24, 2018, for all subjects at one site for one visit.

Related articles

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@275314
showSpacefalse
sorttitle
typepage
cqllabel in ( "flsv" , "risk_based_monitoring" , "monitoring" ) and type = "page" and space = "TKSP"
labelsconfiguration
Page Properties
hiddentrue

Related issues