Development environments

Development (non-prod) and prod environments for the various systems, APIs, and data sources with which VRO interacts.

• Environment Connections
  • VRO should use Lighthouse API (as an intermediary) when possible -- this can simplify getting access and staying up-to-date.

Prior RRD Testing

Testing the RRD prototype involved these environments:

• va.gov staging user
• Lighthouse sandbox
• VBMS uat
• EVSS pint and VBMS uat interact with the linktest (fake) data.

We'll likely do something similar for testing VRO.

• EVSS preprod corresponds with VBMS prodtest

VRO v1 Testing

• va.gov staging
• Lighthouse sandbox
• VRO sandbox (sandbox.lighthouse.va.gov/abd-vro)
  • VRO v1 connects to only Lighthouse (not VBMS or EVSS)
• VBMS uat
• EVSS pint and VBMS uat interact with the linktest (fake) data.

VRO v2 Testing

• va.gov none - no prod-test env exists
• MAS prodtest
• Lighthouse prod
• VRO sandbox (sandbox.lighthouse.va.gov/abd-vro)
  • VRO v2 connects to MAS prodtest, BIP (for VBMS prodtest), and Lighthouse prod
• VBMS prodtest

LHDI

On the nonprod cluster:

• DEV - https://dev.lighthouse.va.gov
  • example: accessible on the VA network at https://dev.lighthouse.va.gov/abd-vro/v1/example/claimsubmissions or https://dev.lighthouse.va.gov/abd-vro/swagger
• QA - https://qa.lighthouse.va.gov
  • https://qa.lighthouse.va.gov/abd-vro
• SANDBOX (used as pre-prod) - https://sandbox.lighthouse.va.gov
  • https://sandbox.lighthouse.va.gov/abd-vro
  • The environment goes through the same release gates that deployments in the production environment.

On the prod cluster:

• PROD - https://api.lighthouse.va.gov
  • https://api.lighthouse.va.gov/abd-vro

See Kubernetes clusters for details

va.gov

va.gov (a.k.a. vets-api)

From VA Platform doc and devops repo

• sandbox
• utility
• dev - https://dev.va.gov/
• staging - https://staging.va.gov/
  • Test User Dashboard "helps teams to find acceptable high quality test users that are available for use on staging" -- also mentions "requesting a new test account"
• prod - https://www.va.gov/

Lighthouse API

From Lighthouse doc

• sandbox
  • use existing test users or submit new test user requests (creation or health data modification)
• prod

Lighthouse Sandbox Test Patient Data Management

• There's 2 ways to submit requests to the Health API team:
  • Email [email protected] (consumer support team's preferred method)
  • Fill out the contact form at developer.va.gov/support/contact-us
• A few reminders:
  • It's okay to send one email that includes the creation of 3 health test patients, for example, but if subsequent changes are needed to the health data for those 3 test patients, a new email should be sent
  • Keep [email protected] in the cc line of the email when responding to requests and questions
  • Specify that the request is for health test patients
  • Indicate which team the request is coming from
  • Request does not need to be in a specific format, but be as specific as possible
• Estimated turn around time: ~1 week, depending on the intricacies of the change

VBMS

VBMS Overview

Logins

In order to login you need:

• Station IDs: the 3-digit number that corresponds to your Regional Office. We usually use 283 for Developers. ARC is 397, and Florida is 317.
• User ID: is the Active Directory account name under which you will authorize access.
• PIV card

Local Testing of VBMS and BGS

• dev
  • bep.dev.vbms.aide.oit.va.gov
  • bepdev.vba.va.gov
• uat (a.k.a. devtest) - Core: https://www.uat.vbms.aide.oit.va.gov/vbmsp2
  • to set up the test Veterans in VBMS UAT, see Notion page - involves logging in to VBMS Core, VBMS Rating, VBMS Awards.
• preprod (a.k.a. prodtest) - Core: https://www.pre.vbms.vba.va.gov/vbmsp2
  • duplicate of production data updated twice a day
• prod

EVSS

• INT
• PINT (aka SQA or staging)
• PreProd
• Prod

CMP/MAS

CMP (a.k.a. MAS - Mail Automation Systems)

• dev - https://iam-dev.ibm-intelligent-automation.com
• test - https://iam-test.ibm-intelligent-automation.com
• prod

MAS tests its OCR function in VBMS prodtest

Old related ticket

MPI

MPI (Master Person Index, a component of Master Veteran Index (MVI) or formerly known as MVI or Master Patient Index)

MPI can be used to get the Integration Control Number (ICN) for a given veteran.

• Lighthouse Veteran Verification API v2 could provide this lookup capability. API-17363 will look into the feasibility of this (Slack).

Resources

• MPI Testing refers to existing Ruby code
• VA MPI Playbook list service functions
• MPI Service Description
• Contacts