You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Description  TOBA-273 - Getting issue details... STATUS


A special-purpose domain that includes a set of essential standard variables that describe each subject in a nonclinical study.  A record will exist for each subject. TOBA-294 - Getting issue details... STATUS  

A special-purpose domain that includes a set of essential standard variables that describe each subject in a nonclinical study. One record will exist for each subject.


Specification

TIG v1.0 Metadata Check for SEND Domain Specification Table Beta 2.1

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 AbbreviationCharDMIdentifierTwo-character abbreviation for the domain.Req
USUBJIDUnique Subject IdentifierChar
IdentifierIdentifier used to uniquely identify a subject across all studies for all applications or submissions involving the product.Req
SUBJIDSubject Identifier for the StudyChar
TopicSubject (i.e., Animal) identifier used within the study.Req
RFSTDTCSubject Reference Start Date/TimeCharISO 8601 datetime or intervalRecord QualifierReference start date/time for the subject in ISO 8601 format. Usually equivalent to date/time when subject was first exposed to study product. Study day calculation (the --DY variable) in all domains will be based on this date. The collected date used to populate RFSTDTC must be defined in the data definition file.Req
RFENDTCSubject Reference End Date/TimeCharISO 8601 datetime or intervalRecord QualifierReference end date/time for the subject in ISO 8601 format. Usually equivalent to the date/time when the subject was determined to have left the study. The collected date used to populate RFSTDTC must be defined in the data definition file.Exp
RFXSTDTCDate/Time of First Study ExposureCharISO 8601 datetime or intervalRecord QualifierFirst date/time of exposure to any protocol-specified product exposure, equal to the earliest value of EXSTDTC. Note: Absolute first.Perm
RFXENDTCDate/Time of Last Study ExposureCharISO 8601 datetime or intervalRecord Qualifier

Last date/time of exposure to any protocol-specified product, equal to the latest value of EXENDTC (or the latest value of EXSTDTC if EXENDTC was not collected or is missing). Note: Absolute last.

Perm
SITEIDStudy Site IdentifierChar
Record QualifierUnique identifier for a study site within a submission. Use only if subjects are housed at different sites.Perm
BRTHDTCDate/Time of BirthCharISO 8601 datetime or intervalRecord QualifierDate/Time of birth of the subject, in ISO 8601 format.Perm
AGEAgeNum
Record QualifierMay be derived (RFSTDTC - BRTHDTC), but BRTHDTC may not be available in all cases. Age may also be collected.Perm
AGETXTAge RangeCharnumber-numberRecord QualifierUsed when the age is a range and the exact birthdate is not known. This variable is a character field for the purposes of defining age ranges, e.g., if the information available for the age of the subject is 6-8 and AGEU is WEEKS. Populate only when BRTHDTC or AGE is not specified. The format for AGETXT is "number-number" (e.g., 6-8).Perm
AGEUAge UnitChar(AGEU)Variable QualifierUnits associated with AGE and AGETXT.Exp
SEXSexChar(SEX)Record QualifierThe sex of the subject.Req
SPECIESSpeciesChar(SPECIES)Record QualifierIf this variable is excluded in the DM domain, the information must be present at a higher level (either Trial Sets or Trial Summary).Perm
STRAINStrain/SubstrainChar(STRAIN)Record QualifierUsed to identify the vendor-supplied strain, substrain, or breed designation for the test system under study. It may combine the background strain, substrain, and associated genetic modifications as supplied by the vendor (e.g., C57BL/6, A/J, B6.129-Pparg<tm2Rev>/J, FISCHER 344, SPRAGUE-DAWLEY IGS, WISTAR Kyoto, BEAGLE, CYNOMOLGUS, and CHIMPANZEE). The SEND Controlled Terminology codelist consists of commonly used wild type strains. It is extensible to accommodate strains not listed and genetically modified substrains. If this variable is excluded in the DM domain, the information must be present at a higher level (either Trial Sets or Trial Summary). Country of origin for non-human primates should not go into STRAIN. In general, details related to coat color (e.g., White and Red designations for New Zealand Rabbits) should not go into STRAIN.Perm
SBSTRAINStrain/Substrain DetailsChar
Record QualifierFree-text field that allows the to enter further details qualifiying the SPECIES and/or STRAIN, depending on the level to which these variables were defined. Examples include the description of a specific genetic alteration, country of origin for non-human primates, details related to coat color (e.g., White and Red designations for New Zealand Rabbits), and important animal husbandry information (e.g., SPF, BR, VAF).Perm
ARMCDPlanned Arm CodeChar
Record QualifierShort name for ARM (may be up to 20 characters) used for sorting and programming. Should be populated when Arms have been defined in the TA domain.Exp
ARMDescription of Planned ArmChar
Synonym QualifierDescriptive name given to a specific Trial Arm to which the subject was assigned.Perm
SETCDSet CodeChar
Record QualifierShort name of a specific Trial Set to which the subject was assigned, as defined by the applicant. Maximum of 8 characters. This represents the Trial Set for which parameters are being submitted.Req


Assumptions

  1. Subject identification: It is presumed that every subject (i.e., animal) in a study will have a subject identifier (SUBJID). In some cases, a subject may be included in more than 1 study within a submission, and, more commonly, subjects from different studies may have the same subject identifier. To identify a subject uniquely across a submission, a unique identifier (USUBJID) should be assigned and included in all subject-related datasets in the submission.
  2. Arm identification: When submitting study design information, the values of ARMCD and ARM should be identical to the values defined for that subject in the Subject Elements (SE) dataset. The assignment of values should be consistent, if possible, within a submission.
  3. When additional information is reported about the subjects, this information should be placed in the Subject Characteristics (SC) domain, adding the specific variable as a value in SCTEST. Study design information that does not vary on an individual subject level should be placed in the Trial Sets (TX) table.
  4. BRTHDTC, AGE, and AGETXT: These variables represent 3 levels of precision for the age of the subject, and they should be used according to the information available.
    1. AGE and AGETXT should never both be populated for the same subject. AGEU refers to whichever variable is used.
    2. If information is available about the time of birth for the subject, it should be presented in the variable BRTHDTC in ISO 8601 format, even if this is only partial information (not a complete date of birth).
    3. Data in BRTHDTC should never be derived from another variable. Either this information is collected or this variable should be blank.
    4. If a specific age for the subject is known, but no information regarding date/time of birth is available, then AGE and AGEU should be populated, using the most descriptive/precise unit for the data (e.g., 1 year, 2 months would be AGE = "14" and AGEU = "MONTHS").
    5. AGE and AGEU may be derived using an algorithm involving BRTHDTC and RFSTDTC. In this case, comments in the define file should indicate how AGE was populated.
    6. If only an approximate age is known (e.g., 6-8 weeks), then use AGETXT in conjunction with AGEU (e.g., AGETXT = "6-8" and AGEU = "WEEKS"). The format for AGETXT is number-number (e.g., "6-8").
  5. RFSTDTC, RFENDTC, and BRTHDTC represent date/time values, but they are considered to have a record qualifier role in DM. They are not considered to be timing variables as described in SDTM v1.5, Section 2.2.6, because they are not intended for use in the general observation classes. The subject may have records in other domains with a date/time prior to RFSTDTC and after the RFENDTC.
  6. SPECIES and STRAIN: These variables are permissible and should be used only if different species or strains are used during 1 study. If all the subjects in 1 study are of the same species, strain, and substrain, then this information is collected in the Trial Summary (TS) table. TX can have multiple species and/or strains if they are different by set.
  7. The SETCD variable is to be used to uniquely identify all distinct "groups" or "trial sets." A trial set is a collection of subjects that have a common set of parameters defined in the protocol, where those parameters include experimental parameters, product exposure strategies, inherent characteristics (e.g., strain) parameters, and/or applicant-defined attributes (e.g., control group designation). In general, if a distinction between arms does not cause the subjects to be summarized or grouped independently, then the arms should not be reflected as a separate trial set. A subject may belong to 1 and only 1 trial set.
  8. ARM: An arm is a planned path through a study. This path covers the entire time of the study. The group of subjects assigned to an arm is also often colloquially called an "arm." The group of subjects assigned to an arm is also often called an "exposure group," although it is not necessarily a product exposure group. The same arm can be used to separate subjects into different satellites. For example, use SETCD for assigning main study subjects and TK study subjects.

  • No labels