Winning Administrator Buy-In for Remote Monitoring Programs
OHSU won leadership approval. McLeod Health proved the case with 31% more patients monitored in five months without adding staff.
Learn how to get your own program to yes.
Register to join live or sign up to get the recording.
Why Requests Stall
Remote monitoring requests stall when they don’t answer leadership’s questions about patient safety, staffing, revenue, and IT.
Who You’ll Hear From
Andrea Bottorff, a nurse manager at OHSU, will share the four objections she faced at every executive level and how she answered each one. Christina Ray, AVP of Operations at McLeod Health, will show where her program found unbilled revenue and the four measures she reports to leadership.
What You’ll Take Away
A 30-day plan you can start before your next budget conversation.
Show Leadership the Workflow
Follow One Transmission End to End
Walk leadership through the path a single transmission takes when your team handles it alone. Each step is a handoff, and each handoff is time your device staff spend.
Step 1
Transmission Arrives
A device sends data to its manufacturer’s portal.
Each manufacturer has its own portal
Step 2
Log In and Pull It
Staff sign in to each portal to find and download it.
A separate login for every vendor
Step 3
Review and Triage
A device nurse reads it and decides what is urgent.
Every alert is read by a person
Step 4
Physician Sign-Off
The report waits for a physician to review and sign.
It sits in a queue until signed
Step 5
Chart and Bill
The signed report goes into the EHR and gets billed.
A missed 31- or 91-day window means a missed bill
Time each step as you go. That number becomes the staffing case you take to leadership.
What McLeod Health Reported to Leadership
The largest single gain came from billing the technical component in-house instead of splitting it with a third party.
31%
more patients monitored in the first five months after switching, with the same five device staff
51%
more billable charges, comparing the 12 months before and after switching
What You’ll Learn
Part 1
Getting It Approved
Andrea Bottorff, OHSU
- 1How to follow one transmission end to end and track the time each step takes, before you write a single requirement
- 2Who to bring in on day one: device staff, physicians, nursing, IT, contracting and security
- 3How to run a fair evaluation, from agreeing on must-haves to demos from vendors around your own workflow
- 4The four objections leadership raised and how she answered them: staff time, IT build, comparison to today and success metrics
Part 2
Proving It Worked
Christina Ray, McLeod Health
- 1Where unbilled revenue hides: missed 31- and 91-day monitoring windows
- 2The four measures she reports to leadership: windows captured, patients current, billing by CPT code and staff capacity
- 3Why moving billing in-house was McLeod’s largest single gain
- 4How to build a before-and-after billing comparison leadership will trust, using 12 months of data on each side
Bring your own approval question for the live Q&A.
Your Next 30 Days
- 01
Day 1
Shadow Your Device Team
Follow one transmission end to end and note where the time goes.
- 02
Meet Every Approver
Talk with everyone who signs off before you make the ask.
- 03
Pull 12 Months of Billing
Break it out by CPT code so you know your baseline.
- 04
Day 30
Frame the Ask
Answer what leadership already asks about: patient safety, staffing, revenue and IT burden.
Frequently Asked Questions
How do you get administrator buy-in for a remote monitoring program?
Answer the questions leadership already asks about patient safety, staffing, revenue and IT burden, and define success before the first demo. Andrea Bottorff took OHSU’s request to every executive level and wrote the success metrics into the contract.
How do you build an ROI case before you have vendor data?
Start from your own numbers. Andrea estimated OHSU’s revenue leakage in the current workflow and used it as the financial case. Christina Ray recommends pulling 12 months of billing by CPT code first, so you know your baseline before any vendor conversation.
Who should be involved before choosing a remote monitoring vendor?
Everyone who owns part of the decision: device staff, physicians, nursing, IT, contracting and security. At OHSU, nursing leadership owned staffing and ROI, IT owned the integration scope, physicians owned review standards and contracting owned the terms. It slowed the early meetings and saved months later. If you have no procurement team, bring in whoever signs contracts on day one.
What should you ask IT for?
A named, bounded request. Andrea let OHSU’s IT team run its own discovery, so the integration scope came from the people who would build it.
Where do remote cardiac monitoring programs lose revenue?
Christina found two places at McLeod Health. One was technical components given away under split billing, where a third party keeps the technical fee. The other was 31- and 91-day monitoring windows that go unbilled. McLeod’s billable charges grew 51%, comparing the 12 months before and after switching.
What should you report to leadership after go-live?
Report against what you promised in the ask. Christina tracks four measures: monitoring windows captured, patients current, billing by CPT code and staff capacity.
When is the webinar, and will it be recorded?
This is a free MedAxiom webinar on Tuesday, January 26, 2027, at 1:00 PM ET / 10:00 AM PT. Registrants who can’t attend live can sign up to receive the recording.
