Hershal
11th March 2009, 05:08 PM
This is the next in the series regarding ISO/IEC 17025:2005 to give some idea regarding the Clauses. As always, this is not from the Oracle of Delphi, so your input is sought also.
ISO/IEC 17025:2005 Clause 4.14 including the sub-Clauses, addresses the internal audit.
Internal audits are often looked upon as bad, but they don't have to be; infact properly done they are good things. First though we need to understand the role of the internal audit.
Internal audit is like a full physical exam you get from your doctor. They take the height and weight and blood pressure and temperature, EKG, other tests too. Some tests we might consider invasive but they are necessary. Intruth internal audits are invasive and disruptive also, but necessary.
Not necessary just because the Standard requires it, but it is a good monitoring tool. In ISO/IEC 17025:2005 it should NOT be considered the ONLY monitoring tool however, and we will discuss others later.
In ISO/IEC 17025:2005 Clause 4.14.1 the internal audit is required to look at the QMS of course but ALSO at the technical operations of the lab. Small labs of course will find this challenging just the same as for Management Review. In larger labs, it may be a littl easier as more people are available, but may not be technically qualified for given operations.
The Standard suggests a one year time to complete the internal audit of all lab operations. However, take this as Gospel. After all, try to take two years or three and see if your AB lets that go!
There must be a predetermined schedule and procedure. Small labs that do everything with quality manual and cal procedures can include this in the quality manual easily. Don't over-engineer this. Most of the time your chosen AB will likely give you their 17025 checklist (not all will though) and then change the headers and use that.
You need to include a schedule also. This may be as basic as simply stating a month in the year, included in the procedure, or could be as detailed as specific departments on specific days. The detail will vary lab to lab, but must be reasonably appropriate to the lab. And of course, the assessor will look to see if the documentation supports the internal audit as covering QMS and technical operations, and whether the audit is effective.
Clause 4.14.2 requires the audit to review whether the operations are effective, and whether the results are correct and valid. The effectiveness is somewhat interpretive, but if incorrect results are going out, review of reports/certs is not done, etc., then the operations may not be effective. This needs to be documented in the internal audit.
The lab has to take "timely" corrective action. The term is interpretive, but the time needs to be resonable, and follow-up to assure effectiveness needs to be done also. Oh, make sure the corrective action system is used, and that non-conformances are reviewed in Management Review.
One other point here that is also mentioned in Clause 4.9.1.d and .e is the potential to have to notify customers and recall work. This comes directly from the effectiveness or lack of, and if the system is not effective then it must be documented under Control of Non-Conforming Work and use the corrective action system.
Clause 4.14.3 basically means keep the documentation, which parallels Clause 4.13.1.1 concerning records.
Non-conformances need to be followed up on once resolved, and that also must be documented.
Now, here is the summary, time for you the reader to share experiences, tips, tricks, etc. with everyone else!
ISO/IEC 17025:2005 Clause 4.14 including the sub-Clauses, addresses the internal audit.
Internal audits are often looked upon as bad, but they don't have to be; infact properly done they are good things. First though we need to understand the role of the internal audit.
Internal audit is like a full physical exam you get from your doctor. They take the height and weight and blood pressure and temperature, EKG, other tests too. Some tests we might consider invasive but they are necessary. Intruth internal audits are invasive and disruptive also, but necessary.
Not necessary just because the Standard requires it, but it is a good monitoring tool. In ISO/IEC 17025:2005 it should NOT be considered the ONLY monitoring tool however, and we will discuss others later.
In ISO/IEC 17025:2005 Clause 4.14.1 the internal audit is required to look at the QMS of course but ALSO at the technical operations of the lab. Small labs of course will find this challenging just the same as for Management Review. In larger labs, it may be a littl easier as more people are available, but may not be technically qualified for given operations.
The Standard suggests a one year time to complete the internal audit of all lab operations. However, take this as Gospel. After all, try to take two years or three and see if your AB lets that go!
There must be a predetermined schedule and procedure. Small labs that do everything with quality manual and cal procedures can include this in the quality manual easily. Don't over-engineer this. Most of the time your chosen AB will likely give you their 17025 checklist (not all will though) and then change the headers and use that.
You need to include a schedule also. This may be as basic as simply stating a month in the year, included in the procedure, or could be as detailed as specific departments on specific days. The detail will vary lab to lab, but must be reasonably appropriate to the lab. And of course, the assessor will look to see if the documentation supports the internal audit as covering QMS and technical operations, and whether the audit is effective.
Clause 4.14.2 requires the audit to review whether the operations are effective, and whether the results are correct and valid. The effectiveness is somewhat interpretive, but if incorrect results are going out, review of reports/certs is not done, etc., then the operations may not be effective. This needs to be documented in the internal audit.
The lab has to take "timely" corrective action. The term is interpretive, but the time needs to be resonable, and follow-up to assure effectiveness needs to be done also. Oh, make sure the corrective action system is used, and that non-conformances are reviewed in Management Review.
One other point here that is also mentioned in Clause 4.9.1.d and .e is the potential to have to notify customers and recall work. This comes directly from the effectiveness or lack of, and if the system is not effective then it must be documented under Control of Non-Conforming Work and use the corrective action system.
Clause 4.14.3 basically means keep the documentation, which parallels Clause 4.13.1.1 concerning records.
Non-conformances need to be followed up on once resolved, and that also must be documented.
Now, here is the summary, time for you the reader to share experiences, tips, tricks, etc. with everyone else!





