Issues and challenges in the design of curriculum information systems

Abstract

Medical schools are increasingly using curriculum information systems to better manage their curricula, to incorporate alternative learning environments, to expand subject-specific instruction, or to adapt the curricula to the changing health care environment. A curriculum information system contains key features, selected by the system's designers, that describe the objectives, the specific content, and/or the educational activities that compose the curriculum. The underlying purpose of such a system is to document and describe the knowledge, behaviors, skills, attitudes, or activities students will be expected to develop or learn. While it might be ideal to have one system that would meet the needs of all possible users, the programming and maintenance requirements of such a single system would exceed most medical schools' resources. Thus, designers of curriculum information systems must first identify the primary intended-user group: students, faculty, or administrators. The system designed for one group will typically differ from the systems for other groups in the emphasis on and level of content detail and curriculum structure information. The general structure and purposes of curriculum information systems are expressed in three distinct system designs: a curriculum database (most helpful for administrators), a curriculum textbase (for faculty), and an electronic syllabus (for students). The authors describe these different designs, and they discuss challenges faced by system designers.