Skip to content
Garnet

Product

EVV that holds up in the field and at the aggregator.

Garnet captures each visit at the point of care, sends it to your state's aggregator, and explains in plain English anything that comes back. Here's how the pieces fit together.

How a visit moves through Garnet.

  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.

Visit capture

Captured at the point of care, with or without signal.

Caregivers clock in and out from their phone's browser. Each visit carries the six data elements the Cures Act requires.

  • GPS at both ends of the visit

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

  • Offline by design

    Visits are encrypted and held on the phone, then sent automatically when signal returns.

  • Nothing to download

    Caregivers open Garnet in their phone's browser and add it to their home screen.

Learn about visit capture

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, in words your team can act on.

  • What happened

    Every aggregator rejection code is mapped to a plain-English description. Your team never sees a raw code.

  • What to do next

    Each exception comes with a way to resolve it, so the answer doesn't live in one person's head.

  • Oldest first

    Exceptions are sorted by how long they've been open, and marked as they age.

Learn about the exception queue
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.

Multi-state

One agency, more than one state.

Which aggregator, which environment, and which credentials apply is set for each state you operate in, not once for the whole agency.

  • Live in one state, onboarding in another

    Run in production where you're ready while you test in the next state.

  • Sandata today, more aggregators to come

    Garnet connects to Sandata. Other aggregators will be added, each set up per state the same way.

  • Records sent in the required order

    Clients, employees, then visits, each numbered in sequence for its state.

Compliance

Audit-ready by default.

The record your auditor asks for is kept as the work happens, not reconstructed afterward.

  • An audit log that can't be rewritten

    Append-only, enforced by the database itself, and retained six years.

  • Reason codes on manual entries

    Your state's approved reason codes, with a note where the state requires one.

  • Reports you can export

    Eight standard visit and compliance reports, each as CSV.

Learn about compliance

Where Garnet stops.

Knowing what a system doesn't do matters as much as knowing what it does.

  • Claims and billing

    Garnet produces the verified visit data you bill from. It doesn't submit Medicaid claims.

  • Payroll

    Export verified visits as CSV for the payroll process you already use.

  • Schedule building

    Your schedule drives clock-in and is checked against authorizations. Garnet doesn't optimize routes or build schedules for you.

See it with your state in mind.

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

Request a demo

Garnet is invite-only. Every agency starts here.