This manuscript discusses the data validation environment from the user's perspective. It covers what must be validated, who is involved in validation, when validation should occur and what it must include, why validation is necessary, the use of test cases, and feedback. It is critical that all users of software have an understanding of validation—including its purpose and how (generally speaking) to perform data system validation. A validation system that is properly planned and executed is an invaluable tool in ensuring that new business software meets the end user's expectations and needs.
Code of Federal Regulations, Title 21, Vol 8, Parts 800–1299. US Government Printing Office, April 1, 2000.
3.
BaldwinD.“Software Development Life Cycles: Outline for Developing a Traceability Matrix.”The Regulatory Forum. www.regulatory.com/tracedoc/html.
4.
General Principles of Software Validation. Draft Guidelines version 1.1. Rockville, MD: US Department of Health & Human Services, Food and Drug Administrations, Center for Devices and Radiological Health; June 1, 1997. www.fda.gov/cdrh/comp/swareval.htm.
5.
Guidelines for the Content of Premarket Submissions for Software Contained in Medical Devices.Rockville, MD: US Department of Health & Human Services, Food and Drug Administration; May 29, 1998.
