Careful design of database components will enhance the utility of adverse event databases. Key elements of database software design are described. Methods are suggested to facilitate data entry and report generation, and to increase flexibility in adapting to changing needs and overall dependability of the systems used to capture, track, and/or report adverse event information.
21 Code of Federal Regulations. Washington, DC: Federal Register. April 1, 1990; §312.32, 314.80.
2.
FlanneryEJ. Reporting foreign ADRs and ADRs in phase IV studies, and the significance of the causality assessment. Food Drug Cosmetic Law J. 1991;46: 43–57.
3.
‘COSTART’ Coding Symbols for Thesaurus of Adverse Reaction Terms. 3rd Edition. Rockville, MD: Food and Drug Administration; 1989. Dept of Health and Human Services, Public Health Services.
4.
International monitoring of adverse reactions to drug. Adverse reaction terminology. Uppsala, Sweden: WHO Collaborating Centre for International Drug Monitoring; 1986.
5.
CurranCFBawaO.Implementation of a worldwide drug safety surveillance system. Drug Inf J. 1990;24: 605–614.
6.
ThompsonWL. Adverse drug reactions: Finding sharp safety signals in a noisy haystack. Food Drug Cosmetic Law J. 1991;46: 487–496.
7.
CassidyRV. Standard tables and prompting systems. Drug Inf J. 1984;18: 43–48.
8.
DobbsJH. Exchange of worldwide safety surveillance data via an international computer database. Drug Inf J. 1988;22: 71–74.
9.
HostelleyL.Reporting and tracking spontaneous adverse experience reports via a computer database. Drug Inf J. 1989;23: 171–177.
10.
TealTWDimmigAL. Adverse drug experience management. A brief review of the McNeil pharmaceutical system. Drug Inf J. 1985;19: 17–25.
11.
AndersonW.Software validation techniques. Drug Inf J. 1987;21: 461–469.
12.
FryJDDrewRT. Creation and implementation of a computer validation program. Drug Inf J. 1992;26: 103–108.
13.
TilsonHH. Discussion panel: Database management and reporting systems of foreign-based companies. Drug Inf J. 1989;23: 197–202.
