China 
Africa 
Explore chapters and articles related to this topic
A Framework for a Secure e-Health Care System Using IoT-Based Blockchain Technology
Published in Sudhir Kumar Sharma, Bharat Bhushan, Aditya Khamparia, Parma Nand Astya, Narayan C. Debnath, Blockchain Technology for Data Privacy Management, 2021
T. Sanjana, B. J. Sowmya, D. Pradeep Kumar, K. G. Srinivasa
The use of a private blockchain owned by an individual is suggested for the health care domain in [33]. The patient alone manages the cross-institutional sharing of information. Fast Healthcare Interoperability Resources (FHIR) are used to provide standard data formats for medical records, and API is used to facilitate the exchange of EHR [34]. This standard format also helps distinguish between data sent by the patient or a clinician. It also helps store data in chronological order. A patient-centric system based on blockchain for health care 4.0 is proposed by in [35]. Data accessibility among the patient, lab, clinician, and system admin is seamlessly possible, using an access control mechanism. A caliper tool is used to verify the performance of the system in terms of latency, throughput, round trip time (RTT), and network security.
Health Informatics for Research Applications of CAD
Published in de Azevedo-Marques Paulo Mazzoncini, Mencattini Arianna, Salmeri Marcello, Rangayyan Rangaraj M., Medical Image Analysis and Informatics: Computer-Aided Diagnosis and Therapy, 2018
There are only a few protocols aiming at interconnecting systems in clinical research: The clinical data interchange standards consortium (CDISC) operational data model (ODM) is designed to facilitate the regulatory-compliant acquisition, archive, and interchange of metadata and data for clinical research studies. ODM is a vendor-neutral, platform-independent format for interchange and archival of clinical study data.The fast healthcare interoperability resources (FHIR) standard is a next-generation framework created by HL7. FHIR combines the best features of HL7’s different versions, while leveraging the latest web standards (REST). FHIR solutions are built from a set of modular components called “Resources.” These resources can easily be assembled into working systems that solve real world clinical and administrative problems at a fraction of the price of existing alternatives. FHIR is suitable for use in a wide variety of contexts, such as mobile phone apps, cloud communications, EHR-based data sharing, server communication in large institutional healthcare providers, and much more.
Healthcare Delivery Systems
Published in A. Ravi Ravindran , Paul M. Griffin , Vittaldas V. Prabhu , Service Systems Engineering and Management, 2018
A. Ravi Ravindran , Paul M. Griffin , Vittaldas V. Prabhu
One of the key challenges of HIE is what is known as interoperability. Interoperability consists of two parts (according to IEEE Standard Computer Dictionary): (i) the ability of two of more systems to exchange information and (ii) the ability of these systems to use the information that has been exchanged. Key to interoperability is agreement on a standard. One popular standard developed for healthcare is Fast Health Interoperability Resources (FHIR), an Internet-based approach developed by Health Level Seven International (HL7), a not-for-profit organization. FHIR is working to allow developers to build standardized browser applications that are independent of the operating system (https://www.hl7.org/fhir/overview.html).
Digital Transformation in Healthcare: Insights on Value Creation
Published in Journal of Computer Information Systems, 2023
Kaushik Ghosh, Michael S. Dohan, Hareesh Veldandi, Monica Garfield
Effective standards for data interchange help break down silos in the healthcare systems. They can also help merge disparate datasets for analytics purposes, because data will be standardized and consistent, therefore ready to merge. However, data integration issues have not been solved by EHRs, or by current standards such as Health Level 7 (HL7), or Systematized Nomenclature of Medicine (SNOMED). There is a demand for more of these standards, and as they improve, there is demand to learn them and gain competency in using them. Participant #11 states: It’s a new standard [FHIR] that is supposed to achieve operability … It’s basically a vendor standard that allows people to build programs that can interact with any EHR. That’s another competency that you have to learn how to do … and do we have that now? No, we don’t have that now.
Designing interoperable telehealth platforms: bridging IoT devices with cloud infrastructures
Published in Enterprise Information Systems, 2020
Kostas M. Tsiouris, Dimitrios Gatsios, Vassilios Tsakanikas, Athanasios A. Pardalis, Ioannis Kouris, Thelma Androutsou, Marilena Tarousi, Natasa Vujnovic Sedlar, Iason Somarakis, Fariba Mostajeran, Nenad Filipovic, Harm op den Akker, Dimitrios D. Koutsouris, Dimitrios I. Fotiadis
This module aims to provide mechanisms to allow interactions between the cloud and existing healthcare services, through a specifically developed API. The scope of this API is to integrate the Fast Healthcare Interoperability Resources (FHIR) standard for healthcare data exchange, as published by HL7®.6 FHIR is an international standard for exchanging digital health data and is increasingly used in health information technology. FHIR streamlines the enrichment of electronic health records (EHRs) by integrating any data sources that can provide clinically meaningful information. FHIR also enables telehealth technologies (Lehne et al. 2019a) and makes health data accessible to advanced, large-scale and population analytics (Braunstein 2019). From the FHIR data models, the proposed API utilises the ‘Observation’ and ‘PlanDefinition’ models. The ‘Observation’ model is used to exchange measurements and metrics between different services to monitor patient progression, determine baselines and patterns that can help clinical decision-making, while the ‘PlanDefinition’ model is used to facilitate patient management. A plan definition is a pre-defined group of actions to be taken in particular circumstances, often including conditional elements, options, and other decision points. Patient data and any other information are transferred in the centralised data repository for storage.