What must Medicaid peer software connect?
It must connect the truthful service record with the exact state, payer, benefit, provider, practitioner, authorization, documentation, coding, unit, limit, and submission rules effective on the service date.
CMS explains that states design Medicaid peer-support benefits and define qualifications and supervision. HCPCS codes provide national descriptions, but a code does not establish state coverage. The provider organization remains responsible for confirming its enrollment and claims.[1][2]
Which Medicaid controls should be visible?
Separate source facts, configured rules, calculated results, exceptions, reviewer decisions, transactions, and payer responses. This preserves accountability when a rule or interpretation changes.
| Criterion | How to evaluate it |
|---|---|
| Organization | Enrolled provider, NPI, taxonomy, location, contract, revalidation, service scope, and effective dates. |
| Peer | Identity, credential, enrollment or affiliation, training, supervisor, restrictions, and service-date qualification. |
| Participant | Eligibility, benefit, payer, plan, authorization, consent, service plan, and coverage dates. |
| Encounter | Actual service, date, time, location, modality, activity, goal, response, note, author, signature, and review. |
| Claim rule | Code, modifiers, POS, units, limits, rate, diagnosis source, filing, companion guide, and official source version. |
| Lifecycle | Hold, approve, submit, acknowledge, reject, adjudicate, deny, adjust, pay, correct, appeal, and reconcile without overwriting evidence. |
What should a Medicaid workflow demo prove?
Use one state and payer with current official sources. Test a clean individual service, group, telehealth when covered, partial time, expired credential, missing authorization, overlap, denial, correction, and payment reconciliation.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Pre-service | Eligibility, benefit, provider, peer, plan, authorization, and limits are verified | Source, effective date, result, and unresolved hold |
| Service | Actual encounter and participant-centered documentation are complete | Schedule does not replace service truth |
| Claim preparation | Code, modifiers, units, POS, diagnosis source, provider fields, and filing are reproducible | Rule version and reviewer approval |
| Transaction | Submitted payload, acknowledgment, claim number, status, remittance, adjustment, and payment remain linked | No silent resubmission or overwrite |
| Exception | Invalid or uncertain data holds the claim and routes the right owner | Resolution preserves original evidence |
| Reconciliation | Claims, remittance, deposits, denials, corrections, refunds, and ledger or reporting entries match | Unresolved differences stay visible |
What should a complete billing workflow handle?
A complete workflow connects the service record, applicable rules, human review, billing activity, correction, and reconciliation without losing history or ownership.
- Which states, payers, programs, codes, modifiers, units, provider types, and effective dates are configured and currently maintained?
- Who validates source changes, approves configuration, tests non-production behavior, and communicates the effective date?
- How does the product connect billing preparation, review, correction, denial work, and reconciliation?
- What remains the provider's responsibility, and which services are performed by the vendor, clearinghouse, billing agent, or other party?
- Can every proposed and submitted claim be reproduced from service evidence, rule version, reviewer decision, and transaction history?
What should a Medicaid organization choose?
Choose software that connects service delivery, documentation, supervision, billing preparation, exceptions, and reporting while preserving the rules and evidence behind every decision.
The enrolled provider organization keeps its provider identity and reimbursement relationship. Its software should make the operational work clear, connected, reviewable, and defensible across the complete service-to-billing process.[3][1]
Frequently asked questions
Does peer billing software make an organization a Medicaid provider?
No. The organization must qualify, enroll, contract, revalidate, and comply with the applicable state and payer requirements.
Does H0038 mean every peer service is billable?
No. H0038 is a code description. Coverage depends on the state's benefit and payer rules, provider and practitioner requirements, service, authorization, documentation, modifiers, units, limits, and date.
How should software handle state and payer variation?
It should connect effective-dated rules and official sources to the service workflow, then keep exceptions, reviews, decisions, and changes visible.
Who receives Medicaid reimbursement?
The enrolled provider organization remains the provider of record and receives reimbursement. Software and billing support do not replace that provider identity.
Sources and product pages
Government sources establish the legal and program requirements covered here. Official vendor pages document the product capabilities and positioning used in this guide.
- Medicaid and CHIP Coverage of Peer Support Services FAQ: Centers for Medicare & Medicaid Services. Federal baseline explaining state authority over peer qualifications, supervision, and benefit design.
- Healthcare Common Procedure Coding System: Centers for Medicare & Medicaid Services. Official source for current HCPCS Level II files and national code definitions; a code does not by itself establish state Medicaid coverage.
- Document: Notes, Assessments, and Supervisor Review: Peerakeet. Peerakeet structured notes, assessments, signatures, and review workflows.
- The HIPAA Security Rule: U.S. Department of Health and Human Services. Official federal overview of safeguards for electronic protected health information.
- Understanding Confidentiality of Substance Use Disorder Records: U.S. Department of Health and Human Services. Official federal overview of 42 CFR Part 2 applicability, consent, use, disclosure, and breach obligations.