Coming Soon: ADNCA and the PK Submission

This is Part 3 of a 3 Part Series

ADNCAv2.jpg

Written by Lucius Reinbolt, DataCeutics, Inc.; Liz MacDonald, Nuventra Pharma Sciences, Inc

INTRODUCTION

There is currently a gap in the SDTM and ADaM standards for handling and formatting data to allow for non-compartmental PK parameter calculations. The data that is required for PK parameter software is a combination of several datasets and therefore an SDTM convention like PC would not meet the necessary requirements for this analysis. In addition, the required data structure is more complicated than the currently defined ADaM BDS structure. Therefore, the ADaM leadership team formed a sub-team tasked with the creation of a new set of specifications specifically for this situation. The end goal of this sub-team was to develop standards that closely follow current ADaM guidance while allowing for flexibility to work with the various types of software packages that are used to analyze PK data and calculate parameters.  ADNCA is the end result of this sub-teams’ effort.

Pharmacokinetics is the study of the effect of the body on a drug. Calculation of pharmacokinetic parameters using a non-compartmental analysis (NCA) approach is a class of mathematical methods for studying the degree of exposure following administration of a drug. NCA is commonly used to analyze drug concentration data by subjects from clinical trials. The derivations result in pharmacokinetic parameters such as Cmax (maximum concentration), Tmax (time at maximum concentration), t1/2 (half-life), and AUC to t (area under the curve to the last time point) that allow the analyst to better understand the distribution of the drug in the body.

Pharmacokinetic parameters are typically calculated using software packages designed to support PK analyses using analysis ready data as the input. The input analysis data needs to comprehensively associate subject drug concentrations with study drug dosing and related time, support the exclusion of specific records and subjects, and provide other information as needed. Parameter calculation is based on the specific dosing regimen, the PK sample collection schedule, and the objective(s) associated with parameter calculations. The parameter calculations will require specific timing variables to relate PK concentration to the actual time from dose.

The flexibility of the BDS structure of the ADNCA will allow the user to incorporate data from multiple sources in order to complete the analysis. For example, if the it was important to segregate the analysis by sex, the SEX column from the ADSL could be added to the ADNCA dataset. The ability to add these qualifying variables is a unique and necessary feature of the dataset. 

Since the analysis data input for non-compartmental parameter calculation is subject to submission to regulatory bodies, it is important to base this dataset on the standardized (SDTM) tabulations data that will be submitted and to comply with ADaM standards. 

We will share the proposed approach through examples. The actual IG content will be publicly released only after internal ADaM review is completed.

TIMING VARIABLES

Pharmacokinetic Non-Compartmental Analysis is primarily a “time from the event” based analysis producing multiple derived parameters. The ADNCA dataset structure is designed to support commonly structured NCAs, including analyses with both discrete time measurements (typical for plasma or serum) and measurements from collections over time (typical for urine). The dataset format is designed to support common NCA analysis needs; additional variables can be added as needed to accommodate more complex derivations.

The ADNCA dataset structure may be used to create multiple tabular and graphical data presentations as they relate to NCA and pharmacokinetic and pharmacodynamics data review, as well as provide a means to assess event collection compliance where the data collected have a structured chronological sequence. Additionally, the ADNCA structure has the potential to be utilized for tabular and graphical data presentation in other pharmacokinetic and pharmacodynamic sparse sampling study designs that do not necessarily require NCA.

ADNCA is comprised of the combination of dose information and concentration results. These data are combined in order to facilitate the creation of both nominal and actual timing variables which are necessary to produce accurate PK parameters. The ADNCA dataset will also include timing variables that relate to the most recent dose as well as the very first dose given to the subject. This structure will, therefore, facilitate the analysis of data from a single dose and multiple dose studies.

SDTM cannot be used for the parameter calculations due to the structure of the individual datasets. The analysis needs the timing variables that are compared back to the dosing date and time and those variables need to be in units of hours, days, etc. This ADNCA dataset will follow the structure of an ADaM BDS. A new or unique data structure is not needed as the analysis of concentration versus time is not multivariate.

EXAMPLE 1: DIFFERENCE BETWEEN AVISIT IN ADNCA AND ‘DAY’ VARIABLES IN SDTM

The AVISIT variable in ADNCA is useful for PK analysis in many situations, for example, it is used as a key variable to extract the concentration-time profiles for different days in multiple day studies.

When deriving the AVISIT and AVISITN variables from tabulated variables in SDTM domains, the following examples shows how the AVISIT variable is different from the PCDY variable in the PC domain of SDTM. Similar considerations will apply to VISIT variables in SDTM domains.

The PCDY variable indicates the study day of when the sample was taken. This variable is one of the timing variables for the specific observations in the records of the PC domain dataset. The example below shows that for the samples taken 24 and 36 hours after dosing, the PCDY variable correctly indicates that this is day “2” and “3” of the study, respectively.

However, with respect to the concentration-time profile for PK analysis, the AVISIT variable needs to indicate that these samples are part of the profile that is related to the day 1 dose. Therefore, the AVISIT variable should have a value of “DAY 1” and corresponding AVISITN has the value of “1”.

Table 1

 Table 1: Example of Difference between AVISIT in ADNCA and ‘day’ variables in SDTM

Table 1: Example of Difference between AVISIT in ADNCA and ‘day’ variables in SDTM

Note that TRTRDTM is a numerical value representing the date and time. To make the table readable, the value of this variable is displayed as a date and time string.

EXAMPLE 2: TIMING AND VALUES FOR MULTIPLE ORAL DOSING

This example shows the nominal and relative times for a multiple oral dosing trial.
Note that the modified relative time from reference dose (MRRELTM) was added for analysis purposes: the negative ARRELTM on row 1 and row 8 is assigned zero, as PK software like Phoenix® WNL will only include observations starting from dosing, and not prior to dosing for parameter estimation.

 Table 2: Example of Timing and Values for Multiple Oral Dosing

Table 2: Example of Timing and Values for Multiple Oral Dosing

FLAGS

Flags are necessary to allow the data to communicate with the PK scientist and other data consumers. The scientist uses the flags on either a subject level or a record level. Allowing for subject level flags is a unique and necessary addition to ADNCA, as these flags often need to be programmed after the data is analyzed and pre-determined exclusion rules may not be applicable. ADNCA will allow for the inclusion of flags expected by the PK scientists for parameter calculations.

EXAMPLE 3: EXCLUSION FLAGS

This section shows examples for the use of the exclusion flags PKEFL for subject-level exclusions and PKREFL for record-level exclusions. The examples show exclusions for reasons that are mainly triggered by sampling considerations. Other reasons, for example records excluded due to a dosing issue, caused by some violation of dosing requirements, would be recorded accordingly.

The first table below shows two examples for record-level exclusions.
The record for subject CPW-s001 at nominal time 2 hours is excluded because no concentration value is available. The record should still be included in the dataset for traceability reasons and to support consistent reporting.

The records for subject CPW-s003 after the dose at time 0 hours are all excluded because the subject vomited too soon after the dose administration (PKEFL set to “Y” and REXSUBJ set to “Vomiting” for all records for this profile). Note that because this is flag indicates record-level exclusion, other observations about this subject would still be included in the analysis.

 Table 3: Example of Record Level Exclusions

Table 3: Example of Record Level Exclusions

The following table shows an example for subject-level exclusion but also includes some record-level exclusions.

  • The record for subject CPW-s011 at nominal time 0.25 hours is excluded because the sample was taken too late.
  • The record for subject CPW-s011 on AVISIT 2 is excluded because it is an intermediate control sample and there are not enough data for any PK analysis.
  • All records for subject CPW-s013 are excluded (PKEFL = “Y”) because there are not enough data for PK analysis for day 1 (REXSUBJ = “Incomp. Day 1 Samples”) and it was decided not to analyze anyof the data for this subject.
 Table 4: Example of Subject Level Exclusion

Table 4: Example of Subject Level Exclusion

CONCLUSION

ADNCA is the result of the ADaM sub-team tasked with creating a standard for analysis data used to support the calculation of PK parameters. What we proposed needs to comply with ADaM standards as well as work with various software packages for PK analysis. ADNCA is still a work in progress. The sub-team is working closely with the ADaM leadership to finalize this submission standard. Please stand by and await this standard to complete ADaM review and eventually make it to public review.

 

REFERENCES

Xie, Y., Chai, P., Kirby S., Wang N. 2011 “Pharmacokinetic Data Submission in the CDISC Environment.” American Association of Pharmaceutical Scientists

 

We have designed this 3 Part series to give the reader a look into the use of this important programming tool from a “basic” point of view to the more technical aspects discussed at the end of the series.

In Part 1, Dr. Joe E Serfaty gave a general overview of how Pharmacokinetics and Pharmacodynamics (PK/PD) plays a key role with 3 key stakeholders: Patients, Drug Companies, and the Federal Drug Administration.

In Part 2, we will focus more on PK with a paper authored by Timothy Harrington titled, “PK Explained” with a bit more technical information on how PK is used in drug trials.