Picture a coordinator at a mid-size academic site running three concurrent oncology trials. She has a Signant Health eCOA device for patient-reported outcomes on the first study, an Ametris ActiGraph wearable for actigraphy and passive sensor data on the second, and a separate EDC login for both. When a data query comes in at 4:45 PM on a Friday, she is reconciling timestamps across two vendor portals, two help desk ticket systems, and two sets of site training credentials — none of which talk to each other. That reconciliation gap is not a technology inconvenience. It is a source of protocol deviations, query aging, and coordinator burnout that sponsors routinely underestimate when they build their data collection architecture in a PowerPoint deck far from the site floor.
Signant Health’s acquisition of Ametris on May 14, 2026 — consolidating Signant’s eCOA platform with Ametris’s wearable-derived digital outcome measures — is the kind of vendor consolidation move that generates a press release and a sponsor strategy meeting but rarely makes it onto a site readiness checklist. It should.
The Fragmentation Cost No One Budgets For
Sponsors report using eCOA in 53% of their clinical trials over the last two years, with plans to increase that to 64% in the next two years. What that adoption curve obscures is how many of those deployments layer multiple COA vendors onto a single study — one vendor for ePRO, a separate vendor for wearable biomarkers, and sometimes a third for clinician-reported outcomes. Each vendor relationship arrives at the site as a separate training module, a separate device accountability log, and a separate escalation pathway when something breaks at 6 AM before a patient visit.
The operational math is straightforward and brutal. A site coordinator managing a study with two COA vendors needs, at minimum, two SIV training sessions, two sets of login credentials, two deviation documentation pathways if a device malfunctions, and two billing cycles during site closeout. Across the network of sites I work with, multi-vendor COA setups consistently appear in monitoring visit findings — not because sites are careless, but because the documentation burden of maintaining ALCOA-C compliance across asynchronous vendor platforms creates structural exposure. Source data traceability, specifically ICH E6(R3) Section 5.5‘s requirement that data be attributable and legible regardless of capture method, becomes genuinely difficult when a wearable sensor timestamp and an ePRO submission timestamp live in separate data architectures with different audit trail formats.
Signant’s previous acquisition of DSG, Inc. — which added a full-featured EDC/DDC solution to Signant’s portfolio for an undisclosed price — signaled the direction: vertical integration of data capture, not point solution competition. The Ametris deal accelerates that logic by pulling passive, continuous wearable data into the same platform stack as patient-reported outcomes. The regulatory groundwork for that integration was laid in December 2023, when the FDA published its final guidance on Digital Health Technologies for Remote Data Acquisition, explicitly recommending that sponsors define in their protocols how DHT-derived data will be attributed, validated, and reconciled with other data streams. That guidance is not optional language — it creates an audit expectation that a fragmented vendor stack makes much harder to satisfy.
Which raises the question sponsors building 2026 and 2027 protocols should be asking now: if the FDA expects a coherent DHT data validation narrative and the vendor landscape is consolidating around integrated platforms, what happens to the multi-vendor architecture you locked into your master service agreement eighteen months ago?
What Consolidation Actually Costs at the Site Level
Vendor consolidation announcements always lead with the platform benefits. The operational reality at sites runs about six months behind the press release.
When Signant absorbs Ametris’s device ecosystem, sites currently running Ametris ActiGraph devices under existing study agreements will face a transition period where training materials, help desk pathways, and device provisioning workflows are being standardized across the combined entity. That transition lands on the coordinators — not on the vendor integration team. Any site that has lived through a mid-study EDC migration, or absorbed a CRO rebrand mid-trial, knows what this looks like: a period of three to six months where the answer to “who do I call?” is genuinely ambiguous, and where monitoring visit findings spike because the documentation trail between legacy and new systems has gaps that no one’s SOP yet covers.
The budget exposure is equally concrete. Screen failure rates climb when device malfunctions are not triaged quickly — a patient who comes in for a baseline visit, fails to sync their wearable, and leaves without completing the ePRO has generated a screen failure that costs the site the full per-patient screening fee and costs the sponsor a lost enrollment slot. Across our network, device-related screen failures in wearable-heavy studies run between 8% and 12% of all screening failures during the first sixty days of enrollment — a window that maps directly onto vendor transition turbulence. That is not a rounding error in a competitive enrollment environment.
Sponsors who built their COA vendor stack assuming the Ametris and Signant platforms would remain independent now need to reassess two things before their next protocol amendment cycle: first, whether their existing vendor contracts specify platform continuity obligations during acquisitions, and second, whether their site training budgets account for retraining if device provisioning or portal interfaces change. Most MSAs are silent on acquisition-triggered platform transitions. That silence becomes a budget dispute between sponsor and CRO at the worst possible moment — when enrollment is already open.
What Operators Should Do Before Monday
For site teams currently running studies with Ametris devices or Signant eCOA platforms: pull your device accountability logs and confirm that your help desk contacts and escalation procedures are documented in your site-level SOPs, not just in the vendor’s onboarding email from eighteen months ago. When vendor support structures change during an acquisition integration, sites that have vendor-agnostic escalation procedures in their own documentation are protected; sites that rely on a vendor portal link that redirects to a new system are not. Document what you have today.
For sponsors and CROs building protocols with both ePRO and wearable digital biomarkers: the FDA’s December 2023 DHT guidance requires a prospective validation plan for remotely acquired data. Use the Signant-Ametris consolidation as the forcing function to draft that plan as a single integrated document rather than two vendor-specific appendices. Integrated data validation narratives are faster through IRB review, simpler to audit, and more defensible at a BIMO inspection — the operational advantage of a consolidated platform only materializes if your protocol architecture is designed to use it.
The sites that will feel this acquisition least are the ones that never let vendor management live inside a vendor’s own portal. The sites that will feel it most are the ones still operating on the assumption that the eCOA stack they set up at the investigator meeting is the same stack they will close out on.
References
- FierceBiotech — “Signant Health buys Ametris to unite data streams in clinical trials”
- PR Newswire — “Signant Health Acquires Ametris to Create an End-to-End eCOA and Digital Outcome Measures Platform” (May 14, 2026)
- Suvoda — “Decoding eCOA Trends: Adoption Predicted to Rise”
- BMT Advisors — “FDA Issued Final Guidance on Digital Health Technologies for Remote Data Acquisition in Clinical Investigations” (December 2023)
- FierceBiotech — “Signant Health snaps up DSG to expand decentralized trial offerings”
- YPrime — “FDA and Clinical Technologies: DHT Guidance Overview”
