Learning outcomes: Exploring implications of adopting a different level of detail.

EUROPEAN JOURNAL OF DENTAL EDUCATION(2018)

Cited 4|Views9
No score
Abstract
IntroductionOutcome-based programmes provide a framework to support educators and learners in understanding content and end points within taught courses. Management of these outcomes in the Dental Degree at Newcastle University has been a challenge in relation to quality assurance and enhancement, having over 1500 detailed student-level outcomes (SLO). This research aimed to explore the implications of adopting a more superficial course level of outcome (CLO), when reviewed against a reference set of external LO requirements. Materials and methodsA purposive sample of five courses within the undergraduate dental programme was selected. The mapping of both SLOs and CLOs was reviewed in relation to their total number and the mapping connections to the reference outcomes. ResultsThere was a mean reduction of 79% in outcomes when comparing SLOs to CLOs. The number of mapping connections between CLOs and the reference set reduced in three courses and increased in two, when compared to SLOs. DiscussionFrom a purely numerical perspective, changing the detail of learning outcomes has led to a change in mapping connections. As the delivered curriculum has remained unchanged, this demonstrates a potential impact of differing interpretations of learning outcomes. Further review of learning outcomes in relation to the domains categorised within the reference outcome document suggested more mapping links were obtained in clinically focused courses than academic or theoretical courses. ConclusionA demonstrable impact in mapping connections was observed when the detail within the learning outcomes was changed. This has implications for programme leaders in structuring LOs for a curriculum.
More
Translated text
Key words
programme development,learning outcomes
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined