Add Medicaid doulas as a billing specialty: ProviderOne and CHAMPS 837P requirements

A company is not ready to add this specialty merely because its software can create a professional claim. The operating entity must be recognized for the state lane, the provider must authorize or associate the company as required, and any required electronic transaction testing must be complete before production submission.

For Washington, HCA says a billing agent or clearinghouse must enroll with Apple Health, complete the ProviderOne application, and execute a Trading Partner Agreement. HCA also requires successful EDI testing for each HIPAA transaction the company plans to use and publishes an 837 Professional companion guide.

For Michigan, only a billing agent can enroll in CHAMPS. Michigan lists doulas among the provider types that use the ASC X12N 837P 5010 Professional format for electronic claims or the Professional direct-data-entry option in CHAMPS, and Michigan Medicaid billing agents must complete B2B testing.

Washington HCA requires a billing agent or clearinghouse to enroll with Apple Health so HIPAA transaction data can be tracked. The state enrollment page directs the company to complete its ProviderOne enrollment and Trading Partner Agreement, then gives provider-side instructions for adding the approved billing agent or clearinghouse.

The current birth doula billing guide says claims generally must be submitted electronically to HCA, with limited exceptions. It describes both ProviderOne direct data entry and HIPAA EDI paths. A company planning to submit 837 Professional files should use HCA's current ProviderOne 5010 companion guide and complete HCA's transaction-specific testing before production use.

Washington's current birth doula guide also says HCA pays covered birth doula services through its fee-for-service system, including when the beneficiary is enrolled in an HCA-contracted managed care plan. That state-specific destination should be confirmed against the guide in effect for the date of service.

Michigan distinguishes billing agents from clearinghouses, software vendors, and service bureaus. Those organizations may handle electronic claims, but the state says only a billing agent can enroll in CHAMPS. Michigan also says a provider associated to a billing agent cannot complete a new enrollment until that billing agent is approved in CHAMPS.

Michigan requires Medicaid billing agents to complete B2B testing for HIPAA-compliant transactions and provides 5010 837 claim test instructions. The state's professional-provider page places doulas in the 837P 5010 or Professional CHAMPS direct-data-entry lane. Michigan also expressly prohibits use or storage of its Medicaid data on systems or servers outside the United States.

Keep the payer boundary exact. A CHAMPS-enrolled doula may submit fee-for-service, or straight Medicaid, claims through CHAMPS. Services for a Medicaid Health Plan member must be billed to that member's plan after the plan's own contracting and credentialing requirements are satisfied. The DoulaPaid application covers the straight Medicaid CHAMPS lane, not Medicaid Health Plans.

State approval and transaction testing are separate. Check that the approved submitter, provider relationship, current companion guide, and tested production path all refer to the same legal entity and billing route.

The runbook should also assign ownership for claim responses, corrections, remittance information, timely filing, and state-guide changes. Those are operational controls, not payment promises. A claim can pass syntax checks and still fail coverage, enrollment, documentation, coding, or payer-policy review.

HHS identifies billing and claims processing as business-associate functions when they involve protected health information. A billing company handling claims therefore needs its own HIPAA analysis, written agreements where required, safeguards, access controls, incident process, and secure systems before receiving private data from a provider.

DoulaPaid stays outside that private claim path. Its public application receives company qualification information only. If a company is selected, the billing company contracts directly with each provider and handles private data only in its own approved environment under the agreements that apply to that relationship.

A PHI-free application does not make the billing company's systems PHI-free. It keeps DoulaPaid's public application out of the data path; the company that performs billing still has the compliance duties created by its own work.

The written application is a company-level qualification screen. One-state companies may apply. The form asks about the exact state lane, Medicaid experience, capacity, business-associate readiness, insurance, exclusion screening, security-program status, direct provider agreements, and fixed commercial terms. It does not ask for a call, patient data, claim files, portal credentials, or state credential numbers.

An application is not state approval and DoulaPaid does not verify production access through the public form. The billing company remains responsible for proving its enrollment, testing, provider authorization, insurance, security, and legal readiness before any private work begins.

Applying does not guarantee selection, a contract, claim volume, collections, or revenue. Commercial arrangements involving Medicaid work should be documented and reviewed by qualified counsel. HHS OIG notes that federal program fraud-and-abuse analysis depends on the facts and intent of an arrangement, and fair market value alone is not a guarantee of legality.