Abstract

BackgroundManaging change has not only been recognized as an important topic in medical informatics, but it has become increasingly important in translational informatics. The move to share data, together with the increasing complexity and volume of the data, has precipitated a transition from locally stored worksheet and flat files to relational data bases with object oriented interfaces for data storage and retrieval. While the transition from simple to complex data structures, mirroring the transition from simple to complex experimental technologies, seems natural, the human factor often fails to be adequately addressed leading to failures in managing change.MethodsWe describe here a case study in change management applied to an application in translational informatics that touches upon changes in hardware, software, data models, procedures, and terminology standards. We use the classic paper by Riley and Lorenzi to dissect the problems that arose, the solutions that were implemented, and the lessons learned.ResultsThe entire project from requirements gathering through completion of migration of the system took three years. Double data entry into the old and new systems persisted for six months. Contributing factors hindering progress and solutions to facilitate managing the change were identified in seven of the areas identified by Riley and Lorenzi: communications, cultural changes in work practice, scope creep, leadership and organizational issues, and training.ConclusionsDetailed documentation of the agreed upon requirements for the new system along with ongoing review of the sources of resistance to change as defined by Riley and Lorenzi were the most important steps taken that contributed to the success of the project. Cultural changes in tissue collection mandated by standards requirements introduced by the Cancer Bioinformatics Grid (CaBIG®) and excessive reliance on the outgoing system during a lengthy period of dual data entry were the primary sources of resistance to change.

Highlights

  • In 2006, the Cooperative Human Tissue Network (CHTN) migrated from a distributed model of six standalone FoxPro databases to house their tissue requests, in use for almost 20 years, to a centralized web-based system with an Oracle backend relational database

  • * Correspondence: medgerton@mdanderson.org 1 Section of Pathology Informatics, Department of Pathology, MD Anderson Cancer Center, Houston, TX, USA Full list of author information is available at the end of the article sions, but they were made compliant with ongoing standards initiative within the National Cancer Institute (NCI). Migration to this new system had a major impact on their data management and workflow

  • A significant source of change was the new ontology and terminology for the disease and histopathological qualities of the tissues being requested that was introduced in order to achieve compliance with the NCI standards initiatives

Read more

Summary

Methods

We describe here a case study in change management applied to an application in translational informatics that touches upon changes in hardware, software, data models, procedures, and terminology standards. We use the classic paper by Riley and Lorenzi to dissect the problems that arose, the solutions that were implemented, and the lessons learned

Results
Conclusions
Introduction
Background
Design and Development Process
Conclusion
Ozbolt J
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call