A code update becomes real when the first claim leaves your office. For ABA clinics, January preparation needs to reach beyond the billing team to scheduling, documentation and payer setup. Start with the handoffs most likely to be missed.
The goal is straightforward: your team should be able to explain what changed, which payer instructions apply and who will resolve a problem before the same error reaches another batch of claims.
The short answer: prepare for the 2027 ABA coding changes by reviewing the applicable code guidance, confirming payer implementation, checking documentation and authorization workflows, and validating claim setup. Treat these as connected tasks with named owners—not a software update that the biller handles alone.
What changes on January 1, 2027?
The ABA Coding Coalition identifies January 1, 2027 as the effective date for the updated adaptive-behavior services code set. Its September 2026 crosswalk describes six new codes, revisions to codes 97151–97158, and the replacement of the previous Category III codes with Category I codes. Read the Coalition’s 2027 crosswalk and accompanying explanation.
That makes this more than a search-and-replace exercise. Review the services your clinic actually provides against the complete 2027 code descriptions and instructions. Use the Coalition’s code overview to orient the discussion, then use the applicable licensed CPT reference and payer guidance for detailed decisions.
A coding effective date does not, by itself, confirm the configuration of every payer system or an individual patient’s authorization. If instructions conflict or implementation is unclear, document the issue and escalate it. Do not improvise a different code simply to get a claim through.
1. Give the transition one accountable owner
A clinical lead may be reviewing documentation while the billing team waits for a payer response and the scheduler continues using an old service list. Each person can be doing their own job well while the overall handoff remains unfinished.
Appoint a transition coordinator and keep one shared issue register. For each item, record the service affected, payer, responsible person, supporting evidence and next action. “Waiting on payer” should include who is following up and when—not become a permanent status.
Make ownership specific. The clinical lead checks whether the record accurately supports the service. Billing checks claim configuration and responses. Operations checks how the change reaches scheduling and staff instructions.
2. Get payer answers you can use
The Coalition’s October 2026 provider communication resource recommends early payer engagement. Three questions deserve written answers:
- When will the payer’s claims system recognize the updated codes?
- Will existing authorizations convert, or is a new request needed?
- What contracted payment terms apply to the affected services?
Save the response with its date and the contact or policy reference. Then translate it into a task your team can complete. An email confirming implementation is useful evidence; it is not proof that your own claim template has been configured correctly.
Keep unresolved questions visible to the practice owner. A payer-specific problem should not quietly turn into a clinic-wide instruction.
3. Check the path from delivered service to claim
Work through one representative scenario at a time with the clinical and billing leads. Compare what was delivered, what the record says and what the proposed claim would report.
- Does the documentation describe the work that actually occurred?
- Is the responsible practitioner or staff role recorded accurately?
- Does the claim setup reflect the reviewed service and applicable instructions?
- Is there a clear route for resolving a discrepancy before submission?
For example, imagine an updated service option appears in the billing system but the note template still prompts staff for an older workflow. That is an illustrative systems problem, not a reason to change the clinical account after the fact. Review the template and staff instructions together, keeping the record faithful to the care provided.
Avoid relying on a code number alone. The supporting activity, documentation and applicable rules still need to agree.
4. Connect authorization decisions to scheduling
Once payer instructions are confirmed, make sure they reach the people arranging the next visit. The scheduler needs to know which issues require escalation and who can resolve them; they should not have to interpret a coding manual at the front desk.
Choose a few realistic scenarios from your own service mix: an authorization that crosses the year boundary, an unresolved payer response, or a service option that is not yet ready in the system. Walk each scenario through the handoff without changing a real patient’s care solely to fit the exercise.
Record the decision and its source. Any question affecting treatment or continuity of care belongs with the appropriate clinical decision-maker, not an improvised billing workaround.
5. Test claim setup before relying on it
Ask your software vendor or clearinghouse what approved testing options are available. Use a test environment or an agreed validation process where possible. Do not send fabricated patient claims or duplicate real claims simply to see what happens.
Check the full route: service selection, claim generation, outgoing fields, returned acknowledgments and the person responsible for exceptions. If an end-to-end test is unavailable, document what was checked and what remains unverified.
A useful test record contains the scenario, expected result, actual result, issue owner and retest outcome. “The screen looks correct” is a weaker conclusion than showing that the relevant output matched the reviewed setup.
6. Review the first live claims as a small learning cycle
After implementation, review an initial sample before assuming the workflow is settled. Look for repeated rejection messages, unexpected adjustments or questions that staff are resolving differently.
Separate the stages of a claim’s progress. Acknowledgment, adjudication and receipt of payment are different events. CMS also distinguishes electronic claim-status requests and responses in its claim-status guidance; confirm the actual messages used by your payer and clearinghouse.
Give recurring issues a single owner and share the verified correction with the affected team. If your practice already tracks clean-claim performance, use consistent definitions so the transition does not make reports misleading.
Your ABA coding-readiness checklist
This is a suggested internal planning checklist, not a payer’s official approval process. Mark each item not started, in progress or confirmed, and attach evidence rather than relying on a verbal update.
- Coding review: the applicable references and services have been reviewed by the right clinical and coding personnel.
- Payer confirmation: implementation questions have written answers, or an unresolved issue has a named escalation owner.
- Documentation: note templates and staff instructions reflect the reviewed workflow.
- Authorization handoff: operations knows how to route transition-related questions.
- Claim setup: testing or validation has a recorded result and any limitations are visible.
- Early follow-up: someone owns the first-claim review and communication of verified corrections.
Start with the first incomplete handoff. Fixing one unresolved dependency can be more useful than declaring an entire department “ready.”
Turn preparation into a clear team handoff
Your clinic does not need every employee to become a coding specialist. It needs each person to understand their part of the transition and where to take a question they cannot resolve.
For broader context, read our guide to managing payer policy changes. If your clinic needs billing-side support, explore PRCM’s medical billing services and discuss the workflow you want to improve.
Discuss your ABA billing readiness with PRCM
This article is an operational planning guide. Use current coding references, payer requirements and appropriately qualified clinical and coding review for individual billing decisions.
