What this is, and who it is for
An event is something that happens to a participant off the schedule: an adverse event, a medication started, another event the study tracks. It has a form of its own, designed for the study (Design forms), and a place in the participant's Events page and in the study's AE Log. An adverse event that is serious is upgraded, which starts a reporting clock and opens the safety trail (Review a serious event).
| You need | To |
|---|---|
clinical.event.write (site coordinator, principal investigator) | Record, upgrade, close and remove an event |
clinical.event.report (project manager, data manager, medical officer, principal investigator) | Mark an initial report sent and correct the awareness time |
clinical.event.read | See events and the logs |
Held by: Principal Investigator, Clinical Research Coordinator (clinical.event.write).
Where to find it
A participant's AEs & medications page (tables of Adverse events, Serious adverse events, Concomitant medications and Other events, each with a Record … button); a visit's Events found at this visit list; and the study's AE Log, one entry per adverse event, read from each event's own form.
What you can do
Record an event
- On the Events page choose Record adverse event (or Record medication, Record other event); or Record event here on a visit. The dialog Record an event: Something that happened to the subject off the schedule: an adverse event, a medication started. It has a form of its own to fill in.
- What kind of event (the kinds the design has; This study's design has no event form to record. A designer adds one in Build. otherwise).
- What happened: in your words, with what you know now. The form takes the detail.
- Found at: A visit or A contact (a call, a letter or a meeting that is not a visit).
- Choose Record event. The event form opens: fill it in and submit it like any form (Enter visit data). Each event form has a kind that the designer sets in Build (
aeadverse event,saeserious adverse event,conmedconcomitant medication,other) and standard fields the logs read by their role: for an adverse event the term, description, onset, end, medications, relatedness, severity, outcome and note; for a medication the medication, dose, unit, route, indication, start, stop and remarks.
- Opens the dialog that records an event.
- Causality as the site judged it.
Record a contact
Record a contact (A call, a letter or a meeting with the subject that is not a visit. An event learned of at a contact can be linked to it.): How you were in touch, When it took place, What it was about. A contact can be removed with a reason. Contacts are the record of attempts to reach a participant before they are declared lost to follow-up.
Close, upgrade, correct, remove
Each event row's Actions:
- Open form: the event's form.
- Upgrade to serious…: for an adverse event that turns out to be serious (below).
- Correct awareness time…: change when the site became aware of a serious event (below).
- Mark the event closed / reopen: Closing says the event is finished and nothing more will be added. The dialog lists what is still open on it (queries, follow-ups) before you confirm.
- Remove…: with a reason; the event stays in the record, marked Removed, and leaves the logs' default view (the log has Include removed events).
Upgrade to serious
Choose Upgrade to serious… on an adverse event. The dialog asks:
| Field | Notes |
|---|---|
| When the site became aware that it was serious | Starts the clock: The initial report is due a set number of hours after this, by the study's design (24 hours unless the version says otherwise) |
| What makes it serious | Tick one or more: Death, Life-threatening, Hospitalisation, Disability, Congenital anomaly, Medically important |
| Why, if more than that says | Free text |
| Learned of it at a contact | Link to a contact, if it was learned of that way |
The event now appears in the SAE Log with its report status Report pending and a due time. A serious adverse event is the upgrade of an adverse event; both forms must exist in the design (Design forms).
- Makes the event a serious adverse event and starts its reporting clock from the time of awareness.
Mark the initial report sent
On the SAE Log or the Events page, Mark report sent (or not required) with the date: This says the initial report went to the regulator, and when. It is final: a report that was sent cannot be withdrawn or reopened here, and its awareness time can no longer be changed. Trialion does not send the report; it records that you did (Not built yet).
Correct the awareness time
Correct awareness time… moves the deadline: it asks Why the time is being corrected (recorded).
Every option
The logs
The AE Log and the SAE Log list one entry per event, with filters and sort, and an Export of each to CSV or Excel (Export data). The SAE Log shows the report status, the due time, an overdue flag, the follow-ups, the medical review and the reconciliation. Site staff see the report and follow-up columns but not the medical review or reconciliation.
What the system records
event.recorded, event.upgraded_to_sae, event.status_changed, event.removed, event.awareness_changed, event.report_status_changed, contact.recorded, contact.removed, plus the form's own field-level audit. See Audit events.
What you cannot do, and why
- Delete an event. It is removed with a reason and kept.
- Withdraw or reopen a sent report, or change its awareness time.
- Record an event with no event form in the design.
- Review or reconcile as a site person (a different permission).
Compliance Q&A
Yes. The upgrade records the criteria and the time of awareness; the deadline is that time plus the version's setting (24 hours by default) and the log flags an overdue report; correcting the time needs a reason and is recorded.
Limits: the system does not tell anyone the deadline is near, and does not send the report. See Review a serious event and Not built yet.
Evidence: server/src/modules/study/events (awareness time, due time from the version setting saeInitialReportHours, report status)safety-logs
Related
Review a serious event · Safety reporting · Change a participant's status · Report a deviation