# Performance of API Design for Interoperability of Medical Information Systems
## 3 Design of the API Proposal
### Discussion  
In this proposal, an object-oriented approach was selected, and design patterns were incorporated to enhance the performance of the software architecture of the medical interoperability API. In this case, the primary concern was addressing the context of inherited medical interoperability that involved medical centers or hospitals with devices that have limited memory capacity for patient data. Emphasis was placed on optimizing the design through the use of dynamic objects in memory generated at runtime. This approach differs from others where all system functions are loaded into memory, potentially negatively impacting the API's operational dynamics due to potential memory saturation on the executing devices.  
\begin{table}
\begin{tabular}{c c c c c} \hline \hline
**ID Path** & \multicolumn{3}{c}{**Sequence**} & \multicolumn{2}{c}{**Performance Parameter**} \\ \hline
1 & v0 & v1 & & \\ \hline CBO & 2 & 3 & & 0.9428 \\ \hline CCM & 1 & 1 & & \\ \hline
2 & v0 & v1 & v2 & \\ \hline CBO & 2 & 3 & 1 & 0.7745 \\ \hline CCM & 1 & 1 & 1 & \\ \hline
3 & v0 & v1 & v2 & v3 & \\ CBO & 2 & 3 & 1 & 2 & 0.0 \\ CCM & 1 & 1 & 1 & 1 & \\ \hline
4 & v0 & v1 & v2 & v4 & \\ CBO & 2 & 3 & 1 & 0.7745 \\ CBM & 1 & 1 & 1 & \\ \hline
5 & v0 & v1 & v2 & v5 & \\ CBO & 2 & 3 & 1 & 0.7745 \\ CMM & 1 & 1 & 1 & & \\ \hline \(\vdots\) & & \(\vdots\) & & \(\vdots\) \\ \hline
18 & V2 & V6 & & \\ CBO & 1 & 0 & & 1.0 \\ CMM & 1 & 0 & & \\ \hline \hline \end{tabular}
\end{table}
Table 3: Set the critical paths evaluated through performance parameters on API architecture.  
To validate and quantify the proposed design approach, a software architecture evaluation method was integrated based on design quality attributes, such as complexity and coupling. The selected proposal for analysis emphasized a complexity approach strengthened with coupling, with the understanding that this relationship is linked to performance and is a desired attribute for application performance. The design evaluation was static, as the source code was not available during this phase. The evaluation was conducted through UML diagrams, algorithms, and other design artifacts. Evaluating the design  
Figure 5: Interoperability API’s ACG.  
Figure 6: Dispersion performance of API architectural design.  
was advantageous due to cost reduction, defect localization and correction before code implementation, and early test prioritization based on components identified with a higher probability of failure.  
The architectural design evaluation applied in this research established a predictive model and a formal method to assess the quality in object-oriented systems. The architectural complexity graph (ACG) was introduced for a deterministic analysis, serving as a basis to establish the performance parameter. Component sequences with a parameter close to +1 were considered to have a stronger relationship between complexity and coupling attributes, indicating a good level of performance. As shown in the plot of the dispersion performance of the API architectural design in Figure 6, implementing abstract factory and wrapper design patterns in the proposed API architecture led to 94.5 percent of the evaluated sequences being close to +1, suggesting a good level based on complexity and coupling. We considered the approach logically valid for indirectly studying the performance of software design architectures.