The Hidden Problem Delaying Decentralised Trials
Decentralised clinical trials (DCTs) have transformed how sponsors and CROs bring patients into studies. Participants can now have their blood pressure monitored at home, at a local clinic, or through ambulatory devices without ever setting foot at a principal investigator site. The flexibility is invaluable but the data problem it creates is significant.
When blood pressure readings are collected across multiple modalities – Home, Office, and 24-hour ABPM monitors – using different equipment from different vendors, the result is almost always the same: fragmented data.
Readings arrive in incompatible formats.
Timestamps don’t align.
Device-specific outputs sit in silos that don’t talk to each other, let alone to your EDC.
Data managers spend weeks reconciling records and delaying database locks, when they should have flowed seamlessly from patient to database from day one. For sponsors and CROs running studies with cardiovascular endpoints or any protocol where BP is a primary or secondary measure, this fragmentation becomes a regulatory and timeline risk.
Why BP Data Fragmentation Happens in DCTs
Decentralised trial design is inherently multi-modal when it comes to blood pressure monitoring. A single protocol might require home BP monitoring for routine readings, office visits for supervised measurements, and ABPM for 24-hour ambulatory profiles. Each modality typically involves different devices, different manufacturers, and different data output formats.
Without a unified data strategy designed around the protocol from the outset, the data from these three streams is rarely structured for submission.
Common failure points include:
Inconsistent device calibration records
Proprietary data formats that require manual transformation
Missing audit trails that don’t satisfy national or international regulatory requirements
Outputs that require significant reformatting before they can be uploaded to EDC systems
The problem is compounded when device supply is handled separately from data capture. When the device vendor has no connection to the data management team, critical decisions about data format, audit trail requirements, and EDC compatibility get made too late or not at all.
Regulatory Stakes Are Higher
Blood pressure is one of the most scrutinised endpoints in cardiovascular, renal, and metabolic trials. Regulators expect clean, traceable, tamper-evident data. FDA 21 CFR Part 11 and EU Annex 11 set clear expectations around electronic records and signatures. Any gaps in your audit trail – from a device that doesn’t record timestamps correctly, or a data pipeline that introduces transcription errors – can trigger queries, delay submissions, or require costly re-adjudication.
When BP data comes from multiple, poorly integrated sources, the likelihood of audit trail gaps increases substantially. Each manual touchpoint in your data pipeline is a potential point of failure, and regulators are increasingly focused on the integrity of remotely collected data.
Sponsors who treat BP data capture as a logistics problem and not a data integrity problem often only discover the true cost at database lock stage.
What a Well Integrated BP Data Utility Looks Like
The solution to BP data fragmentation in decentralised trials is not to choose between measurement modalities — it’s to work with a partner who has built a unified data infrastructure around all three, customised to your protocol.
Properly integrated BP data infrastructure covers the full chain: protocol-specific device configuration, device supply and logistics, and direct device-to-database capture that eliminates manual data entry and the errors that come with it. Every reading, regardless of whether it was taken at home or during a site visit, should flow through a single validated pipeline into your EDC in a format that requires no further transformation.
Critically, that pipeline needs to be fully compliant with FDA 21 CFR Part 11 and EU Annex 11 from the point of capture, not retrofitted at the submission stage. Data should arrive in your EDC of choice ready for submission, with complete audit trails and electronic signatures intact.
Protocol Customisation at the Core
One of the most common mistakes made is treating BP data capture as a commodity service. In reality, the configuration of devices and data flows requires tailoring to the specific requirements of each protocol. The measurement schedule, the averaging rules, the regional regulatory requirements, and the EDC architecture all influence how data should be structured at the point of capture.
A BP data service that starts from a generic template and adjusts at the end will almost always introduce fragmentation. One that starts with your protocol and builds the data architecture around it will not.
This is particularly important in multi-regional trials, where the same protocol may need to accommodate different device availability, standard-of-care practices for office measurements, and local regulatory expectations, all while producing a unified, consistent dataset.
Questions to Ask When Evaluating a BP Monitoring Partner
Before appointing a BP data service provider for your next DCT, it’s worth pressure-testing their offering against a few key criteria.
If the answer to any of these is no or uncertain, the risk of data fragmentation exists, and it could appear at the worst possible time.
Conclusion
BP data fragmentation in decentralised trials is a solvable problem, but solving it requires thinking about data integrity, regulatory compliance, and protocol customisation from the very beginning.
Sponsors and CROs who invest in a properly integrated, protocol-specific BP data services will see the return in cleaner data, faster database locks, fewer regulatory queries, and greater confidence at submission. Those who don’t will continue to spend time and budget reconciling data that should never have been fragmented in the first place.
Looking to eliminate BP data fragmentation from your next decentralised trial? Our blood pressure data services are built around your protocol — covering device supply, device-to-database capture for home, office and ABPM monitoring, and full compliance with FDA 21 CFR Part 11, EU Annex 11, and ISO 9001:2015. Contact us to find out how we support sponsors and CROs from study start-up through to database lock.
