Predicting Responses to Pregabalin for Painful Diabetic Peripheral Neuropathy Based on Trajectory-Focused Patient Profiles Derived from the First 4 Weeks of Treatment.

INTRODUCTION: Prediction of final clinical outcomes based on early weeks of treatment can enable more effective patient care for chronic pain. Our goal was to predict, with at least 90% accuracy, 12- to 13-week outcomes for pregabalin-treated painful diabetic peripheral neuropathy (pDPN) patients based on 4 weeks of pain and pain-related sleep interference data.
METHODS: We utilized active treatment data from six placebo-controlled randomized controlled trials (n = 939) designed to evaluate efficacy of pregabalin for reducing pain in patients with pDPN. We implemented a three-step, trajectory-focused analytics approach based upon patient responses collected during the first 4 weeks using monotonicity, path length, frequency domain (FD), and k-nearest neighbor (kNN) methods. The first two steps were based on combinations of baseline pain, pain at 4 weeks, weekly monotonicity and path length during the first 4 weeks, and assignment of patients to one of four responder groups (based on presence/absence of 50% or 30% reduction from baseline pain at 4 and at 12/13 weeks). The third step included agreement between prediction of logistic regression of daily FD amplitudes and assignment made from kNN analyses.
RESULTS: Step 1 correctly assigned 520/939 patients from the six studies to a responder group using a 3-metric combination approach based on unique assignment to a 50% responder group. Step 2 (applied to the remaining 419 patients) predicted an additional 121 patients, using a blend of 50% and 30% responder thresholds. Step 3 (using a combination of FD and kNN analyses) predicted 204 of the remaining 298 patients using the 50% responder threshold. Our approach correctly predicted 90.0% of all patients.
CONCLUSION: By correctly predicting 12- to 13-week responder outcomes with 90% accuracy based on responses from the first month of treatment, we demonstrated the value of trajectory measures in predicting pDPN patient response to pregabalin. TRIAL REGISTRATION: www.clinicaltrials.gov identifiers, NCT00156078/NCT00159679/NCT00143156/NCT00553475. FUNDING: Pfizer. Plain language summary available for this article.

RCT Entities:   Population Interventions Outcomes

Plain Language Summary

To help healthcare providers make better choices on treatments, it is important to understand patient characteristics and how early responses to a drug therapy might predict later responses to that same drug. This study used data from several clinical trials that enrolled patients with pain associated with diabetic peripheral neuropathy treated with pregabalin. We assessed the characteristics of the patients who did or did not show a clinically meaningful response to pregabalin as measured by pain reduction after the first month of therapy and at the end of treatment to identify a “trajectory” of their pain response to better predict their outcomes. We were able to correctly predict the outcomes of these patients at 12 or 13 weeks with 90% accuracy based on the patients’ response in the first 4 weeks.

Introduction

Prediction of clinical outcomes based on early weeks of drug therapy can lead to the more effective treatment of patients suffering from chronic pain. These patients pose many challenges for clinicians [1], and the effects of inadequate treatment are felt by patients, clinicians, healthcare delivery systems, and other stakeholders affected by an individual’s chronic pain [2-4]. Our prior work with patients with painful diabetic peripheral neuropathy (pDPN) being treated with pregabalin suggested that more information might be discovered from the time course of conditions of care for patients and their treatments [5, 6].

While time-series data can be rich sources of information that could be especially useful for predicting patient outcomes, these types of data are often challenging to analyze, especially when various covariates (e.g., sleep interference) also change over time in patients with pDPN [7-9] or other chronic pain conditions [10-12]. Some investigators have used multilevel regression modeling (also known as mixed-effects modeling or hierarchical linear modeling) and multilevel structural equation modeling to evaluate between- and within-subjects effects of pain, pain-related sleep interference (PRSI) responses, and other variables [10-14]. See Supplemental File 6 for more information on this topic.

Our approach was to seek the simpler solutions first before moving toward building a multilevel model or a growth mixture model [15-25] (as described in Supplemental File 6). Instead, we defined four “responder groups” (i.e., non-latent classes) based on the responder status of patients at specific times (i.e., at week 4 and at the end of study). They are non-latent because they are defined a priori based on known characteristics of patients. The goal of our method was to make predictions about the evolution of pain for each patient through assignment to one of the responder groups. As an alternative to starting with a multilevel model, our approach was to evaluate patterns of the actual values of three linear variables for their ability to predict whether a patient belongs to a particular responder group. In terms of these variables, we had previously explored monotonicity and path length because graphic representation of these metrics had implied differences across responder groups. Based on our earlier work [5], we also started with a stepwise approach that was person-centered (e.g., cluster analysis, latent class analysis, and finite mixture modeling, which aim to classify individuals into distinct groups based on individual response patterns) rather than variable-centered (e.g., regression, factor analysis, and structural equation modeling, which describe relationships among variables) [26]. This prior work had affirmed the advantages of stepwise approaches over making predictions all at once.

Our goal in the present study was to correctly predict 12- to 13-week responder outcomes in patients with pDPN treated with pregabalin, with at least 90% accuracy based on 4 weeks of pain and pain-related sleep interference data.

Methods

We utilized data from six randomized placebo-controlled trials (RCTs) (n = 939) designed to evaluate the efficacy of pregabalin for reducing pain in patients with pDPN (Pfizer label ref.) [27]. The trials were conducted between November 2000 and March 2009 in Asia, Australia, Canada, Europe, Latin America, the Middle East, South Africa, and the United States. Patients received flexible (150–600 mg/day) or fixed-dose pregabalin (75, 150, 300, or 600 mg/day) or placebo for 5–13 weeks (Table 1). Since the current modeling was a post hoc pooled analysis evaluating response to treatment, patients were required to have four or more data points where they were confirmed taking pregabalin. Each of the six studies [28-33] shared fundamental inclusion criteria, including the requirement for patients to be aged ≥ 18 years; have a primary diagnosis of pDPN [type 1 or 2 diabetes mellitus with glycated hemoglobin (HbA1c) ≤ 11% and painful, distal, symmetrical, or sensorimotor polyneuropathy for ≥ 6 months]; have an average pain score over a 7-day baseline period of ≥ 4 [recorded in patients’ daily pain diaries on an 11-point numeric rating scale (NRS), where 0 = no pain and 10 = worst possible pain]; and have a score ≥ 40 mm on the 0–100 mm visual analog scale of the Short-Form McGill Pain Questionnaire at screening and randomization. Patients with creatinine clearance rates ≤ 60 mL/min were excluded, as were patients with any conditions that could jeopardize their health or confound assessment of pain due to pDPN.

Table 1

Summary of patients divided by dose

12-/13-weeks RCTsa	Pregabalin dose
	Flexible doseb	Flexible adjusted dosec	150 mg/day	300 mg/day	600 mg/day	Total
n	83	193	74	297	292	939
% of total	8.8	20.6	7.9	31.6	31.1	100
Females (%)	37 (44.6%)	116 (60.1%)	33 (44.6%)	104 (35.0%)	116 (39.7%)	406 (43.2%)
Males (%)	46 (55.4%)	77 (39.9%)	41 (55.4%)	193 (65.0%)	176 (60.3%)	533 (56.8%)
Age (years), mean (SD)	61.3 (10.3)	57.0 (10.0)	57.7 (12.4)	60.4 (10.0)	58.6 (10.3)	59.0 (10.4)
BMI (kg/m2), mean (SD)	30.2 (4.7)	28.0 (5.7)	29.3 (4.5)	29.7 (7.7)	31.5 (7.3)	29.9 (6.8)
Normal weight (%)	12 (14.5%)	65 (33.7%)	15 (20.3%)	90 (30.3%)	44 (15.1%)	226 (24.1%)
Overweight (%)	29 (34.9%)	72 (37.3%)	29 (39.2%)	91 (30.6%)	83 (28.4%)	304 (32.4%)
Obese (%)	42 (50.6%)	56 (29.0%)	30 (40.5%)	116 (39.1%)	165 (56.5%)	409 (43.6%)
Duration of pDPN (years), mean (SD)d	5.1 (4.3)d	2.8 (1.4)	4.5 (3.9)	4.9 (4.0)	4.3 (3.3)d	4.2 (3.5)d

BMI body mass index, n number of patients, pDPN painful diabetic peripheral neuropathy, RCT randomized controlled trial, SD standard deviation

aStudy 1008-149 [28] conducted Nov 2000–May 2002 in Australia/Europe/South Africa: DB-RCT with 1 week baseline, 1 week dose escalation, 11 weeks maintenance with placebo, pregabalin 150, pregabalin 300, and pregabalin 600 doses. Study 1008-155 (A0081049) [29] conducted Jul 2001–Dec 2002 in Europe: DB-RCT with 1 week baseline, 1–4 weeks dose escalation, 8–11 weeks maintenance with placebo, pregabalin 150–600 flexible dosing, and pregabalin 600 doses. Study A0081030 [30] conducted Jan 2005–Apr 2006 in Asia/Latin America/Middle East: DB-RCT with 1 week baseline, 6 weeks dose escalation, 6 weeks maintenance, 1 week withdrawal with placebo, pregabalin 150–600 flexible dosing (NCT00156078). Study A0081060 [31] conducted Sep 2004–Oct 2005 in US: DB-RCT with 1 week baseline, 1 week dose escalation, 12 weeks maintenance with placebo, pregabalin 600 dose (NCT00159679). Study A0081071 [33] conducted May 2005–May 2007 in US: DB-RCT with 1–2 weeks baseline, 1 week dose escalation, 12 weeks maintenance, 1 week withdrawal with placebo, pregabalin 300, and pregabalin 600 doses (NCT00143156). Study A0081163 [32] conducted Oct 2007–Mar 2009 in Japan: DB-RCT with 1 week baseline, 1 week dose escalation, 12 weeks maintenance, 1 week withdrawal with placebo, pregabalin 300, and pregabalin 600 doses (NCT00553475)

bPatients with 1–4 weeks escalation phase and 8–11 weeks maintenance (Protocol 1008-155)

cPatients with 6 weeks escalation phase and 6 weeks maintenance (Protocol A0081030)

d38 patients with missing values for duration of pDPN: 21 of them are flexible dose patients, and 17 are 600 mg/day dose patients

All studies were conducted in compliance with the ethics principles originating in or derived from the Declaration of Helsinki, internal review board requirements, or Good Clinical Practice guidelines, and all participants provided written informed consent before participation.

The primary efficacy outcome in each study was change in pain score (on the 0–10 NRS). Pain responders at the 50% threshold were defined as those with [pain score at baseline − pain score (t)]/pain score at baseline of ≥ 50% (where t = time at the end of the study). Secondary efficacy outcomes in each study included change from baseline to end of study in PRSI scores derived from daily sleep diaries in which patients rated how much their pain had interfered with their sleep using a 0–10 NRS (where 0 = pain does not interfere with sleep and 10 = pain completely interferes with sleep).

We derived two measures that reflected the trajectories of the NRS data during the first 4 weeks. The first measure, monotonicity, is the extent to which the scores are consistently decreasing or increasing during the first 4 weeks of treatment. A value of − 1 or + 1 means that each of the four points is lower or higher, respectively, than the previous one. Given that there are four points, there are seven possible values for monotonicity (− 1, − 0.667, − 0.333, 0, + 0.333, + 0.667, + 1). See Supplementary File S1 for more information about monotonicity.

The second measure, path length, is a measure of the extent to which a trajectory has fluctuations over time. It is the sum of the absolute value of the unit change from week to week. For example, if pain starts at rating of 8 and reduces to 6 after the first week, the value of 2 is used for the week 1 change. This is repeated for weeks 2, 3, and 4. In theory, the maximum path length could be 40 in the first 4 weeks given integer values from 0 (4× a pain score change of 0) to 40 (4× a pain score change from 0 toward 10 or from 10 toward 0). The smaller the path length, the more stable the trajectory (with a minimum value of 0, which indicates an unchanging trajectory), whereas the larger the path length, the wider the range of values covered by the trajectory. See Supplementary File S2 for more information on path length.

In addition to the primary efficacy outcome of being a 50% pain responder, we defined another measure to use for prediction based upon being a 30% pain responder, which is a threshold that has previously been determined to be clinically meaningful [34]. In summary, we started with the following variables for prediction: Pain0 = pain at week 0; Pain4 = pain at week 4; PMono4 = monotonicity of weekly pain from week 0 to week 4; PPL4 = path length of weekly pain from week 0 to week 4; 50 PRS4 = pain responder status at 50% at week 4; and 30 PRS4 = pain responder status at 30% at week 4.

We then identified four responder groups reflecting responder status at 4 weeks and responder status at 12–13 weeks. The four responder groups are:

Patients who were non-responders both at week 4 and at final week;

Patients who were non-responders at week 4, but then became responders at final week;

Patients who were responders both at week 4 and at final week; and

Patients who were responders at week 4, but then became non-responders at final week.

In order to define the responder groups, we fixed the pain responder thresholds to either 50 or 30% depending on the different steps of our approach (described below). Thus, in every step of our approach, there were always four responder groups, but each step had its own definition of responder groups based on the pain responder thresholds used. We were then able to use the first 4 weeks of data to predict 12- to 13-week responder status without including any additional patient characteristics.

Figure 1 summarizes our three-step approach. In Step 1, we used the actual values of four different variables that, when combined, create a unique pattern (or signature) that can be associated with one of the four responder groups The data elements we used were PMono4, PPL4, Pain4, and Pain0. We then used unique patterns of three of the four variables (referred to as “3-metric combinations”) in order to identify subgroups of patients. Thus, the four possible 3-metric combinations of the data elements were (1) PMono4-PPL4-Pain4, (2) PMono4-PPL4-Pain0, (3) PMono4-Pain4-Pain0, and (4) PPL4-Pain4-Pain0. We considered all four of these combinations for each patient. In particular, for each patient for whom there was at least one 3-metric combination of the data elements that uniquely fit into only one responder group at week 4, we made the prediction that the patient would belong to that very responder group at the 50% responder threshold level at the end of the final week (week 12 or 13, depending on the study). For any patients whom we could not correctly classify in Step 1, we applied Step 2 (subdivided into parts a and b). For Step 2a, we relaxed the responder threshold criterion for prediction in the final week from 50% to 30%, but maintained the 50% threshold for week 4. For Step 2b, we also relaxed the responder threshold for prediction in the final week to 30%; however, in this case, we additionally relaxed the responder threshold to 30% for week 4. Only patients whom we could not correctly predict in Step 2a moved on to be evaluated in Step 2b.

Fig. 1

Flow chart of steps for prediction of responder status at 12 or 13 weeks. FD frequency domain, kNN k-nearest neighbor, Pain pain at week 0, Pain pain at week 4, PMono monotonicity of weekly pain from week 0 to week 4, PPL path length of weekly pain from week 0 to week 4, 30 PRS pain responder status at 30% at week 4, PRSI pain-related sleep interference at week 0, PRSIPL path length of weekly sleep interference from week 0 to week 4, 30 PRSIRS pain-related sleep interference responder status of 30% at week 4, 50 PRSIRS pain-related sleep interference responder status of 50% at week 4. The specific actions associated with the steps in the flow chart are shown below: (1) Collect two data elements at baseline and weekly until week 4 so that four data points exist for each patient: Pain on 0–10 NRS and pain-related sleep interference on 0–10 NRS. (2) Calculate monotonicity for the first 4 weeks (see Supplemental File 1). (3) Calculate path length for the first 4 weeks (see Supplemental File 2). (4) Generate the following four combinations of three of the data elements generated in the prior three actions: (a) 4-week monotonicity, 4-week path length, pain score at week 4 (PMono4-PPL4-Pain4), (b) 4-week monotonicity, 4-week path length, pain score at baseline (PMono4-PPL4-Pain0), (c) 4-week monotonicity, pain score at week 4, pain score at baseline (PMono4-Pain4-Pain0), and (d) 4-week path length, pain score at week 4, pain score at baseline (PPL4-Pain4-Pain0). (5) Check four patterns and see if the pattern aligns with those that are uniquely associated with one of the four responder groups (responders at both week 4 and the final week, non-responders at both week 4 and the final week, responders at week 4 but non-responders at the final week, non-responders at week 4 but responders at the final week). (6) If the pattern aligns, predict patient outcome at the final week (Step 1). (7) If the pattern does not align, move to Step 2a and check whether the pattern aligns with those uniquely associated with one of the four responder groups when the 30% threshold for being a responder in the final week is used. (8) If the pattern aligns with those uniquely associated with one of the four responder groups, then predict the patient’s outcome at the final week (Step 2a). (9) If the pattern does not align, move to Step 2b and check whether  the pattern aligns with those uniquely associated with one of the four responder groups when the 30% threshold is used for being a responder in the final week and in week 4. (10) If the pattern aligns with those uniquely associated with one of the four responder groups, then predict the patient’s outcome at the final week (Step 2b). (11) If the pattern does not align, move to Step 3 and implement the kNN analysis (see Supplemental File 4) by considering the following seven data elements for describing each patient: (a) pain-related sleep interference at baseline, (b) pain score at baseline, (c) 4-week path length of pain-related sleep interference, (d) 4-week path length of pain, (e) pain-related sleep interference responder status at week 4 (30% threshold), (f) pain-related sleep interference responder status at week 4 (50% threshold), (g) pain responder status at week 4 (30% threshold). (12) Identify if there are one or more nearest neighbors; if there is only one neighbor with the same vector values, then use it to predict the patient’s outcome and if there is more than one neighbor with the same value, the majority is selected for the prediction (see Supplemental File 4 for examples). (13) Before selecting the final choice of outcome for Step 3, also implement the FD analysis. For the FD analysis, use 28 days of daily pain score data and follow the steps outlined in Supplemental File 3. (14) Compare the outcomes predicted by the FD analysis with the outcome predicted by the kNN analysis. If the both the FD and kNN analyses assign the patient to the same responder group, select that responder group for the outcome. (15) If the responder group assignment differs between the FD analysis and the kNN analysis, use the responder group based on the one assigned by the FD analysis if the patient was a responder at week 4; use the responder group based on the one assigned by the kNN analysis if the patient was a non-responder at week 4. (16) If daily data are not available, use the kNN analysis alone for Step 3

All patients not correctly predicted in the first two steps were then considered in Step 3. In Step 3, we relied on comparing the results of predictions by two different methods. The first method utilized the frequency domain (FD) instead of the typical time domain. While the time domain reflects the changes in the amplitude of a signal over time, the FD shows how many amplitude values of a signal occur within a given time period (i.e., their frequencies). Typically, a transformation is required to make this change, and we applied the widely used Fourier transform. Fourier transformation [35] was applied to the 28 daily pain scores from week 0 to week 4, and then a logistic regression was performed on the outputs of the Fourier transformation. These outputs included the amplitudes of each of the frequency components (i.e., harmonics) of the signal [36]. With this new way of describing a patient’s trajectory, we believed we could identify a patient’s responder status at the final week based on the patient’s responder status at week 4. In order to know how to classify the patients, we used the logistic regression of the amplitudes of the patients who had been predicted with 100% accuracy in Step 1. The hypothesis behind our application of FD analysis is that pain score trajectories that fluctuate with harmonics of similar frequencies may be considered similar. See Supplementary File S3 for more information on the FD analysis.

For the second method, we used a technique called k-nearest neighbors (kNN) [37, 38]. kNN is a classification method that considers each patient as a vector of a certain number of variables, and it associates each patient to other patients “closest” to him or her, where “closest” is to be identified with respect to the Euclidean distance (ordinary straight-line distance between two points) computed between the vectors representing the patients. We introduced patient responses for sleep interference from week 0 to week 4, which conveyed useful information not previously used in our approach thus far in order to better describe patients and, therefore, correctly identify similar patients for prediction. We performed a kNN analysis (with k = 1, which means the single closest patient) using the following variables: pain-related sleep interference at week 0 (PRSI0), pain at week 0 (Pain0), path length of weekly sleep interference from week 0 to week 4 (PRSIPL4), PPL4, pain-related sleep interference responder status of 30% at week 4 (30 PRSIRS4), pain-related sleep interference responder status of 50% at week 4 (50 PRSIRS4), and a pain responder status of 30% at week 4 (30 PRS4). We added pain-related sleep interference for the kNN analysis because of the well-documented interactions between pain and PRSI [7-9]. For each patient considered in Step 3, we selected the closest (nearest neighbor) patient based on the kNN method and assigned the predicted outcome of the patient being considered to be the same as that of the nearest neighbor. We again chose to use the patients correctly predicted in Step 1 as the patients whom we would consider as candidates for the “nearest neighbor”. Once we identified the nearest neighbor, we chose this nearest neighbor’s outcome to be the predicted outcome for each patient being considered in Step 3. Supporting information on the kNN analysis is available in Supplementary File S4. In essence, by evaluating patients based on a vector of these trajectory-defined pain and PRSI data elements, we generated a patient profile based on trajectory-focused data elements.

With respect to the FD and kNN analysis methods, we made no a priori assumptions regarding the superiority of one over the other; we considered each independently and looked at agreements and disagreements in their responder predictions for each analysis. Accordingly, we examined two possible cases for each patient: the two methods provided the same prediction (i.e., agreement), or they provided different predictions (i.e., disagreement). In the case of agreement, we decided to trust the prediction for that patient, whereas in the case of disagreement, we evaluated whether in a relative sense one method was superior to the other in identifying patients who were either non-responders at week 4 or responders at week 4. As Step 3 always provided a prediction, there were no patients for whom we did not have a prediction, unlike the previous steps.

We evaluated the overall performance of our approach using an accuracy ratio defined as the proportion of correctly predicted patients, independent of the thresholds used to define the responder groups.

Results

Using the various 3-metric combinations approach for unique assignment to a responder group, Step 1 correctly assigned 520 (55.4%) of the patients from the six studies (n = 939) where the pain responder threshold was set to 50% at week 4 and at the final week. Detailed prediction results by responder group for Step 1 are shown in Supplementary Table S1. Given the 11-point NRS pain scale, there were only seven possible values for Pain0, since patients were not enrolled in the studies unless the baseline pain value was at least 4. There were 11 possible values for Pain4, seven possible values for PMono4, and 41 theoretically possible values for PPL4. In reality, no patient had a path length that exceeded 21. The actual values and patterns of 3-metric combinations of pain data elements are shown in Supplementary File S5.

Step 2 was then applied to the 419 patients remaining after Step 1 (44.6% of the total of 939 patients). Step 2 added 121 patients (12.9% of the total of 939 patients) to the number of correctly predicted patients for a total of 641 correctly predicted patients after Steps 1 and 2 (68.3% of the total of 939 patients). Specifically, Step 2a yielded 108 correct predictions using the 3-metric combination approach with the pain responder threshold set to 50% at week 4, with a 30% threshold for correct prediction at the final week. Step 2b yielded 13 correct predictions using the 3-metric combination approach, with the pain responder threshold set to 30% at week 4 and at the final week. Detailed prediction results by responder group for Step 2 are shown in Supplementary Table S2.

After Steps 1 and 2, there were 298 patients (31.7%) remaining who were not uniquely assigned to any responder group. Step 3 correctly predicted 204 patients (21.7% of the total of 939 patients) using the 50% threshold both for responder status at week 4 and at the final week, but did not correctly predict the remaining 94 patients (10.0% of the total of 939 patients). There was agreement between the FD analysis and the kNN analysis for most of the predictions in Step 3 (261 out of 298 or 87.6%). For the 37 patients where there was disagreement, the best correct prediction was provided by kNN for the patients who were non-responders at week 4, while the best correct prediction was provided by FD for the patients who were responders at week 4. Step 3 results by responder group are shown in Supplementary Table S3. We achieved the best performance (90.0% correct prediction) when we used kNN for patients who were non-responders at week 4 and FD for patients who were responders at week 4. However, the differences between FD and kNN analyses were relatively small for other scenarios. For example, using the same method for both responders and non-responders, the overall percentages of correct predictions were 89.2% when that method was FD and 89.8% when the method was kNN. With converse application of the two methods for the handling of disagreements (i.e., FD for patients who were non-responders at week 4 and kNN for patients who were responders at week 4), the overall correct predictions were 89.0%.

Overall, our approach was able to correctly predict 845 patients (90.0% of the total of 939 patients). Most of the 94 incorrectly predicted patients belonged to the responder groups associated with patients who changed their pain responder status between week 4 and the final week: 63 patients were non-responders at week 4 but became responders at the final week, and 20 were responders at week 4 but became non-responders at the final week. Figure 1 illustrates the correct predictions at each step, and the figure legend lists the specific actions associated with each step.

Discussion

Our finding that we could correctly predict 90% of the 12- to 13-week responder outcomes in patients by using only 4 weeks of pain and pain-related sleep interference data supports the predictive value of initial responses to pregabalin treatment—especially when the trajectory-related data elements are utilized (e.g., weekly monotonicity and weekly path length for pain scores). By using unique combinations of these data elements, we could achieve a specific signature for over half (55.4%) of the patients. In essence, these patients resembled each other in terms of subgroups belonging to the same responder group. This “three-dimensional” view of an individual patient’s trajectory characteristics provided an appropriate amount of similarity to differentiate groups without requiring more variables that could potentially lead to an excess of small patient groups. No other variables were needed for these patients, which further supports the predictive importance of trajectory information. When we relaxed the responder threshold to 30% in Steps 2a–b (which is still considered a meaningful clinical change), we could correctly predict over two-thirds (68.3%) of the pregabalin treatment outcomes in patients with pDPN without adding any other variables. These results also reinforce the importance of a stepwise approach in which simpler techniques are used whenever possible before introducing more complex multilevel modeling techniques.

For the remaining 31.7% (298) patients whose response we could not predict with the above approaches, we found that FD-based analyses with daily data, specifically amplitudes of harmonic components, contained relevant information that could be utilized effectively; and we used only one basic element of the many FD measures that could have been used. Our results suggest the importance of exploring the use of FD approaches for trajectory analyses, since characterization of these frequency-related features have not been utilized as commonly in non-cardiac medical prediction as they have in other application areas.

The use of kNN machine learning is gaining more widespread use—again supporting the growing perceived value of patient groups derived from how similar they are to one another. Our “nearest neighbors” again reflected trajectory-derived data elements of weekly pain and PRSI rather than other patient variables, further highlighting the predictive gains that become possible when trajectory-focused data elements are considered and analyzed.

By employing the FD analyses separately from the kNN analyses in Step 3, we were able to utilize two different techniques to identify a patient’s responder group. The agreement of these two approaches about the responder group provided reinforcing information that could then be utilized for correct prediction of another 181 (19.3%) patients in Step 3. However, there is further room for improvement with each technique, if correctly predicting > 90% of the patients is a goal. The finding that neither method was notably more predictive than the other in non-responders versus responders also suggests that both methods demonstrate a persuasive appeal for greater use in prediction. The FD analyses highlight what may be possible with daily pain data and the kNN analyses underscore what is possible when weekly PRSI measures are added.

The results also motivate us to consider other research and clinical implications. For example, for treatment of pDPN, pregabalin is recommended to be titrated from a lower dose of 150 mg/day (in three divided doses) to 300 mg/day after 1 week [27]. Some physicians may consider a lack of pain response during this titration period to be a reason to discontinue treatment. However, these results provide potentially useful trajectory-based data on patients who were non-responders at week 4 but became responders at end of treatment. Indeed, in a prior study evaluating pooled data for weekly response patterns in pregabalin for neuropathic pain, most of the subjects who became 30% or 50% responders at end of treatment achieved their first responder status by weeks 3 or 4, while a small percentage still showed their first response during weeks 5 and 6 [39]. An improved understanding of these patient profiles could better inform treatment decisions. In addition, since smartphones and wearable mobile technologies provide the potential to easily collect daily data, future studies could examine how daily and weekly pain and PRSI scores recorded during the first month of a pregabalin prescription (e.g., through a smartphone app that could be developed) could be more efficiently utilized as trajectory information to optimize clinical study designs as well as clinical care of patients with pDPN. Clearly, more research is needed; however, the advantages observed in these simple analyses (vs. complex, multilevel, or growth mixture modeling approaches) are evident. Others have noted the usefulness of daily diaries [12, 40–43], and the FD analyses also showed the value of daily diary data during the first month of treatment.

Finally, these results reinforce the importance of responses during the first 4 weeks of treatment. Prior work showed that most of the treatment responses occurred during the first 3–4 weeks of treatment [39]. Earlier work has also shown the importance of appropriate dose titration during the first 4 weeks [6].

Limitations

One limitation is that we only used data from 939 patients from six RCTs designed to study the effects of one medication, pregabalin, in one patient type, patients with pDPN. The robustness of the approach will need further evaluation, since the extent to which the success was affected by these specific trial characteristics is unknown. Also, the circumstances of the individual RCTs might have affected the quality of the data and their utility in the approach. For example, our model included both patients treated with flexible dosing (29.4% of the total) and those who had fixed dosing (70.6% of the total), and the impact of these different titration methods on outcomes would need further investigation. However, we consider these variabilities in dosing to be more reflective of real-world practice. Moreover, the pooling of these trials allowed us to create a large dataset for a robust analysis. Next, we further analyzed the 94 patients (10%) whose responses we could not correctly predict and found that 70 of 94 patients (75%) were from fixed-dose arms in the clinical trials. This finding warrants further investigation to understand why trajectory-focused data elements might produce better chances of correct prediction with flexible dosing.

Conclusions

By correctly predicting 12- to 13-week responder outcomes with 90% accuracy based only on data from the first month of treatment, we demonstrated the predictive value of patient profiles enhanced with trajectory-focused data elements in patients with pDPN being treated with pregabalin. These patients could be grouped based on these trajectory-based data elements, and the unique combinations of the scaler measures were highly predictive for two-thirds of the patients. For patients whose responses could not be correctly predicted with the scaler measures, analyses based on the FD and kNN demonstrated the potential value of these approaches to describe such patients. Further research on other pain treatments in pDPN and other chronic pain syndromes can expand upon these findings.

Below is the link to the electronic supplementary material.

Supplementary material 1 (DOCX 1649 kb)