PK parameters and CDISC

[js3110]

Hi!

We are trying to create a file to match up all the PKNCA parameters to the CDISC ones, so that we can create a PP and ADPP output in our app. I can see that this is also an issue that you are working on in #403 , so we look forward to when this is working!
For now, so we can make a temporary solution, I have one question:

1. For time_above, how is this calculated? There are two options in CDISC: "TABL", "Time Above Baseline"or
   "TAT", "Time Above Threshold", which is the PKNCA one?

FYI- we have now created a .csv that has the PKNCA names matched with the CDISC labels (to the best of our knowledge), so if this would help you with issue #403 then let me know and we can share it with you!
Although there are a few that don't always match up as the pknca parameters are sometimes more specific than the CDISC ones, so one CDISC could technically cover many pknca. It would be interesting to know how you are planning on dealing with this!

[billdenney]

First: Yes, please share the PKNCA-CDISC label mapping! I plan to implement the mapping by modifying the add.interval.col() function so that it takes a CDISC label. And, then, I'm planning to modify as.data.frame.PKNCAresults() so that it has an out_format = "sdtm" which will apply that mapping.

Second: time_above has a similar answer to your question in #405. As I understand it "TABL" is a specific example of "TAT" (where the threshold is set to the baseline value). So, PKNCA calculates the general "TAT".

[Gero1999]

Here is the mapping file, feel free to check and give feedback:

pknca_param_mapping_cdisc.csv

There is a column for those parameters that we were not able to identify or PKNCA specific, is.cdisc.sure = F

[js3110]

Ae should be RCAMINT here!

[js3110]

can also rename time above to TAT now as well ! :)