Corrective and Preventive Actions (CAPAs) are an integral process of any good Quality Management System (QMS). They are used to identify actions that may either correct an identified root cause or prevent that cause from happening. The objectives of tracking CAPAs are to provide a mechanism for minimizing risk of harm (fixing an existing root cause) or to drive continuous improvement, which is a cornerstone objective of QMSs as a whole.
This application provides a digital way to manage this process consistently so that you can spend your time focusing on improving your risk profile or QMS effectiveness as a whole. With all your data in digital format you can easily view historical and current records in order to evaluate and manage the effectiveness of your CAPA process and focus on continuous improvement.
***NOTE**** This application contains documentation to help you get up and running more quickly. Contact firstname.lastname@example.org for an Operational Flow Diagram, a Risk Assessment, and a Test Plan for a seamless GxP deployment.all your data in digital format you can easily view historical and current records in order to evaluate and manage the effectiveness of your CAPA process.
This applications works closely with the CAPAs table. Every time a new CAPA is submitted, it is entered into the table. The following metadata stored with each event at the conclusion of the entire workflow includes:
-Linked Quality Event
-Evidence of Completion (text)
-Evidence of Completion (photo)
-Root Cause Description
The application has a pre-defined workflow that guides an event through pre-configured screens in order to move the event through the following states:
At each state change there is also a new Assignee assigned to the ticket. In order to configure and make this application your own you must update the logic to have it route to the appropriate Owner for your organization. In the App Editor make the following updates:
Open the 'Investigation Report' step and click on 'Submit' button
Click the pencil icon next to the 'Update Event' trigger and edit the action that updates the Assignee field.
*Note*: Make sure users have set up their account or else they may not be an option on the list.
If the status' we provided don't work for your organization, you can easily change them by modifying the triggers at each state change. Use this chart to locate the different state changes:
Additional Info - Reject