Electronic consent is the part of a trial where regulatory rigor and patient experience collide most visibly. The consent form has to be readable on a phone, signed in a way that holds up under FDA inspection, and round-tripped into the trial database with the audit trail intact. The tools that nail all three in 2026 are a short list.
For the broader framing, the complete guide to FHIR form builders for clinical research in 2026 is the right primer if you have not read it.
Medidata iMedidata Consent
Medidata's consent tool has been a default in mid-to-large studies for years and the 2025 release added native FHIR Consent and Questionnaire support. The signature ceremony is mature, the audit trail is inspection-ready, and the multi-language story is the strongest in this list.
The cost is real, and the platform tends to come bundled with the rest of Medidata's stack, which suits sponsors already on it and looks expensive to sponsors who are not.
Medable eConsent
Medable's eConsent module is the strongest fit for decentralized trials, with biometric signature options and a path to in-home witnessing through the same app subjects use for ePRO. The FHIR export is clean, with Consent and QuestionnaireResponse landing in the trial store without manual reshaping.
For decentralized studies this is the safe default. For traditional site-based studies it is more capability than most teams need.
Open Health Hub Consent
Open Health Hub's consent flow plugs into the same patient app that handles PRO and adherence prompts, which keeps the subject experience consistent across the trial. Signature and witness flows are configurable per region, which matters for studies running under both MHRA and FDA scope.
Open Health Hub is a fair pick for sponsors who want a single subject-facing app for the whole trial life cycle.
Castor eConsent
Castor's consent module reuses the same form-definition layer as the rest of Castor, which means consent and CRF live in one protocol object. The integration is the strongest argument for it: amendments propagate cleanly, and the audit trail is consistent across consent and study data.
The renderer is competent rather than polished. For sponsors already on Castor, the integration usually outweighs the polish gap.
Custom Build on LHC-Forms with a Signature Layer
The fifth option is a custom build: LHC-Forms for rendering, a signature layer the sponsor owns, and a Consent resource generated at completion. A few research-heavy sponsors run this stack because they want full control over the consent experience and the validation pack.
The investment is real engineering ownership, but the resulting platform reuses across studies and avoids per-study licensing math.
How to Decide
The decisive question for eConsent is whether your studies are decentralized, traditional, or mixed. Decentralized leans toward Medable. Traditional with a Medidata footprint leans toward iMedidata. Castor and Open Health Hub fit the mixed case. The custom build is for sponsors who want the consent layer to be a long-term internal asset.
For the adjacent question of subject-side ePRO, the top 7 FHIR Questionnaire tools for ePRO collection is the natural next read. For the decentralized-trial tooling more broadly, top 4 FHIR form tools for decentralized clinical trials is the right one. And for more on FHIR for healthcare teams across the rest of the stack, the homepage is the entry point.
Sources
- Final Guidance on Conducting Clinical Trials with Decentralized Elements (regulatory primary) - Federal Register, FDA Sept 2024
- FDA DCT Guidance analysis (industry interpretation of regulatory shift) - Clinical Ink 2024
- Audit Trails and Transparency, Tracking Changes in Clinical Data (industry blog, 21 CFR Part 11 alignment) - OpenClinica