...
Info | ||
---|---|---|
| ||
Other File AttributesAs implied above, most ODM documents will contain only part of the total information (current and historical) held in the source database. The information that is sent in a given document can vary along several dimensions. Some examples of the contents of a document are:
Because of this variability, it is also important that each document describe itself, so that the consumer of the document knows what to expect of it. To address these needs, the ODM element has several attributes for describing the current document. The CreationDateTime attribute tells when the ODM document was created. In contrast, the AsOfDateTime attribute tells when the document content was accurate by specifying the date/time at which the source database was queried to create the ODM document. This is of particular importance when a series of files is used to give an evolving view of a changing database. The FileType and Granularity attributes allow the document sender to define the scope, across time and data, that a particular document spans. The Archive attribute allows the sender to assert that the contents of the document meet a specific set of criteria that qualifies it as an electronic record defined in the FDA 21 CFR 11 regulation. Finally, the Description attribute provides the sender a text string in which to give details, as elaborately as necessary, to supplement the other attributes in describing the document. This section details the values these attributes can take, and discusses the use of the values in a single document and in a series of documents. |
...
An ODM document's Granularity is intended to give the sender a shorthand way to describe the breadth of the information in the document, for certain common types of documents.
Here are the intended meanings of these categories:
Category | Document contains |
All | Any and all types of data and metadata |
Metadata | Metadata only |
AdminData | Admin data only |
ReferenceData | Reference data only |
AllClinicalData | Clinical data only |
SingleSite | Clinical data for a single site only |
SingleSubject | Clinical data for a single subject only |
If these shorthand categories are not sufficient, use the document's Description attribute to give details.
...
- The current file must be Transactional.
- If the current file is one of a collection, all other files in the collection must be both Archival and Transactional.
- The set of transactions must be both complete and non-redundant within the file or collection of files. In particular each file must contain:
- no transactions that have an audit date of prior to the AsOfDateTime of its PriorFile (if any),
- all transactions up to its AsOfDateTime. (For Granularity=All, this means all transactions in the study. See Granularity for the meaning of "all" for other Granularity settings),
- all AuditRecord and Signature information available in the source database, and
- no Upsert transactions.
...