WASHINGTON STATE
WA BHO Reporting, Explained. What Washington agencies actually submit.
Written for agency directors and billing managers in Washington State. The terminology changed in 2020, the 837 requirement did not, and King County has its own rulebook on top. Here is the shape of it, with the authoritative sources linked.
Nobody submits to a BHO any more. Everyone still says it.
Washington’s Behavioral Health Organizations formally ended on 1 January 2020, when the last regions moved to Integrated Managed Care. The BHOs became Behavioral Health – Administrative Services Organizations, or BH–ASOs, and Medicaid behavioral health moved into the same managed care plans as physical health.
Six years on, every agency we work with still calls it BHO reporting. So do we, and so does this page. The label stuck because the work did not change much: you still deliver a service, you still have to report the encounter, and somebody still rejects the file if a code is wrong.
What did change is who you report to, and that now depends on how the service is funded rather than on where you are:
Apple Health (Medicaid) services go to the managed care organisation that holds the member’s plan. In King County, Medicaid-funded behavioral health is administered through the King County Integrated Care Network.
Crisis services and state- or federally-funded programs go to your regional BH–ASO. In King County that is the Behavioral Health and Recovery Division.
Most agencies are doing both, which is the part that makes this harder than it sounds.
The 837 is a file format, not a form.
This is the part that turns a billing question into a software question.
An X12 EDI transaction set — the national standard for transmitting healthcare claims and encounter data from a provider to a payer. It is a structured data file, not a document a person fills in. Washington’s Health Care Authority requires encounter data as X12N 837 Professional and Institutional files.
You do not simply start sending files. Submitters test with HCA first, and only once approved are they cleared to send 837 encounter files in production. Transmission is by SFTP or the ProviderOne web portal.
HCA publishes the authoritative specification in its 837 Professional and Institutional Encounter Data companion guide.
A claim asks to be paid. An encounter reports that a service happened, whether or not money moves for it. Under managed care the state still needs the encounter record, which is why agencies on a capitated or grant-funded contract are reporting data they are not billing against.
Washington’s own behavioral health billing guidance acknowledges that some agencies cannot generate a standard 837 encounter record at all from the systems they run. When that is true, the shortfall is not in your billing staff. It is in the software, and it gets paid for out of payroll — someone exporting, reformatting and rebuilding submissions by hand every cycle.
King County adds its own rulebook.
The Service Encounter Reporting Instructions govern how encounter data is coded and submitted by providers contracted with the King County Integrated Care Network and the BH–ASO. SERI is where the detail lives — which service maps to which code, in which circumstances.
King County’s Behavioral Health and Recovery Division publishes a provider manual that is revised monthly. It is the operative document for contracted providers, and it changes often enough that a printed copy is a liability.
BHRD runs periodic EDV reviews against submitted encounter data, alongside administrative reviews. Agencies also submit third-party reports across Medicaid programs — mental health and SUD outpatient, opioid treatment, and residential.
Practically, this means your encounter data has to be defensible after the fact, not merely accepted at submission. A file that passes validation and a file that survives a review are not the same thing.
The reports already exist. That is the whole claim.
Eight Washington agencies run KeyNotes and submit to BHO today. The reporting is built, configured and in production — not a module to licence, and not custom report development you commission and then wait on.
King County EDI went live in September 2025. We wrote up what shipped in Two Wins for Behavioral Health, and followed it with further integration improvements that October.
It shows up as time, not as a feature. One Seattle-area agency cut its Medicaid billing time by 40% after moving across.
Your reporting document setup is part of onboarding, inside the one-time setup fee. There is no separate reporting licence and no per-submission charge. If a code mapping changes or the county revises something, you call us and we fix it — the people who built it are the people who answer.
A word on what this page is. This is an orientation for agency directors and billing managers who are evaluating software — not a compliance manual, and not advice you should rely on for a submission.
The authoritative sources are HCA’s billing guides and fee schedules, HCA’s companion guides, your MCO contracts, SERI, and your BH–ASO’s provider manual. They are revised continually; King County’s is reissued monthly. If something here disagrees with them, they are right and we will fix this page.
If you are evaluating an EHR, the question worth asking every vendor is narrower and more answerable: are the reports already built and in use by agencies like mine, or am I commissioning them?
Serving behavioral health agencies across Washington State since 2005.
Thirty minutes on your own workflows — clinical, billing, and the BHO submissions you actually have to file. Bring your billing manager.
