Skip to main content

Posts Tagged ‘CROs’

How To Fix Problems With Clinical Site And Investigator Payments

This is perhaps the biggest complaint we hear from both sponsors/contract research organizations (CROs) and sites/investigators. Sponsors and CROs dedicate countless resources to researching and addressing payment questions and concerns raised by site personnel, and site personnel often feel frustrated, undervalued, and distrustful of sponsors and CROs that do not pay them as promised. When […]

How To Fix Poor Clinical Document Compliance At Clinical Sites

Keeping sites in compliance with their required documents is an ongoing battle for every sponsor and contract research organization (CRO). Considering the volume of documentation involved in a clinical trial, it’s no wonder why sites struggle to stay on top of it, or why sponsors and CROs get frustrated when auditors issue findings against them […]

How To Fix Ineffective Subject Screening At Clinical Sites

Even when sites are able to recruit a large pool of potential subjects, sponsors and contract research organizations (CROs) see far too many subjects who fail to pass the screening visit (screen failures) and subjects who pass the screening visit only to leave the study early (early terminations). Because sites get paid for every subject […]

Applying The Concept Of Customer Experience (CX) To Life Sciences

My colleagues in Perficient Digital, Perficient’s in-house digital agency, recently published a fantastic guide about customer experience (CX). While the guide focuses primarily on retail customers, a lot of the advice it contains can be quite helpful for life sciences, so I thought I’d take a stab at translating it for you. Now, in full […]

Bug Tracking Systems Aren’t Just For Bugs

Here in Perficient’s life sciences practice, we use a defect tracking system as part of our application development process. It helps us keep track of bugs and resolutions as we develop and test, but there’s nothing particularly remarkable about it…except that we use it for another purpose too: to track problems with our QA controlled […]