# Certified Entity and Certification Data Fields

{% content-ref url="certification-fields-glossary/version-1" %}
[version-1](https://support.iafcertsearch.org/certification-bodies/field-name-glossary/certification-fields-glossary/version-1)
{% endcontent-ref %}

{% content-ref url="certification-fields-glossary/version-1.1" %}
[version-1.1](https://support.iafcertsearch.org/certification-bodies/field-name-glossary/certification-fields-glossary/version-1.1)
{% endcontent-ref %}

{% content-ref url="certification-fields-glossary/version-2.0" %}
[version-2.0](https://support.iafcertsearch.org/certification-bodies/field-name-glossary/certification-fields-glossary/version-2.0)
{% endcontent-ref %}

{% content-ref url="certification-fields-glossary/version-2.1" %}
[version-2.1](https://support.iafcertsearch.org/certification-bodies/field-name-glossary/certification-fields-glossary/version-2.1)
{% endcontent-ref %}

Additional glossary:

### **IAF MD 28 Requirement**

This means that the data field is mandatory and must be provided by the Certification Bodies following the requirements of [IAF MD 28](https://iaf.nu/iaf_system/uploads/documents/IAF_MD_28_Issue1_26102023.pdf).

### **Has System Validation**

This means the system requires specific validation for the field to ensure the data can be properly processed.

### **Conditions**

System conditions refer to the specific requirements or criteria that must be met for a system to function correctly. These conditions can be the following:

1. **Input validation** – Verifying that data adheres to predefined standards.
2. **Operational limits** – Defined thresholds for system performance and load.
3. **Error handling** – Mechanisms to manage system failures and incorrect inputs.
4. **Security protocols** – Measures to safeguard data and system integrity.
5. **Integration dependencies** – Reliance on external systems or services for full functionality.

These conditions maintain system efficiency, accuracy, and security.