🏠 Mobile Nursing Home Visit Coordination

Geofenced Network Mapping — Matching Participants to a Credentialed Field-Nursing Roster

Decentralized trials replace the single brick-and-mortar site with a distributed network of mobile research nurses who travel to the participant. That flexibility only works if every nurse assigned to a participant is licensed in the participant's state, trained on the specific protocol, and reachable within a clinically reasonable drive time — so the first engineering problem in home-visit coordination is not logistics, it is credential-constrained geospatial matching.

• 41: Nurse Licensure Compact states (multistate RN licensure, 2024)
• 25–60 km: Typical service radius (urban vs. rural catchment)
• 6–12 hrs: Protocol-specific training (per nurse, before first visit)
• 2,000+: Vendor network size (large CRO) (credentialed field nurses, US)

Credential-constrained matching, not nearest-neighbor routing

A naive dispatch system would assign the geographically closest nurse to each participant. Home-visit coordination platforms (Illingworth Research Group's Trial Nurse Network, IQVIA MRN, Medable Home Health, Care Access) instead run a constrained matching problem where distance is only one of several hard filters:

• Licensure jurisdiction — under the Nurse Licensure Compact (NLC), a multistate license lets an RN practice in 41 participating states without an additional state license; participants in the remaining states (including California, New York) require a nurse independently licensed in that specific state • Protocol competency — nurse must hold current GCP training (CITI Program or equivalent, renewed every 2–3 years) plus a protocol-specific competency sign-off covering IP handling, device use (e.g., ambulatory ECG patch, spirometer), and adverse-event escalation criteria • Scope-of-practice ceiling — IV infusion of investigational product, arterial lines, or complex titration may require an advanced-practice nurse or require a physician/APRN standing order; the matching engine tags visit types against the minimum credential required • Malpractice and background clearance — active professional liability coverage and a background check refreshed within the past 12 months • Drive-time isochrone, not radius — matching uses routed drive-time polygons (typically capped at 45–75 minutes one-way) rather than a fixed-radius circle, because rural service areas can have low road density inside a nominal 40 km circle

Only after all hard filters are applied does the system rank remaining eligible nurses by drive time, existing route load for the day, and continuity (the same nurse seeing the same participant across visits improves protocol adherence and participant retention).

Continuity of nurse assignment is independently associated with retention: sponsor-reported dropout in visit-heavy decentralized oncology trials falls by roughly one-third when the same field nurse is assigned across ≥80% of a participant's scheduled visits, versus a rotating pool — a finding cited repeatedly in DCT operational reviews since 2022.

Coverage-gap detection and staffing escalation

Once every enrolled or pre-screened participant is geocoded, the platform overlays participant density against nurse coverage polygons to flag gaps before they become missed visits:

• Amber flag: participant falls inside the service radius but outside every currently-scheduled nurse's realistic same-day route capacity (typically 4–6 home visits/day depending on complexity) • Red flag: participant falls entirely outside any credentialed nurse's coverage polygon — triggers a staffing request to the mobile nursing vendor to recruit and credential a new nurse in that ZIP/postal cluster, a process that typically takes 10–21 days including licensure verification • Contingency site fallback: for red-flag participants awaiting new-nurse credentialing, the protocol's contingency plan (required under FDA's 2023 DCT guidance) routes the visit to the nearest brick-and-mortar clinical research site or a local independent home-health agency under a site-delegated task

Geocoding itself must handle rural addressing inconsistencies (P.O. boxes, unnamed rural routes) — platforms typically fall back to reverse geocoding from a participant-confirmed pin drop when a structured address fails automated geocoding, which happens in an estimated 4–7% of rural enrollments.

Visit Scheduling & Route Optimization Inside the Protocol Visit Window

Every scheduled visit in a clinical protocol carries a defined window — typically Day 28 ±3 days for a monthly assessment — inside which the visit must occur for the data point to be valid without a protocol deviation. Home-visit dispatch turns that constraint, multiplied across dozens of nurses and hundreds of participants, into a daily constrained vehicle-routing problem that has to run automatically, every day, without a human dispatcher hand-building routes.

• ±3 days: Typical visit window (protocol-defined, monthly visits)
• 4–6: Visits per nurse per day (complexity-dependent)
• <48 hrs: Missed-visit reschedule SLA (to stay inside window)
• nightly + ad hoc: Route re-optimization (on cancellation/AE escalation)

The daily route as a capacitated vehicle-routing problem

The scheduling engine treats each nurse as a vehicle with a capacity (visits/day, bounded by equipment and fatigue), a starting depot (home base or a regional equipment locker), and a set of time-windowed stops (participant homes, each with an allowable arrival window derived from protocol visit window intersected with participant availability):

Objective: minimize total drive time + minimize schedule slack, subject to: • Each participant visited exactly once per scheduled event • Each visit occurs inside its time window (both the protocol day-window and the participant's stated availability window, e.g., 9am–1pm) • Nurse total route time (drive + dwell) does not exceed a duty-day cap (commonly 8–10 hrs including documentation time) • Equipment constraints — a cooler carrying temperature-sensitive investigational product can only be checked out to one route per day and must return to a qualified storage unit within its validated excursion time • Skill/credential constraints inherited from the matching stage

This is a variant of the classic capacitated VRP with time windows (VRPTW), typically solved with a metaheuristic (large neighborhood search or guided local search) rather than exact solvers, because daily re-optimization across a multi-hundred-nurse network must complete in minutes, not hours. Route quality is measured against a "compact route" heuristic score combining total drive distance and window-violation risk.

Illingworth Research Group has publicly reported field-nursing networks executing over 45,000 home visits annually across 60+ countries; at that scale even a 10% improvement in average route compactness translates into thousands of nurse-hours reclaimed per year and a measurable reduction in missed or window-violating visits.

Handling disruption — cancellations, AEs, and same-day re-routing

Static route plans break constantly in the field: a participant reschedules, a nurse reports a vehicle issue, or a same-day adverse-event visit is triggered by a wearable-device alert or a participant-reported symptom via the eCOA app. The coordination platform must re-optimize the affected nurse's remaining route (and sometimes neighboring nurses' routes) in near real time:

• Cancellation ripple: freed capacity is offered first to participants nearing the edge of their visit window (oldest-window-first prioritization), then to newly-triggered unscheduled visits • Urgent/AE-driven visit insertion: a same-day insertion request (e.g., a participant reports a Grade ≥2 adverse event requiring an in-person assessment) is inserted into the nearest feasible nurse's route with an override that can breach the soft compactness objective but not hard duty-day or credential constraints • Missed-visit recovery: any visit that cannot be completed inside its protocol window is automatically flagged for protocol-deviation logging and routed to the site's clinical operations team with a root-cause code (participant-initiated, nurse unavailability, weather/access, equipment)

Route plans are pushed to each nurse's mobile app the evening before, with turn-by-turn navigation and a pre-visit checklist (kit inventory, IP temperature log check, consent version confirmation) that must be acknowledged before the app allows check-in at the first stop.

Home Visit Execution — Identity Verification, Procedures, and Direct Data Capture

Inside the participant's home, the field nurse becomes, for the duration of the visit, the extension of the investigator's delegated authority. Every action — identity check, procedure, and data entry — has to be defensible on later audit exactly as if it had occurred inside a site exam room, which is why home-visit platforms lean heavily on direct-to-eSource capture rather than paper worksheets transcribed later.

• 2: Identity verification points (independent identifiers, every visit)
• >95%: Same-visit data entry target (captured directly, no transcription)
• who/what/when: Part 11 audit-trail fields (every eSource edit logged)
• 35–90 min: Average home visit duration (complexity-dependent)

Identity verification and delegation-of-authority in a non-clinical setting

A home has none of the institutional identity safeguards of a hospital or clinic, so ICH E6(R2/R3) GCP identity-verification obligations are satisfied procedurally instead of environmentally:

• Dual-identifier check at every visit: full legal name plus date of birth (or a study-issued participant ID plus photo ID on file), matched against the eSource system before any procedure is logged • Delegation log currency: the field nurse's name, credential, and the specific procedures they are authorized to perform must appear on the site's current FDA Form 1572 delegation-of-authority log — an out-of-date delegation log is one of the most common findings in FDA BIMO inspections of decentralized trial sites • Standing orders and remote supervision: procedures requiring real-time clinical judgment (e.g., IP dose-hold decisions) are executed under a pre-approved standing order or via live video connection to the investigator, documented as a distinct telehealth encounter • Chaperone and privacy controls: a second household member present during intimate procedures is logged per protocol privacy plan; visits are scheduled to a private room when possible

Each of these controls exists because a sponsor audit or FDA inspection must be able to reconstruct, months later, exactly who performed which procedure on which participant, under whose authority — with the same rigor expected of an on-site visit.

Direct data capture and 21 CFR Part 11 compliance at the point of care

Modern mobile nursing platforms enter data directly into a validated eSource/eCOA tablet during the visit rather than on paper source documents transcribed later — eliminating the transcription-error and delayed-query risk that dogged early home-health research models:

• Direct data capture (DDC): vitals from Bluetooth-paired devices (BP cuff, pulse oximeter, thermometer, weight scale) stream directly into the eSource record, removing manual keystroke transcription error entirely • 21 CFR Part 11 controls: unique user login, time-stamped audit trail on every field (who, what, old value, new value, when), electronic signature at visit closeout, and role-based access separating nurse data-entry rights from monitor/CRA read-only or query-response rights • Real-time protocol deviation flagging: the eSource form itself enforces the schedule of assessments — attempting to log a procedure outside its allowed visit window, or skipping a required vital sign, triggers an immediate soft-alert to the nurse before she leaves the home, catching most deviations at the point of origin rather than days later during monitoring • Offline-first architecture: connectivity in rural service areas is unreliable, so the tablet caches the visit locally with cryptographic integrity checks and syncs on reconnection — a design requirement explicit in FDA's 2023 draft guidance on decentralized clinical trials for drugs, biologics, and devices • eConsent re-verification: for visits coinciding with a protocol amendment, the nurse confirms the participant has reviewed and signed the updated consent version before proceeding — version mismatch is one of the highest-frequency audit findings in DCTs

Because the eSource record is the source document itself (not a copy of a paper form), CRA source data verification becomes a remote desktop review rather than an on-site chart pull — collapsing the query-to-resolution cycle from a multi-week site visit cadence to same-day or next-day.

Biospecimen Chain-of-Custody and Cold-Chain Logistics from Living Room to Central Lab

A blood draw performed on a kitchen table is scientifically identical to one performed in a phlebotomy suite — but only if the specimen is labeled, logged, temperature-controlled, and time-stamped with the same rigor. Chain-of-custody failures (a mislabeled tube, a courier pickup outside the validated stability window) are among the most common and most damaging data-integrity findings in decentralized trials, because a lost or degraded specimen cannot simply be re-drawn the next day without breaching the protocol window.

• 2–8°C: Standard cold-chain range (refrigerated specimens, most panels)
• <4 hrs: Courier pickup SLA (from draw to cold-chain custody)
• Category B: UN3373 shipping class (biological substance, IATA/DOT)
• <30 min: Acceptable temp excursion (before specimen is queried/discarded)

Positive specimen identification and custody logging at every handoff

Chain-of-custody documentation exists to answer one audit question unambiguously: can this specimen, sitting in the central lab's freezer, be traced back to this exact participant at this exact visit with no gap? The home-visit workflow logs a custody event at every physical transfer:

1. Collection: specimen tube pre-printed with a study-generated barcode (linked to participant ID, visit number, and specimen type) is scanned by the nurse's tablet at the moment of draw — not pre-labeled in bulk, which is a common root cause of mislabeling 2. Nurse custody: specimen placed in a validated transport container (cold pack or dry-ice, per analyte) with the nurse's tablet logging container temperature at time of packing 3. Courier handoff: barcode re-scanned by the courier's handheld device at pickup — this scan timestamps the start of the courier's custody window and must occur within the SLA (commonly under 4 hours of draw for room-temperature-labile analytes) 4. In-transit monitoring: a Bluetooth or cellular temperature logger travels inside the shipping container, streaming readings (or storing them for download) for the full transit duration 5. Central lab receipt: barcode scanned on arrival; temperature log downloaded and reconciled against the validated stability range before the specimen is accessioned into the lab information system (LIMS)

Any break in this scan sequence — a specimen that appears in nurse custody but never registers a courier scan, for example — is auto-flagged for investigation before the specimen is used in any analysis.

Cold-chain validation, excursion management, and dangerous-goods compliance

Most clinical specimen types (serum chemistry, most PK samples, many biomarker panels) require 2–8°C refrigerated transport; some require dry ice at ≤-70°C, and others are stable at ambient temperature for a validated window. Regulatory and logistics requirements stack on top of the clinical stability requirement:

• IATA/DOT dangerous goods classification: diagnostic specimens ship as UN3373 "Biological Substance, Category B," requiring triple packaging (primary receptacle, secondary watertight packaging, rigid outer packaging), specific labeling, and courier personnel certified in dangerous-goods handling — a compliance layer entirely separate from GCP but equally auditable • Validated shipping qualification: each container/coolant combination is validated in advance (summer and winter profiles) to demonstrate it holds the target range for a defined duration — typically 24–72 hours — under worst-case ambient conditions • Temperature excursion triage: an excursion under the pre-validated tolerance (commonly <30 minutes outside range for refrigerated specimens) is logged but the specimen is used; a longer excursion triggers a query to the central lab's stability data to determine usability, and if indeterminate, the specimen is marked "not evaluable" — which itself becomes a protocol deviation requiring root-cause analysis • Cold-chain audit trail retention: temperature logs, custody scans, and courier manifests are retained as part of the trial master file for the same retention period as clinical source data — commonly 15–25 years depending on jurisdiction and product class

Home-visit vendors report that with real-time temperature-logger integration and SLA-bound courier contracts, cold-chain excursion rates in mature DCT programs run at roughly 1–3% of shipments, comparable to — and in some rural-site comparisons better than — traditional site-to-central-lab shipping, where inconsistent site refrigeration practices are a recurring inspection finding.

A 2022 sponsor-reported DCT operational review found that centralizing cold-chain logistics through a single validated home-visit courier network (versus ad hoc site shipping) cut specimen-related protocol deviations by roughly 40% year-over-year, primarily by eliminating "specimen sat at room temperature awaiting pickup" as a root cause.

Remote Monitoring, Deviation Triage, and Quality Oversight of a Distributed Nursing Workforce

Once the visit data lands in the eSource system and the specimen is in transit, the trial's quality apparatus takes over: a central monitor reviews the record, deviations are triaged by severity, and the field-nursing network itself is subject to ongoing performance and competency oversight — because in a decentralized model, nursing quality assurance replaces the informal, in-person oversight a principal investigator has over site staff working down the hall.

• <24 hrs: Remote SDV turnaround (from visit close to CRA review)
• 3: Deviation severity tiers (minor / major / critical, per ICH E3)
• annual + protocol amendment: Nurse re-competency cadence (GCP + protocol refresh)
• monthly: Remote site-visit equivalent (aggregate nurse performance review)

Remote source data verification and same-day deviation triage

Because the eSource record is the authoritative source document, the CRA's source data verification (SDV) role shifts from an on-site chart pull to a remote desktop review performed against the same record the nurse entered in the home — typically completed within 24 hours of visit closeout:

• Automated pre-checks: the eSource system itself runs edit-check logic (range checks, cross-field consistency, missing mandatory fields) before a visit can be marked complete, catching the majority of simple data-quality issues before human review • Risk-based SDV: consistent with ICH E6(R2) Section 5.18.3 risk-based monitoring principles, not every field in every visit is verified — critical-to-quality data points (primary endpoint measures, safety labs, informed consent status) receive 100% verification while lower-risk fields are sampled • Deviation severity classification, aligned to ICH E3 conventions: minor (e.g., visit occurred 1 day outside window with no clinical impact), major (e.g., a required safety assessment was missed), critical (e.g., IP administered without a valid, current informed consent) — severity drives escalation timeline, with critical deviations requiring investigator and often IRB/EC notification within 24–72 hours • CAPA loop: recurring deviation patterns at the nurse or regional level (e.g., a specific nurse repeatedly outside visit windows) trigger a corrective and preventive action review rather than being handled as isolated events — this is where field-nursing quality assurance most resembles classic site-monitoring trend analysis

Ongoing competency oversight of a distributed nursing workforce

A traditional site's principal investigator has continuous informal visibility into staff performance simply by being physically present. A network of hundreds of independently-traveling field nurses requires that oversight to be re-engineered as an explicit, data-driven process:

• Direct observation visits: a clinical quality lead periodically accompanies (in person or via live video) a field nurse's home visit for real-time competency assessment — typically targeted at new nurses in their first 3 visits and refreshed periodically thereafter • Video-audited procedures for high-risk steps: some sponsors require the nurse to record (with participant consent) specific high-risk procedures — e.g., IP reconstitution and administration — for centralized quality review rather than relying solely on self-attestation • Aggregate performance dashboards: on-time visit rate, deviation rate, data-query rate, and participant satisfaction score are tracked per nurse and rolled up regionally on a monthly cadence, functioning as the DCT-era analogue of a monitoring visit report • Annual and amendment-triggered re-training: GCP certification renewal (commonly every 2–3 years) plus a mandatory competency refresh whenever a protocol amendment changes procedures, consent, or safety-reporting criteria — undocumented or lapsed re-training is a recurring finding when FDA's Bioresearch Monitoring (BIMO) program inspects decentralized trial conduct • Participant-reported experience: post-visit satisfaction surveys feed back into nurse-participant matching, since participant-reported comfort with a specific nurse is itself a retention driver in long-duration trials

The net effect, when executed well, is a quality system that substitutes systematic, data-visible oversight for physical proximity — the same substitution that defines decentralized trials at every other layer of the protocol.

FDA's final guidance on Decentralized Clinical Trials for Drugs, Biological Products, and Devices (issued 2024, following the 2023 draft) explicitly names qualification and ongoing oversight of local HCPs and mobile nursing providers performing trial-related activities as a sponsor responsibility that cannot be fully delegated — reinforcing that remote monitoring of the nursing workforce is not optional infrastructure but a defined regulatory expectation.