Skip to content

Every visit verified.Every rejection explained.

GPS-verified clock-in, aggregator transmission, and plain-English rejections in one place.

Invite-only. Every agency starts with a conversation.

21st Century Cures Act

A visit that doesn't reach the aggregator clean is a visit you don't get paid for.

Every Medicaid-funded personal care and home health visit has to be verified electronically and sent to your state's aggregator. In states that validate claims against EVV data, a visit that never arrives clean can mean a claim that isn't paid. Garnet gets it there clean, and tells you plainly when it doesn't.

A smiling caregiver holding hands with an older woman in her home

Everything between the front door and the aggregator.

Four parts of Garnet, built around how Medicaid home care actually works.

Exception queue

Two visits need attention. One was accepted.

REJECTED 1207 CLIENT_IDENTIFIER_UNMATCHED

The state doesn't recognize this client's Medicaid ID

Needs action

Check the ID on the client's record against their eligibility letter. Correct it, then resend the visit.

REJECTED 3310 SVC_AUTH_DATE_RANGE

This visit falls outside the client's authorization dates

Needs review

If the authorization was renewed, update its end date on the client's record, then resend the visit.

ACK 0000

Visit accepted by the aggregator

Accepted

Nothing to do.

Illustrative example. Codes and wording vary by aggregator.

Exception queue

Rejections explained in English.

When a visit doesn't meet your state's program rules, the aggregator rejects it. Garnet puts every rejection in one queue with what went wrong and how to fix it, and polls for status so you know a visit was accepted without logging in somewhere else.

Learn about the exception queue

Specific, not superlative.

What Garnet does, in details you can check for yourself in a demo.

  • 2 GPS captures per visit

    Location and accuracy radius at clock-in and at clock-out, checked against the client's service address.

  • 6 yrs Audit log retention

    Append-only. Entries are added and never edited or removed.

  • 0 Raw error codes to decode

    Every aggregator rejection is mapped to plain English and a way to resolve it.

Built for the obligations HIPAA places on you.

Compliance takes policies and training too, so we won't hand you a badge. These are the specific safeguards Garnet provides.

Role-based access

Everyone sees only what their role requires.

Administrators, supervisors, and caregivers have separate permissions. Caregivers see only their own visits and assigned clients.

From the client's door to a visit you can bill from.

  1. The caregiver clocks in

    From their phone, against the scheduled visit. GPS is captured at clock-in and clock-out, with or without signal.

  2. Garnet transmits the visit

    Client, employee, and visit records go to your state's aggregator in the required order, in the background.

  3. Exceptions come back in English

    If a visit doesn't meet the state's program rules, it appears in your queue with what happened and what to do.

  4. You bill from verified data

    Export verified visits as CSV for billing. Garnet produces the visit data you bill from. It does not submit claims.

See what a rejection looks like in plain English.

We'll walk you through visit capture, transmission, and the exception queue, and answer your compliance lead's questions directly.

Garnet is invite-only. Every agency starts here.

A laptop open on a wooden desk

What agencies ask us first.