Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
According to the ISO 13485:2016, requirement 8.2.4 Internal audit states that the organization must conduct internal audits at planned intervals. The purpose of an internal audit is to determine whether your quality management system conforms to both all documented arrangments, requirements of the ISO 13485:2016, and all other applicable regulatory requirements. So, yes, you need to perform another internal audit to assess the compliance with MDR.
For more information on how the internal audit should be performed, please see following articles:
You can even see which documents our ISO 13485:2016 Internal audit documentation toolkit have:
When one speaks about non-conformities one can be speaking about audit non-conformities or product/service non-conformities.
Let us consider the product/service non-conformity situation.
When a non-conformity is determined the first priority is to prevent the unintended delivery or use. ISO 9001:2015 provides several alternatives to treat the non-conforming product/service:
After correction quality should be controlled again.
Record non-conformities occurrence and reasons. Record what was done and the authority that made the decision about what to do.
The following material will provide you information about nonconformities:
If your organization concluded that cleaning and hygiene is relevant for ensuring product or service quality the most relevant clause for that matter is 7.1.4 - Environment for the operation of processes.
You can find more information below:
Smaller organizations (up to 50 employees) usually implement the standard in up to 8 months. When using our Documentation Toolkit, normally: companies of up to 10 employees - usually implement the standard in up to 3 months and companies of up to 50 employees - usually implement the standard in up to 6 months.
You can find detailed information about how to plan and implement a quality management system in the following links:
If the products designed by Site "C" are not produced on Site "A" or Site "B"; Products of Site "C" are not included in the IATF scope of Site "A" or Site "B".
Since site "C" designs for another manufacturer (for other legal entities), "Site C" becomes a remote location within the scope of the other manufacturer.
For more information please see the following article
ISO 27001 and ISO 9001 share many requirements and these documents can be used after slightly adjustments:
These articles will provide you a further explanation about ISO 9001 and ISO 27001:
This material can also help you:
I'm assuming that by IRM you mean Integrated Risk Management.
Considering that, as a baseline for you to start I suggest the following material:
These materials will also help you regarding ISO 27001:
ISO 9001:2015 recommends the risk-based thinking applied to three situations:
In this free webinar on demand - The Process Approach - What it is, why it is important, and how to do it - https://advisera.com/9001academy/webinar/iso-9001-process-approach-free-webinar-on-demand/ I show how to relate processes and risks.
In this free webinar on demand - ISO 9001:2015 clause 4 - Context of the organization, interested parties, and scope - https://advisera.com/9001academy/webinar/iso-90012015-clause-4-context-of-the-organization-interested-parties-and-scope-free-webinar-on-demand/ I show how to relate context and risks.
The following material will provide you more information about risks and opportunities:
The ISO 45001:2018 standard does not define how you must create your documentation, or how it must look. In terms of procedures you can use whatever format works best for your organization, including flow charts, text documents, or even diagrammatic instructions if that is what works for your employees. As for records, again whatever format make sense to you for a particular record then that is what you can use. This is of course limited by any legal requirements that may exist for records and reports, such as a government form that needs to be submitted.
The general flow for creating documentation should go like this: What information do we need to document? Is there a required format to use (such as legal or other requirement)? If not, what is the best, and simplest, way we can record this information so that it is usable for us?
You can learn more about the new documentation requirements in the article: New approach to ISO 145001 documentation, https://advisera.com/45001academy/blog/2018/03/13/new-approach-to-iso-45001-documentation/