How can we ensure that the applications using CDEs that are versioned don end up with clinical data that is impossible to aggregate?
There are business processes and practices in place for the proposal, review, and acceptance of new CDE versions to minimize unnecessary changes. However, there will be situations where a version change is required for a CDE. The release of a new version of a CDE does not mean that an application or project must immediately update to using the new version. For example, if a project is using version 1.0 of a CDE on a form, and that version will meet their needs for the duration of the trial, there is not necessarily a need for them to modify the form to use the new version – they can continue using version 1.0 for the duration. However, users should be aware of the new version, and make use of it as new projects are started and implemented. There might also be times when the new version of the CDE will have information that a user wants to make immediately accessible (i.e. a new value domain name with an additional set of values). In this case, the user would consider implementing the n
Related Questions
- One of my applications requires an old version of the operating system. How can I ensure I have the rights to run the version current at the time of license purchase and all prior versions?
- I have two .NET applications on the same machine running two different versions of ODP.NET. How do I ensure both these applications use the correct ODP.NET version?
- How can we ensure that the applications using CDEs that are versioned don end up with clinical data that is impossible to aggregate?
