VSiP sessions

If a prison has been onboarded to VSiP, the prison is found in the orchestration endpoint /config/prison/supported then sessions are sourced from the orchestration endpoint /visit-sessions for the specific prisoner. No filtering logic is applied in PVB, all related business logic for capacity, non-association, etc. is outside the concern of PVB and remains in VSiP.

In order for the PVB to use the VSiP intelligence, the prison-visit-2 service needs to be released - this triggers a refresh of the cached settings.

There are 3 environment variables which control the API presented by VSiP, detailed in the public app [Configuration] files (https://github.com/ministryofjustice/prison-visits-public/wiki/Configuration)

If the VSiP endpoint cannot be found for a prison, or if the prison is not using VSiP then the sessions from the prison yaml files are used (see below).

yaml files

The configuration and time slots for each prisons (not using the VSiP endpoint) is set in the establishments yaml files.

NOMIS

Some prisons used to rely on NOMIS time slots for bookings, with the NOMIS time slots take precedence over the yaml files.

Since the introduction of the helm deployment, this has been moved to other files for each environment:

• DEV Link to deployment file
• STAGING Link to deployment file
• PROD Link to deployment file

Any prisons listed in PUBLIC_PRISONS_WITH_SLOT_AVAILABILITY and STAFF_PRISONS_WITH_SLOT_AVAILABILITY will use NOMIS time slots instead of the yaml files.