Empowering Your Practice: April 29, 2026 Weekly Updates
Last updated: April 29, 2026
Welcome to your weekly source for essential team updates. Each week, we will share updates designed to help you run a thriving, compliant, and efficient practice. From platform enhancements to compliance changes, this is your go-to resource for staying aligned.
Product & Engineering
Assigned Provider Roles: We’ve updated how Assigned Providers are categorized in client cases to bring more clarity and consistency across MC and Orbit.
Assigned Provider Options
Supervising BCBA
BCBA providers who oversee the case and make treatment plan decisions
Must be the rendering/billing provider when applicable
Only BCBA providers enrolled with the client’s payer will appear as selectable options
Responsible for clinical oversight and authorization alignment
Care Team
Providers who actively support care delivery under the supervising BCBA
Includes BCaBAs, BA-Candidates, and RBTs
May participate in sessions and documentation based on permissions
Observing Team
Providers with visibility into the client record but no care delivery permissions
Commonly used for unenrolled BCBAs
Full details and assignment instructions are available in the attached Knowledge Base article: Assigned Provider Roles in Client Cases
Clinical Quality & Compliance
97153/97155 Paired Compliance Requirements: We’re introducing an upcoming update to support paired compliance requirements for 97153/97155 sessions.
With this change, RBTs will be asked to select the BCBA who attended the supervision session that overlaps with the direct services session. To keep everything aligned, the BCBA selected on the 97153 session will need to match the BCBA who signs the corresponding supervision note.
To help ensure accuracy and compliance, note completion will be blocked unless:
Both linked sessions (97153 and 97155) are present
Each note independently meets all completion requirements
This update is designed to prevent mismatches between the BCBA selected for supervision on 97153 and the servicing provider on 97155, helping keep documentation consistent and audit-ready.
Cigna and Tricare plans are not subject to these 53/55 paired compliance requirements.
Credentialing and Billing
Adding/Updating Insurance Reminder: We wanted to share a quick reminder to help keep insurance updates running smoothly across systems.
When adding or updating insurance details, please be sure to make all changes in Mission Control rather than directly in Silna. Once information is entered in MC, it will automatically sync over to Silna for you. To help avoid any delays with benefits, eligibility checks, or authorizations, please do not make manual updates in Silna.
If you notice that insurance details aren’t populating in Silna as expected, feel free to reach out to our support team using the chat button in MC or Orbit—we’re always happy to jump in and help get things resolved quickly.
For more details, you can check out our Support Article: Manually Adding/Updating Insurance in Mission Control (MC)
Medicaid vs MCO Coverage: We’ve noticed some cases where “Medicaid” is being selected when adding insurance, even though the client actually has a Managed Care Organization (MCO) plan.
As a reminder, please be sure to:
• Check the insurance card before adding coverage
• If a plan name is listed (e.g., Molina, UHC Community Plan, BlueCare), select that MCO instead of “Medicaid”
• Only use “Medicaid” for true straight/state Medicaid with no managed plan
• If unsure, please verify with your PSM or RCM before adding coverageThank you for taking a moment to double-check! This will help prevent claim issues and delays.
HR
401(k) Update: Our 401(k) plan is officially moving from Accrue to Vestwell. This change is all about giving you a better, simpler, and more flexible way to manage your retirement savings — while keeping everything you’ve already built fully intact.
During this migration period, employees will temporarily be unable to make changes to their account settings, initiate withdrawals, or complete other account updates.
We’ve been advised that this transition is expected to be completed by May 7.
We appreciate your patience during this time and will share updates as soon as the migration is fully complete.
Please do not hesitate to reach out to @Support or your PSM with any questions!