Author ORCID Identifier
Malgorzata Kolotylo-Kulkarni: https://orcid.org/0000-0002-1445-0403
Haoran Zheng: https://orcid.org/0000-0003-1647-5521
Robert Lucia: https://orcid.org/0000-0001-5121-3223
Rachel Borton: https://orcid.org/0000-0001-8112-255X
Alanah Mitchell: https://orcid.org/0000-0002-6304-4671
Abstract
Remote patient monitoring (RPM) uses information and communication technologies (ICT) to monitor patients’ health asynchronously and remotely. COVID-19 pressures and U.S. reimbursement reforms accelerated RPM adoption, but the high data volume and fragmented workflow introduced challenges. We held an interdisciplinary panel of five experts at MWAIS 2024. The findings from the panel indicate a tension between the potential and actualized value of RPM, which stems particularly from challenges associated with a distributed health data ecosystem and a shift in health delivery practices. We observed that the actualization of RPM value, to a large extent, rests upon the resolution of challenges that fall under three key areas: (1) trust, risk, and responsibility; (2) fragmented and limited infrastructure; and (3) shifts in work dynamics and expertise. Building upon the panel findings and extant literature, we identify opportunities for future research on RPM. Along with distinct research directions, we recommend relevant methodological approaches to support information systems (IS) researchers in the identification and study of RPM phenomena. We also discuss curriculum needs and opportunities for pedagogical research to prepare professionals for digital health roles. Our findings advance IS theory and support healthcare practice.
Recommended Citation
Kolotylo-Kulkarni, M., Zheng, H., Lucia, R., Borton, R., & Mitchell, A. (In press). Remote Patient Monitoring: Implications for Information Systems Researchers. Communications of the Association for Information Systems, 58, pp-pp. Retrieved from https://aisel.aisnet.org/cais/vol58/iss1/86
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.