The FDA’s Adverse Event Reporting Requirements

The adverse event reporting system is an important highlight of the FDA’s adverse event reporting requirements. This is the mechanism through which adverse event reporting requirements are listed out for the FDA to take further action.
The adverse event reporting system may be understood as being a database that aids and supplements the FDA’s postmarketing surveillance program for all its approved products that fall in the category of therapeutic biologics and drugs. So, this database has a record of the adverse event reporting done by all individual and sponsors of their clinical trials. It is a catalog of all the error reports that get generated at various times and stages of the clinical research program.
Voluntary in nature

The outstanding aspect of the FDA’s adverse event reporting requirements is that these reporting requirements are not mandatory. Yet, those involved in clinical research, such as sponsors, healthcare and pharmaceutical organizations, institutions and individuals strictly adhere to adverse event reporting requirements in order to steer clear of legal entanglements that could come their way in the future, and to help other players keep track of all adverse events.
Some of the core adverse event reporting requirements

Applicants should electronically submit all Individual Case Safety Reports (ICSRs) for human drug and nonvaccine biologic products in xml format. Among the adverse event reporting requirements, this has been in place from 2000.

The FDA has been amending rules relating to adverse event reporting requirements from time to time. According to the amendment passed in June 2015; the following adverse event reporting requirements apply: All applicants should submit all ICSRs, ICSR attachments, and periodic safety reports electronically. They can do this using either of these options:

• Database-to-database transmission (“E2B”)
• The Safety Reporting Portal (SRP) by manually entering the data via our SRP portal.

The E2B method specifies that the files should be in xml format, and the attachments in pdf.

The Safety Reporting Portal (SRP) is meant for those applicants that do not have the database-to-database capability. To fulfill this among the FDA’s adverse event reporting requirements, the applicant needs to have an account with which to access the portal site. FDA’s adverse event reporting requirements state modes and criteria that applicants have to meet to request an SRP account, to activate the account, to add attachments, and for submitting Periodic Safety Reports (PSR).
click to continue reading

Comprehensive risk management is a must for medical device software

Diligent, complete and correct implementation of risk management of software used in medical devices that takes into consideration the gaps and corrects them from the start of product development is absolutely imperative. This is because of two critical reasons:

    1.      Gaps, incorrect or incomplete implementation can retard or delay or make the certification/approval of medical products impossible;

    2.      Since most activities are closely linked to the development lifecycle; almost none of it can be retrospectively performed. This renders all activities performed till the identification of gaps useless and redundant; making it necessary to start from the beginning, no matter at what stage an anomaly is discovered.

Embedding software risk management into the bigger scope of overall risk management is the way forward if these fiascos have to be avoided.

Learn the ways of doing it right from start till finish 

The proper ways of how to take all the necessary steps for designing, implementing and testing critical medical device software in a regulatory compliant environment will be the learning a two-day, live seminar being organized by GlobalCompliancePanel, a very respected provider of professional trainings for the regulatory compliance areas will impart.

Markus Weber, Principal Consultant with System Safety, Inc., who specializes in safety engineering and risk management for critical medical devices, will be the course Director. To participate in this very important seminar, please log on to http://www.globalcompliancepanel.com/control/globalseminars/~product_id=900683SEMINAR.

In line with globally applicable standard requirements

International consensus, reflected in globally applicable standard requirements such as ISO14971 and IEC62304, has led to risk management being a mandatory component of almost any activity in the medical device industry. This course will explain these requirements.

Given that software risk management has to be embedded into the bigger scope of overall risk management; Markus will introduce all the steps necessary to design, implement and test critical medical device software in a regulatory compliant environment while adhering to the principles of risk management. In addition, he will also address the system level risk management and the resulting interfaces to software.

Understanding safety assurance cases

The 'Safety Case' or 'Assurance Case' document is a well-established method to collect all safety related information together in one place to comprehensively summarize all risk related activities and to demonstrate the safe properties of a device. Currently only required for FDA infusion pump submissions; this documentation will most likely become mandatory for all devices. This course will introduce the basic concepts and content of safety assurance cases and will illustrate their usefulness for internal and external review of safety related information.

This seminar will use real-life examples and proven tips and tricks to make the application of risk management a practical and beneficial undertaking. It will address the system level issues of risk management as well as the increasingly important software related issues of critical systems. The concept of an assurance case will be introduced to make the combined effort towards designing, implementing and verifying a safe device transparent. The outcome of this learning is that it will help to comply with regulatory requirements with minimized overhead and resource burden.

      

Comprehensive risk management is a must for medical device software

Diligent, complete and correct implementation of risk management of software used in medical devices that takes into consideration the gaps and corrects them from the start of product development is absolutely imperative. This is because of two critical reasons:

    1.      Gaps, incorrect or incomplete implementation can retard or delay or make the certification/approval of medical products impossible;

    2.      Since most activities are closely linked to the development lifecycle; almost none of it can be retrospectively performed. This renders all activities performed till the identification of gaps useless and redundant; making it necessary to start from the beginning, no matter at what stage an anomaly is discovered.

Embedding software risk management into the bigger scope of overall risk management is the way forward if these fiascos have to be avoided.

Learn the ways of doing it right from start till finish

The proper ways of how to take all the necessary steps for designing, implementing and testing critical medical device software in a regulatory compliant environment will be the learning a two-day, live seminar being organized by GlobalCompliancePanel, a very respected provider of professional trainings for the regulatory compliance areas.

Markus Weber, Principal Consultant with System Safety, Inc., who specializes in safety engineering and risk management for critical medical devices, will be the course Director. To participate in this very important seminar, please log on to

http://www.globalcompliancepanel.com/control/globalseminars/~product_id=900681SEMINAR?risk-management-medical-devices-Boston-MA.

In line with globally applicable standard requirements

International consensus, reflected in globally applicable standard requirements such as ISO14971 and IEC62304, has led to risk management being a mandatory component of almost any activity in the medical device industry. This course will explain these requirements.

Given that software risk management has to be embedded into the bigger scope of overall risk management; Markus will introduce all the steps necessary to design, implement and test critical medical device software in a regulatory compliant environment while adhering to the principles of risk management. In addition, he will also address the system level risk management and the resulting interfaces to software.

Understanding safety assurance cases

The 'Safety Case' or 'Assurance Case' document is a well-established method to collect all safety related information together in one place to comprehensively summarize all risk related activities and to demonstrate the safe properties of a device. Currently only required for FDA infusion pump submissions; this documentation will most likely become mandatory for all devices. This course will introduce the basic concepts and content of safety assurance cases and will illustrate their usefulness for internal and external review of safety related information.

This seminar will use real-life examples and proven tips and tricks to make the application of risk management a practical and beneficial undertaking. It will address the system level issues of risk management as well as the increasingly important software related issues of critical systems. The concept of an assurance case will be introduced to make the combined effort towards designing, implementing and verifying a safe device transparent. The outcome of this learning is that it will help to comply with regulatory requirements with minimized overhead and resource burden.