Biomedical subjects

Scott P Narus

Publications and source records attributed to Scott P Narus.

8 recordsLinked to original sources

PubMed2006

Implementing a multidisease chronic care model in primary care using people and technology.

Management of chronic disease is performed inadequately in the United States in spite of the availability of beneficial, effective therapies. Successful programs to manage patients with these diseases must overcome multiple challenges, including the recognized fragmentation and complexity of the healthcare system, misaligned incentives, a focus on acute problems, and a lack of team-based care. In many successful programs, care is provided in settings or episodes that focus on a single disease. While these programs may allow for streamlined, focused provision of care, comprehensive care for multiple diseases may be more difficult. At Intermountain Healthcare (Intermountain), a generalist model of chronic disease management was formulated to overcome the limitations associated with specialization. In the Intermountain approach, which reflects elements of the Chronic Care Model (CCM), care managers located within multipayer primary care clinics collaborate with physicians, patients, and other members of a primary care team to improve patient outcomes for a variety of conditions. An important part of the intervention is widespread use of an electronic health record (EHR). This EHR provides flexible access to clinical data, individualized decision support designed to encourage best practice for patients with a variety of diseases (including co-occurring ones), and convenient communication between providers. This generalized model is used to treat diverse patients with disparate and coexisting chronic conditions. Early results from the application of this model show improved patient outcomes and improved physician productivity. Success factors, challenges, and obstacles in implementing the model are discussed.

Adult↗

PubMed2005

A case for manual entry of structured, coded laboratory data from multiple sources into an ambulatory electronic health record.

Laboratory results provide necessary information for the management of ambulatory patients. To realize the benefits of an electronic health record (EHR) and coded laboratory data (e.g., decision support and improved data access and display), results from laboratories that are external to the health care enterprise need to be integrated with internal results. We describe the development and clinical impact of integrating external results into the EHR at Intermountain Health Care (IHC). During 2004, over 14,000 external laboratory results for 128 liver transplant patients were added to the EHR. The results were used to generate computerized alerts that assisted clinicians with managing laboratory tests in the ambulatory setting. The external results were sent from 85 different facilities and can now be viewed in the EHR integrated with IHC results. We encountered regulatory, logistic, economic, and data quality issues that should be of interest to others developing similar applications.

Ambulatory Care Information Systems↗

PubMed2005

Development of an information model for storing organ donor data within an electronic medical record.

OBJECTIVE: To develop a model to store information in an electronic medical record (EMR) for the management of transplant patients. The model for storing donor information must be designed to allow clinicians to access donor information from the transplant recipient's record and to allow donor data to be stored without needlessly proliferating new Logical Observation Identifier Names and Codes (LOINC) codes for already-coded laboratory tests. DESIGN: Information required to manage transplant patients requires the use of a donor's medical information while caring for the transplant patient. Three strategies were considered: (1) link the transplant patient's EMR to the donor's EMR; (2) use pre-coordinated observation identifiers (i.e., LOINC codes with *(wedge)DONOR specified in the system axes) to identify donor data stored in the transplant patient's EMR; and (3) use an information model that allows donor information to be stored in the transplant patient's record by allowing the "source" of the data (donor) and the "name" of the result (e.g., blood type) to be post-coordinated in the transplant patient's EMR. RESULTS: We selected the third strategy and implemented a flexible post-coordinated information model. There was no need to create new LOINC codes for already-coded laboratory tests. The model required that the data structure in the EMR allow for the storage of the "subject" of the test. CONCLUSION: The selected strategy met our design requirements and provided an extendable information model to store donor data. This model can be used whenever it is necessary to refer to one patient's data from another patient's EMR.

Databases as Topic↗

PubMed2005

Use and impact of a computer-generated patient summary worksheet for primary care.

Advanced clinical information systems have been proposed to improve patient care in terms of safety, effectiveness, and efficiency. In order to be effective, such systems require detailed patient-specific clinical information in a form easily reviewed by clinicians. We have developed a patient summary worksheet for use in outpatient clinics, which presents a structured overview of patient health information. The worksheet provides patient demographic information, specific problems and conditions, the patient's current medication profile, laboratory test results pertinent to patient problems, and disease-specific or preventive care actionable advisories. Usage has grown from a few hundred to over 25,000 unique patients per month during a two-year period. Diabetic patients for whom the worksheet is accessed are significantly more likely to be in compliance with accepted testing regimens for glycosolated hemoglobin (OR 1.47, 95% CI 1.28, 1.61).

Ambulatory Care Facilities↗

PubMed2004

Integrating detailed clinical models into application development tools.

Several groups are currently working on defining detailed clinical models (also called templates or archetypes) that are refinements of abstract medical models like the HL7 (Health Level Seven) Reference Information Model. At IHC, we have created over 3,000 detailed clinical models in the last five years. These models have become an essential part of the architecture of our electronic medical record (EMR) system. As a result, we have created an increasingly sophisticated set of tools that allow the models to be searched, viewed, and ultimately incorporated into medical applications. These browsers have some commonality with terminology browsers, but are distinct in that the explicit structure of the information models must be accommodated. In this paper we report our experience in making browsers for detailed clinical models that are integrated with application authoring tools.

Information Management↗

PubMed2003

Development of an information model for solid organ transplantation.

Information required to manage transplant patients and donors is complex, voluminous and requires the reporting and use of one person's medical information within another person's record. One strategy using a vocabulary model (i.e., LOINC codes with *DONOR specified in the system axes) will lead to problems with combinatorial explosion. After evaluating workflow processes, data collection forms, decision support and functional requirements, we designed and implemented an extendable information model to support the process of care following liver transplantation.

Decision Making, Computer-Assisted↗

PubMed2002

Using LOINC to link an EMR to the pertinent paragraph in a structured reference knowledge base.

Intermountain Health Care has integrated the electronic medical record (EMR) with online information resources in order to create easy access to a knowledge base which practicing physicians can use at the point of care. When a user is reviewing problems/diagnosis, medications, or clinical laboratory test results, they can conveniently access a "pertinent paragraph" of reference literature that pertains to the clinical data in the EMR. Using terminology first coined by Cimino1, we call this application the "infobutton." We describe the architectural issues involved in linking our electronic medical record with a structured laboratory knowledge base. The application has been well received as noted by anecdotal comments made by physicians and usage of the application.

Clinical Laboratory Techniques↗

PubMed2002

Using natural language processing to analyze physician modifications to data entry templates.

Efficient data entry by clinicians remains a significant challenge for electronic medical records. Current approaches have largely focused on either structured data entry, which can be limiting in expressive power, or free-text entry, which restricts the use of the data for automated decision support. Text-based templates are a semi-structured data entry method that has been used to assist physicians in manually entering clinical notes, by allowing them to edit predefined example notes. We analyzed changes made to 18,726 sentences from text templates, using a natural language processor. The most common changes were addition or deletion of normal observations, or changes in certainty. We identified common modifications that could be captured in structured form by a graphical user interface.

Medical Records Systems, Computerized↗