> For the complete documentation index, see [llms.txt](https://mdxl.gitbook.io/mediaccel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mdxl.gitbook.io/mediaccel/2.-problem-definition-and-solutions/2.2-limitations-of-existing-projects.md).

# 2.2 Limitations of Existing Projects

Several blockchain-based projects have sought to address issues in the healthcare data ecosystem but have fallen short in solving fundamental problems. Notable examples include **MediBloc, Medicalchain, and Guardtime Health**. Although each project showcased unique strengths, they encountered various challenges during implementation.

**a. MediBloc**\
MediBloc aimed to enhance data transparency and security using blockchain technology, focusing on a patient-centric healthcare data platform. However, challenges in interoperability and standardization among hospitals significantly limited the platform's effectiveness. Additionally, the complexity of complying with diverse global healthcare regulations hindered its scalability.

**b. Medicalchain**\
Medicalchain developed a blockchain platform enabling patients to securely store and share data with medical institutions and research centers. However, its complex authentication processes and data management structures detracted from user experience, leading to low adoption rates. Furthermore, the platform lacked economic incentives for patients, undermining its ability to foster a sustainable patient-centered ecosystem.

**c. Guardtime Health**\
Guardtime Health successfully implemented blockchain technology to ensure data integrity, notably within Estonia’s e-Health system. Over 99% of the population has complete control of their digital medical records, secured by the Keyless Signature Infrastructure (KSI) blockchain. However, the platform lacked reward systems to encourage broader user participation and faced scalability challenges in adapting to different healthcare systems and regulations globally.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mdxl.gitbook.io/mediaccel/2.-problem-definition-and-solutions/2.2-limitations-of-existing-projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
