Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<61f6f4390504111150124d7f3d@mail.gmail.com>
Date:	Mon, 11 Apr 2005 14:50:31 -0400
From:	Jim Drash <jim DOT drash AT gmail DOT com>
Reply-To:	Jim Drash <jim DOT drash AT gmail DOT com>
To:	Jan DOT Schormann AT brainlab DOT com, cygwin AT cygwin DOT com
Subject:	Re: FDA-conform validation - any hints?
In-Reply-To:	<KCEOLMMHICICJKHPFOALMEAGDDAA.Jan.Schormann@BrainLAB.com>
Mime-Version:	1.0
References:	<61f6f43905041107485bf456d7 AT mail DOT gmail DOT com> <KCEOLMMHICICJKHPFOALMEAGDDAA DOT Jan DOT Schormann AT BrainLAB DOT com>
X-IsSubscribed:	yes

Jan:

I work for a very large FDA-regulated company. Our FDA IT audits have
been centered on having documented processess and appropriate sets of
test protocols to show compliance to those processes.

Your validation efforts around GNU tools must describe what is your
intended use and how you would test that.  Please note that this is
around your use of a given piece of software not anyone elses.

So given that you are using some GNU tool as part of your process,
then you the to have the proper work instructions and scope statements
around your use of the tool.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -