Configuring violations in nCORE is a multi-step process involving entries in three lookup lists: Violation Categories, Violation Types, and Violation Types to Categories. 

Violation Categories

Violation Categories are a way of grouping violations. These can then be assigned to a specific program area. Alternatively, the program area field can be left blank for violation categories which apply to multiple program areas.

Example: A violation category may simply be "Agriculture Program", assigned to a program area of "Agriculture". Alternatively, a violation category may be "Storage of Infectious Waste" and be only one of multiple categories assigned to the program area of "Infectious Waste". 

Violation Types

The Violation Type is the individual regulatory reference of the violations.

This lookup contains two columns: Violation Type and Regulation. The violation type is the description of the violation and the regulation is the regulatory reference or stipulation. 

Example: A violation type may read "Failure of a transporter to develop a written infectious waste management plan" and the associated regulation may be "R.61-105.N.6.".

Violation Types to Categories

The Violation Types to Categories lookup maps each Violation Type to a Violation Category. This is also where the nSPECT integration tag for the violation is established.

The columns of this lookup table consist of: Violation Category, Violation Type, nSpect Tag, and Status. The Violation Category is a value which directly correspond to a value in the Violation Categories lookup. The Violation Type is a value which directly correspond to a value in the Violation Types lookup. The nSpect Tag is a new value created in the lookup screen. The value in this column is the tag configured in nSpect inspection forms to enable auto-creation of a violation on import. This value is populated into the "Reference/Citation" field on individual questions of inspection forms.