Define-XML and ryze
ryze supports Define-XML 2.1 and previous versions of Define-XML and you can import and export Define-XML in different versions. Since the formatting can change between versions, there are some properties to consider when working with Define.
External Standards
See External Standards
Origins
Origins in the ryze UI are designed to support the latest version of Define-XML. Since there are differences with the formatting of Define-XML 2.0 and 2.1
For example, when editing an Origin in ryze; if you select Type: Collected and Source: Investigator, then the exported Define 2.0 Origin is displayed as “CRF”.
Importing and Exporting Define 2.0
When adding an Origin to an Asset, (such as a Variable or Value), you should follow CDISC guidance for the expected Type and Source, see the CDISC Define-XML standard.
The following tables show how ryze handles Origin definitions on import and export:
Import
Origin properties are displayed differently in the ryze user interface. The following table shows how these properties are displayed after importing to ryze:

Export
The following table shows how ryze properties are converted to Define 2.0 on export:

!=Vendor: If source is not equal to “Vendor"
"Derived" Origins
Define-XML 2.1 guidance means that when you set an Origin as “Derived” you must also create or associate a Method asset.

Class and Subclass
You can add a subclass to a Class property, Subclasses allow you to provide a more descriptive classification of the datasets. Subclasses are free text fields and you can add more than one Subclass.
Has no data
The “Has no data'' property can be set on assets, such as Variables, where no data is present.
When “Has no data” is checked, a warning is displayed that the user should have a Comment on the corresponding asset to explain why. Once you create or associate a comment, the warning is removed.