Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
1. How to understand Context of the Organization
You can understand the context of the organization as any internal or external factor that can affect the ISMS. As examples of external factors (something that is outside the organization's control), we can mention new technologies, competitors, and laws. As examples of internal factors (something the organization can control or have influence over) are the organization's own resources and knowledge, its culture, and its employees' competencies. Understanding the context is essential to identify where the ISMS can be applied, its strengths and limitations.
This article will provide you a further explanation about the Context of organization for 27001:
These materials will also help you regarding the Context of organization for 27001:
2. and determine scope for Implementation of ISO 27001:2013
According to ISO 27001, an ISMS scope must be defined in terms of information, locations, or business units to be protected, considering the organization's objectives and context.
For small and mid-size organizations (up to 100 employees) often it is better to include all the organizations in the scope because the effort to keep only a part of the organization in the scope is not worthy. For bigger organizations defining a smaller scope may be better to reduce the costs and effort to what really matters for business objectives.
These articles will provide you a further explanation about defining scope:
I'm assuming that by "Vendor log" you mean the document or system you use to record and manage your vendors.
Considering that, to identify which vendors should be in your Vendor Log, and under periodic vendor review, you need to perform a risk assessment on your vendors, to identify if they can rise relevant risks that need treatment. Additionally, you need to evaluate the legal requirements you must comply with (e.g., laws, regulations and contracts), to identify if any of them has clauses defining specific vendors or conditions that will require vendors to be logged or reviewed periodically.
These articles can provide further information:
In your documented procedure Control of documents, you can state that your particular website is also documented information, but you just need to explain somewhere (maybe in the SOP Control of document or in separate SOP) how do you control the website, who is responsible for the changes on the website, how is the back up provided, how do you collect any information from the customers, how data that customers leave on your website is protected and so on.
For more information on documentation control, please see the following article:
You can see how our ISO 13485:2016 documentation toolkit looks like on the following link: https://advisera.com/13485academy/iso-13485-documentation-toolkit/
You can even download the free demo on the following link: https://advisera.com/13485academy/iso-13485-free-demo/
For more information on what is ISO 13485:2016 please see the following links:
If you will have any other questions regarding the ISO 13485, please do not hesitate to contact us.
Requirement 6.2 Human resources from ISO 13485:2016 states that the organization must document how to evaluate the effectiveness of the training. So there is what needs to be done, and not how to do it. It is totally up to you to define the method of training validation. Only keep in mind that you need to ensure the competencies for a particular job and the awareness in employees how they participate in the quality of both products and systems.
Your idea to create a different version of quizzes for a group of SOP sound great.
Here you can see how we in our ISO 13485:2016 documentation toolkit have prepared human resource procedure and record:
ISO 27001, ISO 20000, and ISO 9001 share some common requirements that can be fulfilled by the same documents with minor adjustments, like document control procedure, internal audit, and management review. For requirements specific to each standard you will need to develop specific documents.
There is no specific procedure for such integration, but broadly speaking you can follow the steps to implement ISO 27001 and use the following material to identify when common requirements can be integrated:
For further information, see:
Yes, you can do it with an organizational chart and updating the job descriptions. There is no requirement in the ISO 13485:2016 how you are supposed to do it. The requirement 5.5.1 Responsibility and authority stated that top management shall ensure that responsibilities and authorities are defined, documented, and communicated within the organization. It is totally up to you how you will do it.
For more information on defining roles and responsibilities within an ISO 13485-based QMS, please see the following article:
For more information fulfilling management responsibilities in ISO 13485:2016, please see the following article: