Enforcement
This model was last updated on 23/09/2020, this is version 1.0
Stable
Model created
10/02/2020
Description
Enforcement is the term for the available actions to a Competent Authority to make establishments obey food or feed law, regulations, or policy which falls within a scheme.
Some examples include making the establishment change the way they operate in order to comply or removing the ability for the establishment to carry out activities until the changes are made. This can also take the form of litigation, removal of services, suspension of licensing, and fines.
Related entities
Enforcement is part of a scheme. It represents the actions available to the Competent Authorities who own or run the scheme. Often, the available enforcement actions under the scope of a scheme will be laid out in the legislation or policy documentation.
Enforcement can happen to an establishment, premises, operator or an person depending on the specific enforcement action.
Enforcement action is often the result of unsuccessful interventions, but not always.
Entity diagram
Synonyms
- litigation
- prosecution
- enforcement actions
What it is not
An enforcement is not an intervention although like an intervention it forms part of the regulation of a scheme. Neither is it an activity, but all are associated with a scheme.
Properties, identifiers and reference data
Key properties
The URI of the registry entry for the enforcement action, the name (label), and notation for each item represents the minimum properties.
Contextual properties
When creating records of enforcement actions the following properties will all have uses.
It is important that the start-date and end date of the enforcement is recorded. It is worth noting that sometimes the end date can be blank, determined or a fixed point in time from the start date depending on the rules around the enforcement action. It can also help identify cases of production during a period of time when the business shouldn’t have been operating, and by having start and end dates of enforcement actions makes the task of identifying this easier.
As far as data is concerned, when recording the reason for enforcement, we prefer to use a controlled vocabulary of reasons to make analysis easier.
The identifier of the Competent Authority that undertook the enforcement, because the establishment may have enforcement action taken by multiple authorities.
Unique identifiers
Where possible, lists of enforcements should be modelled as registers within the scope of a scheme and a code list created. The unique identifier should be the URI of the registry entry.