You are on page 1of 5

Journal of the American Medical Informatics Association Volume 16 Number 2 March / April 2009 153

AMIA Board White Paper 䡲


Perspectives
JAMIA on Informatics

Core Content for the Subspecialty of Clinical Informatics

REED M. GARDNER, PHD, J. MARC OVERHAGE, MD, PHD, ELAINE B. STEEN, MA,,
BENSON S. MUNGER, PHD, JOHN H. HOLMES, PHD, JEFFREY J. WILLIAMSON, DON E. DETMER, MD, MA,
FOR THE AMIA BOARD OF DIRECTORS

Abstract The Core Content for Clinical Informatics defines the boundaries of the discipline and informs
the Program Requirements for Fellowship Education in Clinical Informatics. The Core Content includes four major
categories: fundamentals, clinical decision making and care process improvement, health information systems, and
leadership and management of change. The AMIA Board of Directors approved the Core Content for Clinical
Informatics in November 2008.
䡲 J Am Med Inform Assoc. 2009;16:153–157. DOI 10.1197/jamia.M3045.

Background by the Robert Wood Johnson Foundation.2 In November


The Core Content for a medical subspecialty defines the 2008, the AMIA Board of Directors approved both the Core
boundaries of the discipline and informs the Program Re- Content and Program Requirements for clinical informatics.
quirements for Fellowship Education. Program Require-
ments identify the knowledge and skills that must be Definition and Description of the Subspecialty
mastered through the course of fellowship training and Clinical informaticians transform health care by analyzing,
specify accreditation requirements for training programs.1 designing, implementing, and evaluating information and
The American Board of Medical Specialties considers these communication systems that enhance individual and popula-
two documents along with other requirements and factors tion health outcomes, improve patient care, and strengthen the
when deciding whether to establish a new medical subspe- clinician-patient relationship.
cialty. The Core Content for Clinical Informatics is the result Clinical informaticians use their knowledge of patient care
of a two-year national development process initiated by the combined with their understanding of informatics concepts,
American Medical Informatics Association and supported methods, and tools to:
• assess information and knowledge needs of health care
Affiliations of the authors: Department of Medical Informatics, professionals and patients,
University of Utah (RMG), Salt Lake City, UT; Regenstrief Institute
and Indiana Health Information Exchange (JMO), Indianapolis, IN; • characterize, evaluate, and refine clinical processes,
American Medical Informatics Association (EBS, JJW, DED), Be- • develop, implement, and refine clinical decision support
thesda, MD; Arizona Emergency Medicine Research Center, Uni- systems, and
versity of Arizona (BSM), Tucson, AZ; Center for Clinical Epidemi- • lead or participate in the procurement, customization,
ology and Biostatistics, University of Pennsylvania School of development, implementation, management, evaluation,
Medicine (JHH), Philadelphia, PA; University of Virgina School of and continuous improvement of clinical information
Medicine (DED), Charlottesville, VA.
systems.
The American Medical Informatics Association (AMIA) Board of
Directors thanks the members of the Clinical Informatics Core Physicians who are board-certified in clinical informatics
Content team for their thoughtful and energetic discussions that collaborate with other health care and information technol-
resulted in this document. Team members included: Joan S. Ash, ogy professionals to promote patient care that is safe,
PhD, MBA; James J. Cimino, MD; H. Dominic Covvey, MSc; Reed efficient, effective, timely, patient-centered, and equitable.
M. Gardner (Chair), PhD; John H. Holmes, PhD; Nancy C. Nelson,
MS; J. Marc Overhage, MD, PhD (Vice Chair); Charles Safran, MS, As illustrated in Figure 1, clinical informatics encompasses
MD; Richard N. Shiffman, MD, MCIS; and Heiko Spallek, DMD, three spheres of activity:
PhD. AMIA acknowledges the contributions of over fifty reviewers
whose input strengthened the core content. AMIA thanks the • clinical care (i.e., the provision of clinical services to an
Robert Wood Johnson Foundation for generously supporting this individual patient),
project. • the health system (i.e., the structures, processes, and
Correspondence: Elaine B. Steen, MA, American Medical Informat- incentives that shape the clinical care environment; this
ics Association, 4915 St. Elmo Avenue, Suite 401, Bethesda, MD includes major health domains such as public health,
20814; e-mail: ⬍elainesteen@msn.com⬎. population health, personal health, health professional
Received for review: 10/21/2008; Accepted for publication: education, and clinical research, in addition to clinical
12/05/2008 care),
154 Gardner et al., Core Content for Clinical Informatics

methods, concepts, and tools to the practice of medicine.


Thus, they must understand the culture, boundaries, and
complexities of the field. Further, the stakeholders, struc-
tures, and processes that constitute the health system affect
the information and knowledge needs of health care profes-
sionals and influence the selection and implementation of
clinical information processes and systems. The flow of data,
information, and knowledge among the various domains of
the health system also creates important challenges for
clinical informaticians as many of the data used in public
health, personal health management, and clinical research
originate in the clinical domain and reside in clinical infor-
mation systems.
Clinical Decision Making and Care Process
Improvement
The second core content category comprises knowledge and
skills that enable a clinical informatician to implement
effective clinical decision making systems and participate in
the development of clinical processes that support effective,
efficient, safe, timely, and equitable patient-centered care.
F i g u r e 1. Domains of Clinical Informatics. A primary goal of clinical informaticians is to strengthen
clinical decision making by health care professionals and
• information and communications technology (i.e., the patients and to support and improve clinical care processes.
tools that enable the efficient capture, delivery, transmis- This goal depends on implementing systems that support
sion, and use of data, information, and knowledge and clinical objectives and, when necessary, identifying changes
the knowledge of how to apply those tools effectively). needed in clinical processes to take full advantage of clinical
information system capabilities.
Clinical informaticians work at the intersection of these
three domains, and must demonstrate mastery of: A range of theoretical and practical issues must be ad-
dressed in the development and implementation of clinical
• medical knowledge, decision support tools. The cognitive and scientific under-
• the field of informatics, pinnings of medical decision making must be understood to
• the health care environment, including how business capitalize on information system capabilities in improving
processes influence health care delivery and the flow of clinical processes. Design of robust clinical information
data among the major domains of the health system, systems and processes relies upon knowledge management
• how information systems and processes enhance or com- principles in acquiring, generating, representing, modeling,
promise the decision making and actions of health care and maintaining information to support clinical decision
team members, making. Further, to achieve the full benefits of information
• re-engineering health care processes, systems and processes, clinical informaticians must be able
• fundamental information system concepts, including the to conceptualize improvements in clinical processes and
life cycle of information systems, the constantly evolving decision making and collaborate with their clinical col-
capabilities of information technology and health care, leagues as well as information technology professionals to
and the technical and nontechnical issues surrounding implement changes in the information systems and clinical
system implementation, processes.
• how clinical information systems impact users and pa-
tients, how to support clinician users, and how to pro- Health Information Systems
mote clinician adoption of systems, The third core content category comprises knowledge and
• evaluation of information systems to provide feedback skills that enable a clinical informatician to participate in the
for system improvement, development or selection of an information system for
• leadership in organizational change, fostering collabora- clinicians, prepare clinicians before implementation and
tion, communicating effectively, and managing large support them during implementation and ongoing opera-
scale projects related to clinical information systems. tion of a clinical information system, and evaluate the
effectiveness of a system in meeting clinical needs.
The core content for the subspecialty of clinical informatics
comprises four major categories that must be mastered. Clinical informaticians need to assess the advantages and
disadvantages of various technological approaches and de-
Fundamentals termine the best fit for the clinical environment. They also
The first core content category comprises basic knowledge need a common vocabulary and shared knowledge base to
that provides clinical informaticians with a common vocab- collaborate with information technology personnel. Since
ulary and understanding of the environment in which they the quality of clinical data directly affects the effectiveness of
function. information systems and clinical decision support tools as
Clinical informaticians draw from the broader field of bio- well as the reliability of clinical research that depends on
medical and health informatics as they apply informatics those data, clinical informaticians work with interdiscipli-
Journal of the American Medical Informatics Association Volume 16 Number 2 March / April 2009 155

nary teams to ensure that the data used to make clinical 1.2. The Health System
decisions meet state-of-the-art standards. 1.2.1. Determinants of individual and population
Information systems are not limited to hardware and soft- health
ware; they include people, processes, and policies that 1.2.2. Primary domains, organizational structures,
support the use of the technology. Thus, clinical informati- cultures, and processes
cians must address these components as part of system 1.2.2.1. Health care delivery
analysis (planning) and implementation. System evaluation 1.2.2.2. Public health
is required to determine whether a clinical information 1.2.2.3. Clinical research
system is meeting its goals. Clinical informaticians need to 1.2.2.4. Education of health professionals
understand the full range of issues related to evaluation so 1.2.2.5. Personal health
1.2.3. The flow of data, information, and knowledge
that they can determine the appropriate evaluative methods
within the health system
and provide feedback for successful information system
1.2.4. Policy & regulatory framework
implementation and use.
1.2.5. Health economics and financing
There are myriad health information systems and these 1.2.6. Forces shaping health care delivery
systems are constantly evolving. Thus, the Core Content 1.2.7. Institute of Medicine quality components
identifies the common elements of health information sys- 1.2.7.1. Safety
tems used in different clinical settings and does not include 1.2.7.2. Effectiveness
an exhaustive list of clinical information systems. 1.2.7.3. Efficiency
Leadership and Management of Change 1.2.7.4. Patient-centeredness
The fourth core content category comprises knowledge and 1.2.7.5. Timeliness
skills that enable clinical informaticians to lead and manage 1.2.7.6. Equity
changes associated with the introduction and adoption of
2. Clinical Decision Making and Care Process Improve-
clinical information systems.
ment: The knowledge and skills that enable a clinical
Successful implementation of information systems requires informatician to implement effective clinical decision
behavioral, cultural, and social change within an organiza- making systems and participate in the development of
tion. Thus, clinical informaticians require knowledge and clinical processes that support effective, efficient, safe,
skills in understanding and analyzing organizational cul- timely, equitable, and patient-centered care.
ture, planning organizational change, building and working 2.1. Clinical Decision Support
in effective multidisciplinary teams, and leading informa- 2.1.1. The nature and cognitive aspects of human
tion system development and implementation. Clinical decision making
informaticians must be able to listen, understand needs, 2.1.1.1. General
articulate plans, explain rationales, inform constituents, re- 2.1.1.2. Medical
port results, and foster collaboration. They must relate 2.1.2. Decision science
clinical information system needs and plans to larger orga- 2.1.2.1. Decision analysis
nizational strategic goals and be proficient in project man- 2.1.2.2. Probability theory
agement to oversee the implementation of new systems and 2.1.2.3. Utility and preference assessment
processes. 2.1.2.4. Cost effectiveness analysis
2.1.2.5. Test characteristics (e.g., sensitivity,
Core Content specificity, predictive value)
1. Fundamentals: The basic knowledge that provides clini- 2.1.3. Application of clinical decision support
cal informaticians with a common vocabulary and under- 2.1.3.1. Types of decision support (e.g., alerts,
standing of the environment in which they function. reminders, prompts)
1.1. Clinical Informatics 2.1.3.2. Users of decision support (including
1.1.1. The discipline of informatics clinicians and patients)
1.1.1.1. Definitions of informatics 2.1.3.3. Implementing, evaluating, and main-
1.1.1.2. History of informatics (e.g., evolution taining decision support tools
2.1.4. Transformation of knowledge into clinical de-
of health records)
cision support tools
1.1.1.3. Domains/subspecialties of informat-
2.1.4.1. Knowledge generation
ics
2.1.4.2. Knowledge acquisition
1.1.1.4. Careers in informatics
2.1.4.3. Knowledge modeling
1.1.1.5. Professional organizations
2.1.4.4. Knowledge representation
1.1.1.6. Current and future challenges for
2.1.4.5. Knowledge management and
informatics
1.1.2. Key informatics concepts, models, and theo- maintenance
2.1.5. Legal, ethical, and regulatory issues
ries
2.1.6. Quality and safety issues
1.1.3. Clinical informatics literature
2.1.7. Supporting decisions for populations of pa-
1.1.3.1. Core literature
tients
1.1.3.2. Critical analysis of informatics literature
1.1.4. International clinical informatics practices 2.2. Evidence-based Patient Care
1.1.5. Ethics and professionalism 2.2.1. Evidence sources
1.1.6. Legal and regulatory issues 2.2.2. Evidence grading
156 Gardner et al., Core Content for Clinical Informatics

2.2.3. Clinical guidelines 3.2. Human Factors Engineering


2.2.4. Implementation of guidelines as clinical algo- 3.2.1. Models, theories, and practices of human-
rithms computer (machine) interaction (HCI)
2.2.5. Information retrieval and analysis 3.2.2. HCI Evaluation, usability testing, study de-
2.2.5.1. Search skills sign and methods
2.2.5.2. Critical analysis of biomedical literature 3.2.3. Interface design standards and design principles
3.2.4. Usability engineering
2.3. Clinical Workflow Analysis, Process Redesign, and
Quality Improvement 3.3. Health Information Systems and Applications
2.3.1. Methods of workflow analysis 3.3.1. Types of functions offered by systems
2.3.2. Principles of workflow re-engineering 3.3.2. Types of settings where systems are used
2.3.3. Quality improvement principles and practices 3.3.3. Electronic health/medical records systems as
the foundational tool
3. Health Information Systems: The knowledge and skills 3.3.4. Telemedicine
that enable a clinical informatician to participate in the
development or selection of an information system for 3.4. Clinical Data Standards
clinicians; prepare clinicians prior to implementation and 3.4.1. Standards development history and current
support them during implementation and ongoing oper- process
ation of a clinical information system; and evaluate the 3.4.2. Data standards and data sharing
effectiveness of a system in meeting clinical needs. 3.4.3. Transaction standards
3.1. Information Technology Systems 3.4.4. Messaging standards
3.1.1. Computer Systems 3.4.5. Nomenclatures, vocabularies, and terminologies
3.1.1.1. Programming 3.4.6. Ontologies and taxonomies
3.1.1.2. Data and control structures 3.4.7. Interoperability standards
3.1.1.3. Software development methods (e.g.,
agile, waterfall, spiral, rapid prototyp- 3.5. Information System Lifecycle
ing) 3.5.1. Institutional governance of clinical informa-
3.1.1.4. System integration tion systems
3.1.1.5. Quality 3.5.2. Clinical information needs analysis and sys-
3.1.1.6. Information systems design and analy- tem selection
sis (e.g., logical schema, normalization/ 3.5.2.1. Methods for identifying clinician in-
denormalization, process modeling) formation system needs
3.5.2.2. Assessment of clinical process changes
3.1.2. Architecture that will be required
3.1.2.1. Systems (e.g., distributed, centralized, 3.5.2.3. Elements of a system requirements
relational, object oriented, warehouses/ specification document (e.g., technical
data marts) specifications, intellectual property,
3.1.2.2. Networks patents, copyright, licensing, contract-
3.1.2.3. Data/database ing, confidentiality, specific organiza-
tional needs such as user training and
3.1.3. Networks support)
3.1.3.1. Topologies 3.5.2.4. Risk analysis and mitigation
3.1.3.2. Telecommunications 3.5.2.5. The costs of health information and
communications technologies
3.1.4. Security
3.1.4.1. The HIPAA Security Rule and other 3.5.3. Clinical information system implementation
government regulations 3.5.3.1. Elements of a system implementation
3.1.4.2. Firewalls plan
3.1.4.3. Virtual private networks 3.5.3.2. Models of user training and support
3.1.4.4. Encryption processes that can meet clinician
needs
3.1.5. Data 3.5.3.3. Processes and mechanisms that obtain
3.1.5.1. Integrity and respond to clinician feedback
3.1.5.2. Mapping
3.1.5.3. Manipulation (e.g., querying, SQL, re- 3.5.4. Clinical information system testing, before,
porting) during and after implementation
3.1.5.4. Representation and types 3.5.5. Clinical information system maintenance
3.1.5.5. Warehousing 3.5.5.1. Disaster recovery and downtime
3.1.5.6. Data mining and knowledge discovery 3.5.5.2. Clinical information system transitions
and decommissioning of systems
3.1.6. Technical approaches that enable sharing data
3.1.6.1. Integration versus interfacing 3.5.6 Clinical information system evaluation
3.1.6.2. Dealing with multiple identifiers 3.5.6.1. Outcomes relevant to the clinical goals
3.1.6.3. Anonymization of data and quality measures
Journal of the American Medical Informatics Association Volume 16 Number 2 March / April 2009 157

3.5.6.2. Qualitative and quantitative methods for 4.4. Project Management


evaluating clinical information systems 4.4.1. Basic principles
3.5.6.3. Evaluation plan design 4.4.2. Identifying resources
4.4.3. Resource allocation
4. Leading and Managing Change: The knowledge and
4.4.4. Project management tools (non-software spe-
skills that enable clinical informaticians to lead and
cific)
manage changes associated with implementing clinical
4.4.5. Informatics project challenges
information systems and promoting adoption by health
4.4.5.1. Scope creep
professionals.
4.4.5.2. Managing expectations
4.1. Leadership Models, Processes, and Practices
4.4.5.3. Balancing competing priorities
4.1.1. Dimensions of effective leadership
4.1.2. Governance (e.g., processes; responsibility 4.5. Strategic and Financial Planning for Clinical Infor-
versus authority) mation Systems
4.1.3. Negotiation 4.5.1. Establishing mission and objectives
4.1.4. Conflict management 4.5.2. Environmental scanning
4.1.5. Collaboration 4.5.3. Strategy formulation
4.1.6. Motivation 4.5.4. Action planning and strategy implementation
4.1.7. Decision making 4.5.5. Capital and operating budgeting
4.5.6. Principles of managerial accounting
4.2. Effective Interdisciplinary Teams
4.5.7. Evaluation of planning process
4.2.1. Human resources management (e.g., hiring,
performance reviews and feedback, profes- 4.6. Change Management
sional development, termination) 4.6.1. Assessment of organizational culture and be-
4.2.2. Team productivity and effectiveness (e.g., ar- havior
ticulating team goals, defining rules of opera- 4.6.2. Change theories (e.g., precede-proceed, social
tion, clarifying individual roles) influence theories, complex adaptive systems)
4.2.3. Group management processes (e.g., nominal 4.6.3. Change management strategies
group, consensus mapping, Delphi method) 4.6.4. Strategies for promoting adoption and effec-
4.2.4. Managing meetings tive use of clinical information systems
4.2.5. Managing group deliberations
References y
4.3. Effective Communications
1. Safran C, Shabot MM, Munger BS, Holmes JH, Steen EB,
4.3.1. Effective presentations to groups
Lumpkin JR, et al. Program Requirements for Fellowship Edu-
4.3.2. Effective one-on-one communication cation in the Subspecialty of Clinical Informatics. J Am Med
4.3.3. Writing effectively for various audiences and Informatics Assoc 2009;16:158-166.
goals 2. Detmer DE, Lumpkin JR, Williamson JJ. Defining the Medical
4.3.4. Developing effective communications pro- Subspecialty of Clinical Informatics. J Am Med Informatics
gram to support system implementation Assoc 2009;16:167-168.

You might also like