CO-272: Coverage rules or program criteria not met

The payer is telling you that, under the member's benefit plan or the payer's program rules, the service as billed is not covered. In plain terms, they are saying their internal coverage criteria or care-management guidelines were not met for the date, code, provider, or setting you used. Mechanically, the claim hits an edit that checks diagnosis, procedure, place of service, provider type, authorization, and the member's specific benefit package against payer rules. When the claim fails that rule, the payer assigns CO-272 and moves some or all of the charge into a contractual adjustment, which you cannot bill to the patient unless the denial is overturned.

You will see CO-272 a lot when a behavioral benefit has very specific program rules: for example, a commercial plan that only covers PHP when the member first had a failed trial of IOP, or a Medicaid plan that only covers residential for certain diagnoses or ASAM levels. If your documentation or coding does not match those rules, the days come back with CO-272 and the daily rate becomes nonpayable. It also shows up when behavioral health is carved out to a separate vendor that uses its own clinical guidelines. For instance, you may bill H0015 for IOP to the medical payer, but the BH vendor requires a specific diagnosis list or minimum weekly hours and denies for CO-272 when their system does not see those elements in prior review notes. Telehealth PHP or IOP can also trigger it if the payer only covers on-site services or only covers telehealth for individual therapy but not groups. Medication-assisted treatment and OTP services can hit CO-272 if the payer requires certain diagnoses, age ranges, or participation in counseling. Example: buprenorphine management billed with 90834 on the same day for therapy, when the payer's MAT guideline only covers medical management without same-day psychotherapy at that level of care.

• Check the full remit, including any RARC codes and denial letter, to identify the exact guideline the payer cites.
• Compare the denied service to the member's benefits, payer clinical policy, and program rules for that level of care and code.
• Confirm that diagnosis codes, POS, modifiers (like 95 or 93), units, and rendering provider type match the coverage criteria.
• If it is a coding or data mismatch, correct the claim (codes, modifiers, POS, NPI, authorization number) and submit as a corrected claim per payer rules.
• If the service truly meets the guideline but the payer disagrees, prepare an appeal with clinical notes, ASAM or LOCUS scoring, treatment plan, and any care-management approvals.
• Track CO-272 denials by payer and service line so you can escalate patterns through provider relations if needed.

• Build payer-specific coverage grids for each level of care, code family, and telehealth option, and require staff to check them at admission.
• Configure your scrubber to flag claims where diagnosis, POS, provider type, modifiers, or units do not align with known payer program rules.
• Tighten clinical documentation templates so medical necessity and program criteria (symptoms, risk, functional impairment, ASAM level) are clearly stated for every concurrent review.
• After each contract update or payer policy revision, review behavioral benefits and update billing rules, prior auth workflows, and coding guidelines.