Choose RPM software by testing how it handles a patient’s monitoring workflow, from enrollment and the first reading to follow-up and billing review. Ask vendors to demonstrate the routine work, the exceptions and the records your team will need, then confirm which responsibilities belong to your practice.
A dashboard can look convincing while leaving important questions unanswered. Who notices a missing reading? Where does an alert go when the assigned coordinator is absent? Can your billing staff trace a summary back to the work recorded?
Use these 12 questions to turn a sales demonstration into a practical evaluation.
1. Can you demonstrate one patient’s complete workflow?
Ask the vendor to follow one demonstration patient from enrollment through monitoring, follow-up and billing review. You should see how information moves between screens, who acts at each stage and what remains in the record. A sequence of disconnected feature demonstrations will not show those handoffs.
Start with a new patient. Record the enrollment information, connect a device and receive a reading. Then introduce a missing reading and an alert that needs review.
Ask the presenter to use the same patient throughout. Note every point where someone must copy information, leave the platform or remember an action without a visible task.
2. How does the software support enrollment and consent documentation?
Ask where staff record enrollment, patient consent and device education, and how those records are retrieved later. Your coordinator should be able to distinguish a patient who is ready to begin from someone still waiting for setup. Test corrections and incomplete records as well as successful enrollment.
CMS’s 2026 remote monitoring guidance requires patient consent when RPM services are provided. CMS also describes education and device setup as a component of remote monitoring. Ask your billing and clinical leads how the proposed workflow meets the requirements applicable to your program.
A useful demonstration includes a patient who has consented but has not transmitted a first reading. Ask how your team finds that patient the following morning.
3. Which devices work, and how do readings reach the dashboard?
Request the supported device list, connection method and patient requirements in writing. Then watch a reading travel from the device to the patient record. Ask how the system distinguishes a delayed transmission, a failed connection and a patient who has not taken a reading.
CMS’s 2026 guidance describes electronic collection and automatic upload of physiologic data. A vendor should explain its data path clearly enough for your team to assess it against applicable requirements.
For Bluetooth devices, test pairing and reconnection. For cellular devices, ask about coverage and transmission failures. Use the Bluetooth and cellular comparison to prepare patient suitability questions.
4. What happens when readings are missing?
Ask the vendor to show how missing readings become visible, how follow-up is assigned and how staff record the outcome. You need to distinguish a reminder sent from a problem resolved. The demonstration should show what happens when the first attempt receives no response.
Consider a coordinator opening the worklist on Monday. Several patients have missing readings, but the reasons differ: one device disconnected, one patient is away and another needs help using the app.
Can staff record those differences and identify the next action? Ask how unresolved work carries into the next shift without depending on a private spreadsheet.
5. How are alerts configured, assigned and closed?
Ask who can set alert thresholds, who receives notifications and how an alert moves from new to reviewed. Your clinical team should define the response process. The software evaluation should establish whether that process is visible, usable and documented, including when the usual reviewer is unavailable.
Have the vendor demonstrate a threshold change, an alert reassignment and a completed review. Look for the original reading, the action taken and the responsible person.
Ask what happens outside your practice’s monitoring hours. Agree the patient-facing explanation and staff coverage process before launch rather than leaving them implicit.
6. What do automated calls do, and what reaches the care record?
Ask vendors to demonstrate the purpose of each automated call, the information collected and the summary staff receive. Your team should be able to tell whether a reminder was delivered, whether the patient responded and whether further review is needed. Ask how inaccurate or incomplete summaries are handled.
Keep automated follow-up separate from staff conversations in your evaluation. Do not treat an automated call as satisfying a billing requirement for interactive communication.
Review the interactive communication guide with your billing lead before accepting a vendor’s interpretation. Ask for the supporting source whenever a demonstration includes a reimbursement claim.
See how PCL Health brings enrollment, readings, alerts and care plans together in the clinician platform.
7. Can billing staff trace summaries back to recorded activity?
Ask for a demonstration billing record and trace each entry to its underlying activity. Your billing staff need to understand who recorded the work, what happened and which period the summary covers. A total without supporting detail is difficult to review when an entry is questioned.
Test a corrected time entry and an incomplete note. Ask whether changes retain a history and whether overlapping activities can be identified.
Request separate demonstrations of time tracking, documentation summaries and any code mapping. Confirm their scope in writing. Software documentation supports billing review; it does not establish patient eligibility or guarantee reimbursement.
8. How do permissions match the people using the system?
Ask the vendor to demonstrate access for a coordinator, clinician and administrator rather than describing permissions in general terms. Check what each role can view and change, how access is removed and what happens when someone moves between facilities. Include any patient or caregiver access in the review.
HHS’s Security Rule summary describes access management and audit controls among the safeguards for electronic protected health information. Your security lead should assess how the vendor’s controls fit your organization’s obligations.
Try removing a demonstration user’s access. Ask where the change is recorded and how active sessions are handled.
9. What security responsibilities belong to each party?
Request the proposed business associate agreement, hosting information and a written division of security responsibilities. Your review should cover access, incident reporting, backups and recovery. Ask who is responsible for each control instead of relying on a security badge or a broad compliance statement.
HHS explains that using a cloud provider to maintain or process electronic protected health information can create a business associate relationship. HHS also makes clear that a BAA does not replace the customer’s other HIPAA responsibilities, including risk analysis.
Have your privacy or security lead review the documents before introducing real patient information.
10. What support will patients and staff receive during launch?
Ask who handles device pairing, account access and failed transmissions, and how your staff reach that support. Confirm support hours, escalation routes and training materials in writing. A launch plan should name the people responsible for resolving problems rather than simply promise that onboarding is included.
Use a fictional scenario: a patient takes a reading, but nothing appears in the dashboard. Ask the vendor to walk through the investigation.
Who contacts the patient? Who checks the device connection? Where is the resolution recorded? Those answers help you estimate the work your practice must retain.
11. What will the service cost, and what can change?
Request an itemized commercial proposal that identifies software, devices, implementation, training and any usage-based charges. Ask which costs continue when a patient pauses monitoring and which charges change as the program grows. Compare written scope across vendors before comparing headline prices.
Use a common worksheet:
| Area | Evidence to request |
|---|---|
| Implementation | Included tasks and your team’s responsibilities |
| Devices | Supply, replacement and return arrangements |
| Software | Charging basis and included modules |
| Support | Hours, channels and escalation scope |
| Renewal | Notice periods and change provisions |
| Exit | Export scope, timing and charges |
Keep projected reimbursement separate from the vendor’s charges.
12. What happens if you change platforms?
Ask how patient records, readings, notes and activity histories can be returned when the agreement ends. Request a sample export and have the people who will use it inspect the format. Confirm the process, timing and contractual terms before you depend on the platform.
HHS’s cloud guidance identifies data return after termination, availability and recovery as matters that may be addressed in service agreements.
For buyers considering licensing or acquisition, use the main guide to building, licensing or buying an RPM platform to frame the wider commercial decision.
How should you make the final decision?
Score vendors against your written workflow and the evidence they provide. Involve a coordinator, clinical lead, billing reviewer and security reviewer. Resolve material gaps before signing, and use a limited launch with agreed acceptance criteria to test the workflow under your practice’s operating conditions.
Choose criteria you can observe: a first reading received, a missing reading assigned, an alert reviewed and a billing record retrieved. Record whether each demonstration passed and what remains unresolved.
Frequently asked questions
Should a small practice choose software or a managed service?
Start by deciding which work your practice will perform and which work a service provider would perform. Compare the staffing responsibilities, documentation access and contract scope of each option.
Does RPM software guarantee reimbursement?
No. Your billing staff must review the service delivered against current payer requirements; a software summary alone does not establish eligibility or payment.
How should buyers evaluate AI features?
Test a defined task, such as a missed-reading reminder, and inspect the resulting record. Ask how staff review exceptions and correct errors.
Can buyers evaluate PCL Health using these questions?
Yes. Ask PCL Health to demonstrate the relevant workflow and confirm the product and contract scope for your organization.
Book a demo: Choose a time to see the platform.
This article is general information, not billing or legal advice. Confirm current payer requirements before submitting claims.
Sources
- CMS — Telehealth & Remote Monitoring, 2026: Consent and electronic data collection requirements.
- CMS — Remote Patient Monitoring: Education, device setup and monitoring components.
- HHS — Summary of the HIPAA Security Rule: Access management and audit controls.
- HHS — Guidance on HIPAA & Cloud Computing: Business associate relationships, risk analysis and service agreement considerations.