Why promising concepts have not translated into practical implementation? Lessons Learned.
Several peer-reviewed papers proposed that eligibility criteria, visit schedules, consent states, and even payments could be encoded into blockchain logic, transforming the protocol from a static document into an executable system. Early reviews and conceptual frameworks in the clinical research literature explored this “protocol-as-code” vision, often highlighting transparency, immutability, and automation as advantages. However, systematic reviews published between 2017 and 2025 consistently conclude that these proposals remain theoretical, with no production-grade implementations beyond limited pilots. The primary reason is not that protocols cannot be encoded. Clinical protocols are already implemented across CTMS, EDC, IRT, TMF, and financial systems, but that no single executable artifact can simultaneously function as operational logic and as the authoritative regulatory object of record. Clinical protocols are interpretative, exception-driven, and continuously amended, rather than closed, binary rule sets.
A closely related proposal framed the patient as a smart contract: a programmable entity capable of granting and revoking consent, triggering data access, and enforcing protocol-defined interactions. Peer-reviewed work on patient-centric blockchain architectures acknowledges that consent lifecycle management and auditability are genuine strengths of distributed ledgers. However, these same studies also identify a fundamental mismatch between patient behavior and smart-contract assumptions. Consent in clinical research is contextual, reversible, and ethically protected; it is not a deterministic state machine.
Another recurring obstacle identified in the literature is governance. Some authors suggested that blockchain-based governance mechanisms could manage protocol amendments through voting, versioning, and immutable audit trails. While technically feasible, peer-reviewed analyses of blockchain governance in healthcare consistently note that regulatory systems do not recognize collective or token-weighted decisions as valid authorization. Clinical protocol amendments require named legal responsibility, documented rationale, and regulator-specific approval workflows.
Across the peer-reviewed literature, a clear consensus has emerged: blockchain does not fail because clinical trial automation is impossible, but because the problem is mischaracterized. Clinical trials are governed processes, not autonomous systems. They depend on accountable interpretation, contextual decision-making, and reversible control. Properties that conflict with immutable execution models. As recent reviews conclude, the elements that did survive blockchain experimentation are version control, audit trails, and consent traceability. These have been absorbed into traditional clinical systems such as TMF platforms, rule engines, and event-based logging, without requiring distributed ledgers. In this sense, the “protocol as smart contract” vision was not rejected outright; it was reframed into architectures that prioritize governance over automation, explanation over execution, and responsibility over consensus.
The mismatch between clinical trial requirements and blockchain capabilities becomes clearer when protocol needs are examined side by side with what distributed ledgers actually provide.
| Clinical protocol need | Why it matters | What blockchain offers | Why it doesn’t map cleanly |
|---|---|---|---|
| Patient safety & clinical judgment | Trials require exceptions, overrides, and context-aware decisions to protect participants. | Deterministic rule execution (smart contracts). | Clinical decisions are interpretative; rigid execution can’t justify or safely handle deviations. |
| Accountability & legal responsibility | Audits need named entities responsible for decisions, not “the network”. | Shared governance logs, multi-party approval traces. | Governance records don’t replace formal authorization and personal/organizational accountability. |
| Protocol amendments & controlled rollout | Amendments must be justified, approved, versioned, and implemented consistently across sites. | Versioning + immutable change history. | The hard part is operational alignment (who switches when) and rationale, not just version history. |
| Informed consent (ethics & GDPR) | Consent is contextual, revocable, and ethically protected; withdrawal must be frictionless. | Tamper-evident consent trail; permission checkpoints. | Consent is not a simple on/off state; automation risks oversimplifying vulnerability and voluntariness. |
| Data protection (GDPR: correction/erasure) | Records may require correction; personal data has lifecycle rights and retention constraints. | Append-only immutability and timestamping. | Immutability conflicts with correction/erasure; off-chain workarounds reduce the value proposition. |
| Audit readiness & TMF completeness | Auditors assess documentary evidence, rationale, completeness, and inspection readiness over time. | Cryptographic proof that events occurred; immutable logs. | Audits focus on “why” and “is it complete/fit-for-purpose”; the TMF remains the authoritative governance layer. |
Viewed from a clinical operations and audit perspective, the failure of “protocol-as-smart-contract” proposals is not a failure of technology but of framing. Peer-reviewed literature increasingly converges on the observation that clinical trials are governed knowledge systems rather than executable machines. What regulators ultimately inspect is not automated execution, but documented intent, justified deviation, and accountable decision-making over time. In practice, the elements blockchain research attempted to formalize, e.g. immutability, traceability, version lineage, and consent history, are already native requirements of the Trial Master File. Rather than executing protocols on-chain, contemporary clinical systems increasingly treat the TMF as the authoritative governance layer: where protocol versions, amendments, approvals, deviations, and rationale are coherently documented and audit-ready. In this sense, blockchain did not point toward automated trials, but indirectly reinforced why clinical research governance remains document-driven, interpretation-centric, and anchored in accountable human oversight.
Agbo, C. C., Mahmoud, Q. H., & Eklund, J. M. (2019). Blockchain technology in healthcare: A systematic review. Journal of Medical Internet Research, 21(2), e12439. https://doi.org/10.2196/12439
Casino, F., Dasaklis, T. K., & Patsakis, C. (2019). A systematic literature review of blockchain-based applications: Current status, classification and open issues. Telematics and Informatics, 36, 55–81. https://doi.org/10.1016/j.tele.2018.11.006, https://www.sciencedirect.com/science/article/pii/S0736585318306324
Kuo, T. T., Kim, H. E., & Ohno-Machado, L. (2017). Blockchain distributed ledger technologies for biomedical and health care applications. Journal of the American Medical Informatics Association, 24(6), 1211–1220. https://doi.org/10.1093/jamia/ocx068, https://academic.oup.com/jamia/article/24/6/1211/4108087
Mettler, M. (2016). Blockchain technology in healthcare: The revolution starts here. 2016 IEEE 18th International Conference on e-Health Networking, Applications and Services (Healthcom), 1–3. https://doi.org/10.1109/HealthCom.2016.7749510, https://ieeexplore.ieee.org/document/7749510
Zhang, P., Schmidt, D. C., White, J., & Lenz, G. (2018). Blockchain technology use cases in healthcare. Advances in Computers, 111, 1–41. https://doi.org/10.1016/bs.adcom.2018.03.006, https://www.sciencedirect.com/science/chapter/bookseries/abs/pii/S0065245818300196
Shojaei P, Vlahu-Gjorgievska E, Chow Y-W. Security and Privacy of Technologies in Health Information Systems: A Systematic Literature Review. Computers. 2024; 13(2):41. https://doi.org/10.3390/computers13020041, https://www.mdpi.com/2073-431X/13/2/41
Prior Blockchain post on this blog: https://www.project-owner.com/2025/06/blockchain-in-project-management-and.html
No comments:
Post a Comment