-
Notifications
You must be signed in to change notification settings - Fork 6
Lighthouse APIs
Gabriel Zurita edited this page Oct 18, 2024
·
3 revisions
We prefer to use Lighthouse APIs when possible. It usually provides the quickest path to production since approvals are minimal, builds on existing working code, and has fewer unknowns.
Some APIs need CCG (machine-to-machine auth) to be enabled. Such features should be requested sooner rather than later.
Of particular relevance to VRO:
- Patient Health API (FHIR) to get health evidence to support fast-tracking a claim
- Benefits Claims API to get claim data; details
- Veteran Verification APIs don't return veteran information like SSN, name, and DOB. It will need to be expanded so VRO can get veteran information to generate a PDF; additionally, VRO needs the veteran's ICN -- see the MPI section below
Useful resources
- API Backend Systems - backing VA system(s) for each Lighthouse API
Pertinent Secrets
VRO_SECRETS_LH
- LH_ACCESS_CLIENT_ID
- LH_PRIVATE_KEY_BASE64