Projects
E-HEALTH BRAZIL
Scroll down to discover

2021 Brazil E-Health Project Phase 1

pexels-thirdman-5327915
pexels-gustavo-fring-3985299
pexels-andrea-piacquadio-3823488
pexels-laura-james-6098054 (1)

2021 Brazil E-Health Project Phase 1

This project is in reference to requirements put-forward by IBREI Brazil which is represented in over 20 countries and supporting in collaboration with technologies and strategic partners as well as international think tanks. This project aims bringing out path-breaking strategic plans that reflect new directions in technology, product and process innovations, social shaping of technology and creating a healthy and conducive ecosystem for fostering innovations in the State of Brazil.

Several Hospitals and Universities have joined this effort to change the current technological environment of the system relevant hospitals and health institutions of Brazil.Due to the nature oft this project we can give only a small insight of the 1st phase

In cooperation with Accubits Technologies, ATROMG8 and IBREI have put forward a solution where Blockchain can be integrated into the current E-health platform for better data security and better data transfer.

The onboarding process for medical treatment will be the same for the patient. The data collected by the Hospital front desk will be segregated by the application and the PII data along with HIN id will be send to the blockchain application server for onboarding process.

The blockchain application server will then send patient account creation request to the Blockchain Node. Once the account has been created the blockchain node will create a public and private key for the patient and sends the keys to blockchain application server.

The PII data will then be encrypted with public key inside the blockchain application server and that data will then be send to Blockchain Node. The Node saves the data and will return the corresponding transaction hash to the Blockchain application server. The HIN id, public key and the transaction hash mapping is saved in another database.

The transaction hash and HIN id will be send to e health application server from the blockchain application server. The eHealth database will store HIN id, transaction hash and also the Non PII information. The eHealth application server will then send the HIN id to the front desk. This Id can be used for future purposes. All the medical data regarding the patient will be saved in this Id.

The next time when the patient visits the hospital or any other Medical Service he just have to share his HIN id to the front desk. If the non PII data is required then the front desk will request for non PII data will be given to eHealth application server. Using the HIN id the application will search for Non PII data in the applications database. It then returns the information to the hospital front desk. For getting the PII data, the hospital front desk will send request to the eHealth application server.

As the PII data is stored in the Blockchain application server, the eHealth application server will request for PII data using the HIN id. Using the patient’s HIN id, the blockchain retrieves patient’s public key and transaction hash. The public key can be used to get patient’s private key. The retrieved transaction hash from database can be used to get patients encrypted PII from the Blockchain node. The encrypted PII data can be decrypted using the patient’s private key. A SMS or E-Mail will be send to the patient mentioning that their data has been accessed. The blockchain application server will send the PI data and HIN id to eHealth application server. The application will then forward the data to the front desk of the hospital.

PROJECT SCOPE ONBOARDING PROCESS

  1. Using the e-health application, non PII data and PII data are separated
  2. The non PII data is stored in the e Health Application database
  3. To store the PII information, the E-Health application server puts forward a request to the Blockchain application server
  4. The Blockchain application server puts forward a request to the Blockchain node to create an account for the patient
  5. The public and private keys for the node are then sent over to the Blockchain application server
  6. The PII data in the blockchain application server is encrypted with the public key and sent over to the blockchain node
  7. The Blockchain node saves the PII data and reverts to the blockchain application server with a transaction hash
  8. The HIN Id, Public key, and transaction hash mapping are saved in the blockchain database
  9. The blockchain application server reverts to the e health application server with the transaction hash and HIN Id
  10. This data is made available in the hospital front desk

 

PATIENT CONSULTATION

  1. The patient provides their HIN Id at the hospital front desk
  2. The hospital front desk system requests for PII data against the HIN data to the E -Health application server
  3. The E-Health application data requests for PII data in the Blockchain application server, against the HIN Id d. The blockchain application server collects the patient information public key and transaction hash from the database
  4. The private key is then retrieved from the key management by the blockchain application server
  5. Using the retrieved transaction hash and private key, the encrypted PII data is then decrypted and available
  6. At this point, SMS and Email notifications are sent to the patient’s registered number
  7. The SMS and Email are sent only once in 24 hours
  8. The PII information is sent from the blockchain application server to the E-health Application server, and then to the hospital front desk