Washington Apple Health doula billing guide

Washington is one of the strongest first states for DoulaPaid because the Apple Health birth doula benefit has a defined billing guide, a published fee schedule, and a payment model that rewards careful unit tracking. The official HCA Birth Doula Services Billing Guide, effective April 1, 2026, is the primary source for eligibility, provider requirements, covered services, documentation, telemedicine limits, limitation extension requests, and claim timing. The HCA fee schedule, effective January 1, 2025, is the source used here for published payment amounts.

DoulaPaid does not replace HCA guidance, ProviderOne, or a biller who knows your organization. The job of the product is narrower and more practical: help a doula, collective admin, or biller see whether a first Apple Health doula claim packet is complete enough to review before manual payer portal work. That means keeping provider setup, client eligibility notes, service lines, visit documentation, missing fields, denial reasons, and payment follow-up in one workflow.

The HCA guide describes birth doulas as nonmedical professionals who provide support during pregnancy, labor, delivery, pregnancy loss, and the postpartum period. For Apple Health billing, the setup path starts before a claim exists. A provider needs to meet Washington birth doula requirements, hold the required Department of Health certification pathway, and enroll with HCA so services can be billed through ProviderOne. HCA also expects providers to follow privacy and security expectations, coordinate care, and maintain records that support the service billed.

Provider setup should be treated as a billing readiness checklist, not a one-time profile page. Before preparing a packet, confirm the legal name or business name, NPI, billing address, certification status, contact information, enrollment status, and the person responsible for final packet review. A collective should also know whether a solo doula, collective admin, or biller/admin owns each step. When this ownership is fuzzy, claims tend to stall after the visit because nobody knows who is supposed to fix the missing field.

DoulaPaid models this as provider setup progress, source notes, and missing-field warnings. The public Washington provider setup checklist is intentionally no-PHI. It helps you review operational readiness without entering client information.

The HCA fee schedule lists three core birth doula service lines. The prenatal intake visit uses CPT 59899 with modifier U1 and pays $750. Additional prenatal and postpartum visits use HCPCS T1032 and pay $25 per unit. Labor and delivery support uses HCPCS T1033 and pays $750. These amounts should stay tied to the source document version because payer schedules can change, and a billing assistant should never publish uncited rates as if they are timeless.

Washington is not a simple global package state. The billing guide explains that prenatal intake and labor support are paid as flat-rate services, while other prenatal and postpartum doula services are paid in 15-minute increments. The guide gives a unit example: a 70-minute visit is billed as four units because it does not reach the midpoint for a fifth unit. That kind of rule is exactly why a packet workflow should show duration, unit calculation, service line, and remaining unit capacity in the same review surface.

HCA also describes a 20-hour, 80-unit limit across prenatal and postpartum visits, with six units designated for postpartum care. The current DoulaPaid Washington ruleset uses that unit-based model as the generality test against the Oregon global-fee model. If a product can represent both the Washington flat-plus-unit structure and the Oregon global package, future states can be launched with ruleset data rather than one-off code paths.

HCA requires providers to retain documentation and submit it upon request. The guide identifies several documentation basics that should be visible before a packet is marked ready: client consent, date of service, time or duration, nature of the services provided, care coordination, referrals, community supports, and screening details when screening tools are used. For a prenatal intake visit, the guide also describes a minimum two-hour visit and expects items such as Apple Health benefit overview, plan of care, birth plan preferences, history review, support establishing care, and mental or emotional health screening coordination.

A good packet review process asks a boring question again and again: does the note support the line? If the service line says timed T1032 units, the note should support the date, duration, and covered doula support. If the packet includes labor and delivery support, the documentation should match that service. If a visit was telemedicine, the reviewer should confirm that the service is eligible for telemedicine and that any in-person prerequisites were met.

Public tools should never collect visit notes. That is why the DoulaPaid Washington documentation checklist is a habit checker, not a note form. The private app is the place for client-specific documentation once production privacy, access control, audit logging, backups, and service agreements are in place.

Eligibility should be verified outside this public page before a packet is built. The HCA guide points providers back to ProviderOne and managed care eligibility checks, and it explains that managed care clients can still receive birth doula services while providers bill HCA fee-for-service directly for the doula benefit. For a practical workflow, that means the packet should include a clear eligibility verification note, the correct client identifier in the private workspace, and enough context for a reviewer to know whether the client was covered on the date of service.

Coverage boundaries matter as much as covered services. The guide states that birth doula services do not require prior authorization, but it also describes limits around telemedicine, audio-only services, overnight postpartum support, and noncovered household tasks. A reviewer should not have to remember all of those rules from memory. The packet should surface prompts when a service line looks like prenatal intake, first visit with a new doula, labor and delivery support, first postpartum-initiated care, or another service where telemedicine or coverage limits can change the billing answer.

Timing is another quiet denial risk. The HCA guide says providers must bill within 365 days from the date of service. A strong packet workflow should therefore flag service dates near the timely filing limit and make the next action obvious. DoulaPaid tracks claim status, denial reason, next action, and payment state because submission is not the end of the billing story. The useful product outcome is not a pretty export by itself; it is a first packet that a real person can review, submit, monitor, and correct without losing the thread.