Remote patient monitoring support
Connect Monitoring Data With a Repeatable Practice Workflow
Kitronixe helps practices organize operational and billing workflows around eligible remote patient monitoring programs, including patient review, enrollment, device workflow, monitoring activity, documentation, follow-up and billing readiness within the agreed scope.
- 01
41
Patients for Review
- 02
12
Enrollment Pending
- 03
8
Device Setup
- 04
186
Data Available
- 05
27
Review Needed
- 06
14
Interaction / Follow-Up
- 07
19
Documentation Pending
- 08
73
Billing Review
Illustrative data for a fictional practice’s program. Counts of work items only - no patient data, readings or alerts - and not a Kitronixe result.
Clinical responsibility: Clinical interpretation and medical decision-making remain the responsibility of appropriately qualified healthcare professionals.
More than a device
A monitoring program only works if the workflow around it does
A remote patient monitoring program depends on more than a device. Patients are reviewed and enrolled, eligible devices are set up, data has to keep arriving, the clinical team reviews it, interactions are documented, and each period is reviewed before billing - and every one of those steps can stall.
Kitronixe supports the operational side of that workflow: tracking enrollment and device setup, following up when data is missing, keeping documentation workflow visible and reviewing billing readiness against current program and payer requirements. Clinical review, interpretation and medical decisions stay with the practice’s qualified clinical team.
The RPM workflow
From the patient’s device to billing review, in ten stages
Patient / device
Patient Review
Patients the practice may consider for the program are organized for clinical review.
Patient / device
- 01
Patient Review
Patients the practice may consider for the program are organized for clinical review.
- 02
Program Eligibility Review
Program and payer requirements checked for each patient, where applicable.
- 03
Consent / Enrollment
Consent and enrollment tracked to completion and recorded.
- 04
Eligible Device Setup
An eligible device is set up and assigned - device eligibility depends on program requirements.
- 05
Data Collection
Patient-generated data arrives from the device; missing data is followed up.
Secure workflow
- 06
Monitoring Workflow
Data availability and review timing tracked for the clinical team.
Practice team
- 07
Provider / Clinical-Team Review
The practice’s clinical team reviews the data and makes any clinical decision.
Documentation
- 08
Documented Interaction
Interactions with the patient documented by the clinical team, as the program requires.
Billing / review
- 09
Billing Readiness
A workflow readiness review before billing - not a guarantee of payment.
- 10
Program Reporting
Enrollment, data, review and documentation status reported to the practice.
Device to practice
Where the data goes, and who acts on it
Eligible connected device
A device that meets the applicable program’s requirements.
Patient-generated data
Physiologic data transmitted from the device.
Monitoring workflow
Whether data is arriving and review is due, tracked operationally.
Practice / clinical review
The clinical team reviews the data and decides what, if anything, to do.
Practice / clinical team
Documented interaction
The clinical team documents interactions as the program requires.
Practice / clinical team
Program / billing workflow
The period is reviewed for billing readiness against current requirements.
- Device eligibility depends on applicable program requirements.
- Clinical interpretation remains with the practice / qualified clinical team.
Eligible devices
Connected does not mean eligible
01
Connected health device
Many devices can send data. That alone says nothing about program eligibility.
- Blood pressure device
- Weight scale
- Other physiologic monitoring devices
02
Program requirements
Whether a device and patient fit a program depends on the applicable program and payer requirements.
- Device requirements
- Patient eligibility
- Documentation
- Coverage
03
RPM workflow
Only once the requirements are met does the monitoring workflow - and billing review - apply.
- Enrollment
- Monitoring workflow
- Clinical review
- Billing readiness
Not in the RPM workflow - connected alone is not enough
A note on CGM. Continuous glucose monitoring (CGM) has its own coding and coverage considerations and should not automatically be treated as RPM. Examples here are conceptual; no device or patient is eligible by default.
Remote Patient Monitoring
RPM Revenue Opportunity Calculator
Estimate potential gross reimbursement opportunity for an eligible Remote Patient Monitoring program using your Medicare population, enrollment assumptions, monthly participation and reimbursement assumptions.
- Patient population
- Participation
- Program assumptions
- Revenue opportunity
Patient population
Aggregate counts only - never a name, an ID or a diagnosis.
Total Medicare / Medicare Advantage population0
Participation
How many of the review population enroll, and how many take part in a given month.
ScenarioPlanning assumption
Sets the three participation assumptions. Every value stays editable, and no scenario changes an allowed amount.
- Potential review population
- 0
- Estimated enrolled participants
- 0
- Estimated monthly participating
- 0
Program and reimbursement assumptions
Recurring amounts apply each month to participating patients. Initial / setup amounts apply once per new enrollment and are never multiplied across the year.
Your estimated opportunity
Gross reimbursement opportunity - before any cost, never a guarantee.
Monthly recurring opportunity
$0
Annual recurring opportunity
$0
Initial / setup opportunity
$0
Once per new enrollment
Estimated first-year gross opportunity
$0
Annual recurring + initial / setup
Monthly participating patients
0
Avg. monthly amount per participant
$0
- Potential review population0
- Estimated enrolled patients0
- Original Medicare - recurring (monthly)$0
- Medicare Advantage - recurring (monthly)$0
- Original Medicare - initial / setup (year)$0
- Medicare Advantage - initial / setup (year)$0
- How the first year is built
- Monthly recurring = monthly participating patients × recurring allowed amount
- Annual recurring = monthly recurring × 12
- Initial / setup = expected new enrollments in the year × initial / setup allowed amount
- First year = annual recurring + initial / setup
Estimated monthly recurring gross opportunity $0, first-year gross $0, for 0 monthly participating patients.
- Active Medicare / MA population0
- Potential RPM review population0
- Estimated enrolled patients0
- Estimated monthly participating0
- Annual recurring$0
- Initial / setup$0
- Original Medicare$0
- Medicare Advantage$0
Reimbursement assumptionsCMS-derived
- Medicare rate basis
- Not configured - the estimate uses the allowed amounts you enter
- Locality
- Default planning amount where configured, otherwise visitor-entered
- Effective year
- 2026
- Last reviewed
- 2026-09-26
Original Medicare amounts vary by year, locality, service and setting. Medicare Advantage payment and coverage vary by plan, contract and program rules, and are never assumed equal to Original Medicare.
Who does what
Three roles, and only one of them is clinical
Patient
- Use the device
- Participate in the program
- Respond to outreach where applicable
Practice / clinical team
- Clinical oversight
- Clinical review
- Medical decisions
- Clinical interactions
Kitronixe operational support
- Workflow tracking
- Enrollment administration where scoped
- Operational follow-up
- Documentation workflow support
- Billing readiness
- Reporting
Clinical responsibility: Clinical interpretation and medical decision-making remain the responsibility of appropriately qualified healthcare professionals.
Program operations
Every enrollee, with the next operational step
RPM operations work queue
Filter by provider, location, program status or month
| Enrollee | Program status | Provider | Location | Month | Next action |
|---|---|---|---|---|---|
| Enrollee 01 | Patient Review | Provider A | Location 1 | Month 2 | Provider review |
| Enrollee 02 | Enrollment Pending | Provider B | Location 1 | Month 2 | Record consent |
| Enrollee 03 | Device Setup Pending | Provider A | Location 2 | Month 2 | Confirm device setup |
| Enrollee 04 | No / Limited Data | Provider C | Location 1 | Month 2 | Operational outreach |
| Enrollee 05 | Review Needed | Provider B | Location 2 | Month 2 | Flag to clinical team |
| Enrollee 06 | Interaction Needed | Provider A | Location 1 | Month 2 | Clinical team to contact |
| Enrollee 07 | Documentation Pending | Provider C | Location 2 | Month 1 | Confirm documentation |
| Enrollee 08 | Billing Review | Provider B | Location 1 | Month 1 | Readiness review |
| Enrollee 09 | Follow-Up | Provider A | Location 2 | Month 1 | Resolve open item |
| Enrollee 10 | No / Limited Data | Provider B | Location 2 | Month 1 | Device help call |
Enrollee 01Month 2
Patient Review
Provider A · Location 1
Provider review
Enrollee 02Month 2
Enrollment Pending
Provider B · Location 1
Record consent
Enrollee 03Month 2
Device Setup Pending
Provider A · Location 2
Confirm device setup
Enrollee 04Month 2
No / Limited Data
Provider C · Location 1
Operational outreach
Enrollee 05Month 2
Review Needed
Provider B · Location 2
Flag to clinical team
Enrollee 06Month 2
Interaction Needed
Provider A · Location 1
Clinical team to contact
Enrollee 07Month 1
Documentation Pending
Provider C · Location 2
Confirm documentation
Enrollee 08Month 1
Billing Review
Provider B · Location 1
Readiness review
Enrollee 09Month 1
Follow-Up
Provider A · Location 2
Resolve open item
Enrollee 10Month 1
No / Limited Data
Provider B · Location 2
Device help call
10 enrollees shown
Illustrative queue: invented program enrollees, identified by number, with providers as letters. No patient, device or clinical data; not a Kitronixe result.
Reported regularly
- Enrollment Status
- Device Setup Status
- Data Availability
- Review Outstanding
- Follow-Up Required
- Documentation Outstanding
- Billing Readiness
- Provider / Location View
What is supported
RPM workflow support, within the agreed scope
Review, enrollment & devices
Patient review workflow
Patients the practice may consider for the program organized for clinical review - the practice decides.
Program eligibility workflow
Program and payer requirements tracked for each patient under review, where applicable.
Enrollment
Consent and enrollment tracked to completion and recorded.
Device workflow
Eligible device setup, assignment and readiness tracked for each enrolled patient.
Monitoring operations
Monitoring operations
Whether data is arriving, and whether review is due, tracked for the clinical team.
Missing-data / exception follow-up
Patients with no or limited data followed up operationally, and flagged to the practice.
Patient engagement workflow
Administrative outreach - device help, reminders - where it is part of the scope.
Escalation workflow
Anything clinical routed straight to the practice’s clinical team, as agreed.
Documentation
Documentation workflow tracked so required interactions and time are recorded by the clinical team.
Billing
Billing readiness
A workflow readiness review before billing - subject to program, documentation and coverage requirements.
Claim workflow support
RPM claims worked through submission and follow-up, where it is part of the scope.
Reporting & visibility
Reporting
Enrollment, device setup, data availability, review and documentation status, reported regularly.
Program visibility
Program status by provider and location, so outstanding work is visible to the right people.
Where this sits
RPM support, CCM support and Practice Analytics
Remote Patient Monitoring SupportThis page
The operational and billing workflow around an eligible RPM program.
Chronic Care Management Support
The monthly workflow around a CCM program - often run alongside RPM.
Practice Analytics
Reporting across the whole practice, beyond one program.
Why Kitronixe
How Kitronixe supports an RPM program
Operational support, clinical boundaries
Kitronixe tracks the workflow; clinical review and decisions stay with the practice.
Careful about eligibility
Device and patient eligibility are reviewed against current requirements, never assumed.
Missing data followed up
Patients with no or limited data are found and followed up rather than discovered at month end.
Documentation workflow visible
What still needs documenting is visible before billing review.
Provider and location view
Program status is reported by provider and location.
Fits with CCM and RCM
RPM support can sit alongside chronic care management support or full RCM.
What is Remote Patient Monitoring?
Remote patient monitoring programs use eligible connected devices to collect patient-generated physiologic data between visits, which the practice’s clinical team reviews. Program, device and coverage requirements vary by payer and change over time.
Does every connected device qualify for RPM?
No. Being connected does not make a device eligible for an RPM program. Device eligibility depends on the applicable program and payer requirements. Continuous glucose monitoring, for example, has its own coding and coverage considerations and should not automatically be treated as RPM.
Does Kitronixe provide clinical monitoring?
No. Clinical interpretation and medical decision-making remain the responsibility of appropriately qualified healthcare professionals. Kitronixe supports the operational and billing workflow around the program.
Can you help with patient enrollment?
Yes. Consent and enrollment are tracked to completion. Which patients are appropriate for the program is a clinical decision made by the practice.
Can you support device workflow?
Yes - tracking eligible device setup, assignment and readiness for each enrolled patient. Kitronixe does not manufacture or supply devices.
Can you track missing data or follow-up?
Yes. Patients with no or limited data are identified and followed up operationally, and the practice is told. Anything clinical is escalated to the practice’s clinical team.
Can you help with RPM billing workflow?
Yes, where billing is in scope: a workflow readiness review, claim submission and follow-up. Whether a period is billable depends on program, documentation and coverage requirements; readiness review does not guarantee payment.
Can you provide RPM reporting?
Yes: enrollment status, device setup status, data availability, review outstanding, follow-up required, documentation outstanding and billing readiness, by provider and location. No clinical outcome reporting is implied.
Can RPM be combined with CCM?
The workflows can be supported together. Whether both programs apply to the same patient in the same period depends on current program, payer and documentation requirements.
Can RPM support work across multiple providers or locations?
Yes. The program can be tracked and reported by provider and location.
Talk through your RPM workflow
Tell us how the program runs today - enrollment, devices, data and review. We will say plainly where operational support would help.