About Vault EDC Objects
Vault “objects” are part of the application data model. The application data model is a critical part of what makes each Vault application unique. It provides contextual information that drives the business processes in each Vault application.
Vault EDC has its own unique data model, like each other Vault application. For example, the structure of Study, Site, Subject, Casebook, Event, Form, and Item in EDC is part of the data model. Each of these is an object.
Each time you create a new casebook in EDC, you create a Casebook object record, as well as several objects related to that Casebook object record. Each form that you fill represents a Form record, and each field on that form represents an Item object record.
The EDC Objects data model includes:
- Objects: Top level in the data model, for example, Study, Casebook, and Organization.
- Object Definitions: These are the objects that Vault EDC copies during casebook creation. You create object definition records in EDC Studio. When you create a casebook from object definitions, the data collection object records in the casebook are based on these definitions.
- Object Records: Items within an object, for example, United States and Canada are each object records within the Country object. When you design a Study in EDC Studio, each item definition that you create is a record within the Item Definition object.
- Object Relationships: Hierarchical (parent-child) or non-hierarchical (reference) relationships between objects and object records; for example, a parent-child relationship exists between Event (parent) and Form (child), while a reference relationship exists between Site and Location.