Journal of Participatory Medicine · Published 2025-08-03 · DOI 10.2196/72552
Abstract BackgroundLaunched in January 2022, the SingHealth Patient Advocacy Network at the Department of Emergency Medicine (SPAN@DEM) represents the first emergency department-specific advocacy group in Singapore. This initiative marks a significant advancement in local patient advocacy efforts because it employs a shared collaborative model to address the needs and concerns of patients within the unique context of the emergency department environment. SPAN@DEM emerged in recognition of the limitations of existing cluster-level advocacy groups, which are inadequate to address specific challenges inherent to the fast-paced, high-pressure nature of the emergency department. ObjectiveIn this article, we describe the establishment of SPAN@DEM, discuss the challenges and considerations encountered, and reflect on lessons gleaned through this journey. MethodsA start-up committee, comprising two emergency physicians and four patient advocates, was convened to delineate the processes required to form a new patient advocacy group. Key features of SPAN@DEM include co-leadership by an emergency physician and a patient advocate, and diverse membership composition with equal representation from health care professionals and patient advocates. SPAN@DEM convenes quarterly with informal luncheons during meetings to foster open communication between advocates and health care staff. Membership is voluntary and motivated solely by altruism, and all members are required to participate in mandatory advocacy training to empower them to provide more actionable insights. ResultsSince its inception, SPAN@DEM has implemented several initiatives such as PIKACHU ConclusionsSPAN@DEM exemplifies the value of specialized emergency department-specific advocacy groups in advancing patient-centered emergency care. This model may serve as an exemplar for other health care institutions seeking to enhance patient advocacy efforts.
Abstract from DOAJ. Public domain (CC0 1.0).
Read the article at the publisher →