What should an encounter record establish?
It should establish the actual service before any billing interpretation: participant, peer, date, start and end, breaks, location, modality, service activity, goal connection, participant response, record author, and review status.
H0038 has a national HCPCS description tied to 15 minutes, but the code definition does not determine whether a state covers the service, which provider may bill, which modifiers apply, how partial units are handled, or what limits and documentation control the claim.[1][2]
Which layers must remain separate?
Preserve service facts, program classification, payer interpretation, unit calculation, and claim status as related but distinct layers. This makes a rule change possible without rewriting history.
| Criterion | How to evaluate it |
|---|---|
| Actual encounter | People, date, times, breaks, locations, modality, attendance, activity, goal, response, note, and signatures. |
| Program service | Approved service type, program, site, funding source, staff role, supervision, and organization policy. |
| Coverage rule | State, payer, benefit, provider type, practitioner, authorization, code, modifiers, POS, limits, and effective date. |
| Unit result | Eligible minutes, excluded time, method, resulting units, limit checks, overlap checks, and rule source. |
| Review decision | Passed, held, corrected, approved, excluded, or escalated, with reason, reviewer, and timestamp. |
| Downstream status | Report, invoice, claim, acknowledgment, adjudication, adjustment, payment, or denial linked without overwriting the encounter. |
How should unit calculations be audited?
A reviewer should be able to reproduce the result from documented time and the versioned source rule. The system should never infer missing encounter time to create a billable unit.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Time source | Actual start, end, breaks, attendance, and eligible duration | Signed or approved service record |
| Rule identity | Payer, program, code, unit definition, partial-unit method, limits, and effective date | Current official manual, table, or contract |
| Calculation | Eligible minutes transformed under the identified rule | Reproducible formula and retained inputs |
| Conflict checks | Overlap, duplicate, authorization balance, daily limit, group logic, and incompatible service | Visible pass, hold, or exception |
| Human approval | Authorized reviewer confirms unresolved judgment and proposed claim fields | Reviewer, decision, timestamp, and reason |
What should encounter-tracking software demonstrate?
Test individual, group, telehealth, travel or outreach when relevant, partial time, a cancellation, an overlap, a correction, and a payer rule change with effective dates.
- Can actual service time be preserved separately from scheduled time, documentation time, travel, and calculated units?
- How are group attendance, practitioner time, participant-level records, and group coding connected without duplication?
- Can state and payer rules be versioned so a past service continues to use the rule effective on its date?
- Does an exception hold the proposed claim while leaving the truthful encounter record intact?
- Can exported totals be reconciled to participants, peers, services, notes, units, and excluded records?
What is the safest operating principle?
Capture the service truth once, apply an identified current rule transparently, keep unresolved claims on hold, and require authorized human review before submission.
A schedule is not proof that a service occurred, a note is not automatically a billable claim, and a 15-minute code description is not a universal rounding rule. Use official state and payer instructions for the exact service date and preserve every assumption behind the calculation.[1][2]
Frequently asked questions
Does one H0038 unit always equal any 15 minutes on the schedule?
No. The code description uses 15 minutes, but only eligible documented service time counts, and the applicable payer controls partial-unit, limit, overlap, and other rules.
Can documentation time be added to service time?
Only when the controlling source clearly allows it for the exact service and payer. Do not assume administrative or documentation time is separately or automatically billable.
Should scheduled time populate actual time?
Scheduled time can provide context, but the service record must reflect what actually occurred. The author should verify and correct the facts before signing.
Can software approve a claim automatically?
It can apply deterministic checks and route exceptions, but authorized people remain responsible for coverage, source interpretation, documentation, coding, and claim decisions.
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.
- 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.
- 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.
- Document: Notes, Assessments, and Supervisor Review: Peerakeet. Peerakeet structured notes, assessments, signatures, and review workflows.