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.

FieldMeaningNotes
appointment.external_refScheduling system appointment IDRequired — the join key back to your record
veteran.file_numberBeneficiary / claim file numberRequired — identifies who is paid
facility.codeFacility or clinic identifierRequired — determines the destination address
appointment.scheduled_atAppointment date and timeRequired — ISO 8601 with offset
appointment.kindscheduled | emergencyDefaults to scheduled
attendance.statusattended | no_show | emergency_walk_inRequired — the only clinical-adjacent flag exchanged
attendance.occurred_atCheck-in timestampDefaults to receipt time
travel.one_way_milesHome-to-facility distanceOptional — computed from addresses on file when omitted
travel.authorized_mealsMeal per diem authorizedOptional boolean
travel.authorized_lodgingLodging authorizedOptional boolean
travel.ticket_amountAir / rail / bus fare receiptedOptional 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

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 running
Published for the VAVC platform. Product home: VAVerifyCare.com · A product of The Concept Factory, LLC, founded by Don "Corky" Mitchell, disabled U.S. Air Force veteran and former Special Operations helicopter pilot.

VAVerifyCare.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.