Ben Vaughn, Principal Statistical Scientist, has participated in over 25 marketing applications and is an expert on CDISC implementation and standards. His work has included coproducing the ISS/ISE for multiple analgesic products; and statistical consultation, display generation and submission work for several chronic and acute pain products. In the past three years, he has supported five opioid sponsors at DAAAP advisory committee meetings, both back room and bullpen.
Pain trials are unique among clinical trials, and it is important to select a clinical research partner that understands and embraces the many differences. There are several key factors to consider when choosing a CRO to work with on your next pain trial.
1. Enrollment
In any pain study, enrollment may present a challenge. For example, in acute pain model studies, sites tend to enroll quickly and sponsors can find themselves in an over-enrollment situation. Some overage can be helpful to account for subjects withdrawing early from the study, but too much overage can significantly impact exceed the trial’s budget. Sponsors must work with the CRO to set a reasonable cap on the overall number of subjects enrolled to minimize overages while allowing sites to continue to enroll without undue restrictions. For example, for a phase III bunionectomy study, we were able to complete enrollment seven weeks early while managing the enrollment cap by using experienced CRAs and maintaining strong relationships with high performing sites.
Chronic pain studies present the opposite challenge. Enrollment is usually much slower than what sponsors hope for, as chronic pain studies can be a tough sell for subjects. Why enter a trial if your current medication is already working and risk receiving a placebo, a rescue medication offering little analgesic control, or an experimental new drug which may or may not work? Naturally, this presents challenges when meeting predetermined time
lines. During a recent osteoarthritis study, we were able to complete enrollment early by expanding advertising programs across all sites, closing underperforming sites while increasing enrollment caps at high enrolling sites, and continuing to run advertisements throughout the entire enrollment period.
In both situations, transparency with your CRO is key. Understanding a realistic budget and timeline will help keep your trial running smoothly. Your CRO should be able to provide data to support budget and timeline projections. At times, sponsors may be reluctant to approve advertising expenses upfront. For one particular sponsor, we were able to provide them with a comparison of the advertising costs versus the cost of extending the timeline if enrollment targets weren’t met. This comparison encouraged them to move forward with early advertising, and, as a result, their enrollment target was met.
During site identification for another study, it became apparent to us that some of the sites provided by the sponsor were likely to enroll few, if any, patients. We recommended dropping these sites in favor of higher enrolling sites or adding a couple of additional sites to make sure that enrollment rates met their expectations. The sponsor declined because the investigators at those sites were key opinion leaders (KOLs) and they didn’t want the additional expense of adding more sites. In the end, it took an additional 2 months to complete enrollment. Sometimes it is a choice between paying more upfront to reduce the risks of slow and costly enrollment period extensions.
Another obstacle we see is that some sponsors estimate site budgets too low rather than market value for site payments. While we do our best to negotiate the best site agreements we can on behalf of sponsors, unreasonable budget expectations can lead to a study not being able to initiate enough (or the right) sites. The costs in timeline extensions often exceed the costs of offering market-based site payments upfront. Your CRO should be able to provide you with market-based estimates for site payments based on your study design and their experience in similar studies.
2. Subject Reported Data
Pain is not usually a visible condition. A health care professional cannot look at a subject and objectively determine how much pain that person is in. The only way to gather data during pain trials is to ask the subjects to report the information themselves. Any time subjects must provide their own data from a trial, site staff must be educated to work with subjects to better standardize subjective data collection. Similarly, subjects must receive training from site staff on how to report the information, whether electronically or on paper.
If an abnormal value entered by the subject is discovered in your data, the site cannot go back and request a clarification. For example, a subject reporting only to one extreme – all 10s say, or all 1s – is not considered clean data. In an acute pain trial, it would need to be determined how to best represent these outlier data. In a chronic trial, the study team and CRAs must revisit the site for retraining purposes.
3. Data Monitoring
Because there is generally a great volume of data collected in any pain trial, it is important that a CRO monitor these data regularly. This requires a keen eye and can be quite time consuming, particularly in acute pain trials because subjects may leave the clinic before data is available to the study team. However, frequent visits to a site can help catch errors and irregularities before they become a major concern. The study team should look for outliers in the data to identify sites that may need more frequent monitoring visits or additional training for site staff. It is also important to have an experienced CRA capable of monitoring the large amount of data while visiting sites.
To manage this, many sponsors require that CRAs for pain trials have a certain level of experience. As a result, sponsors should be mindful to ensure their selected CRO can meet these expectations for staffing purposes.
4. Drug Preparation
For many pain trials, the investigational product (IP) or rescue medication may be a controlled substance scheduled by the DEA. CROs must be familiar with both DEA and state licensing requirements and forms and must also have an understanding of how to ship, move, and monitor scheduled drugs.
5. Diversion & Misuse
Diversion and misuse of medications can be an issue in pain trials, particularly for chronic subjects. If IP counts appear incorrect, sponsors need to determine if it was a mistake or something more. The CRAs should work closely with sites to ensure IP accountability is performed on a very regular basis.
Because pain, is not necessarily a visible condition, site staff need to be diligent in recognizing suspicious behavior and detecting drug-seeking individuals. This is another area where a well-trained site can make all the difference. It is imperative to consider these points during the site selection process.
6. FDA Approval
A final point to consider when selecting your CRO is the experience of the team in supporting submissions for Food and Drug Administration (FDA) approval. DEA-scheduled drug trials not only need to demonstrate safety and efficacy, but must also address the human abuse liability/potential (HAL/HAP). Additionally, FDA’s Division of Anesthesia, Analgesia and Addiction Products (DAAAP) has been quick to enforce the recommendations of a 2010 FDA position paper on missing data, so sponsors must be extremely precise in their treatment of missing data or risk rejection.
Ultimately, there are many considerations a sponsor must make when selecting a CRO for a pain trial. Trained and experienced project staff are key in keeping trials moving forward with ease, detecting potential issues and monitoring vast quantities of data quickly. Any CRO seeking work on pain trials should also be prepared to demonstrate positive relationships with study sites, which can help ensure good subject recruitment and produce clean data.
Learn how our experts mitigated COVID-19 related risks for a complex pain program, while exceeding aggressive timelines and maintaining trial integrity.
This website uses cookies. By continuing to use the website, you are providing consent. For more information, View our Privacy Notice.
If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.
cookietest
session
This cookie is used to see if the browser is set to block or allow cookies.
hs_do_not_track
6 months
This cookie can be set to prevent the tracking code from sending any information to HubSpot.
Session_Id
session
This cookie is generated as part of the sign-in process and used to defend against Cross Site Request Forgery (CSRF)
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
__cf_bm
30 minutes
Cloudflare Detection of malicious actors
__hs_initial_opt_in
6 months
HubSpot Opt In
__hs_opt_out
6 months
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie
Duration
Description
hubspotutk
6 months
This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
i18n
session
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
jasession
session
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
JSESSIONID
session
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
searchSource
1 month
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
sp
1 year
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_FX4Z6BSDKJ
2 years
This cookie is installed by Google Analytics.
_ga_FX4Z6BSDKJ
1 year
WPEngine Analytics
_gclxxxx
90 days
This is a conversion tracking cookie used in connection with Google Analytics.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
_janalytics_id.b246
2 years
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
_janalytics_ses.b246
session
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
_jibe_sticky_params
session
These cookies are used in connection with iCIMS for Rho’s job opportunities portal
__hssc
1 day
This cookie keeps track of sessions. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
__hssrc
1 day
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
__hstc
6 months
The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
LastMRHSession
session
This cookie is used to check if the browser supports cookies.
MRHSession
session
This cookie is used to contain your language settings.
Targeting cookies are used to provide visitors with relevant ads and marketing campaigns. They record your visits to our Website, the pages you have visited, and the links you have followed.
Cookie
Duration
Description
fr
3 months
Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
MUID
1 year 24 days
Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.
sliguid
1 year
This cookie is used in connection with Salesloft for use in live website tracking to help identify and qualify leads.
slireg
7 days
This cookie is used in connection with Salesloft for use in live website tracking to help identify and qualify leads.
slirequested
1 year
This cookie is used in connection with Salesloft for use in live website tracking to help identify and qualify leads.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
visitorId
1 year
This cookie is used by ZoomInfo to identify visitors to the Website.
_fbp
3 months
This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_gat_gtag_UA_6056224_1
1 minute
Set by Google to distinguish users.
_gat_UA-6056224-1
1 minute
A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gcl_au
3 months
Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_uetsid
1 day
Bing Ads sets this cookie to engage with a user that has previously visited the website.
_uetvid
1 year 24 days
Bing Ads sets this cookie to engage with a user that has previously visited the website.