The document introduces GSK's approach to implementing a risk-based monitoring (RBM) strategy using a new RBM tool. The tool analyzes data from multiple sources to generate risk indicators and overall risk scores for clinical trial sites. It then produces monitoring activity plans to guide monitors to focus on high-risk sites and activities. The tool aims to make monitoring more data-driven and risk-focused compared to traditional schedule-based approaches. A demo of the tool shows how it can detect changes in sites' risk scores over time and identify sites for further central review and discussion. Some initial challenges in implementation were confusion around the tool's purpose and indicators. Feedback indicated the tool helps prioritize monitoring efforts and drives more data-driven conversations
Based off of project findings, this presentation highlights the process of identifying KRIs for site quality for digestive disease studies and demonstrates the practical application of surrogate KRIs in risk-based monitoring.
Based off of project findings, this presentation highlights the process of identifying KRIs for site quality for digestive disease studies and demonstrates the practical application of surrogate KRIs in risk-based monitoring.
Gone are the days of using spreadsheets to manage clinical trials. Fortunately, a clinical trial management system (CTMS) such as Oracle Siebel CTMS, offers an effective method for streamlining business processes, reducing cost and saving time.
Whether you are a sponsor running global trials or a research organization conducting hundreds of studies, Perficient’s Param Singh, Director of Clinical Trial Management Solutions, will teach you:
What a CTMS is and who needs one
Key functions of a CTMS
CTMS selection process
System types and implementation options
Best practices
How BrackenData Leverages Data on Over 250,000 Clinical TrialsBracken
Learn about our why we've created our clinical trial intelligence solutions, how they provide big value to teams in the life sciences industry, and how you can start leveraging data immediately.
Leverage Big Data Analytics to Enhance Clinical Trials from Planning to Execu...Saama
Nikhil Gopinath, Senior Solutions Engineer for the Life Sciences at Saama, spoke at EyeforPharma's Clinical Trial Innovation Summit event in February 2017. These slides are from his "Leverage Big Data Analytics to Enhance Clinical Trials from Planning to Execution" presentation.
Who needs fast data? - Journal for Clinical Studies KCR
How “no news” during the life of a trial is bad news, and what data management (among other things) can do to help when ensuring access to fast data? Get to know this and more about smart e-solutions in the newest article of Kaia Koppel, Associate Director, Biometrics & Clinical Trial Data Execution Systems at KCR, in the recent issue of Journal for Clinical Studies (p.40-21).
Technology Considerations to Enable the Risk-Based Monitoring Methodologywww.datatrak.com
TransCelerate BioPharma Inc developed a methodology based on the notion that shifting monitoring processes from an excessive concentration on source data verification to comprehensive risk-driven monitoring will increase efficiencies and enhance patient
safety and data integrity while maintaining adherence to good clinical practice regulations. This philosophical shift in monitoring processes employs the addition of centralized and off-site mechanisms to monitor important trial parameters holistically, and it uses adaptive on-site monitoring to further support site processes, subject safety, and data quality. The main tenet is to use available data to monitor, assess, and mitigate the overall risk associated with clinical trials. Having the right technology is critical to collect and aggregate data, provide analytical capabilities, and track issues to demonstrate that a thorough quality management framework is in place. This paper lays out the high-level considerations when designing and building an integrated technology solution that will aid in scaling the methodology across an organization’s portfolio.
Tips and Tricks on how to go about certifying yourself quickly for the Quality Payment Program in 2018. How does it impact workflow, security and means to accelerate certification.
Tools to Drive Enrollment OCT Arena-Boston-2015Dan Diaz
The 4th Annual Clinical Operations in Oncology Trials East Coast was an amazing hit. Over 25 speakers challenged the 200 attendees on how- "WE" as an industry can use new tools and strategies to better our Clinical Trial Execution and Patient Enrollment.
With only 3% of the patients in the USA participating in Cancer Trials- we have to do a better job finding ways to educate them about the benefits of clinical studies.
The following tools are some of the new enhancements for better site and physician selection which can help find better results.
Leveraging Siebel CTMS for Risk-Based MonitoringPerficient, Inc.
In a risk-based monitoring (RBM) strategy, rather than treating all clinical sites and source data equally, monitoring resources are focused on the sites that need the most help, and the data that is most critical to the study or most likely to have issues.
Because RBM is so effective at saving time, reducing costs, and improving quality, sponsors and contract research organizations are working to make the switch. While doing so may not be easy, companies with Oracle’s Siebel Clinical Trial Management System (CTMS) will have a leg up on the competition.
Learn how you can configure and leverage Siebel CTMS to support an RBM strategy.
Risk based monitoring presentation into what Risk Based Monitoring (RBM) is all about. The value of getting it right, and the risks of getting it wrong. We look at the Triumph Research Intelligence (TRI) approach to RBM, and the TRI solution to RBM. An insight into the Future of Visual OPRA is given.
Gone are the days of using spreadsheets to manage clinical trials. Fortunately, a clinical trial management system (CTMS) such as Oracle Siebel CTMS, offers an effective method for streamlining business processes, reducing cost and saving time.
Whether you are a sponsor running global trials or a research organization conducting hundreds of studies, Perficient’s Param Singh, Director of Clinical Trial Management Solutions, will teach you:
What a CTMS is and who needs one
Key functions of a CTMS
CTMS selection process
System types and implementation options
Best practices
How BrackenData Leverages Data on Over 250,000 Clinical TrialsBracken
Learn about our why we've created our clinical trial intelligence solutions, how they provide big value to teams in the life sciences industry, and how you can start leveraging data immediately.
Leverage Big Data Analytics to Enhance Clinical Trials from Planning to Execu...Saama
Nikhil Gopinath, Senior Solutions Engineer for the Life Sciences at Saama, spoke at EyeforPharma's Clinical Trial Innovation Summit event in February 2017. These slides are from his "Leverage Big Data Analytics to Enhance Clinical Trials from Planning to Execution" presentation.
Who needs fast data? - Journal for Clinical Studies KCR
How “no news” during the life of a trial is bad news, and what data management (among other things) can do to help when ensuring access to fast data? Get to know this and more about smart e-solutions in the newest article of Kaia Koppel, Associate Director, Biometrics & Clinical Trial Data Execution Systems at KCR, in the recent issue of Journal for Clinical Studies (p.40-21).
Technology Considerations to Enable the Risk-Based Monitoring Methodologywww.datatrak.com
TransCelerate BioPharma Inc developed a methodology based on the notion that shifting monitoring processes from an excessive concentration on source data verification to comprehensive risk-driven monitoring will increase efficiencies and enhance patient
safety and data integrity while maintaining adherence to good clinical practice regulations. This philosophical shift in monitoring processes employs the addition of centralized and off-site mechanisms to monitor important trial parameters holistically, and it uses adaptive on-site monitoring to further support site processes, subject safety, and data quality. The main tenet is to use available data to monitor, assess, and mitigate the overall risk associated with clinical trials. Having the right technology is critical to collect and aggregate data, provide analytical capabilities, and track issues to demonstrate that a thorough quality management framework is in place. This paper lays out the high-level considerations when designing and building an integrated technology solution that will aid in scaling the methodology across an organization’s portfolio.
Tips and Tricks on how to go about certifying yourself quickly for the Quality Payment Program in 2018. How does it impact workflow, security and means to accelerate certification.
Tools to Drive Enrollment OCT Arena-Boston-2015Dan Diaz
The 4th Annual Clinical Operations in Oncology Trials East Coast was an amazing hit. Over 25 speakers challenged the 200 attendees on how- "WE" as an industry can use new tools and strategies to better our Clinical Trial Execution and Patient Enrollment.
With only 3% of the patients in the USA participating in Cancer Trials- we have to do a better job finding ways to educate them about the benefits of clinical studies.
The following tools are some of the new enhancements for better site and physician selection which can help find better results.
Leveraging Siebel CTMS for Risk-Based MonitoringPerficient, Inc.
In a risk-based monitoring (RBM) strategy, rather than treating all clinical sites and source data equally, monitoring resources are focused on the sites that need the most help, and the data that is most critical to the study or most likely to have issues.
Because RBM is so effective at saving time, reducing costs, and improving quality, sponsors and contract research organizations are working to make the switch. While doing so may not be easy, companies with Oracle’s Siebel Clinical Trial Management System (CTMS) will have a leg up on the competition.
Learn how you can configure and leverage Siebel CTMS to support an RBM strategy.
Risk based monitoring presentation into what Risk Based Monitoring (RBM) is all about. The value of getting it right, and the risks of getting it wrong. We look at the Triumph Research Intelligence (TRI) approach to RBM, and the TRI solution to RBM. An insight into the Future of Visual OPRA is given.
How To Optimize Your EDC Solution For Risk Based Monitoringwww.datatrak.com
This presentation presents best training practices to leverage EDC technology and risk-based monitoring to effectively and efficiently monitor clinical research.
Our focus is on the practical process of preparing your team to optimize the tools made available through an EDC solution.
This presentation is applicable to CRA’s, clinical project managers, clinical data managers, regulatory compliance professionals, and those involved in the design and implementation of risked-based monitoring plans.
TRI, the risk-based monitoring company holds a number of industry "firsts". TRI is the first company entirely dedicated to RBM and quality oversight. They are the creators of the world's first purpose-built RBM platform, OPRA, and the first company to offer a true, holistic RBM solution- offering not only the technology but also the knowledge and services required for any organization wishing to successfully implement and adopt a risk-based approach in their clinical trials. TRI - Where's the Risk?
Slides from a webinar presented by Steve Schlarman (RSA) and Kirk Hogan (Iceberg). An overview of a large financial institution's journey to improve their application risk management process, from spreadsheets to a centralized inventory of risk data, allowing for more confident, informed and effective decisions.
Presentation delivered by Lori A. Tierney, BSN, Director, Site Management Operations, Allergan, Inc. at the marcus evans Evolution Summit Fall 2019 in San Diego CA.
SPPM Clinical 7 Best Practices In Forecasting & Planningguest1fe658d
Strategic Project Portfolio Management for Clinical Trials
Ø Plan clinical trial expenditure using a top-down approach based on empirical or historical data
Ø Adjust the plan bottom-up after assessing individual site and region enrolment plan
Ø Update the plan using actual study performance data
Ø Manage accruals and payments
Risk Based Monitoring in Clinical Trials.ClinosolIndia
Risk-based monitoring (RBM) is a monitoring strategy in clinical trials that aims to improve the quality and efficiency of data collection while reducing costs and burden on study participants. Rather than conducting monitoring activities at fixed intervals, RBM utilizes a risk assessment approach to identify areas of the study that are at higher risk of errors or deviations from the protocol and focuses monitoring efforts on those areas.
The RBM process begins with a risk assessment, which involves identifying potential risks to the study's data integrity, participant safety, and study conduct. This may include risks related to patient enrollment, data collection, adverse event reporting, or protocol compliance. Based on the risk assessment, the study team creates a risk management plan that outlines the monitoring strategy to be employed throughout the trial.
In RBM, monitoring activities are targeted to focus on the areas of the study that present the highest risk. For example, if a study has a high risk of data entry errors, the monitoring plan may include a more intensive review of data entry activities or require that data be entered in real-time, so errors can be identified and corrected more quickly.
RBM can be facilitated through several tools, such as centralized monitoring, key risk indicator (KRI) dashboards, or data analytics. Centralized monitoring allows for remote review of study data by a team of experts who can identify trends and issues more efficiently. KRIs are pre-defined metrics used to track performance and detect areas of concern, allowing for proactive management of risks. Data analytics can identify unusual patterns or outliers in the data, enabling the study team to focus on those areas of concern.
RBM is a dynamic process that involves ongoing evaluation of the study's risk profile and adjusting the monitoring strategy accordingly. By focusing monitoring efforts on the areas of the study that pose the highest risk, RBM can improve data quality and participant safety, while reducing monitoring costs and burden.
A Murphological View on Software Measurement: a serious joke or a funny seri...Luigi Buglione
The 30-year experience from the Software Measurement field explains that a strong resistance usually comes from project team members, supposing the real objective is a personal evaluation on their performance and not a neutral measurement for a concrete process improvement. Concurrently, from the middle ‘80s a series of SPI models - such as the Software Capability Maturity Model (Sw-CMM) and nowadays its evolution, the CMMI –provided a guide for realizing a real improvement, where measurement played an important role, before as a Common Feature, then as a separate process (MA – Measurement and Analysis) at Level 2. But a certain resistance still remain alive also after these years.
Recently, in the Management field (and also in ICT) more than “serious” books and reference guides it seems that (apparent) semi-serious publications such as the Dilbert strips by Scott Adams are referenced in technical presentations and papers as a starting point for commenting daily ICT malpractices. If so, another good source for “joking” with such serious things are some of the most know laws, the “Murphy’s laws”, originally written by Arthur Block and after created/modified by plenty of people worldwide and published over the Internet in a sort of “GNU licence for humour”.
This paper tries to propose a “murphological view” on Software Measurement issues, commenting some related measurement-related laws and providing links with main SPI practices at the aim to reduce the percentage of failures in application of Software Measurement programs, as noted by H.Rubin some years ago.
Overview of Risk Based Monitoring in Clinical Trial ProcessesEditorIJTSRD1
Risk based monitoring RBM has emerged as a transformative approach in clinical trial processes. This paper provides an overview of RBM and its impact on the field of clinical research. By moving away from traditional on site monitoring and adopting a targeted and efficient approach, RBM has demonstrated numerous benefits in terms of cost effectiveness, data quality, and patient safety. This abstract summarizes the key findings discussed in the conclusion. The proactive identification and management of risks throughout the trial lifecycle have led to improved decision making, increased study participant compliance, and enhanced overall trial success rates. With advancing technology, RBM approaches are expected to evolve further, allowing for greater optimization and streamlining of clinical trial processes. The abstract concludes by emphasizing the potential of risk based monitoring to shape the future of clinical research and contribute to the development of safe and effective therapies for patients worldwide. Kelam Himasri | Sankara Narayanan. K "Overview of Risk-Based Monitoring in Clinical Trial Processes" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-7 | Issue-3 , June 2023, URL: https://www.ijtsrd.com.com/papers/ijtsrd58586.pdf Paper URL: https://www.ijtsrd.com.com/pharmacy/pharmacy-practice/58586/overview-of-riskbased-monitoring-in-clinical-trial-processes/kelam-himasri
Role of Clinical Data Management in Risk-Based MonitoringClinosolIndia
Clinical Data Management (CDM) plays a significant role in the implementation of Risk-Based Monitoring (RBM) within clinical trials. RBM is an approach that focuses monitoring efforts on areas of highest risk, thereby optimizing resource allocation, enhancing data quality, and ensuring patient safety. Here's how CDM contributes to RBM
Similar to ACDM - "Data Driven" Monitoring of Clinical Trials - Neill Barron (20)
06-04-2024 - NYC Tech Week - Discussion on Vector Databases, Unstructured Data and AI
Round table discussion of vector databases, unstructured data, ai, big data, real-time, robots and Milvus.
A lively discussion with NJ Gen AI Meetup Lead, Prasad and Procure.FYI's Co-Found
Techniques to optimize the pagerank algorithm usually fall in two categories. One is to try reducing the work per iteration, and the other is to try reducing the number of iterations. These goals are often at odds with one another. Skipping computation on vertices which have already converged has the potential to save iteration time. Skipping in-identical vertices, with the same in-links, helps reduce duplicate computations and thus could help reduce iteration time. Road networks often have chains which can be short-circuited before pagerank computation to improve performance. Final ranks of chain nodes can be easily calculated. This could reduce both the iteration time, and the number of iterations. If a graph has no dangling nodes, pagerank of each strongly connected component can be computed in topological order. This could help reduce the iteration time, no. of iterations, and also enable multi-iteration concurrency in pagerank computation. The combination of all of the above methods is the STICD algorithm. [sticd] For dynamic graphs, unchanged components whose ranks are unaffected can be skipped altogether.
Adjusting OpenMP PageRank : SHORT REPORT / NOTESSubhajit Sahu
For massive graphs that fit in RAM, but not in GPU memory, it is possible to take
advantage of a shared memory system with multiple CPUs, each with multiple cores, to
accelerate pagerank computation. If the NUMA architecture of the system is properly taken
into account with good vertex partitioning, the speedup can be significant. To take steps in
this direction, experiments are conducted to implement pagerank in OpenMP using two
different approaches, uniform and hybrid. The uniform approach runs all primitives required
for pagerank in OpenMP mode (with multiple threads). On the other hand, the hybrid
approach runs certain primitives in sequential mode (i.e., sumAt, multiply).
The Building Blocks of QuestDB, a Time Series Databasejavier ramirez
Talk Delivered at Valencia Codes Meetup 2024-06.
Traditionally, databases have treated timestamps just as another data type. However, when performing real-time analytics, timestamps should be first class citizens and we need rich time semantics to get the most out of our data. We also need to deal with ever growing datasets while keeping performant, which is as fun as it sounds.
It is no wonder time-series databases are now more popular than ever before. Join me in this session to learn about the internal architecture and building blocks of QuestDB, an open source time-series database designed for speed. We will also review a history of some of the changes we have gone over the past two years to deal with late and unordered data, non-blocking writes, read-replicas, or faster batch ingestion.
Quantitative Data AnalysisReliability Analysis (Cronbach Alpha) Common Method...2023240532
Quantitative data Analysis
Overview
Reliability Analysis (Cronbach Alpha)
Common Method Bias (Harman Single Factor Test)
Frequency Analysis (Demographic)
Descriptive Analysis
06-04-2024 - NYC Tech Week - Discussion on Vector Databases, Unstructured Data and AI
Discussion on Vector Databases, Unstructured Data and AI
https://www.meetup.com/unstructured-data-meetup-new-york/
This meetup is for people working in unstructured data. Speakers will come present about related topics such as vector databases, LLMs, and managing data at scale. The intended audience of this group includes roles like machine learning engineers, data scientists, data engineers, software engineers, and PMs.This meetup was formerly Milvus Meetup, and is sponsored by Zilliz maintainers of Milvus.
Levelwise PageRank with Loop-Based Dead End Handling Strategy : SHORT REPORT ...Subhajit Sahu
Abstract — Levelwise PageRank is an alternative method of PageRank computation which decomposes the input graph into a directed acyclic block-graph of strongly connected components, and processes them in topological order, one level at a time. This enables calculation for ranks in a distributed fashion without per-iteration communication, unlike the standard method where all vertices are processed in each iteration. It however comes with a precondition of the absence of dead ends in the input graph. Here, the native non-distributed performance of Levelwise PageRank was compared against Monolithic PageRank on a CPU as well as a GPU. To ensure a fair comparison, Monolithic PageRank was also performed on a graph where vertices were split by components. Results indicate that Levelwise PageRank is about as fast as Monolithic PageRank on the CPU, but quite a bit slower on the GPU. Slowdown on the GPU is likely caused by a large submission of small workloads, and expected to be non-issue when the computation is performed on massive graphs.
2. Objectives
• Introduce GSKs approach to implementing
an RBM strategy
• Overview/Demo of the RBM tool &
Processes to support this strategy
• Use of Tool on real data – Mini-Pilots
• Benefits & Challenges
2
3. Traditional Monitoring Methods vs. RBM “Data-Driven”
Model
TraditionalTraditional
• Monitoring visit based on predetermined
schedule, independent of workload
• All sites and events treated equally
• On-site CRA visits not predominantly
concentrated on high value activities
• Solely driven by CRAs with little involvement
from the DQL or central team
Risk Based MonitoringRisk Based Monitoring
• A “Data-Driven” approach
• Visits driven by:
– Quality
– Safety signals
– Workload
• CRA productivity focused on key areas
– Subject safety
– Data integrity
– Regulatory compliance
• New tools allow greater involvement of
central team in decision making
4. RBM Tool Concept – A “Data-Driven” approach to
monitoring
• Data from various source systems (Inform, Etrack, Ramos,
External data) are consolidated into a single data source
feeding the RBM tool
• 11 “Core” RBM Risk Indicators are created in the RBM tool
by analysing this data
• The overall risk profile of sites (“Overall Risk Score”) is
derived from the cumulative effect of risk from each of the
core risk indicators, and any study specific risk indicators
defined
• Consolidated site level reports (“Monitoring Activity
Plans”) are generated from the RBM tool and used by
monitor to guide monitoring intervention (what) and
monitoring frequency (when)
• Using “Oversight Visuals” in the RBM tool, study team
review “Overall Risk Score” by site to detect outlier sites
(not all sites) e.g. Highest Risk sites, that drive targeted
conversations with CSM/CRA
• CSMs will also access “Oversight Visuals” so they can get
helicopter view of their local sites.
The RBM tool enables a single consolidated “helicopter” view of risk across sites, with the
ability to drill into the detail behind any or all of the risk signals, in order to drive focussed
and targeted monitoring intervention, where and when needed
eDC CTMS
External
Data
Consolidated
RBM Database
Core RBM
Indicators x 11
Study Specific
Indicators (2-
4)
Monitoring
Activity Plan
Oversight
“Helicopter
view” Visuals
CRA Action
Central
Oversight
Study
Specific
Data
8. DM Refreshes RBM Tool
Reports
CRA pulls site-specific
Monitoring Activity Plan
CRA reviews MAP (in
conjunction with other
site information)
CRA carries out corrective
actions
DM reviews RBM
‘Oversight’ visuals
“outlier” sites
DM discusses “outliers”
with Central Team,
Country Study Managers
CRA determines
corrective actions
If required, DM or Country
Study Mgr discusses
potential root-causes and
remediation with CRA
RBM Process Overview
CRA documents all site
contacts
Central Team discuss
potential root-causes and
implement remediation
Data Changes
feed back to
RBM Tool
Study
level
issues
Site
level
issues
CRA = Clinical Research Associate (monitor)
DM = Data Manager
Study Team = DMs, Study Lead, Stats
DM creates the Monitoring
activity plan
9. Sample Site 1 - High Value site exhibiting High Risk
9
00 Month 0000Presentation title in
footer
Monitoring Activity
Plan
Adobe Acrobat
Document
10. Sample Site 2 - Site exhibiting improvement after
targeted RBM tool driven action
10
00 Month 0000Presentation title in
footer
Site exhibiting
Overall Risk Score
Reduction between 11th
Nov and 18th
Dec.
Adobe Acrobat
Document
Adobe Acrobat
Document
11. Sample Site 3 - Site exhibiting increase in Overall Risk Score
11
00 Month 0000Presentation title in
footer
Site exhibiting
Increase in
Overall Risk Score
Between October
and December
12. Sample Site 4 – Low Risk Site with High Frequency MVs
12
00 Month 0000Presentation title in
footer
13. Sample Site 5 – Higher Risk Site with Low Frequency MVs
13
00 Month 0000Presentation title in
footer
14. Challenges to Implementation
• CSMs/CRAs getting “defensive” re
risks identified and focus was on
actions to turn risk signals from
“Red” to “Green”
• Some confusion between general
risk indicators/instream data review
and RBM indicators
• Lack of clarity that RBM tool is not
a data-management tool to
manage daily operational DM tasks
14
February 2014RBM Mini-Pilots
Observations
• Training on each risk indicator, its
meaning and how mitigating actions
may or may not affect risk signal
• Clear guidance for EST on identifying
study specific indicators for RBM –
what does an RBM indicator look like?
• Clear messaging that the RBM tool is
an additional tool to drive monitoring
intervention - not a general DM/data
quality tool. Understanding where
RBM tool fits with other tools is key
and clear role definition – avoid
duplication of effort
Some impacts on Capability development
15. Feedback from end users on benefits
15
00 Month 0000Presentation title in
footer
“it is fascinating that the shift
that we have seen for some
of the sites in their overall risk
score now that the study
specifics are in there…risk
scoreds align and somewhat
quantify/verify the risks that
we were ‘feeling’”
“Encourages real
depth of discussion
about what types of
data are important
and value added for
the study”
“Provides the
capability to
customize and target
LOC or site/CRA
specific training,
actions to address
risks that are
identified in RBM.”
“Allows high level
oversight of relative
performance of sites
– this relativity is not
available by other
means to either
central study teams,
or LOCs or CRAs
“Provides real data
to discuss – versus
“feelings” about
potential problem
sites”
• New issues detected
earlier – e.g. Rounding at
sites, IP Compliance,
Frequent Rater Changes
• Provides “Real” data to
drive conversations between
Study Team and LOCs
around problem sites and
monitoring strategy
• Allows LOCs and CRAs to
develop and implement
targeted action for areas of
highest risk
• Provides a “one-stop shop”
complete data driven view of
risk across sites,
consolidating various data
sources
This was what was referred to as the “Jupiter” site. It was a high enroller displaying highest risk driven by a number of red signals across a number of indicators.
The site exhibited late data entry, high AE rates, issues with IP compliance and well as red signal for disease progression. As a high enrolling site, this site stood out as the one to tackle first
Team had suspicions about this site but couldnt quite put their finger on it. The risk signal drove conversations with the CRA/CSM on the root causes and it drove an onsite visit
On 11th November this site was identified as highest risk site – 11th November, site exhibited highest Overall Risk Score
H3M contacted CRA to discuss details of MAP –
Risk Profile of this site was validated
It was agreed that a site visit was needed to address risks identified
On site visit occurred – actions taken to address and mitigate risks.
As a result of these actions, some risk signals were eliminated e.g. Safety Signals since last MV, Subject visits Since Last MV, MVR Site staff issues detected.
A key learning is that not all Risk Signals can be eliminated even though action has been taken e.g. where data does not change. Example AE rates, Rater Changes, etc
Therefore, some risk signals remain even though mitigating actions have been taken … i.e. the risk still exists even though risk has been mitigated. Important to keep an eye on these risks and deteriorating trends of overall risk scores
Important to note that we did not have the tool running for long enough to track any ongoing trends
But we did readily identify sites that jumped up in risk score that speaks to the value of Study Specific Indicators
Before study specific indicators were added to the tool, this site exhibited a low risk score. Study specific RBM indicators were then added
This site exhibited a high number of patients with worsening EDSS and poor baseline EDSS that increased risk of early withdrawal
Also there were a high number of relapses at this site that increase risk of early withdrawal also
These risk signals coupled with risk signals on IP Compliance made this a high risk site
DEMONSTRATES importance of the right study specific indicators
Commentary/Notes
Low Risk Site exhibiting a high MV frequency
Validated that low risk at this site was accurate
H3M team contacted monitor to discuss
Site has been remotely monitored since then with average MV frequency decreasing for this site (from 1.1 MVs per month to 0.85 MVs per month)
Commentary/Notes
Identifying this outlier in October identified need for a MV
After MV, site’s risk score improved as outstanding items were addressed on site