An HIE system and a method for improving treatment of a chronic disease of a patient are described. The method comprises providing a user device for allowing a patient to connect to a health care network implemented over blockchain and to manage access of patient data stored over the blockchain. The method further comprises providing a physician network device for allowing a physician to connect to the health care network. A request may be received from the physician for accessing the patient data and a first parameter related to the patient. The first parameter may be correlated with patients' data to identify correlated data points relevant for the patient. The correlated data points may be sent to the physician, for being used towards the treatment of the chronic disease.

A system and a method of enhancing security of data in a health care network are described. The method includes providing a Health Information Exchange (HIE) server implemented over the blockchain to store users' health information and providing a user device present in communication with the HIE server. Events of accessing a user's health information may be monitored using an Artificial Intelligence (AI) learning module to determine a typical access pattern. All access requests may be compared with the typical access pattern to determine an unusual access behavior corresponding to malicious attempts for breach of the user's health information. The user may be reported about such unusual access behavior to enhance the security of data.

Some embodiments are directed to a system for selectively disclosing attributes and data entries of a record. An issuer device generates a digital signature on a message comprising the attributes and a secret record identifier, and digital signatures on messages comprising respective data entries and each comprising the secret record identifier. The record, secret record identifier, and signatures are provided to a selector device. The selector device selectively discloses attributes and data entries of the record to a receiver device, proving authenticity by means of a zero-knowledge proof of knowledge of the signature on the attributes and signatures on respective data entries. The receiver device verifies the proof with respect to the public key of the issuer and the received attributes and data entries.

One example method includes accessing stored data, associating a unique identifier with the data, creating a hash by hashing a combination that comprises the unique identifier and the data, transmitting the hash to a notary service, receiving, from the notary service, a digital signature that corresponds to the hash, appending the digital signature to the data, and storing, as an object, a combination that comprises the digital signature, the data, and the unique identifier.

An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities that can act as data, service, product providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR Data API can access and retrieve patient identifiable information (PII) and generate a non-patient-identifiable Single Purpose Patient ID (SPPID) for a particular patient. The EHR patient transaction blockchain API (e.g., EHR-DATA-BC-API) can store the SPPID, store particular, discrete data retrieved from the EHR for a patient, execute smart contracts, and control the execution of digital currency transfers, among other functions.

An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities and healthcare providers that can act as data, service, product and service providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR data blockchain system can provide workflow on the blockchain that can utilize smart contracts to define workflow processes, expected outcomes, and financial costs. When a prescription transaction is complete, it will result in the settlement of each of the smart contracts that were added to the prescription workflow.

A method controls a modification of an adjustable device. A system establishes a circle of trust for a plurality of devices, where at least one of the plurality of devices is an adjustment control device for adjusting an adjustable device. Operations of the adjustment control device are controlled via a blockchain, where the blockchain must approve the adjustment control device before an adjustment of the adjustable device is performed by the adjustment control device. The system receives an approval from the blockchain for the adjustment control device to adjust the adjustable device, and the adjustment control device adjusts the adjustable device in response to receiving the approval from the blockchain.

An example operation may include one or more of connecting, by a pharmacy node, to a blockchain network configured to store patients' data on a blockchain ledger, receiving, by the pharmacy node, a request from a patient node for a prescription refill, the request contains a secret key of a patient, extracting, by the pharmacy node, the secret key from the request to verify a patient's identity, and executing, by the pharmacy node, a smart contract to: (a) decrypt a prescription data located on the ledger by an application of the secret key, (b) retrieve patient's allergy records from the ledger to check the allergy records against the prescription data, (c) determine a number of remaining refills from the prescription data, (d) check validity of the prescription data based on an expiration date, and commit a prescription refill transaction to the blockchain based on a successful execution of (b)-(d).

A consent block is a type of block that may be stored in a blockchain. Each consent block has an owner and may store an owner consent contract, i.e., a smart contract containing owner-specified access rules that determine who may access data assets that are stored in other blocks of the blockchain and owned by the same owner. The consent block also stores a hash value determined from the owner consent contract and a previous hash value of the block immediately preceding the consent block. The owner consent contract and the position of the consent block in the blockchain are verifiable from the hash value. Each consent block, once added to the blockchain, becomes part of the immutable record of data stored in the blockchain, and therefore leaves an auditable trail of who had access to which data, and when.

A computer implemented method includes receiving a request at a provider for protected data, the request including a unique identifier corresponding to an authorization to access the protected data or a participant identifier, searching a revocation ledger, denying the request for protected data in response to the unique identifier being stored in the revocation ledger wherein the revocation ledger comprises cryptographically linked blocks of revocations of previous documents granting access to the protected data, denying the request for protected data in response to the participant identifier being stored in the revocation ledger, and granting the request for the protected data in response to neither the unique identifier nor that participant identifier being stored in the revocation ledger.