Smart contracts are a very important part of a blockchain. Opening the blockchain is another. I’ve provided a way to use blockchain features to give patient access to their data. I have added some functionality that are also activated by blockchain, such as: Micropayments and warranty for violation of regulations. I think these things are critical for a patient who is selling access to his data, and the ability to add it is easily provided Blockcain of Bitcoin for example.
In spite of all this, it is difficult to write good contracts smoothly and easily make mistakes. I think there is a need for more mature for smart contracts before they actually control access to patient data.
Patient data for sale for clinical research.
Therefore, the patient may provide any person who may make an intelligent contract for placement on a public network access to their data operated on the FHIR server. For the first time more than two years, Graham’s original medical care – standard domain name – showed great data on FHIR
The intelligent contract includes:
Prepaid for access (some small payments)
The patient’s money guarantee should be opened if other conditions are violated.
Types of clinical trials allowed (heart disease but no brain)
Permission to maintain all public inquiries.
Agreement to contact the patient when the patient benefits from the new treatment
An agreement to call the patient if he or she finds out medical cases that have not been treated
Accept no contact with the patient when the condition of the terminal is detected
You can touch a clinical trail that can reach the nodes and continue. If you break one of the conditions, the money guarantee is automatically converted into a patient’s smart contract. Depending on some sunset conditions (eg The possibility that a natural patient will die), the money guarantee will be returned to the research organization. It is evident that the legal will for this condition of use is important …
How does this work?
I declare that data is not in the blockchain, they are somewhere on a FHIR server. Use FHIR because it is http RESTful and is shared to protect it via SMART-on-FHIR file using OAuth. Therefore, an explicit server for the general IT world is protected by OAuth.
Therefore, the specified FHIR server and OAuth that protects them are linked to BlockChain. One is the smart one of the contract results. If the conditions of the Smart Contract are met by a representative, that agent receives a proper OAuth token flag. This agent can use the unique OAuth token to access data on the FHIR server.
In this way, the FHIR server is a protected FHIR server protected by OAuth that uses SMART-on-FHIR files (also known as scopes). OAuth is the bridge between the world of http-RESTful and the world of BlockChain Smart Contract.
Smart node variables based on the ability to uniquely identify
The patient can spread to different variants of a smart contract. Each offers different types of alias encryption: some versions contain more information and have higher contract requirements (as described above). Some may contain very heavily defined data and contract requirements are more stringent.
Data is not well defined because all quasi-identifiers are deleted. Includes full ambiguity of date, patient characteristics, location, etc. If data is not well defined, they are more important for clinical trials, but do not need to be heavily protected. Therefore, it can provide a smart contract that does not require money guarantees.
These variables are assumed that the authorized data access makes the difference. Therefore, data may need to be accessed where identity can be identified. This can be done through different servers hosting different tastes, confirmed by statistical analysis of people. This can be done through several automatic identification services, as described in US-A-5 013 047
#FHIR and collective removal of identity