Standards for detailed clinical models as the basis for medical data exchange and decision support

Introduction: Detailed clinical models are necessary to exchange medical data between heterogeneous computer systems and to maintain consistency in a longitudinal electronic medical record system. At Intermountain Health Care (IHC), we have a history of designing detailed clinical models. The purpos...

Full description

Saved in:
Bibliographic Details
Published in:International journal of medical informatics 2003-03, Vol.69 (2), p.157-174
Main Authors: Coyle, Joseph F., Mori, Angelo Rossi, Huff, Stanley M.
Format: Article
Language:English
Subjects:
Archetypes
Biological and medical sciences
Clinical models
Decision support
Decision Support Systems, Clinical - standards
Electronic medical record
Humans
Information models
Medical data exchange standards
Medical Informatics
Medical Record Linkage - methods
Medical Records Systems, Computerized - standards
Medical sciences
Medical terminology
Models, Organizational
Programming Languages
Systems Integration
Templates
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Introduction: Detailed clinical models are necessary to exchange medical data between heterogeneous computer systems and to maintain consistency in a longitudinal electronic medical record system. At Intermountain Health Care (IHC), we have a history of designing detailed clinical models. The purpose of this paper is to share our experience and the lessons we have learned over the last 5 years. Design: IHC's newest model is implemented using eXtensible Markup Language (XML) Schema as the formalism, and conforms to the Health Level Seven (HL7) version 3 data types. The centerpiece of the new strategy is the Clinical Event Model, which is a flexible name–value pair data structure that is tightly linked to a coded terminology. Discussion: We describe IHC's third-generation strategy for representing and implementing detailed clinical models, and discuss the reasons for this design.
ISSN:1386-5056
1872-8243
DOI:10.1016/S1386-5056(02)00103-X