Question:Using Phoenix WinNonlin Crossover object for Tmax test [Nonparametrics]

posted by 0521 – China, 2018-11-09 08:02 (1966 d 01:57 ago) – Posting: # 19550
Views: 9,210

Dear Helmut Schütz,

When using Phoenix WinNonlin Crossover object for Tmax testing, how can I judge whether it is equivalent by the result? :confused:

I read the "The Use Of Non-Parametric Methods In The Statistical Analysis" document (PMID: 4556704), and I think he is doing the following steps to judge:

1. Determine if the P value of the sequence is greater than 0.05,
2. If the P value of the sequence is less than 0.05, the test of "Treatment" cannot be performed.
3. If the P value of the sequence is greater than 0.05, it is judged whether the P value of the treatment is greater than 0.05.
4. If the P value of the Treatment is greater than the equivalent, otherwise it is not equivalent.

5. If the P value of the sequence and the P value of the Period are both greater than 0.05, a sign test can be used instead of the rank sum test used in the above steps.

Assuming α = 0.05, all of the above P values are the results in the "Effects" table.

Is the above judgment process correct? :confused:
If not, what is the correct judgment process? :confused:

PARAMETER  Test                                T_stat    L_stat   p_Value
Tmax       Sequence                            177.5              0.91791649
Tmax       Treatment|(SEQ1=SEQ2)                 220             0.021731156
Tmax       Period|(SEQ1=SEQ2)                    185              0.62428829
Tmax       Treatment & Residual (simultaneous)        5.6567621  0.059108471


[image]

Best,

0521

Complete thread:

UA Flag
Activity
 Admin contact
22,957 posts in 4,819 threads, 1,640 registered users;
73 visitors (0 registered, 73 guests [including 3 identified bots]).
Forum time: 10:00 CET (Europe/Vienna)

Nothing shows a lack of mathematical education more
than an overly precise calculation.    Carl Friedrich Gauß

The Bioequivalence and Bioavailability Forum is hosted by
BEBAC Ing. Helmut Schütz
HTML5