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.2 Rigorous Management Standards for Services Participating in Ecosystem

Services participating in the ecosystem will be subjected to significant financial penalties if they fail to appropriately protect the personal information, violate requirements notified, specific order related to consent, responsibilities of data controller and processor, and need for data protection evaluation, etc. In addition, approval of the patient (Opt-In[1] format) for the ‘personal information requiring considerations’[2] including the medical data is a requisite in principle, and Opt-Out format of providing personal information to 3rd party without clear awareness of the patient is not acknowledged.

Business operator tasked with anonymization of medical information will be limited to corporations who can satisfy prescribed standards including securing of high level of information security and holding of sufficient anonymization processing technology as well as capable of appropriately and definitively execute anonymization for the management and utilization of medical information. Consigned business operator to handle medical information is limited to corporation capable of appropriately and definitively prevent disclosure and damaging of anonymized medical information and execute measures necessary for safe management of other corresponding (anonymized) medical information for participation in the provision of services within the ecosystem.

[2] Personal information needing considerations: Information with concerns for occurrence of discrimination, prejudice and disadvantages in accordance with race, social status and past medical history, etc.

[1] Opt-In: Format of processing information in accordance with consent of individual in advance

Previous3.1 High level of Authority of Data UserNext3.3 Disclosure of transparent data management standards

Last updated 2 years ago

đŸ“–