A denied claim arrives after the expensive part: your team has already reviewed the chart, enrolled the patient, and delivered care. Then someone has to investigate and rework the claim. FairPath brings documented-condition eligibility, payer payment history, and live insurance verification into the workflow so practices and pharmacy-led teams can fix avoidable problems earlier.
Our breakdown of the real cost of RPM, APCM, and CCM counts unpaid clinical time and denial rework as separate drains on a program. This companion focuses on the second: payment problems you can catch before you build a month of work around them.
Short answer
Before enrollment, check program fit, the payer's payment history, and current insurance information. Each answers a different question. Turn the issues they uncover into specific work items before starting the program.
Key takeaways
- Read payment history for the verified payer, not just the payer on file.
- RPM, APCM, and CCM have different requirements. Qualify the patient for the program you intend to deliver.
- Investigate payment-history shortfalls before adding more patients to the same workflow.
- Record what was checked, who owns the next action, and what remains unresolved.
- FairPath surfaces the three checks so your team can act before enrollment and billing.
1. Match the patient to the right program
A diagnosis list is a starting point. The useful question is: What care does this patient need, and what supports this program choice?
- RPM: For a patient with hypertension, the clinician identifies a need for blood-pressure readings between visits. CMS describes RPM as connected-device data used to treat or manage an acute or chronic condition. The workflow has three parts: patient education and device setup, device supply and data transmission, and treatment management, not just sending a cuff.
- CCM: CMS's chronic care management guidance requires two or more chronic conditions expected to last at least 12 months or until death that place the patient at significant risk of death, acute exacerbation or decompensation, or functional decline. The chart and care plan should explain that clinical picture.
- APCM: Start with the practitioner responsible for the patient's primary care and the appropriate service level. CMS sets requirements by APCM level: G0557 requires two or more qualifying chronic conditions; G0558 adds Qualified Medicare Beneficiary status. The two-condition requirement does not apply to every APCM level.
Our CCM compliance analytics guide traces the evidence chain: qualifying conditions → care plan → monthly work → billing review. A note records the work; it doesn't, by itself, establish why the patient qualified.
Leave this check with: the proposed program, supporting documentation, and any clinical question to resolve before outreach.
2. Review how this payer has actually paid
Clinical fit and payment history are different questions. Look at your organization's collections for the payer and service you're planning to bill. Compare actual payments with what you expected, then investigate a recurring gap.
Give the billing team a short work list:
- Pull recent remittances for that payer and service.
- Compare denial and adjustment reasons.
- Check whether the gap clusters by plan, location, or documentation step.
- Assign the correction: documentation, billing process, or coverage review.
Leave this check with: the issue, its owner, and the action needed before repeating the same workflow with more patients.
3. Verify the insurance record you will use today
The card in the chart shows what was recorded. Live verification shows what the insurer reports now.
Confirm payer and member information, save the response, and resolve mismatches. If the response leaves a service-specific coverage question open, give that question an owner rather than passing it downstream unanswered.
Our plain-English insurance article covers why plan changes and unclear coverage land on staff. The next person should see what was checked, when, and what remains open, without restarting the investigation.
Leave this check with: current insurance information, the dated response, and any remaining coverage question.
What this looks like for one patient
Here's a fictional RPM example: monitoring fits, but the chart still holds an old plan.
How FairPath turns the checks into usable work
Your practice or pharmacy provides the clinical workforce and owns care, enrollment decisions, and billing. FairPath supplies the information behind those decisions:
| Function | What your team owns | What FairPath records or surfaces |
|---|---|---|
| Program fit | Decide clinical suitability and resolve documentation gaps | Documented-condition eligibility and supporting information |
| Payer review | Investigate payment concerns and assign the correction | Actual-versus-expected payment patterns by payer and service |
| Insurance verification | Confirm patient information and resolve coverage questions | Current insurer verification results saved with the patient record |
FairPath keeps those findings connected to consent, care planning, documentation, and billing review. An issue found at enrollment shouldn't become a surprise for the person submitting the claim.
The cost article also links to guides on work that falls short of a traditional billing block and time spent deciding which patient needs attention next. These checks address rework instead, the kind that starts with an unresolved enrollment question. Find it early, assign it, and carry the answer forward.
See how FairPath connects remote care operations in one platform.
Sources
Related FairPath Guides
- The Real Cost of RPM, APCM, and CCM
- CCM Compliance Is Becoming an Analytics Problem
- The Plain-English Insurance Era Is Dawning
- The Hidden Pressure No One Talks About in RPM: What Happens at 18 Minutes
- Prioritizing Patients for Clinical Monitoring Through Exploration