Description

A trial design domain that contains the planned order and number of visits in the study within each arm.


Specification

TIG v1.0 Metadata Check for SDTM Domain Specification Table Beta 3.2

Metadata check macro is applied and detected no issues. This notice is provided as a visual reminder. It will be removed during final publication. Release Notes

Variable NameVariable LabelTypeControlled Terms, Codelist, or FormatRoleCDISC NotesCore
STUDYIDStudy IdentifierChar
IdentifierUnique identifier for a study.Req
DOMAINDomain AbbreviationCharTVIdentifierTwo-character abbreviation for the domain.Req
VISITNUMVisit NumberNum
Topic
  1. An assigned numeric identifier that aligns to the chronological order of an encounter.
  2. Numeric version of VISIT, used for sorting.
Req
VISITVisit NameChar
Synonym Qualifier
  1. The label for a protocol-defined encounter.
  2. May be used in addition to VISITNUM and/or VISITDY.
Req
VISITDYPlanned Study Day of VisitNum
Timing

Planned study day of VISIT. Due to its sequential nature, used for sorting.

Perm
ARMCDPlanned Arm CodeChar
Record Qualifier
  1. ARMCD is limited to 20 characters and does not have special character restrictions. The maximum length of ARMCD is longer than for other "short" variables to accommodate the kind of values that are likely to be needed for crossover trials. For example, if ARMCD values for a 7-period crossover were constructed using 2-character abbreviations for each product and separating hyphens, the length of ARMCD values would be 20.
  2. If the timing of visits for a trial does not depend on which arm a subject is in, then ARMCD should be null.
Exp
ARMDescription of Planned ArmChar
Synonym Qualifier
  1. Name given to an arm or product exposure group.
  2. If the timing of visits for a trial does not depend on which arm a subject is in, then Arm should be left blank.
Perm
TVSTRLVisit Start RuleChar
RuleRule describing when the visit starts, in relation to the sequence of elements.Req
TVENRLVisit End RuleChar
RuleRule describing when the visit ends, in relation to the sequence of elements.Perm


Assumptions


  1. Although the general structure of the Trial Visits (TV) dataset is 1 record per planned visit per arm, for many clinical studies—particularly blinded clinical studies—the schedule of visits is the same for all arms, and the structure of the TV dataset will be 1 record per planned visit. If the schedule of visits is the same for all arms, ARMCD should be left blank for all records in the TV dataset. For studies with study visits that are different for different arms, ARMCD and ARM should be populated for all records. If some visits are the same for all arms, and some visits differ by arm, then ARMCD and ARM should be populated for all records, to ensure clarity, even though this will mean creating near-duplicate records for visits that are the same for all arms.

  2. A visit may start in one element and end in another. This means that a visit may start in one epoch and end in another. For example, if one of the activities planned for a visit is the administration of the first dose of study product, the visit might start in the screen epoch and end in a product exposure epoch.
  3. TVSTRL describes the scheduling of the visit and should reflect the wording in the protocol. In many studies, all visits are scheduled relative to the study's day 1 (RFSTDTC). In such studies, it is useful to include VISITDY, which is, in effect, a special case representation of TVSTRL.
  4. Note that there is a subtle difference between the following 2 examples. In the first case, if visit 3 were delayed for some reason, visit 4 would be unaffected. In the second case, a delay to visit 3 would result in visit 4 being delayed as well.
    1. Case 1: Visit 3 starts 2 weeks after RFSTDTC. Visit 4 starts 4 weeks after RFSTDTC.
    2. Case 2: Visit 3 starts 2 weeks after RFSTDTC. Visit 4 starts 2 weeks after visit 3.
  5. Many protocols do not give any information about visit ends because visits are assumed to end on the same day they start. In such a case, TVENRL may be left blank to indicate that the visit ends on the same day it starts. Care should be taken to assure that this is appropriate; common practice may be to record data collected over more than 1 day as occurring within a single visit. Screening visits may be particularly prone to collection of data over multiple days. The examples for this domain show how TVENRL could be populated.
  6. The values of VISITNUM in the TV dataset are the valid values of VISITNUM for planned visits. Any values of VISITNUM that appear in subject-level datasets that are not in the TV dataset are assumed to correspond to unplanned visits. There will be a one-to-one relationship between values of VISIT and VISITNUM in TV. If a subject-level dataset includes both VISITNUM and VISIT, then records that include values of VISITNUM that appear in the TV dataset should also include the corresponding values of VISIT from the TV dataset.


  • No labels