We have developed a series of Electronic Student Encounter Log (ESEL) programs intended to introduce medical students to promising medical informatics concepts. We attempted to expand ESEL’s scope from ambulatory settings to all hospital venues and to track progress toward educational goals. Students were confused and frustrated by a previously fast interface and delayed feedback. Numerous scaling problems emerged. Our attempt to address these problems in an extensive revision, developed for the latest affordable hardware and operating system, failed due to new data-corrupting crashes. Risks of scaling up and other familiar software development lessons are reinforced
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.