CPAP compliance monitoring: catching the patient in the first 30 days

The data is recorded. Nobody is told.

A modern PAP device reports every night through its modem to the manufacturer's cloud platform: hours of use, mask leak, residual AHI. The data arrives on time. What does not arrive is a person looking at it.

Sleep practices we work with describe the same gap. The platform holds the numbers, and finding a problem means opening it, one patient at a time. No one on the team has the hours to do that daily for every new start. So a problem surfaces when the patient calls the DME supplier or the clinic, and by then the first weeks of the trial are spent.

Those first weeks matter twice. They decide whether the patient gets the clinical benefit of treatment, and they decide whether the device stays covered. Medicare's rule is four hours or more on 70% of nights across a consecutive 30-day window inside the first three months. CPAP compliance sets out the rule in full.

Monitoring turns the nightly record into a short list of patients who need a person today.

The signals that matter in the first 30 days

Five signals carry almost every early problem. The clinic sets every threshold.

The first three are logistics. The fourth is clinical. The fifth is arithmetic, and it is the one most programs never compute.

Nights to spare: the number to watch

Compliance needs 21 nights of four hours or more in a 30-night window. A window can absorb nine missed nights. The tenth ends it.

The window can start on any night, as long as it closes inside the first three months. So the question for each patient is not "how many hours this week" but "for every window that can still close in time, how many misses are left?"

A patient who has missed six of the first twelve nights has three to spare in the window that started on night one. Later windows are still open, with their own counts. A program that shows each patient's nights to spare, every morning, tells staff who to call before the count reaches zero, not after.

Average hours hide this. Eight hours on three nights and nothing on four averages over three hours a night. It is three compliant nights out of seven.

From signal to action

Every signal ends in one of three places: a text to the patient, a task for the clinic's staff, or a referral to the DME supplier.

Texts never carry the number. "Your mask leak was high last night" gets a worried patient. "If your mask feels loose or noisy, call your equipment supplier at this number" gets a refit.

Staff make the call. A live, two-way call is also the interactive communication that the RTM treatment-management code needs each month. The call that solves the problem is the call the month needs.

Equipment problems go to the supplier. Mask fit, replacement parts and device faults belong with the DME supplier. The clinic decides which supplier the patient is sent to and records that the patient was sent.

Clinical signals go to a clinician. A high residual AHI is a question about the therapy. The agent opens a review task. It does not text the patient about it.

Every task closes with a disposition: reviewed, called, sent to supplier, visit booked, plan changed, or unable to reach. It is logged with the time and the person.

A first-month timeline

• Day 0. Setup and education documented. RTM consent recorded. The practice's path to the device data confirmed.
• Days 1 to 3. First check for any data at all. A device that never reported is the fastest problem to fix.
• Days 4 to 14. Daily sort into on track, slipping, no data and device problem. Texts to slipping and silent patients within a day. A staff call by day 7 for anyone still slipping.
• Days 15 to 30. Nights to spare checked every morning. When a window is about to fail, the clinician decides what changes: refit, pressure review, re-education, a different interface.
• Day 31 onward. The re-evaluation booked as soon as the patient has a qualifying window, inside day 31 to day 91.

CPAP compliance has the full day-0 to day-91 program calendar and the RTM codes that pay for it.

Guardrails

• Consent first. No outreach until consent is on the chart.
• Quiet hours. Texts go out between 08:00 and 20:00 in the patient's local time.
• STOP ends texts at once. Staff get a task to reach the patient by phone.
• Not an emergency line. Patients are told texts are not monitored as an emergency service and to call 911.
• One open task per signal. New nights update the open task. They do not stack.
• The clinic owns the clinical content. Thresholds, wording and the supplier list come from the clinic.
• Everything is logged. Every text, reply, task, call and disposition sits on the patient's record, so the month's evidence builds as the work happens.

How Caesar Health runs it

Caesar runs PAP adherence as a remote therapeutic monitoring program inside a clinic operating system, the same layer that answers the practice's phone and books its schedule. It is not a device and it does not replace the manufacturer's platform. The RTM software page covers the program in full.

Caesar Health is HIPAA compliant, signs a Business Associate Agreement at contract, and has SOC 2 Type II in progress.

What Caesar does not do

• It does not change a pressure setting or prescribe an interface.
• It does not interpret a residual AHI. A clinician does.
• It does not place the clinical call.
• It does not bill. The practice bills under its own provider numbers, from the gate.
• Its activity is not billable time. The treatment-management codes pay for a person's minutes.