Table 1. Literature review.

References	Objectives	1	2	3	Limitations
[15, 23, 29, 30]	The blockchain-based management system to handle EMRs	×	×	✓	Third party privileges are not considered, no classification of data.
[32, 33]	Patient’s data access management mechanisms to address the issue of patients’ privileges	×	✓	×	Patients’ privileges are not considered, plus none-patient driven.
[49–51]	Patient’s data access management mechanisms to address the issue of user privileges	×	✓	×	User privileges are considered except the patients’ privileges, none-patient centric.
[53, 54]	Patient’s data access management mechanisms to address the issue of data privacy	×	×	✓	Patient privileges are not considered, including diverse privileges and scalability complications.
[12, 21, 23, 57, 58]	Patient-centric healthcare data access management scheme for privacy preservation.	×	×	✓	Patient centric, Patients’ privileges are not fully considered.
[34–36, 43],	Patient-centric healthcare data management scheme for privacy preservation.	×	✓	×	Patients’ privileges are not considered, including none-patient driven.
[37, 38, 40, 41]	To protect the privacy of electronic health records.	×	×	✓	Third party privileges are not considered, and have no classification of data.
[42, 45]	To view patient medical records in an emergency without the patient’s permission	✓	×	×	Patient centric, patients’ privileges are not fully considered.

1: Patients have partial control over their records. 2: Patients have no control over their records. 3: Patients have full control over their records.