A core curriculum for clinical fellowship training in pathology informatics

Background: In 2007, our healthcare system established a clinical fellowship program in Pathology Informatics. In 2010 a core didactic course was implemented to supplement the fellowship research and operational rotations. In 2011, the course was enhanced by a formal, structured core curriculum and reading list. We present and discuss our rationale and development process for the Core Curriculum and the role it plays in our Pathology Informatics Fellowship Training Program. Materials and Methods: The Core Curriculum for Pathology Informatics was developed, and is maintained, through the combined efforts of our Pathology Informatics Fellows and Faculty. The curriculum was created with a three-tiered structure, consisting of divisions, topics, and subtopics. Primary (required) and suggested readings were selected for each subtopic in the curriculum and incorporated into a curated reading list, which is reviewed and maintained on a regular basis. Results: Our Core Curriculum is composed of four major divisions, 22 topics, and 92 subtopics that cover the wide breadth of Pathology Informatics. The four major divisions include: (1) Information Fundamentals, (2) Information Systems, (3) Workflow and Process, and (4) Governance and Management. A detailed, comprehensive reading list for the curriculum is presented in the Appendix to the manuscript and contains 570 total readings (current as of March 2012). Discussion: The adoption of a formal, core curriculum in a Pathology Informatics fellowship has significant impacts on both fellowship training and the general field of Pathology Informatics itself. For a fellowship, a core curriculum defines a basic, common scope of knowledge that the fellowship expects all of its graduates will know, while at the same time enhancing and broadening the traditional fellowship experience of research and operational rotations. For the field of Pathology Informatics itself, a core curriculum defines to the outside world, including departments, companies, and health systems considering hiring a pathology informatician, the core knowledge set expected of a person trained in the field and, more fundamentally, it helps to define the scope of the field within Pathology and healthcare in general.

[1]  M Peters,et al.  Pathologists and training in information technology. , 1992, Journal of clinical pathology.

[2]  Huimin Lu,et al.  Modeling complex workflow in molecular diagnostics: design specifications of laboratory software for support of personalized medicine. , 2010, The Journal of molecular diagnostics : JMD.

[3]  Leyda Napoles,et al.  Developing a lean culture in the laboratory. , 2006, Clinical leadership & management review : the journal of CLMA.

[4]  D Nevalainen,et al.  Evaluating laboratory performance on quality indicators with the six sigma scale. , 2000, Archives of pathology & laboratory medicine.

[5]  M. Michael Shabot,et al.  AMIA Board White Paper: Program Requirements for Fellowship Education in the Subspecialty of Clinical Informatics , 2009, J. Am. Medical Informatics Assoc..

[6]  Yukako Yagi,et al.  Use of whole slide imaging in surgical pathology quality assurance: design and pilot validation studies. , 2006, Human pathology.

[7]  Ji Yeon Kim,et al.  The Use of Decision Analysis Tools for the Selection of Clinical Laboratory Tests: Developing Diagnostic and Forecasting Models Using Laboratory Evidence , 2011 .

[8]  Anil V Parwani,et al.  Residency training in pathology informatics: a virtual rotation solution. , 2009, American journal of clinical pathology.

[9]  Yukako Yagi,et al.  Primary histologic diagnosis using automated whole slide imaging: a validation study , 2006, BMC clinical pathology.

[10]  Michael Blechner,et al.  Analysis of search in an online clinical laboratory manual. , 2006, American journal of clinical pathology.

[11]  Roy E. Lee,et al.  Different tracks for pathology informatics fellowship training: Experiences of and input from trainees in a large multisite fellowship program , 2012, Journal of pathology informatics.

[12]  M. Hendrickson,et al.  Decision Analysis and Decision Support Systems in Anatomic Pathology , 2011 .

[13]  Walter H Henricks,et al.  Informatics training in pathology residency programs. , 2002, American journal of clinical pathology.

[14]  A M Marchevsky,et al.  Reasoning with uncertainty in pathology: artificial neural networks and logistic regression as tools for prediction of lymph node status in breast cancer patients. , 1999, Modern pathology : an official journal of the United States and Canadian Academy of Pathology, Inc.

[15]  Michael J Becich,et al.  Pathology and patient safety: the critical role of pathology informatics in error reduction and quality initiatives. , 2004, Clinics in laboratory medicine.

[16]  Anand S Dighe,et al.  Physician survey of a laboratory medicine interpretive service and evaluation of the influence of interpretations on laboratory test ordering. , 2004, Archives of pathology & laboratory medicine.

[17]  Walter H Henricks,et al.  Informatics training in pathology residency programs: proposed learning objectives and skill sets for the new millennium. , 2009, Archives of pathology & laboratory medicine.

[18]  Edward H. Shortliffe,et al.  The Computer Meets Medicine and Biology: Emergence of a Discipline , 2001 .

[19]  James H Harrison,et al.  Training in pathology informatics: implementation at the University of Pittsburgh. , 2003, Archives of pathology & laboratory medicine.

[20]  B A Friedman Informatics as a separate section within a department of pathology. , 1990, American journal of clinical pathology.

[21]  G J Buffone,et al.  Informatics. A subspecialty in pathology. , 1993, American journal of clinical pathology.

[22]  J. Marc Overhage,et al.  AMIA Board White Paper: Core Content for the Subspecialty of Clinical Informatics , 2009, J. Am. Medical Informatics Assoc..

[23]  J Myers Computer-retrievable surgical pathology files. A low-cost, shareable system. , 1975, Archives of pathology.

[24]  Becich Mj Information management: moving from test results to clinical information. , 2000 .

[25]  R. Forsman,et al.  Why is the laboratory an afterthought for managed care organizations? , 1996, Clinical chemistry.

[26]  Thomas J Persoon,et al.  Improving preanalytic processes using the principles of lean production (Toyota Production System). , 2006, American journal of clinical pathology.

[27]  Gregory Butler,et al.  The EnzymeTracker: an open-source laboratory information management system for sample tracking , 2011, BMC Bioinformatics.

[28]  Charles D Hawker,et al.  Laboratory automation: total and subtotal. , 2007, Clinics in laboratory medicine.

[29]  L. Leape,et al.  Errors in medicine. , 2009, Clinica chimica acta; international journal of clinical chemistry.

[30]  John R. Gilbertson,et al.  The pathology informatics curriculum wiki: Harnessing the power of user-generated content , 2010, Journal of pathology informatics.

[31]  Anand S Dighe,et al.  Analysis of laboratory critical value reporting at a large academic medical center. , 2006, American journal of clinical pathology.

[32]  Marianne Philippe,et al.  Application of the Six Sigma concept in clinical laboratories: a review , 2007, Clinical chemistry and laboratory medicine.

[33]  J C Healy,et al.  Medical informatics training in pathology residency programs. , 1997, American journal of clinical pathology.

[34]  The Henry Ford Production System: reduction of surgical pathology in-process misidentification defects by bar code-specified work process standardization. , 2009 .

[35]  Min Xu,et al.  Application of the Toyota Production System improves core laboratory operations. , 2010, American journal of clinical pathology.

[36]  Korpman Ra Using the computer to optimize human performance in health care delivery. The pathologist as medical information specialist. , 1987 .

[37]  David S. McClintock,et al.  Clinical fellowship training in pathology informatics: A program description , 2012, Journal of pathology informatics.