Dataset Information

Julius--a template based supplementary electronic health record system.

ABSTRACT:

Background

EHR systems are widely used in hospitals and primary care centres but it is usually difficult to share information and to collect patient data for clinical research. This is partly due to the different proprietary information models and inconsistent data quality. Our objective was to provide a more flexible solution enabling the clinicians to define which data to be recorded and shared for both routine documentation and clinical studies. The data should be possible to reuse through a common set of variable definitions providing a consistent nomenclature and validation of data. Another objective was that the templates used for the data entry and presentation should be possible to use in combination with the existing EHR systems.

Methods

We have designed and developed a template based system (called Julius) that was integrated with existing EHR systems. The system is driven by the medical domain knowledge defined by clinicians in the form of templates and variable definitions stored in a common data repository. The system architecture consists of three layers. The presentation layer is purely web-based, which facilitates integration with existing EHR products. The domain layer consists of the template design system, a variable/clinical concept definition system, the transformation and validation logic all implemented in Java. The data source layer utilizes an object relational mapping tool and a relational database.

Results

The Julius system has been implemented, tested and deployed to three health care units in Stockholm, Sweden. The initial responses from the pilot users were positive. The template system facilitates patient data collection in many ways. The experience of using the template system suggests that enabling the clinicians to be in control of the system, is a good way to add supplementary functionality to the present EHR systems.

Conclusion

The approach of the template system in combination with various local EHR systems can facilitate the sharing and reuse of validated clinical information from different health care units. However, future system developments for these purposes should consider using the openEHR/CEN models with shareable archetypes.

SUBMITTER: Chen R

PROVIDER: S-EPMC1868711 | biostudies-literature | 2007 May

REPOSITORIES: biostudies-literature

ACCESS DATA

Publications

Julius--a template based supplementary electronic health record system.

Chen Rong R Enberg Gösta G Klein Gunnar O GO

BMC medical informatics and decision making 20070502

<h4>Background</h4>EHR systems are widely used in hospitals and primary care centres but it is usually difficult to share information and to collect patient data for clinical research. This is partly due to the different proprietary information models and inconsistent data quality. Our objective was to provide a more flexible solution enabling the clinicians to define which data to be recorded and shared for both routine documentation and clinical studies. The data should be possible to reuse th ...[more]

PMID: 17474997

Similar Datasets

Project description:BackgroundElectronic health records (EHRs) enable health data exchange across interconnected systems from varied settings. Epic is among the 5 leading EHR providers and is the most adopted EHR system across the globe. Despite its global reach, there is a gap in the literature detailing how EHR systems such as Epic have been used for health care research.ObjectiveThe objective of this scoping review is to synthesize the available literature on use cases of the Epic EHR for research in various areas of clinical and health sciences.MethodsWe used established scoping review methods and searched 9 major information repositories, including databases and gray literature sources. To categorize the research data, we developed detailed criteria for 5 major research domains to present the results.ResultsWe present a comprehensive picture of the method types in 5 research domains. A total of 4669 articles were screened by 2 independent reviewers at each stage, while 206 articles were abstracted. Most studies were from the United States, with a sharp increase in volume from the year 2015 onwards. Most articles focused on clinical care, health services research and clinical decision support. Among research designs, most studies used longitudinal designs, followed by interventional studies implemented at single sites in adult populations. Important facilitators and barriers to the use of Epic and EHRs in general were identified. Important lessons to the use of Epic and other EHRs for research purposes were also synthesized.ConclusionsThe Epic EHR provides a wide variety of functions that are helpful toward research in several domains, including clinical and population health, quality improvement, and the development of clinical decision support tools. As Epic is reported to be the most globally adopted EHR, researchers can take advantage of its various system features, including pooled data, integration of modules and developing decision support tools. Such research opportunities afforded by the system can contribute to improving quality of care, building health system efficiencies, and conducting population-level studies. Although this review is limited to the Epic EHR system, the larger lessons are generalizable to other EHRs.

Project description:BACKGROUND:Computable phenotypes have the ability to utilize data within the electronic health record (EHR) to identify patients with certain characteristics. Many computable phenotypes rely on multiple types of data within the EHR including prescription drug information. Hypertension (HTN)-related computable phenotypes are particularly dependent on the correct classification of antihypertensive prescription drug information, as well as corresponding diagnoses and blood pressure information. OBJECTIVE:This study aimed to create an antihypertensive drug classification system to be utilized with EHR-based data as part of HTN-related computable phenotypes. METHODS:We compared 4 different antihypertensive drug classification systems based off of 4 different methodologies and terminologies, including 3 RxNorm Concept Unique Identifier (RxCUI)-based classifications and 1 medication name-based classification. The RxCUI-based classifications utilized data from (1) the Drug Ontology, (2) the new Medication Reference Terminology, and (3) the Anatomical Therapeutic Chemical Classification System and DrugBank, whereas the medication name-based classification relied on antihypertensive drug names. Each classification system was applied to EHR-based prescription drug data from hypertensive patients in the OneFlorida Data Trust. RESULTS:There were 13,627 unique RxCUIs and 8025 unique medication names from the 13,879,046 prescriptions. We observed a broad overlap between the 4 methods, with 84.1% (691/822) to 95.3% (695/729) of terms overlapping pairwise between the different classification methods. Key differences arose from drug products with multiple dosage forms, drug products with an indication of benign prostatic hyperplasia, drug products that contain more than 1 ingredient (combination products), and terms within the classification systems corresponding to retired or obsolete RxCUIs. CONCLUSIONS:In total, 2 antihypertensive drug classifications were constructed, one based on RxCUIs and one based on medication name, that can be used in future computable phenotypes that require antihypertensive drug classifications.

Project description:BackgroundPatients' perspectives and social contexts are critical for prevention of hospital readmissions; however, neither is routinely assessed using the traditional history and physical (H&P) examination nor commonly documented in the electronic health record (EHR). The H&P 360 is a revised H&P template that integrates routine assessment of patient perspectives and goals, mental health, and an expanded social history (behavioral health, social support, living environment and resources, function). Although the H&P 360 has shown promise in increasing psychosocial documentation in focused teaching contexts, its uptake and impact in routine clinical settings are unknown.ObjectiveThe aim of this study was to assess the feasibility, acceptability, and impact on care planning of implementing an inpatient H&P 360 template in the EHR for use by fourth-year medical students.MethodsA mixed methods study design was used. Fourth-year medical students on internal medicine subinternship (subI) services were given a brief training on the H&P 360 and access to EHR-based H&P 360 templates. Students not working in the intensive care unit (ICU) were asked to use the templates at least once per call cycle, whereas use by ICU students was elective. An EHR query was used to identify all H&P 360 and traditional H&P admission notes authored by non-ICU students at University of Chicago (UC) Medicine. Of these notes, all H&P 360 notes and a sample of traditional H&P notes were reviewed by two researchers for the presence of H&P 360 domains and impact on patient care. A postcourse survey was administered to query all students for their perspectives on the H&P 360.ResultsOf the 13 non-ICU subIs at UC Medicine, 6 (46%) used the H&P 360 templates at least once, which accounted for 14%-92% of their authored admission notes (median 56%). Content analysis was performed with 45 H&P 360 notes and 54 traditional H&P notes. Psychosocial documentation across all H&P 360 domains (patient perspectives and goals, mental health, expanded social history elements) was more common in H&P 360 compared with traditional notes. Related to impact on patient care, H&P 360 notes more commonly identified needs (20% H&P 360; 9% H&P) and described interdisciplinary coordination (78% H&P 360; 41% H&P). Of the 11 subIs completing surveys, the vast majority (n=10, 91%) felt the H&P 360 helped them understand patient goals and improved the patient-provider relationship. Most students (n=8, 73%) felt the H&P 360 took an appropriate amount of time.ConclusionsStudents who applied the H&P 360 using templated notes in the EHR found it feasible and helpful. These students wrote notes reflecting enhanced assessment of goals and perspectives for patient-engaged care and contextual factors important to preventing rehospitalization. Reasons some students did not use the templated H&P 360 should be examined in future studies. Uptake may be enhanced through earlier and repeated exposure and greater engagement by residents and attendings. Larger-scale implementation studies can help further elucidate the complexities of implementing nonbiomedical information within EHRs.

Project description:BackgroundThe predominant implementation paradigm of electronic health record (EHR) systems in low- and middle-income countries (LMICs) relies on standalone system installations at facilities. This implementation approach exacerbates the digital divide, with facilities in areas with inadequate electrical and network infrastructure often left behind. Mobile health (mHealth) technologies have been implemented to extend the reach of digital health, but these systems largely add to the problem of siloed patient data, with few seamlessly interoperating with the EHR systems that are now scaled nationally in many LMICs. Robust mHealth applications that effectively extend EHR systems are needed to improve access, improve quality of care, and ameliorate the digital divide.ObjectiveWe report on the development and scaled implementation of mUzima, an mHealth extension of the most broadly deployed EHR system in LMICs (OpenMRS).MethodsThe "Guidelines for reporting of health interventions using mobile phones: mobile (mHealth) evidence reporting assessment (mERA)" checklist was employed to report on the mUzima application. The World Health Organization (WHO) Principles for Digital Development framework was used as a secondary reference framework. Details of mUzima's architecture, core features, functionalities, and its implementation status are provided to highlight elements that can be adapted in other systems.ResultsmUzima is an open-source, highly configurable Android application with robust features including offline management, deduplication, relationship management, security, cohort management, and error resolution, among many others. mUzima allows providers with lower-end Android smartphones (version 4.4 and above) who work remotely to access historical patient data, collect new data, view media, leverage decision support, conduct store-and-forward teleconsultation, and geolocate clients. The application is supported by an active community of developers and users, with feature priorities vetted by the community. mUzima has been implemented nationally in Kenya, is widely used in Rwanda, and is gaining scale in Uganda and Mozambique. It is disease-agnostic, with current use cases in HIV, cancer, chronic disease, and COVID-19 management, among other conditions. mUzima meets all WHO's Principles of Digital Development, and its scaled implementation success has led to its recognition as a digital global public good and its listing in the WHO Digital Health Atlas.ConclusionsGreater emphasis should be placed on mHealth applications that robustly extend reach of EHR systems within resource-limited settings, as opposed to siloed mHealth applications. This is particularly important given that health information exchange infrastructure is yet to mature in many LMICs. The mUzima application demonstrates how this can be done at scale, as evidenced by its adoption across multiple countries and for numerous care domains.

Project description:BackgroundElectronic Health Records (EHRs) are now widely used to create a single, shared, and reliable source of patient data throughout healthcare organizations. However, health professionals continue to experience mismatches between their working practices and what the EHR allows or directs them to do. Health professionals adopt working practices other than those imposed by the EHR to overcome such mismatches, known as workarounds. Our study aims to inductively develop a typology of enduring EHR workarounds and explore their consequences by answering the question: What types of EHR workarounds persist, and what are the user-perceived consequences?MethodsThis single case study was conducted within the Internal Medicine department of a Dutch hospital that had implemented an organization-wide, commercial EHR system over two years ago. Data were collected through observations of six EHR users (see Additional file 1, observation scheme) and 17 semi-structured interviews with physicians, nurses, administrators, and EHR support staff members. Documents were analysed to contextualize these data (see Additional file 2, interview protocol).ResultsThrough a qualitative analysis, 11 workarounds were identified, predominantly performed by physicians. These workarounds are categorized into three types either performed while working with the system (in-system workflow sequence workarounds and in-system data entry workarounds) or bypassing the system (out-system workarounds). While these workarounds seem to offer short-term benefits for the performer, they often create threats for the user, the patient, the overall healthcare organization, and the system.ConclusionThis study increases our understanding of the enduring phenomenon of working around Electronic Health Records by presenting a typology of those workarounds that persist after adoption and by reflecting on the user-perceived risks and benefits. The typology helps EHR users and their managers to identify enduring types of workarounds and differentiate between the harmful and less harmful ones. This distinction can inform their decisions to discourage or obviate the need for certain workarounds, while legitimating others.

Dataset Information

Julius--a template based supplementary electronic health record system.

Background

Methods

Results

Conclusion

Publications

Julius--a template based supplementary electronic health record system.

Similar Datasets

OmicsDI is part of the ELIXIR infrastructure

Tweets