--- title: "Using TrialKit For a Safety Database" slug: "using-trialkit-for-a-safety-database" updated: 2026-11-12T16:04:29Z published: 2026-11-12T16:04:29Z canonical: "help.trialkit.com/using-trialkit-for-a-safety-database" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.trialkit.com/llms.txt > Use this file to discover all available pages before exploring further. # Using TrialKit For a Safety Database **TrialKit can be configured as a study-level safety database for collecting, reviewing, coding, and tracking safety events. That is different from claiming it replaces a full pharmacovigilance system for regulatory case processing and submissions.** It can serve as the study’s operational safety repository when the sponsor’s requirements are met and the configured workflow is validated. ## What a safety database does A safety database is the controlled record of adverse events and their assessment over time. It helps a sponsor answer: What happened, how serious was it, could the product have caused it, what follow-up is needed, and who needs to be informed? Its core functions include: - **Case collection:** Capture the patient, reporter, suspect product, event, relevant medical history, medications, labs, and supporting documents. - **Safety assessment:** Document severity, seriousness, causality, expectedness, outcome, and medical review. Severity and seriousness are different: severity describes intensity; seriousness concerns outcomes such as hospitalization or death. - **Case management:** Track initial reports, follow-up information, queries, review, approval, and closure while preserving history. - **Medical coding:** Standardize event and medication terminology so cases can be searched and analyzed consistently. - **Reporting and oversight:** Produce case reports, line listings, summaries, and data for ongoing safety review. A full pharmacovigilance platform often adds duplicate detection, country-specific reporting rules and deadlines, electronic individual case safety report (ICSR) submissions, aggregate reporting, and signal detection across studies and marketed products. ## How TrialKit fits TrialKit provides many of the building blocks needed for the study-level workflow. The safety database would be a configured application of TrialKit’s forms, logic, coding, review, and reporting capabilities, rather than simply turning on an AE form. ### 1. Collect structured AE and SAE cases Build an adverse event log with a separate record for each event. Configure fields for onset and resolution dates, severity, seriousness criteria, product relationship, action taken, outcome, narrative, and sponsor assessment. Related forms can hold follow-up information and supporting clinical details. TrialKit specifically recommends log forms rather than normalized tables for adverse events, making each event independently reportable. See [Study Database Design and Modeling](https://help.trialkit.com/docs/study-database-design-and-modeling.md). ### 2. Notify the safety team and track follow-up Conditional actions can send emails when qualifying data is saved, such as an event being marked serious, and optionally create a follow-up task. The notification content can include information from the triggering form. That supports an initial SAE notification workflow, but an email alert is not the same as a regulatory submission or a validated reporting-deadline engine. Notification recipients, trigger conditions, and blinding behavior need careful testing. See [Email Notifications and Tasks](https://help.trialkit.com/docs/conditional-actions-email-notifications.md). ### 3. Support medical review and coding Role-based review levels can be configured for activities such as safety review, medical assessment, and investigator sign-off. Queries support clarification; locking and electronic signatures support controlled approval. TrialKit Coder supports MedDRA and WHO Drug coding, manual and automatic coding, coding queries, and coding review. These capabilities let the safety team work with standardized terminology rather than inconsistent free text. ### 4. Maintain history and generate outputs TrialKit supports audit exports, archived record versions, role-filtered data exports, and document templates populated from collected data. These can support safety listings, case summaries, and configured SAE report documents. The documented export formats include CSV, Excel, SAS XML, and CDISC ODM. XML export alone does not establish E2B compatibility. ## A practical TrialKit safety workflow Site enters AE → seriousness condition triggers notification → safety team reviews and queries → medical assessment and coding are completed → follow-up is collected → case is approved → reports or data are provided to the designated recipient or external safety system. Using the same underlying study records can reduce duplicate entry and reconciliation, although any separate safety records or external systems still need a defined reconciliation process.