The Vault QMS Recurrence Check feature is an intelligent and streamlined interface for users to determine whether an event, such as a Quality Event or Complaint is a recurrence of another event. With this feature configured, Vault can simplify a complex manual process with a simple user action where text search terms are automatically suggested by Vault. After performing the user action, the user is shown a set of potential records along with their similarity score in a side-by-side comparison user interface. When the analysis is complete, Vault stores the results and automatically links recurrent Quality Events by creating Related Quality Events or Related Event records, depending on your configuration.

The Recurrence Check feature supports records of the Complaint object as well as the following object types for the Quality Event object:

  • Deviation
  • Complaint
  • MedTech Complaint
  • Change Control
  • Proactive Initiative
  • External Finding
  • Internal Finding
  • Lab Investigation
  • Nonconformance

The configuration steps for those objects and object types is described below, and the Quality Event and Complaint objects are collectively referred to as the “supported object” in this article.

Configuration Overview

Complete the following steps to enable the Recurrence Check feature:

Configuring the Run Quality Record Check Action for Recurrence

In order for users to have access to recurrence check functionality at the appropriate stage in the supported object’s lifecycle, you must make the Run Quality Record Check action available to users in that lifecycle state:

  1. Navigate to Admin > Configuration > Object Lifecycles and click into the supported object lifecycle.
  2. In the States section, click into the lifecycle state in which you want users to run their recurrence check. For example, select the Closed state to allow users to check for recurrence after the Quality Event has been finalized.
  3. In the User Actions section, click Edit.
  4. Click Create Rule.
  5. If configuring the action for a Quality Event object type, select Perform with Conditions, and select Quality Event Type > equals > [object type].
  6. Select Run Quality Record Check from the Allow the following actions drop-down.
  7. Select an appropriate Quality Record Check from the Available Quality Record Checks drop-down. See below for Quality Record Check configuration instructions.
  8. Select the Allow user to override discovered match terms checkbox to allow modification of search terms in a pop-up dialog after the user performs the action.
  9. Add an Action Label for the action.
  10. Click Save.

Creating Quality Record Checks for Recurrence

You can create Quality Record Check configurations for each scenario in which users will need to check for recurrences. For example, if your quality system requires that a newly completed Deviation be checked against older Deviations for recurrence for either six months or one year, depending on the affected process, you can create two Quality Record Check configurations appropriately, both available to users as a separate user action.

To create Quality Record Check configurations for recurrence:

  1. Navigate to Admin > Configuration > Quality Record Checks.
  2. Click Create.
  3. Enter a Label.
  4. In the Date comparison field drop-down, select a date field from the supported object from which to base your timeframe.
  5. In the Date comparison timeframe drop-downs, select a number and time period unit. For example, to include records up to one year previous to the value in the date field selected above, select 1 and Years.
  6. In the Fields on object that must match field, select one or more fields on the object that must match exactly between the records to be included in the recurrence check. For example, if your processes require you to check for recurrences only affecting the same facility, select the Owning Facility field to exclude records for other facilities.
  7. Optional: If you want to limit the check to evaluate object records with a certain lifecycle state, select those states in the Lifecycle states to include drop-down.
  8. In the Fields on object to compare in text search field, select text fields on which to run the recurrence check. When a user performs the action on a record, these are the fields for which Vault provides a percentage match score. If you are configuring a Complaint or MedTech Complaint recurrence check, this field is optional.
  9. Optional: In the Related Object Match Criteria section, select fields on objects referenced by supported object records with which to further limit the records included in the check. For example, if your originating Deviation has Root Cause Category values of Materials, Labelling, and Tooling, you can define match criteria to only include Deviation records where the Root Cause Category on related Root Cause records includes at least one of those categories. Vault displays these criteria to the user when they perform the recurrence check action.
  10. Fill in the Comparison Settings section. If you are creating a Quality Record Check for a Complaint or MedTech Complaint, this step is not necessary.
  11. Click Save.

Comparison Settings

If you are configuring a Quality Record Check for any Quality Event object type except Complaint or MedTech Complaint, perform these additional steps:

  1. In the Comparison Settings section, define three tiers of match similarity to assist users in analyzing potential recurrences. If you select the Display checkbox, when a user performs the recurrence check user action, Vault displays the tier as a category at the top of the page.
  2. Select a % minimum similarity score from the drop-down for each tier.
  3. Optional: For each tier, selecting the Relationship type required checkbox requires users to provide a relationship type when analyzing each record of that tier. For example, you might require that users select a relationship only for the most likely matches. If you select this option, you can further require users to provide a justification by selecting the Justification required checkbox.
  4. In the Quality Relationship Automation drop-down, select the relationship configuration applicable to your recurrence check, then select the Relationship types applicable to the Deviation being checked.
  5. Optional: In the Fields to Display section, you can choose fields from the Deviation record to display in the recurrence check interface to assist the user in their analysis. These fields are not included in the match calculation.

Configuring the Generate Document From Report Action for Recurrence

The Generate Document From Report action allows a user to create a document containing recurrence check information directly from a Record Check Result record. The newly generated document is linked from a document reference field on the originating Record Check Result record. In order for users to have access to this function, you must create an appropriate report and make the Generate Document From Report action available to users in the Record Check Result object lifecycle.

Creating a Report for Recurrence Checks

When configuring the Generate Document From Report action, you must select a report type and report view. While you can select any report in your Vault, it is most useful to select a report type which matches Record Check Result details to supported object details for records that have been identified as duplicates in the recurrence check. The report view can further filter the resulting report to records of the appropriate object type.

Recurrence Check Limitations

By default, there is a maximum number of records which Vault can include in a recurrence check, which differs by object type:

  • Quality Event object types: Deviations, Change Controls, Proactive Initiatives, External Findings, Internal Findings, Lab Investigations, and Nonconformances: 100
  • Quality Event object types: Complaints and MedTech Complaints: 200
  • Complaint object: 200

If you wish to modify these limits, contact Vault Product Support.

You must have the following permissions to configure or use Quality Record Checks:

Type Permission Controls
Security Profile Admin: Quality Record Check: Read, Create, Edit, Delete Ability to see, create, and manage Quality Record Check configurations
Security Profile Admin: Quality Relationship Automation: Read Ability to select Quality Relationship Automation values within Quality Record Check configurations
Security Profile Object: Quality Event: [object type]: Read Ability to view records of this object type in the recurrence check interface
Security Profile Object: Complaint: Read Ability to view records of this object in the recurrence check interface
Security Profile Object: Record Check Result: [object type]: Read, Edit Ability to view and edit Record Check Results and records of this object type
Security Profile Object: Record Check Match Record: [object type]: Read, Edit Ability to view and edit Record Check Match records of this object type