Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Element NameAuditRecord
Parent ElementsReferenceData, ClinicalData, SubjectData, StudyEventData, ItemGroupData, ItemDataQuery
Element XPath(s)
  • /ODM/AdminData/Location/Query/AuditRecord
  • /ODM/ReferenceData/AuditRecord
  • /ODM/ClinicalData/AuditRecord
  • /ODM/ClinicalData/Query/AuditRecord
  • /ODM/ClinicalData/SubjectData/AuditRecord
  • /ODM/ClinicalData/SubjectData/Query/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/Query/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/ItemGroupData/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/ItemGroupData/Query/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/ItemGroupData/ItemData/AuditRecord
  • /ODM/ClinicalData/SubjectData/StudyEventData/ItemGroupData/ItemData/Query/AuditRecord
Element Textual ValueNone
Usage/Business Rules

An AuditRecord applies to  any descendent data element that allows a TransactionType and does not have an AuditRecord.  Query elements must have their own AuditRecord(s).

AuditRecord information describes a change to clinical data, but is not itself clinical data. The value of some clinical data can always be changed by a subsequent transaction, but history cannot be changed -- only added to.

For the Archive use case, all AuditRecord information in the data collection system must be provided within the ODM ClinicalData.

When the ODM FileType attribute is set to Transactional, every ClinicalData that has a TransactionType must also have an AuditRecord.

AttributesEditPoint, UsedMethod.
Child Elements(UserRefLocationRefDateTimeStampReasonForChange?, SourceID?, StateTransition?)