Safety Database

The documentation of SAEs requires the recording of sensitive data that is documented in the safety database application in encrypted fields. Decrypting these fields and assigning roles with access to decrypted fields is entirely in your hands.

In the application, SAE messages are recorded manually in a user friendly case input mask. A case can be assigned to a sponsor and (especially in the context of clinical trials) a study and a site. In one case, both several individual (belonging together) and follow-up SAE messages can be documented.

The input mask contains all the necessary and optional input fields that are described in the most up-to-date version of the ICH guideline E2B Revision 3 and the subsequent EU Business Rules. The EU case-specific fields are always optional in order to fully document cases that are independent of EU regulations.

The documented cases can be filtered and sorted with the most important parameters on overview pages and downloaded as Excel lists.

You are supported in the documentation by tool tips and by direct feedback upon violation of documentation rules in order to report compliant to ICH guidelines.

Once all content has been recorded in compliance with the rules, a complete report in PDF and XML format can be created in the system. The PDF form corresponds to the layout of EudraVigilance and can be used for complete data transmission for authorities and other recipients. The XML file is automatically checked by the application against the current ICH schema when it is created and can be transmitted digitally at EudraVigilance via EVPOST directly out of the application.

The AMEDON safety database has its own gateway for this purpose, whose compatibility and function has been confirmed by EudraVigilance after passing all necessary test steps. The validated gateway connection also enables the user to view the electronic receipt confirmations (MDN & ACK) of the EMA directly in the application.

Regardless of ICH compliant EudraVigilance reporting, you are always able to generate a CIOMS form, which is mainly used when reporting to ethical authorities. Reports such as line listings and reconciliation listings can be created and exported from the database at any time to meet the obligations of regular reporting and control of pharmacovigilance data.

The framework of the safety database allows you to make adjustments to your workflows in various ways.

The application provides a special “page” to document additional case or event (SAE) -specific information. The contents are variable and you can choose from a range of suggestions or implement your own ideas with us.

Furthermore, the framework allows to extend the scope of services. For this purpose, additional pages or organizational levels can be constructed based on your specific request.

The existing reports Line Listing and Reconciliation Listing can be adapted at any time with little effort. Additional reports can also be ordered and added, also without application downtime. It is also possible for you to create and use your own reports by means of a data warehouse license.

With an additional documentation area, the safety database can in addition or exclusively be used in vigilance of medical devices.

Additional input fields enable the documentation of serious adverse events and device deficiencies in accordance with directives 90/385/EEC and 93/42/EEC. The data collected in this way is presented in a specially developed report compatible with MEDDEV 2.7/3.

The data documented and reported in this way is filed in case and event documentation in the safety database analogous to pharmacovigilance. Thus, you are already setting the course for a controlled recording and monitoring of incidents in medical device development with a view to a later implementation of the EU Regulation 2017/745 (MDR).