## 4 Results  
We evaluated our architecture against the design criteria shown in Table 2 and the first comparison was made according to the simulation scenarios, platforms, and tools used. In [PERSON] and [PERSON] [39], simulations were used to predict and describe the impact of different configurations, targets, and scenarios on the system behavior. Thus, simulation can answer questions such as, \"What would happen if experimenting with new designs and policies without the need for the system's operation?\" [40]. When designing and deploying blockchain solutions, many performance-impacting configuration choices must be made [24; 39; 41]. The smart contract is made up with Solidity in the proposed design and compiled and tested using Remix IDE. Solidity is a sophisticated high-level programming language to create intelligent contracts; it lets users create decentralized programs so that miners may run and test and debug Solidity code in its environment [8; 46; 47]. Conversely, Table 3 displays the functional attributes of blockchain architectures for medical record management and data exchange. An implementation comparison was made to highlight the usefulness and feasibility of the proposed design, in which the authentication of users and the safeguarding of information under the attributes of reliability or data structure are performed, authorized, and access is authenticated with validation and decentralized supervision, in addition to compliance within the country's legal framework, where the medical record is considered as a set of documents of any kind, in which health personnel must record, annotate, and certify their interventions. [PERSON] [49] mentions that Mexican information protection laws cover all the data in the medical record to be protected and prevent unauthorized personnel from using this information. Medical records are defined and regulated legal standards focus on the parameters of medical information integration and on technical regulation. The safety of the proposed design was consistent with that of the theorem. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**Model** & **Target** & **Tools for Development** & **Platform** & **Environments of Simulation** \\ \hline Access administration system [42] & IoT access control & Remix IDE & Ethereum, raspberry & Javascript \\ \hline System for controlling access [43] & Cross-chain-based access control & - & IOTA and Tangle & Ubuntu 16.04 \\ \hline Access administration system [44] & Access control with IoT-related & - & Multiple public & OMNeT++ 5.4.1 \\ \hline Safeguard data exchange [45] & Deep learning is used to share data & Go & Ethereum & Python \\ \hline Secure data exchanges & Data sharing with A.I. & - & Hyperledger fabric & - \\ \hline The proposed model includes access control, record sharing, and management & Access control, data exchange, and management. & Remix IDE, Solidity & Hyperledger, separate modules & Remix IDE, python, JavaScript \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Platforms and tools used. \begin{table}
\begin{tabular}{l c c c c c c} \hline \hline
**Systems** & **Reliability** & **Authorization** & **Authentication** & **Validation** & **Decentralized** & **Regulations** \\ \hline Access administration system [42] & Yes & No & No & Yes & Yes & No \\ Access administration system [43] & No & No & No & No & Yes & No \\ Access administration system [44] & No & Yes & No & No & Yes & Yes \\ Data sharing system [45] & No & No & Yes & Yes & Yes & Yes \\ Data sharing system [48] & Yes & No & No & No & Yes & No \\ Proposed data sharing and access control system & Yes & Yes & Yes & Yes & Yes & Yes \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Comparison of parameters with other works. **Theorem 1**.