...

Introduction

An event (or a visit) represents a package of eCRFs that contain data that relate to a specific visit. 

 E.g. This normally represents a visit from a patient to a physician or a phone call with the patient. For example, at day 8 of a cycle lab work has to be done or every 8 weeks there's a survival phone call.

An EventGroup represents several events that are considered as to occur in a defined period of time is a collection of events in a certain sequence from a start date up to an end date of that group of events (the visit dates of the individual events fall within start and stop of the EventGroup).

  E.g. For a treatment cycle the protocol defines a visit at day 1, day 8 and day 15. The EventGroup is 'cycle' and the events are 'day 1', 'day 8' and 'day 15'; the visit date of day 1 would normally be the start date of the EventGroup and the visit date of day 15 cannot be after the end date of the EventGroup.

Anepoch is a planned period of study participation (cfr. CDISC standards).

E.g. screening, treatment or follow-up.

Depending on the study specific settings, study specific events can be available by default in the data section or can be dynamically triggered by the subject specific activities initiated in the study flow. 

Overview

The overview of events/EventGroups shows 3 types.

Type

Type	Description
Scheduled	The event was planned as described in the protocol. Scheduled events correspond to sets of forms that are expected to be collected for each subject as part of the planned visit sequence for the study.
Unscheduled	The event was not planned according to the protocol. Unscheduled events are available to report data that may or may not occur for any particular subject.   A set of forms that are completed for an extra lab assessment (for example due to observed toxicity) which is not expected by the protocol. Or a lab assessment that is normally scheduled per protocol, but was done clearly outside protocol windows.
Common	The event is described in the protocol, but there is no specific visit in which it is planned. It is a randomly occurring event.  An adverse event or a concomitant medications log.

Category

Within these types, events and eventgroups are EventGroups are ordered according to category. The most obvious would be to group several events/eventgroups EventGroups in an epoch. It is possible to hide the content of a category by collapsing it.

 When a category is considered " clean " or "no Issues"or without issues, the category is minimized by default. In case of missing, incomplete or data with issues, the category remains as maximized by default always maximized. 

Image RemovedImage Added

Dates

Visit Date

Within an event a visit date can be requested. When a visit date is collected, the date is displayed in the events overview. 

Start and End Date

Within an eventgroup...

Event(Group) Validation Status

Options

Several options are available at event(group) level. 

Audit trail

The user can access the audit trail  via the  icon. The audit trail will display all actions up to that specific level.

...

After confirming the user will receive a warning that this actions induces a deletion of all forms within the event and a second confirmation has to be provided.

Navigation

In case the event is dynamically triggered by the activity initiated in the study flow, a navigation button is available for the user to easily access the corresponding activity in the study flow section. Like that the user can verify if sufficient data is completed to initiate the next activity in the subject specific pathway.

The activity details will indicate the status of the eCRF completion of the corresponding event.

...