CME Webcast Discusses Remote Patient Monitoring. In 2020, telehealth saw a major uptick and broad adoption with the spread of COVID-19 pandemic and global lockdown. Now, the COVID-19 national emergency is ending but telehealth has remained and continued to expand. With that is an expansion of Remote Patient Monitoring or Remote Physiologic Monitoring (RPM) Modern technology is seeing newer, better sensors that are cheaper to manufacture making remote monitoring of patients using medical devices more accessible. But how can we leverage this technology to best care for our patients?
To answer that question, We’ve invited two of Ohio State University’s Primary Care Innovation experts. We’re pleased to introduce Associate Professor of Internal Medicine Dr Jodi Grandominico. Jodi serves as the Associate Director of Clinical Operations in the Division of General Internal Medicine and leads many clinical innovation programs for the division. I also have the pleasure of welcoming Associate Professor and Doctor of Pharmacy Kelli Barnes. Kelli is the lead pharmacist for General Internal Medicine and created & leads the Remote Monitoring program along with many other pharmacy programs in primary care.
What you’ll learn in this webcast
As a result of this educational activity, webcast participants will be able to:
- Understand clinical, financial, and patient satisfaction considerations for an RPM implementation strategy in your clinical practice
- Review the current literature depicting the benefits of remote physiologic monitoring and potential use cases in healthcare
- Describe important considerations for remote physiologic monitoring implementation in diverse healthcare settings.
You’ll also learn about the following:
- Types of Conditions
- Healthcare Team Integration
You can find this and many other MedNet21 programs on the OSU – CCME website.
Call our MedNet21 Program Manager at 614.293.3473 for more details about subscribing to MedNet21 as a hospital or as an individual. You can also e-mail him at firstname.lastname@example.org.