LEMONCHAIN_ENG
WhitePaper
  • LEMONCHAIN Introduction
  • LEMONCHAIN Feature
  • HBN (Healthcare Blockchain Network)
  • 📖WhitePaper
    • 1. Abstract
    • 2. Introduction
      • 2.1 Current status of Smart Healthcare Ecosystem
      • 2.2 Importance of Smart Healthcare Ecosystem
      • 2.3 Role of Healthcare Data
      • 2.4 Mission of LEMONCHAIN team
    • 3. LEMONCHAIN, New Healthcare Data Ecosystem
      • 3.1 High level of Authority of Data User
      • 3.2 Rigorous Management Standards for Services Participating in Ecosystem
      • 3.3 Disclosure of transparent data management standards
      • 3.4 Decentralized Blockchain Ecosystem Structure
      • 3.5 Incentives for wellness
      • 3.6 Healthcare Big data statistics & search service
      • 3.7 HBN (HealthCare Blockchain Network)
    • 4. Technical details of LEMONCHAIN
      • 4.1 1st layer: Data accumulation
      • 4.2 2nd layer: Data inquiry
      • 4.3 3rd layer: Data utilization
    • 5. LEMONCHAIN, business flow
      • 5.1 Provision of complete decentralized healthcare service
      • 5.2 Data upload
      • 5.3 Settlement of account
      • 5.4 Making payment
      • 5.5 Data marketplace
      • 5.6 Guarantee for quantity of healthcare services that can be provided according to staking
      • 5.7 Mediation of disputes
      • 5.8 Fees
      • 5.9 Additional business operator
        • 5.9.1 Information business operator
        • 5.9.2 Settlement of account business operator
        • 5.9.3 Insurance business operator
    • 6. Future of LEMONCHAIN ecosystem
      • 6.1 Employment of LECO format for the ‘Healthcare data & service’
      • 6.2 Application of DeFi system
        • 6.2.1 Automated Market Maker (AMM)
        • 6.2.2 Lending protocols: Healthcare data-based loan-deposit margin model
        • 6.2.3 Synthetic assets: Issuance of token that follows price of specific asset
        • 6.2.4 Service for trading of divided ownership of healthcare data NFT
    • 7. Token model
      • 7.1 Overview of LEMC token
      • 7.2 LEMC token Pool
      • 7.3 Token Allocation
    • 8. Road Map
    • 9. Timeline
    • 10. Miscellaneous (legal issues to be notified, etc.)
Powered by GitBook
On this page
  1. WhitePaper
  2. 3. LEMONCHAIN, New Healthcare Data Ecosystem

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.

[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

Previous3. LEMONCHAIN, New Healthcare Data EcosystemNext3.2 Rigorous Management Standards for Services Participating in Ecosystem

Last updated 2 years ago

📖