---
title: Compliance
slug: ryze/compliance
description: Ensure compliance for Standards/Studies, Asset Groups, and Assets with this document. Learn how compliance is determined and understand the different statuses of Compliant, Deviation, or Non-Standard for each Asset.
createdAt: 2023-08-31T12:09:16.406Z
---

## Overview

The compliance status is displayed for Standards/Studies, Asset Groups, and Assets. 

:::hint{type="info"}
To have a compliance status indicator, the Standard/Study/Asset Group/Asset must contain at least one Asset that derives from a Standard.&#x20;
:::

Compliance is a measure of the adherence to the rules defined in the source or Derived-from Standard.

![](https://api.archbee.com/api/optimize/aRGXD44FysHcCUICvfsxc/CRkRyFpTJ_AsxdTr6P33i_compliance.png)

Ryze also displays the compliance status for each asset. If an asset is shown as non-compliant, you can click the icon to view the non-compliant asset.

The compliance status of an asset displays only rules on the asset itself. The compliance of status of child assets does not affect parent assets. For example, a Terminology that is non-compliant does not make a Question that uses it non-compliant.

The compliance status for an Asset can be Compliant, Deviation, or Non-Standard.

- **Compliant&#x20;**- Compliant assets display the green tick icon. These assets conform to the rules set in the parent or derived-from standard.
- **Deviation&#x20;**- Deviating assets display a red cross icon. These assets do not conform to the rules set in the parent or derived-from standard.
- **Non-Standard** - These are assets that are not derived from a Standard, for example, assets that are created manually by the user.

## Deviating Assets

The following is an example of how to handle deviating assets in your standards.

If you select **Show Deviating** next to a list of assets, a list of deviating assets is displayed.

These are typically datasets with variables where the SDTM-IG indicates that a terminology is required but is sponsor-defined. You need to create and associate a terminology to that variable. For example, in AE, AECAT, and AESCAT variables require terminologies (denoted by \* in the Implementation Guide).

![](https://api.archbee.com/api/optimize/aRGXD44FysHcCUICvfsxc/xgK2j2jkqzEbdx69v0Eo2_image.png)

In this example, updating these assets to include Terminologies will make them compliant.















