Decentralized Clinical Trial (DCT) Compliance: A Sponsor’s Checklist for Home Health, ePRO, Wearables, and Televisits

PI oversight and delegation in decentralized delivery models

Decentralized and hybrid trials distribute activities across locations and organizations. Inspection risk increases when the Investigator’s oversight becomes hard to see in the records. The goal is to make oversight explicit through delegation, training, communication pathways, and documented review of critical activities.

This section is operational guidance only and not legal advice.

Delegation and supervision controls (practical)

• Delegation log scope: include home health nurses, telehealth clinicians, and any remote assessors who perform protocol-required procedures.
• Training evidence: role-based training on protocol procedures, AE identification/reporting, device handling, and documentation requirements.
• Supervision cadence: documented check-ins and review of key data (e.g., tele-visit notes, home visit worksheets).
• Escalation pathways: how home health staff report urgent medical issues to the Investigator and sponsor.

Connect DCT oversight to your vendor oversight and monitoring strategy (see Vendor Oversight and RBM That Works).

Home health and mobile nursing: documentation that counts as source

Home visits create a common tension: operational efficiency vs. source documentation quality. Decide up front what constitutes source, how it will be captured, and how it will be reviewed.

Home visit worksheet checklist (example fields)

• Subject ID, visit date/time, location
• Verifier: identity confirmation method used
• Protocol procedures performed (with completion status and notes)
• Vitals and assessments with units and device identifiers where relevant
• Investigational product handling steps if applicable (delivery, storage, accountability)
• AE screening questions and any reported events
• Deviations encountered (missed window, incomplete sample, technical issues)
• Escalations made (who contacted, when, and outcome)
• Signature/attestation and audit trail mechanism

Controls to prevent common findings

• Training + competency: confirm home staff can follow protocol-specific procedures and document them consistently.
• Source transfer: if paper is used, define scanning standards, upload timelines, and QC checks.
• Data privacy: ensure devices and transport methods meet your privacy expectations; document controls.

Televisits: keep the clinical narrative and timestamps defensible

Televisits can be compliant and high quality, but only if you standardize documentation and manage technology limitations.

Minimum documentation for a tele-visit note

• Platform used and any technical limitations encountered
• Confirmation of participant identity and location (as relevant to safety)
• Confirmation of privacy (e.g., participant in a private setting)
• Protocol assessments completed and any omissions with rationale
• AE screening and safety assessment
• Any referrals, dose changes, or follow-up actions

Where televisits intersect with consent (e.g., remote re-consent), ensure the consent process is fully documented and version-controlled (see Informed Consent Compliance).

ePRO, wearables, and devices: data flow, assurance, and integrity

DCTs often increase dependence on technology. You should be able to explain the data journey from the subject’s device to the analysis dataset and show controls at each step.

1) Map the data flow

At minimum, document:

• Device provisioning and subject onboarding steps
• How data are captured (online/offline), time-stamped, and transmitted
• Where data are stored (vendor cloud, sponsor systems) and who has access
• How missing or anomalous data are flagged and acted upon
• Export and transformation steps into EDC/analysis systems

2) Assurance and audit trail expectations

Use a risk-based assurance approach for systems and integrations (see CSV vs CSA). Make sure you can retrieve audit trails and demonstrate ALCOA+ attributes for key data (see ALCOA+ Data Integrity).

3) Operational controls checklist

• Standard onboarding script and troubleshooting guidance
• Replacement and re-provisioning process (lost devices, phone upgrades)
• Calibration/maintenance logs if applicable
• Alerts workflow: who receives alerts, response timelines, documentation
• Data review cadence and escalation for non-compliance

Safety reporting in DCTs: don’t let distributed care break timelines

In decentralized models, adverse event information may be captured via home staff, device alerts, tele-visits, or ePRO diaries. Define what counts as “receipt,” how it is transmitted to the safety team, and how follow-up is coordinated.

Safety controls checklist

• Clear pathways for home staff/telehealth clinicians to report events rapidly
• Training on seriousness criteria and urgent escalation
• Reconciliation between ePRO events/alerts and AE/SAE entries in EDC
• Documented oversight and metrics for timeliness and follow-up

For a detailed PV workflow and reconciliation approach, see PV & Safety Reporting. Make sure DCT vendor oversight includes these safety handoffs (see Vendor Oversight).

Direct-to-participant IP: accountability, excursions, and documentation

Direct shipment of investigational product can be compliant, but only when the chain of custody and exception handling are controlled. Most downstream issues come from unclear ownership (site vs depot vs courier vs participant) and from missing documentation of the decision to ship or replace product.

Minimum controls and evidence outputs (practical)

• Shipment authorization rule: who releases a shipment and what prerequisites must be verified (eligibility, consent/reconsent status, lab results, safety checks).
• Chain-of-custody: shipment ID, dispatch date/time, receipt confirmation method, and documentation of any failed deliveries.
• Temperature monitoring (when required): how excursions are detected, evaluated, and documented; who decides “use vs replace.”
• Accountability reconciliation: how participant-reported dosing aligns with shipped quantities and return/destruction records.
• Returns/destruction: controlled instructions, documentation of completion, and filing location in TMF/eTMF.

Where direct-to-participant IP is supported by vendor systems, confirm that records are enduring and retrievable and that audit trails can be exported when needed (see CSV vs CSA and TMF/eTMF).

DCT-specific KRIs and centralized oversight: measure what fails first

Decentralized models create early warning signals that are different from traditional site-only trials. Build a small set of DCT-focused KRIs and review them routinely in central monitoring so you can intervene before data become irrecoverable.

Examples of DCT KRIs (with typical actions)

• Visit window non-compliance for key assessments → trigger scheduling workflow review and participant reminder optimization.
• Device/ePRO missingness trend (drop in completion rate) → trigger participant support outreach and device troubleshooting; assess impact on evaluability.
• Televisit documentation completeness (missing identity confirmation, missing AE screening) → trigger refresher training and note template updates.
• Home visit failure rate (missed appointments, incomplete samples) → trigger vendor escalation, resourcing review, and contingency planning.
• IP delivery exception rate (failed deliveries, excursions, reshipments) → trigger depot/courier process review and accountability reconciliation.

Document the chain of signal → assessment → decision → action in central review notes and governance minutes (see RBM That Works). When repeated issues indicate systemic failure, initiate CAPA with measurable effectiveness checks (see CAPA).

Technology operations: support, incidents, and evidence of control

DCT success depends on reliable technology and rapid support. From a compliance perspective, the key is to show that technology failures are detected, triaged, and resolved in a controlled way—with documentation of participant impact and data impact.

Incident log fields (example)

• Incident ID, date/time opened, reporter (participant/site/vendor)
• System/device affected and subject(s) impacted
• Problem description and severity (safety impact? critical data impact?)
• Containment actions (temporary workaround, visit rescheduling)
• Resolution and verification step (how you confirmed the fix worked)
• Data impact assessment (missing data? incorrect timestamps? duplicate entries?)
• CAPA linkage if recurring or systemic

For critical systems, ensure your assurance binder includes incident handling and change control evidence (see CSV vs CSA). If incidents affect data integrity, document reconciliation and audit trail review outcomes (see ALCOA+ Data Integrity).

DCT deviation patterns: decide in advance what is a deviation (and what is a data issue)

DCTs create frequent exceptions—missed ePRO entries, failed home visits, device replacements—that can overwhelm deviation logs if you treat every technical hiccup the same. Define decision rules so your deviation process stays meaningful.

Decision prompts (example)

• Did the event break a protocol requirement? If yes, assess whether it impacted safety/rights/endpoints.
• Was it a technology failure? If yes, open an incident record and evaluate whether it caused protocol non-compliance or only missingness.
• Is it recurrent? If yes, trend it as a KRI and consider CAPA (vendor resourcing, training, or system change).
• Does it require subject contact? (e.g., missed safety diary, missed symptom report) If yes, define follow-up timelines.

When DCT deviations indicate systemic weakness, escalate through CAPA with effectiveness checks (see Protocol Deviations and CAPA) and document oversight decisions in central monitoring notes (see RBM That Works).

Distributed geography: document how you keep clinical accountability clear

In decentralized models, participants, home staff, and telehealth clinicians may be in different locations. Without giving legal advice, operational teams should ensure there is a documented model for Investigator oversight, escalation pathways, and how location-related constraints are handled (e.g., when a participant travels). Keep decisions and communications traceable, and train staff to escalate unusual location scenarios rather than improvising. Include a simple “who to call” tree so urgent safety concerns do not bounce between vendors, and document escalation outcomes consistently across sites.

Practical tip: include at least one DCT-focused “subject story” retrieval drill (televisit note + home visit worksheet + ePRO export + IP shipment record). If you can retrieve that package quickly and consistently, many DCT inspection questions become straightforward.