# 3.1 High level of Authority of Data User

LEMONCHAIN ecosystem is composed of mobile device user, diversified healthcare devices and app, hospital and EMR companies, etc. User has the authority to utilize the data and will decide whether to save, access and transmit to other institute.

If the user measures one’s biodata through healthcare devices and app, they will be saved in and managed by LEMONCHAIN ecosystem. If the user consents, diversified services within the LEMONCHAIN ecosystem will be linked with the EMR of hospital and user’s biodata. Measured healthcare data and information are saved in the mobile devices of the user first before being saved in cloud upon consent by the user. Health data saved in the specific app installed in the user’s mobile devices can also be accessed with the consent of the user. LEMONCHAIN ecosystem adopts \[1]Opt-Out format in principle and the format of automatic linkage between hospital system and patient’s data with disclosing of the intent of the patient to refuse the utilization of the data thereafter is also scheduled to be utilized.

{% hint style="info" %}
\[1]Opt-Out: Processing information without prior consent of individuals and stopping the use of information if the subject of information expresses his/her intention to refuse the use of the information afterwards
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://lemonchain.gitbook.io/lemonchain_whitepaper_v1.9_eng/whitepaper/3.-lemonchain-new-healthcare-data-ecosystem/3.1-high-level-of-authority-of-data-user.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.