| | NOVEMBER 2024 8UTLOOKHealthcare Tech IN MY OPINIONRemote Patient Monitoring ­ Still Not a Household NameBy Gerard Frunzi, Director of Virtual Care - Common Spirit Mountain Region, formerly Centura HealthTelehealth became a household name during the COVID-19 pandemic. Most of the expansion was live video visits with providers. Remote patient monitoring (RPM) and a new offering, remote therapeutic monitoring (RTM), are not commonly known and have not seen national adoption like video visits. This article will review some of the issues and barriers surrounding RPM and what the future might hold. Before 2020, if I had a conversation with a stranger asking what I did for a living, I'd answer I was in business operations at a hospital system. There was just too much effort explaining telehealth to strangers. Now, it's an engaging conversation with strangers. Everyone has experience with telemedicine and has a strong opinion about it. Some truly love it, while others dislike it. RPM involves the use of technology to monitor patient health outside brick-and-mortar healthcare facilities. It allows healthcare providers to track vital signs, symptoms, and other health data remotely, enabling timely interventions and personalized care plans. RTM is an expansion into therapy-based services leveraging similar technologies, gaining acceptance with Medicaid coverage that started in 2022.The uptake of RPM was significant throughout the pandemic, seeing well over 1000 percent increase since 2020. Care by video care had a different trend of acceptance than RPM. Video care skyrocketed in 2020 and then slowed down steadily to the new normal. RPM, on the other hand, did not do the 2020 skyrocket and has instead steadily increased over the years, with the most significant jump this past year. This recent jump can be attributed to better coverage by private insurance and Medicare. State Medicaid has not yet fully embraced RPM nationally. For example, coverage for RPM in some states Medicaid might be limited to home health patients or, in another example, only for a subset of cardiology patients. Organizational adoption of RPM has been an issue. The startup costs are notable for licensing, logistics, and labor to start an RPM program. Creating an RPM service is much more complex than a project adding video for telehealth. Integrating RPM into the electronic medical record can be costly as it's not well standardized for integration or interoperability. There are far too many systems and clinical groups that lack even the option to leverage RPM for patient care. Groups that have gone through the investment to initiate RPM must also address the barriers to expanding the program. Each new offering is built for a clinical use case. This requires time and effort by the telehealth program, IT technical team, and clinician partners. Figuring out which tools to include in the home kit, setting alert barriers, and building customization for services. Beyond state Medicare coverage issues, Federal Medicaid and private insurance reimbursement is limited. It is not going to be a large Gerard Frunzi
< Page 7 | Page 9 >