Search

Many medical errors occur in the process of treating cardiovascular patients, and most of these errors are related to prescription errors. There are several, one of the methods to prevent prescription errors is the use of a computerized physician order entry (CPOE) system. One of the obstacles of implementing this system is improper design and non-compliance with user needs. one of the issues that should be considered in designing information systems is having a standard minimum data set (MDS). Although many computerized physicians order entry (CPOE) systems have been developed in the world, no study has identified the necessary data and minimum data set (MDS) of CPOE system, and published the process of creating this MDS. This study aimed to develop an MDS for cardiovascular CPOE and standardize it with Fast Healthcare Interoperability Resources (FHIR). A multi-method approach including systematic review for identifying data elements of CPOE, reviewing the content of medical records, validation of the data elements using the expert panel and, determination of the necessary data elements using a survey was conducted. Classification of the data elements and mapping them to FHIR were done to facilitate data sharing and integration with the electronic health record (EHR) system as well as to reduce data diversity. The final data elements of MDS were categorized into 5 main categories of FHIR (foundation, base, clinical, financial, and specialized) and 146 resources, where possible. Mapping was done by one of the researchers and checked and verified by the second researcher. Non-mapped data elements were added to relevant resources as extensions of existing FHIR resources. In total, 270 data elements were identified from the systematic review. After reviewing the content of 20 patients’ medical records, 28 data elements were identified. After combination of data elements of two previous phases and removing duplication, 282 data elements remained. Data elements that were considered necessary to be included in CPOE by conducting a survey among cardiovascular physicians were 109 elements. From 146 resources of FHIR, the data elements of this MDS are covered by 5 resources. This study introduced an MDS for cardiovascular CPOE by combining suggested data elements of previous research, and the practical and local requirements identified in patients' medical records. To facilitate data sharing and integration with EHR, reduce data diversity, and also to categorize data, this MDS was standardized with FHIR. The steps we used to develop this MDS could be a model for creating MDS in other CPOEs and health information systems. This is the first time that the process of developing an MDS for cardiovascular CPOE has been presented in the literature. [ABSTRACT FROM AUTHOR]

As a consequence of the epidemiological transition towards non-communicable diseases, integrated care approaches are required, not solely focused on medical purposes, but also on a range of essential activities for the maintenance of the individuals' quality of life. In order to allow the exchange of information, these integrated approaches might be supported by digital platforms, which need to provide trustful environments and to guarantee the integrity of the information exchanged. Therefore, together with mechanisms such as authentication, logging or auditing, the definition of access control policies assumes a paramount importance. This article focuses on the development of a parser as a component of a platform to support the care of community-dwelling older adults, the SOCIAL platform, to allow the definition of access control policies and rules using natural languages. [ABSTRACT FROM AUTHOR]

We sought to enable better interoperability and easy adoption of healthcare applications by developing a standardized domain independent Application Programming Interface (API) for an Electronic Medical Record (EMR) system. We leveraged the modular architecture of the Open Medical Record System (OpenMRS) to build a Fast Healthcare Interoperability Resources (FHIR) based add-on module that could consume FHIR resources and requests made on OpenMRS. The OpenMRS FHIR module supports a subset of FHIR resources that could be used to interact with clinical data persisted in OpenMRS. We demonstrate the ease of connecting healthcare applications using the FHIR API by integrating a third party Substitutable Medical Apps & Reusable Technology (SMART) application with OpenMRS via FHIR. The OpenMRS FHIR module is an optional component of the OpenMRS platform. The FHIR API significantly reduces the effort required to implement OpenMRS by preventing developers from having to learn or work with a domain specific OpenMRS API. We propose an integration pathway where the domain specific legacy OpenMRS API is gradually retired in favor of the new FHIR API, which would be integrated into the core OpenMRS platform. Our efforts indicate that a domain independent API is a reality for any EMR system. These efforts demonstrate the adoption of an emerging FHIR standard that is seen as a replacement for both Health Level 7 (HL7) Version 2 and Version 3. We propose a gradual integration approach where our FHIR API becomes the preferred method for communicating with the OpenMRS platform. [ABSTRACT FROM AUTHOR]