Mobile Nursing Vendors in DCTs: Compliance

When a decentralized trial sends a nurse to a participant’s home rather than the participant to a site, that nurse is very often not a site employee at all. A growing segment of the decentralized clinical trial (DCT) supply chain is made up of third-party mobile and home health nursing vendors — staffing and service organizations that recruit, credential, and dispatch registered nurses (and, in some models, phlebotomists or paramedics) to perform protocol-specified visits wherever a participant lives. This arrangement solves a real operational problem, but it introduces a distinct set of delegation, credentialing, and compliance mechanics that don’t arise when all study procedures happen inside a single investigative site’s four walls. This guide covers those mechanics specifically — how tasks are legally and procedurally delegated to a vendor’s nursing staff, how that workforce is credentialed and kept current, and what compliance infrastructure has to exist around every home visit for it to hold up under monitoring and inspection.

This is a narrower, staffing-and-oversight question than “what is a DCT platform” or “should this trial run centralized or decentralized” — see the site’s centralized vs. decentralized trials comparison for that higher-level decision. A DCT platform is the software and service layer connecting visits, consent, and data; a mobile nursing vendor is the physical workforce that actually performs the visit. Most decentralized trials of any scale need both, and they are governed by different mechanics.

What Mobile and Home Health Nursing Vendors Actually Do

A mobile/home health nursing vendor is typically contracted by the sponsor or CRO — occasionally directly by a site — to supply nurses who travel to a participant’s home, workplace, or a local community setting to perform some subset of protocol-specified procedures: vital signs and physical assessments, blood draws and specimen collection, investigational product (IMP) administration (including injections and infusions where permitted), device training and downloads, and administration of paper or electronic outcome assessments. The vendor is not the trial’s regulatory sponsor or the investigative site; it is a service provider whose staff perform delegated clinical tasks under the oversight of the principal investigator (PI) of record, even though those staff never set foot in the PI’s clinic.

This model is distinct from a participant’s own local physician or home health agency providing routine, standard-of-care treatment unrelated to study endpoints — FDA’s guidance on decentralized trials treats that scenario differently from research-specific procedures performed by vendor staff acting on the investigator’s behalf (see the delegation section below). Mobile nursing vendors exist specifically to perform the latter: tasks tied to protocol endpoints, conducted under investigator delegation, and documented as part of the trial’s essential records.

Delegation of Duties to Non-Site Nursing Staff

Good Clinical Practice has always allowed an investigator to delegate trial-related duties to appropriately qualified staff, documented on a Delegation of Authority (DoA) Log (see also the site’s annotated DoA log template). What changes with a mobile nursing vendor is that the delegate is not co-located with, and often not directly employed by, the investigator or the site — they work for a separate contracted organization, sometimes performing visits for the same trial across dozens of geographically dispersed participants and multiple sites simultaneously.

FDA’s final guidance on Conducting Clinical Trials With Decentralized Elements (issued 2024) addresses this directly: routine, standard-of-care procedures performed by a participant’s existing local healthcare provider generally do not require a formal delegation of authority, but research-specific procedures tied to study endpoints — the kind mobile nursing vendors are contracted to perform — do. Where a home health nurse is carrying out protocol-specified assessments or interventions on the investigator’s behalf, FDA expects the same delegation, training, and oversight rigor as for on-site staff: the investigator (or a qualified sub-investigator) must ensure the nurse is trained to the protocol, competent to perform the delegated tasks, and subject to ongoing review of the data and records that visit produces.

In practice, this means the trial’s DoA Log — or a vendor-specific addendum to it — has to capture every nurse who may perform a visit for that PI’s participants, not just a fixed roster of on-site coordinators. Because mobile nursing vendors often maintain a large, rotating field workforce to provide geographic coverage, sponsors and sites typically negotiate one of two delegation models with the vendor up front:

Named-roster delegation — the vendor supplies a finite, vetted list of nurses eligible to work on the trial; each is individually added to the DoA Log (or a vendor-managed sub-log referenced by it) before performing any visit, with training records verified in advance.
Credentialed-pool delegation — the vendor maintains a larger qualified pool and assigns whichever available, trained nurse is geographically closest for a given visit; delegation authority is tied to a documented credentialing and training standard the vendor attests every assigned nurse meets, with per-visit assignment records substituting for a static named list.

Either way, delegation is not satisfied by a master services agreement alone — the trial’s essential documents need a traceable link between a specific nurse, a specific visit, and evidence that nurse met the protocol’s training and competency bar at the time of that visit. This is the area regulatory inspectors and monitors probe hardest in vendor-nurse models, because it is where the paper trail is most likely to be incomplete.

Credentialing the Vendor’s Nursing Workforce

Credentialing a mobile nursing vendor’s workforce covers several layers that a purely on-site model handles more simply because everything sits in one regulatory binder at one location:

State licensure and multistate practice

A home health research nurse must hold an active, unrestricted license valid in the state where the participant physically receives care at the time of the visit — not merely the state where the vendor or the nurse is based. The Nurse Licensure Compact (NLC), administered through the National Council of State Boards of Nursing, allows a nurse whose primary state of residence is an NLC member state to hold a single multistate license recognized across all participating states and territories (44 as of 2026), which is what makes a geographically dispersed field-nursing model operationally viable at scale. For visits in non-compact states, the vendor needs either a nurse separately licensed in that state or a single-state license processed for that jurisdiction — a real driver of which states a vendor can realistically cover, and a question sponsors should ask before assuming national coverage.

GCP and protocol-specific training

Because vendor nurses are not employed by the site, their Good Clinical Practice training has to be independently verified and documented rather than assumed from institutional onboarding. Sponsors typically require current ICH E6 GCP certification plus protocol-specific training (delivered by the sponsor, CRO, or site) completed and documented before a nurse is added to the delegation record — the same “trained to the same standard as site staff” expectation FDA’s decentralized-trials guidance sets out.

Background screening and exclusion checks

Vendor nursing staff performing federally funded or FDA-regulated trial activities are subject to the same exclusion and debarment screening as any other clinical trial personnel — see the site’s guide on OIG exclusion list screening for clinical research staff for the mechanics. Because vendor staff turn over more frequently than a fixed site team, this screening needs to be a recurring process built into the vendor relationship, not a one-time check at contract signing.

Professional liability coverage

Home-visit nursing carries liability exposure a traditional site visit doesn’t — the nurse is working alone, off institutional premises, often performing procedures like venipuncture or IMP administration outside a clinical facility. Contracts typically require the vendor to carry and evidence its own professional liability/malpractice insurance naming the sponsor and site as additional insureds, separate from the site’s own institutional coverage.

Reconciling vendor credentialing files with the site’s regulatory binder

The practical failure point in this model is not usually that credentialing doesn’t happen — it’s that it happens in the vendor’s own system and never makes it, in a monitor-ready form, into the trial’s essential documents. Sites and CROs increasingly require vendors to submit a standardized credentialing packet (license verification, GCP certificate, protocol training completion, background check attestation) per assigned nurse, timed to precede that nurse’s first visit, rather than relying on the vendor’s internal HR system as the system of record for the trial.

Compliance Mechanics Specific to Home-Based Visits

Chain of custody for specimens and product

A specimen drawn in a participant’s living room has to travel through the same validated chain of custody a site-drawn specimen would — collection time, storage conditions, courier pickup, temperature-monitored transport, and receipt at the central or local lab all need to be documented, but now across a home environment the sponsor doesn’t control. Vendor SOWs typically specify courier services, temperature-logging device requirements, and time-to-pickup windows as contractual deliverables, not just process guidance.

HIPAA and data-sharing agreements

Because the vendor is a separate legal entity handling protected health information and research data outside the site’s own systems, a Business Associate Agreement (or equivalent data processing agreement, depending on jurisdiction) between the site/sponsor and the vendor is a baseline requirement, alongside role-based access controls for whatever eSource or eCOA system the vendor’s nurses use to document the visit.

Adverse event escalation from the field

A vendor nurse who observes or is told about an adverse event during a home visit is the first point of contact for a safety signal the PI has to become aware of on the same regulatory timelines as any other AE. Vendor contracts and training need an explicit, protocol-referenced escalation pathway — who the nurse calls, within what window, and how that’s documented — because there is no site coordinator down the hall to catch it informally.

Source documentation and monitor access

Monitors and auditors need a defined path to review home-visit source records — whether that’s direct read access to the vendor’s eSource platform, periodic transfer of completed visit records into the site’s system, or scheduled remote or on-site access to the vendor’s own files. This should be specified in the vendor agreement and the monitoring plan up front; discovering during an inspection that vendor-held source records are difficult to access is a recurring finding in decentralized-trial oversight discussions.

Vendor oversight as an extension of sponsor oversight

A mobile nursing vendor is functionally a delegated third party in the same regulatory sense as a CRO performing outsourced trial functions — sponsor oversight obligations don’t transfer away just because the work is subcontracted. See the site’s guide on sponsor oversight of delegated CRO functions under ICH E6(R3) for the general oversight framework this extends to a nursing vendor specifically: a documented quality/oversight plan, periodic performance review (visit completion rates, protocol deviation rates, credentialing currency), and escalation authority if the vendor’s performance or compliance slips.

Contracting and Scope-of-Work Considerations

Because so much of the above is only enforceable if it’s written into the contract, sponsors and CROs typically negotiate specific provisions with mobile nursing vendors beyond a standard master services agreement:

Geographic coverage commitments — which states/regions the vendor can realistically staff, given licensure constraints, and the process (and lead time) for expanding coverage into a state outside the current pool.
Named delegated task list — an explicit scope of work enumerating exactly which protocol procedures vendor nurses are authorized to perform, mapped to the DoA Log rather than left as a general “clinical support” description.
Credentialing SLAs — turnaround time for submitting a new nurse’s credentialing packet before that nurse can be added to the delegation record, and a recurring cadence for re-verifying licensure and training currency.
Data and specimen handling specifications — courier, chain-of-custody, and eSource access terms, not left implicit.
Liability and insurance requirements — coverage minimums and additional-insured provisions.
Escalation and reporting — safety-event escalation timelines and routine performance reporting (visit completion, deviations, complaints) to the sponsor or CRO.

Sites and sponsors that treat the vendor relationship as a standard staffing procurement, without these trial-specific provisions, are the ones most likely to discover gaps in delegation or credentialing documentation only when a monitor or inspector asks for it.

Frequently Asked Questions

Is a mobile nursing vendor the same thing as a DCT platform?

No. A DCT platform is the software and coordination layer — eConsent, telehealth, direct-to-patient IMP shipment, eCOA/device integration. A mobile nursing vendor is the physical clinical workforce that performs in-person procedures at a participant’s location. Many decentralized trials use both together: the platform schedules and documents the visit; the vendor’s nurse performs it.

Does a home health nurse performing study procedures need to be on the site’s Delegation of Authority Log?

Generally yes, for research-specific procedures tied to study endpoints — FDA’s decentralized-trials guidance treats this the same as any other delegated clinical task, distinct from a participant’s own local provider delivering unrelated standard-of-care treatment. See the delegation section above for the named-roster vs. credentialed-pool approaches sponsors typically use to manage this at scale.

Can a single mobile nursing vendor cover a trial across all 50 U.S. states?

Only if its nursing workforce’s licensure covers those states. The Nurse Licensure Compact lets a nurse licensed in a compact member state practice across other compact states under one multistate license, but non-compact states still require a separate license, which is a real constraint on national coverage claims — worth confirming state-by-state with a prospective vendor rather than assuming.

Who is responsible for an adverse event a vendor nurse observes during a home visit?

The principal investigator remains responsible for AE/SAE assessment, causality, and regulatory reporting timelines regardless of who observed the event. The vendor’s role is to escalate promptly and document what was observed; the contract and training should specify exactly how and how fast.

Does using a nursing vendor change the trial’s GCP obligations?

No. FDA does not treat decentralized elements, including third-party nursing vendors, as a separate regulatory category — the same IND/IDE, GCP, informed-consent, and safety-reporting requirements apply. What changes is where and by whom specific procedures are performed, which is exactly why delegation and credentialing documentation matter more, not less, in this model.

Mobile and Home Health Nursing Vendors in Decentralized Trials: Delegation, Credentialing, and Compliance