Source data verification (SDV) is the single largest line item in most monitoring budgets — it commonly accounts for 25% of a trial budget. Targeted SDV and risk-based monitoring have narrowed what gets verified and brought that cost down, but the SDV that remains is still expensive, and most of it is still done by sending a monitor on site.

The opportunity is to do that remaining work remotely - with high efficiency. The catch: “remote SDV,” as it’s practiced in many trials today, often isn’t a workflow at all. It’s a set of workarounds that cut the number of on-site visits but create new friction and manual burden for sites and monitors — because they lean on email to exchange documents, shared drives to store them and ad hoc trackers to keep up with progress.

Direct access to EMR systems is another workaround, with its own set of limits. First, it isn’t available in every country. Second, it puts a heavy burden on monitors, who must review large volumes of the electronic record to pinpoint the material that actually requires verification. Third, it often prevents downloading the records needed to document what was verified.

Every one of these workarounds shares the same flaw: it fixes one piece of the problem and creates another.

Why remote SDV workarounds fall short

Manual document collection can’t prevent PHI exposure

Source documents shared by email, uploaded to a shared drive, or pulled from the EMR are all moving through an uncontrolled channel. Redaction in that setting is inconsistent by nature — there’s no controlled environment for it to happen in — and the risk of PHI or PII exposure is high.

Email and shared drives can’t manage SDV

Email and shared drives move documents and store them — but none of them manage the work. Without a workflow, the friction piles up: tediously trying to make sure nothing falls through the cracks, manually tracking what’s been received versus what’s still outstanding, knowing which version of which document is current and updating status at every step.

Something more fundamental is missing, too. There’s no integrated way to issue document-based queries, no centralized status reporting across sites and no infrastructure to translate non-English source documents. The monitor manages all of it outside any system.

Ad hoc trackers leave the study team blind

When each monitor keeps their own spreadsheet of what’s been requested, received, verified and queried, the coordination layer that should hold the process together simply isn’t there. There’s no central visibility for the study team and no governed audit trail. A study manager who wants the current state of SDV across the trial ends up reconciling several trackers by hand and still can’t get a clear view. An auditor has no clean trail to follow either — just emails, shared-drive folders and disconnected trackers to piece together after the fact. Ad hoc and global trackers aren’t a solution to centralized visibility — they’re evidence it was never built in.

‍

What an online remote SDV workflow does differently

The difference is structural. Source data verification has six moving parts — source-document collection, redaction, translation, data comparison, querying and status reporting. In a controlled workflow they happen inside one end-to-end process, instead of being scattered across several uncontrolled ones.

In a workaround, the monitor is the workflow — the six parts live in separate places (inboxes, shared drives, spreadsheets) and the monitor is the only thing connecting them. A real workflow connects the steps itself. Each step hands off to the next inside a single, controlled process: the redacted document is ready for comparison, the discrepancy is ready to query, the status updates itself. Nothing gets re-located, re-attached or stitched together by hand — and nothing falls through the seams.

Collecting online source documents up-front prevents backlogs

An online remote SDV workflow starts at data entry. As the site enters data into the EDC, the integration prompts an upload of source documents for required fields right then — while they’re still on hand. No going back to the patient chart weeks later when the monitor is ready for SDV.

Source document collection is where PHI exposure risk is highest. Source documents are full of PHI, and in a manual process the risk is that the document travels first and gets redacted later — emailed, saved to a drive, maybe cleaned up somewhere along the way. By then it’s already moved through uncontrolled channels, and one missed field is a real breach. A controlled workflow flips the order. Redaction happens before the document goes anywhere: the site redacts PHI/PII at upload, with AI-assisted redaction backing up the manual pass so nothing slips through. The document travels only after it’s properly anonymized — inside the same environment that holds it, under controlled access with a complete audit trail.

All of this is happening inside one governed workflow — so the documents a monitor needs are collected early and already redacted and translated if needed, ready for SDV to begin. That’s the shift. In a manual process, verification waits: the site enters data, the monitor requests documents, the site goes back to the chart to find them, they come back over email, and only then can SDV start — often months after the data was entered. Here, there is no wait time. Workflow steps are fully actioned in a single pass.  Documents are ready up front, so verification on critical fields starts in minutes, not months — and data cleaning starts immediately.

The monitor handles translation, SDV and queries inside an end-to-end workflow, not working across scattered tools

The online remote SDV workflow also supports the monitor in multiple ways.

When a source document needs translating before SDV, the monitor can obtain rapid translation through the platform’s translation integration — instead of sending it out to a vendor and waiting for it to come back before verification can start.

The platform provides full query management and manual queries are no longer needed.  The monitor raises a query right on the document in question. It’s answered, re-issued or closed in that same place, and every step is recorded — who raised it, what was decided and why — so the query history is audit-ready. This is a major difference compared to the manual process. There, the monitor writes the query by hand, and it becomes its own email thread and another row in a spreadsheet. Without an online SDV platform, these queries sit outside any system — no visible status, no owner — and resolution lags until someone remembers to follow up.

When the monitor is ready to perform SDV, the monitor can efficiently use a side-by-side view of EDC and the remote SDV platform, to compare the critical data fields requiring SDV to the supporting source documentation supplied by the site.

The study team has one source of truth for SDV status reporting

The online remote SDV workflow brings teams full transparency and line of sight, drawn from the platform’s consolidated, automated tracking. Any trial stakeholder can open a single dashboard or detailed reports and determine the current state of SDV across the trial:

• SDV pending and complete
• Documents requested, received, redacted, translated
• Queries opened and closed

The hours once spent reconciling statuses by hand are gone. “Where are we on SDV?” has an answer available on demand — no hidden backlog, no surprises that stall data cleaning targets, DSMB data reports, interim analyses or final database locks.

Site adoption: less burden, not more

A fair question at this point is around site adoption. Clients ask whether sites will reject using a system to support remote SDV.  Sites already manage more systems than they’d like, and any new tool must justify its place. What we’ve seen is strong site adoption — because in practice, the online remote SDV workflow is far less burdensome than what sites do now, either supporting on-site visits or workarounds. The legacy on-site model means hours of pulling charts and sitting with a monitor. The manual workarounds mean juggling email requests, and pulling charts to hunt for, extract and scan specific documents after performing tedious manual PHI/PII redaction. Compared to these situations, the online remote SDV workflow asks less of the site, not more.

What’s next for remote SDV?

In a poll during the webinar, just 1 in 20 attendees said they already had an efficient remote SDV solution in place. The rest were struggling with some version of the workarounds above — or hadn’t started at all.

The next round of SDV efficiency won’t come from verifying less data. The industry already did that work — risk-based monitoring narrowed the focus to the data that matters, and it was the right move. The next round is about the data verification that remains: doing it in a controlled, observable, efficient, online process instead of a manual one.

And there’s another gain just over the horizon. The same platform that makes online remote SDV possible today is the one that will make AI-assisted SDV possible next.

Watch the webinar on demand: From Integrated Remote SDV to AI-Assisted SDV: What’s Next?

AG Mednet’s Judi platform supports remote SDV as a configured workflow today — including site-side upload, AI-assisted redaction, document-based queries and centralized status reporting across the trial. Request a demo.

‍

‍Cathy Tyner brings 27 years of clinical research experience with a focus on Oversight Group Management for Clinical Endpoint Committees, Data Monitoring Committees, and other operations.

‍