CMS Added G0685 for an Autism-Likelihood Assessment. Check the OPPS Rules First.

CMS made HCPCS G0685 effective October 1, 2026, in its Hospital Outpatient Prospective Payment System (OPPS) update. The descriptor is for an algorithm-based assessment of the likelihood of autism spectrum disorder, derived from validated analysis of eye-gaze data or other technology. The code describes an assessment of likelihood; it does not itself establish an autism diagnosis or authorize a claim.

The timing has two parts. October 1 is the effective date for dates of service unless the instruction says otherwise. October 5 is the implementation date for the contractor update. CMS’s September 29 transmittal replaced an earlier August instruction and clarified the October release. Outpatient departments should identify which version their billing and claim-edit systems use for each date of service.

Keep the code in its payment setting

This instruction addresses the hospital outpatient payment system. Its publication is not a general announcement that G0685 is payable in a physician office, under the Medicare Physician Fee Schedule, or in every ambulatory setting. Confirm the claim’s setting and payment system before adding the code to a superbill or charge table.

CMS lists G0685 with status indicator S and APC 5734 in the October update. Those fields belong to the OPPS file. Check the current Addendum B and the applicable status-indicator definitions for the service date; do not copy an APC assignment into a different payment system.

Document the service that was performed

The code descriptor references an algorithm-based assessment derived from validated eye-gaze analysis or other technology. A practice should be able to trace the reported service to the assessment actually performed and the report returned. Keep enough operational detail to identify the tool and output used, the date of service, the responsible clinician, and how the result was handled in the clinical record. These are practical traceability controls, not a substitute for a CMS coverage rule.

Keep the clinical interpretation with the qualified clinician. The code’s description of likelihood assessment does not convert an algorithm output into a diagnosis, establish medical necessity, or replace the clinical documentation needed for the billed service. Review the applicable coverage policy and payer instructions separately.

A first-claim release check

Before releasing an OPPS claim that includes G0685, billing and clinical teams can review the same short checklist:

• Confirm the date of service and that the claim is being submitted under the hospital outpatient payment system.
• Verify the full code descriptor, status indicator, and APC against the October 2026 CMS Addendum B and the file version active in the claim system.
• Ask the system vendor which I/OCE release and effective date are loaded; compare test claims around the October 1 cutover and confirm contractor implementation timing.
• Confirm the medical record supports the assessment that was performed and links it to the responsible clinician and service date.
• Review coverage, medical necessity, authorization, and payer-specific edits as separate checks; a code’s presence in Addendum B does not guarantee payment.
• Route mismatches or denials to a named owner and record the code file, claim date, edit result, and resolution without placing patient identifiers in a shared log.

A controlled first claim gives the team evidence about its configuration before the code appears repeatedly in production. For claim-level decisions, use the current CMS files and the relevant payer’s guidance.

Use the change as a workflow check

A new code can touch more than one system: clinical documentation, charge capture, claim edits, vendor tables, and denial follow-up. VOSKPO helps practices connect those steps with documented review and human oversight. A revenue review can map a code change to the claims and workflows a practice actually uses.