# Performance of API Design for Interoperability of Medical Information Systems
## 2 Related Work  
After the experience of the COVID-19 pandemic, it was found that the efficient and secure interoperability of medical information is of great importance to provide a good medical diagnosis and treatment of patients [1]. There is a need to exchange clinical records to improve the knowledge base and efficiency of care in the health sector. Electronic health records (EHRs) are a collection of information about a person's health status [3]. This standard focuses on the distinction between the representation of health information and its technical implementation. This separation enables the development of more flexible and adaptable electronic health systems over time, which, in turn, significantly contributes to the continuous improvement of patient healthy [2; 19]. This has a great impact on society's health since it is used to carry out assertive diagnoses in medical treatments. The information interoperability in the health sector from an international approach is intended to be resolved through interoperability standards and robust interoperability platforms [1; 2; 20]. The big problem when linking information systems are the coexisting heterogeneity between data and processes related to health records. Many countries have complex health systems; the use of standards and their automation must support the complexity that represents the interoperability of information from clinical records in the various systems that constitute the complex health systems of these regions. [PERSON] Medical Information Interoperability  
Shin [15] described the development of a mobile application for the transmission of biosignals in the health field through the HL7 protocol. The proposed solution is optimized for the home healthcare (uHealthcare) environment and uses ubiquitous computing technologies to monitor health at home. The main components of a ubiquitous medical system are identified, including detection, transmission, diagnosis, and prescribing. This paper describes a specific approach to developing an HL7 API using LabVIEW, emphasizing its role in the transformation of medical data and its capability to transmit this data to other systems via a radio frequency. In this application, data are transmitted from the SpO2 sensor's biosignal to a mobile phone using a serial approach. The mobile phone converts raw data to the HL7 standard and sends it to other PCs via Bluetooth or a WLAN. In the system development, the structure of the abstract message was defined as part of the message-modeling material. The research area of health monitoring systems has transitioned from the simple reasoning of wearable sensor readings to advanced data processing, with the aim to provide more valuable information to end users. In [PERSON]'s study [21], emphasis was placed on the significant role of data mining techniques in extracting valuable insights from data collected by wearable sensors in health monitoring systems. These techniques include anomaly detection, the prediction of future trends based on historical sensor data, making informed decisions about individual health status, and processing continuous time series measurements. However, these advancements also pose challenges and concerns, such as ensuring the reliability and accuracy of collected data, data processing efficiency, and validation in practical healthcare settings. In [PERSON]'s work [16], a prototype for the HL7 mapping function in version v3-RIM was introduced to integrate distributed clinical data sources using R-MIM classes. This prototype was integrated as a module within the Clinical Data Management System (CDMS) clinical databases. During testing with the legacy CDMS, the authors argued for a significant improvement in the information delivery. The unique identifications of the message, interaction identifier, injection event, and receiver responsibilities is achieved through the root element. In the system architecture, the wrapper or decorator design pattern was employed to encapsulate information defined by the interaction code (IN).