Originally posted by Al Dyer:
Sure they can, but think of the following:
- The situation will need to be addressed in your document control procedure.
- What would be the methodology to ensure current revision levels and updates to the document?
- How much time would it take to just transcribe the instructions into your own (Word) document and control it under the current method?
Just a couple of items to consider.
ASD...
I'll throw in a strong reason
for using manufacturer's procedures under a 17025 system. Two words -
Method Validation. The manufacturer (should) know how to properly test the device. But, in the instance that you have only a few procedures to deal with (<100) I would write my own and document that the method is from the manufacturer, as Al stated.
Document control of manufacturer procedures is a nightmare in most cases, as most manufacturers do not tell you when the procedure has been updated, and most often you must
pay for the new procedure. My company uses literally thousands of procedures, and to pay $40 each every few years would be financial suicide.
Another problem with manufacturer's procedures is the equipment that it calls out for use. No lab has everything that every mfr procedure calls out, and substitution on the fly requires quite a time investment in researching what you have, what its uncertainty is, possibly several items to perform the function of one, and so on. The ability to make proper, informed decisions on this substitution is quite often out of the realm of the standard technician, and again, the substitution must be validated. You would save time in the long run by importing the document and tailoring it to your exact capabilities.
In other words - What Al said.
Ryan