Standards for detailed clinical models as the basis for medical data exchange and decision support.Int J Med Inform, Vol. 69, No. 2-3. (March 2003), pp. 157-174.
|
Reviews
[Write a review of this article]
There are no reviews of this article
Find related articles from these CiteULike users
Find related articles with these CiteULike tags
AbstractINTRODUCTION: 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.
BibTeX record
RIS record