Vendor documentation · VAVerifyCare.com
Attendance integration spec
The VAVC platform needs exactly one fact from your medical IT platform: did the veteran show up. Everything else — distance, rates, per diem, who gets told — is resolved on this side, so an integration is a single call.
1. Field mapping
Map your scheduling and demographic fields to these names. Only the first six are required; anything omitted falls back to data already on file.
| Field | Meaning | Notes |
|---|---|---|
| appointment.external_ref | Scheduling system appointment ID | Required — the join key back to your record |
| veteran.file_number | Beneficiary / claim file number | Required — identifies who is paid |
| facility.code | Facility or clinic identifier | Required — determines the destination address |
| appointment.scheduled_at | Appointment date and time | Required — ISO 8601 with offset |
| appointment.kind | scheduled | emergency | Defaults to scheduled |
| attendance.status | attended | no_show | emergency_walk_in | Required — the only clinical-adjacent flag exchanged |
| attendance.occurred_at | Check-in timestamp | Defaults to receipt time |
| travel.one_way_miles | Home-to-facility distance | Optional — computed from addresses on file when omitted |
| travel.authorized_meals | Meal per diem authorized | Optional boolean |
| travel.authorized_lodging | Lodging authorized | Optional boolean |
| travel.ticket_amount | Air / rail / bus fare receipted | Optional decimal |
2. Inbound check-in call
Fire this the moment your check-in screen is saved. It is idempotent per appointment: a repeat call returns the existing attendance event rather than creating a second claim.
POST /api/public/attendance
Content-Type: application/json
apikey: <project publishable key>
{
"external_ref": "SCHED-889321",
"file_number": "VA-104-2291",
"status": "attended",
"ticket_amount": 0
}3. Outbound attendance event
Every active subscriber office receives this payload. Because the subscriber list is configuration, an office discovered later is added by an administrator in minutes — the contract below does not change.
{
"event": "attendance.confirmed",
"event_id": "b6f1c0e2-...",
"occurred_at": "2026-02-11T14:32:05Z",
"veteran": { "file_number": "VA-104-2291", "bank_account_last4": "4417" },
"facility": { "code": "VAMC-DEN", "name": "Denver VA Medical Center" },
"appointment": {
"external_ref": "SCHED-889321",
"clinic": "Cardiology",
"kind": "scheduled",
"scheduled_at": "2026-02-11T14:00:00Z"
},
"attendance": { "status": "attended", "source": "clerk_console" },
"reimbursement": {
"round_trip_miles": 84,
"mileage_rate": 0.415,
"mileage_amount": 34.86,
"deductible": 3.00,
"meals_amount": 0,
"lodging_amount": 0,
"ticket_amount": 0,
"total_amount": 31.86,
"status": "pending"
}
}4. Boundaries
- No clinical content. Diagnoses, notes and orders never enter or leave this system. Attendance plus clinic name is the entire clinical surface.
- Read-only for veterans. A veteran sees their own attendance and payment history and cannot alter it; corrections are made by the facility travel office by phone, which keeps an accountable human in the loop.
- Facility-scoped access. Clerks see only their own facility's queue; Travel Pay sees verified claims; every state change is written to an immutable audit log.
- Rates are configuration. Mileage rate, per-trip deductible and per diem amounts are versioned by effective date, so a rate change never requires a code release.
Adapting to another agency
Nothing in the contract is VA-specific except the vocabulary. Replace the file number with any beneficiary identifier, adjust the rate table, and register whichever offices must be notified. The check-in event stays identical.
See it runningVAVerifyCare.com (VAVC) is a commercial product of The Concept Factory, LLC. It is not a government website and is not affiliated with, endorsed by, or operated by the U.S. Department of Veterans Affairs.