Because Derived Lists are created from Master Lists, information can be “passed down” from a master list to a derived list. Another way to say this is that the derived list can “inherit” information from the Master list. This inheritance concept allows information to be shared from the master with the derived. It also ensures that as information is updated on the dervied, that this information can roll back up to the master list.
When a Derived List is created, most Participant Properties retain the value and the scale from the Master List. Not only is the value and scale “passed down” to the Derived List, but if the value of these properties is changed on the Derived list, the new value will roll up to the master list, and will then roll back out to any other lists that derive from the master.
All Custom Participant Properties are inherited in this manner.
Most of the Standard Participant Properties are inherited in this manner aside from the exceptions listed below:
- The following properties do not inherit their value from the Master List:
- The following property does not by default inherit the values from the Master List, but the User can edit the Derived List indicating the Sites and Site Groups that will be inherited and show in this Property List:
DATSTAT_SITE – Unless Set Site from Master List, is checked when creating a Derived Participant List
- The following property defaults to the value on the Master list, but if it is changed on the Derived list, the value from the derived list does not roll up to the master list:
DATSTAT_ALTPID (but it does default to the MASTER list’s value if none is specified)
- The following properties default to the value on the Master list, and cannot be changed on the Derived list:
- The following properties are unique to the Derived List – they do not exist on a Master List as they only exist when associated with a specific study: