Search PubMed⌕ Search

SEARCH · Search PubMed

Results for “Medical Records Systems, Computerized”

Search indexed PubMed citations on genomics, clinical trials, systematic reviews and public health. Explore titles, authors and supplied subject terms, then open the PubMed record.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 127 records · Page 7Linked to original sources

A comparison of problem lists generated by physicians, nurses, and patients: implications for CPR systems.

Using a sample of 201 patients hospitalized for Pneumocystis carinii pneumonia, this study describes problem lists generated by physicians and examines the overlap among problem lists generated by physicians, nurses, and patients. The findings indicate that the majority of patients in this sample had at least one problem that occurred in more than one problem list. Problems that most frequently appeared in more than one problem list were those related to the medical diagnosis of Pneumocystis carinii pneumonia and its associated physiological symptoms. Problems which occurred uniquely in the nurse problem list were knowledge deficit and potential for injury. Thirty-four percent of the patients identified at least one psychosocial problem that did not occur in either the physician- or nurse-generated problem lists. The study findings demonstrate that while there is overlap among the problem lists in problems related to the principal medical diagnoses, the nurse- and patient-generated problem lists include unique problems which provide additional significant information related to patient status that has the potential to impact patient outcomes. These findings suggest that a unified, nonredundant, multidisciplinary problem list is warranted in order to provide a comprehensive view of the patient for computer-based patient record (CPR) systems. Appropriate data models and comprehensive controlled vocabularies are needed to support the multiple uses of the problem list for CPR systems.

Humans↗

Representation of clinical problem assessment phrases in U.S. family practice using Read version 3.1 terms: a preliminary study.

The Read Codes from the United Kingdom are a comprehensive clinical vocabulary, and one of the most likely candidates for adoption as a standard for use in Computer-Based Patient Record (CPR) systems. The new version 3.1 codes represent a major enhancement to the content and structure of the coding system, including incorporation of a new hierarchy and an explicit model for the use of qualifier terms. This is a preliminary study investigating the suitability of these codes for representing clinical problem assessment phrases in U.S. family practice. Problem assessment phrases from outpatient progress notes were encoded into the equivalent Read terms. The problem assessment phrases were evaluated for complexity and clarity. The coded representations of the phrases were evaluated for clinical acceptability. A list of coding difficulties was compiled. The most common difficulties were (1) qualifier terms present but not allowable for that Read concept (24%), and (2) qualifier terms not present (20%). British spelling and abbreviation variants were noted, but were relatively insignificant. The Read codes appear to be suitable for use in U.S. primary care practice with fairly minor modifications, but further development is required to expand the content and structure of the model for qualifier terms.

Family Practice↗

Health record problem-oriented information system.

Health Record refers to the recording of the medical and relevant social history of the patient, obtained directly or indirectly. It is an instrument of frequent use that must guarantee the quality of assistance provided, reflecting all information pertinent to forming the patient's medical history. It must be designed so that data is easily and effectively retrieved for everyday use, without compromising the patient's privacy. The Health Record Problem Oriented model achieves all of these objectives. This model comprises: 1. Initial data: the relevant medical histories and biography is recorded. 2. Problems list: the patient provides reasons why she is seeking medical attention. 3. Performance plans: these include diagnostic, therapeutic, pharmacological, dietetic, physiotherapist, and surgical plans, as well as the education of the patient. 4. Evolution notes: the progress of the condition. This model guarantees multi-professional registration, an integral focus on the health, and a continued focus on the patient. These characteristics make it the model par excellence of Primary Care. Prior to the implementation of this model, existing information must be analyzed so that it can eventually be converted to a relational database. The Entity-Relationship Model (E/R Model) has been used to represent the database. Here, the basic concepts involved are entities, relationships, and attributes. Entities represent classes or objects from the real world that have common characteristics. The relationships represent the aggregation of two or more entities. The attributes are elemental properties of both entities and relationships. The E/R Diagram graphically represents the conceptual model of a database; the one built for the Health Record Problem Oriented reflects all the entities that compound the attending processes and the relationships existing between them. The Patient is the central axis of the attending process. The record contains the identifying data of the subject and his habits. We can know his medical history by means of his past Illness (personal and family record), Vaccine (what he is vaccinated against), and Case History (each patient has a case history). The other important component is the Consult Motive. A patient has a reason for every consultation, and this reason is added to her medical history as part of the Consult Motive. Each consult motive produces different events that are shown as relations with the other entities. So, for example, by analyzing a patient's history of complaints, a doctor can more suitably determine if she should recommend Cardiac or Anthropometric Exploration, request an Analysis, request a Radiography or Specialist Report, or prescribe a Treatment. The various elements that are part of a Consult Motive are expressed as different entities. Once the conceptual schema of the database is defined, the next step is to convert this schema to a logical schema, suitable for the Relational Model.

Medical Records Systems, Computerized↗

Seven years experience with a computerized diabetes clinic database.

With the emergence of information technology applications in medicine, a computerized medical record system that could be used to : (1) maintain patients' clinical records over time, (2) communicate with referring practitioners, and (3) form the basis of a potential research database of information, was sought. In 1987, we developed such a clinical database to register patients attending our busy Diabetes Clinic, now seeing in excess of 300 new referrals and, on average, 3,000 clinic visits per year. Baseline demographic data, clinical history, and examination and investigation results are recorded. We also record diabetes therapy and other medication dosage and changes, monitor follow-up, assess health outcome information (such as stroke or amputation), and generate results, summaries, and reports to referring practitioners and other health professionals. We now have almost seven years of experience using the system. Initially established on a single PC with paper-based data collection and subsequent data entry (running as a DOS application), it is now established on a PC Local Area Network [LAN] with terminals in the clinic consultation rooms enabling direct data entry and allowing patients to view their results in graphic form on screen. From its inception, the Diabetes Clinic Database System has maintained patient demographic and clinical data (which facilitates efficient clinic management) with patient clinic lists and adhesive address labels generated from appropriate menus. Batch mode processing produces daily work sheets which facilitate the running of clinics as well as ad hoc, daily, and weekly reports for all patients (as required). This expedites correspondence with referring doctors. A quality assurance report to the clinic doctor highlights missing clinical information which must be obtained in order to ensure data completeness. The initial system was relatively inefficient in that it required data entry following patient consultation and provided no immediate feedback to patients themselves. In January 1994, to address these deficiencies, the system was established on a PC LAN (running under Novell); it provided on-line data entry within the clinic setting and enabled patients to participate in the recording of their information, observe their own progress by way of on-screen graphs (e.g., blood sugar control, weight, cholesterol), and receive hand-held summaries generated immediately following the clinic visit. Batch programs generate hard copies of this data to be filed in medical records. Two major assessments of the system have been undertaken. In February 1990, we undertook a survey of Local Doctors with 5 or more patient referrals on the system; this resulted in a pleasing 66% response rate. There was an almost universal acceptance and indeed a significant preference for this system over 'traditional' letters. In January 1994, following the introduction of the system onto the PC LAN for direct data entry in the clinic setting, we assessed (by anonymous questionnaire at the end of the consultation) patient attitudes towards these changes. The development of the CRS Diabetes Clinic Database System has improved our approach to diabetes outpatient care and our communication with other health professionals. It has the added benefit of providing a database of information that is suitable to address critical clinical research issues in diabetes management. This system provides an acceptable blend of information technology and clinical medicine, redesigning and enhancing the way we deliver medical care to patients with diabetes. Involving the patient in the collection and interpretation of their clinical data via a computer system (as utilized within our clinical unit), is both acceptable to the patient and her referring doctor. Ongoing system refinement and assessment remains integral to our use of information technology.

Australia↗

A standards-based clinical information system for HIV/AIDS.

OBJECTIVE: To create a clinical data repository to interface the Veteran's Administration (VA) Decentralized Hospital Computer Program (DHCP) and a departmental clinical information system for the management of HIV patients. This system supports record-keeping, decision-making, reporting, and analysis. The database development was designed to overcome two impediments to successful implementations of clinical databases: (i) lack of a standard reference data model, and; (ii) lack of a universal standard for medical concept representation. BACKGROUND: Health Level Seven (HL7) is a standard protocol that specifies the implementation of interfaces between two computer applications (sender and receiver) from different vendors or sources of electronic data exchange in the health care environment. This eliminates or substantially reduces the custom interface programming and program maintenance that would otherwise be required. HL7 defines the data to be exchanged, the timing of the interchange, and the communication of errors to the application. The formats are generic in nature and must be configured to meet the needs of the two applications involved. The standard conceptually operates at the seventh level of the ISO model for Open Systems Interconnection (OSI). The OSI simply defines the data elements that are exchanged as abstract messages, and does not prescribe the exact bit stream of the messages that flow over the network. Lower level network software developed according to the OSI model may be used to encode and decode the actual bit stream. The OSI protocols are not universally implemented and, therefore, a set of encoding rules for defining the exact representation of a message must be specified. The VA has created an HL7 module to assist DHCP applications in exchanging health care information with other applications using the HL7 protocol. The DHCP HL7 module consists of a set of utility routines and files that provide a generic interface to the HL7 protocol for all DHCP applications. SETTING: The VA's DHCP core modules are in standard use at 169 hospitals, and the role of the VA system in health care delivery has been discussed elsewhere. This development was performed at the Miami VA Medical Center Special Immunology Unit, where a database was created for an HIV patient registry in 1987. Over 2,300 patient have been entered into a database that supports a problem-oriented summary of the patient's clinical record. The interface to the VA DHCP was designed and implemented to capture information from the patient treatment file, pharmacy, laboratory, radiology, and other modules. RESULTS: We obtained a suite of programs for implementing the HL7 encoding rules from Columbia-Presbyterian Medical Center in New York, written in ANSI C. This toolkit isolates our application programs from the details of the HL7 encoding rules, and allows them to deal with abstract messages and the programming level. While HL7 has become a standard for healthcare message exchange, SQL (Structured Query Language) is the standard for database definition, data manipulation, and query. The target database (Stitt F.W. The Problem-Oriented Medical Synopsis: a patient-centered clinical information system. Proc 17 SCAMC. 1993:88-93) provides clinical workstation functionality. Medical concepts are encoded using a preferred terminology derived from over 15 sources that include the Unified Medical Language System and SNOMed International ( Stitt F.W. The Problem-Oriented Medical Synopsis: coding, indexing, and classification sub-model. Proc 18 SCAMC, 1994: in press). The databases were modeled using the Information Engineering CASE tools, and were written using relational database utilities, including embedded SQL in C (ESQL/C). We linked ESQL/C programs to the HL7 toolkit to allow data to be inserted, deleted, or updated, under transaction control. A graphical format will be used to display the entity-rel

Acquired Immunodeficiency Syndrome↗

Automated classification of encounter notes in a computer based medical record.

Harvard Community Health Plan is exploring emerging information technologies for means to use the text portion of its 25 year old computerized medical record system. The Center for Intelligent Information Retrieval is developing systems to answer the question: to what extent can automated information systems replace manual chart review of encounter notes? INQUERY, a probabilistic inference net information retrieval system, and FIGLEAF, an inductive decision tree text classifier are applied to the problem of classifying electronic encounter notes to identify acute exacerbations in pediatric asthmatics. Both systems achieve average precisions of greater than 80%, with a new enhancement to INQUERY's relevance feedback, the top performer. Refinement of the systems and plans for their integration are discussed.

Asthma↗

A shared computer-based problem-oriented patient record for the primary care team.

1. INTRODUCTION. A computer-based patient record (CPR) system, Swedestar, has been developed for use in primary health care. The principal aim of the system is to support continuous quality improvement through improved information handling, improved decision-making, and improved procedures for quality assurance. The Swedestar system has evolved during a ten-year period beginning in 1984. 2. SYSTEM DESIGN. The design philosophy is based on the following key factors: a shared, problem-oriented patient record; structured data entry based on an extensive controlled vocabulary; advanced search and query functions, where the query language has the most important role; integrated decision support for drug prescribing and care protocols and guidelines; integrated procedures for quality assurance. 3. A SHARED PROBLEM-ORIENTED PATIENT RECORD. The core of the CPR system is the problem-oriented patient record. All problems of one patient, recorded by different members of the care team, are displayed on the problem list. Starting from this list, a problem follow-up can be made, one problem at a time or for several problems simultaneously. Thus, it is possible to get an integrated view, across provider categories, of those problems of one patient that belong together. This shared problem-oriented patient record provides an important basis for the primary care team work. 4. INTEGRATED DECISION SUPPORT. The decision support of the system includes a drug prescribing module and a care protocol module. The drug prescribing module is integrated with the patient records and includes an on-line check of the patient's medication list for potential interactions and data-driven reminders concerning major drug problems. Care protocols have been developed for the most common chronic diseases, such as asthma, diabetes, and hypertension. The patient records can be automatically checked according to the care protocols. 5. PRACTICAL EXPERIENCE. The Swedestar system has been implemented in a primary care area with 30,000 inhabitants. It is being used by all the primary care team members: 15 general practitioners, 25 district nurses, and 10 physiotherapists. Several years of practical experience of the CPR system shows that it has a positive impact on quality of care on four levels: 1) improved clinical follow-up of individual patients; 2) facilitated follow-up of aggregated data such as practice activity analysis, annual reports, and clinical indicators; 3) automated medical audit; and 4) concurrent audit. Within that primary care area, quality of care has improved substantially in several aspects due to the use of the CPR system [1].

Ambulatory Care Information Systems↗

Medical records and other stories: a narratological framework.

A new model of the medical record is introduced which can incorporate context, structure, process and use of the medical record within a single narratological framework. It is claimed that the analysis of narrative and, in particular, the study of the story metaphor can provide a theoretical model which provides coherence within the broad discipline of Medical Informatics. It is argued that this framework maintains different levels of abstraction, is useful for teaching and clinical practice, and that its concepts can be readily understood by those in both lay and technical healthcare professions.

Communication↗

The medical record: narration and story as a path through patient data.

Kay and Purves' proposed narratological model of the medical record is based on the familiar phenomenological insight that the perception of data is conditioned by the conceptual framework of the perceiver. Unfortunately, unless handled very carefully, this approach will make the significance of a medical record unique to the person who constructed it and impermeable to outside scrutiny. However, when integrated into the analog-model of the medical record, the narratological model can be accommodated as the clinician-relative construction of a patient profile within the data that make up the medical record. Some implications for the construction of expert systems and competence analysis are indicated.

Data Collection↗

Clinical similarities and demographic differences between residency and private practice patients.

BACKGROUND: This study compared the clinical and demographic mix of patients at a family practice residency site in South Carolina to those from other regions and demonstrated the effectiveness of a computerized medical record in facilitating such analysis. METHODS: Patient visits to Richland Family Practice Center (RFP), the outpatient care site for the University of South Carolina School of Medicine, were retrospectively sampled for the period July 1992-June 1993. Data analysis used descriptive statistics and contingency tables. A time test comparing manual and computerized data retrieval was also performed. RESULTS: The patients seen were predominantly female (75.2%) and African-American (68%). RFP treated proportionately more federally funded and minority patients than did community-based physicians. The top five principal diagnoses at RFP were hypertension, diabetes mellitus, general medical examination, normal pregnancy, and acute upper respiratory infection; the top 20 principal diagnoses accounted for 51.3% of all visits. When compared to the top 20 diagnoses for all family and general practice physicians in the southern United States, considerable overlap was present, confirming clinical similarity between patient populations at residency and private practice sites. Computerized data retrieval was faster and more complete than manual data retrieval. CONCLUSIONS: Diagnoses encountered at RFP and reported by other family practice residencies generally parallel those documented in family practice in various geographic regions. However, residencies differ from private practices in that they care for more economically disadvantaged patients. Computerized medical records systems facilitate research within a residency program.

Adolescent↗

[Difficulties in quality of health evaluations in the context of an African hospital: experience of the Gynecology-Obstetrics Department of the National Hospital Center of Ouagadougou,Burkina Faso].

The quality of medical care was studied in the gyneco-obstetrical department of the National Hospital Center of Ouagadougou, Burkina Faso. Evaluation covered not only facilities, procedures and results, but also patient satisfaction using standardized criteria. The results showed an apparent contradiction between poor facilities and high maternal and prenatal mortality rate on the one hand and proper use of procedures and good patient satisfaction on the other. Installation of a computerized medical record system should allow continuous monitoring of the quality of care in the context of a sub-Saharan hospital by providing ready access to simple standardized indicators especially of maternal and prenatal mortality.

Adolescent↗

Medical records: past, present, and future.

This paper considers the lessons learnt during the development of the electronic medical record for patient care. It is not a definitive history of medical records but an assessment of what has been learnt, what has to be learnt and how we can move forward. It considers the needs for structured intelligent records that help in individual patient care, the need to provide functionality that fits with the requirements of the clinician-patient interaction and the need to take into account the human factors that affect clinician's uptake of such systems. It outlines the issues of free form input as opposed to controlled input that have to be resolved.

Attitude of Health Personnel↗

Taking the problem oriented medical record forward.

The problem oriented medical record (POMR) has proved to be very successful in providing a structure that helps doctors record their notes about patients, and view those notes subsequently in a manner that quickly gives them a good understanding of that patients history. This approach has been validated by the American Institute of Medicine. With the increased use of computer systems that implement the POMR by doctors, the limitations of this structure have become apparent, and there is clearly scope for developing the model further to improve the quality of the data recorded, and adding meaning to it. This paper describes some of the limitations of the POMR, and discusses a number of areas in which it may be extended. Crucially, this is done in a manner which is both implementable, and usable. The extensions explored include some types of entity including encounters, episodes and subproblems; and an alternative view-the Timeline. The terminology used for the extensions is clarified. Mechanisms by which these extensions have been implemented are described. Ways in which systems can manage these extensions automatically are suggested. Such implementations are constrained by the need not to allow the demands of the computer to intrude into the patient encounter. They are also constrained by the requirements for reporting by professional and governmental institutions, and by what is pragmatically feasible in software and hardware.

Computer Systems↗

Clinical care management and workflow by episodes.

This paper describes the implementation of clinically defined episodes of care and the introduction of an episode-based summary list of patient problems across Mayo Clinic Rochester in 1996 and 1997. Although Mayo's traditional paper-based system has always relied on a type of 'episode of care' (called the "registration") for patient and history management, a new, more clinically relevant definition of episode of care was put into practice in November 1996. This was done to improve care management and operational processes and to provide a basic construct for the electronic medical record. Also since November 1996, a computer-generated summary list of patient problems, the "Master Sheet Summary Report," organized by episode, has been placed in all patient histories. In the third quarter of 1997, the ability to view the episode-based problem summary online was made available to the 3000+ EMR-capable workstations deployed across the Mayo Rochester campus. In addition, the clinically oriented problem summarization process produces an improved basic "package" of clinical information expected to lead to improved analytic decision support, outcomes analysis and epidemiological research.

Episode of Care↗