Resolve issue with ordering of eligibility criteria

[ASL-rmarshall]

In release 3.2, the definitions for eligibility criteria were moved from StudyDesignPopulation and StudyCohort into an API-only collection under StudyVersion. The rationale for this move was so that each criterion can be defined once, with the single definition then available to be referenced from multiple study designs.

The problem is that the definition of each criterion current contains its ordering relative other criteria (using the previous and next attributes). However, it's quite possible that the same criterion might be referenced in multiple study designs, but that the ordering of criteria in each study design could be different.

Also:

• Is the ordering of criteria affected by their use in populations vs cohorts?
• Is the numbering of criteria dependent on where they're used (study designs, populations, cohorts)?

[BSnoeijerCD]

@ASL-rmarshall @dih-cdisc As a note: The phased multiple design study that I mapped had all the criteria in 1 longer list but referred per criterium to the different study parts/cohorts they were applicable to per criterium. So in that case it works well with the current set-up of the model.

We can look into more examples of such studies to be able to see whether it works in the current design or not.