planning for components

Planing for components

Entities

Data Subject
Trusted By DS: YES

Role:

• Provides data for the system

Actions:

• Registers with a broker.
  • Create polcies on broker
• Sells data to data consumer.
• Registers with data custodian.

Are:

• Normal people

Data Consumer
Trusted By DS: NO

Role:

• Funds the system
• Run blockchain nodes

Actions:

• Buys data from data subjects via a broker.
• Registers with broker.

Are:

• Researchers
• Private researchers

Data Custodian
Trusted By DS: YES

Role:

• Holds the data subjects data.
• distributes data subjects data to data consumers via a broker.

Actions:

• Has users register with it.
• Distributes Data.
• Stores Data.

Are:

• Fit bit
• Cloud

Broker
Trusted By DS: PARTIAL

Role:

• Connects a data consumer to a data subject.
• Hides the data subject from the data consumer.
• Connects the data consumer and the data custodian.
• Stores meta data on data subjects.
• Anonymise data

Actions:

• Has users register with it.

Knowledge Areas

These are knowledge areas where we will need a team member(s) to understand.

Matchmaking

User Management

Why: The Broker will need to contact Data Subjects, Data Custodians and Data Consumers. In order to get permission from the data subject to sell their data; Get the data from the Data Custodian and transfer the data to the data consumer. What:

• We need someone who understands how to create a user registration process.
• Crete front end for people to register.
• TBD: User accounts what standards are necessary.

Data polices

Why: Brokers need data polices so they can fulfill to the data subjects privacy requirements. What:

• Front end policy creation screen Eg: Google's privacy screen.
• Policy storage
• Policy evaluation
• Having policy interactions via smart contract

Order Processing

Why: data subjects need compensation from the data consumer. When their data is bought. What:

• Crypto payment via smart contract
• Payments from Data consumer to broker.

Components

Policy

Fields

• Id
• Where to access data
• Metadata for searching
• Conditions
  • Who can buy
• Price

Data Anonymizer

Inputs:

• List of Medical Data.

Outputs:

• List of Medical data.

Requirements:

• Be able to receive

Data Broker Output API

Inputs:

• List of Medical data.

Outputs:

• interface for data consumer to fetch data.

Data Broker data fetcher

Inputs

• Where to access data.

Outputs:

• Medical data.

Planning

This section is where spike reports can be found.

Spike Reports to Plan

• Data Gathering

  • What Devices we have access too
  • How much data is on chain vs off
  • What data we can even pull from devices
  • What format do we output to researchers (it's just CSV right?)
  • How much off chain infrastructure do we even need

• Organisation/Researcher Registration system

• Researcher Search for clinical trial

  • Find patients with X criteria
  • All patients are anonymised

• Researcher patients contact

  • Send a request to patients to share their data
  • Can attach a bounty to the data request eg x amount of fake internet money per 1000
  • After Request is received by patient the bounty is paid into their account