I would like to ask for your opinion regarding our practice of declaring several minor non-conformities as a major non-conformity. The minor findings may be found in one or several departments and we usually call this system non-conformity.
Answer
I agree with that practice and use it myself in my audits. If I find several minor nonconformities about a similar topic throughout an organization, I normally write a major nonconformity because it is a systemic problem and each previous minor nonconformity support that conclusion.
Question 2
Another thing is whenever there are 3 or 4 observations, we elevate and consolidate them into a non-conformity.
Answer 2:
About observations I have a problem. There is no ISO 9000:2015 or ISO 19011:2018 definition of observation. What do you consider an observation? Your findings either are conformity or nonconformity. If they are conformities and you think there is an opportunity for improvement it is your opinion based on your experience. You as auditor can suggest that there is an opportunity for improvement. What do you consider as an observation?
Answer
Yes, it is fairly common a certification audit being about more than one standard. For example, a combined audit concerning ISO 9001 and ISO 14001, or even a combined audit concerning ISO 9001, ISO 14001 and ISO 45001. If an organization has implemented an integrated management system and wants to obtain its certification it has to contact a certification body and agree on the terms. Again, it is a fairly common situation.
It is a mandatory requirement to inform the customers of the complaint if it is pertaining to a medical device recall or a field safety corrective action as the customers might need to quarantine any stocks that have been sold out or are currently in their warehouse. You should be looking at clause 8.2.2 Complaint handling which provides you with more information on the procedure of complaint handling. With regards to clause 7.2.3, it means that the company should have a way to get feedback from a custom er with regards to the purchased product or services (quality or not quality related), including complaints.
In order to manage risk for the QMS, you will need to identify critical processes or parameters that will affect the safety and performance of the device that you are dealing with or the service that you will render for the medical device. This will be followed by a quick assessment using FMEA or any suitable matrix to assess the occurrence and severity in which you will also propose controls to mitigate the risk and implement them accordingly. All the information should be documented in a risk management report. What I have just summarized was basically in the following steps: Risk Analysis, Risk Evaluation, Risk Control, and Residual risk evaluation.
As for the clinical evaluation, you need to assess the safety and performance characteristics of the device that will affect its intended uses. You can base the evaluation on the IFU( Instructions For Use) that will be supplied to the client.
As per reference to ISO 11607, sterile barrier system means minimum package that prevents ingress of microorganisms and allows aseptic presentation of the product at the point of use.
First it is important to note that a RACI matrix is not mandatory for ISO 27001.
Considering that, there is no definitive RACI chart for this situation, because organizations are free to implement ISO 27001 controls as best fits them, but in a general manner the roles to include in such RACI matrix should consider at least:
- Top management / CISO as Accountable for controls implementation decisions
- Risk owners as Responsible for the overall controls implementation and operation
- Team members as Responsible for tasks / activities related to controls implementation and operation
- Units Heads / Processes Owners / Asset owners / Interested Parties as Consulted about controls to be implemented
- Employees / Users / as Informed about implemented controls
ISO 27001 does not prescribe retention periods for documents, but requires an organization to define them, and you can do that based on legal requirements (e.g., contracts, laws, regulations, etc.) the organization must comply with, business needs, and results of risk assessment.
As one example you can consider that for a ISO 27001 certified ISMS, you must retain obsolete documents at least for as long as the next certification audit is (i.e., a three year retention period).
Answer: The implementation of ISO 27001 is quite similar regardless the industry and size (what differs is the quantity of resources and complexity of deliverables), and the general steps are:
1) getting management buy-in for the project;
2) defining ISMS basic framework (e.g., scope, objectives, organizational structure), by understanding organizational context and requirements of interested parties;
3) development of risk assessment and treatment methodology;
4) perform risk assessment and define risk tent plan;
5) controls implementation (e.g., policies and procedures documentation, acquisitions, etc.);
6) people training and awareness;
7) controls operation;
8 performance monitoring and measurement;
9) perform internal audit;
10) perform management critical review; and
11) address nonconformities, corrective actions and opportunities for improvement.
Regarding implementation approaches, the most common are:
- Use your own staff to implement the ISMS
- Use a consultant to perform most of the effort to implement the ISMS
- Use a consultant only to support the staff on specific issues, leaving the organization's staff with most of the implementation effort.
Answer: ISO 27001 does not prescribe the specific need for a risk committee, only that relevant information security responsibilities are defined, so you can assign responsibilities for risk management the way it best fit your organization (e.g., you can adopt a risk committee, or this responsibility can be assigned to the CISO)
First it is important to note that BIA is not required by ISO 27001 and this approach will only help to identify which processes are critical to the organization concerning availability, and for information security you also have to consider the loss of confidentiality and integrity.
Answer:
Your statement is not exactly correct; a company does not need to be certified to ISO 9001:2015 before becoming certified to AS9100 Rev D, you can just be certified to AS9100 Rev D without going through the first step.
The AS9100 Rev D standard actually includes all of the ISO 9001:2015 requirements, plus additional aerospace specific requirements. So, by being compliant to AS9100 Rev D you are also entirely certified to ISO 9001:2015. In fact, some certification bodies include both standards on the certificate so as to make it clear that the requirements of both are satisfied. This being said, you do not need to have certification audits for both ISO 9001 and AS9100, the one certification audit is sufficient, and by being compliant to AS9100 you are also compliant to ISO 9001; separate certificates and audits are not required.
For a better understanding of everything included in AS9100 Re v D, see the whitepaper: Clause-by-clause explanation of AS9100 Rev D, https://info.advisera.com/9100academy/free-download/clause-by-clause-explanation-of-as9100-rev-d