Interoperability of heterogeneous health information systems: a systematic literature review

Abstract

Background The lack of interoperability between health information systems reduces the quality of care provided to patients and wastes resources. Accordingly, there is an urgent need to develop integration mechanisms among the various health information systems. The aim of this review was to investigate the interoperability requirements for heterogeneous health information systems and to summarize and present them. Methods In accordance with the PRISMA guideline, a broad electronic search of all literature was conducted on the topic through six databases, including PubMed, Web of science, Scopus, MEDLINE, Cochrane Library and Embase to 25 July 2022. The inclusion criteria were to select English-written articles available in full text with the closest objectives. 36 articles were selected for further analysis. Results Interoperability has been raised in the field of health information systems from 2003 and now it is one of the topics of interest to researchers. The projects done in this field are mostly in the national scope and to achieve the electronic health record. HL7 FHIR, CDA, HIPAA and SNOMED-CT, SOA, RIM, XML, API, JAVA and SQL are among the most important requirements for implementing interoperability. In order to guarantee the concept of data exchange, semantic interaction is the best choice because the systems can recognize and process semantically similar information homogeneously. Conclusions The health industry has become more complex and has new needs. Interoperability meets this needs by communicating between the output and input of processor systems and making easier to access the data in the required formats.

Overview of Early ChatGPT’s Presence in Medical Literature: Insights From a Hybrid Literature Review by ChatGPT and Human Experts

“…[31][32][33]. This is particularly critical in the medical field, where there is a need for clear and accurate communication of medical information to patients and healthcare professionals [34].…”

Public Health Informatics and the Perioperative Physician: Looking to the Future

“…Systemized Nomenclature of Medicine (SNOMED) is another vocabulary able to represent everything listed above and more. 92 Some of these vocabularies are in very wide use. For example, use of NDC codes for medications is industry standard, and the barcode on every vial, jar, and package of prescription medication represents the NDC code for that specific brand and formulation of that drug.…”

“…These vocabularies include representations of drugs and medications (National Drug Code [NDC]), laboratory and clinical observations (Logical Observation Identifiers Names and Codes [LOINC]), disease conditions (International is another vocabulary able to represent everything listed above and more. 92 Some of these vocabularies are in very wide use. For example, use of NDC codes for medications is industry standard, and the barcode on every vial, jar, and package of prescription medication represents the NDC code for that specific brand and formulation of that drug.…”

What is meant by ‘integrated personalized diabetes management’: A view into the future and what success should look like

“…Technological fragmentation happens when various healthcare systems and technologies are not compatible and cannot exchange data efficiently. 131 Software applications, including mobile phone apps, often work as standalone solutions and may not be suitable for daily interdisciplinary workflows. 132 One approach to address organizational and technological fragmentation is using an integrated digitally enabled health service platform.…”

“…As previously discussed, the provision of integrated services is a challenge due to the lack of coordination and integration among different organizations, systems, and technologies. Technological fragmentation happens when various healthcare systems and technologies are not compatible and cannot exchange data efficiently 131 . Software applications, including mobile phone apps, often work as standalone solutions and may not be suitable for daily interdisciplinary workflows 132 …”