What makes a state-agency purchase different?
A state agency may need to govern a network of providers, credentials, programs, funding, services, and reports while preserving local delivery models, statutory authority, procurement duties, accessibility, privacy, and public accountability.
CMS confirms that state Medicaid programs define peer qualifications and supervision within their benefits, which makes effective-dated jurisdiction configuration important. The software should represent the official rule and source, not convert a configurable setting into legal authority.[1][2]
Which agency requirements should be explicit?
Separate statewide standards from program, provider, payer, region, grant, and local variation. Name who can propose, approve, test, publish, monitor, and retire each configured rule.
| Criterion | How to evaluate it |
|---|---|
| Authority and procurement | Statute, regulation, plan, waiver, contract, grant, budget, procurement method, evaluation, approvals, and protest or record duties. |
| Network | Providers, peers, supervisors, credentials, sites, regions, programs, contracts, status, and effective dates. |
| Service rules | Population, service, plan, authorization, modality, documentation, supervision, code, unit, rate, limit, and source. |
| Data governance | Purpose, collection, standard, identity, consent, access, sharing, quality, retention, public records, export, and deletion. |
| Reporting | Program, provider, region, population, equity, service, workforce, funding, outcome, denominator, suppression, and methodology. |
| Operations | Identity, security, accessibility, environments, integrations, support, incident response, change control, continuity, and exit. |
Which statewide scenarios should vendors prove?
Test one central standard, two local variations, a rule change with an effective date, a provider transition, corrected data, a public or legislative report, and contract termination.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Rule publication | Official source becomes a versioned configuration after approval and testing | Past periods retain prior rule |
| Provider onboarding | Enrollment, contract, site, peer, supervisor, training, access, and data exchange are validated | Incomplete provider remains clearly pending |
| Local variation | Approved regional or program difference works without copying an uncontrolled system | State and local ownership stay visible |
| Reporting | Statewide totals reconcile to providers with denominators, missingness, suppression, and corrections | Provider can review its own contribution |
| Transition | Provider, vendor, or contract change preserves required records, definitions, access, and continuity | Tested export and transition plan |
What should an agency ask during procurement?
Require responses that distinguish base product, configuration, custom work, integration, professional services, partner dependencies, planned features, and ongoing state responsibilities.
- Which requirements can be met in the current product and contract period without custom code or a single implementation partner?
- How will the state own data definitions, configuration history, interfaces, reports, documentation, and usable exports?
- How are accessibility, language access, rural connectivity, tribal and local governance, and varied provider capacity tested?
- What evidence supports security, privacy, availability, incident, subcontractor, support, and disaster-recovery commitments?
- How can providers or the state transition to another vendor without losing required records, history, definitions, or service continuity?
What should the state avoid?
Avoid buying a rigid statewide workflow, relying on unverifiable compliance labels, or creating a data collection burden whose purpose, authority, quality, and use are unclear.
Use written acceptance criteria, transparent evaluation, conflict management, source-backed configuration, role-based pilots, provider and peer input, security and legal review, and an exit plan. The product should increase accountability while leaving policy and program judgments with authorized people.
Frequently asked questions
Should a state require every provider to use one workflow?
Not automatically. Standardize what authority, interoperability, reporting, quality, or contract requirements justify while preserving approved service-model and local variation.
Can the vendor encode state Medicaid policy?
It can implement approved configurations, but the state and authorized program owners remain responsible for official policy, effective dates, interpretation, testing, communication, and correction.
Should the state collect participant-level data?
Only with a defined authority and purpose, appropriate minimization, privacy and security controls, access, retention, quality, transparency, and review. Aggregate data may serve some needs.
What matters most in an exit clause?
Timely usable data and metadata, configuration and history, ongoing access where required, transition support, secure deletion when authorized, fees, verification, and continuity responsibilities.
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.
- 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.
- Core Competencies for Peer Workers in Behavioral Health Services: Substance Abuse and Mental Health Services Administration. Federal framework for recovery-oriented peer work, role clarity, and person-centered practice.
- Peerakeet Platform: Peerakeet. Peerakeet's five connected product pillars and human-guided approach.