This Article Full Text Full Text (PDF) All Versions of this Article: M1957v1 13/3/277    most recent Submit a response Alert me when this article is cited Alert me when eLetters are posted Alert me if a correction is posted Services Similar articles in this journal Similar articles in PubMed Alert me to new issues of the journal Download to citation manager Citing Articles Citing Articles via HighWire Citing Articles via Google Scholar Google Scholar Articles by Rosenbloom, S. T. Articles by Brown, S. H. Search for Related Content PubMed PubMed Citation Articles by Rosenbloom, S. T. Articles by Brown, S. H.

Interface Terminologies: Facilitating Direct Entry of Clinical Data into Electronic Health Record Systems

Affiliations of the authors: Departments of Biomedical Informatics (STR, RAM, KBJ, SHB) and Pediatrics (STR, KBJ), School of Nursing (STR, RAM), Vanderbilt University, Nashville, TN; Mayo Foundation for Medical Education and Research, Rochester, MN (PLE); U.S. Department of Veterans Affairs, Nashville, TN (SHB).

Correspondence and reprints: S. Trent Rosenbloom; e-mail: <trent.rosenbloom{at}vanderbilt.edu>.

Received for publication: 08/31/05; accepted for publication: 01/09/06.

Previous investigators have defined clinical interface terminology as a systematic collection of health care–related phrases (terms) that supports clinicians' entry of patient-related information into computer programs, such as clinical "note capture" and decision support tools. Interface terminologies also can facilitate display of computer-stored patient information to clinician-users. Interface terminologies "interface" between clinicians' own unfettered, colloquial conceptualizations of patient descriptors and the more structured, coded internal data elements used by specific health care application programs. The intended uses of a terminology determine its conceptual underpinnings, structure, and content. As a result, the desiderata for interface terminologies differ from desiderata for health care–related terminologies used for storage (e.g., SNOMED-CT^®), information retrieval (e.g., MeSH), and classification (e.g., ICD9-CM^®). Necessary but not sufficient attributes for an interface terminology include adequate synonym coverage, presence of relevant assertional knowledge, and a balance between pre- and post-coordination. To place interface terminologies in context, this article reviews historical goals and challenges of clinical terminology development in general and then focuses on the unique features of interface terminologies.

This article has been cited by other articles:

				J. L. Schnipper, J. A. Linder, M. B. Palchuk, J. S. Einbinder, Q. Li, A. Postilnik, and B. Middleton "Smart Forms" in an Electronic Medical Record: Documentation-based Clinical Decision Support to Improve Disease Management J. Am. Med. Inform. Assoc., July 1, 2008; 15(4): 513 - 523. [Abstract] [Full Text] [PDF]

				S. T. Rosenbloom, R. A. Miller, K. B. Johnson, P. L. Elkin, and S. H. Brown A Model for Evaluating Interface Terminologies J. Am. Med. Inform. Assoc., January 1, 2008; 15(1): 65 - 76. [Abstract] [Full Text] [PDF]

				J. E. Andrews, R. L. Richesson, and J. Krischer Variation of SNOMED CT Coding of Clinical Research Concepts among Coding Experts J. Am. Med. Inform. Assoc., July 1, 2007; 14(4): 497 - 506. [Abstract] [Full Text] [PDF]

				S. A. Spooner and and the Council on Clinical Information Technology Special Requirements of Electronic Health Record Systems in Pediatrics Pediatrics, March 1, 2007; 119(3): 631 - 637. [Abstract] [Full Text] [PDF]

				R. L. Richesson, J. E. Andrews, and J. P. Krischer Use of SNOMED CT to Represent Clinical Research Data: A Semantic Characterization of Data Items on Case Report Forms in Vasculitis Research J. Am. Med. Inform. Assoc., September 1, 2006; 13(5): 536 - 546. [Abstract] [Full Text] [PDF]