# Using Quality Incidents

The _Quality Incident_ object and lifecycle allow your organization to triage an incident to determine if it is necessary to initiate a quality event. This avoids skewing quality event metrics, and unnecessarily complicating audits. Information from a quality incident can be automatically copied to a quality event, including attachments that represent pictures and video documenting the incident.

## Supported Objects

_Quality Incidents_ are currently supported for the following objects:

  * _Quality Event_
  * _Change Control_
  * _Complaint_
  * _Continuous Improvement_
  * _Deviation_
  * _Lab Investigation_
  * _MedTech CAPA_
  * _Nonconformance_

## Example: Quality Incident to Deviation

An employee at your organization, Peter Production, notices an issue with a piece of equipment while performing a routine maintenance procedure. Peter is unsure if the issue fits all the necessary criteria for a deviation. In this case, Peter could add a _Quality Incident_ record, including any supporting material such as photos of the equipment and a description of the possible issue.

Another employee, Quincy Quality, can then triage Peter's quality incident and determine whether it meets the requirements to become a true deviation or not. In the event that the incident is determined to be a true deviation, Quincy can change the state of the _Quality Incident_ record to, for example, _Requires Quality Event_, automatically creating a new related _Deviation_ record. When Vault creates the resulting _Deviation_ record, it copies attachments and other information from the originating _Quality Incident_ to the _Deviation_.

## Creating & Managing Quality Incidents

You can create and manage _Quality Incidents_ like other object records in Vault. Once evaluation and triage of a _Quality Incident_ is complete, the record is typically either closed or promoted to a state that automatically creates a related quality event, such as a _Deviation_ or _Nonconformance_, for further processing.

Depending on the configuration set up by your Vault Admin, the lifecycle of _Quality Incidents_ may automate quality event creation upon entering certain _Quality Incident Lifecycle_ states.

### Generating Quality Incident QR Codes

To create a QR code for use in _Quality Incident_ intake, perform the **Generate Quality Incident QR Code** user action on the _Quality Incident Configuration Data_ object record. You can use your browser’s print dialog to save or print the QR code. Click **Copy Link to URL** to copy the QR code’s URL to your clipboard. Users with the ability to generate this QR code in Vault can this URL to provide easy navigation to the same _Quality Incident_ creation page as the QR code.  For example, the URL can be made available to users in company portals.

### Creating a Quality Incident with a QR Code

If <a href="/en/gr/60704601/">configured by an Admin</a>, you can scan QR codes provided by your organization in your environment to expedite the creation of _Quality Incident_ records:

  1. Scan the QR code with a mobile device scanner, typically the device’s camera app.
  2. When you tap the resulting URL link, you may need to log in to Vault if the device has not already been logged in.
  3. On the intake form, some data may already be filled in for you. Enter the remaining data on the form.
  4. Add any attachments from your mobile device to the intake form.
  5. Tap **Submit**.

If another _Quality Incident_ is necessary, tap **Submit Another Incident**.

## Related Permissions

To create and manage _Quality Incidents_, users require _Read_, _Create_, and _Edit_ <a href="/en/gr/22824/#object-permissions">permissions</a> for the _Quality Incident_ object.

To generate QR codes, users require _Execute_ access to perform the _Generate Quality Incident QR Code_ user action on _Quality Incident Configuration Data_ records.