A pulse-oximeter reading is useful when it helps a care team decide what to do next. For a patient with chronic obstructive pulmonary disease (COPD), remote patient monitoring (RPM) brings oxygen-saturation trends into the same review as symptoms and the prescribed treatment plan. FairPath helps practices organize enrollment, device context, clinical review queues, and time and communication records around that work.
Short answer: COPD RPM uses physiologic data from a qualifying connected medical device to support care between visits. Pulse oximetry estimates peripheral oxygen saturation (SpO2) and pulse; it does not diagnose an exacerbation or determine an oxygen dose. The practice combines reliable measurements with symptom context, assigns clinical review and documents the services it furnishes.
Key Takeaways
- Pulse oximetry is not spirometry, an arterial blood gas test or an automatic diagnosis of a COPD exacerbation.
- Symptoms and the patient's usual pattern matter even when an oxygen-saturation estimate looks reassuring.
- Measurement instructions and escalation plans should be individualized; one cutoff or oxygen-adjustment rule does not fit every patient.
- Medication and oxygen changes belong to appropriately authorized clinicians, not to a dashboard rule.
- Device-data days, management time and live interactive communication are different billing requirements.
- FairPath organizes records and review work; the practice owns its clinical workforce, treatment decisions and claims.
Start with the clinical question, not the device
COPD RPM is a care workflow, not a prescription for every patient with COPD to take daily oxygen readings. A clinician should identify what will be monitored, why information between visits is reasonable and necessary, and how the team will use it. For one patient, the question may concern an oxygen-saturation trend after a change in care. For another, measurement burden or unreliable technique may make a different follow-up approach more useful.
Connected pulse oximetry provides an SpO2 estimate, pulse rate and timestamps. It does not measure airflow obstruction or replace the tests used to diagnose and assess COPD. A symptom diary may help interpret readings, but typing symptoms or an oxygen value into an ordinary portal does not satisfy Medicare RPM's automatic physiologic-data collection and upload requirements.
Selection therefore involves more than a diagnosis code. The clinician needs an established patient relationship for Medicare RPM, a documented clinical rationale, and a feasible plan for obtaining and reviewing data. The patient or caregiver must be able to use the equipment or receive suitable assistance. A person who cannot obtain dependable readings needs support or a different approach—not repeated reminders followed by a billing assumption.
The enrollment discussion should explain what the team monitors, when it reviews information, how patients contact the practice, consent and expected cost sharing. Remote monitoring is not a promise of continuous observation or an emergency-response service. If severe symptoms develop, the patient should follow the emergency instructions in their established care plan rather than wait for a device alert to be reviewed.
Read oxygen saturation alongside symptoms and measurement context
The FDA's pulse-oximeter guidance explains that readings are estimates and should not be the sole basis for assessing health. Accuracy can be affected by factors including poor circulation, skin pigmentation, skin temperature, nail polish and tobacco use. A connected device does not remove these limitations.
A useful review establishes whether the patient was resting or recently active, whether prescribed oxygen was in use, whether the measurement followed the manufacturer's instructions, and whether the reading belongs to the right patient. The team compares that context with the patient's usual pattern before deciding what the change means.
Symptom context is equally important. Increasing breathlessness, a change in cough or sputum, fever, reduced ability to do usual activities, or a patient saying they feel distinctly worse may need assessment regardless of the displayed number. NHLBI's COPD living-with guidance recommends contacting the provider when symptoms worsen or signs of infection occur and following the prescribed treatment plan.
Check the reading. Listen to the patient.
Measurement quality and clinical symptoms need separate attention.
A measurement concern
Check technique and relevant conditions under the patient’s instructions.
Worsening symptoms
Seek clinical assessment even if the number looks familiar.
Two reviews, two different jobs. In one illustrative case, a patient sends an unexpected reading but feels as usual. The team checks measurement conditions and follows the patient's care plan for a repeat when appropriate, recording both results. In the other, readings look familiar but breathlessness is worsening. That patient needs clinical assessment; the number is not an all-clear. Worsening or severe symptoms follow the patient's escalation and emergency instructions without waiting for a repeat reading or routine device review.
Neither example supplies a universal SpO2 threshold or a treatment algorithm. The patient's clinician establishes the measurement and escalation plan, including what the patient should do while awaiting a response. Changes to oxygen flow, medications or other treatment require the appropriate clinical assessment and authorization.
Choose a device the patient and practice can actually use
The device decision has two parts: whether the equipment and data flow support the intended service, and whether this patient can use them reliably. A consumer wellness product should not be assumed to qualify merely because it displays oxygen saturation or connects to a phone. Medicare requires a device that meets FDA's definition of a medical device and electronic physiologic collection with automatic upload to a secure location available for practitioner analysis.
| Decision | Evidence the practice needs |
|---|---|
| Clinical purpose | A documented reason to monitor this patient's physiologic information between visits |
| Device and intended use | The exact device, relevant manufacturer information and support for the intended measurement |
| Data pathway | A demonstrated automatic upload, correct patient attribution and usable timestamps |
| Patient usability | An observed measurement, understandable instructions and a practical support route |
| Review continuity | A named clinical owner, coverage arrangements and a way to close follow-up work |
Connectivity should be tested where the patient will use the equipment, not only in the office. Training should include a demonstration and a patient or caregiver return demonstration. The team should also explain how to report symptoms, since a device feed may contain no explanation for a concerning value.
Missing readings need investigation. The cause may be a transmission problem, difficulty with the equipment, a hospitalization, a change in care or a patient choosing not to continue. A reminder can be useful, but it is not a substitute for resolving the reason the expected information is absent. The program should have a way to repair, replace, pause or discontinue equipment and to record transitions in care.
Close the loop from review to patient communication
A review queue is only useful if someone owns what happens next. Administrative staff can help with scheduling, delivery and connectivity support. Qualified clinical staff may perform appropriate RPM work under the billing practitioner's general supervision when applicable requirements are met. The practice owns the clinical service and must meet licensure, scope and supervision requirements. A practical coverage plan names the clinical reviewer, the clinician who handles escalations and a backup for absences; the patient's care plan determines the review schedule.
| Activity | Accountable work |
|---|---|
| Enrollment and training | Explain participation, obtain required consent, teach use and confirm the data connection |
| Measurement support | Identify a device or technique concern and follow the established support pathway |
| Clinical review | Interpret trends with symptoms, baseline and prescribed treatment context |
| Treatment decision | Obtain assessment and authorization from a clinician permitted to make the decision |
| Follow-up and documentation | Communicate the plan, record the response and keep the case open until its next step is owned |
Close the clinical loop
A reviewed alert is not necessarily a completed response.
Assess
Read the trend with symptoms and treatment context.
Decide
The authorized clinician maintains or changes the plan.
Communicate
Tell the patient, document the response and name the next owner.
In an illustrative handoff, the reviewer records what prompted contact, the symptoms in the patient's words and the relevant measurement and oxygen context. The note identifies who assessed the patient, what they decided—or that assessment is still pending—and what the patient was told. It ends with a named follow-up owner and a review point drawn from the patient's plan. That makes the next action clear in a way that “alert resolved” does not.
Review does not always lead to a new prescription. A clinician may decide to maintain the plan, arrange an assessment, address technique or transition the patient to another form of follow-up. The important distinction is between recording that data arrived and documenting how the team used it in patient care.
Separate the care record from the Medicare billing record
A clinically useful month does not automatically support every RPM code. For CY 2026, device-supply services use a 30-day data period, while treatment-management services use a calendar month. The shorter-duration alternatives expand the code structure; they do not turn minimum thresholds into clinical targets.
| Service | CY 2026 Medicare code structure |
|---|---|
| Initial setup and patient education | 99453; CMS adopted a two-day monitoring requirement in a 30-day period |
| Device supply, 2–15 days | 99445 |
| Device supply, 16–30 days | 99454; an alternative to 99445, not an additional code for the same period |
| First 10 minutes of treatment management | 99470 |
| First 20 minutes of treatment management | 99457; an alternative to 99470 for that calendar month |
| Each additional 20 minutes | 99458, following the 20-minute base service 99457 |
One program. Two clocks.
CY 2026 Medicare RPM separates device evidence from management work.
Device data · 30 days
2–15 days: 99445. Or 16–30 days: 99454.
Management · calendar month
First 10 minutes: 99470. Or first 20: 99457. Additional 20 after 99457: 99458.
CMS explains that the 10- and 20-minute base codes are not additive. Live interactive communication with the patient or caregiver contributes to the management total but does not need to make up all of it. The record should identify who furnished the work, the time, the communication and its clinical substance. Scheduling, shipping or automated reminders should not be treated as management merely because they appear in a work log.
CMS did not make treatment management contingent on having 16 days of data. For example, 11 qualifying device days point to the shorter device-supply alternative rather than 99454. Separately, 22 minutes of qualifying management work with the required live interaction may support the 20-minute base when the other requirements are met. It does not support an additional 20-minute unit. Neither the device-day count nor the minute total alone establishes a payable claim.
Medicare permits only one practitioner to bill RPM for a patient in a 30-day period and does not permit concurrent RPM and remote therapeutic monitoring (RTM) billing for the same patient. When RPM is furnished alongside another care-management service, independently satisfy the applicable rules and do not count the same time or effort twice. Medicare Advantage and other payers may have different coverage, authorization or payment policies; confirm the patient's actual payer before projecting revenue.
Where FairPath fits
The platform keeps the enrollment, device and review records available to the people doing the work.
| Function | What your team owns | What FairPath records or surfaces |
|---|---|---|
| Enrollment | Medical necessity, consent discussion and patient education | Enrollment and consent records |
| Device context | Qualification, patient training and reliable measurement | Device information and associated patient context |
| Clinical review | Clinical workforce, supervision, assessment and escalation | Review queues and clinician-workspace context |
| Communication | Authorized care instructions and follow-up | Time and communication documentation |
| Period close | Code selection, supporting evidence and the claim decision | Billing-review items for human assessment |
Records and queues can make work easier to find. They do not prescribe oxygen, establish medical necessity or guarantee that a claim is supportable.
Common questions
Can a patient enter pulse-oximeter readings manually? Manual reports may inform care, but they do not replace Medicare RPM's automatic electronic physiologic-data collection and upload requirements.
What happens when readings stop or the patient leaves the program? Find out why: equipment, connectivity, hospitalization, a change in care or the patient's choice may explain the gap. Repair, replace, pause or discontinue equipment as appropriate, record the transition and evaluate that period's billing against the services actually furnished.
Does the practice need 16 days before it can do useful management? No. Clinical need guides care, and CMS does not impose a 16-day device-data prerequisite on treatment management. Each billed service still needs its own evidence.
Does monitoring replace routine COPD care? No. It supports an individualized plan that may also include visits, medication review, inhaler education and other appropriate care.
Related FairPath Guides
- RPM program guide
- 2026 RPM coding changes: 99445 and 99470
- Who can bill RPM and perform the clinical work?
Sources
- CMS CY 2026 Physician Fee Schedule final rule, remote-monitoring section: code alternatives, communication, management and setup requirements.
- CMS MLN901705: Telehealth & Remote Monitoring, December 2025, pages 12–13: data, patient relationship, device, supervision and billing requirements.
- CMS remote patient monitoring overview.