IN THIS ARTICLE |
1. eQMS flexibility 2. Quality driven dashboards 3. Task automation and follow-through 4. Security and traceability 5. Out of the box processes with the eQMS |
Most systems provide a task notification mechanism, which is typically an internal task via the system and email notice. When you need to perform a task, the task notifies you.
Deadlines and reminders are also a very crucial part of making sure the ISO quality management system is run efficiently as possible. A Quality Manager shouldn’t need to chase actions or CAPA’s but often many hours are spent doing so. The system should give a time frame to complete the task, remind the user before the deadline just in case they missed it, remind them on the deadline, remind them after the deadline and then escalate to a manager or their manager that a task has not been completed. How aggressive these deadlines are, how many reminders should be in place before escalation should be the choice of the quality manager or management. Without the tasks been completed to fully undermines the whole purpose of an ISO quality management system.
More advanced notification functionality should be available that allows notifications to go to users based on logic. So if an issue is related to quality it will go to the quality manager if it related to a product then it will go the product manager of that product.
Other examples might include:
- Top 5 customer complaint generates a cc notification to management.
- Rejected change request notifies the initiator of the change
- Health and Safety issues are sent to the Health and Safety Manager
Depending on the standards you the following whether it is ISO, FDA, GMP will determine the amount of traceability and security that is required.
I won’t talk about logins as this is pretty basic and obvious but there should be 2 types of authentication. Such as username & passwords (This is one type), mobile authentication, email authentication, biometrics. If you in the pharmaceutical industry or medical devices industry it’s worth checking to see if the software complies with 21 CFR Part 11A.
This ensures that the system has the capability of digital signatures to the required standard.
The software should be able to track who has completed an action, the time of action and a description of the action. These logs should be accessible by an administrator or a process owner.
When you have important tasks like final sign-off or implementation go request on a change process than a digital signature using one of the above methods should take place.
This combined with flexibility mentioned earlier is a real game-changer, businesses do not want to spend weeks mapping out their processes into a new software they may have spent this kind of work when they did their ERP system.
They can take a solution that is out of the box and has most of the processes they need, they then tweak them for their individual needs they can do this themselves or with the software vendor.
It’s worth noting in advance what processes are important to you is it:
- Document Control
- Audits
- Change Control
- Calibration
- CAPA
- Non Conformance
and many more
These processes should be easily changeable to the company requirements.