Medicaid and HCBS

Connect Medicaid service delivery to the evidence behind it.

Bring schedules, EVV, authorizations, visit exceptions, documentation, claims, remittance, and operational ownership into one traceable flow.

Operations / Service evidenceRiverside branch DP
SERVICE EVIDENCEAuthorization to payment
In scope
AUTHORIZATIONPersonal care · HCBSValid through Sep 30 · 84 of 120 hours used
70% used
ScheduledAuthorization checked
EVV receivedTime and source linked
3Review1 exception owned
4ClaimPending approval
OWNED EXCEPTIONService code review

Visit evidence is complete. Confirm the program-specific billing selection.

Due today · Billing team
Illustrative product view

What changes

Exact support matters more than broad claims

EVV and Medicaid workflows vary by state, program, payer, service, aggregator, and implementation model. Ethiya should show precisely what is supported, how data moves, and which exceptions remain with the agency.

Connected capabilities

Each part of the workflow keeps its context, boundaries, and accountable owner.

01

Start before the visit

Keep service and authorization context available during scheduling.

  • Apply agency and program rules with effective dates.
  • Identify missing eligibility or expiring prerequisites.
  • Prevent avoidable conflicts without hardcoding one policy for every agency.
02

Capture and review visit evidence

Connect supported EVV methods to the scheduled visit, assigned caregiver, service, time, location or verification source, documentation, and exception process.

03

Make transmission states visible

Accepted, rejected, pending, corrected, and resubmitted are operational states, not technical footnotes. Show the payload or evidence, reason, owner, next action, and history where partner systems permit it.

04

Carry approved work into claims and payment

Use verified service, authorization, rate, and payer context to prepare supported claim transactions. Reconcile remittance and payment back to the visit and exception that produced them.

Honest compliance language

Keep compliance language honest

Ethiya can support an agency's compliance process. It cannot guarantee that every schedule, visit, note, transmission, claim, or staff decision meets every applicable rule.

Questions to ask

Clear answers belong in the evaluation.

Is Ethiya EVV-compliant in my state?+

Ethiya supports EVV operations, but compatibility varies by state program, aggregator, service, data requirements, and agency configuration. Ethiya confirms exact, dated support during evaluation and does not claim universal state compliance.

Does Ethiya connect to state aggregators?+

Ethiya supports aggregator synchronization where a production connection is available. The evaluation documents the exact state and program scope, direction, frequency, status visibility, and known limitations.

Does Ethiya manage authorizations?+

Yes. Ethiya supports authorization tracking, scheduling context, utilization, alerts, billing controls, and claim linkage.

Can Ethiya submit Medicaid claims?+

Yes, where the required transaction and connection are supported. Ethiya documents the exact claim format, clearinghouse or payer connection, program, response workflow, and limitations during evaluation.

See it in context

Evaluate the exact workflow

Bring the state, program, payer, service code, EVV model, aggregator, authorization logic, and claim path. We will document what Ethiya supports, what integrates, and what remains out of scope.

Review your program with Ethiya