A Controllable Secure Blockchain-Based Electronic Healthcare Records Sharing Scheme
Table 4
Report of the prototype system test.
Test scenario
Operation
Observation report
Result
EHR file upload
The doctor submitted the EHR file to IEFS
IEFS successfully returned the hash file address: Qmcm55BkaB9PifiqBwqGDY489z2YXMQEjZYKKY4sz1jnuz
Done
EHR abstract publish
The doctor published the EHR abstract on BEAS
(1) The abstract was successfully published (2) The file address was encrypted with the patient’s public key. The new address was ‘4e652982f63d24eb3cbef31f43d999f5a9a3bef3898b44329fab575b702b421a7974ef0f87111b665dac9e124da6de1336d83f2e21c489db30df6042f856a5a6’
Done
Invalid access of EHR file
The visitor tried to visit the EHR file outside the time window
The visit was rejected
Done
The unauthorized visitor tried to visit the EHR file
The visit was rejected
Done
EHR file address request
The doctor sent the request to BEAS
(1) The doctor’s ID and the time window were successfully accepted by IEFS (2) The file address was successfully decrypted by the patient’s private key and re-encrypted with the visitor’s public key (3) The address was returned to the visitor. The encrypted address was ‘8a2e1348205a9ef5ab1ad22a83c2211063a8127975e5aa32f75d350ce1a3f3bffedd5ddc28fa214c52926ac679e7ab7462515dfa9708e437db3b5a1723d69556’
Done
EHR file download
The doctor sent the request to IEFS
(1) The file address was decrypted with the doctor’s private key to the original value ‘Qmcm55BkaB9PifiqBwqGDY489z2YXMQEjZYKKY4sz1jnuz’ (2) The doctor’s ID and the visit time were accepted (3) The file was output by IPFS and encrypted with the doctor’s public key (4) The visit log was published to BEAS for auditing (5) The doctor got the file and decrypted it to the original file
