Skip to content
Garnet

Exception queue

Rejections explained in English.

When a visit doesn't meet your state's program rules, the aggregator rejects it with a code. Garnet turns every code into what happened and what to do about it, in one queue your team can work from.

Plain English

No more decoding.

Your team never sees a raw error code. Each rejection arrives as a sentence and a next step.

  • What happened

    The problem described in terms of your own records: the client, the caregiver, the authorization, the visit.

  • What to do

    A resolution path that points to the record to fix, so the answer doesn't depend on one person's memory.

  • Worked by the right people

    Agency admins and supervisors work the queue. Caregivers never see aggregator errors.

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.

What happens after a visit is captured.

  1. Records go out in the background

    Client, employee, and visit records are sent to your state's aggregator, such as Sandata, in the order it requires, each with its own sequence number.

  2. Garnet checks the result

    Garnet checks each record's status with the aggregator and retries with backoff if it's slow or down. Caregivers are never held up.

  3. Rejections land in one queue

    Every rejection appears in one place, explained in plain English, oldest first.

  4. Your team fixes it at the source

    Follow the resolution path and correct the record. The queue shows what's still open.

Built to be worked, not just read.

  • Marked as it ages

    Each exception shows how long it's been open: aging after two days, overdue after five.

  • Open, acknowledged, resolved

    Separate views keep what's new apart from what's already in hand.

  • Searchable

    Search the queue to find the exception for a specific visit.

  • Retries without you

    If the aggregator doesn't answer, Garnet tries again with backoff before anything reaches your queue.

  • Role-based

    Agency admins and supervisors see the queue. Caregivers see only their own visits.

  • On the record

    Opening the queue is written to the audit log, like other access to visit data.

Multi-state

Each state, its own connection.

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.

  • Sequence numbers per state

    Kept separately for each state program and record type, and never reused.

Questions about exceptions.

More of Garnet.

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.