Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
Indeed, Excel can be used as the primary program /tool in a Laboratory Information Management System, if it will achieve the purpose for your laboratory. In fact, the Advisera ISO 17025 toolkit provides templates as either Microsoft Word or Excel. The toolkit can serve as the core documentation for your LIMS system.
A LIMS is typically made up of a combination of noncomputerized (hardcopy records) and computerised systems. The computerised system can range from a simple system of stored scanned Pdf format records and Microsoft Word and Excel documents, forms and records; to more complex direct data transfer, processing and storage between instruments and database programmes. As long as the requirements for the LIMS are identified, scope defined (what it does) and it is tested and validated for functionality - then that is an acceptable framework. Functional validation involves test cases to provide evidence that the system does what it is meant to do. All the requirements for data and information control must be met. That includes protection, access and change control, integrity and recording system failures. Furthermore, all calculations and data transfers must be checked and safeguarded.
For more detail on what is required for ISO 17025, read the whitepaper Clause-by-clause explanation of ISO 17025:2017 available for download from https://advisera.com/17025academy/free-downloads/ and preview the toolkit at https://advisera.com/17025academy/iso-17025-documentation-toolkit/
Risks can be about:
Risks about products, services and processes can be monitored, evaluated and reported based on process performance indicators, and other indicators like customer complaints, customer satisfaction and returns. These indicators illustrate how well risks were determined, and effective actions were taken.
Risks about context and interested parties are more about trends in the external environment that can help or hinder performance. For example, in this picture from our webinar about Clause 4:
You can see how internal and external context collide with an interested party expectation to raise a risk. Management review can be used to evaluate these kinds of risks and determine actions. The effectiveness of those actions will be evaluated in the next management review meeting.
Consider also the following information:
Please note that the toolkit was developed in a way that the easiest way for implementation is to approve the documents as soon as you finish developing them (you should follow the sequence of documents as they are presented in the folders in the toolkit). The references are included in a way that when you approve them in the suggested sequence, the referred documents are already approved, or have minimal impact on the document (i.e., they provide complimentary guidance).
We do not recommend you approve all of them at the same time, to not overload responsible for approvals and users with too much information (documents should be implemented with a short interval between them so people get used to information security in a controlled manner).
In fact, changes in the ISMS scope are quite a common business and your organization can perform changes in the ISMS scope at any moment during the certification period. The scope can be expanded or reduced according to the organization's needs.
A change in the ISMS scope is something expected during a certification life cycle and this situation does not make it invalid, provided that the new scope still fulfills all requirements of the standard. Considering that, after defining the new scope, you need to evaluate the impacts of the change and make proper adjustments in the ISMS (e.g., risk assessment, risk treatment, SoA, etc.).
Regarding the certification body, you need to communicate it about the change in the scope, so it can verify if any adjustment in the planned surveillance audits is necessary (e.g., if only minor adjustments in the current schedule are enough, or if additional days are required).
These articles will provide you a further explanation about the scope definition:
- How to define the ISMS scope https://advisera.com/27001academy/knowledgebase/how-to-define-the-isms-scope/
- Problems with defining the scope in ISO 27001 https://advisera.com/27001academy/blog/2010/06/29/problems-with-defining-the-scope-in-iso-27001/
This material will provide you a further explanation about the scope definition:
- How to set the ISMS scope according to ISO 27001 [free webinar on demand] https://advisera.com/27001academy/webinar/how-to-set-the-isms-scope-according-to-iso-27001-free-webinar-on-demand/
It is difficult to answer this question because mostly it depends on your domestic tax law. From a GDPR point of view I can say that along with consent and Court order there is also internal law and regulation. Therefore, you should verify with a lawyer of your country the legitimacy of the tax department's behavior.
Here you can find more information on the legal basis to process personal data according to the GDPR:
If you want to learn how personal data are processed under the EU GDPR you may consider enrolling in our free training EU GDPR Foundations course: https://advisera.com/training/eu-gdpr-foundations-course//
You need to determine the environmental aspects and impacts, you need to determine and evaluate the compliance obligations, you need to determine priorities to improve your organization’s interactions with the environment, and develop action plans.
You need to determine an environmental monitoring plan. And, of course, you have to update the scope and the context analysis, the interested parties, the policy, the objectives.
Those first two topics: environmental aspects and impacts, and compliance obligations determine the amount of work to be done on the shop floor.
For more information, see:
ISO 27001 is designed to be implemented in organizations of any size and industry, so its implementation in a scenario where the organization has only one person is perfectly feasible.
Regarding the duration of implementation, for very small business (up to 5 employees) generally is possible to implement ISO 27001 within 3 months.
For more information about the time needed for the implementation, I suggest you see this article:
These materials can provide you more information:
First is important to know which objectives you want to achieve (i.e., to which purpose you want to use ISO 27001 as a guideline).
For example, if your organization wants to be fully compliant with ISO 27001, even if you are not intending certification, then the Statement of Applicability is mandatory.
In case your intent does not involve being fully compliant with ISO 27001 (e.g., you only want to adopt some controls of the standard), then the Statement of Applicability is not mandatory, but we strongly recommend that you use it as a good practice, because the SoA can be used as the main guide to understand and provide an overview on how information security is implemented in your organization.
This article will provide you a further explanation about the Statement of Applicability:
These materials will also help you regarding ISO 27001 implementation:
If a customer-specific requirement is not defined by your customer; the training you received is enough for you to do second-party audits.
Note: Generally German customers (Daimler, Volkswagen,..) require the VDA 6.3 process audit approach to supplier audits, therefore customer-specific requirements should be taken into account.
The software company acts as a processor while the caregiver is the data controller. In that case, your privacy notice will state that the controller is the caregiver since it is the person that has control over data processing. You will also need a data protection agreement with caregivers annexed to your commercial licensing/software agreement.