Background: In the ever-evolving landscape of healthcare communication, medical staff—primarily from Generations X and Y—traditionally employ two-way communication. This approach fosters active engagement and shared decision-making in student-centered teaching. However, aligning this well-established method with the preferences of Generation Z remains unexplored. This study delves into these preferences, specifically comparing traditional two-way communication with modern, digital platform-based one-way methods.Methods: Through a cross-sectional study conducted among externs and interns at Surin Hospital, Thailand, we examined communication preferences using a 1-5 rating scale. Descriptive statistics were employed to analyze the data, providing insights into the evolving communication landscape.Results: Among the 67 interns and externs, with an impressive 80.6% response rate, preferences leaned toward hybrid consultation models. While two-way consultations received an average score of 3.2 (SD 0.88)—indicating moderate preference—respondents (63%) highly valued its educational benefits. Interestingly, 50% reported experiencing anxiety and insomnia before consultations, suggesting potential drawbacks. A key finding emerged, with 81.5% favoring a shift toward digital one-way communication for non-urgent cases. Moreover, nearly all participants expressed a preference for a three-level triage system, utilizing both methods: one-way for non-urgent, two-way for urgent, and two-way for emergency cases.Discussion and Conclusion: This study underscores the need for tailored communication approaches in medication consultations for Generation Z medical trainees. Integrating digital platforms and offering a hybrid model can enhance communication effectiveness and adapt to the preferences of this emerging generation.
No takes yet. Share an insight, caveat, or question.
Chalernchai Lertanansit (2024) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: