1. background and objectives · differences in system requirements among fields and themes. the...

1

1. Background and Objectives In FY2016, the Ministry of Economy, Trade and Industry (METI), Japan, conducted a survey in order address

excessive expectations and misunderstandings concerning blockchain-based systems. This includes formulating system evaluation forms for evaluating centralized systems and a blockchain-based system (*1).

At the same time, the need to conduct further study on “Evaluation Forms for Blockchain-Based System ver.1.0 (System Evaluation Forms)” and to address the legal and technical issues toward social implementation of a blockchain-based system was pointed out.

In this study, the following three action items were undertaken in order to contribute to the promotion of social implementation of a distributed system, such as a blockchain-based system.

Issue

Target

An example of the evaluation method (measurement method, etc.), which may differ depending on use cases and verification of completeness, is required in order to promote implementation of the system evaluation forms

Social implementation may be hindered because the distributed technology has not yet been considered by law• Social implementation may be hindered

by existing regulations and systems• Utilization may be delayed because legal

application is unclear

It is necessary to understand the maturity of core technologies required to build a system implementing blockchain and clarify issues and status (resolved or not) of this system

Select individual use cases and perform system evaluation for each case using the system evaluation forms

① Selecting system evaluation target② Materializing use cases③ Designing system configuration④ System evaluation

Clarify legal interpretation, consider deregulation and discuss institutional design

① Study of legal issues related to themes common to use cases such as smart contracts

② Study of different legal issues for each case

Study of core technology necessary forservice development and its maturity

Clarification with evaluation items of system evaluation forms using blockchain technology (1. Performance efficiency, 2. Maintenance/operability, 3. Security)

System assessmentusing evaluation forms Examining the legal issues Identifying core technologies

required for service development

Promote social implementation of distributed system*1: METI, Survey Report on Establishing Evaluation Forms for Blockchain-Based System, March 29, 2017

Evaluation Forms for Blockchain-Based System ver.1.0Evaluation Items

2

2.1. Policy: System evaluation using System Evaluation Forms For system evaluation, select use cases and evaluate each of them.

In order to examine the evaluation results (whether they satisfy needs, etc.), we defined system requirements, materialized evaluation items and performed desk checking based on system configuration.

• Materialize use cases by talking to companies that have been taking advanced approaches (venture capital, etc.).

Designing system

configuration

System evaluation

• Talk to companies that consider using the above cases to determine system requirements and design system configuration that are the premise of evaluation

• Specify the evaluation items of the system evaluation forms based on the system requirements

• Perform desk checking based on the specified evaluation items

• Examine evaluation results and consider whether blockchain technology can be implemented

Selecting system evaluation target

• From the perspective of study status forsocial implementation of blockchainsystems in fields where utilization of blockchain technology is expected, we selected fields and use cases that are subject to system evaluation

Procedure for System Evaluation

Quality

Performance efficiency

Processing performance (throughput)Network performance

Block determination performanceReference performance

Interoperability Interoperability (existing system)Interoperability (other blockchain)

ScalabilityProcessing performance improvementNetwork performance improvement

Capacity expandabilityNumber of nodes expandability

ReliabilityMaturity

AvailabilityFault tolerance

Resilience

SecurityConfidentiality

IntegrityNonrepudiation

AuthenticityPortability Adaptability

Exchangeability

Maintenance/operability


ModularityReusability

AnalyzabilityCorrectability

Testability

Costs

Research and Development

Blockchain infrastructureSubsystem

ImplementationHardwareSoftware

System implementationMaintenance and

operationOperation

MaintenanceNeed to be specified based on the system requirements

to examine evaluation results

Materializing use cases

Stud

y fo

r ea

ch ta

rget

3

2.2. Selection of System Evaluation Targets We selected fields and use cases for system evaluation from perspectives that study status toward social

implementation of blockchain systems in fields where the utilization of blockchain technology is expected and differences in system requirements among fields and themes.

The following shall be the targets of system evaluation: the fields “Medical/Healthcare” and “Logistics/Supply chain/Mobility, etc.” for which implementation of blockchain technology has been considered in Japan and globally; use cases for “smart property,” which is thought to be utilized in other countries and is expected to be used in Japan in the future.

Field* Characteristics Advantages Practical use examples

Promisingfields

Medical/Healthcare/Nursing care

• Sensitive data is dealt with.• Huge impact is expected in event

of unexpected data falsification.• Immutability of data

• Clinical trial data management platform

• Medical record sharing system

Logistics/Supply chain/Mobility, etc.

• Data can be falsified due to complex relationship among various stakeholders.

• Tampering can be prevented while many stakeholders are involved.

• Traceability in manufacturing• Traceability in the food industry

Cross-sectionalthemes in

fieldswhere

utilizationis

expected

IoT

• Use of communication terminals and transactions is expected to surge in the future.

• Secure environment is crucial.

• Direct transaction between devices

• Immutability of access permissions

• M to M small-scale transaction• IoT device management/access

control

Smart Property• Enhancement of property rights,

activation of commerce is expected.

• Promotion of distribution through tokenization of property rights

• Low-cost property rights where centralized databases areunnecessary

• Profit sharing and agreement management of contents

• Transaction of immovable property rights

• Data circulation platform

Sharing Economy • Realization of transparent sharing economy is expected.

• Elimination of arbitrary operation of platformers with decentralized service driven by prosumers

• Private accommodation (minpaku), ridesharing, car sharing

*NOTE: These are representative fields for blockchain technology utilization. Scope of system evaluation

6

2.3. System EvaluationClinical Trial Data Management System (Medical/Healthcare)

*1: METI, Survey Report on Establishing Evaluation Forms for Blockchain-Based System, March 29, 2017*2: IBM, Hyperledger Fabric: A Distributed Operating System for Permissioned Blockchains, (https://arxiv.org/pdf/1801.10228v1.pdf)

Evaluation items Results (Desk study)

Quality


Processing capacity A yearly average of 600 cases of clinical trial data can be processed.

According to the benchmark results of Hyperledger fabric (*2), more than 1,000 throughputs per second can be performed.

Block finality efficiency

Data becomes referable within 30 seconds after registration.

This can be realized as in Hyperledger Fabric , configuration of the block creation period (required least seconds before new block creation after transaction) is available. (The default value is 2 seconds)

Inter-operability

Interoperability(with conventional

systems)

Interconnection with conventional electronic certificate infrastructure including HPKI is secured.

Interconnection can be realized by distributing public key certification to each server.

Expandability Scalability to add nodes

Nodes can be added. Establishing of Blockchain networks per pharma company gives scalability to add new nodes.Maximum number of nodes in a network should be determined by performance evaluation. (Specification of servers should be reviewedas the performance issues of the nodes in PDMA or medical institutions involved in multiple networks could be a bottleneck.)

Reliability Availability No service disruption is required in the event of system troubles of participant companies.

Hyperledger Fabric causes no service disruptions as long as the nodes that meet the preliminarily set approval policy are working. For example, if the system is set to require approvals from all of the three groups - PDMA, pharma companies/CRO, medical institutes/SOM - for any data change, no service disruptions will occur due to problems with a single node.

Security Confidentiality Data can be kept confidential(but not required for this system).

Data confidentiality can be maintained by hashing or encrypting the data.NOTE: Hashing requires separately sharing original data among stakeholders.Encryption requires sharing the decryption key among stakeholders.

Integrity Equipped with membership management function

Hyperledger Fabric can manage separately contract administrators and users.

Non-repudiation function

Authenticity

Data cannot be falsified. In Hyperledger Fabric, data cannot be falsified since the data with approvers’ signatures is shared by all of the nodes. (In other words, modification of data requires all approvers’ signatures.)

Operation & Maintenance

Operability/maintainability

Maintainability Maintenance can be performed without service disruptions.

In Hyperledger Fabric, contract codes can be modified during operation of the service.

We created evaluation items from the System Evaluation Forms(*1) based on the system configuration of clinical trial data management, and conducted desk checking.

9

2.4. System EvaluationEV Battery Life Cycle Management (Logistics/Supply chain/Mobility, etc.)

*1: METI, Survey Report on Establishing Evaluation Forms for Blockchain-Based System, March 29, 2017*2: IBM, Hyperledger Fabric: A Distributed Operating System for Permissioned Blockchains, (https://arxiv.org/pdf/1801.10228v1.pdf)

Evaluation items Results (Desk study)

Quality


Processing capacity At least 1KB of residual value per day out of 100 thousands cars can be processed (1.16 case/sec)

According to the benchmark results of Hyperledger Fabric (Reference 2), more than 1,000 throughputs per second can be performed.

Block finality efficiency Data becomes referable within 30 seconds after registration.

This can be realized because in Hyperledger Fabric, configuration of the block creation period (least required seconds before new block creation after transaction) is available. (The default value is 2 seconds.)

Inter-operability

Interoperability(with conventional

systems)

The system can cooperate with IoT edge servers.

Interactive cooperation can be established by connecting Edge servers as clients and entering data into them.

Expandability Scalability to add nodes

Nodes can be added. Establishing of blockchain networks per EV manufacturer gives scalability to add new nodes. The maximum number of nodes in a network should be determined by performance evaluation.(Specification of servers should be reviewed as the performance issues of the nodes involved in multiple networks could be a bottleneck.)

Reliability Availability No service disruption is required in the event of system troubles of participant companies.

Hyperledger Fabric makes no service disruptions as long as the nodes that meet the preliminarily set approval policy are working. For example, if the system is set to require approvals from three or more companies for any data change, no service disruptions will occur due to problems with a single node.

Security Confidentiality Data can be kept confidential (but not required for this system).

Data confidentiality can be maintained by hashing or encrypting the data.NOTE: Hashing requires separately sharing original data among stakeholders.Encryption requires sharing the decryption key among stakeholders.


Hyperledger Fabric can manage separately contract administrators and users.

Non-repudiation function/Authenticity

Data cannot be falsified. In Hyperledger Fabric, data cannot be falsified since the data with approvers’ signatures is shared by all of the nodes. (In other words, modification of data requires all approvers’ signatures. )

Operation & Maintenance

Operability/maintainability

Maintainability Maintenance can be performed without service disruptions.

In Hyperledger Fabric, contract codes can be modified during operation of the service.

We created evaluation items from the System Evaluation Forms(*1) based on the system configuration of the EVbattery management system and conducted desk checking.

12

2.5. System EvaluationSmart Token Platform (Smart Property)

*1: METI, Survey Report on Establishing Evaluation Forms for Blockchain-Based System, March 29, 2017

Evaluation item (Theoretical) Evaluation results

Quality


Processing performance Having processing performance of seven cases per second, which is the maximum throughput of Bitcoin

It can be realized because Ethereum's production network can process a higher number of transactions than Bitcoin.

Block determination performance

Has the same deterministic performance as Bitcoin

Since Ethereum's consensus method is PoW (Proof of Work), same as Bitcoin, the same definite performance can be achieved. (However, although the block generation interval is about 10 seconds, which is short compared to Bitcoin's 10 minutes, it is necessary to decide among traders how many blocks are to be regarded as determined)

Inter-operability

Interoperability (existing systems)

Able to cooperate with IoT system The IoT infrastructure becomes a client of Ethereum and it can cooperate by registering data.

Scalability Scalability of the number of nodes

Able to add nodes(Not a requirement of this system)

Depends on the scalability of Ethereum because it uses Ethereum production network operated as cryptocurrency.

Reliability Availability Services are not stopped by a single failure Depends on the availability of Ethereum because it uses Ethereum production network operated as cryptocurrency.(As long as Ethereum does not stop the service, this system will not stop the service either.)

Security Confidentiality Data can be concealed(Not a requirement of this system)

Data can be concealed by hashing and encrypting.In the event of hashing, however, it is necessary to separately share the original data among stakeholders.In the event of encryption, it is necessary to separately share the decryption key among stakeholders.


The contract manager and the user can be managed separately.

Nonrepudiation, authenticity

Difficult to falsify data It is difficult to alter the data because it is shared by all nodes of the Ethereum production network.

Maintenance/operations


Correctability Able to modify the system without stopping the service

For Ethereum, contract codes can be modified while the service is running

We created evaluation items from the System Evaluation Forms(*1) based on the system configuration of token management system and conducted desk checking.

3.2. Study of Legal Issues (Cross-cutting Themes) Through interviews with experts, the study group identified the following legal issues: 1) Legality of issuing of records via

blockchain when issuing via e-mail or cloud is permitted by the law where delivery by electromagnetic documents is legal; 2) Effectiveness of smart contract; 3) Effectiveness of transfer of rights caused by the transfer of tokens. Since these are legal issues applicable to various use cases, they were discussed as cross-cutting themes.

Some people have expressed the opinion that the issuing of electromagnetic records is highly likely to be implemented legally

On the other hand, since smart contracts written in machine language do not have reproducibility depending on the adopted blockchain infrastructure, practical efforts such as storing of evidence are required. Furthermore, concerning the effectiveness of transfer of tokens, it was pointed out that the right recorded on the blockchain and the right of the person actually holding the right may not be protected.

Item Issue Examples of findings by study group members

Legality of issuing of

electromagnetic records using

blockchain

When delivery by electromagnetic documents is permitted by law, is the issuing of records via blockchain accepted when e-mail or cloud are recognized as specific methods of delivery?

Since most cases can be regarded as the same as cloud, it is highly probable that issuing by electromagnetic recording using blockchain can be done legally.

Effectiveness of smart contract

Establishment of contract

Is conclusion of a contract as a smart contract effective?

In principle, the contract is effective if both parties agree. However, for smart contracts that are written in machine language and are automatically executed, preliminary consensus among the relevant parties including understanding of its structure are necessary for the contract to be effective.

EvidenceWhat kind of evidential force do smart contracts have in the event of a conflict?

There are few lawsuits where formal evidential capability is an issue and therefore formal evidential force is not likely to be an obstacle to social implementation. However, when the author of the document matters, since the estimation of authenticity (so-called two-stage estimation) of the document does not work where the electronic signature that satisfies requirements of the electronic signature law is not used much, there remains risk for blockchain users.In addition, it may be necessary to have an interface whose record third parties can understand because unreadable contracts are not sufficient as substantial evidence.Also, even if a contract code is stored and executed when a dispute occurs, the same execution results may not be obtained in some cases depending on the platform of the implemented blockchain. Therefore, practical measures such as saving the execution results at the time of concluding a contract may be required.

Effectiveness of transfer of rights due to the transfer of token

Is it acceptable as a legitimate right if you transfer property rights and credits of movables and real estate by including them in tokens?

The transfer is effective based on the conformity of the parties‘ intention to manifest with some exceptions. However, with respect to the transfer of the right that requires competing requirements under the law, even if the right is recorded on the token, the acquisition of the right in the case of double assignment or bankruptcy cannot be opposed if it does not satisfy an opposing requirement such as registration outside the blockchain.

14

15

≪Reference≫ Recommended Efforts for Smart Contract In the study group, it was pointed out that legal risks can be reduced by developing a practical policy so that social

implementation can be promoted.

Especially for smart contracts, we discussed ideal practical policies. We thought that we had better explain the mechanism, promote the understanding of users, record and keep evidence, etc. in order to increase the effectiveness of smart contract conclusion and evidential force when a dispute arises. When using it globally, it is also necessary to consider the applicable laws.

Large category Small category Recommended efforts Note

Building a user-friendly system • It is recommended that the contract contents for consumer interface be readable in natural language.

Develop provisions for the system

Terms and conditions

• It is recommended to clearly state that smart contract is used and the contract details, and to get consent from the user in advance.

Applicable law • When building a system for which nodes exist dispersedly around the world, there is a risk when selecting an applicable law.

• It is important to specify the law of the appropriate country as the applicable law while considering laws and regulations of other countries

For example, it is said that Japanese law is flexible regarding contract conclusion and evidential force for smart contracts.

• From the perspective of how to settle disputes, keep in mind that the judgment of the Tokyo District Court can hardly be enforced in Asia.

• In that case, it is necessary to arbitrate based on agreements concerning arbitration obtained beforehand or to conduct a trial at courts located in the country or state where the defendant is located.

Record and store evidence • For non-deterministic code(*), it is effective to store the evidence of execution results when necessary.

One method could be: Compile and execute the source code, hash the results and record them on the blockchain.

However, when blockchain is used in small transactions, strict acquisition and storage of evidence may not be cost effective.

We may warn the consumer that the evidence of only the codes is inadequate and advise them to use it on their own responsibility depending on the transaction.

• The determinability of the execution results differs depending on the blockchain infrastructure.

(*Note) This is a code for calculation based on the information dependent on the execution environment such as server time and randomnumber generated by the server, and the execution results may differ.

18

4.1. Technical Issues related to Distributed Systems Compared to centralized systems, distributed systems such as Blockchain-based systems generally have the issues shown

below regarding performance efficiency, maintenance/operability, and security. We conducted the survey on the details of technology and implementation propriety (development situation) with regard to

core technologies to solve the problems related to performance efficiency, maintenance/operability, and security.

Item Technical issues of Blockchain-based systems Issue summary


Speeding up(Transaction throughput)

Since processing is performed while forming agreements among distributed nodes, the processing speed is generally low.

Size of ledger data With the increase in transactions, the amount of ledger data has increased and the storage runs out of space. The data of a node administrator can be destroyed.


Ease and confidentialityBlockchain is a new technology and the use of virtualization technology is effective for frequent runtime deployment required by software update, but data confidentiality also needs to be considered because the data in virtual machines and containers is visible from hosts.

Operational continuity when the system becomes vulnerable

Blockchains may suddenly be weakened due to the compromise of encryption technologies and reduced motivation of node administrators. Preparation for lowering reliability and availability is necessary in order to realize stable operation continuity.

Development and operation of smart contract

Since contract details are written in programming languages in smart contracts, it is difficult for people other than experts to understand the content. In addition, it is necessary to protect the program from bugs and vulnerabilities and to prevent rewriting of programs not noticed by stakeholders.

Security

Privacy protection (confidentiality) For use cases dealing with personal information and confidential information, it is necessary to protect the privacy of the data in the ledger.

ID management of node administrator, access control

For non-centrally built blockchains without a specific node to trust, it is difficult to discover other reliable nodes when a new node joins.

Key managementWhen giving an electronic signature using a secret key to guarantee the validity of written data, spoofing can be performed if the secret key is stolen. Therefore, it is necessary to take measures against loss of thekey or hacking.

Personal data managementWhen individual identity information is centrally managed by specific organizations, the use of the identity information may be restricted intentionally by such organizations. Decentralized identity management is required.

Collateral for reliability of input data Blockchain is tamper- or denial-resistant for data in the ledger, but the correctness of the registered data is not guaranteed. It is necessary to ensure the reliability of the data before it is registered in the ledger.

19

4.2. Technical issues: Performance Efficiency As technologies to solve issues related to performance efficiency, technologies for processing and storing data

outside blockchain, and concurrent processing with multiple nodes are studied and developed.

There is a better outlook on a solution for issues with the improvement of transaction throughput by executing transactions outside the ledger.

Issue Core technology required for resolution

Developmentstatus

Idea

Stud

y

Impl

em

enta

tio

n

Speeding up(transaction throughput)

Outside ledger transaction In order to suppress the amount of write transactions, execute multiple transactions outside the ledger and record results in a book (Lightning Network or Raiden).

Algorithm improvement Divide nodes into groups and process transactions concurrently in parallel for each group. Record results in the ledger together at the end (sharding).

Utilization of trusted hardwareTrusted hardware is a function to configure secure areas on a memory which some recent general-purpose processors have. In this way, nodes that behave maliciously during consensus building can be detected with fewer communication times and participating nodes so that a faster consensus building algorithm can be configured. (MinBFT, etc.)

Size of ledger data Cooperation with external DB A framework to keep data written in blockchain to a minimum and store the rest in the external DB is necessary.

4.3. Technical issues: Operation and Maintenance Technologies for easy development and improving verification methods are being researched and developed to solve

issues related to operation and maintenance.

Regarding operation and maintenance, however, many issues are unique to blockchain: research and development is only a concept.


Developmentstatus

Idea

Stud

y

Impl

emen

tatio

n

Ease and confidentiality

Easy creation and deployment of execution environment Implementation of virtual machine technology and container technology (Docker, etc.) .

Improve data confidentiality Consideration on how to keep data confidential from the host is required when utilizing virtualization technology.

Operational continuity when

the system becomes

vulnerable

Transferred to other infrastructure during operations

When the main infrastructure is compromised, the operation can be transferred to other infrastructure (such as common API, etc. that absorbs differences in blockchain implementation).

Development and operations of smart

contract

High readability framework Implement a framework that can describe with high readability (a software component that can easily implement typical patterns of business processes according to procedures)

Domain specialized languageUse domain specialized language (a programming language specialized for a specific business field. It can easily describe processing of the target domain compared to general-purpose languages, e.g. Hyperledger Composer, etc.).

Static code check Use static code checking to detect defects by verifying only superficial patterns of the source code.

Vulnerability catalog Utilize documents summarizing typical vulnerabilities (Ethereum Smart Contract Security Best Practices, etc.)

Formal verification Model the program status and introduce methods such as formal verification to confirm that there is no defect in specifications.

Secure open resources library Development of an open source library aiming for high safety (OpenZeppelin, etc.).

Visualization of contract update Do not implement the function to update contract codes on the blockchain infrastructure (Ethereum) Reinstallation is required when the logic needs to be updated. 20

21

4.4. Technical issues: Security As a technology to resolve issues related to security, technologies for utilizing secure hardware and separating

critical information from blockchain, etc. have been studied and developed.

In terms of security, effective solution technology already exists. However, it is pointed out that it is necessary to embed it in system design to promote utilization.


Developmentstatus

Idea

Stud

y

Impl

em

enta

tion

Privacy protection (confidentiality)

Assign roles for each participating node

Divide responsibilities of nodes into two: one is for checking the correctness of data and the other for ensuring the order of data.

Constitute chains only by transaction stakeholders Constitute chains only by the transaction stakeholders.

Utilizing existing encryption protocol

Use zero knowledge proof (to prove that the secret key for a certain public key is known without receiving any information about the secret key) to secure the validity of data without disclosing.

ID management of node administrator,

access control

Public Technology to discover existing nodes when participating in blockchain (e.g. DNS Seed)

Consortium Manage node information using PKI infrastructure, etc.

Key managementProper use depending on the

occasion

Hot wallet (a method for managing secret keys in an environment connected to network all the time. Highly convenient)Cold wallet (a method for managing secret keys in an environment disconnected from a network. Highly secure)

Multiple secret key distribution Implement an electronic signature using two or more secret keys (multisig).

Personal data management

Sharing personal information through the ledger

Personal information is managed by individuals outside the ledger. Share such information with others through the ledger when necessary.

Secure the reliability of the

data registered to the ledger

Linking people, things and data Utilize biometric technology (face, fingerprints etc.), IC tag authentication (RFID etc.), object fingerprint authentication

Prevention of data falsification by IoT device hacking

Utilize Tamper Resistance (technology that destroys its data and make it unrecoverable when someone is attempting to retrieve data such as a private key from the device) and trusted hardware (hardware that provides the ability to protect software from malicious codes).

22

5. Expected Efforts for Social Implementation of Distributed system To promote social implementation of distributed systems such as blockchain-based systems, some study group members

indicate that further legal and technical efforts are necessary.

– In the study group, it was pointed out that review of laws and regulations that are not based on distributed society (e.g. the Electricity Business Act on electric power interchange) and formulation of guidelines for operations of smart contracts will be necessary to address legal issues before talking about blockchain technology in order to promote social implementation.

– Further research and development will be required for technology concerning throughput and maintenance/operability in the future. It is also necessary to promote implementation of technologies including core technology for “security” which is already at the stage of practical use.

Legal efforts

Technical efforts

It is necessary to consider this not only on paper but also how to put a legal system into force after examining the technical feasibility and influence on the stable supply of electric power through demonstration experiments.

Legal interpretation of evidential capability of smart contracts and formulation of guidelines concerning remarks on legal issues in actual operations are required.

It is necessary to study the establishment of a new countermeasure system including a special law on the transfer of property rights and claims set for the registration system at the time of assignment of account receivables

Further discussions on who takes responsibility when there is a defect in the program and community/multiple people participate in development are required for DApps(*) for which responsible entities do not exist

It is necessary to improve performance so that it can withstand actual operation by utilizing off-chain technology and improving the consensus building mechanism.

It is necessary to establish an implementation structure such as privacy protection, key management, linking with real world events and data.

A mechanism is necessary to allow participants and users who do not have programming expertise to understand the contract code written in programming language.

(Note) DApps (Decentralized Applications) is an application built by a non-centralized entity such as a developer community with tokens as a reward, and the application is built without any central management entity.

23

<<Reference>> Study Group of Legal System related to Blockchain

To discuss issues concerning legal system related to blockchain, we established a study group consisting of lawyers/academic experts who have knowledge of blockchain and business persons involved in blockchain.

We held two meetings for each field from November 2017 to March 2018.

Name Institution/organization

Taiki Ishikura

CBOJapanese Organization for Medical Device Development, Inc.

Takafumi Ochiai

LawyerAtsumi & Sakai

Eiji Sasahara

Doctor of Pharmaceuticals, Director, Healthcare Cloud Initiative

Yuzo Kano Japan Blockchain Association

Soichiro Takagi

Research DirectorCenter for Global Communication, International University of Japan

Ikuo Takahashi

LawyerKomazawa Legal Chambers

Takanori Fujita

National Center for Global Health and MedicineBureau of International Health CooperationInstitute for Global Health Policy Research (iGHP)

Masakazu Masujima

LawyerMori Hamada & Matsumoto


Yasuhiko Ogushi

Industry AnalystBlockchainHub Inc.

Takafumi Ochiai


Yuzo Kano Representative DirectorJapan Blockchain Association

Yusuke Shimada

LawyerCity-Yuwa Partners

Soichiro Takagi


Ikuo Takahashi


Masakazu Masujima



Takafumi Ochiai


Yuzo Kano Representative DirectorJapan Blockchain Association

Ken Kawai LawyerAnderson Mori & Tomotsune

So Saito LawyerSo Law Office

Eiji Sasahara

Doctor of Pharmaceuticals, Director,Healthcare Cloud Initiative

Soichiro Takagi


Ikuo Takahashi


Takashi Nakazaki

Anderson Mori & Tomotsune

Masakazu Masujima


Medical/Nursing care/Healthcare Logistics/Supply chain/Mobility, etc

*Japanese syllabary order, titles omitted

Cross-cutting themes

1. background and objectives · differences in system requirements among fields and themes. the...

Documents