Versions Compared

Key

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

...

Three different data collection scenarios may be used for for laboratory test results. It is up to the sponsor applicant to determine which data collection scenario best meets the study needs. Details on these collections scenarios can be found in section 2.7.6.9, CDASH Laboratory Test Results (LB).

Scenario 1.0 Central Processing  In this scenario, subject specimens are taken at the site and sent out for processing. Results are provided in an electronic file; the sponsor applicant has chosen to collect reconciliation data (e.g., LBDAT, LBTIM, VISITNUM, LBREFID) on the CRF. This scenario may also apply if the central lab results are imported into a sponsorapplicant's electronic data collection (EDC) system. The fields for test results are not defined here, as these data are not part of the CRF.

Scenario 2: Central Processing with Investigator Assessment of Clinical Significance Assessment for Abnormal Values  In this scenario, subject specimens are taken at the site and sent to a central lab for processing. The results are provided in an electronic file to the sponsorapplicant. In addition, the results are provided to the investigator for assessment of clinical significance for any abnormal values, and that information is provided to the sponsor applicant on the CRF.

Scenario 3: Local Processing  In this scenario, subject specimens are taken and analyzed, and then the results are recorded directly on the CRF. 

...

Logical Observation Identifiers Names and Codes (LOINC®) is clinical terminology that is important for laboratory test orders and results, and is one of a suite of designated standards for use in U.S. Federal Government systems for the electronic exchange of clinical health information. It is recommended, that if the laboratory used for testing is able to provide the appropriate LOINC® that they be included in the SDTM dataset. If using LBLOINC, the sponsor applicant is expected to provide the dictionary name and version used to map the terms, utilizing Define-XML external codelist attributes. 

...