RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →Building an Audit-Proof Care Plan in 90 Seconds
The Bottom Line
- The Problem: Most audits fail because the "Care Plan" is just a generic PDF attached to the chart, not a living document.
- The FairPath Fix: We dynamically combine multiple conditions (e.g., Hypertension + Diabetes) into a single, unified care plan.
- Medical Necessity: The system automatically suggests clinical goals (e.g., "Maintain BP < 130/80") that justify the need for remote monitoring.
- Speed: You can generate, customize, and sign a compliant plan for a complex patient in under two minutes.
Why "Generic" Care Plans Fail Audits
A "Care Plan" in the eyes of CMS is not just a list of diagnoses. It must be a structured document that defines goals, interventions, and measurement criteria. If you are billing RPM (99457) or CCM (99490), this document is your "invoice" justification.
Many practices use static templates that say "Monitor Blood Pressure." This is insufficient. An audit-proof plan must be specific to the patient's comorbidities.
| Standard EHR Template (Risk) | FairPath Dynamic Plan (Safe) |
|---|---|
| Single generic PDF ("Hypertension Plan"). | Combined data model ("HTN + T2 Diabetes Plan"). |
| Static text: "Patient should monitor BP." | Specific goal: "Maintain systolic < 130 over 30 days." |
| Disconnected from device alerts. | Alert thresholds are hard-coded into the plan. |
The "Multi-Condition" Logic
As shown in the video, FairPath doesn't force you to create two separate plans for a patient with two conditions. The system recognizes the ICD-10 codes (e.g., I10 for Hypertension, E11.9 for Diabetes) and merges the relevant protocols into one workflow. This ensures your staff isn't toggling between screens to manage one patient.
Video Transcript
0:00 Hi, I'm Justin Brochetti from FairPath. Before we can start monitoring a patient or letting Amy triage their alerts, we have to establish the rules of engagement. In CMS terms, this is the "Care Plan."
0:12 I am on the patient onboarding screen. You can see we have already pulled in the patient's demographics and insurance from the EHR. Now, look at the "Conditions" block. This patient has both Hypertension and Type 2 Diabetes.
0:25 In most systems, you would have to build a plan for BP, and then a separate plan for Glucose. Watch this. I simply select both conditions. FairPath automatically recognizes the comorbidity overlap.
0:38 I click "Generate Plan." The system instantly builds a unified care protocol. It sets the Blood Pressure threshold to 140/90 because that is standard for HTN, but it also pulls in the Glucose fasting goals.
0:50 Now, I can customize it. Let's say this patient is high-risk. I want to tighten that BP goal to 130/80. I just drag the slider. The system updates the alert logic immediately.
1:05 Finally, I review the "Interventions" section. These are the specific actions we will take if they go out of range. I click "Sign & Activate."
1:15 That's it. We have created a compliant, multi-condition care plan in under 90 seconds. This document is now the "source of truth" that justifies every minute of monitoring we bill later. In the next video, I'll show you how Amy uses this exact plan to triage alerts automatically.
Ready to see this plan in action?
Now that the care plan is built, watch how our AI agent "Amy" uses it to filter patient noise.
