Advantages: One configuration point
Clinical trial designs often change. In legacy EDC/EDM architectures, this can requires trial teams to perform and reconcile a number of changes. Timaeus makes incorporating changes simple by organising them from one configuration point.
Designing and modifying trials without structural database changes
Timaeus overlays its flexbile data architecture with an Abstract Data Model that makes configuration even more flexible. Trials teams configure using content, not structural database changes. As a result, they can create and modify complex trial designs without worrying about “breaking” the underlying data model. It also lets them publish trial changes without downtime.
Driving all configuration from one point
Using the Abstract Data Model, Timaeus infers the entire Trial Database structure from the eCRF page definitions. One definition controls the page views and validation checks for:
- Data Capture
- Monitoring
- Data Management
- Medical Coding
- Reporting
Trial teams can do this using native XML, Timaeus Trial Builder or third-party CDISC applications—whichever is easier.
Eliminating work, re-work and reconciliation
Configuration of the trial database from one point saves much work. At the start of a trial, teams only need to configure databases from one place. Later, when designs change, they only need to update one place—eliminating the need to reconcile design changes across multiple places.
