What Does Remote Monitoring Billing Compliance 2027 Mean for Clinics and Care Networks?
For clinics and care networks, remote monitoring billing compliance 2027 means designing remote patient monitoring and remote therapeutic monitoring so that every claim can be tied to a qualifying patient, an appropriate order, a real service, and a payment rule effective on the date of service. It does not mean that CMS has finalized a ban on third-party RPM, even though the 2027 Physician Fee Schedule proposed rule triggered that shorthand in recent commentary. The proposed rule would prohibit payment for remote monitoring furnished under arrangements with a third party that has not itself submitted a claim to Medicare for its portion of the service. The ban would also reach a party that billed Medicare for a different service involving the same monitoring device, which was a narrow but consequential restriction. JD Supra, Fierce Healthcare, Bipartisan Policy Center
Also worth reading: How Do Clinics Turn RPM Compliance into Measurable Performance in 2026? · What Is the Definitive RPM Coding Compliance Checklist for Healthcare Clinics in 2027? · How Do Clinics Validate Patient Monitoring AI Bias Testing Protocols Today?
The proposed rule is not the whole compliance story. Current CMS rules still govern device and data requirements, the 16-day collection threshold, consent, supervision, medical decision-making, time, incident-to rules, and the prohibition on counting the same minute toward both time-based and non-time-based professional services. A device may collect data without a qualifying medical device, but the collected information must be a type of data allowed under the applicable CMS program. If the device is a general wellness product, the program rules matter even more because wellness data alone does not automatically support an RPM or RTM claim. CMS has also continued to warn against using Bluetooth-enabled blood-pressure cuffs merely to enter an office reading or manufacture a day of data.
The practical answer is therefore to build around the rule that applies on each claim date, not around the product name on a vendor dashboard. A care network may be comfortable in 2026 and exposed in 2027 if its contracts, workflow, and audit files assume that a vendor can bill while the clinic bills separately. The safer approach is to decide who is furnishing each service, who submits each claim, who owns the documentation, and what happens if the proposed restriction becomes final. A care-coordination platform can support that discipline, but software cannot cure a service that was not medically necessary, not properly ordered, or not actually furnished.
The 2027 CMS Change and Why It Matters
CMS proposed the change in the 2027 Physician Fee Schedule proposed rule, which was released on 18 June 2026. CMS received comments through 14 July 2026. The proposal would change the interpretation of remote monitoring services furnished under arrangements with another person or entity. Under the current CMS guidance, a practice may bill for RPM or RTM furnished under an arrangement when the practitioner meets the requirements, even if a vendor supplies the device, collects the data, or performs some of the required work. The proposed rule would narrow that path for 2027 claims.
The proposal would not eliminate every outsourced activity. A vendor could still support a clinic with technology, patient outreach, workflow, and clinical coordination, provided the clinic or its own practitioner is the party submitting the applicable claim and the service meets all other requirements. The danger is a two-claim arrangement in which the vendor bills Medicare for one service and the clinic bills for another service based on the same monitoring relationship. CMS described this as a concern involving duplicate or otherwise impermissible payment, not as a general finding that every vendor-supported program is improper.
The proposal also contains a device-specific restriction. If a third party has already billed Medicare for a different service involving the same remote monitoring device, the clinic generally cannot use that same device to support another remote monitoring claim. This matters for networks that have several affiliated practices, shared devices, or vendor contracts that shift billing responsibility from one entity to another. The issue is not only whether the data arrived; it is who furnished the service and which entity claimed it.
Clinics should treat the proposal as a planning trigger rather than a final policy. The final rule may change the language, scope, or effective date. Commercial payers may also take a different position. Contracting teams should nevertheless prepare now because a 2027 claim file must show a consistent billing owner, a valid device history, and a documented clinical relationship. The BPC commentary and industry alerts are useful context, but they are not substitutes for the Federal Register text, CMS guidance, or the final rule. Healthcare Finance News, Buchanan Ingersoll & Rooney, The Clinical Trial Vanguard
The Current Billing Rules That Still Matter
RPM and RTM are related Medicare programs, but they are not interchangeable. RPM generally concerns physiologic data such as blood pressure, glucose, weight, pulse oxygen saturation, or other data used to monitor a medical condition. RTM is designed for non-physiologic data and functional measures, such as respiratory therapy adherence, mobility, or other therapeutic monitoring information. A care network should not assume that a device approved for wellness can be converted into an RPM device simply by placing it in a patient portal.
A current RPM claim normally requires a qualifying health condition, a valid order or care plan, patient consent, a device that transmits the required data, and collection of data on at least 16 days during the 30-day measurement period. The practitioner or qualified care professional must provide the required clinical review, communication, and medical decision-making. The billing practitioner must be the one who orders the monitoring and must either furnish the required services personally or satisfy the applicable supervision and incident-to conditions. A vendor may perform work, but the claim file must still identify the responsible practitioner and the services that support the code.
Time can support certain professional services, but it must be documented with the correct start and stop times or a credible equivalent record. Time spent on one service cannot be counted again for another service in the same period. The same patient data cannot be used to create separate claims for unrelated practitioners unless each claim independently satisfies the program rules and the billing entity is clear. A dashboard showing 20 connected days does not prove that the patient was enrolled, that the data were clinically reviewed, or that the required communication occurred.
The 16-day rule is a minimum collection threshold, not a promise of payment. A patient who generates data on 16 days but has no qualifying order, no clinical review, or no documented medical decision-making does not automatically create a billable service. Conversely, a short enrollment may still be clinically useful even when it does not meet a particular code requirement. Care networks should separate operational metrics from billing eligibility so that revenue goals do not distort clinical judgment.
A Safer 2027 Billing Model for a Care Network
The safest model is to assign one billing owner for each Medicare remote monitoring service and make that owner visible in the contract, the electronic health record, and the audit report. The owner should be the practitioner or entity that can demonstrate that it furnished the service and submitted the claim. If the vendor is the billing owner, the vendor must meet the applicable Medicare requirements for its claim. If the clinic is the billing owner, the contract should state that the vendor is supporting the clinic rather than creating a second, parallel claim for the same device or monitoring relationship.
The contract should also specify who owns the device, who pays for it, who maintains it, and who is responsible for patient outreach. These questions affect both compliance and patient experience. A low device cost may look attractive, but a network still needs a plan for lost devices, connectivity failures, duplicate enrollments, and patients who stop responding. The agreement should identify the data fields used for billing, the process for correcting a missing day, and the procedure for handling a patient who changes primary care practitioners.
The care-coordination workflow should begin with eligibility and consent, not with a sales enrollment. The clinician should confirm the qualifying condition, order the monitoring, explain the expected data collection, and document the patient’s agreement. The platform should then collect only the data needed for the stated clinical purpose. Automated reminders can improve adherence, but they should not be used to pressure a patient into generating data for a code.
For networks with several sites, the billing owner should be checked at the patient, practitioner, and service levels. An affiliated practice may use the same vendor and the same dashboard while still having different billing responsibilities. The audit file should preserve the order, consent, device identifier, daily transmission record, clinical review, communication, time record, and claim history. That file is more useful than a single vendor certification because it shows how the service was actually delivered.
Comparison: Outsourced, Clinic-Owned, and Hybrid Models
| Feature | Vendor as billing owner | Clinic as billing owner | Hybrid model |
|---|---|---|---|
| Claim responsibility | Vendor bills Medicare for its service | Clinic or designated practitioner bills | Each party bills only its own documented service |
| Best fit | Vendor can directly satisfy all Medicare requirements | Network wants centralized clinical ownership | Multiple sites use one platform but separate claimants |
| Main risk | Vendor must prove furnishing, order, consent, data, and time | Clinic must prove every element and avoid duplicate claims | Contract boundaries can become unclear |
| Device handling | Vendor normally controls device lifecycle | Clinic or site controls device lifecycle | Device ownership and transfer must be explicit |
| 2027 exposure | Lower if the vendor submits the only applicable claim | Lower if the clinic is the sole claimant for the service | Highest if two parties bill for the same monitoring relationship |
A clinic-owned model gives the practice more control over the clinical relationship and may fit a network that already has care managers, nursing staff, and billing teams. It also creates more work. The clinic must train staff, monitor data quality, document review and communication, and ensure that the vendor is not independently creating a second claim. This model can be appropriate when the practice wants to keep ownership of the patient relationship and use the vendor mainly as a technology and workflow partner.
The hybrid model is common in large networks, but it needs the clearest contract. One site may bill for RPM, another may bill for RTM, and a vendor may bill for a separate service involving a different device. That can be legitimate when each service is distinct and each claimant documents its own work. It becomes risky when the same patient, device, and monitoring period are used to support overlapping claims. The comparison table is a planning tool, not a payment guarantee, and commercial contracts should be reviewed by qualified counsel.
Practical Steps for Compliance Teams
The first step is to create a one-page rule map for every remote monitoring service. It should identify the program, the qualifying condition, the billing owner, the device, the required data, the consent process, the supervision model, and the documentation owner. The map should be versioned because a 2026 workflow may not remain valid in 2027. It should also distinguish Medicare rules from commercial-payer rules, since a contract that satisfies one payer may not satisfy another.
The second step is to reconcile contracts with actual claims. Select a sample of active patients and trace each claim from the order through the device, daily data, clinical review, communication, time record, and payer submission. Check whether the vendor billed Medicare for a different service involving the same device. If the answer is yes, determine whether the services were truly separate or whether the arrangement creates duplicate or overlapping payment. A small audit sample can reveal a systemic contract problem before a larger payer review.
The third step is to fix the daily workflow. Staff should verify that the patient has a valid order and consent before enrollment, confirm that the device is transmitting, and document the reason for any missing data. A missed day should be handled as a care-coordination issue, not as a reason to backfill a number. If a patient cannot generate data for 16 days, the team should document that outcome and avoid presenting the enrollment as a successful RPM episode.
The fourth step is to test the time record. For services supported by time, the record should show the date, practitioner or qualified professional, start and stop times, and the activity performed. The record should make clear why the time belongs to the claimed service and why it was not used for another service. A vendor report that says “120 minutes reviewed” is not enough if it does not identify the service, the person performing the work, and the date.
The fifth step is to monitor outcomes and claims together. A network should track enrollment, active days, response rate, escalation rate, readmission or visit impact, patient satisfaction, and denied claims. These measures should be reviewed by clinical and revenue-cycle leaders. If a workflow produces many claims but poor clinical response, it deserves redesign rather than praise. If it produces good engagement but frequent documentation gaps, the billing process should be corrected before volume increases.
Common Mistakes and the Costs Behind Them
The most common mistake is treating a vendor platform as proof of a billable service. A dashboard may show that a cuff transmitted a reading, but it does not prove that the patient had a qualifying condition, signed consent, or received the required clinical review. It also does not prove that the practitioner ordered the monitoring or that the claimant furnished the service. The same problem appears when a vendor sends a reminder, records a call, or performs outreach without a clear link to the claimed code.
Another frequent mistake is assuming that all connected devices qualify. A blood-pressure cuff used in a clinic may be useful clinically, but a reading entered manually for that purpose is not automatically RPM data. Bluetooth transmission, a smartphone app, and a connected device are different facts. The compliance team should document how the data were generated, when they were transmitted, and why they meet the applicable program definition.
Cost should be evaluated in the same file as compliance. Device acquisition, shipping, replacement, connectivity, patient support, clinical review, care-manager time, billing staff, software licenses, and denials all affect the economics. A $20 device can become expensive if it produces low adherence, frequent returns, or claims that fail documentation review. A $100 device may be more economical if it improves engagement and reduces avoidable visits, but that outcome must be measured rather than assumed.
Pricing should be compared using a total-cost model. The network should calculate cost per enrolled patient, cost per active data day, cost per completed review, and cost per accepted claim. It should also model a denial rate and the cost of correcting a claim. If a vendor charges a monthly platform fee plus a per-patient device fee, the contract should state whether the fee continues during a nonbillable period. A low headline price is not a good substitute for transparent terms.
The cost of inaction can be larger than the cost of redesign. A denied claim may require staff time to appeal, while a repeated pattern can create overpayment risk, payer scrutiny, and patient complaints. The right response is not to stop all remote monitoring. It is to separate clinical value from billing eligibility and to charge only for services that meet the applicable rules.
When a Clinic Should Act Before 2027
A care network should begin the review as soon as it plans to bill Medicare for RPM or RTM in 2027, especially if a vendor currently submits its own claim. Acting before 2027 gives the organization time to test the workflow, revise contracts, retrain staff, and correct historical file gaps. Waiting until the first quarter of 2027 leaves little time to resolve device ownership, supervision, or claimant questions.
The review should be completed at least 90 days before the first 2027 claim. The final CMS rule may not be available by then, so the network should use a conservative assumption: do not bill two parties for the same monitoring relationship, and do not rely on a vendor claim unless the vendor is clearly the furnishing and billing owner. The network should also confirm whether its commercial payers follow the Medicare approach or have separate rules.
Act immediately if the contract says that the vendor may bill Medicare, the clinic may bill separately, or the same device may be used by more than one site. Act immediately if the device is a general wellness product, if staff routinely backfill missing days, or if time is recorded only as a monthly total. These are not minor administrative details. They are the facts a payer is likely to examine when a claim is questioned.
The organization should also schedule a quarterly audit rather than relying on an annual review. Remote monitoring changes quickly: patients start and stop, devices are replaced, practitioners move between sites, and vendor contracts are renewed. A quarterly sample should include both successful claims and failed or abandoned enrollments. That approach shows whether the program is clinically useful and whether its billing record remains defensible.
What GetPulse Should Do for Clinics and Networks
GetPulse should present itself as the operating layer for consistent care coordination, not as a guarantee of Medicare payment. The product can help a clinic capture the order, consent, device status, daily transmissions, care-team tasks, escalation events, and claim-supporting documentation in one workflow. It can also flag a missing day, an expired consent, a duplicate device assignment, or a practitioner change before those gaps reach billing. Those controls reduce rework and make the clinical story easier to review.
The platform should expose the billing owner for every episode. A site administrator should be able to see whether the clinic, a practitioner, or a vendor is responsible for a given claim, while the care team continues to work from the same patient record. The system should preserve the relationship between a device and a patient, but it should also prevent the same device from being silently reused for an overlapping claim. That design is more useful than a generic “connected” status.
GetPulse should also separate clinical value from billing eligibility. A patient who sends blood pressure readings for 10 days may still benefit from outreach, medication review, or a care-plan adjustment. The platform can document that work without forcing the team to call it RPM. This distinction protects clinicians from treating a code requirement as a clinical target and helps networks report real outcomes.
Finally, GetPulse should make compliance visible without turning every staff member into a compliance officer. Alerts should be specific: “Consent expired,” “16-day threshold not met,” “time record missing,” or “vendor claim detected for same device.” The care team should see the operational consequence, while billing and compliance leaders see the audit trail. That is the appropriate B2B value proposition for 2027 remote monitoring billing compliance.
Bottom Line
Remote monitoring billing compliance 2027 is not a single CMS rule and not a reason to abandon vendor-supported monitoring. It is a set of requirements that must be satisfied on the date of service, with a clear billing owner, qualifying data, valid consent, appropriate clinical work, and documentation that survives review. The 2027 proposed rule is important because it would restrict payment when a third party bills for the monitoring service or for another service involving the same device. The proposal remains subject to change, so clinics should prepare for the stricter interpretation while monitoring the final rule.
The practical path is to audit contracts, claims, devices, and daily workflows now. Decide whether the vendor or clinic is the billing owner, remove duplicate-claim arrangements, and document every service that supports a code. Use GetPulse or a comparable care-coordination platform to make those facts visible, but do not confuse software visibility with payment. The strongest programs will be the ones that can show both clinical benefit and a clean billing record.