Versions Compared

Key

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

...

Metadataspec
NumVariable PopulationImplementation
1Result Precision
  • For numeric non-derived data, --ORRES will represent results to precision collected. Precision will not be artificially changed due to computer storage considerations.
  • For numeric derived data, --ORRES and --STRESC will represent the correct number of significant figures based upon the calculation used to derive the value. Trailing zeroes will be retained when significant.
2Standardized Units

Applicants may standardize units within a study for a given test per scientific and regulatory requirements. Standardization of units is recommended when data for the same test are collected via different sources using different units. In such cases, --ORRESU will represent the collected unit and --STRESU will represent the standardized unit.

3Original and Standardized Results (--ORRES, --ORRESU, --STRESC, --STRESU, --STRESN) 

The following is applicable to results that are not :

  • Not collected via QRS instruments
. Please
  • ; please refer to QS domain assumptions for expected variable population. 
  • Not collected free-text for 

  • --ORRES will be populated with the result of the measurement or finding as originally collected or received, using controlled terminology when applicable.  
    • When applicable, the unit associated the value of --ORRES will be populated in --ORRESU, using controlled terminology. 
  • Values will be populated in --STRESC when --ORRES is populated. The value of --STRESC will be:
    • Derived by the conversion of numeric values in --ORRES to numeric values with standard units. Standard units will be represented in --STRESU using controlled terminology.
      • Numeric --ORRES values with characters attached (e.g., a greater than (>) or less than (<) sign) will be converted to standard units and the value of --STRESC will maintain the attached character (e.g., >10,000, <1). 
    • The assigned of the value of --ORRES. 
      • For nonclinical studies, in the Macroscopic and Microscopic Findings (MA/MI) domains, --ORRES may contain a finding with multiple concatenated modifiers. In this case, --STRESC would represent only the finding without the modifiers. 
  • Numeric values represented in --STRESC will be assigned to --STRESN. If --STRESC is a character value, then, --STRESN will be null. 
    • Numeric values with attached characters (e.g., >10,000, <1) are considered to be character results and will not be populated in --STRESN.
4Tests Not Done

When an entire examination (e.g., Laboratory Test Results (LB)), a group of tests (e.g., hematology or urinalysis), or an individual test (e.g., glucose) is not done for a USUBJID, POOLID, or SPTOBID and this information is explicitly captured with or without the reason for not collecting the information, record(s) can be created in the dataset to represent these data.

In such cases, applicants may include:

  • Individual records for each test not done for each subject or pool; or
  • One record for each subject or pool for a group of tests that were not done. In such cases:
    • The paired values of --TESTCD and --TEST will represent a general description of testing in scope for the domain and will be used for all groupings of not done tests within the domain.  
      • --TESTCD will be the domain code concatenated with the word "ALL".
      • --TEST will be the domain description per controlled terminology.
    • --CAT will represent the group of tests not done.
    • --ORRES will be null.
    • --STAT will be "NOT DONE".
    • --REASND will be the reason the group of tests was not done, if collected.

For example, if a group of hematology or urinalysis tests represented in the LB domain are not done for a subject, then:

USUBJIDLBTESTCDLBTESTLBCATLBORRESLBSTATLBREASND
ABC-001LBALLLaboratory Test ResultsHEMATOLOGY
NOT DONE
ABC-001LBALLLaboratory Test ResultsURINALYSIS
NOT DONENo urine specimen present
5Biological Significance 

Nonclinical Only:

  • For assessments of biological significance when the overall interpretation is a record in the domain, use the supplemental qualifier (SUPP--) record (with QNAM = --BIOSIG) linked to the record that contains the overall interpretation or a particular result.
    • An example would be a QNAM value of LBBIOSIG in SUPPLB with a value of "Y", indicating that a lab result for albumin of 30 mg/mL was biologically significant.
  • Biological significance is not the same as the concepts of normal and abnormal, which are generally represented in --ORRES.
6Clinical Significance

Product Impact on Individual Health Only:

  • For assessments of clinical significance when the overall interpretation is a record in the domain, use the --CLSIG (Clinically Significant) variable on the record that contains the overall interpretation or a particular result.
    • For example, EGCLSIG = "Y" indicates that an ECG result of "ATRIAL FIBRILLATION" was clinically significant.
  • Clinical significance is not the same as the concepts of normal and abnormal and lab values out of normal range which are generally submitted in --ORRES and normal range/indicator variables respectively.
7Derived Records

...