Skip to main content
Skip table of contents

Multiple doses and steady state

Objectives: learn how to define and use a PK model with multiple doses or assuming steady-state.

Demos: multidose_project, addl_project, ss1_project, ss2_project, ss3_project

Multiple doses

  • multidose_project (data = ‘multidose_data.txt’ , model = ‘lib:bolus_1cpt_Vk.txt’)

In this project, each patient receives several iv bolus injections. Each dose is represented by a row in the data file multidose_data.txt:

2018-02-14_00h08_20-1024x381-20240603-090953.png

The PK model and the statistical model used in this project properly fit the observed data of each individual. Even if there is no observation between 12h and 72h, predicted concentrations computed on this time interval exhibit the multiple doses received by each patient:

VPCs, which is a diagnosis tool, are based on the design of the observations and therefore “ignore” what may happen between 12h and 72h:

2018-02-14_00h06_49-20240603-091001.png

On the other hand, the prediction distribution, which is not a diagnosis tool, computes the distribution of the predicted concentration at any time point:

2018-02-14_00h07_28-20240603-091019.png

Additional doses (ADDL)

https://www.youtube.com/watch?v=z_pHfV6c9Ro

 

  • addl_project (data = ‘addl_data.txt’ , model = ‘lib:bolus_1cpt_Vk.txt’)

We can note in the previous project, that, for each patient, the interval time between two successive doses is the same (12 hours for each patient) and the amount of drug which is administrated is always the same as well (40mg for each patient). We can take advantage of this design in order to simplify the data file by defining, for each patient, a unique amount (AMT), the number of additional doses which are administrated after the first one (ADDITIONAL DOSES) and the time interval between successive doses (INTERDOSE INTERVAL):

2018-02-14_00h09_41-1024x380-20240603-091051.png

The keywords ADDL and II are automatically recognized by Monolix.

Remarks:

  • Results obtained with this project, i.e. with this data file, are identical to the ones obtained with the previous project.

  • It is possible to combine single doses (using ADDL=0) and repeated doses in a same data file.

Steady-state

  • ss1_project (data = ‘ss1_data.txt’ , model = ‘lib:oral0_1cpt_Tk0VCl.txt’)

The dose, orally administrated at time 0 to each patient, is assumed to be a “steady-state dose” which means that a  “large” number of doses before time 0 have been administrated, with a constant amount and a constant interval dosing, such that steady-state, i.e. equilibrium, is reached at time 0. The data file ss1_data contains a column STEADY STATE which indicates if the dose is a steady-state dose or not and a column INTERDOSE INTERVAL for the inter-dose interval:

2017-11-16_15h55_59-20240603-091110.png

Click on Check the initial fixed effects to display the predicted concentration between the last dose administrated at time 0. One can see that the initial concentration is not 0 but the result of the steady state calculation.

2018-01-23_10h54_49-1024x616-20240603-091124.png

We see on this plot that Monolix adds 5 doses before the last dose to reach steady-state. Individual fits display the predicted concentrations computed with these additional doses:

2017-11-16_16h01_47-1024x762-20240603-091134.png

If the dynamics is slow, adding 5 doses before the last dose might not be sufficient. You can adapt the number of doses in the frame data and thus define it for all individuals as on the following figure.

2017-11-16_16h04_20-20240603-091235.png

leading to the following check initial fixed effects

2018-01-23_10h57_18-1024x616-20240603-091242.png

  • ss2_project (data = ‘ss2_data.txt’ , model = ‘lib:oral0_1cpt_Tk0VCl.txt’)

Steady-state and non steady-sates doses are combined in this project:

2017-11-16_16h06_47-20240603-091255.png

Individual fits display the predicted concentrations computed with this combination of doses:

2017-11-16_16h08_58-1024x751-20240603-091303.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.