Ambulatory EHR functionality: a comparison of functionality lists.

Abstract

There is a proliferation of lists intended to define and clarify the functionality of an ambulatory electronic health record system. These lists come from both private and public entities and vary in terminology, granularity, usability, and comprehensiveness. For example, functionality regarding a problem list includes the following possible definitions: * "Create and maintain patient-specific problem lists," from the HL7 Electronic Health Record Draft Standard for Trial Use. * "Provide a flexible mechanism for retrieval of encounter information that can be organized by diagnosis, problem, problem type," from the Bureau of Primary Health Care. * "The system shall associate encounters, orders, medications and notes with one or more problems," from the Certification Commission on Health Information Technology. * "Displays dates of problems on problem list," from COPIC Insurance Co. * "Shall automatically close acute problems using an automated algorithm," from the Physicians Foundations HIT Subcommittee. This article will compare the attributes of these five electronic health record functionality lists and their usefulness to different audiences-clinicians, application developers and payers.