## 5 Results and Discussion
### Functional Requirements
#### 5.1.3 PHR and Stakeholders  
This theme illustrates common interests among all stakeholders.
* Unified medical standards and regulations The system should have unique record numbers across all participating healthcare centers that are different from the patient IDs. As Expert 7 illustrates, \"There must be a mechanism to give a unified number to each patient, and then we build on this file. This number can be used to direct access to the patient's record, even in emergency situations\". This, as a result, will allow a healthcare center to share data and transfer a patient to another healthcare center or physician. According to Expert 12, \"If the healthcare center cannot treat the patient, the healthcare center can transfer the patient to another healthcare center participating in the blockchain network, and the patient can permit other physicians to view reports to take additional consultations on their condition\".  
1.4 Healthcare Provider Administration Issues and PHRs This theme illustrates the healthcare providers' requirements that should be considered from their side when designing PHRs.
* Keep PHR for patient use and have another for healthcare center administrative use There are several benefits that a PHR provides to a patient; however, a healthcare center needs to access PHRs without obtaining patient approval. According to Expert 1,\"We in the health records department follow the patient's record and make sure all data are entered completely and correctly after they leave... for inpatient, we make sure that the test form is passed to the physician to monitor the patient's condition appropriately\" This is called a health services foster; so, waiting for a patient to give a healthcare center approval will negatively impact the work on medical records. Moreover, physicians should have the ability to modify PHR reports to correct wrong information for healthcare centers. According to Expert 1, \"It does not make sense to get back to the patient and ask him to allow us to make modifications to their records... there is an example that happens daily. We raise insurance claims, so we do modifications as insurance agencies requests for more clarification, and we add more details about his condition to know if the insurance approves the claim or rejects [it]. So, the patient pays the costs, and sometimes the insurance does not respond until a patient leaves or is discharged\". This should be for administrative tasks, but patients must not be able to edit or delete reports. \"The patient should not be able to change some results or add or remove reports. The patient should only be able to block or allow a physician to check his reports\".  
The section for physician documentation is not visible to a patient without a release option  
The system should have a release option for a physician for sensitive reports. As Expert 4 explains, \"There is something we call investigation release and results release, for example, if a woman has a pregnancy test, and the result comes out. The physician has the option to allow the analysis to appear for the patient; this is called results or lab release\". In addition, the system should also have a release option for physicians for sensitive reports; as Expert 4 stated, \"... another person went to the physician with serious symptoms or for a patient with psychological symptoms indicating that he could commit suicide. The physician here writes these special notes... the physician has a choice whether he releases so it is clear to another physician who treats the patient, but it is not visible to the patient\".