What is the purpose of credential tracking?
Its purpose is to help the organization verify and maintain the exact qualification, training, affiliation, and supervision evidence required for a person's assigned role, service, state, payer, program, and date.
CMS states that Medicaid peer qualifications and supervision are defined through state benefit design, so a national credential label does not answer every assignment question. The system should retain the source and effective dates behind each rule and verification.[1][2]
Which data belongs in a credential record?
Store enough evidence to verify status and scope while limiting access to sensitive workforce information. Distinguish the credential from documents, training events, checks, payer enrollment, and organization authorization.
| Criterion | How to evaluate it |
|---|---|
| Credential identity | Type, issuing body, identifier, jurisdiction, status, scope, issue, effective, expiration, and renewal dates. |
| Evidence | Source document or official verification, date checked, checker, result, limitations, and next verification. |
| Training | Course, provider, version, hours, completion, assessment, renewal, audience, and approved equivalency. |
| Program qualification | Service, state, payer, site, population, supervisor, background check, affiliation, and organization approval. |
| Restrictions | Suspension, lapse, investigation, limited scope, leave, pending renewal, and action owner with appropriate access. |
| History | Every status, evidence, rule version, notification, decision, assignment block, and override is attributable and dated. |
How should eligibility for an assignment be tested?
The decision should use the person's verified evidence and the requirements effective for the proposed service date. Missing or conflicting evidence should hold the assignment or route authorized review.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Person | Verified identity, role, employment or affiliation, and organization | Authoritative workforce source |
| Service | Program, payer, state, site, population, modality, and proposed date | Configured service requirement |
| Qualification | Credential, training, enrollment, checks, supervisor, and any restrictions | Current source evidence |
| Decision | Eligible, ineligible, pending, exception, or escalation with reason | Human review where judgment is required |
| History | Rule, evidence, decision, notification, and later change | Reproducible for a historical service date |
What should credential software demonstrate?
Test new onboarding, upcoming expiry, late renewal, changed state rule, cross-program assignment, supervisor change, restriction, evidence correction, and offboarding.
- Can one person have multiple credentials, trainings, enrollments, roles, sites, programs, supervisors, and different effective dates?
- Can the system distinguish self-reported, uploaded, verified, pending, expired, restricted, and superseded evidence?
- What action occurs before expiry, at expiry, after renewal, and when source verification conflicts with the stored record?
- Who can view sensitive evidence, verify it, change status, approve an exception, and assign the person?
- Can historical assignments be evaluated against the rule and evidence in effect on the service date?
What should the software never claim?
It should never claim that an alert, uploaded document, unchecked box, or database status independently proves current legal, payer, credential, or program eligibility.
Assign qualified owners to source maintenance and verification. Keep rule changes prospective unless an authorized correction establishes otherwise, prevent silent overrides, and require review when evidence is missing, conflicting, expired, or outside configured scope.
Frequently asked questions
Is a state peer certification enough to bill Medicaid?
Not necessarily. Billing can also depend on the benefit, provider and practitioner enrollment, affiliation, supervision, service, authorization, payer, code, documentation, and date.
Can an uploaded certificate be treated as verified?
Only if the organization's approved process allows it and the responsible person confirms authenticity, status, scope, dates, and issuing source. Keep uploaded and verified states distinct.
Should expired credentials delete old service records?
No. Preserve historical records and the evidence or status used at the time. Resolve possible ineligible services through the approved review process.
Can credential software replace the issuing authority?
No. The authoritative issuer or official source controls the credential. Software helps the organization store, verify, monitor, and act on that information.
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.
- Operate: Peer Support Workforce and Caseload Management: Peerakeet. Peerakeet workforce, caseload, schedule, supervision, and task workflows.
- 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.
- The HIPAA Security Rule: U.S. Department of Health and Human Services. Official federal overview of safeguards for electronic protected health information.